5400 LCP Release 4.0 Alarm Dictionary

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
ISSUE 4
MARCH 2011
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
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
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
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
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
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
March 2011
Contents
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
x Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
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
March 2011
List of figures
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xii Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
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
March 2011
About this document
....................................................................................................................................................................................................................................

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 floating IPv4
The following topics have been updated:

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

(p. 8-38)
• “To add a new external fixed IPv6
• “To add a new external floating IPv6
....................................................................................................................................................................................................................................
xiv Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
March 2011
About this document
....................................................................................................................................................................................................................................

reissue
• “To add a new external IPv6 subnet”

(p. 8-42)
(p. 8-40)
(p. 8-44)

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
March 2011
About this document
....................................................................................................................................................................................................................................

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 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)
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
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
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
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
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
March 2011
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
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
...................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
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
...................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures To add, modify, or delete the SNE(s) for MI-GUI discovery
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Discovery Configurator window
The Discovery Configurator window, with Node Discovery tab selected:
Figure 3-1 Node Discovery
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures To display or change the local title on 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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures Northbound Interface task flow
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures Northbound Interface task flow
....................................................................................................................................................................................................................................
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)
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures To load Northbound Interface MIB at the MI-GUI
....................................................................................................................................................................................................................................
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

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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures To load Northbound Interface MIB at the MI-GUI
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures To select MIB version
....................................................................................................................................................................................................................................
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

The northbound interface MIB Lucent-WebNMS-MIB is loaded.
Required skills
Users must have a general knowledge of SNMP and MIBs.
Procedure
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures To configure Northbound Interface manager
....................................................................................................................................................................................................................................
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

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
...................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Select OK. A new row will appear in the table.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures To reconstruct lost traps
....................................................................................................................................................................................................................................
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

It is assumed that the following procedure has been performed: “To load Northbound
Interface MIB at the MI-GUI” (p. 3-12)
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures Supported NBI traps/notifications (MIB version 2)
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................

cesAlarmChanged Notification is generated when cesSystemDN
the severity of an alarm has cesAlarmNotification
changed.
Source:
cesNotiSequenceNum
cesAlarmType
cesAlarmTime
cesAlarmName
cesAlarmServiceUser
cesAlarmCleared Notification is generated when cesAlarmId
an alarm is cleared. cesSystemDN
cesNotiSequenceNum
cesAlarmType
cesAlarmTime
cesAlarmName
cesAlarmServiceUser
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................

cesAlarmListRebuiltNotifica- This notification is send to the cesNotiSequenceNum
tion manager indicating that the cesAlarmType
alarm list has been rebuilt.
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
deleted from the management
domain cesEventManagedObjectInstance
cesSystemDN
cesEventTime
cesMOAttrChangeNotifica- The MI sends a cesNotiSequenceNum
tion cesMOAttrChangeNotification cesEventType
to the manager when any
discovered MOs one or more
attributes are changed. cesEventManagedObjectInstance
cesSystemDN
cesEventTime
cesEventAttributeIdentifier
cesEventAttributeType
cesAttributeOldValue
cesAttributeNewValue
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................

cesMOStateChangeNotifica- The MI sends a cesNotiSequenceNum
tion cesMOStateChangeNotification cesEventType
to the manager when any
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.
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
cesAttributeNewValue This variable indicates the new value of the MO's X.731
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
SNMP traps (notifications)
The following table defines SNMP traps, their definition, and the fields or objects
supported for each trap:

cesPMfileAvailable This notification indicates cesNotiSequenceNum
that a Performance cesEventType
Measurements file has
been created and may be
retrieved by the Element cesEventManagedObjectInstance
Management System. cesSystemDN
cesEventTime
cesAppNotification This notification is a cesNotiSequenceNum
generic event notification. cesEventType
cesEventManagedObjectInstance
cesSystemDN
cesEventTime
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures To configure the MIB browser for NBI access via SNMPv3
....................................................................................................................................................................................................................................
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

Required skills
Users should have a general knowledge of SNMPv3 and MIBs.
Procedure
...................................................................................................................................................................................................
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).
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures To configure the MIB browser for NBI access via SNMPv3
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures To clone a user for SNMPv3 from MI CLI
....................................................................................................................................................................................................................................
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

• Ensure the default user exists
• Connect to the MI-GUI via CLI access to execute commands.
Refer to User Interface, 270-702-013.
Procedure
...................................................................................................................................................................................................
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]
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures To clone a user for SNMPv3 from MI CLI
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures Description of discovery, growth/degrowth
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures Global rediscovery 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

• 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
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures Global rediscovery using the MI-GUI's CLI
....................................................................................................................................................................................................................................
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

• The MI-GUI must be able to reach the SNE that discovery is being performed on
• You must connect to the MI-GUI via CLI access to execute CLI commands.
Procedure
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures Global rediscovery using the MI-GUI's CLI
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures Explicit rediscovery 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

• You must connect to the MI-GUI via the web-based user interface.
Procedure
...................................................................................................................................................................................................
1 At the MI-GUI, navigate (using the Tree View or Map View) to the specific element and
select Rediscover.
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures Explicit rediscovery using the MI-GUI's CLI
....................................................................................................................................................................................................................................
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

Procedure
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures To enable the auto-delete option during discovery
....................................................................................................................................................................................................................................
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

• Changing the default value can only be performed at the MI-GUI's CLI
Procedure
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures Discovery degrowth 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

• 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
...................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
3 Click OK.
Result: A window confirming the deletion displays.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures Discovery degrowth using the MI-Agents CLI
....................................................................................................................................................................................................................................
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

• 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
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures Discovery degrowth using the MI-Agents CLI
....................................................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - MI-GUI procedures MI-GUI 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

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
...................................................................................................................................................................................................
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.

....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Inventory Report window
The Inventory Report window displays:
Figure 3-3 Inventory Report
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Generate Inventory Report
The window used to generate an inventory report:
Figure 3-4 Generate Inventory Report
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
View Inventory Report
The window used to view inventory reports with collapsed folders:
Figure 3-5 View Inventory Report
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
The window used to display the inventory data with a selected item:
Figure 3-6 Display Inventory Report
....................................................................................................................................................................................................................................
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
...................................................................................................................................................................................................................................
March 2011
Manage system configuration - view or control the Overview
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - view or control the To display the current state of the MI Virtual Cluster
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

• 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
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - view or control the To display the current state of a MI Virtual Machine
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

allow requested commands (for example if a switch-over command is entered and
switch-over).
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................

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

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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - view or control the To start the MI Virtual Cluster
operational state
....................................................................................................................................................................................................................................
To start the MI Virtual Cluster

Purpose
Use this procedure to start the MI Virtual Cluster.
Before you begin

• You must connect to the MI-GUI via CLI access to execute CLI commands. Refer to :
• You must be able to log in as 'root'.
switch-over).
Procedure
...................................................................................................................................................................................................
1 From the MT, telnet/ssh to the MI-GUI host and log in as lss
...................................................................................................................................................................................................
2 Choose editor and enter

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

Start the Virtual Cluster startMI (this command is an alias forMIcmd
start vc)
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - view or control the To start a MI Virtual Machine
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

User Inteface Guide, 270-702-013.
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
...................................................................................................................................................................................................
...................................................................................................................................................................................................

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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - view or control the To stop the MI Virtual Cluster
operational state
....................................................................................................................................................................................................................................
To stop the MI Virtual Cluster

Purpose
Use this procedure to stop the MI Virtual Cluster.
Before you begin

switch-over).
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................

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

Stop the Virtual Cluster stopMI (this command is an alias for MIcmd stop vc
)
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - view or control the To stop a MI Virtual Machine
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

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
...................................................................................................................................................................................................
...................................................................................................................................................................................................

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

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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - view or control the To switch states of MI Virtual Machines in Virtual Cluster
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

Refer to User Interface, 270-702-013.
switch-over).
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Choose editor and enter

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

Switch states of Virtual Machines in MIcmd switch
a Virtual Cluster
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - view or control the To modify the state of a diskless host
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

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
...................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
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
....................................................................................................................................................................................................................................
March 2011
operational state
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
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
...................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
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
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
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
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
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

Release notes, capacity figures from System Guide, traffic expectation model.
Procedure
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
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

Release notes, OAM&P manual, LWS acceptance test plan, customer test guideline.
Procedure
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth Growth system preparation process
....................................................................................................................................................................................................................................
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

...................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To install new hardware
....................................................................................................................................................................................................................................
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

Required user skills
The person performing the installation should be familiar with the installation guidelines.
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
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To cable new hardware
....................................................................................................................................................................................................................................
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

• 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
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To cable new hardware
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To verify growth system stability
....................................................................................................................................................................................................................................
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

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.
• Logfiles
• Alarm history.
System requirements
The user should be logged on the MI-GUI as root.
Procedure
...................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To verify growth system stability
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
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
....................................................................................................................................................................................................................................
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

...................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
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

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
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
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

This procedure is performed at the MI command line interface.
Procedure
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
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

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
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth Growth implementation process
....................................................................................................................................................................................................................................
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

...................................................................................................................................................................................................
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).
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth Growth implementation process
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
3 If you grow service on diskless hosts (on ATCA), use: “To grow service of diskless hosts
for multiple services” (p. 5-54).
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskless hosts
....................................................................................................................................................................................................................................
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

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)
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Procedure
...................................................................................................................................................................................................
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
hostdat.layout
hostdat.ksh
...................................................................................................................................................................................................
5 Execute the following command as root.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
...................................................................................................................................................................................................
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
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)
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
90: FRU # 0
Entity: (0xa0, 0x60)
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
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
N) for no more: n
y
IPv6 subnet number 4, subnet prefix 2500:0:0:0202:0:0:0:0, prefix
length 64, subnet name campus6
length 64, subnet name signal6
length 64, subnet name billing6
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
N) for no more: 5
N) for no more: n
Enter the SUBNET ID for the IPv4 default gateway: 2
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
cdr
cs
ss7
h248
vlr
ims
fsdb
fs5k
gls
gjs
gos
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
none
y
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
return for skip :1
Please enter offset for ims: 10
N) for no more: 2
N) for no more: n
y
return for skip :4
N) for no more: 5
N) for no more: n
none
y
return for skip :1
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
N) for no more: 2
N) for no more: n
y
return for skip :4
N) for no more: 5
N) for no more: n
Do you config IPv4 for fs5k Service (y/n) ?
y
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
N) for no more: n
Do you config IPv6 for fs5k Service (y/n) ?
y
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
N) for no more: 5
Enter IPv6 address for pair 1 fs5k service: 2500:0:0:0203:0:0:0:14
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
N) for no more: n
Do you config IPv4 for h248 Service (y/n) ?
y
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
N) for no more: n
Do you config IPv6 for h248 Service (y/n) ?
y
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
N) for no more: 5
Enter IPv6 address for pair 1 h248 service: 2500:0:0:0203:0:0:0:15
Valid NI_Type for h248 Service IP 1:
diam_rf,dns,enum
Enter comma separated IP 1 NI Types for h248,enter return for
N) for no more: n
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
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
**************************************************************
**************************************************************
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!
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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>
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To grow hardware and service on diskful hosts
....................................................................................................................................................................................................................................
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.
• 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

• The system is stable.
• 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)
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
– NI types
Procedure
...................................................................................................................................................................................................
1 Open two windows and from both log into MI-1 as root.
...................................................................................................................................................................................................

MIcmd state vc
> MIcmd state vc
...................................................................................................................................................................................................
3 If the primary VM is not active then switch by using the following command:
MIcmd switch vc
MIcmd state vc
...................................................................................................................................................................................................
tool.
create_ht
> create_ht
data
Fri Apr 23 15:51:26 CDT 2010 Wrote new /var/opt/lib/sim/data/hosts.dat
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
su_health -a
...................................................................................................................................................................................................
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
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
cdr
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
cs
ss7
h248
vlr
ims
fsdb
fs5k
gls
gjs
gos
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
y
IPv6 subnet number 4, subnet prefix 2500:0:0:01f2:0:0:0:0, prefix
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
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
N) for no more: n
n
> hwgrow
cdr
cs
ss7
h248
vlr
ims
fsdb
fs5k
gls
gjs
gos
Enter the SERVICE TYPE for pair 1 HostID 0: fsdb
Are you using offsets for fsdb (y/n) ?n
y
Enter IPv4 SUBNET ID for 1 fsdb Service with NI-default (IP 0), enter
return for skip :1
N) for no more: 7
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
net4conf_adm: error: IPv4 external subnet 7 does not exist
No available IP on subnet 7 now, try other subnet
2
diam_sh,dns,fsdb_geosync
N) for no more: n
y
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
diam_sh,dns
N) for no more: n
> hwgrow
cdr
cs
ss7
h248
vlr
ims
fsdb
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
fs5k
gls
gjs
gos
Enter the SERVICE TYPE for pair 1 HostID 0: fsdb cdr
Are you using offsets for "fsdb cdr" (y/n) ?n
y
Enter IPv4 SUBNET ID for 1 fsdb Service with NI-default (IP 0), enter
return for skip :1
N) for no more: 2
diam_sh,dns,fsdb_geosync
N) for no more: n
y
Enter IPv6 address for pair 1 fsdb service: 2500:0:0:0202:0:0:0:12
diam_sh,dns
N) for no more: n
y
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
return for skip :1
N) for no more: 2
diam_rf,dns
N) for no more: n
y
return for skip :4
Enter IPv6 address for pair 1 cdr service: 2500:0:0:0202:0:0:0:13
N) for no more: 5
Enter IPv6 address for pair 1 cdr service: 2500:0:0:0203:0:0:0:13
diam_rf,dns
N) for no more: n
...................................................................................................................................................................................................

sim hwgrow start -x hwgrow.xml -d rules/hwgrow/hosts.dat
> sim hwgrow start -x hwgrow.xml -d rules/hwgrow/hosts.dat
**************************************************************
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
**************************************************************
SIM hwgrow start was successfully launched!
...................................................................................................................................................................................................

tail -f /var/opt/log/sim/hwgrow/sim.log
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.
Example of resume:
> sim hwgrow resume
**************************************************************
**************************************************************
[y/n] y
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Host: "Active"
# clia board <card#>
Physical Slot # 3
90: Entity: (0xa0, 0x60) Maximum FRU device ID: 0x03
PICMG Version 2.2
96: FRU # 2 (AMC # 5)
Entity: (0xc1, 0x65)
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#>
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
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
interfaces.ifTable.ifEntry.ifAdminStatus.9 = up(1)
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
**************************************************************
**************************************************************
[y/n] y
...................................................................................................................................................................................................
21 Growth is completed successfully when log file displays:

Result
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)
...................................................................................................................................................................................................
22 After the growth process is completed, execute the following command to update the
hosts.dat file:
create_ht
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
MI-GUI ” (p. 3-37).
...................................................................................................................................................................................................
25
GUI.
5420 CTS services
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To jumpstart diskful card
....................................................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To jumpstart diskful card
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To establish a processor card SOL session
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To grow service of diskless hosts for multiple services
....................................................................................................................................................................................................................................
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

During the process, you need to open two windows on the lead (active) MI to observe the
status of the growth procedure:
• The “Hardware and service growth of diskless hosts” procedure is executed first.
• 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)
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
– NI types assigned to a particular IP address
– Offset (if required)
Procedure
...................................................................................................................................................................................................
1 Open two windows and from both log in to MI-1 as root.

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

MIcmd state vc
...................................................................................................................................................................................................
MIcmd switch vc
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
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.
cs
ss7
h248
ims
fs5k
Enter the SERVICE TYPE for pair 1: ims
Are you using offsets for "ims" (y/n) ?n
y
Enter 1 SUBNET ID for 1 ims Service with NI-default (IP 0), enter
return for skip :1
N) for no more: 2
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
N) for no more: n
y
IPv6 subnet number 4, subnet prefix 2500:0:0:00b4:0:0:0:0, prefix
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
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
unassigned : pdf
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 ...
none

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.
...................................................................................................................................................................................................

sim svcgrow start -x svcgrow.xml -d rules/svcgrow/hosts.dat
> sim svcgrow start -x svcgrow.xml -d rules/svcgrow/hosts.dat
**************************************************************
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
**************************************************************
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 svcgrow start was successfully launched!
...................................................................................................................................................................................................

tail -f /var/opt/log/sim/svcgrow/sim.log
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.
...................................................................................................................................................................................................
10 Service Growth is completed successfully when log file displays:

Result
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 After the grow process is completed, execute the following command to update the SIM
host table.
create_ht
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
MI-GUI ” (p. 3-37).
...................................................................................................................................................................................................
14
GUI.
• 5450 IP Session Control Application User Guide for provisioning IMS and H.248
services
5420 CTS services
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To grow RTM with disk on an existing diskful host
....................................................................................................................................................................................................................................
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

• The following information required to grow an RTM with disk are kept ready:
For example:
– Shelf number
– Card number
Procedure
...................................................................................................................................................................................................
1 Open a window and log in to MI-1 host as root.

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

MIcmd state vc
> MIcmd state vc
...................................................................................................................................................................................................
MIcmd switch vc
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
MIcmd state vc
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................

su_health -a
...................................................................................................................................................................................................
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
...................................................................................................................................................................................................
...................................................................................................................................................................................................
MI-GUI ” (p. 3-37).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To determine the serial port configured in laptop
....................................................................................................................................................................................................................................
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
• A laptop
cable.
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.
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To determine the serial port configured in laptop
....................................................................................................................................................................................................................................
You will use this port in the sub-section.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To configure laptop for serial connection on Windows XP
....................................................................................................................................................................................................................................
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
• A laptop
cable.
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To configure laptop for serial connection on Windows XP
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware growth To establish serial port connection on the laptop
....................................................................................................................................................................................................................................
To establish serial port connection on the laptop

Overview
This procedure provides steps to establish serial port connection on the laptop.
Materials Required
• A laptop
cable.
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
....................................................................................................................................................................................................................................
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
...................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware de-growth Overview
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware de-growth De-growth implementation flow
....................................................................................................................................................................................................................................
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

...................................................................................................................................................................................................
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).
...................................................................................................................................................................................................
2 If you de-grow diskless/diskful hosts, use: “To de-grow hardware and service on
diskless/diskful hosts ” (p. 6-9).
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware de-growth To de-grow service of multiple services on diskless hosts
....................................................................................................................................................................................................................................
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.
• ATCA
• 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

status of the de-growth procedure:
• 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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
...................................................................................................................................................................................................
...................................................................................................................................................................................................

MIcmd state vc
...................................................................................................................................................................................................
MIcmd switch vc
MIcmd state vc
...................................................................................................................................................................................................
tool.
create_ht
> create_ht
data
Fri Apr 23 16:35:08 CDT 2010 Wrote new /var/opt/lib/sim/data/hosts.dat
hostdat.layout
Fri Apr 23 16:35:08 CDT 2010 Wrote new /var/opt/lib/sim/data/hostdat.ksh
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

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.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
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.
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
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
**************************************************************
**************************************************************
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 svcdegrow start was successfully launched!
...................................................................................................................................................................................................

tail -f /var/opt/log/sim/svcdegrow/sim.log
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
**************************************************************
**************************************************************
[y/n] y
*** Cannot resume from a previous SIM failure. ***
> sim svcdegrow start -x svcdegrow.xml -d rules/svcdegrow/hosts.dat
**************************************************************
**************************************************************
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
SIM svcdegrow start was successfully launched!
Note: During the execution of the de-growth procedures additional transient alarm
...................................................................................................................................................................................................
10 Service de-growth is completed successfully when log file displays:

Result
DE-GROWTH IS COMPLETE!!!!!
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 After the de-grow process is completed, execute the following command to update the
SIM host table.
create_ht
...................................................................................................................................................................................................
...................................................................................................................................................................................................
MI-GUI ” (p. 3-37).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - hardware de-growth To de-grow hardware and service on diskless/diskful hosts
....................................................................................................................................................................................................................................
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.
• ATCA
• ims
• fs5k
• h248
• ss7
The following diskful service is supported
• fsdb
• cdr
• vlr
• gos
• gjs
• gls
Before you begin

status of the de-growth procedure:
• 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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................

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
...................................................................................................................................................................................................
MIcmd switch vc
MIcmd state vc
...................................................................................................................................................................................................
tool.
create_ht
Result:
> create_ht
data
hosts.dat
hostdat.layout
hostdat.ksh
...................................................................................................................................................................................................

su_health -a
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
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.
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
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
...................................................................................................................................................................................................

sim hwdegrow start -x hwdegrow.xml -d rules/hwdegrow/hosts.dat
> sim hwdegrow start -x hwdegrow.xml -d rules/hwdegrow/hosts.dat
**************************************************************
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
**************************************************************
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 hwdegrow start was successfully launched!
...................................................................................................................................................................................................

tail -f /var/opt/log/sim/hwdegrow/sim.log
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:
When this occurs,
> sim hwdegrow resume
**************************************************************
**************************************************************
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
10 De-growth is completed successfully when log file displays:

Result
DE-GROWTH IS COMPLETE!!!!!
...................................................................................................................................................................................................
11 After the de-grow process is completed, execute the following command to update the
SIM host table.
create_ht
...................................................................................................................................................................................................
...................................................................................................................................................................................................
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.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
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
...................................................................................................................................................................................................................................
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

• The system is stable
• The following information needed to convert a pair of cards:
– Shelf number
– Card number
Procedure
...................................................................................................................................................................................................
1 Open two windows and from both windows, log in to MI-1 host as root.
...................................................................................................................................................................................................

MIcmd state vc
> MIcmd state vc
...................................................................................................................................................................................................
3 If the primary VM is not active, then switch by using the following command:
MIcmd switch vc
MIcmd state vc
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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
hostdat.layout
hostdat.ksh
...................................................................................................................................................................................................

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 ***
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
*** 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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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.
(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.
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
You are about to deactivate Shelf-Card: 00-02
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 02 R22.08.00 front local_disk
SIM fru start was successfully launched!
...................................................................................................................................................................................................

tail -f /var/opt/log/sim/fru/sim.log
error and resume the growth by typing sim fru resume.
...................................................................................................................................................................................................
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>
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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,
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
'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
Enter the Action [[d]eactivate or [a]ctivate]:a
SHELF number = 0
Enter the CARD number [ 2 ]: 2
CARD number = 2
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
**************************************************************
**************************************************************
Using rules file: /opt/LSS/share/sim/rules/fru/activate.xml
...................................................................................................................................................................................................
29 On the second active MI-1 window, execute the following command to tail the SIM log:
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
30 SIM will pause for jumpstart of Blade 2.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
32 Once jumpstart is completed successfully, execute the following command to resume:

sim fru resume
Example:
> sim fru resume
**************************************************************
**************************************************************
[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:

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:
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
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
services.
services.
services
**************************************************************
**************************************************************
...................................................................................................................................................................................................
41 Execute the following command to tail the SIM log:

....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
42 When SIM rules are done, wait until the blade is completely powered down.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
44 Replace the blade with a new Molene2 diskful blade.

...................................................................................................................................................................................................
45 Execute the following command to remove the old hardware from data:
Example:
...................................................................................................................................................................................................
46 Execute the following command to get the front and rear mnemonics of the new card:
Example:
FMO16JD;NONE
...................................................................................................................................................................................................

cardnum <card number> --frontmnemonic <front mnemonic> --
rearmnemonic <rear mnemonic>
Example:
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:

....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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
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')
...................................................................................................................................................................................................
52 Execute the following command to activate the new Molene2 card in Slot 1:
fru_cli
Example:
> fru_cli
SHELF number = 0
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
CARD number = 1
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
**************************************************************
**************************************************************
...................................................................................................................................................................................................
53 On the second active MI-2 window, execute the following command to tail the SIM log:
...................................................................................................................................................................................................
54 SIM will pause for jumpstart of Blade 1.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
56 Once the jumpstart is completed successfully, execute the following command to resume:
sim fru resume
Example:
> sim fru resume
**************************************************************
**************************************************************
[y/n] y
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
57 Wait until the SIM rules are completed successfully in the SIM log.
...................................................................................................................................................................................................
58 On MI-2, execute the following commands:

dhcpconf_adm --action control_host_all --command reload
tzconf_adm --action set_all
create_ht
...................................................................................................................................................................................................
59 On MI-1, Execute the following commands:

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
...................................................................................................................................................................................................
MI-GUI ” (p. 3-37).
GUI.
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
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.
• 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
...................................................................................................................................................................................................
3 If the second MI is active, switch to the active MI by executing the following command:
MIcmd switch vc
State Change.
.............................
MI virtual cluster switched over successfully
MIcmd state vc
...................................................................................................................................................................................................

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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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:
...................................................................................................................................................................................................
7 Deactivate hub 8 by executing the following command:

fru_cli
For example:
> fru_cli
Enter the location [ front|rear ]: front
Hub Card 00-08 deactivation SUCCESSFUL
...................................................................................................................................................................................................

...................................................................................................................................................................................................
9 Remove the old hardware from the data by executing the following command on the MI:
For example:
> hwconf_adm --action del_card_instance --shelfnum 0 --
cardnum 8
...................................................................................................................................................................................................
10 Replace it with a hub with no HSPP4.

....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
11 Get the front and rear mnemonics of the new card by executing the following command:
For example:
NBMASW1;NONE
...................................................................................................................................................................................................
12 Add the card information by executing the following command:

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:

...................................................................................................................................................................................................
15 Install System Configuration data by executing the following command:

...................................................................................................................................................................................................
16 Synchronize the database by executing the following command:

syncConfigDB -l
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)
host_id = 4)
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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')
...................................................................................................................................................................................................

create_ht
For example:
> create_ht
data
hosts.dat
hostdat.layout
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
SHELF number = 0
CARD number = 8
Please wait. Activation in progress ...
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
... 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...
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-s00c07h0: aquiring SSH keys... done
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
at071-s00c01h0: generating SSH daemon configuration... done
at071-s00c01h0: 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.
...................................................................................................................................................................................................

fru_cli
For example:
> fru_cli
...................................................................................................................................................................................................

...................................................................................................................................................................................................
21 Remove the old hardware from data by executing the following command on the MI:
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
For example:
hwconf_adm --action del_card_instance --shelfnum 0 --cardnum 8
...................................................................................................................................................................................................
22 Replace it with a hub with no HSPP4.

...................................................................................................................................................................................................
For example:
NBMASW1;NONE
...................................................................................................................................................................................................

rear mnemonic
For example:
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
...................................................................................................................................................................................................

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

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

syncConfigDB -l
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
For example:
> syncConfigDB -l
host_id = 0)
host_id = 4)
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')
...................................................................................................................................................................................................

create_ht
For example:
> create_ht
data
hosts.dat
hostdat.layout
hostdat.ksh
...................................................................................................................................................................................................
fru_cli
A root password is required for the blade. If prompted for a factory blade, enter alatcav2.
For example:
> fru_cli
SHELF number = 0
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
CARD number = 7
... Card is up.
..
..
..
..
..
...................................................................................................................................................................................................
31 Synchronize the meta data by executing the following command:

...................................................................................................................................................................................................
32 Allow MI switchover by executing the following command:

rccInhibit -a CLEAR MI-1hostname
...................................................................................................................................................................................................
33 On MI-2 execute the following commands:

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
....................................................................................................................................................................................................................................
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.
• 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
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................

create_ht
> create_ht
Wed Mar 24 14:08:45 CDT 2010 Saving backup files to /var/opt/lib/
sim/data
hosts.dat
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
hostdat.layout
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:
Example: rccInhibit -d at071-s00c01h0
...................................................................................................................................................................................................
7 Deactivate hub 8 by typing the command:

fru_cli
Example of fru_cli command:
fru_cli
You can use ^C (control-C) at any time to safely abort this
interactive script.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Example:
...................................................................................................................................................................................................
10 Replace it with a hub with HSPP4.

...................................................................................................................................................................................................
11 Get the front and rear mnemonics of the new card by typing the following command:
Example: getMnemonic -s 0 -c 8
FMA1AD;NONE
...................................................................................................................................................................................................

rear mnemonic
Example:
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
...................................................................................................................................................................................................

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

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

syncConfigDB -l
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Example:
> syncConfigDB -l
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')
Synchronization complete. Command completed successfully.
...................................................................................................................................................................................................

create_ht
Example:
> create_ht
data
hosts.dat
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
hostdat.layout
hostdat.ksh
...................................................................................................................................................................................................
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
You can use ^C (control-C) at any time to safely abort this
interactive script.
SHELF number = 0
CARD number = 8
... Card is up.
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...
..................................
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Sleeping 30 seconds while hub finishes booting...
Connecting 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.
syncing RADIUS badwords file... done
syncing RADIUS license file... done
syncing RADIUS key file... done
... SSH configuration updated successfully.
... All Services are active.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

fru_cli
For example:
> fru_cli
...................................................................................................................................................................................................

...................................................................................................................................................................................................
For example:
> hwconf_adm --action del_card_instance --shelfnum 0 --
cardnum 7
...................................................................................................................................................................................................
22 Replace it with a hub with HSPP4.

...................................................................................................................................................................................................
For example:
Result:
FMA1AD;NONE
...................................................................................................................................................................................................

rear mnemonic
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
For example:
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
...................................................................................................................................................................................................

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

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

syncConfigDB -l
For example:
> syncConfigDB -l
host_id = 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')
7, 4, -1, '000A474074000000000000000000000000000000', 'at071-
s00c07h4', 0, -1, 1, 'R22.08.00', 1, 'eth0.800:0',
'000A472074000000000000000000000000000000', 'eth1.801:0',
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
'000A473074000000000000000000000000000000', 'eth0.800:1',
'eth1.801:1', '0000000000000000000000000000000000000000',
'0000000000000000000000000000000000000000', 'node', 'FMA1AD')
...................................................................................................................................................................................................

create_ht
For example:
> create_ht
data
hosts.dat
hostdat.layout
hostdat.ksh
...................................................................................................................................................................................................
fru_cli
Note: A root password for the blade is required. If prompted for factory blade, enter
alatcav2.
For example:
> fru_cli
SHELF number = 0
CARD number = 7
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
... Card is up.
..
..
..
..
..
...................................................................................................................................................................................................
31 Synchronize the meta data by executing the following command:

...................................................................................................................................................................................................
32 Allow MI switchover by executing the following command:

rccInhibit -a CLEAR MI-1hostname
...................................................................................................................................................................................................
33 On MI-2 execute the following commands:

create_ht
...................................................................................................................................................................................................
34 Plug in the 10G cross connect cable between the two hubs into UPLF/UPL0 ports.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
Platform hardware conversion To convert Disk Schema
....................................................................................................................................................................................................................................
To convert Disk Schema

Prerequisites
Ensure the following:
• Stable system.
• 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
...................................................................................................................................................................................................
3 If the second MI is active, switch to the active MI by executing the following command:
MIcmd switch vc
State Change.
.............................
MI virtual cluster switched over successfully
MIcmd state vc
...................................................................................................................................................................................................
4 Back up all the files required from the disk being converted.
...................................................................................................................................................................................................

create_ht
> create_ht
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
VM list: fsdb
Warning: You are about to deactivate a card that has ACTIVE services.
services.
services
...................................................................................................................................................................................................
8 Execute the following command on the second active MI-1 window and to tail the SIM
log:
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
Host: "Active"
# clia board <card#>
For example:
# clia board 5
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
Executing command: hwconf_adm --action generate_host_all
at001-s00c01h0: 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
Executing command: hwconf_adm --action install_host_instance --
shelfnum 0 --cardnum 2 --hostnum 0
...................................................................................................................................................................................................
11 Execute the following command to power on the blade:

resetCard -s <shelf> -c <slot> -v poweron
For example:
...................................................................................................................................................................................................
12 Execute the following command to activate the new card:

fru_cli
For example:
> fru_cli
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
SHELF number = 0
CARD number = 4
...................................................................................................................................................................................................
13 Execute the following command on the second active MI-1 window and tail the 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
Continue? [y/n] y
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Executing command: svcconf_adm --action install_host_all
Executing command: hwconf_adm --action install_host_all
Executing command: tzconf_adm --action set_all
at001-s00c01h0: setting timezone... done
Executing command: scdm_adm --action sync_config
Executing command: create_ht
data
hosts.dat
hostdat.layout
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
data
hosts.dat
hostdat.layout
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
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
VM list: fsdb
services.
services.
services
...................................................................................................................................................................................................
19 Execute the following command to tail the SIM log:

....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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:
...................................................................................................................................................................................................
22 Execute the following command to activate the new card in slot above:
fru_cli
For example:
> fru_cli
SHELF number = 0
CARD number = 1
...................................................................................................................................................................................................
23 Execute the following command on the second active MI-2 window and tail the 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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
For example:
> sim fru resume
Continue? [y/n] y
...................................................................................................................................................................................................
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
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2011
8 8 anage system
M
configuration - IP
configuration
Overview
Purpose
This chapter describes the IP addresses and addressing schemes that are used by the 5400
Linux CP.
Contents
Internal IP addresses and subnets 8-3

Internal IP subnetworks 8-4
Hardware-related subnetworks and IP addressing 8-7
Service-related subnetwork and IP addressing 8-15
DNS and ENUM in the 5400 Linux CP 8-17
Domain Name System (DNS) 8-18
To add a 5400 Linux CP DNS domain or server 8-24
5400 Linux CP DNS administration 8-26
Telephone Numbering Mapping (ENUM) 8-28
To add a 5400 Linux CP ENUM remote or local server 8-30
To add or delete 5400 Linux CP ENUM domain and server 8-32
To verify 5400 Linux CP DNS local query 8-34
To check the status of 5400 Linux CP DNS processes 8-36
IP address and route configuration 8-37
To add a new external IPv4 subnet 8-38
To delete an external IPv4 subnet 8-40
...................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration Overview
....................................................................................................................................................................................................................................
To add a new external fixed IPv4 address 8-46

To delete an external fixed IPv4 address 8-48
To add a new external floating IPv4 address 8-50
To delete an external floating IPv4 address 8-52
To add or delete static routes for a service 8-62
To modify the IP addresses of a Network Interface 8-67
To modify the Default Gateway data for a service 8-71
To set port speeds of hub-based transport interfaces 8-75
NTP servers and time zone 8-76
To add or delete remote NTP servers IP addresses 8-77
To change the time zone 8-79
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Overview
Purpose
This section provides information about the internal IP addresses and subnets that are
used for the 5400 Linux CP.
Contents
Internal IP subnetworks 8-4

Hardware-related subnetworks and IP addressing 8-7
Service-related subnetwork and IP addressing 8-15
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration Internal IP subnetworks
....................................................................................................................................................................................................................................
Internal IP subnetworks
Internal subnetworks
Within the 5400 Linux CP six internal IP subnetworks (sub nets) are used to route internal
IP messages between the different cards and processes that are running on these cards.
The subnetworks used can be divided into:
• Five hardware-related subnetworks
• One service-related subnetwork.
More IP addresses per component

In order to better understand the functions and necessity of the different subnetwork
types, it is useful to know that within a 5400 Linux CP cabinet each component:
• Can have multiple IP addresses at the same time
• The IP addresses can belong to different subnetworks.
Virtual Local Area Networks (VLANs)

There are different VLANs defined for different purposes. Therefore, each Host will
have:
• Untagged interfaces for the use of DHCP
• Tagged interfaces for use of Internal Subnets (Internal Service and Host Active
subnets in the 800 series of VLAN tags)
• Differently tagged interfaces for use of External Subnets (External Service subnets in
the 400 and/or 600 series of VLAN tags)
For the untagged and internal VLANs, the Left Hub broadcast areas and the Right Hub
broadcast areas DO NOT INTERCONNECT. That means a Broadcast from an untagged or
internally tagged interface on eth0 will not be seen by any eth1 interface of any host
(exceptions are of the Hosts on the Hubs and ShMCs) irrespective of the number of
shelves in the configuration.
The following table lists all of the VLANs defined on the Hubs:
Range Category Use Block Left Hub Right Hub
300 Platform
Untagged (e.g., for DHCP) 300 300 301

400 Transport - Hub
Front Panel
Transport F-0 - GE0 400 400 401

Transport F-1 - GE1 410 410 411
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Range Category Use Block Left Hub Right Hub
Transport F-2 - Used for alarm 420 420 421

panel
Transport F-3 - GE3 430 430 431
600 Transport - Hub

RTM
Transport R-0 - GE0 600 600 601
Transport R-1 - GE1 610 610 611

Transport R-2 - GE2 620 620 621
Transport R-3 - GE3 630 630 631

Transport R-4 - GE4 640 640 641
Transport R-5 - GE5 650 650 651

Transport R-6 - GE6 660 660 661
Transport R-7 - GE7 670 670 671
800 Internal by
Tenant
Tenant 0 800 800 801

Tenant 1 810 810 811
Tenant 2 820 820 821
Tenant 3 830 830 831
Tenant 4 840 840 841
Tenant 5 850 850 851
Tenant 6 860 860 861
Tenant 7 870 870 871

Tenant 8 880 880 881
Tenant 9 890 890 891
Note: Different VLANs are used for different purposes:

• VLAN 300 is used for DHCP requests and responses in the Left Hubs
• VLAN 301 is used for DHCP requests and responses in the Right Hubs
• VLANs 400/401 is used in the Left/Right Hubs for External Subnet IP Addresses
accessed from the customer network over the Hub front panel connections in port
FP GE0.
accessed from the customer network over Hub front panel connections in port FP
GE1
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
GE2
GE3
• VLANs in the 600 range is used for the Rear Transition Module (RTM) in the
same fashion as the 400 range VLANs
• VLAN 800/801 is used in the Left/Right Hubs for all IP addresses that stay on the
ATCA shelf. Neither of these VLANs is configured on any port of the Hub
connected to the customer network.
• Other VLANs in the 800 range will be configured on the Hubs for use by other
Applications, however 5400 Linux CP will not use them on their Hosts.
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration Hardware-related subnetworks and IP addressing
....................................................................................................................................................................................................................................
Hardware-related subnetworks and IP addressing

Internal hardware subnetworks types
The internal hardware-related subnetworks can be divided into the following different
subnetwork types:
• Host Subnet
• DHCP0 Subnet
• DHCP1 Subnet
• LSN0 Subnet
• LSN1 Subnet
Host Subnet
The Host subnet is used to communicate with Host IP addresses of other hosts. Each host,
including the Hub and ShMC host is associated with a Host IP address and tagged
interfaces in VLANs(eth0.800 and eth1.801). The host IP address exist on both backplane
interfaces in the tagged VLANs.
Note: The host subnet assigns each Host a specific IP address based on the Shelf
number, Slot Number, and Host Number. Host Subnet is also known as Host Active
Subnet. The Hub cards have the host active addresses only on ONE interface, whereas
in Node cards host active addresses are on both interfaces. The Host Active address on
Hub 7 is in VLAN 800 while on Hub 8, it is in VLAN 801. The interface to VLAN
correlation is opposite between Hub 7 and Hub 8.
DHCP0 Subnet
The DHCP0 subnet is used for DHCP requests and responses in the untagged VLAN 300
which spans the Left Hubs, and does not go out to the customer network.
A booting diskless host or a jumpstarted diskful host would send a DHCP request
broadcast. This broadcast would be untagged and hence interpreted by the switch to be in
VLAN 300. The DHCP server (the OAM Server) would respond to this request if
configured to respond to the hardware MAC address of the requesting host. It would give
the requesting device, among other things, an IP address in the DHCP0 subnet for its eth0
interface. A host will first attempt a DHCP request on its eth0 interface. If no response is
received, a request is attempted on its eth1 interface.
DHCP1 Subnet
The DHCP1 subnet is used for DHCP requests and responses in the untagged VLAN
301which spans the Right Hubs, and does not go out to the customer network.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
A booting diskless host or a jumpstarted diskful host would send a DHCP request
broadcast in VLAN 301. The DHCP server (the OAM Server) would respond to this
request if configured to respond to the hardware MAC address of the requesting host. It
would give the requesting device, among other things, an IP address in the DHCP1 subnet
for its eth1 interface.
LSN0 Subnet
The LSN0 subnet is used for communicating with other LSN0 IP addresses. The path of
any packets using LSN0 IP addresses will only traverse the Left Hub Switches.
The LSN0 subnet is associated with eth0 for all Hosts and tagged interfaces in VLAN 800
on the Left Hubs. The only exceptions are the slot 8 (Right Hub Host) and the Bottom
ShMC, on which the eth1 interface has a presence in VLAN 800.
Note: All hosts have the same interface/vlan correlation (LSN0 on eth0 vlan 800 and
LSN1 on eth1 vlan 801) EXCEPT for the hub in slot 8 (the right hub) and the bottom
ShMC. These two hosts have the interfaces flipped with respect to the other hosts in
the system. The LSN0 IP is on the eth1.800 interface and the LSN1 IP is on the
eth0.801 interface.
LSN1 Subnet
The LSN1 subnet is used for communicating with other LSN1 IP addresses. The path of
any packets using LSN1 IP addresses will only traverse the Right Hub Switches.
The LSN1 subnet is associated with eth1 for all Hosts and tagged interfaces in VLAN 801
on the Right Hubs. The only exceptions are the slot 8 (Right Hub Host) and the Bottom
ShMC, on which the eth0 interface has a presence in VLAN 801. These two hosts have
the interfaces flipped with respect to the other hosts in the system.
IP addressing and naming

This table lists the IP addressing and naming convention that is used within the 5400
Linux CP:
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Slot/ Card Type of RCC active interface IP address Example IP address for shelf
card name 0
01 Node -eth0 Left N/A x.y.(0+s).(c×16+h) 169.254.0.16

(DHCP0)
Node -eth1 Right N/A x.y.(16+s).(c×16+h) 169.254.16.16

(DHCP1)
Node Left AXXXX-s<nn>c01h0-1 x.y.(32+s).(c×16+h) 169.254.32.16
-eth0.800
(LSN0)
Node Right AXXXX-s<nn>c01h0-r x.y.(48+s).(c×16+h) 169.254.48.16

-eth0.801
(LSN1)
Node Left N/A x.y.(64+s).(c×16+h) 169.254.64.16

(Host)
Node Right N/A x.y.(64+s).(c×16+h) 169.254.64.16
(Host)
(DHCP0)

(DHCP1)
-eth0.800
(LSN0)

-eth0.801
(LSN1)
(Host)
(Host)
(DHCP0)
(DHCP1)
-eth0.800
(LSN0)

-eth0.801
(LSN1)

(Host)

(Host)
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
card name 0

(DHCP0)

(DHCP1)
-eth0.800
(LSN0)
-eth0.801
(LSN1)

(Host)

(Host)
(DHCP0)
(DHCP1)

-eth0.800
(LSN0)
-eth0.801
(LSN1)
(Host)
(Host)
(DHCP0)

(DHCP1)

-eth0.800
(LSN0)

-eth0.801
(LSN1)

(Host)
(Host)
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
card name 0
07 Hub -eth0 Left N/A x.y.(0+s).(c×16+h) 169.254.0.112

(DHCP0)
Hub -eth1 Right N/A x.y.(16+s).(c×16+h) 169.254.16.112

(DHCP1)
Hub Left N/A x.y.(32+s).(c×16+h) 169.254.32.112
-eth0.800
(LSN0)
Hub Right N/A x.y.(48+s).(c×16+h) 169.254.48.112
-eth1.801
(LSN1)
Hub (Host) Left N/A x.y.(64+s).(c×16+h) 169.254.64.112

08 Hub -eth0 Left N/A x.y.(16+s).(c×16+h) 169.254.16.128
(DHCP1)
Hub -eth1 Right N/A x.y.(0+s).(c×16+h) 169.254.0.128
(DHCP0)
Hub Left N/A x.y.(48+s).(c×16+h) 169.254.48.128

-eth0.801
(LSN1)
Hub Right N/A x.y.(32+s).(c×16+h) 169.254.32.128

-eth1.800
(LSN0)
Hub (Host) Right N/A x.y.(64+s).(c×16+h) 169.254.64.128
(DHCP0)
(DHCP1)
-eth0.800
(LSN0)
-eth0.801
(LSN1)

(Host)
(Host)
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
card name 0

(DHCP0)

(DHCP1)
-eth0.800
(LSN0)
-eth0.801
(LSN1)

(Host)

(Host)
(DHCP0)
(DHCP1)

-eth0.800
(LSN0)
-eth0.801
(LSN1)
(Host)
(Host)
(DHCP0)

(DHCP1)

-eth0.800
(LSN0)

-eth0.801
(LSN1)

(Host)
(Host)
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
card name 0

(DHCP0)

(DHCP1)
-eth0.800
(LSN0)
-eth0.801
(LSN1)

(Host)

(Host)
(DHCP0)
(DHCP1)

-eth0.800
(LSN0)
-eth0.801
(LSN1)
(Host)
(Host)
15 ShMC1 - Virtual N/A x.y.(64+s).(c×16+h) 169.254.64.240
eth0:rmcp
ShMC1 - Upper N/A x.y.(32+s).(c×16+h) 169.254.32.241

eth0
ShMC2 - Bottom N/A x.y.(48+s).(c×16+h) 169.254.48.242

eth0
ShMC1 - Upper N/A x.y.(48+s).(c×16+h) 169.254.48.241
eth1
ShMC2 - Bottom N/A x.y.(32+s).(c×16+h) 169.254.32.242
eth1
Notes:
1. <nn> = Shelf number in the RCC active interface name column
2. c = Card/Slot number in the RCC active interface name column.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
3. s = Shelf Number in IP address column
4. c = Slot/Card number in IP address column
5. h = Host number in the IP address column. h = 0 for every card except ShMC. For ShMC, h = 0 for the
virtual IP; h = 1 for the upper card; h = 2 for the lower card.
6. AXXXX = The Switch or customer site prefix (where A must be an alphabetic (a-z) and XXXX must be an
alphanumeric (a-z, 1-9)).
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration Service-related subnetwork and IP addressing
....................................................................................................................................................................................................................................
Service-related subnetwork and IP addressing

Internal service subnetwork
An internal service subnetwork is a range of private IP addresses, that can be assigned to
services running on Processor cards.
Service subnetwork types

The service-related subnetwork can be divided into the following different IP address
ranges:
• Internal fixed IP addresses
An internal fixed service IP Address is an IP address that remains associated with a
particular instance of a service, regardless of whether that instance is active or
standby.
• Internal floating IP addresses.
An internal floating service IP Address is an IP Address that is moved (floated) to an
instance of a service that is currently in the active state.
Subnetwork IP address ranges

The table lists service subnetwork conventions that are used:
IP address range Network mask

169.254.128 - 169.254.191 255.255.128.0
169.254.192 - 169.254.255
Service-related subnetwork mapping

This table lists the service subnetwork conventions that are used for each of the 5400
Linux CP services:
# Service1 Service Name Internal Fixed IP2 Internal Floating IP2
2 Config server cnfg 169.254.130.0 169.254.194.0

3 MI-GUI mi 169.254.131.0 169.254.195.0
4 CDR server cdr 169.254.132.0 169.254.196.0
11 H.248 DS h248 169.254.139.0 169.254.203.0

26 IMS ims 169.254.154.0 169.254.218.0
27 Feature Server Database fsdb 169.254.155.0 169.254.219.0
28 5420 CTS fs5k 169.254.156.0 169.254.220.0
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration Service-related subnetwork and IP addressing
....................................................................................................................................................................................................................................
Notes:
1. Depending on the solution for which the platform is configured, different services may be available.
2. The fourth octet with the value 0 denotes the first IP of that service type and fixed/float type. For example,
H.248 Device Servers each have their own internal fixed service addresses. The first one would be
169.254.139.0, but the second of the first mated pair of call servers would be 169.254.139.1. The first of the
second mated pair of call servers would be 169.254.139.2, and the second of the second would be
169.254.139.3. and so on.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Overview
Purpose
This section describes the task and the characteristics of the DNS that is running
internally on the 5400 Linux CP.
Contents
Domain Name System (DNS) 8-18

To add a 5400 Linux CP DNS domain or server 8-24
5400 Linux CP DNS administration 8-26
Telephone Numbering Mapping (ENUM) 8-28
To add a 5400 Linux CP ENUM remote or local server 8-30
To add or delete 5400 Linux CP ENUM domain and server 8-32
To verify 5400 Linux CP DNS local query 8-34
To check the status of 5400 Linux CP DNS processes 8-36
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration Domain Name System (DNS)
....................................................................................................................................................................................................................................
Domain Name System (DNS)

Introduction
The Domain Name System (DNS) translates Fully-Qualified Domain Names (FQDN) to
IP addresses and translates IP addresses to FQDN. A FQDN is a meaningful and
easy-to-remember “handle” for an IP address. DNS is primarily based on RFC 1034 and
RFC 1035, but there are other DNS RFCs.
DNS is arranged in a hierarchy. If one DNS server does not know how to translate a
particular domain name, it asks another server and so on, until the correct IP address is
returned.
Telephone Number Mapping (ENUM)

Telephone Numbering Mapping (ENUM) uses Dynamic Delegation Discovery System
(DDDS) and DNS to unify telephone numbers with the Internet. It stores E.164 telephone
numbers and translates them to IP addresses. For more information refer the “Telephone
Numbering Mapping (ENUM)” (p. 8-28) section.
5400 Linux CP DNS processes

The 5400 Linux CP DNS has the following processes:
PowerDNS
PowerDNS is an authoritative server. In an 5400 Linux CP system it is configured in a
multi-master setup with a dedicated instance of a MySQL DB as replicating storage
backend. Dynamic updates are done directly in the MySQL DB, both for zones as well as
for zone entries.
Unbound
Unbound is a caching, recursive resolver with a rich set of parameters for IP, cache and
ACL configuration. In a 5400 Linux CP system it is configured on hosts with services that
need to resolve DNS queries to forward queries for remote entities to remote
DNS/ENUM servers and to forward queries for 5400 Linux CP entities to the sns service
on the 5400 Linux CP system.
Note: As the control type of SNS is none, the SNS status appears on the MI GUI as
follows: X731 state and status not supported.
dnsproxy
dnsproxy is an ACL based DNS query forwarder. In an 5400 Linux CP system the ACLs
are configured such that DNS queries originating from friendly sources outside the 5400
Linux CP system are forwarded to the resolver and DNS queries originating from
non-friendly sources outside the 5400 Linux CP system are forwarded to the authoritative
server.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
5400 Linux CP DNS infrastructure
The 5400 Linux CP DNS infrastructure overview is illustrated below:
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
The 5400 Linux CP DNS server infrastructure with Internally Triggered Query is
illustrated below:
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
The 5400 Linux CP DNS infrastructure with Dynamic update and Externally Triggered
Query is illustrated below:
5400 Linux CP DNS server

The 5400 Linux CP DNS server is based on PowerDNS and MySQL. The DNS server is
provided by the Shared Network Services (SNS) and is configured on each OAM server,
together with the MI-GUI and Config server services.
5400 Linux CP DNS client

The 5400 Linux CP DNS client uses the Unbound resolver and each service that requires
DNS resolution runs this resolver.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
External DNS functionality provided by 5400 Linux CP
The 5400 Linux CP can be configured with one or more remote DNS servers and one or
more remote ENUM servers.
• The servers in each set must be able to resolve the same queries
• The same servers can be configured to provide both DNS and ENUM
• 5400 Linux CP provides two external fixed IP addresses to communicate with the
customer’s DNS/ENUM servers.
Note: The customer is responsible for the redundancy of the customer DNS servers.
DNS naming
Customer DNS is always the Master Domain. 5400 Linux CP DNS is always the
sub-domain.
Note: The Master domain name must be higher in the naming hierarchy than the
sub-domain name.
DNS naming convention
1. Configure external DNS to forward to the 5400 Linux CP local zone domain. SNS
will use external fixed IP address to communicate with the external DNS.
2. Forward the query from the external DNS to SNS using the SNS external fixed IP
address.
3. Declare the external DNS as the name server.
For example:
• Y = ims.example.com
• X = lcp1
• X.Y = lcp1.ims.example.com
Where:
• Y = Master domain of External DNS Server
• X.Y = 5400 Linux CP Local Zone Domain
4. Define a zone data file of zone X and point to the name server.
Note: 5400 Linux CP security:
• The 5400 Linux CP never accepts zone transfers.
• The 5400 Linux CP only accepts queries from known external servers.
Example of good naming:
Master domain – ims.example.com
5400 Linux CP Site 1 sub-domain – lcp1.ims.example.com
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Example of bad naming:
Master Domain – ims.example.com
5400 Linux CP Site 2 sub-domain – lcp2.ca.ims.example.com
In this example, ca has not been defined for the 5400 Linux CP Site 2 sub-domain.
Note: All names should be at the same level or the missing level must be defined.
Dynamic DNS update

The steps for any updates to the DNS server:
1. DNS parameters (SIPia port management) are updated via the Provisioning GUI
2. DNS parameters are dynamically updated on the DNS server residing within the MI
3. The MI DNS dynamically updates the MySQL database.
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To add a 5400 Linux CP DNS domain or server
....................................................................................................................................................................................................................................
To add a 5400 Linux CP DNS domain or server

Purpose
Use this procedure to add a 5400 Linux CP DNS remote domain or server.
Before you begin

Required configuration
Command Line (CLI) access must be established to the MI-GUI.
System requirements
Users must be logged on as root.
Prerequisites:
• For adding or deleting remote domain - a list of server IPs, a list of domain names.
• For adding or deleting remote server - a list of server IPs.
Procedure
...................................................................................................................................................................................................
1 Login to the Active MI as root.

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

dns_adm -a add_remote_domain -i <IP list> -d <domainname list>
The valid actions are:
• add_remote_domain
• del_remote_domain
• add_remote_server
• del_remote_server
Please note that when it runs into failure, the procedure will backout automatically.
When it completes successfully, it will print out the messages:
'dns_adm add_remote_server SUCCESSFUL. AFTER TESTING, RUN "dns_
adm -a commit". OR YOU CAN BACKOUT VIA dns_adm -a backout.'
...................................................................................................................................................................................................
3 To commit the procedure, execute the following command:

dns_adm -a commit
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To add a 5400 Linux CP DNS domain or server
....................................................................................................................................................................................................................................
Backout procedure:
If you want to backout before commit, execute the following command:
dns_adm -a backout
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration 5400 Linux CP DNS administration
....................................................................................................................................................................................................................................
5400 Linux CP DNS administration

Purpose
Use this procedure to administer the 5400 Linux CP DNS.
Before you begin

System requirements
Prerequisites:
For administering the DNS, we need the following:
• List of server IPs
• List of domain names.
Procedure
...................................................................................................................................................................................................

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

dns_adm -a <action> -i <IP list> [-d <domainname list>] [-c] [-t]
dns_adm -a add_solution_dns [-c] [-S <solution>] [-L <local zone>
] [-s <base,mask>] [-e <subnm,entnm,ip>]
...................................................................................................................................................................................................
3 To check the status, execute the following command:

dns_adm -a show_status [-k <status type>]
...................................................................................................................................................................................................
4 To set the log level, execute the following command:

dns_adm -a set_log_level -l <level>
...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration 5400 Linux CP DNS administration
....................................................................................................................................................................................................................................
dns_adm -a commit
Backout procedure:
dns_adm -a backout
E...................................................................................................................................................................................................
N D O F S T E P S
The actions for -a <action> can be the following:

• del_remote_domain
• show_status
• set_log_level
The backout command is used to backout the procedure.
The commit command is used to commit the procedure.
The [-d] denotes the domain name that needs to be added, deleted or changed. If the
domain names is a list, then separate them with commas.
The -i denotes the DNS server IPs that need to be added or deleted. If the IPs is a list,
then separate them with commas.
The [-k] denotes the specified status types. The status types can be the following:
• remote_domain
• remote_server
• mysql
• solution_dns
The -l denotes the log level.
The [-c] denotes clean start (remove lock file).
The [-h] is used to print help information.
The [-t] is used to test if the DNS server IP that needs to be added can be pinged.
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration Telephone Numbering Mapping (ENUM)
....................................................................................................................................................................................................................................
Telephone Numbering Mapping (ENUM)

Introduction
Telephone Numbering Mapping (ENUM) uses Dynamic Delegation Discovery System
(DDDS) and DNS to unify telephone numbers with the Internet. It stores E.164 telephone
numbers and translates them to IP Addresses. ENUM is based on RFC 3761 Architecture
is the same as DNS, but used differently.
Definition
ENUM Telephone Numbering Mapping (ENUM) is a standard adopted by the IETF that
uses the Domain Name System (DNS) to map telephone numbers to Web addresses or
Uniform Resource Identifiers (URIs). The goal of the ENUM standard is to provide a
single number to replace the multiple numbers and addresses for an individual's home
phone, business phone, fax, cell phone, and e-mail.
E.164 ITU-T Recommendation E.164 describes the international public
telecommunication numbering plan. Recommendation E.164.1 describes the
procedures and criteria for the reservation, assignment, and reclamation of E.164
country codes and associated Identification Code (IC) assignments. The criteria and
procedures are provided as a basis for the effective and efficient utilization of the
available E.164 numbering resources.
E.164 to DNS name conversion

The E.164 number must be converted before ENUM can issue a DNS query. To find the
DNS names for a specific E.164 number, the following steps should be followed:
1. See that the E.164 number is written in its full form, including the country code.
Example: +46-8-9761234
2. Remove all non-digit characters.
Example: 4689761234
3. Put dots (“.”) between each digit.
Example: 4.6.8.9.7.6.1.2.3.4
4. Reverse the order of the digits.
Example: 4.3.2.1.6.7.9.8.6.4
5. Append a dot, followed by the default ENUM domain name to the end.
Example: 4.3.2.1.6.7.9.8.6.4.e164.arpa
The reason that the number has to be reversed is because DNS names are structured from
right to left. In this example, DNS would first search for the top-level domain “arpa”, then
search “e164”, then the country code “46”, and so on. The dots are used to separate the
number into administrative zones (domains).
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration Telephone Numbering Mapping (ENUM)
....................................................................................................................................................................................................................................
DNS/ENUM Query
The DNS/ENUM server is used to determine if the called number is assigned to a packet
network subscriber or if the called number is assigned to a PSTN subscriber.
The S-CSCF generates an ENUM query if the Request URI in an INVITE messages
contains an E.164 number If the called number is assigned to a packet network subscriber,
the response from the DNS/ENUM server will contain a SIP URI. The S-CSCF copies
this SIP URI into the Request URI of the INVITE and forwards the INVITE to the host
name in this URI. If the called number is assigned to a PSTN subscriber, then the ENUM
server will not return a SIP URI. The S-CSCF will forward the INVITE to the BGCF.
References
For more information:
• RFC 2915
• RFC 2916
• RFC 3401
• RFC 3761.
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To add a 5400 Linux CP ENUM remote or local server
....................................................................................................................................................................................................................................
To add a 5400 Linux CP ENUM remote or local server

Purpose
Use this procedure to add 5400 Linux CP ENUM remote or local server
Before you begin

System requirements
Prerequisites:
• a list of server IPs
Procedure
...................................................................................................................................................................................................

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

enum_adm -a add_remote_server -i <IP list>
The valid actions are:
• add_local_server (for pure 5420 CTSceglar only)
• del_local_server (for pure 5420 CTSceglar only)
Note: The procedure will backout automatically when it runs into failure.
enum_adm add_remote_server SUCCESSFUL. AFTER TESTING, RUN "enum_
adm -a commit". OR YOU CAN BACKOUT VIA enum_adm -a backout.
...................................................................................................................................................................................................

enum_adm -a commit
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To add a 5400 Linux CP ENUM remote or local server
....................................................................................................................................................................................................................................
Backout procedure:
enum_adm -a backout
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To add or delete 5400 Linux CP ENUM domain and server
....................................................................................................................................................................................................................................
To add or delete 5400 Linux CP ENUM domain and server

Purpose
Use this procedure to add or delete a 5400 Linux CP ENUM domain and server.
Before you begin

System requirements
Prerequisites:
For adding or deleting an ENUM domain and server, we need the following:
• List of server IPs
• List of domain names.
Procedure
...................................................................................................................................................................................................

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

enum_adm -a <action> [-n <domain name>] -i <IP list> [-c] [-t]
...................................................................................................................................................................................................
3 To check the status, execute the following command:

enum_adm -a show_status [-k <status type>]
...................................................................................................................................................................................................
4 To set the log level, execute the following command:

enum_adm -a set_log_level -l <level>]
...................................................................................................................................................................................................
5 To backout or commit the procedure, execute the following command:
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To add or delete 5400 Linux CP ENUM domain and server
....................................................................................................................................................................................................................................
enum_adm -a backout | commit
E...................................................................................................................................................................................................
N D O F S T E P S
The actions for -a <action> can be the following:

• add_local_server
• del_local_server
• show_status
• set_log_level
The backout command is used to backout the procedure.
The commit command is used to commit the procedure.
The -i denotes the ENUM server IPs to be added or deleted. If the IPs is a list, then
separate them with commas.
The [-k] denotes the specified status types. The status types can be the following:
• remote_domain
• remote_server
• local_server
• mysql
The -l denotes the log level.
The [-c] denotes clean start (remove lock file).
The [-h] is used to print help information.
The [-t] is used to test if the ENUM server IP that needs to be added can be pinged.
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To verify 5400 Linux CP DNS local query
....................................................................................................................................................................................................................................
To verify 5400 Linux CP DNS local query

Purpose
Use this procedure to verify 5400 Linux CP DNS local query.
Procedure
...................................................................................................................................................................................................

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

dig -p 53001 @<internal fixed of SNS service> pisf-stdn<LCP
Local Zone Domain>
E...................................................................................................................................................................................................
N D O F S T E P S
Example of a successful local query

Use the following command to test 5400 Linux CP query:
dig -p 53001 @10.216.188.0 ln016-mi-p00f000-
g1.ln016.lucentlab.com
Output:
; <<>> DiG 9.3.4 <<>> -p 53001 @10.216.188.0 ln016-mi-p00f000-
g1.ln016.lucentlab.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31122 ;;
flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION: ;ln016-mi-p00f000-g1.ln016.lucentlab.com.
IN A
;; ANSWER SECTION:
ln016-mi-p00f000-g1.ln016.lucentlab.com. 60 IN A 135.1.48.225
;; Query time: 2 msec
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To verify 5400 Linux CP DNS local query
....................................................................................................................................................................................................................................
;; SERVER: 10.216.188.0#53001(10.216.188.0) ;; WHEN: Thu Dec 4
14:24:08 2008 ;; MSG SIZE rcvd: 73
Example of a unsuccessful local query

Here is an example of a unsuccessful local query:
dig -p 53001 @10.61.188.0 dtas-stdn1.fsimsgroup0-
000.at061.lucentlab.com
Output:
; <<>> DiG 9.3.4 <<>> -p 53001 @10.61.188.0 dtas-
stdn1.fsimsgroup0-000.at061.lucentlab.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3020 ;;
flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;dtas-stdn1.fsimsgroup0-000.at061.lucentlab.com. IN A
;; AUTHORITY SECTION:
at061.lucentlab.com. 60 IN SOA
at061.lucentlab.com.
root.at061.lucentlab.com. 1 15 5 1 15
;; Query time: 2 msec
;; SERVER: 10.61.188.0#53001(10.61.188.0) ;; WHEN: Mon Dec 8 08:
42:46 2008 ;; MSG SIZE rcvd: 105
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To check the status of 5400 Linux CP DNS processes
....................................................................................................................................................................................................................................
To check the status of 5400 Linux CP DNS processes

Purpose
Use this procedure to check the status of 5400 Linux CP DNS processes.
Procedure
...................................................................................................................................................................................................

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

dns_adm -a show_status
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Overview
Purpose
This section provides the procedures necessary to modify the IP address, default gateway
or add a static route.
Contents

To add or delete static routes for a service 8-62
To modify the IP addresses of a Network Interface 8-67
To modify the Default Gateway data for a service 8-71
To set port speeds of hub-based transport interfaces 8-75
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To add a new external IPv4 subnet
....................................................................................................................................................................................................................................
To add a new external IPv4 subnet

Purpose
Use this procedure to add one new external IPv4 subnet to existing systems.
Note: Please run this procedure during low traffic periods. Not following the steps of
this procedure in order may cause call processing outages.
Before you begin

Obtain the following:
• Access to the console port in MI shelf 0.
• MI root password.
• The primary MI service is Active. If primary MI is not active, run the following
command to switchover the MI service:
MIcmd switch vc
MIcmd state vc
• The value of the parameters described in the following table. Do not start procedure
until all the information is complete.
Parameter Value Description

Subnet Base Specifies an IPv4 subnet value.
For example: 172.25.126.8
Subnet Mask Specifies an IPv4 subnet mask.
For example: 255.255.255.248.
Subnet Name Specifies a string with a 16-byte maximum
length. Characters can be alphanumeric,
underscore, dash and space. The first character
must be alphabetic. If spaces are used, the name
must be contained within double quotes.
Subnet Number Use
net4conf_adm --action show_external_
subnet to list the existing external subnets.
Select a new number.
V4 Gateway Specifies an offset value to an IPv4 address to
the default gateway.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................

Transport ID 1 Specifies a single transport ID (simplex) or a
Transport ID 2 pair of transport IDs (duplex). Transport IDs
correlate an external subnet with the wires or
interfaces that the subnet uses to connect to the
customer network. For example, use
ltf0,rtf0 to communicate with the Hubs
GE0 front panel port.
To list all transport IDs enter:
net4conf_adm --action list_external_
transport .
Procedure
...................................................................................................................................................................................................
1 Login to Active MI host as root.

...................................................................................................................................................................................................
2 To add a new external IPv4 subnet, enter the following command:

ip_adm -a add_subnet -b <Subnet Base> -m <Subnet Mask> -n
<Subnet Name> -s <Subnet Number> -o <V4 Gateway> -t <Transport
ID 1,Transport ID2>
Here are some examples:
ip_adm -a add_subnet -b 192.168.1.0 -m 255.255.255.0 -n
Samp4Simplex -s 4 -o 1 -t lnf2
ip_adm -a add_subnet -b 192.168.1.0 -m 255.255.255.0 -n
Samp4Duplex -s 4 -o 1 -t ltf1,rtf1
...................................................................................................................................................................................................
3 To save changes enter:

ip_adm -a commit
To backout before saving, enter:
ip_adm -a backout
Note: Commit and backout actions must be executed on the same card as the
add_subnet action.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To delete an external IPv4 subnet
....................................................................................................................................................................................................................................
To delete an external IPv4 subnet

Purpose
Use this procedure to delete an external IPv4 subnet in existing system.
Note: Run this procedure during low traffic periods. Ensure the steps in the procedure
are followed in order, to prevent call processing outage.
Before you begin

MIcmd switch vc
MIcmd state vc
• The value of the parameters described in the following table.

Subnet Use net4conf_adm --action show_external_subnet to get all
Base correct parameters corresponding your subnet to be deleted
Subnet
Number
Note: Do not start the procedure until all the information is complete.
Procedure
...................................................................................................................................................................................................
1 Login to the active MI host as root.

...................................................................................................................................................................................................
2 To check if there is IPv4 address on this subnet to be deleted, enter the following
command:
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
net4conf_adm --action show_service_all
If Then
there is IPv4 fixed address delete all IPv4 fixed addresses using the
procedure “To delete an external fixed IPv4
there is IPv4 floating address delete all IPv4 floating addresses using the
procedure “To delete an external floating IPv4
...................................................................................................................................................................................................
3 To delete an external IPv4 subnet, enter the following command:

ip_adm -a del_subnet -b <Subnet Base> -s <Subnet Number>
Example:
ip_adm -a del_subnet -b 10.241.71.192 -s 9
...................................................................................................................................................................................................
4 To save changes enter the following command:

ip_adm -a commit
ip_adm -a backout
del_subnet action.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
To add a new external IPv6 subnet

Purpose
Use this procedure to add one new external IPv6 subnet to existing systems.
Note: Please run this procedure during low traffic periods. Ensure the steps in the
procedure are followed in order, to prevent call processing outage.
Before you begin

• The primary MI service is active. If primary MI is not active, run the following
MIcmd switch vc
MIcmd state vc
• The value of the parameters described in the following table. Do not start the
procedure until all the information is complete.

Subnet Prefix Specifies a partial Global Unicast IPv6 subnet value.
The first three bits are "001" to indicate a unicast
address. For example: 2001:DB8::
Prefix Length Specifies the number of bits in the above number.
Prefix lengths can be any length from 3 to 127.
Subnet Name Specifies a string with a 16-byte maximum length.
Characters can be alphanumeric, underscore, dash and
space. The first character must be an alphabet. If
spaces are used, the name must be contained within
double quotes.
Subnet Number Use
subnet to list existing external subnets. Select a new
number.
V6 Gateway Specifies an IPv6 address to the default gateway.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................

Transport ID 1, Specifies a pair of transport IDs. Transport IDs
Transport ID 2 correlate an external subnet with the wires or
interfaces that the subnet uses to connect to the
customer network. For example, use ltf0,rtf0 to
communicate with the Hubs GE0 front panel port. Use
net6conf_adm --action list_external_
transport to list all transport IDs.
Procedure
...................................................................................................................................................................................................
1 Login to ActiveMI host as root.

...................................................................................................................................................................................................
2 To add a new external IPv6 subnet, enter the following command:

ip_adm -a add_subnet -b <Subnet Prefix> -m <Prefix Length> -n
<Subnet Name> -s <Subnet Number> -o <V6 Gateway> -t <Transport
ID 1,Transport ID2>
Examples:
ip_adm -a add_subnet -b 2001:DB8:: -m 64 -n Samp6Simplex -s 4 -o
2001:dB8::1 -t lnf2
ip_adm -a add_subnet -b 2001:DB8:: -m 64 -n Samp6Duplex -s 4 -o
2001:dB8::1 -t ltf1,rtf1
...................................................................................................................................................................................................
3 To save changes enter:

ip_adm -a commit
ip_adm -a backout
add_subnet action.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
To delete an external IPv6 subnet

Purpose
Use this procedure to delete an external IPv6 subnet in the existing system.
Before you begin

MIcmd switch vc
MIcmd state vc

Subnet Base Use net6conf_adm --action show_external_subnet to
Subnet get all correct parameters corresponding your subnet to be deleted.
Number
Procedure
...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 To check if there is IPv6 address on this subnet to be deleted, enter the following
command:
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
If Then
there is IPv6 fixed address delete all IPv6 fixed addresses using the
procedure “To delete an external fixed IPv6
there is IPv6 floating address delete all IPv6 floating addresses using the
procedure “To delete an external floating IPv6
Check again using the following command:

...................................................................................................................................................................................................
3 To delete an external IPv6 subnet, enter the following command:

ip_adm -a del_subnet -b <Subnet Prefix> -s <Subnet Number>
Example:
ip_adm -a del_subnet -b 2500:0:0:476:0:0:0:0 -s 10
...................................................................................................................................................................................................

ip_adm -a commit
ip_adm -a backout
del_subnet action.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To add a new external fixed IPv4 address
....................................................................................................................................................................................................................................
To add a new external fixed IPv4 address

Purpose
Use this procedure to add new external fixed IPv4 addresses to existing systems for one
service pool at a time. This procedure only supports the configuration of IPv4 external
service IP addresses for NI types of services on diskless and diskful hosts.
Before you begin

MIcmd switch vc
MIcmd state vc

Service Type Specifies the service type for a diskless or diskful card.
Use svcconf_adm --action list_service_type to
list existing service types.
Pool ID Use svcconf_adm --action show_host to list existing
pool numbers.
Subnet Number Use
net4conf_adm --action show_external_subnet to
list existing external subnets.
NI Type Optional Specifies the Network Interface type.
Use svcconf_adm --action list_ni_type to list all
NI Types associated with a specified service. If not
specified, the "unassigned" NI Type is used.
Offset 1 This is for adding external Specifies a pair of offset values
Offset 2 to the external IPv4 fixed IPs. One offset for each host.
Offset 1 is for Pool Member 0. Offset 2 is for Pool Member
1.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Procedure
...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 To add a new external fixed IPv4 address, enter the following command:
ip_adm -a add_fixed_ip -t <Service Type> -i <Pool ID> -s <Subnet
Number> -o <Offset 1,Offset 2>
ip_adm -a add_fixed_ip -d -t cnfg -i 0 -s 4 -n default -o 2,3
ip_adm -a add_fixed_ip -d -t cnfg -i 0 -s 4 -o 2,3
...................................................................................................................................................................................................
3 To save changes, enter:

ip_adm -a commit
ip_adm -a backout
add_fixed_ip action.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To delete an external fixed IPv4 address
....................................................................................................................................................................................................................................
To delete an external fixed IPv4 address

Purpose
Use this procedure to delete an external fixed IPv4 address in existing system for one
service pool at a time. This procedure supports the removal of IPv4 external service IP
addresses from all host types.
Before you begin

MIcmd switch vc
MIcmd state vc

Service Type Use net4conf_adm --action show_service_all to get all
Pool ID the correct parameters corresponding to the IP address to be
deleted.
Subnet Number
Offset 1
Offset 2
Procedure
...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 To check the NI type of this IP address, enter the following command:
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
net4conf_adm --action show_service_all --servicetype <type> --
poolnum <num>
If Then
The NI type of the IP address is “unassigned” Proceed to the next step.
The NI type of the IP address is anything other Modify the NI type of the IP address to
than “unassigned” “unassigned”.
See “To modify the IP addresses of a Network
Interface” (p. 8-67).
...................................................................................................................................................................................................
3 To delete an external fixed IPv4 address, enter the following command:

ip_adm -a del_fixed_ip -t <Service Type> -i<Pool ID> -s <Subnet
Number> -o <Offset 1,Offset 2>
Here is an example:
ip_adm -a del_fixed_ip -t cnfg -i 0 -s 4,4 -o 2,3
...................................................................................................................................................................................................

ip_adm -a commit
ip_adm -a backout
del_fixed_ip action.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To add a new external floating IPv4 address
....................................................................................................................................................................................................................................
To add a new external floating IPv4 address

Purpose
Use this procedure to add one new external floating IPv4 address to existing systems for
one service pool at a time. This procedure only supports the configuration of IPv4
external service IP addresses for NI types of services on diskless and diskful hosts.
Before you begin

MIcmd switch vc
MIcmd state vc

Service Type Specifies the service type for a diskful or diskless
card.
Use
svcconf_adm --action list_service_
type to list existing service types.
Pool ID Use svcconf_adm --action show_host to
list existing pool numbers.
Subnet Number Use
subnet to list existing external subnets.
Use svcconf_adm --action list_ni_type
to list all NI Types associated with a specified
service. If not specified, the "unassigned" NI
Type is used.
Offset Specifies an offset value to the external IPv4
floating IP.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Procedure
...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 To add a new external floating IPv4 address, enter the following command:
ip_adm -a add_floating_ip -t <Service Type> -i <Pool ID> -s
<Subnet Number> -o <Offset>
ip_adm -a add_floating_ip -d -t cnfg -i 0 -s 4 -n default -o 2
ip_adm -a add_floating_ip -d -t cnfg -i 0 -s 4 -o 2
...................................................................................................................................................................................................

ip_adm -a commit
ip_adm -a backout
add_floating_ip action.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To delete an external floating IPv4 address
....................................................................................................................................................................................................................................
To delete an external floating IPv4 address

Purpose
Use this procedure to delete an external floating IPv4 address in existing system for one
Before you begin

MIcmd switch vc
MIcmd state vc

Pool ID the correct parameters corresponding to the IP address to be deleted.
Subnet Number
Offset
Procedure
...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
poolnum <num>
If Then
...................................................................................................................................................................................................
3 To delete an external floating IPv4 address, enter the following command:

ip_adm -a del_floating_ip -t <Service Type> -i<Pool ID> -s
<Subnet Number> -o <Offset>
Here is an example:
ip_adm -a del_floating_ip -t ims -n -i 0 -s 9 -o 2
...................................................................................................................................................................................................

ip_adm -a commit
ip_adm -a backout
del_floating_ip action.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
To add a new external fixed IPv6 address

Purpose
Use this procedure to add new external fixed IPv6 addresses to existing systems for one
service pool at a time. This procedure only supports the configuration of IPv6 external
service IP addresses for NI types of services on diskless and diskful hosts.
Before you begin

MIcmd switch vc
MIcmd state vc

Service Type Specifies the type of service for a diskful or diskless
card.
Use
svcconf_adm --action list_service_type
to list existing service types.
Pool ID Use svcconf_adm --action show_host to list
existing pool numbers.
Subnet Number Use
Use svcconf_adm --action list_ni_type to
list all NI Types associated with a specified service. If
not specified, the "unassigned" NI Type is used.
V6 Address 1 Specifies a pair of external IPv6 fixed IPs. One IP for
V6 Address 2 each host. V6 Address 1 is for Service Pool Member
0. V6 Address 2 is for Service Pool Member 1.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Procedure
...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 To add a new external fixed IPv6 address, enter the following command:
ip_adm -a add_fixed_ip -t <Service Type> -i <Pool ID> -s <Subnet
Number> -o <V6 Address 1,V6 Address 2>
ip_adm -a add_fixed_ip -d -t cnfg -i 0 -s 4 -n default -o 2001:
DB8::1:2:3:4,2001:DB8::1:2:3:5
ip_adm -a add_fixed_ip -d -t cnfg -i 0 -s 4 -o 2001:DB8::1:2:3:
4,2001:DB8::1:2:3:5
...................................................................................................................................................................................................

ip_adm -a commit
To backout before save, enter:
ip_adm -a backout
add_fixed_ip action.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
To delete an external fixed IPv6 address

Purpose
Use this procedure to delete an external fixed IPv6 address in existing system for one
Before you begin

MIcmd switch vc
MIcmd state vc

Pool ID the correct parameters corresponding to the IP address to be deleted.
Subnet Number
V6addr 1
V6addr 2
Procedure
...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
poolnum <num>
If Then
...................................................................................................................................................................................................

ip_adm -a del_fixed_ip -t <Service Type> -i<Pool ID> -s <Subnet
Number> -o <v6addr1,v6addr2>
Example:
ip_adm -a del_fixed_ip -t ims -i 0 -s 10 -o 2500:0:0:476:0:0:0:
100,2500:0:0:476:0:0:0:200
...................................................................................................................................................................................................

ip_adm -a commit
ip_adm -a backout
del_fixed_ip action.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
To add a new external floating IPv6 address

Purpose
Use this procedure to add one new external floating IPv6 address to existing systems for
one service pool at a time. This procedure only supports the configuration of IPv6
external service IP addresses for NI types of services on diskless and diskful hosts.
Before you begin

MIcmd switch vc
MIcmd state vc

Service Type Specifies the service type for a diskful or diskless
card.
Use
svcconf_adm --action list_service_type
to list existing service types.
Pool ID Use svcconf_adm --action show_host to list
existing pool numbers.
Subnet Use
Number net6conf_adm --action show_external_
Use svcconf_adm --action list_ni_type to
list all NI Types associated with a specified service.
If not specified, the "unassigned" NI Type is used.
V6 Address An IPv6 address to the external IPv6 Floating IP.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Procedure
...................................................................................................................................................................................................

...................................................................................................................................................................................................
2 To add a new external floating IPv6 address, enter the following command:
ip_adm -a add_floating_ip -t <Service Type> -i <Pool ID> -s
<Subnet Number> -o <V6 Address>
ip_adm -a add_floating_ip -d -t cnfg -i 0 -s 4 -n default -o
2001:DB8::1:2:3:4
ip_adm -a add_floating_ip -d -t cnfg -i 0 -s 4 -o 2001:DB8::1:2:
3:4
...................................................................................................................................................................................................

ip_adm -a commit
ip_adm -a backout
add_floating_ip action.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
To delete an external floating IPv6 address

Purpose
Use this procedure to delete an external floating IPv6 address in existing system for one
Before you begin

MIcmd switch vc
MIcmd state vc

Pool ID the correct parameters corresponding to the IP address to be
deleted.
Subnet Number
V6addr
Procedure
...................................................................................................................................................................................................

...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
poolnum <num>
If Then
...................................................................................................................................................................................................

ip_adm -a del_floating_ip -t <Service Type> -i<Pool ID> -s
<Subnet Number> -o <v6addr>
Example:
ip_adm -a del_floating_ip -t ims -i 0 -s 10 -o 2500:0:0:476:0:0:
0:100
...................................................................................................................................................................................................

ip_adm -a commit
ip_adm -a backout
del_floating_ip action.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To add or delete static routes for a service
....................................................................................................................................................................................................................................
To add or delete static routes for a service

Purpose
Use this procedure to add or delete static routes for a selected service.
Caution
NOTICE
Service-disruption hazard
This procedure affects IP traffic to and from the system. Performing this procedure
outside the maintenance period, when the system is busy, or both can result in service
disruption.
Perform this procedure only during the maintenance period and when the system is not
busy. The time required to complete this procedure is between 7 to 15 minutes depending
on the size and activity on the system.
NOTICE
Performing system configuration activities while you perform this procedure can result in
service disruption.
While you perform this procedure, limit your access to the MI-GUI and Provisioning GUI
to viewing only. Do not perform any other activity that is related to system configuration
such as software upgrade, software patching, hardware maintenance, growth or degrowth
procedures.
Before you begin

This procedure is performed via the MI-GUI.
Important! It is important that all services are running active/standby and no
maintenance activities to change these states (for example cnfg service switchover)
are occurring before using this procedure.
In order to check the switch health make sure that the command su_health -a runs
complete successfully without errors or warnings.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Procedure
...................................................................................................................................................................................................
1 Use the tree view on the MI-GUI, to expand Office → Configuration Management.
...................................................................................................................................................................................................
2 Click Static Route.

Result: The Static Route window appears in the topological view of the MI-GUI.
Note: The Static Route window can also be accessed by the following procedure:
1. At the MI-GUI tree view, select Office → Network Maps → <Sub-Network
Element> → LCP-(x) → Services.
2. Select the service in the Pools list and use the cursor menu to open the Static
Route window. In this case proceed with step 4.
...................................................................................................................................................................................................
3 Select the desired service in the list at the right side of the window.
Result: The Static Routes for Service: table is displayed
...................................................................................................................................................................................................
4 If you want to.. then...

add a static route proceed with Step 5.
delete a static route select the static route and click Delete.
Apply the confirmation message.
The screen displays the updated data.
End of procedure.
Note: When a static route is deleted, it is removed only from the service that has been
selected in the MI GUI. The other services on this host that have not been selected
will still have the static route. To remove the static route from other services, delete
the static route for each service one after the other.
If the data of the static route page is out of date, please run a Global Rediscovery.
...................................................................................................................................................................................................
5 Click Add.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Result: The Add new Static Route for Service window is displayed.
...................................................................................................................................................................................................
6 If you want to.. Then...

add a IPv4 static route add the requested data in the text fields Subnet
Base, Subnet Mask, select the Subnet Number
to use as the default gateway and click
Confirm.
Refer image: Figure 8-1, “Add a IPv4 static
route:” (p. 8-66)
add a IPv6 static route add the requested data in the text fields Subnet
Prefix, Subnet Length, select the Subnet
Number to use as the default gateway and
click Confirm.
Refer image: Figure 8-2, “Add a IPv6 static
route” (p. 8-66)
Result: The System Configuration Data Tool (SCDT) will update the database. The
Add new Static Route for Service: window is closed, the Static Routes for Service:
table displays the updated data.
Note: The database update procedure takes a couple of minutes.
When a static route is added, all the services on this host (not only the service selected
on the MI GUI) will have this static route.
If the data of the static route page is out of date, please run a Global Rediscovery.
E...................................................................................................................................................................................................
N D O F S T E P S
Static Route map

The window used to mange the Static Route.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Add
Figure 8-1 Add a IPv4 static route:
Figure 8-2 Add a IPv6 static route
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To modify the IP addresses of a Network Interface
....................................................................................................................................................................................................................................
To modify the IP addresses of a Network Interface

Purpose
Use this procedure to change the Network Interface to external IP assignment for a
selected service.
Caution
NOTICE
disruption.
NOTICE
service disruption.
procedures.
Before you begin

....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Click Network Interface.

Result: The Network Interface window appears in the topological view of the
MI-GUI.
Note: The Network Interface window can also be accessed by the following
procedure:
2. Select the service in the Pools list and use the cursor menu to open the Network
Interface window (Network Interface is available only for IMS and FS5k
service). In this case, proceed with Step 4.
...................................................................................................................................................................................................
3 Select the desired service in the list at the left side of the Network Interface window.
Result: Two lists are displayed: Service Instances and Network Interface for
Service:
...................................................................................................................................................................................................
4 Select the desired NI in the list Network Interface for Service and click Modify to
initiate the IP modification.
Result: A warning message is displayed in a new screen and all available IP addresses
are displayed.
Note:
• If the ’Zone Transfer’ and ’Notify’ DNS capability (RFC 1034, 1035, 1995, 1996)
are not enabled between 5400 Linux CP and the external DNS system, the
impacted DNS entries on the external DNS system must be manually updated
accordingly.
• The default NI to IP association and the unassigned NI to IP association are not
allowed to change!
• When changing the pdf to IP association an additional manual switchover is
required in order to activate the new IP address.
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
• When changing the web_portal to IP association for a 5420 CTS, the
Alcatel-Lucent CM must be updated to reflect the new service label associated
with the IP address of the web_portal. For procedures to change the Web Portal
Identity (WPIF) parameter refer to the Alcatel-Lucent Communication Manager
Administration Guide, .255-490-001 Section: Add, modify, or delete a node.
• The base_cfg.sh command allows the system administrator to change the WPIF
realm in the 5420 CTSceglar data base.
...................................................................................................................................................................................................
5 Select the IPs and click Apply.

Result: The database will be updated and the new data will be displayed in the
Network Interface for Service table.
E...................................................................................................................................................................................................
N D O F S T E P S
Network Interface Map

The window used to manage the NI parameter:
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Figure 8-3 Network Interface
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To modify the Default Gateway data for a service
....................................................................................................................................................................................................................................
To modify the Default Gateway data for a service

Purpose
Use this procedure to change the Default Gateway for a selected service.
Caution
NOTICE
disruption.
NOTICE
service disruption.
procedures.
Before you begin

....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
2 Click Default Gateway.

Result: The Default Gateway window appears in the topological view of the
MI-GUI.
Note: The Default Gateway window can also be accessed by the following
procedure:
2. Select the service in the Pools list and use the cursor menu to open the Default
Gateway window. In this case proceed with step 4.
...................................................................................................................................................................................................
3 Select the desired service in the list at the left side of the Default Gateway window.
Result: The Subnet Information is displayed listing the Host Pair Information.
...................................................................................................................................................................................................
4 Click Modify.
Result: The Available Default Gateway Subnet Number dialog window is
displayed.
Note: Please note the warning in the dialog window.
...................................................................................................................................................................................................
5 Select the new subnet assignment and click Modify again.

Result: A message box appears asking for confirmation of the modification.
...................................................................................................................................................................................................
6 Confirm the modification.

Result: The System Configuration Data Tool (SCDT) command will be started to
update the data in the database. After that the confirmation window will be closed and
the updated data is then displayed in the Default Gateway window.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Default Gateway map
The window used to manage the Default Gateway:
Figure 8-4 Default Gateway
Modify
The window that is used to modify the subnet assignments:
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Figure 8-5 Modify Default Gateway
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To set port speeds of hub-based transport interfaces
....................................................................................................................................................................................................................................
To set port speeds of hub-based transport interfaces

Purpose
Use this procedure to set the port speeds of hub-based transport interfaces.
Procedure
...................................................................................................................................................................................................
1 The System Configuration Data Tools (SCDT) will support new command line
parameters to the netconf_adm tool for setting port speeds of hub-based transport
interfaces.
...................................................................................................................................................................................................
2 Execute the following command to set the port speed:

netconf_adm --action set_port_speed --transportid [tpids] --portspeed
<speed>
Note: --transportid indicates an external transport ID with [tpids] representing
a comma-separated list of one or more external transport IDs. For a complete
overview of the available external transport IDs, check the map file from the
following location: /var/opt/lib/map/transport_vlan.map
--portspeed <speed> indicates a port speed with <speed> having a value of a
valid port speed. For a complete overview of the available port speeds, check the map
file from the following location: /var/opt/lib/map/hardware_info.map
...................................................................................................................................................................................................
3 Execute the following command to clear the port speed:

netconf_adm --action clr_port_speed --transportid [tpids]
...................................................................................................................................................................................................
4 Execute the following command to show the port speed:

netconf_adm --action show_port_speed [--transportid [tpids]]
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Overview
Purpose
This section provides the procedures necessary to add or delete the remote NTP servers IP
addresses and to change the time zone.
Contents
To add or delete remote NTP servers IP addresses 8-77

To change the time zone 8-79
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To add or delete remote NTP servers IP addresses
....................................................................................................................................................................................................................................
To add or delete remote NTP servers IP addresses

Purpose
Use this procedure to add or delete the IP addresses of remote Network Time Protocol
(NTP) servers on the 5400 Linux CP system.
Use the backout instructions in the procedure, if the changes are not correct.
Before you begin

Refer to “ntp_adm” (p. A-20) for explanation of the ntp_adm command used in this
procedure.
Have the following configuration data ready:
• The IP address of the new NTP server, to add the IP addresses of remote NTP servers
• The IP address of the current NTP server, to delete the IP addresses of remote NTP
servers
Run the following command to show current remote NTP server:
– ntpconf_adm --action show_server
Procedure
...................................................................................................................................................................................................
1 Login to the active MI as root:

...................................................................................................................................................................................................
2
To add a remote NTP server or a list of remote Proceed with Step 3
NTP servers
To delete a remote NTP server or a list of Skip to Step 4
remote NTP servers
...................................................................................................................................................................................................
3 To add a remote NTP server or a list of remote NTP servers, type the following command:
ntp_adm –a add –i <IP list>
Note: The procedure will backout automatically when it runs into a failure.
When it completes successfully, it will print out the message:
ntp_adm add SUCCESSUL. AFTER TESTING, RUN “ntp_adm –a
commit”. OR YOU CAN BACKOUT VIA ntp_adm –a backout.
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To add or delete remote NTP servers IP addresses
....................................................................................................................................................................................................................................
Go to Step 5
...................................................................................................................................................................................................
4 To delete a remote NTP server or a list of remote NTP servers, type the following
command:
ntp_adm –a del –p <IP list>
When it completes successfully, it will print out the message:
ntp_adm del SUCCESSUL. AFTER TESTING, RUN “ntp_adm –a
commit”. OR YOU CAN BACKOUT VIA ntp_adm –a backout.
...................................................................................................................................................................................................
5 Commit the changes by typing the following command.

ntp_adm –a commit
To backout before commit, type the following command:
ntp_adm –a backout
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To change the time zone
....................................................................................................................................................................................................................................
To change the time zone

Purpose
Use this procedure to set the time zone on the 5400 Linux CP system.
Before you begin

Refer to “tz_adm” (p. A-21) for explanation of the tz_adm command used in this
procedure.
Keep the following provisioning data ready to complete the procedure:
• Country name for new time zone
Procedure
...................................................................................................................................................................................................
1 Login to the active MI as root:

...................................................................................................................................................................................................
2 Find the current time zone by typing the following command:

tzconf_adm --action show_timezone
...................................................................................................................................................................................................
3 Find the valid country code by typing the following command:

tz_adm –a list_country_code –l <country name>
Example:
tz_adm -a list_country_code -l "india"
Tue Dec 9 04:46:09 CST 2008
Running tz_adm
country_code country_name
----------------------------------------
IN India
IO British Indian Ocean Territory
...................................................................................................................................................................................................
4 Find the valid time zone by typing the following command:

tz_adm –a list_tz_name –n <country_code>
Example:
tz_adm -a list_country_code -n "IN"
Tue Dec 9 04:66:09 CST 2008
Running tz_adm
....................................................................................................................................................................................................................................
March 2011
Manage system configuration - IP configuration To change the time zone
....................................................................................................................................................................................................................................
country_code time_zone
----------------------------------------
IN Asia/Calcutta
...................................................................................................................................................................................................
5 Change the time zone by typing the following command:

tz_adm –a change –t <time zone>
tz_adm add SUCCESSUL. AFTER TESTING, RUN “tz_adm –a commit”.
Or YOU CAN BAcKOUT VIA ntp_adm –a backout.
...................................................................................................................................................................................................
6 Commit the changes by typing the following command.

tz_adm –a commit
To backout before commit, type the following command:
tz_adm –a backout
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
March 2011
Appendix A: Command
descriptions
Overview
Purpose
This appendix provides information on the hazard statements and CLI commands used for
configuration management.
Contents
Hazard statements A-2

Structure of safety statements A-2
Common cautions and warnings A-4
Command descriptions A-6
lss_adm A-6
su_health A-8
create_ht A-10
sim A-11
grow A-13
degrow A-14
dns_adm A-15
ip_adm A-18
ntp_adm A-20
tz_adm A-21
enum_adm A-22
...................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary A-1
March 2011
Command descriptions Structure of safety statements
Hazard statements
....................................................................................................................................................................................................................................
Hazard statements
Structure of safety statements

Overview
Safety statements describe the safety risks relevant while performing tasks on
Alcatel-Lucent products during deployment and/or use. Failure to avoid the hazards may
have serious consequences.
General structure
Safety statements include the following structural elements:
B C D
CAUTION
Lifting hazard E F
Lifting this equipment by yourself can result in injury
due to the size and weight of the equipment. G
Always use three people or a lifting device to transport
and position this equipment. [ABC123]
H
Item Structure element Purpose
1 Safety alert symbol Indicates the potential for personal injury
(optional)
2 Safety symbol Indicates hazard type (optional)
3 Signal word Indicates the severity of the hazard
4 Hazard type Describes the source of the risk of damage or
injury
5 Safety message Consequences if protective measures fail
6 Avoidance message Protective measures to take to avoid the hazard
7 Identifier The reference ID of the safety statement
(optional)
....................................................................................................................................................................................................................................
A-2 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
March 2011
Command descriptions Structure of safety statements
Hazard statements
....................................................................................................................................................................................................................................
Signal words
The signal words identify the hazard severity levels as follows:
Signal word Meaning

DANGER Indicates an extremely hazardous situation which, if not avoided, will
result in death or serious injury.
WARNING Indicates a hazardous situation which, if not avoided, could result in
death or serious injury.
CAUTION Indicates a hazardous situation which, if not avoided, could result in
minor or moderate injury.
NOTICE Indicates a hazardous situation not related to personal injury.
....................................................................................................................................................................................................................................
March 2011
Command descriptions Common cautions and warnings
Hazard statements
....................................................................................................................................................................................................................................
Common cautions and warnings

Common cautions
WARNING
Overhead-load hazard
Cabinet eyebolts can break, severely damaging the cabinet, if a crane is used to lift the
cabinet into an upright position.
Ensure that the cabinet is in an upright position before transportation by crane.
WARNING
Electric-shock hazard
There is a danger of electric shock if the grounding system is inadequate.
You must comply with the grounding requirements for the grounding system.
CAUTION
Lifting hazard
Lifting this equipment by yourself can result in injury due to the size and weight of the
equipment.
Always use three people or a lifting device to transport and position this equipment.
NOTICE
ESD hazard
Electronic components can be destroyed by electrostatic discharge (ESD).
Circuit packs must therefore always be kept in antistatic covers. Use the original
antistatic packaging if possible.
Always observe the general ESD instructions.
NOTICE
Overhead-load hazard
Connectors on the roof of the cabinet can be damaged during transport by the crane
hook, lifting harness, or chains causing damage to the unit.
Avoid any contact between connectors and heavy lifting equipment. Operate with caution.
....................................................................................................................................................................................................................................
March 2011
Command descriptions Common cautions and warnings
Hazard statements
....................................................................................................................................................................................................................................
NOTICE
Condensation can occur in the network element during transport, especially on moving
from outside to closed rooms. Condensation can cause malfunctioning of the circuit
packs.
Ensure that circuit packs and shelves have reached room temperature and are dry before
taking them into operation.
All hazard statements that are not specific to individual procedures are mentioned in this
topic. Hazard statements describe risks, primarily to personnel, that are relevant to
procedures performed during the deployment and/or use of Alcatel-Lucent products.
Failure to avoid the hazards can have serious consequences.
....................................................................................................................................................................................................................................
March 2011
Command descriptions 5400 Linux CP compliance summary
....................................................................................................................................................................................................................................
lss_adm
Description
This command provides backup capabilities for the 5400 Linux CP non-MI diskful hosts.
The 5400 Linux CP non-MI diskful hosts are as follows:
• CDR
• FSDB
• CNFG
Tasks
The lss_adm command is used to perform the following tasks:
• Back up configuration files and database for 5400 Linux CP Non-MI service hosts
(using CLI)
• List backups of configuration files and database for 5400 Linux CP Non-MI service
hosts (using CLI)
• Retrieve the 5400 Linux CP software version per Non-MI service diskful host or for
all Non-MI service diskful hosts
Synopsis
[1] lss_adm -a action [ -v ] [ -d <debug_level> ] [ --forcecln|--
nocln|--condchk ]
Parameters
-a <action>
Specify the administrative task to be performed. The valid actions are:
• help: Print the usage message.
• version:
Print the LSS software version currently installed, applicable for Non-MI service
hosts.
• Backup configuration files and database for Non-MI service hosts
• list_backup: Print a summary of the LSS software releases and
configuration/data backups that have been archived on the host system.
-v Generates verbose mode to stdout. This is equivalent to specifying the option “-d
1”.
-d <level>
....................................................................................................................................................................................................................................
March 2011
Command descriptions lss_adm
....................................................................................................................................................................................................................................
Generates increasing amount of debug output as the integer level parameter increases.
--forcecln Used only when action is specified as “backup”. During a “backup”, old
data backups are removed automatically if the number of allowed data backups for the
LSS is exceeded. The user is not prompted for confirmation. The number of allowed
data backups per network element can be provisioned by using the bkup_adm tool.
--nocln Used only when action is specified as “backup”. During a “backup”, old
data backups are not removed.
--condchk Used only when action is specified as “backup”. A “backup” is not run if
the number of allowed data backups for the LSS is exceeded. The number of allowed
data backups per network element can be provisioned using the bkup_adm tool.
Additional information
This command can be used at any login with sysadmin privilege.
Examples
[1] lss_adm —a list_backup
[2] lss_adm —a help
[3] lss_adm –a action
....................................................................................................................................................................................................................................
March 2011
Command descriptions su_health
....................................................................................................................................................................................................................................
su_health
Description
This command is a utility to check for the "SU health" of a ATCA-based LSS system .
Tasks
The command is used when performing the following tasks:
• Checking the system condition in case of a backup, restore or pack replacement
procedure.
• Normally run prior to and after the completion of a software upgrade of the
system.
• Executed from the MI as user 'root'.
• can be used to collect log files from the system (using the -l option) to aid in
debugging from the next level of technical support.
Synopsis
[1] su_health -[aAbBcdD < MI|CNFG > fhiImMqrRsStvV]
Parameters
–a Performs all relevant system tests
-A Checks su_alarm
–b Checks database replication
–B Checks Database
-c Checks connectivity of all cards
-d Checks disk space
-D <MI|CNFG> Checks DHCP data on specified service type
-f Check all relevant tests after a field installation
-h Prints help information
-H Checks the hub configuration
-i Information about all IP addresses sent to screen
-I Information about all IP addresses sent to log
-m Checks SCDT health.
-M Checks diskless images consistency between CNFGs
-q Checks root access to all hosts via rsh or ssh
-r Checks REM states for diskless cards
-R Checks RCC states for diskful cards
....................................................................................................................................................................................................................................
March 2011
Command descriptions su_health
....................................................................................................................................................................................................................................
-s Checks rsh for both the MIs
-S Checks software version and build number for diskless cards
-t Checks if system time is synchronized between all hosts
-v Checks for software version consistency
-V Checks VM states for diskful cards.
Usage
By default su_health writes relevant output to stdout and saves detailed information in
the log file:
/var/opt/log/suhealth/suhealth.log
Additional Information
This command can only be used as user root.
Examples
• To run all the tests type the following command:
su_health -a
• To run just the ping component of the tests, if some hosts fail to ping, type the
following
su_health -c
....................................................................................................................................................................................................................................
March 2011
Command descriptions create_ht
....................................................................................................................................................................................................................................
create_ht
Description
This command is use to create the system configuration tables. The sim tool uses these
tables during the installation of the new release software to determine the physical
configuration of the system. Entering the command creates the hosts.dat file used by the
SIM process to list the actionable items that could be taken by SIM based upon the rules
being applied.
• Replacement of Hub Cards
• Replacement of a diskless Processor card
• Replacement of a diskful Processor` card
• Restore the “Protected” 5400 Linux CP database for non-MI diskful blades
• Hardware and service growth of diskless hosts
• Hardware and service growth of diskful hosts
• Degrowth of diskful and diskless hosts
• Hardware and service degrowth of diskless/diskful hosts
• Stop 5400 Linux CP processes
• Restore Non-MI database on every Non-MI host.
Command syntax
The command syntax for create_ht is create_ht.
When running the command the following files are created:
• hosts.dat
• hostdat.layout
• hostdat.ksh
....................................................................................................................................................................................................................................
March 2011
Command descriptions sim
....................................................................................................................................................................................................................................
sim
Description
The Software Installation Manager (sim) tool is used by a variety of maintenance process
procedures in order to execute a series of commands required by a maintenance process.
When sim is initiated it will report the location of the following files used during
processing. It will then prompt the user for authorization to continue before applying any
of the process rules.
• sim log file - Logs the status of commands executed by sim
• hosts file - Defines data used by sim for all the hosts in the system.
• rules file - Defines commands to be executed by the sim process procedure.
The sim command is used when performing the following maintenance process tasks:
• Upgrading software on the MI-B host and on other hosts
• Patching software on the MI-B host and on other hosts
• Replacing diskful/diskless host hardware
• Restoring database for all non-MI diskful hosts
• Hardware growth and degrowth of diskful/diskless host
• Service growth and degrowth on diskful/diskless hosts
• Replacing chassis
Command syntax
The command syntax for the sim command is:
[1] sim procedure|action
Parameters
The appropriate 'sim' process argument is specified by documentation, for the procedure
that requires 'sim'.
Procedure process parameters:
• mi_su
• upgrade
• mi_patch
• patch
• fru
• restore
• hwgrow
• hwdegrow
....................................................................................................................................................................................................................................
March 2011
Command descriptions sim
....................................................................................................................................................................................................................................
• svcgrow
• svcdegrow
• chassis_repl
Action parameters:
• start - To begin the specified process task
• resume - To resume the specified process task already begun by sim
• backout - To back out the previously applied action of the process task
Note:Not all process actions have a backout.
Important!Do not use this action unless specified by official procedure
documentation or directed by higher level support.
• pause - To stop a running sim process task for an intended manual break.
The process stops after the completion of all previously dispatched commands.
• abort - To abort a running sim process task.
The process stops immediately without waiting for the completion of previously
dispatched commands..
Important! Do not use this action unless specified by official procedure
documentation or directed by higher level support.
NOTICE
Inappropriate use of 'sim' can result in damage to the system files and render the system
inoperable. Use only as specified by official documented procedures or higher level
support.
Use the command with caution.
Execute this command on the MI host as specified by the process procedures, using the
root login. Only one 'sim' procedure may be executed at any given time. The 'sim' tool
blocks concurrent 'sim' procedures from being initiated
The sim procedure executes as a background process. The sim log file may be monitored
to determine progress. To stop the 'sim' procedure before completion of the procedure,
execute 'sim pause'. When 'pause' is invoked, 'sim' halts processing as soon as the current
command (step) in the procedure completes. To resume a halted sim process, execute 'sim
resume'
....................................................................................................................................................................................................................................
March 2011
Command descriptions grow
....................................................................................................................................................................................................................................
grow
Description
The command is a tool used to prepare the hosts.dat file for hardware and service growth
of a pair of diskless and diskful hosts.
The tool prompts for information pertaining to the host and service that needs to be
grown. A temporary hosts.dat file is created with this information which is used by SIM
to perform the actual growth activity. The SIM commands that are run are displayed as
part of the output of this command.
Tasks
• Hardware and service growth of diskless hosts
• Hardware and service growth of diskful hosts.
Synopsis
[1] grow
....................................................................................................................................................................................................................................
March 2011
Command descriptions degrow
....................................................................................................................................................................................................................................
degrow
Description
The command is a tool used to prepare hosts.dat file for hardware and service de-growth
of a pair of diskless and diskful hosts.
The tool prompts for shelf and slot information of the hosts that needs to be de-grown. A
temporary hosts.dat file is created with this information which is used by SIM to perform
the actual de-growth activity. The SIM commands that are run are displayed as part of the
output of this command.
Tasks
The command is used when performing the following task: Hardware and service
de-growth of diskless/diskful hosts.
Synopsis
[1] degrow
....................................................................................................................................................................................................................................
March 2011
Command descriptions dns_adm
....................................................................................................................................................................................................................................
dns_adm
Description
This command provides DNS administration capabilities for the 5400 Linux CP .
Tasks
Use this command to perform the following tasks:
• add DNS remote domain
• delete DNS remote domain
• add DNS remote server
• delete DNS remote server
• show the status of DNS local domain, remote domain, remote server and MySQL
• set DNS log level
Synopsis
[1] dns_adm -a <action> -d <domainname> -i <IP list> -k <status type> -1
<level> [-c]
Parameters
-a <action>
must be one of the following values:
• add_solution_dns
• del_solution_dns
• show_status
• set_log_level
• backout
• commit
-d <domainname> must be domain name to be added, changed or deleted
-i <IP list> must be DNS server IPs to be added or deleted
-k <status type>
• local_domain
• remote_domain
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
• remote_server
• mysql
• solution_dns
-S <solution>
specifies the solution component of the FQDN.
-L <local>
specifies the local component of the FQDN.
-s <base,mask>
specifies a query subnet. The specified subnet base and subnet mask is created if it
does not exist.
• base: Specifies the IPv4 subnet base associated with the subdomain. This is a
subnet prefix for IPv6.
• mask: Specifies the IPv4 subnet mask associated with the subdomain. This is a
prefix length for IPv6.
-e <subnm,entnm,ip>
specifes a subdomain entity. The specified entnm name (along with the associated ip)
is created. The subnm name is also created if it does not exist. This option can have
one or three parameters.
• subnm: Specifies the subdomain component of the FQDN. For example: mrf.
• entnm: Specifies the entity component of the FQDN. For example: mrf1
• ip: Specifies the IP value of the entity within the subdomain subnet.
-1 <level> indicates a log level for bind where 0 is default 0 through 92
Example
[1] dns_adm -a add_remote_server -i 10.10.1.1
[2] dns_adm -a add_solution_dns -S icslab.com -L ics01
Tasks
Use this command to perform the following tasks in a single command:
• activate_daemon_type
• deactivate_daemon_type
Synopsis
[1] dns_adm --action <action> --service type <type> --poolnum <num>
--daemontype <type>
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Parameters
--action <action>
• activate_daemon_type
• deactivate_daemon_type
--service <type>
specifies the service type
--poolnum <num>
specifies the pool number
--daemontype <type>
specifies the daemon type
....................................................................................................................................................................................................................................
March 2011
Command descriptions ip_adm
....................................................................................................................................................................................................................................
ip_adm
Description
Use this command to add or delete an external IPv4/IPv6 address or subnet to both
diskless and diskful cards.
Tasks
• add an external IPv4 or IPv6 subnet
• delete an external IPv4 or IPv6 subnet
• add an external IPv4 or IPv6 IP address for a Diskful or Diskless service.
• delete an external IPv4 or IPv6 IP address for a Diskful or Diskless service.
Synopsis
[1] ip_adm -a <action> -t <service type> -i <pool id> -s <subnet num>
[-n <ni type>] -o <offset1,offset2> || -o <v6addr1,v6addr2> [-c]
[-r]
[2] ip_adm -a <action> -b <subnet base> -m <subnet mask> -n <subnet
name> -s <subnet num> -o <gtwayoffset> || -o <v6addr> -t
<tpid1[,tpid2]> [-c]
[3] ip_adm -a <action> -t <service type> -i <pool id> -s <subnet num>
[-n <ni type>] -o <offset> || -o <v6addr> [-c] [-r]
Parameters
-a action
• add_fixed_ip
• del_fixed_ip
• add_floating_ip
• del_floating_ip
• add_subnet
• del_subnet
• backout
• commit
For action add_fixed_ip/del_fixed_ip:
-i pool id
-o external fixed 1,2 IPv4 subnet offsets or external fixed 1,2
IPv6 addresses corresponding to member 0 and member 1 of the
service pool, respectively
....................................................................................................................................................................................................................................
March 2011
Command descriptions ip_adm
....................................................................................................................................................................................................................................
-n external fixed 1,2 NI types
-s external subnet number
-t service type
For action add_floating_ip/del_floating_ip:
-i <pool id>
-o external floating IPv4 subnet offset or external floating
IPv6 address
-n external floating NI type
-r reuse flag for an existing IP
-t service type
For action add_subnet:
-b external subnet base
-m external subnet mask
-n external subnet name
-o external IPv4 subnet gateway offset or external IPv6 gateway
address
-t transport id 1 and [2]. If there is two, separate them with
comma.
For action del_subnet:
-b external subnet base
....................................................................................................................................................................................................................................
March 2011
Command descriptions ntp_adm
....................................................................................................................................................................................................................................
ntp_adm
Description
This command provides remote NTP administration capabilities for the 5400 Linux CP
Tasks
• Add remote NTP server(s)
• Delete remote NTP server(s)
Synopsis
[1] ntp_adm -a <action> -d <domainname> -i <IP list> -p <IP to deleted>
[-c] [-t]
Parameters
-a <action>
can be one of the following values:
• add - adding remote NTP server IPs
• del - deleting remote NTP server IPs
• chg - adding and deleting NTP server IPs
• backout - backout the procedure
• commit - commit the procedure
-i remote NTP server IPs to be added. Comma separated if multiple
-p remote NTP server IPs to be deleted. Comma separated if multiple
-[c] clean start (remove lock file)
-h print help information
-[t] test if remote NTP server IP to be added is pingable
Example
[1] ntp_adm –a add –i 135.2.80.30
....................................................................................................................................................................................................................................
March 2011
Command descriptions tz_adm
....................................................................................................................................................................................................................................
tz_adm
Description
This command provides Time Zone administration capabilities for the 5400 Linux CP.
Tasks
Use this command to perform the following task:
• Change time zone
Synopsis
[1] tz_adm -a change -t <time zone> [-c]
[2] tz_adm -a list_country_code -l <country>
[3] tz_adm -a list_tz_name -n <contry_code>
[4] tz_adm -a backout | commit
[5] tz_adm -h
Parameters
-a <action>
can be one of the following values:
• change - change time zone
• list_country_code - list country code based on country name
• list_tz_name - list time zone name based on country code
• backout - backout the procedure
• commit - commit the procedure
-t <time zone name>
-l <country name>
-n <country code>
-[c] clean start (remove lock file)
-h print help information
Example
[1] tz_adm -a list_country_code -l "united state"
[2] tz_adm -a list_tz_name -n US
[3] tz_adm -a change -t America/Chicago
....................................................................................................................................................................................................................................
March 2011
Command descriptions enum_adm
....................................................................................................................................................................................................................................
enum_adm
Description
This command provides ENUM administration capabilities for 5400 Linux CP.
Tasks
• add ENUM remote server
• delete ENUM remote server
• add ENUM local server (for pure FS5K only)
• delete ENUM local server (for pure FS5K only)
• set ENUM log level
Synopsis
[1] enum_adm -a <action> -n <domain_name> -i <IP list> -k <status type>
-1 <level> [-c]
Parameters
-a <action>
• add_local_server (for pure FS5K only)
• del_local_server (for pure FS5K only)
• show_status
• set_log_level
• backout
• commit
-k <status type>
• local_server
• remote_server
• mysql
-i <IP list> must be ENUM server IPs to be added or deleted
-1 <level> indicates a log level for bind where 0 is default 0 through 92
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
Example
[1] enum_adm -a add_remote_server -i 10.10.1.1
....................................................................................................................................................................................................................................
March 2011
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2011
Appendix B: Conformance
statements
5400 Linux CP compliance summary

Purpose
This topic provides a summary of compliance of the 5400 Linux CP.
Compliance
The 5400 Linux CP is compliant with the following specifications:
• Telcordia Technologies GR-1089-CORE Sections 2, 3, 4, 5, 6, 7, 8, and 9 (Issue 4,
2006)
• Telcordia Technologies GR-63-CORE Sections 2, 3, 4.0, 4.1, 4.2, 4.3, 4.4, 4.5, 4.6,
and 4.7 (Ed 03, 2006)
...................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary B-1
March 2011
Conformance statements Eco-environmental statements
....................................................................................................................................................................................................................................
Eco-environmental statements
Introduction
This topic provides the eco-environmental statements that apply to Alcatel-Lucent
systems.
Packaging collection and recovery requirements

Countries, states, localities, or other jurisdictions may require that systems be established
for the return and/or collection of packaging waste from the consumer, or other end user,
or from the waste stream. Additionally, reuse, recovery, and/or recycling targets for the
return and/or collection of the packaging waste may be established.
For more information regarding collection and recovery of packaging, and packaging
waste within specific jurisdictions, contact the Alcatel-Lucent Services - Environmental
Health and Safety organization.
For installations not performed by Alcatel-Lucent, contact the Alcatel-Lucent Customer
Support Center at the following telephone number: +1 630 224 4672, prompt 2 (for all
countries).
Recycling / take-back / disposal of product

Electronic products and batteries bearing or referencing the Figure B-1, “Electronic
products symbol” (p. B-3) and Figure B-2, “Batteries symbol” (p. B-3) must be collected
and treated at the end of their useful life, in compliance with applicable European Union
and other local legislation. They must not be disposed of as part of unsorted municipal
waste. Due to materials that may be contained in the product and batteries, such as heavy
metals, the environment and human health may be negatively impacted as a result of
inappropriate disposal.
Note 1: For electronic products put on the market in the European Union, a solid bar
under the crossed-out wheeled bin indicates that the product was put on the market after
13 August 2005.
....................................................................................................................................................................................................................................
B-2 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
March 2011
....................................................................................................................................................................................................................................
Figure B-1 Electronic products symbol
Note 2: For batteries put on the market in the European Union, a chemical symbol Hg
(mercury), Cd (cadmium), or Pb (lead), or a combination of those symbols, beneath the
cross-out wheeled bin indicates that the battery contains the corresponding heavy metals.
Figure B-2 Batteries symbol
In compliance with legal requirements and contractual agreements, where applicable,

Alcatel-Lucent offers to provide for the collection and treatment of Alcatel-Lucent
products bearing the logo at the end of their useful life, or products displaced by
Alcatel-Lucent equipment offers.
For information regarding take-back, recycling, or disposal of equipment by
Alcatel-Lucent or for equipment take-back requests, visit the Alcatel-Lucent Take-Back
web page (http://www.alcatel-lucent.com/product_takeback) or contact Alcatel-Lucent
Takeback Support (takeback@alcatel-lucent.com). For technical information on product
treatment, consult the the Alcatel-Lucent Recycling Information web page
(http://www.alcatel-lucent.com/product_recycling).
Material Content Compliance

European Union (EU) Directive 2002/95/EC, "Restriction of the use of certain Hazardous
Substances" (RoHS), restricts the use of lead, mercury, cadmium, hexavalent chromium,
and certain flame retardants in electrical and electronic equipment. This Directive applies
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary B-3
March 2011
....................................................................................................................................................................................................................................
to electrical and electronic products placed on the EU market from 1 July 2006, with
various exemptions, including an exemption for lead solder in network infrastructure
equipment. Alcatel-Lucent products shipped to the EU from 1 July 2006 comply with the
RoHS Directive.
....................................................................................................................................................................................................................................
B-4 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
March 2011
Glossary
...................................................................................................................................................................................................................................
A AES
Advanced Encryption Standard
ATCA
Advanced Telecommunications Computing Architecture
...................................................................................................................................................................................................................................
C CALEA
Communications Assistance for Law Enforcement Act
CDR
Call-Detail Record
CLI
Command Line Interface
CNFG
Configuration Service
cPSB
Compact PCI Packet-Switched Backplane
...................................................................................................................................................................................................................................
D DDDS
Dynamic Delegation Discovery System
DDF
Digital Distribution Frame
DES
Data Encryption Standard
DHCP
Dynamic Host Configuration Protocol
DNS
Domain Name System
DS
Device Server
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary GL-1
March 2011
Glossary
....................................................................................................................................................................................................................................
DS
Digital Signal
...................................................................................................................................................................................................................................
E ENUM
Telephone Numbering Mapping
ESD
Electrostatic Discharge
EU
European Union
...................................................................................................................................................................................................................................
F FCAPS
Fault, Configuration, Accounting, Performance, and Security management
FQDN
Fully-Qualified Domain Name
FRU
Field-Replaceable Unit
FSDB
Feature Server Database Accepted
...................................................................................................................................................................................................................................
G GUI
Graphical User Interface
...................................................................................................................................................................................................................................
H HTTP
Hypertext Transfer Protocol
...................................................................................................................................................................................................................................
I IC
Identification Code
ICD
Internet Call Diversion
IMS
IP Multimedia Subsystem
IP
Internet Protocol
....................................................................................................................................................................................................................................
GL-2 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
March 2011
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
M MDF
Main Distribution Frame
MI
Management Interface
MIB
Management Information Base
MT
Maintenance Terminal
...................................................................................................................................................................................................................................
N NBI
Northbound Interface
NMS
Network Management System
NTP
Network Time Protocol
...................................................................................................................................................................................................................................
O OAM
Operations, Administration, Maintenance
OAM&P
Operations, Administration, Maintenance & Provisioning
ODF
Optical Distribution Frame
ODM
Office Data Manual
OOS
Out Of Service
OS-6850-48
OmniSwitch 6850 with 48 ports
...................................................................................................................................................................................................................................
R RCC
Reliable Cluster Computing
....................................................................................................................................................................................................................................
March 2011
Glossary
....................................................................................................................................................................................................................................
REM
Redundancy Manager
RoHS
Restriction of the use of certain Hazardous Substances
...................................................................................................................................................................................................................................
S S-CSCF
Serving Call Session Control Function
SCDT
System Configuration Data Tool
SIM
Software Installation Manager
SIP
Session Initiation Protocol
SNE
Subnetwork Element
SNMP
Simple Network Management Protocol
SNS
Shared Network Services
SU
Software Update
...................................................................................................................................................................................................................................
T TAS
Telephony Application Server
...................................................................................................................................................................................................................................
U URI
Uniform Resource Identifier
UTC
Universal Time Coordinated
...................................................................................................................................................................................................................................
V VC
Virtual Cluster
....................................................................................................................................................................................................................................
March 2011
Glossary
....................................................................................................................................................................................................................................
VLAN
Virtual Local Area Network
VM
Virtual Machine
VoIP
Voice over Internet Protocol
...................................................................................................................................................................................................................................
W WIP
Web Portal Identity
...................................................................................................................................................................................................................................
X XML
Extensible Markup Language
....................................................................................................................................................................................................................................
March 2011
Glossary
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
March 2011
Index
Numerics ............................................................. Discovery

5400 Linux CP DNS processes overview of, 3-33
D de-grow
Check status, 8-36 Disk Schema Conversion, 7-37
diskful hosts, 6-9
Starting, 8-30 Disk space availability
diskless hosts, 6-9
Stopping, 8-30 verification, 5-21
de-growth
............................................................. diskful hosts
diskless hosts, 6-4
A Acceptance test plan availability degrow de-grow, 6-9
verification, 5-9
command description, A-14 growth, 5-39
Add SNE for MI-GUI discovery,
Degrow SNE growth of RTM with disk, 5-60
3-4
using MI-GUI, 3-43 diskless hosts
.............................................................
delete de-grow, 6-9
C cautions and warnings, A-4
external fixed IPv4 address, de-growth, 6-4
Check status
8-48 growth, 5-27, 5-54
5400 Linux CP DNS
external fixed IPv6 address, modify state, 4-10
processes, 8-36
8-56
CNFG service, 2-3 Display state
external fixed IPv6 subnet,
compliance 8-44 MI Virtual cluster, 4-3
RoHS, B-2 external floating IPv4 address, MI Virtual machine, 4-4

8-52 DNS
WEEE, B-2
external floating IPv6 address, See: Domain Name System
compliance summary, B-1
8-60 add a DNS domain, 8-24
configuration administration
external IPv4 subnet, 8-40 add or delete a 5400 Linux CP
command
Discovery DNS solution, 8-26
health, A-8
add SNE, 3-4 dns_adm
Convert Rouzic OAM server to
Molene2 OAM server, 7-2 discovery command description, A-15
auto-delete option, 3-42 software administration

command, A-15
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary IN-1
March 2011
Index
....................................................................................................................................................................................................................................
Domain Name System, 8-18, 8-28, growth ip_adm
8-34
RTM with disk on diskful host, command description, A-18
............................................................. 5-60
software administration
E eco-environmental statement, B-2 Growth implementation command, A-18
ENUM workflow, 5-25 .............................................................

See: Telephone Numbering Growth planning L lss_adm
Mapping
workflow, 5-7 command description, A-6
add or delete a 5400 Linux CP
ENUM solution, 8-32 Growth procedure availability software administration
verification, 5-9 command, A-6
enum_adm
Growth setup .............................................................
command description, A-22
system backup, 5-22
M Malban without HSPP4, 7-16
software administration
command, A-22 growth setup
MI service, 2-5
Explicit rediscovery verify backup success, 5-23
MI Virtual cluster
using CLI, 3-41 Growth setup
Display state, 4-3
using MI-GUI, 3-40 verify disk space, 5-21
start, 4-5
............................................................. workflow, 5-20
Stop, 4-7
F functional architecture MI Virtual machine
cable new hardware, 5-13
CNFG host, 2-3 Display state, 4-4
install new hardware, 5-12
CNFG service, 2-3 start, 4-6
verify system stability, 5-15
MI host, 2-5 Stop, 4-8
workflow, 5-11
MI service, 2-5 Switch state, 4-9
Growth/degrowth
............................................................. MI-GUI
overview, 3-33
G Global discovery change local title, 3-8
.............................................................
using CLI, 3-38 degrow a SNE, 3-43, 3-44
H Hardware explicit rediscovery, 3-40, 3-41
using the MI-GUI, 3-37
IP addressing, 8-7 global discovery, 3-37
grow
subnetworks, 8-7 Global discovery, 3-38
Hardware version verification, 5-9 inventory management, 3-47
growth
Hub growth with HSPP4, 7-25 .............................................................
diskful hosts, 5-39
.............................................................
diskless hosts, 5-27, 5-54 N New hardware
Growth I Install ethernet transport, 5-17 cable for growth, 5-13
introduction, 5-4 Inventory management install for growth, 5-12

process stages, 5-5 MI-GUI, 3-47 Northbound Interface
IP subnetwork, 8-4 configure manager, 3-15
....................................................................................................................................................................................................................................
IN-2 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
March 2011
Index
....................................................................................................................................................................................................................................
configure MIB via SNMPv3, SNE System stability
3-28
degrow using CLI, 3-44 verification, 5-15
description of supported traps,
discovery by MI-GUI, 3-4 .............................................................
3-21
Software upgrade setup T task flow
load MIB, 3-12
system backup, 5-22 Northbound Interface, 3-10
lost traps, reconstruct, 3-18
software upgrade setup Telephone Numbering Mapping,
select MIB version, 3-14
verify backup success, 5-23 8-28
set SNMP port to listen on,
3-12 SOL session time zone
task flow, 3-10 establish processor card, 5-53 change time zone, 8-79
traps/notification, description Start command description, A-21

of, 3-21 transport interface: set port speed,
MI virtual cluster, 4-5
NTP 8-75
MI Virtual machine, 4-6
add or delete remote NTP traps
Starting
server IP address, 8-77 reconstruct lost, NBI, 3-18
5400 Linux CP DNS
processes, 8-30
.............................................................
state control
O operational commands modify for diskless host, 4-10
create_ht, A-10 Stop
sim, A-11 MI Virtual cluster, 4-7
............................................................. MI Virtual machine, 4-8
P platform hardware conversion, 7-1 Stopping
............................................................. 5400 Linux CP DNS
processes, 8-30
S Seed file
su_health
provision, 3-4
serial port
Switch state
establish laptop connection,
5-68 MI Virtual machine, 4-9
laptop, 5-64 System backup
windows XP, 5-66 perform, 5-22
Service system backup
Service-related IP addressing, verify, 5-23

8-15 System requirements
Service-related subnetwork, minimal, 5-8
8-15
verification, 5-8
....................................................................................................................................................................................................................................
5400 Linux CP Release 4.0 Alcatel-Lucent – Proprietary IN-3
March 2011
Index
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
IN-4 Alcatel-Lucent – Proprietary 5400 Linux CP Release 4.0
March 2011

5400 LCP Release 4.0 Alarm Dictionary

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

5400 LCP Release 4.0 Alarm Dictionary

Hochgeladen von

Copyright:

Verfügbare Formate

Use pursuant to applicable agreements

Refer to Appendix B, “Conformance statements”

About this document

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

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

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

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

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

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

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

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

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

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

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

1 5400 Linux CP configuration

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

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

2 Required 5400 Linux CP Services

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

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

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

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

3 Manage system configuration - MI-GUI procedures

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

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

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

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

Overview ...................................................................................................................................................................................... 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 clone a user for SNMPv3 from MI CLI ................................................................................................................... 3-30

Discovery and growth using the MI-GUI

Overview ................................................................................................................................................................................... 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

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

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

4 Manage system configuration - view or control the operational state

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

View or control the operational state

Overview ...................................................................................................................................................................................... 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

5 Manage system configuration - hardware growth

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

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

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

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

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