Professional Documents
Culture Documents
8DG42146LAAA-Vol1
Issue 1
October 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.
Notice
Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to
change.
Warranty
Alcatel-Lucent provides a limited warranty for this product. For more information, consult your local Alcatel-Lucent customer support team.
Ordering information
The ordering number for this document is 8DG42146LAAA-Vol1. To order 1350 OMS information products, contact your local Alcatel-Lucent customer
support team.
Technical support
For technical support, contact your local customer service support team. You can reach them via the Web at the Alcatel-Lucent Customer Support web site
(http://www.alcatel-lucent.com/support) or the customer support telephone number listed at the Alcatel-Lucent Contact Us web site (http://www.alcatel-
lucent.com/contact).
For questions or concerns about this or any other Alcatel-Lucent information product, please contact us at one of the following numbers: (888) 727 3615 (for
the continental United States) · +1 (630) 713 5000 (for all countries).
Contents
1350 OMS Modules for System Resiliency and Northbound Communication ................................................. 1-6
1-6
....................................................................................................................................................................................................................................
1350 OMS iii
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Contents
....................................................................................................................................................................................................................................
2 Applications and Their Instances
3 Configurations
Establish a Group and Initialize Node Name Management Persistent Data ....................................................... 4-7
4-7
Align All Group Member Nodes to a Specified Member Node ............................................................................ 4-17
4-17
Align One Group Member Node to Another Group Member Node .................................................................... 4-18
4-18
....................................................................................................................................................................................................................................
iv 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Contents
....................................................................................................................................................................................................................................
Change the IP Address of the Current/Local Node .................................................................................................... 4-30
4-30
Run scbackup for a Local Disk or an Application Instance Backup ................................................................... 5-24
5-24
Run scbackup Using a Disk Directory as the Supporting Output Media ........................................................... 5-29
5-29
Run screstore to Restore Data from the fbackup Media .......................................................................................... 5-37
5-37
Run the scmirrorfs Tool to Set Up the Mirrored Configuration ............................................................................ 5-44
5-44
....................................................................................................................................................................................................................................
1350 OMS v
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Contents
....................................................................................................................................................................................................................................
6 Mirror Disks
7 Network Depot
Run scbuilddepot to Create or Update the Platform Software Depot .................................................................... 7-4
7-4
Edit the .rhosts file to Authorize Access to the Application Software Depot ................................................... 7-10
7-10
8 General Operations
9 Security
Web Portal Macro Functions and Default User Profiles .......................................................................................... 9-11
9-11
PMC Management Macro Functions and Default User Profiles .......................................................................... 9-12
9-12
Session Management Macro Functions and Default User Profiles ...................................................................... 9-13
9-13
Alarm and FM Related Macro Functions and Default User Profiles .................................................................. 9-14
9-14
....................................................................................................................................................................................................................................
vi 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Contents
....................................................................................................................................................................................................................................
User Management Macro Functions and Default User Profiles ............................................................................ 9-16
9-16
Configure a Printer Booting upon Booting from the Local System .................................................................... 10-9
10-9
11 Troubleshooting
General Troubleshooting
....................................................................................................................................................................................................................................
1350 OMS vii
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Contents
....................................................................................................................................................................................................................................
System / Environment
Remove the WDM Component from the 1350 OMS ............................................................................................. 11-21
11-21
Product Installation
Configure and Test the Centralized User-DB in a Distributed Environment ................................................. 11-29
11-29
Product Customization
Customize a 1350 OMS Component while Other Components Are Running ............................................. 11-34
11-34
Perform a Manual Customization/De-customization (without using the Install Wizard) .......................... 11-36
11-36
....................................................................................................................................................................................................................................
viii 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Contents
....................................................................................................................................................................................................................................
Work Arounds for the MS-GUI ...................................................................................................................................... 11-59
11-59
A List of Abbreviations
Index
....................................................................................................................................................................................................................................
1350 OMS ix
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Contents
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
x 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
List of tables
....................................................................................................................................................................................................................................
1350 OMS xi
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
List of tables
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xii 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
About this document
About this document
Purpose
This preface provides an overview of this information product (IP), which is the 1350
OMS Administration Guide, Vol 1: Common Tools and Processes.
The purpose of the 1350 OMS Administration Guide, Vol 1: Common Tools and Processes
is to explain to system and network administrators how to administer and to maintain the
1350 OMS 9.5.
Safety information
This document does not contain any safety information (cautions or warnings) because
the 1350 OMS is a software product.
Important! When working with any hardware that is associated with any piece of
software, always refer to the safety information that the hardware manufacturer provides
for that particular piece of hardware. For example, when working with an HP® server,
refer to safety information that is provided in the HP® documentation for that server.
When working with any Alcatel-Lucent network element, refer to safety information that
is provided in the Alcatel-Lucent documentation for that particular NE.
Intended audience
The 1350 OMS Administration Guide, Vol 1: Common Tools and Processes is written
primarily for operations personnel who administer and maintain the 1350 OMS. This
document can be used by anyone who needs specific administration information about the
features, applications, and operations of the 1350 OMS. These people are you, its users.
...................................................................................................................................................................................................................................
1350 OMS xiii
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
About this document
....................................................................................................................................................................................................................................
Conceptual and task content
In the broadest sense, this document contains the following types of content:
• Conceptual content, which is background information, is given so users can better
understand the tasks that must be performed. The presentation of conceptual
information varies according to the topic being explained—sections, subsections,
tables, figures, and screen captures can be commonly found.
• Task content, which includes step-by-step instructions, is provided so users can
administer, provision, and maintain the system. The task information is typically
presented as series of tasks that follows the conceptual information.
The conceptual information complements and enhances the step-by-step instructions that
are found in each task. To optimize the use of the conceptual and task content, users
should consider the following:
• The conceptual information should be used to broaden your general knowledge of the
network management system. It is best if you read all conceptual information and
have a good understanding of the concepts being presented before undertaking the
step-by-step instructions given in any task.
• The conceptual and task portions of the document have extensive hyperlinks. Use
these links to toggle between the two types of information presented so you can
access all pertinent information related to particular concepts and tasks.
• The task information is based on a user needs analysis that has been performed for
each management system user job; therefore, use the task information to get the job at
hand done quickly and with minimal system impact.
....................................................................................................................................................................................................................................
xiv 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
About this document
....................................................................................................................................................................................................................................
skipped and the task can still be completed successfully. A task is considered to be
completed when all of its steps are completed and when the wording End of Steps
appears.
Many times, the management system affords users with multiple ways to accomplish the
same task. In these instances, this type of task gives the user several Methods of how to
accomplish the same set of steps successfully.
....................................................................................................................................................................................................................................
1350 OMS xv
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
About this document
....................................................................................................................................................................................................................................
Technical content
In general, the technical content in this document is augmented by technical content that
is provided in other documents in this documentation set and/or in the document set of the
particular network element (NE ) or piece of hardware in the network configuration. It is
the user's responsibility to read all pertinent material in all documentation sets in order to
understand a particular concept or procedure and/or to implement the procedure in his or
her working environment.
This document contains information on the complete line of NEs that the 1350 OMS
supports. Each release of the 1350 OMS and its applications supports certain NEs within
the Alcatel-Lucent family of optical NEs. Mention of NEs or specific NE features in the
text of this document, or any document in the 1350 OMS documentation set, that are not
supported in this particular product release can apply to prior or future product releases.
Such material may not be currently visible or operable on the GUI and/or the server and
has been added only as a convenience for our customers. This material is subject to
change. For a list of NEs that are supported in the 1350 OMS 9.5, contact your
Alcatel-Lucent local customer service support team.
This document, or any document in the 1350 OMS documentation set, may contain
information that is related to features, service packs (SPs), maintenance releases, or other
updates that our product and its applications supported in prior releases or is to support in
the near future. This material may not be visible or operable on the supported servers
and/or GUI, and has been added only as a convenience for our customers. This material is
subject to change. For a list of all supported features for a particular release, contact your
Alcatel-Lucent local customer service support team.
Treatment of terms
A term that is presented in the text of this document, along with any used abbreviation for
the term, is typically defined where the term is initially introduced.
Many of the more generic terms that are defined in this document, along with the terms
that are defined in other documents in this documentation set, are also defined in the
Glossary, which is part of the 1350 OMS Getting Started Guide. We encourage our users
to rely on the Glossary for a comprehensive set of terms and any abbreviations of the
terms.
....................................................................................................................................................................................................................................
xvi 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
About this document
....................................................................................................................................................................................................................................
Related documentation
The following documents are related to the 1350 OMS Administration Guide, Vol 1:
Common Tools and Processes, 9.5:
1. The 1350 OMS Installation Guide (8DG42146MAAA) explains how to perform the
installation of the 1350 OMS and its components.
2. The 1350 OMS Getting Started Guide (8DG42146AAAA) explains the look-and-feel
of the 1350 OMS user and administration GUIs to new users. This document contains
a complete explanation of the 1350 OMS information product set and a glossary of
terms that is applicable to the documentation set.
3. The 1350 OMS Administration Guide (8DG42146LAAA) explains how to use the
tools and the administration GUIs to administer and maintain the element
management layer, network management layer, and service management layer of the
1350 OMS.
This document consists of the following volumes:
• The 1350 OMS Administration Guide, Vol 1: Common Tools and Processes
(8DG42146LAAA-Vol1) explains how to administer and maintain the common
tools and processes that are associated with the 1350 OMS.
• The 1350 OMS Administration Guide, Vol 2: Common GUI Functions
(8DG42146LAAA-Vol2) explains how to administer and maintain the common
administration GUIs that are associated with the 1350 OMS.
4. The 1350 OMS EML Guide (8DG42146BAAA) explains how to administer and
provision the 1350 OMS EML application of the 1350 OMS, which is the element
management layer of the 1350 OMS.
5. The 1350 OMS PKT Guide (8DG42146DAAA) explains how to administer and
provision the Packet (PKT) application of the 1350 OMS that provides Ethernet
network management layer support.
6. The 1350 OMS SDH Guide (8DG42146CAAA) explains how to administer and
provision the Synchronous Digital Hierarchy (SDH) network management layer of the
1350 OMS.
7. The 1350 OMS WDM Guide (8DG42146QAAA) explains how to administer and
provision the 1350 OMS WDM, which provides the Wavelength Division
Multiplexing (WDM) and Dense Wavelength Division Multiplexing (DWDM)
network management layer for the 1350 OMS.
8. The 1350 OMS Service Assurance Guide (8DG42146FAAA) explains alarm
management and performance monitoring for the 1350 OMS.
9. 1350 OMS CLI Reference (8DG42146KAAA) provides detailed reference material on
the Command Line Interface for the advanced user of the 1350 OMS.
10. The 1350 OMS eOMS Guide explains how to administer and provision the eOMS.
....................................................................................................................................................................................................................................
1350 OMS xvii
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
About this document
....................................................................................................................................................................................................................................
The document consists of the following volumes:
• The 1350 OMS eOMS Guide, Vol 1: Getting Started (8DG42146RAAA-Vol1)
explains the look-and-feel of the1350 OMS eOMS GUI. In addition, this
document contains a glossary of terms for the 1350 OMS eOMS set of documents.
• The 1350 OMS eOMS Guide, Vol 2: Administration (8DG42146RAAA-Vol2)
explains how to administer the 1350 OMS eOMS.
• The 1350 OMS eOMS Guide, Vol 3: Network Element Management
(8DG42146RAAA-Vol3) explains how to use the 1350 OMS eOMS to provision
and manage network elements.
• The 1350 OMS eOMS Guide, Vol 4: Connection Management (8DG42146RAAA-
Vol4) explains how to provision and manage connections in the 1350 OMS eOMS
environment of the 1350 OMS.
• The 1350 OMS eOMS Guide, Vol 5: Ethernet Management (8DG42146RAAA-
Vol5) explains how to use the Ethernet Management feature to provision and
manage Ethernet connections in the 1350 OMS eOMS environment of the 1350
OMS.
• The 1350 OMS eOMS Guide, Vol 6: Service Assurance (8DG42146RAAA-Vol6)
explains how to manage and interpret fault and performance monitoring
information that is collected from the 1350 OMS eOMS environment of the 1350
OMS.
The 1350 OMS 9.5 also supports modules for system resiliency and northbound
communication. These modules are explained in the following documents:
• The 1350 OMS HA Guide (8DG42146GAAA) explains how to install, administer, and
use the High Availability feature.
• The 1350 OMS OI Guide (8DG42146HAAA) explains how to install, administer, and
use the Open Interfaces that are supported for the 1350 OMS.
In addition, the 1350 OMS 9.5 also supports migration activities with related
documentation. Contact your Alcatel-Lucent local customer service support team for
additional details.
Document formats
This document is available for use in HTML format and PDF.
The on-line HTML version of the document has a search capability, a table of contents in
the front matter of the document, a partial table of contents in each chapter, and an index.
The PDF version can be viewed on-line; or it, or portions of it, can be printed locally at
the user's discretion.
On-line help
The 1350 OMS help systems are designed to consider the task that the user is performing
and to help the user complete the task.
....................................................................................................................................................................................................................................
xviii 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
About this document
....................................................................................................................................................................................................................................
Contact sensitive help, which defines many GUI fields, is available; and other types of
help can be accessed from the GUI menu.
Ordering information
The entire document set that supports the Alcatel-Lucent 1350 OMS 9.5 release can be
ordered on CD-ROM. The ordering number for this CD-ROM is 8DG42147AAAA. The
ordering number for this particular document is 8DG42146LAAA-Vol1. Contact your
local Alcatel-Lucent local customer service support team for details.
In addition, to order the 1350 OMS and/or any of its applications, add-on features or
upgrades, contact your local Alcatel-Lucent local customer service support team.
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatel-
lucent.com/comments/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
....................................................................................................................................................................................................................................
1350 OMS xix
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
About this document
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
xx 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
1 1roduct and
P
Administration Overview
Overview
Purpose
This chapter provides an overview of the 1350 OMS and the system administration
functions provided to maintain the 1350 OMS applications.
Contents
...................................................................................................................................................................................................................................
1350 OMS 1-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Product and Administration Overview 1350 OMS Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Product and Administration Overview 1350 OMS Overview
....................................................................................................................................................................................................................................
Refer to the following documents and contact your Alcatel-Lucent local customer service
support team for additional details:
• 1350 OMS EML Guide
• 1350 OMS Service Assurance Guide
....................................................................................................................................................................................................................................
1350 OMS 1-3
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Product and Administration Overview 1350 OMS Overview
....................................................................................................................................................................................................................................
For 1350 OMS support of WDM and DWDM in a legacy system, refer to “Legacy
management and NE support” (p. 1-4) for details.
....................................................................................................................................................................................................................................
1350 OMS supported NEs
The 1350 OMS supports the Alcatel-Lucent family of optical network elements (NEs). To
accommodate the world of optical transmission standards, these NEs operate using
different transport structures and they support different native command languages.
Contact your local customer support team for a list of NEs that are supported by the 1350
OMS and its particular applications.
Important! Each release of the 1350 OMS and its applications supports certain NEs
within the Alcatel-Lucent family of optical NEs. Mention of NEs or specific NE features
in the text of this document, or any document in the 1350 OMS documentation set, that
are not supported in this particular product release can apply to prior or future product
releases. Such material may not be currently visible or operable on the GUI and/or the
server and has been added only as a convenience for our customers. This material is
subject to change. For a list of NEs that are supported in the 1350 OMS 9.5, contact your
Alcatel-Lucent local customer service support team.
....................................................................................................................................................................................................................................
1350 OMS 1-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Product and Administration Overview 1350 OMS Modules for System Resiliency and Northbound
Communication
....................................................................................................................................................................................................................................
1350 OMS OI
The 1350 OMS OI software package is installed on top of an already installed and
configured MW-INT platform and independently of any other application such as the
1350 OMS SDH, 1350 OMS PKT, or 1350 OMS WDM any element manager such as the
1350 OMS EML or 1350 OMS eOMS.
The 1350 OMS OI enables the 1350 OMS applications to export or import data to
multiple external operation systems (OSs). The 1350 OMS OI is a flexible, powerful, and
effective set of generic OS-to-OS interfaces (GENOS) that allow an external OS to
synchronize alarms, performance monitoring, network inventory, and remote inventory
data with any of the 1350 OMS applications.
The 1350 OMS OI is explained in detail in the 1350 OMS OI Guide (8DG42146HAAA).
This document includes installation, administration, and user information for the Open
Interfaces (OIs) that are supported for the 1350 OMS.
Contact your Alcatel-Lucent local customer service support team for additional details.
....................................................................................................................................................................................................................................
1-6 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Product and Administration Overview ANTP
....................................................................................................................................................................................................................................
ANTP
ANTP Overview
ANTP is an Alcatel-Lucent proprietary network time protocol (NTP) that enables a
precise, real-time clock alignment between the NEs and a reference clock source, such as
an ANTP server. ANTP is based on an algorithm that NTP implements and uses in the
UNIX® environment.
While NTP functions in TCP/IP environment, ANTP protocol is based on OSI layer 3
(Connectionless Network Protocol, or CLNP) communication services. To synchronize
the NE and the reference source, modifications in the interface and packet format of
standard NTP product enable it to be plugged on top of CLNP.
ANTP is based on a client-server paradigm. The NE functions as the client, while the
ANTP server is typically located on the network manager. The client (the NE)
periodically queries the server to discover the current time and date on the server. This
periodic query enables round trips delays and average statistical values to be calculated
for the best real-time alignment of the client (the NE) and server.
....................................................................................................................................................................................................................................
1350 OMS 1-7
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Product and Administration Overview Common Security and Access
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1-8 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Product and Administration Overview Common Security and Access
....................................................................................................................................................................................................................................
System-wide OA&M security
The 1350 OMS affords a single backup and restore capability for all data domains that are
associated with the core applications. In addition, the system supports a central start/stop
of the entire platform, one embedded component, or one process group.
For Disaster Recovery configurations, a system backup facility is available if the security
of a system has been compromised and recovery to a secure state is needed.
....................................................................................................................................................................................................................................
1350 OMS 1-9
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Product and Administration Overview System Administrator Responsibilities
....................................................................................................................................................................................................................................
Application management
The system administrator is responsible for managing the 1350 OMS and its applications
and keeping the HP-UX OS up and running, which includes the following:
• Process monitoring and configuration
• Logs management
• Trace management
• Backup and restore operations
• NE maintenance including software downloads and saving TPs
• Reconfigurations (stack and processes)
Preventative Maintenance
The system administrator is responsible for preventative maintenance of the 1350 OMS
and its applications, which includes the following:
• Minimize the consequences of hardware and software failures
• Avoid full file systems
Corrective Maintenance
The system administrator is responsible for corrective maintenance of the 1350 OMS and
its applications, which includes the following:
• Power supplies
• Full file systems
• Hardware failures (disk crashes, SCSI errors)
• Software failures (Panix UNIX® operating system, application bugs)
....................................................................................................................................................................................................................................
1-10 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
2 2 pplications and Their
A
Instances
Overview
Purpose
This chapter provides the administrator with the conceptual information and the
associated tasks that pertain to the instances of a particular 1350 OMS application.
Contents
...................................................................................................................................................................................................................................
1350 OMS 2-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Applications and Their Instances Instance Overview
....................................................................................................................................................................................................................................
Instance Overview
Instance definition
The 1350 OMS supports the 1350 OMS PKT, 1350 OMS SDH, and 1350 OMS WDM
applications, along with the 1350 OMS eOMS and 1350 OMS EML element level
management systems (EMLs). Each single running occurrence of any of these
applications or EMLs that is installed and customized in the 1350 OMS management
system is referred to as an instance.
The MW-INT, which is the Middleware Interface, manages each application or EML
instance.
Instance format
A single running occurrence of an application or EML is an instance. Multiple instances
of an application or EML mean that the application or EML has been loaded several
times. In the 1350 OMS, an instance of an application or EML has this format:
<Application_Instance>
Where:
Application is the supported 1350 OMS application, which can be the 1350 OMS PKT,
1350 OMS SDH, or 1350 OMS WDM applications or the 1350 OMS eOMS or 1350
OMS EML EMLs.
Examples:
Examples of instance names could be the following:
SDH_1-1.0
EOMS_2-5.6
EML_2-4.1
PKT_1-8.1
....................................................................................................................................................................................................................................
2-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Applications and Their Instances Instance Overview
....................................................................................................................................................................................................................................
Types of instances
The 1350 OMS supports the following types of instances:
• A Master instance is that instance of an application that supplies all data concerning
that application.
• A Client instance is that instance of an application that is requesting all data
concerning the application from the master instance.
When configuring a 1350 OMS application, that configuration must be created only on
Master instances. The configuration is not required on client instances.
Related tasks
The following tasks are related to instances:
• “Remove an Instance of an Application” (p. 2-4)
• “Free System Resources Used by an Application Instance” (p. 2-6)
To install an instance of an application, refer to the 1350 OMS Installation Guide.
....................................................................................................................................................................................................................................
1350 OMS 2-3
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Applications and Their Instances Remove an Instance of an Application
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Instance Overview” (p. 2-2)
For details about how to install an instance of an application, refer to the 1350 OMS
Installation Guide.
Task
Complete the following steps to remove the instance of an application.
...................................................................................................................................................................................................
1 From the Web portal, follow this path to stop the application by selecting the name of the
application instance.
Actions > Stop > Selected item
Result: The application instance is stopped.
...................................................................................................................................................................................................
3 Log in as root.
...................................................................................................................................................................................................
4 Enter the following command line to remove/decustomize the instance from the
MW-INT:
…,root> /alcatel/Kernel/script/Decustom <Application_Instance>
Example:
/alcatel/Kernel/script/Decustom PKT 1-9.5
The MW-INT no longer manages this instance of the 1350 OMS PKT named PKT 1-9.5.
....................................................................................................................................................................................................................................
2-4 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Applications and Their Instances Remove an Instance of an Application
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 Enter the following command lines to remove all files that are associated with the
application instance:
…,root> cd /usr/Systems [Enter]
…,root> rm -Rf <Application_Instance>/* [Enter]
…,root> rm -f /alcatel/BackupArea/<Application_Instance> [Enter]
…,root> rm -f /alcatel/MirrorArea/<Application_Instance> [Enter]
...................................................................................................................................................................................................
6 Enter the following command lines to kill any and all process that belong to the
application or the 1350 OMS (alcatel) user:
…,root> ps -efa | grep <application user> [Enter]
Enter the following command to kill all process numbers that the previous command
listed:
…,root> kill -<process number> [Enter]
…,root> ps -efa | grep alcatel [Enter]
Carefully identify those processes that belong to the particular application that is to be
removed. Enter the following command to kill all process numbers that the previous
command listed:
…,root> kill -<process number> [Enter]
...................................................................................................................................................................................................
7 If a new release of the application is to be installed, all current packages for the release
must be removed.
First, enter the following command lines to remove the remaining directories for NMS,
NMA, and NMC:
…,root> cd /alcatel/<release number>/NMS [Enter]
…,root> rm -rf <application> [Enter]
…,root> cd /alcatel/<release>/NMA [Enter]
…,root> rm -rf <application>*/ <release> [Enter]
On the master workstation only, enter the following commands:
…,root> cd /alcatel/<release>/NMC [Enter]
…,root> rm -rf TAO_INT/<release> [Enter]
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 2-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Applications and Their Instances Free System Resources Used by an Application Instance
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Instance Overview” (p. 2-2)
For details about how to install an instance of an application, refer to the 1350 OMS
Installation Guide.
Task
Complete the following steps to free the system resources application instance uses.
...................................................................................................................................................................................................
Remove INSTANCE
....................................................................................................................................................................................................................................
2-6 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Applications and Their Instances Free System Resources Used by an Application Instance
....................................................................................................................................................................................................................................
Item SWP Name SWP Version INSTANCE Number INSTANCE
Dimension
---- --------------- ----------- --------------- --------------------
1 <App Name> <Release> 1 <Application>_IM_Medium
Enter 'q' to Quit, 'd' to Display again or the Item Number :
...................................................................................................................................................................................................
3 Select the number of the particular application instance to be removed and press Enter.
<application instance number> [Enter]
Result: The SWP outputs a display that is similar to the following:
4 If the number that represents the application instance to be removed is correct, enter y for
yes and press Enter.
y [Enter]
Result: The SWP outputs a display that is similar to the following:
5 Press Enter.
Press Enter again.
[Enter] [Enter]
Result: The SWP main menu outputs its main menu again.
...................................................................................................................................................................................................
6 Select a to Apply:
a [Enter]
Result: The SWP begins the removal. As the logical file system is modified, the
workstation reboots.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 2-7
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Applications and Their Instances Free System Resources Used by an Application Instance
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
2-8 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
3 Configurations
3
Overview
Purpose
This chapter provides the administrator with the conceptual information and the
associated tasks that pertain to the configuration of the overall 1350 OMS.
Contents
...................................................................................................................................................................................................................................
1350 OMS 3-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Configurations Configuration Preparation
....................................................................................................................................................................................................................................
Configuration Preparation
Configuration process
The installed TMN system applications must be configured to run properly; and to run
properly, the following must be created:
• Configuration files
• Databases
The configuration must be created only on master systems. The configuration is not
required on client systems.
....................................................................................................................................................................................................................................
3-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Configurations Configuration Preparation
....................................................................................................................................................................................................................................
Master and client integration
If any application client instances exist and the 1350 OMS SDH is not installed, the 1350
OMS EML clients must be integrated with their master. Refer to the for details.
....................................................................................................................................................................................................................................
1350 OMS 3-3
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Configurations 1350 OMS EML IP Configuration
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
3-4 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Configurations Static Routing Configurations
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 3-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Configurations Static Routing Configurations
....................................................................................................................................................................................................................................
Important! Remember to add a new routing destination to the routing table for each
new network defined for the ISA board. (Edit the /etc/rc.config.d/netconf file.)
IP address = 10.61.4.33
Logical AND'd
Netmask = 255.255.0.0
----------------------------
network = 10.61.0.0
The configuration is created by defining a GNE IP address (10.3.7.6) as a gateway to
reach the ISA board (IP address = 10.61.4.33), with following command:
..,sys,root # route add network 10.61.0.0 netmask 255.255.0.0
10.3.7.6 1 [Enter]
Check network connectivity by executing the ping command from the 1350 OMS EML
master system to the ISA board (IP address = 10.61.4.33):
..,sys,root # ping 10.61.4.33 64 10 [Enter]
Use the netstat -r command to verify the routing table contents.
When the correct configuration is reached, add the proper configuration lines to the
/etc/rc.config.d/netconf file.
Note: when the gateway GNE fails, the ISA board will become unreachable in this
configuration. To recover, you must modify the routing table to remove the route from
the failed GNE (IP address 10.3.7.6) and to set up a new route from an alternative
GNE (for example, IP address 10.3.7.7).
....................................................................................................................................................................................................................................
..,sys,root # route add 10.61.0.0 netmask 255.255.0.0 10.2.1.6 1
[Enter]
Check the network connectivity by executing a ping command from the 1350 OMS EML
client to the ISA board:
..,sys,root # ping 10.61.4.33 64 10 [Enter]
Important! The ping command can fail because the 1350 OMS EML master system is
not yet configured to forward the packages.
When the right configuration is reached, add the following configuration lines to
the/etc/rc.config.d/netconf file:
..,sys,root # vi /etc/rc.config.d/netconf [Enter]
Type G and insert the following lines:
....................................................................................................................................................................................................................................
1350 OMS 3-7
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Configurations Routing Configurations for Client Applications
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
..,sys,root # route add <IP address lan1 SHM> <IP address lan0
SHM> 1 [Enter]
Enter the following command to verify the correct data entry on the 1350 OMS EML
client:
..,sys,root # ping <IP address lan1 SHM> [Enter]
When the right configuration is reached, add following lines to the
/etc/rc.config.d/netconf file so the information is saved after a system reboot:
..,sys,root # vi /etc/rc.config.d/netconf [Enter]
Type G and insert the following lines:
....................................................................................................................................................................................................................................
1350 OMS 3-9
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Configurations Multi-LAN Configurations
....................................................................................................................................................................................................................................
Multi-LAN Configurations
Overview
When the 1350 OMS EML is installed with HP-UX 11.11 (Hewlett Packard Unix) , all
LANs that are present in configuration—for both master and presentation systems—must
have an IP address, even if they are not being used.
The Retix Stack can be used on more than one LAN board. Every LAN board that is
being used must be configured with an appropriate TCP/IP address. Usually lan0 is
automatically configured by the HP-UX Operating System in the installation phases, but
other LANs must also be configured.
....................................................................................................................................................................................................................................
lan1: flags=963<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,MULTICAST
inet 192.1.1.1 netmask ffffff00 broadcast 192.1.1.255
..,sys,root # ifconfig lan2
lan2: flags=963<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,MULTICAST
inet 192.1.2.1 netmask ffffff00 broadcast 192.1.2.255
The IP belongs to this ISA board. For example: an ISA board with the IP address of
10.6.4.33 has the netmask of 255.255.0.0 and belongs to the network 10.6.0.0.
Where:
<mask> is the bit setting. If the bit is set to 1, the address part that is related to the
network is identified. If the bit is set to 0, the host address is identified.
<gateway> is the IP address of the router or ADM GNE that allows access to the
destination ISA board.
When the right configuration is reached, add following lines to the
/etc/rc.config.d/netconf file so the information is saved after a system reboot:
..,sys,root # vi /etc/rc.config.d/netconf [Enter]
Type G and insert the following lines:
....................................................................................................................................................................................................................................
1350 OMS 3-11
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Configurations Multi-LAN Configurations
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
3-12 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
4 Node Name Management
4
Overview
Purpose
This chapter provides the 1350 OMS network administrator with the conceptual
information and the associated tasks that pertain to the Node Name Management tool.
Contents
...................................................................................................................................................................................................................................
1350 OMS 4-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Node Name Management Tool
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-PUT = put network map 14-CHGATEWAY = change gateway
5-LIST = list network map 15-DNSADD = add to DNS
6-TOTALIGN = alignment each node 16-DNSCHANGE = change DNS
7-ACTALIGN = alignment a single node 17-DNSREMOVE = remove from DNS
8-GRPOPEN = open the current group
9-GRPIMPORT = import a remote group
10-GRPMERGE = merge two groups [0] - exit
Enter management option [0..17] :
The following menu options are available:
1. INIT is used to install the first 1350 OMS system in the entire group and to initialize
the Node Management persistent data to create the group to which group members are
to belong. Refer to the “Establish a Group and Initialize Node Name Management
Persistent Data” (p. 4-7) task.
2. ADD is used to add a new node/host and to enable the addition of any type of
node/host to the database. Standalone member nodes, external nodes, and cluster
nodes can be added. Refer to the “Add a New Member to the Group” (p. 4-9) and the
“Add a New External Node to the Group” (p. 4-12) tasks.
3. REMOVE is used to remove an existing node/host from the database. Current member
nodes, external nodes, and cluster nodes can be removed. Refer to the “Remove a
Member from a Group” (p. 4-14) task.
4. PUT is used to update the node name database of a remote group member, which can
be useful to align a node database.
5. LIST is used to view the database contents of the current or any other group member
node. Refer to the “List the Database Contents of a Group Member Node”
(p. 4-16) task.
6. TOTALIGN is used to align all group member nodes to one specified member. Refer to
the “Align All Group Member Nodes to a Specified Member Node” (p. 4-17) task.
7. ACTALIGN is used to align a specific group member node to another group member
node. Refer to the “Align One Group Member Node to Another Group Member
Node” (p. 4-18) task.
8. GRPOPEN is used to open groups for communication; that is, to enable communication
between distinct two groups to which both the current and the remote hosts belong.
Refer to the “Open Two Groups for Communication” (p. 4-20) task.
9. GRPIMPORT is used to import information between groups; that is, to include the
remote group descriptions on the current local group hosts. Refer to the “Import Node
Information Between Two Different Groups” (p. 4-22) task.
10. GRPMERGE is used to merge the nodes that belong to two groups into one group; that
is, to obtain a single group that contains the description of the nodes of both groups.
Refer to the “Merge Nodes in Two Groups into One Group” (p. 4-24) task.
11. CHIPADDR is used to change the Internet Protocol (IP) address of a system that is
configured with the Node Name Management tool. Refer to the “Change the IP
Address of a Remote Node” (p. 4-26) and “Change the IP Address of the
Current/Local Node” (p. 4-30) tasks.
....................................................................................................................................................................................................................................
4-4 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Node Name Management Tool
....................................................................................................................................................................................................................................
12. CHNODENAME is used to change the node/host name. Refer to the “Change the
Hostname of a Remote Node” (p. 4-34) and “Change the Hostname of the
Current/Local Node” (p. 4-37) tasks.
13. CHNETMASK is used to change the subnetwork mask of a group member host. Refer to
the “Change the Subnetwork Mask” (p. 4-41) task.
14. CHGATEWAY is used to change the current gateway Internet Protocol (IP) address and
host name of a group member host. Refer to the “Change the Gateway IP Address and
Hostname” (p. 4-42) task.
15. DNSADD is used to add a new server to the current Domain Name Service (DNS)
configuration of a group member host. Refer to the “Add a Server to the Current DNS
Configuration” (p. 4-44) task.
16. DNSCHANGE is used to modify the current Domain Name Service (DNS) configuration
of a group member host. Refer to the “Change a Server in the Current DNS
Configuration” (p. 4-46) task.
17. DNSREMOVE is used is used to remove an existing server from the current Domain
Name Service (DNS) configuration of a group member host. Refer to the “Remove a
Server from the Current DNS Configuration” (p. 4-48) task and the “Change a Server
in the Current DNS Configuration” (p. 4-46) task.
0 is used to exit the Node Name Management tool.
....................................................................................................................................................................................................................................
1350 OMS 4-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Node Name Management Tool
....................................................................................................................................................................................................................................
Node Name Management tool functional restrictions
The Node Name Management tool bases network communication on the MW-INT
Remotizer library, which means that the MW-INT has to be installed and customized
before it can correctly execute the Node Name Management tool. The Node Name
Management tool cannot be started before MW-INT installation and customization.
For the correct execution of the tool, the involved machines cannot differ more than 5
minutes in their system times.
Important! The relevant system time does not take into account time zones, so
administrators must check the time difference by entering the following command:
date -u
Refer to the 1350 OMS Installation Guide for more details on time synchronization.
....................................................................................................................................................................................................................................
4-6 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Establish a Group and Initialize Node Name Management
Persistent Data
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Node Name Management Tool” (p. 4-3)
Task
Complete the following steps to establish a group and to initialize the Node Name
Management persistent data.
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
3 Enter the number 1 to establish a group and to initialize the Node Name Management
persistent data.
Result: The group is created and the Node Name Management persistent data has
been initialized when the following message is displayed:
** MESSAGE: node "<hostname>" (<IP address>) initialized.
Press [Enter] to continue.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-7
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Establish a Group and Initialize Node Name Management
Persistent Data
....................................................................................................................................................................................................................................
To exit the tool, press 0, then press Enter.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-8 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Add a New Member to the Group
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Node Name Management Tool” (p. 4-3)
• “Establish a Group and Initialize Node Name Management Persistent Data”
(p. 4-7) task
....................................................................................................................................................................................................................................
1350 OMS 4-9
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Add a New Member to the Group
....................................................................................................................................................................................................................................
Important! When executing some commands, the following message might appear. If
it does appear, ignore it.
Redefining sub ConnectionManager::GetConnectionPort at /
alcatel/Kernel/lib/lib_perl/Remotizer.pm line 695
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
5 Enter the hostname and IP address of the new remote member. Wait until the tool
completes execution.
Result: The new group member has been added to the group and is known to all other
group members.
...................................................................................................................................................................................................
7 Go to “Task 2: Make the New Member Join the Group” (p. 4-11).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-10 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Add a New Member to the Group
....................................................................................................................................................................................................................................
Task 2: Make the New Member Join the Group
Complete the following steps to make the new member join the group.
...................................................................................................................................................................................................
1 Log in to the new member, which was formerly known as the remote member, as root.
Result: You now have superuser privileges.
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
3 Enter the number 2 to add the new group member to the group.
Result: The ADD - Management option is displayed.
...................................................................................................................................................................................................
5 Enter the hostname and IP address of the group member node. Wait until the tool
completes execution.
Result: The new node is now a member of the group.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-11
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Add a New External Node to the Group
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Node Name Management Tool” (p. 4-3)
• “Establish a Group and Initialize Node Name Management Persistent Data”
(p. 4-7) task
Task
Complete the following steps to add a new external node to the group.
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-12 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Add a New External Node to the Group
....................................................................................................................................................................................................................................
Result: The ADD - Management option is displayed.
...................................................................................................................................................................................................
5 Enter the hostname and IP address of the new host. Wait until the tool completes
execution.
Result: The new group member has been added to the group and is known to all
group members. Its information is automatically distributed to the entire group.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-13
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Remove a Member from a Group
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Node Name Management Tool” (p. 4-3)
Task
Complete the following steps to remove a member from a group.
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
4 Choose the menu option that is related to the action that you want to execute.
The Remove option enables you to remove the following:
• Remove Entry for the Current Node
Entries for the current node can be removed one of two ways:
1. One for the primary or physical hostname
2. Another for the virtual hostname for cluster configurations
• Remove Entry for Other Group Member
....................................................................................................................................................................................................................................
4-14 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Remove a Member from a Group
....................................................................................................................................................................................................................................
You can remove the entry for other group members for both the primary and virtual
hostname.
• Remove Entry for External Nodes
You can remove the entry for external nodes.
...................................................................................................................................................................................................
5 Enter the hostname and IP address of the node to be removed. Wait until the tool
completes execution.
Result: The node has been removed from the group and from all group member
databases.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-15
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management List the Database Contents of a Group Member Node
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Node Name Management Tool” (p. 4-3)
Task
Complete the following steps to list the database contents of a group member node.
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
3 Enter the number 5 to list the database contents of a group member node.
...................................................................................................................................................................................................
4 Enter the hostname and IP address of the node in which the database contents are to be
listed. Wait until the tool completes execution.
Result: The database contents of the specified node are displayed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-16 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Align All Group Member Nodes to a Specified Member Node
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Node Name Management Tool” (p. 4-3)
• “Align One Group Member Node to Another Group Member Node” (p. 4-18) task
Task
Complete the following steps to align all group member nodes to a specified node.
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
3 Enter the number 6 to align all group member nodes to a specified node.
...................................................................................................................................................................................................
4 Enter the hostname and IP address of the node to which all group members are to be
aligned. Wait until the tool completes execution.
Result: All group member nodes are now aligned with the specified node.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-17
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Align One Group Member Node to Another Group Member
Node
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Node Name Management Tool” (p. 4-3)
• “Align All Group Member Nodes to a Specified Member Node” (p. 4-17) task
Task
Complete the following steps to align one group member node to another group member
node.
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
3 Enter the number 7 to align one group member node to another group member node.
...................................................................................................................................................................................................
4 Enter the hostname and IP address of the two nodes to be aligned. Wait until the tool
completes execution.
Result: The two group member nodes are now aligned.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-18 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Align One Group Member Node to Another Group Member
Node
....................................................................................................................................................................................................................................
To exit the tool, press 0, then press Enter.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 4-19
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Open Two Groups for Communication
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Node Name Management Tool” (p. 4-3)
Task
Complete the following steps to open groups for communication.
...................................................................................................................................................................................................
1 Log in to the group member system that you want to enable a remote connection to as
root.
Result: You now have superuser privileges.
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
....................................................................................................................................................................................................................................
4-20 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Open Two Groups for Communication
....................................................................................................................................................................................................................................
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
4 Enter the hostname and IP address of the remote node to which you want to link. Wait
until the tool completes execution.
Result: The two groups to which the current and the remote nodes belong are now
linked and can communicate.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-21
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Import Node Information Between Two Different Groups
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Node Name Management Tool” (p. 4-3)
Task
Complete the following steps to import information between two different groups.
...................................................................................................................................................................................................
1 Complete the steps in the “Open Two Groups for Communication” (p. 4-20) task.
...................................................................................................................................................................................................
2 Log in to the group member system for which you want to configure the nodes of the
remote group as root.
Important! The group member system MUST BE the same remote node that you
specified during the “Open Two Groups for Communication” (p. 4-20) task.
....................................................................................................................................................................................................................................
4-22 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Import Node Information Between Two Different Groups
....................................................................................................................................................................................................................................
Result: You now have superuser privileges.
...................................................................................................................................................................................................
3 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
5 Enter the hostname and IP address of the remote node to which you want to link. Wait
until the tool completes execution.
Important! The hostname and IP address MUST BE the same remote node hostname
and IP address that you specified during the “Open Two Groups for Communication”
(p. 4-20) task.
Result: The configuration of each node member of a local group includes the
description of all node members of the remote group.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-23
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Merge Nodes in Two Groups into One Group
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Node Name Management Tool” (p. 4-3)
Task
Complete the following steps to merge the nodes that belong to two groups into one
group.
...................................................................................................................................................................................................
1 Complete the steps in the “Open Two Groups for Communication” (p. 4-20) task.
...................................................................................................................................................................................................
2 Log in to the group member system for which you want to configure the nodes of the
remote group as root.
Important! The group member system MUST BE the same remote node that you
specified during the “Open Two Groups for Communication” (p. 4-20) task.
....................................................................................................................................................................................................................................
4-24 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Merge Nodes in Two Groups into One Group
....................................................................................................................................................................................................................................
Result: You now have superuser privileges.
...................................................................................................................................................................................................
3 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
4 Enter the number 10 to merge the nodes that belong to two groups into one group.
...................................................................................................................................................................................................
5 Enter the hostname and IP address of the remote node to which you want to merge. Wait
until the tool completes execution.
Important! The hostname and IP address MUST BE that of the same remote node that
you specified during the “Open Two Groups for Communication” (p. 4-20) task.
Result: All node members of the two groups have been merged into a single group.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-25
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the IP Address of a Remote Node
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Node Name Management Tool” (p. 4-3)
• “Change the IP Address of the Current/Local Node” (p. 4-30)
....................................................................................................................................................................................................................................
4-26 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the IP Address of a Remote Node
....................................................................................................................................................................................................................................
To perform this type of change, execute two different tasks in the following order:
1. Change the IP address of a remote node; meaning, change the IP address on a remote
network node, but not the IP address of the node to which you are logged on. This
change is performed in this task.
2. Change the IP address of the current/local node; meaning, the IP address of the node
to which you are currently logged on. This change is performed in the “Change the IP
Address of the Current/Local Node” (p. 4-30) task.
Important! The change must be performed in this order. Communication cannot be
established again unless both of these tasks are completed. In addition, before you
proceed with another set of tasks, verify that communication is once again established
between the nodes that have the new IP addresses and the remaining group members.
Task
Complete the following steps to change the IP address of a remote node; meaning, change
the IP address on a remote network node, but not the IP address of the node to which you
are logged on
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-27
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the IP Address of a Remote Node
....................................................................................................................................................................................................................................
Enter management option [0..2] :
...................................................................................................................................................................................................
4 Enter the number 2 to change the IP address of the remote member node.
Result: The tool begins to prompt you for the hostname, old IP address, new IP
address, and network ID of the remote member node/host.
...................................................................................................................................................................................................
5 Enter the hostname for the remote host/node at the following prompt:
Please insert the HOSTNAME for remote host :
<remote host/node name> [Enter]
Example:
hostc in “Node Name Management tool network example” (p. 4-6).
...................................................................................................................................................................................................
6 Enter the old IP address for the remote host/node at the following prompt:
Please insert the OLD IP ADDR. for remote host :
<old IP address of the remote host/node> [Enter]
Example:
192.202.21.8 in “Node Name Management tool network example” (p. 4-6).
...................................................................................................................................................................................................
7 Enter the new IP address for the remote host/node at the following prompt:
Please insert the NEW IP ADDR. for remote host :
<new IP address of the remote host/node> [Enter]
Example:
192.202.21.99 in “Node Name Management tool network example” (p. 4-6).
...................................................................................................................................................................................................
8 Enter the network ID for the remote host/node at the following prompt:
Please insert the NETWORK ID for remote host :
<LAN ID for the remote host/node> [Enter]
Example:
0=lan1, 1=lan1, ... in “Node Name Management tool network example” (p. 4-6).
Result: The tool prompts you to confirm your choices.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-28 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the IP Address of a Remote Node
....................................................................................................................................................................................................................................
Do you confirm the execution [Y/N - def.=Y]? : Y
Result: The tool outputs the following warning:
WAIT THE END OF THE ACTIVITY (DO NOT PRESS ANY KEY !!).
When the tool completes execution, it displays the following:
** MESSAGE: IP ad. of "<hostname>" (<current IP address>)
changed in <new IP address>. Press [Enter] to continue.
The IP address of the indicated node has been changed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-29
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the IP Address of the Current/Local Node
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Node Name Management Tool” (p. 4-3)
• “Change the IP Address of a Remote Node” (p. 4-26)
....................................................................................................................................................................................................................................
Important! The change must be performed in this order. Communication cannot be
established again unless both of these tasks are completed. In addition, before you
proceed with another set of tasks, verify that communication is once again established
between the nodes that have the new IP addresses and the remaining group members.
Task
Complete the following steps to change the IP address of the current/local node; meaning,
the IP address of the node to which you are currently logged on.
...................................................................................................................................................................................................
1 Complete the steps in the “Change the IP Address of a Remote Node” (p. 4-26) task.
...................................................................................................................................................................................................
3 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
5 Enter the number 1 to change the IP address on the current member node.
....................................................................................................................................................................................................................................
1350 OMS 4-31
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the IP Address of the Current/Local Node
....................................................................................................................................................................................................................................
Result: The tool begins to prompt you for the old IP address, new IP address, and
network ID of the current host/node.
...................................................................................................................................................................................................
6 Enter the old IP address for the current/local node at the following prompt:
Please insert the OLD IP ADDR. for local host :
<old IP address of the current/local host> [Enter]
Example:
192.202.21.8 in “Node Name Management tool network example” (p. 4-6).
...................................................................................................................................................................................................
7 Enter the new IP address for the current/local node at the following prompt:
Please insert the NEW IP ADDR. for local host :
<new IP address of the current/local host> [Enter]
Example:
192.202.21.99 in “Node Name Management tool network example” (p. 4-6).
...................................................................................................................................................................................................
8 Enter the network ID for the current/local node at the following prompt:
Please insert the NETWORK ID for local host :
<LAN ID for the current/local host> [Enter]
Example:
0=lan1, 1=lan1, ... in “Node Name Management tool network example” (p. 4-6).
Result: The tool prompts you to confirm your choices.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-32 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the IP Address of the Current/Local Node
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-33
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the Hostname of a Remote Node
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Node Name Management Tool” (p. 4-3)
• “Change the Hostname of the Current/Local Node” (p. 4-37)
....................................................................................................................................................................................................................................
4-34 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the Hostname of a Remote Node
....................................................................................................................................................................................................................................
Task
Complete the following steps to change the hostname of a remote node; meaning, change
the hostname on a remote network node, but not the hostname of the node to which you
are logged on
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
4 Enter the number 2 to change the hostname of the remote member node.
Result: The tool begins to prompt you for the old hostname, IP address, and new
hostname of the remote member node/host.
...................................................................................................................................................................................................
5 Enter the old hostname for the remote host/node at the following prompt:
Please insert the OLD HOSTNAME for remote host :
<old remote host/node name> [Enter]
Example:
....................................................................................................................................................................................................................................
1350 OMS 4-35
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the Hostname of a Remote Node
....................................................................................................................................................................................................................................
hostc in “Node Name Management tool network example” (p. 4-6).
...................................................................................................................................................................................................
6 Enter the IP address for the remote host/node at the following prompt:
Please insert the IP ADDR. for remote host :
<IP address of the old remote host/node> [Enter]
Example:
192.202.21.8 in “Node Name Management tool network example” (p. 4-6).
...................................................................................................................................................................................................
7 Enter the new hostname for the remote host/node at the following prompt:
Please insert the NEW HOSTNAME for local host :
<new hostname of the remote host/node> [Enter]
Example:
hostx in “Node Name Management tool network example” (p. 4-6).
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-36 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the Hostname of the Current/Local Node
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Node Name Management Tool” (p. 4-3)
• “Change the Hostname of a Remote Node” (p. 4-34)
....................................................................................................................................................................................................................................
1350 OMS 4-37
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the Hostname of the Current/Local Node
....................................................................................................................................................................................................................................
Task
Complete the following steps to change the hostname of the current/local node; meaning,
the hostname of the node to which you are currently logged on.
...................................................................................................................................................................................................
1 Complete the steps in the “Change the Hostname of a Remote Node” (p. 4-34) task.
...................................................................................................................................................................................................
3 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
5 Enter the number 1 to change the IP address on the current member node.
Result: The tool begins to prompt you for the new hostname of the current host/node.
...................................................................................................................................................................................................
6 Enter the new hostname for the current/local host at the following prompt:
Please insert the NEW HOSTNAME for local host :
<new hostname of the current/local host> [Enter]
Example:
....................................................................................................................................................................................................................................
4-38 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the Hostname of the Current/Local Node
....................................................................................................................................................................................................................................
hostx in “Node Name Management tool network example” (p. 4-6).
...................................................................................................................................................................................................
10 Enter the following command line to execute the ChangeHostName tool, which is run to
update the hostname in MW-INT environment (including the Kerberos database):
/alcatel/Kernel/etc/ChangeHostName.pl –hostname <new_hostname>
Example:
In the “Node Name Management tool network example” (p. 4-6), <new_hostname>
would be hostx.
....................................................................................................................................................................................................................................
1350 OMS 4-39
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the Hostname of the Current/Local Node
....................................................................................................................................................................................................................................
Result: The execution of the ChangeHostName tool takes about 100 minutes. Do not
abort the tool.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
4-40 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the Subnetwork Mask
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Node Name Management Tool” (p. 4-3)
Task
Complete the following steps to change the subnetwork mask, which includes each
network interface that is configured.
...................................................................................................................................................................................................
1 Log in to the group node in which you want to change the subnetwork mask as root.
Result: You now have superuser privileges.
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
4 At the prompts, enter the new subnetwork mask and the LAN identification number
(0=lan0, 1=lan1, etc.). Wait until the tool completes execution.
Result: The new subnetwork mask is automatically activated for the current host.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-41
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the Gateway IP Address and Hostname
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Node Name Management Tool” (p. 4-3)
Task
Complete the following steps to change the IP address and hostname of a gateway on
each network interface that is configured.
...................................................................................................................................................................................................
1 Log in to the group node in which you want to change the subnetwork mask as root.
Result: You now have superuser privileges.
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
3 Enter the number 14 to change the IP address and hostname of a gateway on each
network interface that is configured.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-42 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change the Gateway IP Address and Hostname
....................................................................................................................................................................................................................................
Result: The new gateway, the IP address, and hostname are automatically activated
for the current host.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-43
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Add a Server to the Current DNS Configuration
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Node Name Management Tool” (p. 4-3)
Task
Complete the following steps to add a server in the current Domain Name System (DNS)
configuration for a group member host.
...................................................................................................................................................................................................
1 Log in to the group member node in which you want to add the DNS configuration
information as root.
Result: You now have superuser privileges.
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
4 Enter the hostname of the new DNS server at the following prompt:
Please insert the NEW DNS NAMESERVER HOSTNAME for local host :
<new DNS_hostname> <new DNS hostname> [Enter]
Important! You must know the name of the Domain Name Service and the nameserver.
...................................................................................................................................................................................................
5 Enter the IP address of the new DNS server at the following prompt:
....................................................................................................................................................................................................................................
4-44 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Add a Server to the Current DNS Configuration
....................................................................................................................................................................................................................................
Please insert the NEW DNS NAMESERVER IP ADDR for local host
<new_DNS IP address> [Enter]
Important! You must know the name of the Domain Name Service and the nameserver.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-45
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change a Server in the Current DNS Configuration
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Node Name Management Tool” (p. 4-3)
Task
Complete the following steps to modify the current Distributor Names Server (DNS)
configuration of a group member node.
...................................................................................................................................................................................................
1 Log in to the group member node where you want to change the DNS as root.
Result: You now have superuser privileges.
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
4 If you want to replace a DNS nameserver that is currently configured, enter the current
name of the DNS nameserver at the following prompt:
current DNS nameserver name <current DNS nameserver> [Enter]
....................................................................................................................................................................................................................................
4-46 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Change a Server in the Current DNS Configuration
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 If you want to replace a DNS nameserver that is currently configured, enter the new DNS
server at the following prompt:
new DNS nameserver name <new DNS nameserver> [Enter]
...................................................................................................................................................................................................
6 If you want to replace the DNS nameserver that is currently configured, enter its new IP
address at the following prompt:
new DNS nameserver IP addr
<IP address of the new DNS server host> [Enter]
...................................................................................................................................................................................................
7 Optional: To change the DNS local domain name, enter the new name of the local
domain at the following prompt or press Enter to maintain the current local domain
name:
new DNS local domain name
<new DNS local domain name>/<blank for the current search domain
list> [Enter]
...................................................................................................................................................................................................
8 Optional: To change the current search list, enter the new name of the search list at the
following prompt or press Enter to maintain the current search domain list:
search list for host-name lookup
<Name of the new serach list>/<blank for the current search
domain list> [Enter]
Wait until the tool completes execution.
Result: The new DNS configuration is automatically updated on the current member
node.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-47
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Remove a Server from the Current DNS Configuration
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Node Name Management Tool” (p. 4-3)
Task
Complete the following steps to remove a server from the current Distributor Names
Server (DNS) configuration.
...................................................................................................................................................................................................
1 Log in to the group member node where you want to remove the DNS nameserver as
root.
Result: You now have superuser privileges.
...................................................................................................................................................................................................
2 Enter the following command to run the Node Name Management tool:
...sys,root # scNMmng [Enter]
Result: The Network Management Nodes menu is displayed.
...................................................................................................................................................................................................
4 At the following prompts, enter the name of the DNS nameserver, which is currently
defined, that must be removed. (Note that the IP address is automatically displayed.)
Please insert the OLD DNS NAMESERVER HOSTNAME for local host:
<current DNS nameserver> [Enter]
Please insert the OLD DNS NAMESERVER IP ADDR. for local host:
<current DNS nameserver IP Address> [Enter]
....................................................................................................................................................................................................................................
4-48 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Remove a Server from the Current DNS Configuration
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 4-49
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Node Name Management Remove a Server from the Current DNS Configuration
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
4-50 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
5 S5ystem Backup and
Restore
Overview
Purpose
This chapter provides the 1350 OMS network administrator with the conceptual
information and the associated tasks that pertain to the backup and recovery of the 1350
OMS.
Contents
...................................................................................................................................................................................................................................
1350 OMS 5-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Backup and Restore Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
5-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore scbackup Overview
....................................................................................................................................................................................................................................
scbackup Overview
Backup objective
The backup procedure provides the administrator with an easy-to-use tool to store, on
tape or on a disk directory (local or remote mounted via Network File System - NFS), the
contents of the disks and the disk partitioning. The backup can be used if a disk failure
occurs or if data corruption becomes evident.
All backups are done using the scbackup command.
Backup tools
The backup procedure uses the following HP-UX® tools:
• fbackup, which is the backup tool that is included in the HP-UX® 11.31 Core.
• Ignite-UX, which is an add-on HP® tool for system installation services.
The versions of the tool that are certified are listed in the following table. The behavior of
scbackup is only guaranteed with the versions that are listed in the following table. Using
an older version of the tool can cause the backup to fail.
scbackup syntax
The command syntax of scbackup is as follows:
The following syntax is the typical format for a backup:
scbackup [-t <minutes>] [-a <dir_name>][-o <option list>] [-d] ARG...
The following syntax must be used when errors occur during the backup and the disk
mirroring must be recovered. The failed backup displays a warning message that this
syntax must be used:
scbackup -R
The following syntax is used to print out the procedure version or for help:
scbackup -v | -h
....................................................................................................................................................................................................................................
1350 OMS 5-3
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore scbackup Overview
....................................................................................................................................................................................................................................
Where:
• -t <minutes> specifies the time to wait in minutes to insert a new tape. If the time
expires, the backup is terminated. The default is an infinite waiting time. This option
is not allowed if the -a option is specified.
• -a <dir_ name> specifies that the output of the backup is to be generated in a file that
is stored on the associated disk directory (<dir_name>). This directory can be
mapped on a local disk or on a remote disk that has been mounted by the Network
File Server (NFS). The filename will have the format:
<hostname>_<yymmdd>-<time>_fbackup.out
For example: tlvsnk_101123-15.21_fbackup.out
Important! The disk directory must already be specified in /etc/fstab using the
following syntax:
<directory> <mount-point> <type> <options> <backup frequency> <pass
number> [<comment>]
Example for a local directory:
nodeName:/bck_dir /bck_dir nfs rw,nolargefiles 0 0
Example for a remote directory:
/dev/vg01/lvol3 /bck_dir vxfs nolargefiles,delaylog 0 0
For more information about the syntax of fstab, refer the fstab man page.
• -o <option_list> specifies the command options, which can be one of the following:
noIRT | IRTonly
online | offline
One option, or none, can be selected from each pair:
– noIRT skips the IRT production.
– IRTonly makes only an IRT version.
Note: If the -a option is specified and the creation of the IRT is required, use
either of the following:
scbackup -a <dir_name> ... .
Or:
scbackup a <dir_name> -o IRT only ...
The scbackup does not provide a bootable tape; but, it does provide a bootable
ISO image that can be used to reproduce the current system configuration. (This
bootable image must be burned on a DVD.) The image is stored on the associated
disk directory (<dir_name>) with a filename that has this format:
<hostmane>_<yymmdd>-<time>_image.iso
For example: tlvsnk-101123_15.21_image.iso
– online forces the online backup.
– offline forces the offline backup.
• -d, which is for test purposes only, specifies that a dry-run is to be done. When -d is
specified, most checks are performed, but a tape is not written to. The -d option is not
available if the -a option is specified.
....................................................................................................................................................................................................................................
5-4 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore scbackup Overview
....................................................................................................................................................................................................................................
• -R specifies that a recovery is to be done. When -R is specified, a recovery from
previous disk mirroring errors occurs.
• -v specifies that a version is to be done. It prints the procedure version and exits.
• -h specifies that a short help page is to be displayed. It displays the page and exits.
• ARG, which are the command arguments, are as follows:
system specifies a system disk backup. Local application instances are ignored.
<name_version_id> specifies an application instance backup. More than one instance
can be specified.
<no arguments> specifies a local disk backup. The entire contents of the local disk
are backed up.
For backups of application instances, the command format, in its simplest form, is the
following:
...,sys,root # scbackup instance_0 ... instance_n [Enter]
This command format produces a tape that contains the application instances that are
listed as command arguments. Each command argument has the following format:
<name>_<version>_<id>
The data for <name>_<version>_<id> can be retrieved with the following command:
scinstance -l
A shared instance backup is allowed only if the instance has status SMVI-SA, which is the
instance is active on its master system.
Example:
....sys,root # scbackup SDH_9.5.0_1 EML_9.5.0_1
This command line backs up two application instances; the tool automatically determines
if these instances should be backed up online or standard/offline.
....................................................................................................................................................................................................................................
1350 OMS 5-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Backup Strategies
....................................................................................................................................................................................................................................
Backup Strategies
Types of backups
The following types of backups can be done using scbackup:
• “Online backups” (p. 5-6)
• “Standard backups” (p. 5-6)
Online backups
Online backups are used to back up disks without having to shut down and reboot the
system.
Online backups are typically performed during these scenarios:
• When the logical volumes to be backed up are mirrored and in a stable state; and, the
administrator does not select the offline option.
During this scenario, the administrator must stop all applications, the logical volumes
are split, the backup is performed, and the administrator is advised that the
applications can be restarted.
• When the user has forced an online backup using the online option, which overrides
the default.
During this scenario, the administrator must stop all applications that involve the
particular logical volumes. The applications can be restarted when the backup is
completed.
Standard backups
Standard backups, which are also referred to as offline backups, require the system to be
shut down and a reboot to occur when backing up the local disks. All applications are
stopped, either by a system shutdown or by a command.
A standard backup is performed during the following scenarios:
• At least one of the logical volumes to be backed up is not mirrored or its mirroring
state is not stable and the administrator has not selected the online option.
• The administrator has forced the backup using the offline option to override the
default.
Instance backups
An instance backup is used to back up the Alcatel-Lucent TMN application data. All
application instances, local or shared, can be backed up. (Local instances can also be
backed up through the steps that are given in the “Run scbackup for a Local Disk or an
Application Instance Backup” (p. 5-24) task.)
....................................................................................................................................................................................................................................
5-6 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Backup Strategies
....................................................................................................................................................................................................................................
The steps to back up applications instances are those steps that are listed in “Run
scbackup for a Local Disk or an Application Instance Backup” (p. 5-24) task, unless the
following scenarios occur:
• An IRT is not made.
• The standard backup does not perform a system shutdown and reboot when the shared
instances have to be backed up. The backup only requires the applications to be shut
down while the backup is writing data to tape.
Refer to “scbackup syntax” (p. 5-3) for a detailed explanation of the command syntax to
use when backing up an application instance.
After the tool analyzes the options that are specified in the command line, it outputs a
display that is similar to the following:
....................................................................................................................................................................................................................................
1350 OMS 5-7
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Backup Tape Sets
....................................................................................................................................................................................................................................
Second set: the fbackup set containing the entire local disk
The second tape set is created by the fbackup tool and it contains the entire contents of
the local disk. This backup can be done online or offline. The tool can automatically
choose the most appropriate type of backup depending on the system configuration and
the status; however, the administrator can override any automatic choices.
Depending on the data size, more than one tape might be needed.
....................................................................................................................................................................................................................................
5-8 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Backup Tape Sets
....................................................................................................................................................................................................................................
Third set: the fbackup set for the shared application instances
The third, and optional, tape set is created by fbackup and it contains the contents of
disks where the shared application instances have been configured. This backup can be
done online or offline. The tool can automatically choose the most appropriate type of
backup depending on the system configuration and the status; however, the administrator
can override any automatic choices.
Depending on the data size, more than one tape might be needed.
....................................................................................................................................................................................................................................
1350 OMS 5-9
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Backup Restrictions and Requirements
....................................................................................................................................................................................................................................
Console restriction
fbackup is executed in single user mode during the HP-UX boot phase.
Important! If you shut off the console terminal or disconnect the Web console during
the execution of fbackup, fbackup is interrupted and the backup does not complete.
....................................................................................................................................................................................................................................
5-10 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Troubleshoot a Backup
....................................................................................................................................................................................................................................
Troubleshoot a Backup
Log files
The scbackup tool creates one log file that records all data that pertains to the entire
backup:
/SCINSTALL/log/scbackup.log
System crashes
If a system crash occurs during an online backup, the configuration of the original disk
must be recovered, which is done automatically at system start-up.
Time-out expiration
If the administrator started the backup with the -t option and does not fulfill a request for
a new tape cassette within the set time, the backup tool terminates and must be run again.
Should this scenario occur, backup can be run with the -o noIRT option, which skips the
creation of the IRT.
MERGE-DELETE problems
Any MERGE-DELETE problems are typically the cause of faulty disk mirroring. The
administrator should check the log file for errors and manually run the scbackup -R
command.
Login messages
If problems occur at the end of a standard/offline backup, the fbackup tool displays
warning or error messages upon login. The administrator should check both types of
messages in the /SCINSTALL/log/scbackup.log file to determine the nature of the message
and/or the potential problem.
....................................................................................................................................................................................................................................
1350 OMS 5-11
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Troubleshoot a Backup
....................................................................................................................................................................................................................................
After a backup on tape, the following warning message can be ignored:
WARNING: unable to read a volume header.
With Error messages, check the /SCINSTALL/log/scbackup.log to determine the cause of
the errors. The tape set is not useful and the backup must be rerun.
To clear the messages from being displayed, remove the
/var/adm/fbackfiles/fbackup.msg file.
....................................................................................................................................................................................................................................
5-12 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Restore and screstore
....................................................................................................................................................................................................................................
Restore phases
The restore consists of the following phases:
• The first phase uses the IRT tape set or ISO image, and it recreates the Logical
Volume Manager (LVM) disk configuration of the local disks that exists at backup
time. In addition, it installs a minimal operating system that allows the system to be
booted from disk. This phase destroys the existing content of the local disks.
• The second phase recovers the contents of the local disks, which are typically grouped
in the volume group vg00. The administrator must run the screstore tool to complete
this phase.
• The third, and optional phase, recreates the volume groups for the shared instances
and recovers data on external disks. The administrator must run the screstore tool to
complete this phase.
screstore syntax
The command syntax for screstore is the typical format for a backup:
screstore [-a <dir_name>] [ARG] ...
Where:
-a <dir_name> specifies that the input of restore is a file that is stored on the associated
disk directory (<dir_name>) with the following name:
<hostname>_<yymmdd>-<time>_fbackup.out
Example:
tlvsnk_101123-15.21_fbackup.out
-v prints the version of the tool.
-o displays a short help file.
[ARG] are the command arguments for the application instances.
Example:
...,sys,root # screstore SDH_9.5.0.1
If an argument is not specified, the contents of the entire backup tape or ISO image is
restored/recovered.
....................................................................................................................................................................................................................................
1350 OMS 5-13
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Restore and screstore
....................................................................................................................................................................................................................................
IRT recovery
Note: If you performed a backup on a directory disk (using the –a option with the
scbackup command), the IRT is a DVD that contains the bootable ISO image.
The recovery of the Ignite-UX Recovery Tape (IRT), includes the following activities,
which are performed by booting the HP Integrity system from the IRT:
• Reconfiguration all of the hard disks in use, exactly as they were, at backup time.
• Restoration of a minimum HP-UX® operating system on the hard disks so the
frecover tool can be run.
....................................................................................................................................................................................................................................
5-14 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Troubleshoot a Restore
....................................................................................................................................................................................................................................
Troubleshoot a Restore
IRT rebooting errors
If Ignite-UX encounters errors during the recovery, output similar to the following is
displayed:
....................................................................................................................................................................................................................................
1350 OMS 5-15
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Troubleshoot a Restore
....................................................................................................................................................................................................................................
The following is a useless error message regarding some scripts/tools that have failed.
This type of message should be ignored:
Console messages that are displayed during the reboot from the IRT
Because the IRT restores only a subset of entire HP-UX® operating system and nothing
of 1350 OMS application, errors can occur.
The following is a useless error message that occurs when the system is rebooted from the
restored disks. This type of message occurs because of the partial recovery that Ignite-UX
performs and because of the temporary inconsistency between the restored files and the
contents of /etc/inittab. The messages disappear after the recovery of the fbackup set;
and in general, output that is similar to the following display should be ignored:
....................................................................................................................................................................................................................................
5-16 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Troubleshoot a Restore
....................................................................................................................................................................................................................................
The source of the media must be checked.
• The IRT and fbackup media were produced at different times and with different
system configurations, which means that the administrator is trying to restore an
fbackup media on a system in which the disk configuration is different from the target
file system, on a system that is not available, or on a system that is not large enough to
perform the restore.
The validity of the media must be checked.
• The input media is correct, but something was modified during the Ignite-UX
recovery process (interactive restore installation), or after the successful Ignite-UX
recovery and before the screstore process.
If an inconsistency does occur, the screstore process must be stopped to determine and
correct the problem, then screstore must be rerun.
*************************************************************
WARNING: Current host is different from the one backed up.
Current host -> hosta
Backedup host -> hostb
*************************************************************
***************************************************
ERROR: Volume group name "<volume group name>"
present on tape but not defined on system
***************************************************
***************************************************
WARNING: Volume group name "<vg_name>"
is present on tape but not ACTIVATED on system
***************************************************
....................................................................................................................................................................................................................................
1350 OMS 5-17
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Troubleshoot a Restore
....................................................................................................................................................................................................................................
When this warning is displayed, the volume group must be activated with the vgchange
command:
vgchange -a y <Volume Group>
****************************************************
ERROR: Logical volume "<lv_name>"
present on tape but not defined on system
****************************************************
When the following error message is displayed, the logical volume must be mounted with
the mount <lv_name> <mount_point> command.
mount: /dev/vg00/lvol11 was either ignored or not found in /etc/
fstab
***************************************************
ERROR: Logical volume "<lv_name>"
has been created but not mounted on system
***************************************************
If the command succeeds, screstore must be rerun. If the command fails, the IRT and
fbackup input media must be verified for consistency.
******************************************************************
WARNING: Different mount points found for the Logical volume <lv_name>
actual mount point - > <act_mp>
tape mount point - > <tape_mp>
****************************************************************
******************************************************************
ERROR: Mount Point: <mount_point>
is not a directory
****************************************************************
....................................................................................................................................................................................................................................
5-18 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Troubleshoot a Restore
....................................................................................................................................................................................................................................
WARNING: The mount point...
When the following message is displayed, a nesting of the mount point directory has
occurred. You should have one or more empty directories; and if you do, you can proceed.
If you do not, check the contents of the directories.
******************************************************************
WARNING: Mount Point: <mount_point>
is not an empty directory
****************************************************************
******************************************************************
WARNING: The file system mount on <mount_point>
has not enough free space:
to recover the logical volume
actual free space - > 500 Mb
required space - > 550 Mb
*****************************************************************
....................................................................................................................................................................................................................................
1350 OMS 5-19
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Mirror Configurations
....................................................................................................................................................................................................................................
Mirror Configurations
The scmirrorfs tool
The scmirrorfs tool is used to assign and/or reassign disks for the mirror copy of data.
This tool requires the administrator to enter the device names of the primary disk and the
alternate disk that must be used to store the mirror copy of the data. Use of the scmirrorfs
tool can possibly change the configuration.
Disk requirements
The following disk requirements apply:
• The administrator must know the names of the primary and the alternate disks that are
to be used in the mirror configuration.
• The disks that belong to the mirror copy disk do not have to be physically identical to
the main disk set.
• The amount of space on both disks must be sufficient to store all of the logical volume
that is currently defined.
• The disks that belong to the mirror copy disk set should not share the same SCSI bus
as the main disk. When the configuration script recognizes that the disk that is being
added to the mirror copy is connected to a SCSI bus that is already in use for the main
disk set, output similar to the following is displayed:
WARNING: Controller disk already used in “Main path (pvg0)"
Do you want to choose another disk ?
To guarantee the machine functionality if the disk controller fails, you must to choose
another disk that belongs to another chain.
....................................................................................................................................................................................................................................
5-20 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run scdisk_read_check to Read and Check the Disk
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Backup and Restore Overview” (p. 5-2)
Task
Complete the following steps to run the scdisk_read_check tool, which reads and checks
the disk.
...................................................................................................................................................................................................
=><date/time stamp>
=>START: OSConf Disk Read check
--- Disk read check for Volume Group: /dev/vg00 ---
Note: record size is 64 MByte
<date/time stamp> Start read check of disk c2t5d0
Disk Size 8678 MByte (note: must be check 135 records)
135+1 records in
....................................................................................................................................................................................................................................
1350 OMS 5-21
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run scdisk_read_check to Read and Check the Disk
....................................................................................................................................................................................................................................
135+1 records out
real 8:28.0
user 0.0
sys 3.5
<date/time stamp> End successfully
=><date/time stamp>
=>END: OSConf Disk Read check
...,sys,root #
If the tool executes successfully, you can proceed with the backup.
Important! If the tool issues I/O errors or if it gets stopped (CPU activity does not
occur for the process), a hardware problem exists. Correct the problem before you
proceed with the backup.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-22 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Perform a Tape Check
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Backup and Restore Overview” (p. 5-2)
Task
Complete the following steps to perform a tape check.
...................................................................................................................................................................................................
3 Visually verify that the /dev/rmt exists and that it is not empty.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 5-23
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run scbackup for a Local Disk or an Application Instance
Backup
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Backup and Restore Overview” (p. 5-2)
• “Backup Restrictions and Requirements” (p. 5-10)
• “Troubleshoot a Backup” (p. 5-11)
• “Mirror Configurations” (p. 5-20)
....................................................................................................................................................................................................................................
5-24 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run scbackup for a Local Disk or an Application Instance
Backup
....................................................................................................................................................................................................................................
Task
Complete the following steps to run the scbackup tool using a tape as the output media.
...................................................................................................................................................................................................
4 If the IRT is to be created, enter the tape device that is to be used for writing the IRT and
press Enter, or press Enter to select the file that is displayed:
Enter tape device for Ignite <default=<tape device>>:
<tape device> [Enter]
....................................................................................................................................................................................................................................
1350 OMS 5-25
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run scbackup for a Local Disk or an Application Instance
Backup
....................................................................................................................................................................................................................................
Example:
Enter tape device for Ignite <default=<tape device>>:
/dev/rmt/0m [Enter]
Important! The tape device must be of type NO-REWIND. In addition, its name must be
in the format of the following:
/dev/rmt/<x>mn
Where: x is a digit from 0 to 9.
Result: The tool prompts you to mount a tape in the tape drive.
Please insert a tape labelled 'Ignite' into device <tape_
device>.
Press [Enter] when ready.
...................................................................................................................................................................................................
5 Mount an unprotected tape cassette and wait until the drive light stops blinking.
...................................................................................................................................................................................................
6 When the blinking light stops blinking and the device light becomes stable, press Enter to
create the IRT:
Enter
Result: The creation of the IRT can take up to 40 minutes. Any error that is detected
aborts the execution of the tool. The tool outputs the status of the execution on your
monitor.
When the IRT completes without errors, the following message is displayed:
**************************************************
Please, label the Ignite Recovery Tape as:
<host> - Ignite Bootable - <date> <time>
...................................................................................................................................................................................................
7 Enter the following command lines to print vital information regarding the contents of the
tape. This step is imperative because this information can be useful if a disk failure
occurs.
...,sys,root # vgdisplay -v [Enter]
...,sys,root # scextendfs -i [Enter]
....................................................................................................................................................................................................................................
5-26 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run scbackup for a Local Disk or an Application Instance
Backup
....................................................................................................................................................................................................................................
Result: The system outputs vital information regarding the contents of the tape.
...................................................................................................................................................................................................
8 Label the tape properly, remember the root password that was staved in the IRT, and store
the printout containing the output of the vgdisplay and scextendfs commands with the
tape.
Result: Once the tool completes the creation of the IRT, it prompts you for the
HP-UX® device file for the fbackup.
...................................................................................................................................................................................................
9 Enter the tape device that you want to use to back up the entire disk and press Enter, or
press Enter to select the file that is displayed:
Enter tape device for Fbackup <default=<tape_device>>:
<tape device> <Enter
Example:
Enter tape device for Fbackup <default=<tape device>>:
/dev/rmt/0m [Enter]
Important! The tape device must of type NO-REWIND. In addition, its name must be in
the format of the following:
/dev/rmt/<x>mn
Where: x is a digit from 0 to 9.
Result: The tool verifies that all logical volumes that are going to be backed up are
correctly mounted on the system. In addition, the tool determines if the system should
be backed up online or offline. The system choice can be overridden by using the
option -o. Note: the tool tries to guarantee the consistency of the backed up data; so,
we suggest that you do not override the system choice.
...................................................................................................................................................................................................
**************************************************
Please, label the tape volume(s) as:
<host> - Fbackup Volume i of <n>
<date/time stamp> - local full
***************************************************
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
5-28 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run scbackup Using a Disk Directory as the Supporting
Output Media
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Backup and Restore Overview” (p. 5-2)
Task
Use this task to use a disk directory as the output media when running scbackup
command.
...................................................................................................................................................................................................
2 Optional: To optimize the tool's behavior and to reduce execution time, use the
excluded-list file(s) to specify the application files and directories that are to be excluded
from the backup. The application files and the directories will be backed up by the
application specific tools.
You can have more than one excluded-list file; but, all of the excluded-list files have to be
stored in the /sbin/SC_ExcludeFiles directory, which is created automatically during the
1350OMS-MW_OS installation.
...................................................................................................................................................................................................
**************************************************
ISO Image creation: "/bck_test/tlvsnk-110728_14.52_image.iso"
**************************************************
Bootable ISO Image procedure ended
Press <Enter> to continue...
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
5-30 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run scbackup Using a Disk Directory as the Supporting
Output Media
....................................................................................................................................................................................................................................
Result: The tool continues to save the application files.
When the preliminary checks are finished, the following message is displayed:
********************************************************************
ATTENTION: You are going to perform the standard system backup, but
this requires a system SHUTDOWN-REBOOT.
*******************************************************************
********************************************************************
ATTENTION: It is better to stop applications before shutting down the system,
Please, do it before answering 'YES' next question.
*********************************************************************
WARNING: Answering "NO" to the following question, will terminate the backup
procedure.
Continue with system SHUTDOWN & REBOOT (y|n) ? :
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 5-31
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run scbackup Using a Disk Directory as the Supporting
Output Media
....................................................................................................................................................................................................................................
One of the copies of the logical volume is removed from the mirror and is used for the
backup. When the disk splitting is completed, the tool prompts you to restart the
applications. Upon backup completion, the logical volumes are automatically reduced;
that is, the disk copies are removed from the mirror system for the backup, they are put
back, and the mirror is restored to its normal state.
If disk splitting is not to occur, stop all applications and be present to answer all prompts
that the tool outputs. When the backup completes, the tool prompts you to restart the
applications.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
5-32 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Verify the Readability of the fbackup Tape
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Backup and Restore Overview” (p. 5-2)
• “Backup Restrictions and Requirements” (p. 5-10)
• “Troubleshoot a Backup” (p. 5-11)
Task
Complete the following verify the readability of the fbackup tape.
...................................................................................................................................................................................................
4 Repeat steps 2 and 3 for every tape that was made during the backup.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 5-33
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Boot from the IRT
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Backup and Restore Overview” (p. 5-2)
• “Restore and screstore” (p. 5-13)
• “Troubleshoot a Restore” (p. 5-15)
Task
Complete the following steps to boot from the IRT.
...................................................................................................................................................................................................
2 Connect a tape drive that is compatible with the IRT to the system.
...................................................................................................................................................................................................
6 Enter the following command to view the device where the IRT was inserted.
sea
....................................................................................................................................................................................................................................
5-34 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Boot from the IRT
....................................................................................................................................................................................................................................
Result: The system displays information that is similar to the following:
Path# Device Path (dec) Device Path (mnem) Device Type and Utilities Rev
----- ----------------- ------------------ ------------------------- ----
P0 0/0/2/0.0 ide.0 Random access media 1
IPL
P1 0/1/1/0.1 intscsia.1 Sequential access media 1
IPL
P2 0/1/1/0.0 intscsia.0 Random access media 1
IPL
P3 0/1/1/1.5 intscsib.5 Random access media 1
IPL
P4 0/1/1/1.4 intscsib.4 Random access media 1
IPL
P5 0/1/1/1.3 intscsib.3 Random access media 1
IPL
Important! A tape device is always referred to as Sequential access media. A DVD
device is always referred to as Ide.0.
...................................................................................................................................................................................................
7 Enter the following command to boot from the device where the IRT is inserted:
boot <device_path_number>
Where: device_path_number is the path number that corresponds to one of the device
types (tape or DVD) that is listed in the Results of Step 6.
Example:
boot P1
...................................................................................................................................................................................................
8 At the following prompt, enter N (for No) so you do not interact with the IPL:
Interact with IPL (Y, N or C) > N
Result: The machine begins to boot from the device where the IRT is inserted.
Output similar to the following is displayed:
HARD Booted
ISL Revision ......
ISL Booting hpux (;0) INSTALL
Boot
...: tape (...
If the boot starts correctly, the ISL prompt is not displayed after 3 minutes. Ignite-UX
performs the recovery of the LVM disk structure and the HP-UX® OS in a minimum
configuration. You do not have to enter any commands; you only must check the
output for error messages.
....................................................................................................................................................................................................................................
1350 OMS 5-35
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Boot from the IRT
....................................................................................................................................................................................................................................
The IRT reboots the system twice. The recovery from the IRT can take up to 90
minutes, depending on the system model. Wait until the end of the second reboot.
If the boot does not start successfully, go to “IRT rebooting errors” (p. 5-15).
If the machine does not reboot automatically, go to “No automatic reboot from the
IRT” (p. 5-15).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-36 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run screstore to Restore Data from the fbackup Media
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Backup and Restore Overview” (p. 5-2)
• “Restore and screstore” (p. 5-13)
• “Troubleshoot a Restore” (p. 5-15)
*****************************************************************************
NOTE: Restore device check issued some warnings.
Restoring from this <device> could result in a wrong system
Please, verify carefully each warning before answering
the following question.
*****************************************************************************
Do you want to continue with restore (y|n) ? :
Where: <device> will be:
• tape for an screstore from a tape device
• disk archive for restore from an ISO image file
Refer to “Troubleshoot a Restore” (p. 5-15) and analyze the warnings; and, if necessary,
correct any problems before you answer y to continue the restoration.
....................................................................................................................................................................................................................................
1350 OMS 5-37
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run screstore to Restore Data from the fbackup Media
....................................................................................................................................................................................................................................
Task 1: Using a Tape
Complete the following steps to run the screstore tool to restore data from the fbackup
tapes.
...................................................................................................................................................................................................
1 Log in as root using the same password that was active when the backup was done.
Result: You now have superuser privileges.
After restoring the IRT, only the system is restored, which means that not all of the
required files are currently available; therefore, messages such as the following are
displayed. Ignore these messages because they disappear when the restoration is
completed.
Cannot chdir to /var/news
cat: Cannot open /SCINSTALL/data/boot_version*: No such file
or directory
...................................................................................................................................................................................................
2 Optional: If you must complete any preliminary tasks on the system before you activate
the restore, create a command file called screstore_init in the SCINSTALL/etc directory
that can be executed before the frecover.
...................................................................................................................................................................................................
3 Enter the following command to invoke the screstore tool and to start the restoration:
..,sys,root # screstore [Enter]
Important! This command is shown in its simplest form. Refer to “screstore syntax”
(p. 5-13) for the complete syntax of this command.
Result: The tool prompts you to enter the file that has to be used for the restoration:
**************************************************
Selection of Tape device
Enter tape device for Frecover <default=<tape device>>
...................................................................................................................................................................................................
4 At the following prompt, enter the HP-UX® file that is associated with the tape device
that you want to use for the fbackup tape set and press Enter, or press Enter to select the
file that is displayed:
Enter tape device for Frecover <default=<tape device>>
<directory/filename> [Enter]
Example:
Enter tape device for Frecover <default=<tape device>>
/dev/rmt/0m [Enter]
....................................................................................................................................................................................................................................
5-38 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run screstore to Restore Data from the fbackup Media
....................................................................................................................................................................................................................................
Result: The tool prompts you to mount the first tape of the fbackup tape set.
...................................................................................................................................................................................................
5 Mount the first tape cassette into the tape device, wait until the tape device is ready, and
press Enter to start:
Enter
Result: The tool outputs the expected tape label and asks you to verify it to the tape
that you are have just mounted.
...................................................................................................................................................................................................
7 For an instance restore only, enter y when the tool outputs a display similar to the
following to create mount points:
8 If the tool determines that you must change the run level, stop all TMN applications and
specify y for yes when the tool prompts you to go to run level 3:
Are you ready, system go to run level 3 (y|n) ? : y
....................................................................................................................................................................................................................................
1350 OMS 5-39
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run screstore to Restore Data from the fbackup Media
....................................................................................................................................................................................................................................
Result: The recovery begins.
Important! Be present during this phase of the recovery because you might have to
load/remove tapes.
...................................................................................................................................................................................................
11 If you mounted the correct tape, the frecover has ended. See the Results in Step 12.
If you mounted the incorrect tape, mount the correct tape now (after the previous message
appears), and then press Enter. Go to Step 12.
...................................................................................................................................................................................................
12 If you initially mounted the incorrect tape and have since mounted the correct tape or if
you initially entered the correct tape, the frecover tool has ended.
....................................................................................................................................................................................................................................
5-40 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run screstore to Restore Data from the fbackup Media
....................................................................................................................................................................................................................................
Result: The frecover tool has ended successfully. If the system was mirrored at the
backup time, the procedure reminds you to rebuild the disk mirroring using the
scmirrorfs when ends.
...................................................................................................................................................................................................
15 At the following prompt, enter the grace time for the user's log off in minutes or press
Enter for an immediate shut down
Enter the grace time for user's logoff before shutting down or
press [Enter] for immediate shutdown
Grace time (in sec.) >
...................................................................................................................................................................................................
16 After the system restart, restore the Alcatel-Lucent TMN applications data following the
appropriate, if any, recovery procedure and you can start up all applications.
E...................................................................................................................................................................................................
N D O F S T E P S
2 Optional: If you must complete any preliminary tasks on the system before you activate
the restore, create a command file called screstore_init in the SCINSTALL/etc directory
that can be executed before the frecover.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 5-41
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run screstore to Restore Data from the fbackup Media
....................................................................................................................................................................................................................................
..,sys,root # screstore -a <directory> [Enter]
Where: <directory> is the path of the disk directory where is stored the ISO image file to
use as input for this tool.
Important! This command is shown in its simplest form. Refer to “screstore syntax”
(p. 5-13) for the complete syntax of this command.
Result: The tool outputs the expected tape label.
...................................................................................................................................................................................................
4 When the tool outputs the expected tape label, it then asks you to verify it to the tape that
you are have just mounted.
If the ISO image file labels match, enter y to continue:
Is the label OK (y|n) ? : y
If the ISO image file labels do not match, enter n to stop the restoration/recovery:
Is the label OK (y|n) ? : n
Result: The recovery procedure continues to check the tape consistency, volume
groups, and logical volumes that are to be restored. If any check fails and the error is
not recoverable, the tool aborts or displays a warning message. When all checks are
completed, the recovery procedure prompts you to continue.
When performing an instance restore, the tool checks the instances that are found on
the tape BEFORE it checks the volume groups. If the mount point for the file system
of an instance is not found in the system, the tool outputs a similar warning and asks
you if you want it to create the mount point. The tool outputs this type of message for
every missing mount point. If you are performing an instance restore, go to Step 5.
Important! Read the warning messages that the tool outputs during this phase and
answer y to continue only if you are sure that the warning messages are not applicable
to your configuration.
The frecover tool ends successfully. If the system was mirrored at the time of the
backup, the procedure reminds you to rebuild the disk mirroring using the scmirrorfs
when it ends.
...................................................................................................................................................................................................
5 For an instance restore only, enter y when the tool outputs a display similar to the
following to create mount points:
....................................................................................................................................................................................................................................
5-42 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run screstore to Restore Data from the fbackup Media
....................................................................................................................................................................................................................................
Result: The tool invokes the scextends routine, which detects the available hardware
and prompts you to create the instance volume group on an external disk device that it
discovers. If the choice that is discovered is suitable to you, answer y and scextendfs
continues to create the needed mount points.
...................................................................................................................................................................................................
8 At the following prompt, enter the grace time for the user's log off in minutes or press
Enter for an immediate shut down
Enter the grace time for user's logoff before shutting down or
press [Enter] for immediate shutdown
Grace time (in sec.) >
...................................................................................................................................................................................................
9 After the system restart, restore the Alcatel-Lucent TMN applications data following the
appropriate, if any, recovery procedure and you can start up all applications.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 5-43
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run the scmirrorfs Tool to Set Up the Mirrored Configuration
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Mirror Configurations” (p. 5-20)
• “Troubleshoot a Restore” (p. 5-15)
Task
Complete the following steps to set up the mirrored disk configuration.
...................................................................................................................................................................................................
1 Log in as root using the same password that was active when the backup was done.
Result: You now have superuser privileges.
...................................................................................................................................................................................................
=><date/time stamp>
=>START: OSConf File(s) System Mirroring
Hardware detection in progress, please wait ........
Total disk(s) found = 6
Total CDRoms found = 1
Press [Enter] to continue...
...................................................................................................................................................................................................
3 Press the Enter key to continue with the mirror copy of the data.
Result: The tool displays output that is similar to the following. Note the entry for
Pri_Boot.
_______________________________________________________________
Disks Selection
....................................................................................................................................................................................................................................
5-44 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run the scmirrorfs Tool to Set Up the Mirrored Configuration
....................................................................................................................................................................................................................................
Mirroring need Alternate Boot disk on Volume Group:"vg00"
______________________________________________________________
Device MByte Hardware Path Usage Type VolGroup
_______________________________________________________________
c1t2d0 8680 0/0/1/1.2.0 Pri_Boot _Main_ vg00
c2t2d0 8680 0/0/2/0.2.0 _(free)_ ______ __
c4t8d0 8680 0/4/0/0.8.0 _(free)_ ______ __
c4t9d0 8680 0/4/0/0.9.0 _(free)_ ______ __
c5t12d0 8680 0/7/0/0.12.0 _(free)_ ______ __
c5t13d0 8680 0/7/0/0.13.0 _(free)_ ______ __
...................................................................................................................................................................................................
4 At the following prompt, enter the name of an alternative device from which to boot:
Select Alternate BOOT dev name or [q] to quit: <device name>
Result: The tool displays output that is similar to the following. Note the entries for
Pri_Boot and Alt_Boot.
Disk Selection
________________________________________________________________
Device MByte Hardware Path Usage Type VolGroup
__________________________________________________________________
c1t2d0 8680 0/0/1/1.2.0 Pri_Boot _Main_ vg00
c2t2d0 8680 0/0/2/0.2.0 _(free)_ ______ __
c4t8d0 8680 0/4/0/0.8.0 Alt_Boot Mirror vg00
c4t9d0 8680 0/4/0/0.9.0 _(free)_ ______ __
c5t12d0 8680 0/7/0/0.12.0 _(free)_ ______ __
c5t13d0 8680 0/7/0/0.13.0 _(free)_ ______ __
_________________________________________________________________
Confirm selection of device "<device name>"
...................................................................................................................................................................................................
5 At the following set of prompts, enter y to confirm the selection of the alternate device
from which to boot:
Confirm selection of device <device name>.
Press [y] for yes, [n] for no or [q] to quit, then press [Enter] y
Result: The tool displays output that is similar to the following. Extraneous lines have
been deleted for ease of reading/use.
....................................................................................................................................................................................................................................
1350 OMS 5-45
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
System Backup and Restore Run the scmirrorfs Tool to Set Up the Mirrored Configuration
....................................................................................................................................................................................................................................
with Allocation policy "contiguous"
...
=><date/time stamp>
....... Mirroring Logical Volume:"/dev/vg00/lvol10"
NOTE: Check /etc/lvmrc ..... =><date/time stamp>
NOTE: Set Alternate Boot Hardware Path to disk:"c4t8d0"
=><date/time stamp>
=>END: OSConf File(s) System Mirroring
Restore Warning and/or Error Messages
...................................................................................................................................................................................................
6 If you receive any restore warnings or error messages, see “Troubleshoot a Restore”
(p. 5-15) for details.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
5-46 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
6 Mirror Disks
6
Overview
Purpose
This chapter provides the 1350 OMS system administrator with the conceptual
information and the associated tasks that pertain to mirrored disks.
Contents
...................................................................................................................................................................................................................................
1350 OMS 6-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Mirror Disks Mirrored Disk Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
6-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Mirror Disks Mirrored Disk Overview
....................................................................................................................................................................................................................................
Mirrored disk configuration example
It is critical for administrators to be able to identify the hard disks that are present in a
configuration and how they are connected to the system box. This information is hidden
in the disk hardware path. The fist dot (“.”) in the hardware path distinguishes the
controllers.
In the following example, two different buses are shown: 0/5/1/0/4/1 and 0/5/1/0/4/0.
Each one has three disks connected.
Disks Selection
____________________________________________________________________
Device MByte Legacy Harware Path Usage Type VolGroup
____________________________________________________________________
disk17 140000 0/5/1/0/4/1.2.0 Pri_Boot _Main_ vg00
disk18 140000 0/5/1/0/4/1.1.0 _(free)_ ______ _______
disk19 140000 0/5/1/0/4/1.0.0 _(free)_ ______ _______
disk20 140000 0/5/1/0/4/0.2.0 _(free)_ ______ ________
disk21 140000 0/5/1/0/4/0.0.0 _(free)_ ______ _______
disk22 140000 0/5/1/0/4/0.1.0 _(free)_ ______ _______
____________________________________________________________________
Press [Enter] to continue...
The best mirror disk configuration, including controller fault resilience, is as follows:
disk17, disk18 and disk19 as Main units.
disk20, disk21 and disk22 as Copy units.
....................................................................................................................................................................................................................................
1350 OMS 6-3
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Mirror Disks Install the Mirror Disk/UX
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Mirrored Disk Overview” (p. 6-2)
Task
Complete the following steps to install the Mirror Disk/UX software.
...................................................................................................................................................................................................
1 Log in to the system in which the Mirror Disk/UX software is to be installed as root.
Result: You now have superuser privileges.
...................................................................................................................................................................................................
2 Enter the following command to initialize the installation and press Enter:
..,sys, root # /SCINSTALL/etc/scinstall3PP MIRROR [Enter]
Result: The installation is initialized and the software prompts you to select the
software source.
...................................................................................................................................................................................................
3 When the software prompts you to select the source as CD/DVD or depot, choose 1,
which is DVD/CD-ROM, and press Enter:
....................................................................................................................................................................................................................................
1 - DVD/CDRom
2 - DEPOT
q - quit
Insert choice and press [Enter]:
Result: The software prompts you to confirm the source device.
...................................................................................................................................................................................................
4 When the software prompts you to confirm the source device, enter the correct source
device and press Enter, or select the default by pressing Enter.
**************************************************************
ATTENTION
Installation require shutdown and reboot
Applications is better already stopped before start installation
************************************************************
Do you want execute installation NOW?:
Press [y] for yes or [n] for no, then press [Enter]
...................................................................................................................................................................................................
5 When the software prompts you to execute the installation, answer y to start the
installation now or n to postpone, but not stop, the installation:
Press [y] for yes or [n] for no, then press [Enter] y/n [Enter]
Result: If you answered y, to start the installation, the reboot begins.
If you answered n to postpone the installation, resume the installation at a later time
and go to Step 6.
...................................................................................................................................................................................................
6 If you have postponed the installation, enter the following command line when you are
ready to resume the installation:
...,sys,root # /SCINSTALL/SCINSTALL start [Enter]
Result: The scinstall installation is restarted.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 6-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Mirror Disks Configure Disk Fault Protection with Mirror Disk/UX®
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Mirrored Disk Overview” (p. 6-2)
Task
Complete the following steps to configure disk fault protection with Mirror Disk/UX®
after a full disk backup or if the mirror configuration was skipped for any reason at
installation time.
...................................................................................................................................................................................................
1 Log in to the system in which the alternate boot disk is to be specified as root.
Result: You now have superuser privileges.
...................................................................................................................................................................................................
2 Enter the following command to initialize the tool and press Enter:
..,sys, root # scmirrorfs [Enter]
Result: The installation is initialized and the software prompts you to select the
alternate boot device:
____________________________________________________________________
Disks Selection
Mirroring need Alternate Boot disk on Volume Group:"vg00"
____________________________________________________________________
Device MByte Hardware Path Usage Type VolGroup
___________________________________________________________________
c1t2d0 8680 0/0/1/1.2.0 Pri_Boot _Main_ vg00
....................................................................................................................................................................................................................................
6-6 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Mirror Disks Configure Disk Fault Protection with Mirror Disk/UX®
....................................................................................................................................................................................................................................
c2t2d0 8680 0/0/2/0.2.0 __Data__ _Main_ vg00D
c4t8d0 8680 0/4/0/0.8.0 _(free)_ ______ ________
D c4t9d0 8680 0/4/0/0.9.0 _(free)_ ______ ________
c5t12d0 8680 0/7/0/0.12.0 _(free)_ ______ ________
c5t13d0 8680 0/7/0/0.13.0 _(free)_ ______ ________
____________________________________________________________________
Select Alternate BOOT dev name or [q] to quit:
...................................................................................................................................................................................................
3 When the tool prompts you, enter the name of the alternate boot device:
Select Alternate BOOT dev name or [q] to quit:
<name of the alternate boot device>
Important! Refer to “Mirrored disk configuration example” (p. 6-3) for the naming
conventions and pairing details.
Result: When the amount of disk space requested is reached, the tool displays output
that is similar to the following:
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 6-7
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Mirror Disks Configure Disk Fault Protection with Mirror Disk/UX®
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
6-8 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
7 Network Depot
7
Overview
Purpose
This chapter provides the 1350 OMS system administrator with the conceptual
information and the associated tasks that pertain to the management of the Network
Depot.
Contents
...................................................................................................................................................................................................................................
1350 OMS 7-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Network Depot Network Depot Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Network Depot Network Depot Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 7-3
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Network Depot Run scbuilddepot to Create or Update the Platform
Software Depot
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Platform software depot” (p. 7-2)
Task
Complete the following steps to run scbuilddepot tool to create the platform software
depot.
...................................................................................................................................................................................................
2 Enter the following command to run the scbuilddepot tool and press Enter:
...,sys,root # scbuilddepot [Enter]
Result: The tool outputs a display that is similar to the following:
===================================================================
MW_OS Depot Builder
===================================================================
The depot copy requires 8.6 Gbytes extra space on disks
* Do you have enough space available [Y/N] :
...................................................................................................................................................................................................
3 When the tool prompts you about the space available, answer Y for yes:
The depot copy requires 8.6 Gbytes extra space on disks
* Do you have enough space available [Y/N] Y
....................................................................................................................................................................................................................................
7-4 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Network Depot Run scbuilddepot to Create or Update the Platform
Software Depot
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 At the following prompt, enter the source media, which is the CD-ROM, or press Enter
for the default device that is displayed, which is the CD-ROM that was used to install
HP-UX:
* Enter the CDROM device [ /dev/dsk/c1t2d0 ] : Enter
Result: The tool outputs a display that is similar to the following to indicate that it is
checking/extending the directory for the creation of the depot:
NOTE: Checking/Extending /<directory> for depot creation
If the current size of the partition mounted at /<directory> is not large enough, new
disk resources are required until the requested size is reached. The tool outputs a
display that is similar to the following
5 If additional/new disk resources are required, press the Enter key at the following
prompt:
Press [Enter] to continue... Enter
Result: The tool outputs a display that is similar to the following, which shows you
the amount of free space on each particular device:
6 At the following prompt, enter the name of the device to be used for the depot:
Select Data Area (Main instance) dev name or [q] to quit:
....................................................................................................................................................................................................................................
1350 OMS 7-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Network Depot Run scbuilddepot to Create or Update the Platform
Software Depot
....................................................................................................................................................................................................................................
Example:
Select Data Area (Main instance) dev name or [q] to quit: c1t4d0
...................................................................................................................................................................................................
7 When the file system mounted at /<directory> is large enough to house the depot, the
tool prompts you to specify the first disk of the set:
* Please insert CD SWP-OSCONF-V7.1.0 - 1/4 into the drive and
press [Enter] when ready
Insert the specified CD-ROM.
Press Enter when the LED on the CD-ROM stops blinking.
...................................................................................................................................................................................................
8 When the tool once again prompts you for the next CD-ROM in the set, replace the
current CD-ROM in the drive with the specified one.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
7-6 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Network Depot Add Software to the Platform Software Depot
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Platform software depot” (p. 7-2)
Task
Complete the following steps to add the software to the Platform Software Depot.
...................................................................................................................................................................................................
2 Enter the following command line to mount the device and press Enter:
...,sys,root # mount -o rr /dev/dsk/<device name>/SD_CDROM [Enter]
...................................................................................................................................................................................................
3 Enter the following command lines to copy the software package and press Enter to
execute each command line:
...,sys,root # swcopy -x enforce_dependencies=false / [Enter]
-s /SD_CDROM 1350OMS-MW_OS @/<directory>/SCDEPOT [Enter]
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 7-7
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Network Depot Create the Application Software Depot
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Application software depot” (p. 7-2)
Task
Complete the following steps to create the application software depot.
...................................................................................................................................................................................................
2 Enter the following command to extend the /alcatel directory to allow the storage of the
application software and press Enter:
...,sys,root # scextendfs /alcatel/DEPOT <required disk size>
[Enter]
...................................................................................................................................................................................................
3 Enter the following command to change directories to the depot directory and press
Enter:
...,sys,root # cd /alcatel/DEPOT [Enter]
Result: You are now in the /alcatel/DEPOT directory.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-8 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Network Depot Create the Application Software Depot
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 Enter the following command to check the CD-ROM type and press Enter:
...,sys,root # fstyp /dev/dsk/ [Enter]
...................................................................................................................................................................................................
6 Depending on whether the CD-ROM is a cdfs or hfs, use one of the following to mount
the CD at the /SD_CDROM directory:
If the CD-ROM type in the previous step is a cdfs, enter the following command and
press Enter:
...,sys,root # mount -o rr /dev/dsk/<cdrom device file> /SD_
CDROM [Enter]
If the CD-ROM type in the previous step is a hfs, enter the following command and press
Enter:
...,sys,root # mount -r /dev/dsk/<cdrom device file> /SD_CDROM
[Enter]
...................................................................................................................................................................................................
7 Enter the following command to copy the entire contents of the CD-ROM to the
/alcatel/DEPOT directory and press Enter:
...,sys,root # cp -p /SD_CDROM/* /alcatel/DEPOT [Enter]
...................................................................................................................................................................................................
8 Enter the following command to unmount the CD-ROM and press Enter:
...,sys,root # umount /SD_CDROM [Enter]
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 7-9
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Network Depot Edit the .rhosts file to Authorize Access to the Application
Software Depot
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Application software depot” (p. 7-2)
Task
Complete the following steps to edit the .rhosts file to authorize access to the Application
Software Depot.
...................................................................................................................................................................................................
2 Use the vi editor to access the .rhosts file and add the following lines:
hosta root
hostb root
hostc root
Save the changes that you have made to the file.
...................................................................................................................................................................................................
3 Specify these same hosts, in the same manner, the /etc/hosts file.
....................................................................................................................................................................................................................................
7-10 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Network Depot Edit the .rhosts file to Authorize Access to the Application
Software Depot
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 At the end of the installation, use the vi editor to access the .rhosts file and delete the
following lines:
hosta root
hostb root
hostc root
Save the changes that you have made to the file.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 7-11
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Network Depot Edit the .rhosts file to Authorize Access to the Application
Software Depot
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
7-12 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
8 General Operations
8
Overview
Purpose
This chapter contains conceptual information and the related tasks that are needed for the
basic operation of the 1350 OMS.
Contents
...................................................................................................................................................................................................................................
1350 OMS 8-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
General Operations Restart the HP® Servers
....................................................................................................................................................................................................................................
Related information
This task does not have any related information.
Task
Note: Important ! For any restart situation, do not use the reboot command.
...................................................................................................................................................................................................
2 Stop the applications using the PMC application. Select the applications on the PMC
window; and from the popup menu, select the command Stop, as shown in figure
....................................................................................................................................................................................................................................
8-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
General Operations Restart the HP® Servers
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
4 On the CDE front panel, press the terminal icon to start a Unix terminal application.
Execute the command su -root
Stop the Kernel Services using the following command:
...,sys,root # /alu/Kernel/script/KernelServices stop [Enter]
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
cd /
...................................................................................................................................................................................................
6 Enter the following command to reboot or stop the HP® servers gracefully:
shutdown -r now
or
shutdown -h now
The command is shutdown -h if you want to stop the system completely or
shutdown -r if you want to stop the system and restart it.
Note: If you are connected to the server, the shutdown command outputs the
following message:
SHUTDOWN PROGRAM
<date/time stamp> METDST
Do you want to send your own message? (You must respond with
'y' or 'n'.):
Answer n to the question.
...................................................................................................................................................................................................
7 When the system is restarted, press the terminal icon to start a UNIX terminal application.
Execute the command su -root to login as root user.
...................................................................................................................................................................................................
9 As the alcatel user, start the applications using the PMC application. Select the
applications on the PMC window and from the popup menu, select the command Start.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
8-4 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
General Operations Decompress a Compressed .gz File
....................................................................................................................................................................................................................................
Related information
This task does not have any related information.
Task
Use this task to decompress a compressed .gz file.
...................................................................................................................................................................................................
1 From the machine on which the 1350 OMS application is running, log into the
application.
...................................................................................................................................................................................................
4 Enter the following command to decompress a file and to redirect the output to another
file:
/usr/contrib/bin/gunzip -c <file to be compressed.gz> > <output
directory/output file>
Example:
/usr/contrib/bin/gunzip -c /tmp/alarm.log.gz > tmp/alarm.log
....................................................................................................................................................................................................................................
1350 OMS 8-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
General Operations Decompress a Compressed .gz File
....................................................................................................................................................................................................................................
Result: The file that you specified is decompressed and its output is redirected to the
file specified.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
8-6 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
General Operations Eject a CD-ROM
....................................................................................................................................................................................................................................
Eject a CD-ROM
When to use
Use this task to eject a CD-ROM when the CD-ROM does not get ejected as expected.
Related information
This task does not have any related information.
Task
Use this task to eject a CD-ROM when the CD-ROM does not get ejected as expected.
...................................................................................................................................................................................................
1 From the machine on which the 1350 OMS application is running, log in as root.
...................................................................................................................................................................................................
3 Enter the following command lines to facilitate the ejection of the CD-ROM:
fuser -cku /SD_CDROM
umount /SD_CDROM
...................................................................................................................................................................................................
4 Press the Eject button to retrieve the CD-ROM from the drive.
Result: The CD-ROM is ejected.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 8-7
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
General Operations Eject a CD-ROM
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
8-8 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
9 Security
9
Overview
Purpose
This chapter provides the 1350 OMS system administrator with the conceptual
information and the associated tasks that pertain to the security of the overall 1350 OMS
network.
Contents
...................................................................................................................................................................................................................................
1350 OMS 9-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
9-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Security Overview
....................................................................................................................................................................................................................................
Security Overview
Security requirements
To guarantee the most secure system possible and to reduce the risk of security breaches,
1350 OMS sets up an HP® Trusted System configuration and hardens the system with the
HP-UX® Bastille Security Hardening Tool.
This security platform is based on user authentication, which is based on the following:
• The system identifies each user with a user identifier, or a UID.
• The system grants access to the system through the use of a password.
....................................................................................................................................................................................................................................
1350 OMS 9-3
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Security Overview
....................................................................................................................................................................................................................................
Bastille has disabled keyboard interrupts.
NOTE: Bastille is scanning the system configuration...
Bastille is now locking down your system in accordance with your
answers in the "config" file. Please be patient as some modules
may take a number of minutes, depending on the speed of your machine.
NOTE: Executing File Permissions Specific Configuration
NOTE: Executing Daemon Specific Configuration
NOTE: Executing Account Security Specific Configuration
NOTE: Executing Inetd Specific Configuration
NOTE: Executing Sendmail Specific Configuration
NOTE: Executing DNS Specific Configuration
NOTE: Executing Apache Specific Configuration
NOTE: Executing Printing Specific Configuration
NOTE: Executing FTP Specific Configuration
NOTE: Executing HP-UX's Security Patch Check Configuration
NOTE: Executing HP-UX Specific Configuration
NOTE: Executing IPFilter Configuration"
Disabled cimserver
Disabled hpsmh
Admin Tools have been disabled.
Please check
/var/opt/sec_mgmt/bastille/TODO.txt
for further instructions on how to secure your system.”
The tool continues to display output that is similar to the following regarding the Login
Banner Configuration:
....................................................................................................................................................................................................................................
The tool concludes its display with output that is similar to the following that is intended
to call the administrator's attention to when scsecurity should be rerun and a note about
scsecurity revert.
....................................................................................................................................................................................................................................
1350 OMS 9-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Security Banners
....................................................................................................................................................................................................................................
Security Banners
About security banners and scsecurity
The 1350 OMS security sets up temporary banners pages that are displayed at login time
for both the shell and ftp access. Administrators must customize these two banner pages
with the appropriate information to represent their company and/or their use.
NOTE: "issue login message file" was not managed by security: /etc/issue
If you added as suggested an "Authorized Use Only" warning message,
please remove the message.
*******************************************************************
NOTICE TO USERS
This computer system is the private property of <COMPANY NAME> whether
individual, corporate or government. It is for authorized use only.
Users (authorized or unauthorized) have no explicit or implicit
expectation of privacy.
....................................................................................................................................................................................................................................
9-6 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Security Banners
....................................................................................................................................................................................................................................
Any or all uses of this system and all files on this system may be
intercepted, monitored, recorded, copied, audited, inspected, and
disclosed to your employer, to authorized site, government, and law
enforcement personnel, as well as authorized officials of government
agencies, both domestic and foreign.
By using this system, the user consents to such interception, monitoring,
recording, copying, auditing, inspection, and disclosure at the
discretion of such personnel or officials. Unauthorized or improper use
of this system may result in civil and criminal penalties and
administrative or disciplinary action, as appropriate. By continuing to
use this system you indicate your awareness of and consent to these terms
and conditions of use. LOG OFF IMMEDIATELY if you do not agree to the
conditions stated in this warning.
********************************************************************
....................................................................................................................................................................................................................................
1350 OMS 9-7
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Security Profiles
....................................................................................................................................................................................................................................
Security Profiles
Security profile types
Prior to setting up the security, administrators must select one of the following security
profiles:
• one profile named trusted-base
• one profile named trusted-advanced
....................................................................................................................................................................................................................................
9-8 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Security Profiles
....................................................................................................................................................................................................................................
*These restrictions are preconfigured on the system at the installation time. Both the
security profiles check if the system configuration is complete and re-apply the restriction
if necessary.
....................................................................................................................................................................................................................................
1350 OMS 9-9
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Security Profiles
....................................................................................................................................................................................................................................
Security and restrictions on High Availability configurations
For High Availability configurations that rely on the OS-Cluster or OS-Resilience,
security for the 1350 OMS must be set up with the same profile on every system. The
different storage methods for passwords can cause serious problems when the security
environments are not exactly aligned.
....................................................................................................................................................................................................................................
9-10 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Web Portal Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
Actions
SEC
Security (SEC) Database Management is only allowed for users who have an
Administrator profile.
....................................................................................................................................................................................................................................
1350 OMS 9-11
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security PMC Management Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
PMC Actions
✓ is Allowed
Actions Administrator Constructor Operator Viewer
Exit ✓ ✓ ✓ ✓
Start Selected Item ✓
Stop Selected Item ✓
Set Run Level ✓
Synchronize
View
PMC View
✓ is Allowed
View Administrator Constructor Operator Viewer
Info ✓ ✓ ✓ ✓
Selected Agent Trace ✓ ✓ ✓ ✓
PMC2 Log ✓ ✓ ✓ ✓
Local Configuration ✓ ✓ ✓ ✓
File
Agent Configuration ✓ ✓ ✓ ✓
File
Configuration
PMC Configuration
✓ is Allowed
Configuration Administrator Constructor Operator Viewer
Set Threshold ✓
....................................................................................................................................................................................................................................
9-12 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Session Management Macro Functions and Default User
Profiles
....................................................................................................................................................................................................................................
File
....................................................................................................................................................................................................................................
1350 OMS 9-13
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Alarm and FM Related Macro Functions and Default User
Profiles
....................................................................................................................................................................................................................................
Fault
✓ is Allowed
Users Administrator Constructor Operator Viewer
Current Alarms ✓ ✓ ✓ ✓
Historical Alarms ✓ ✓ ✓ ✓
....................................................................................................................................................................................................................................
9-14 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Alarm and FM Related Macro Functions and Default User
Profiles
....................................................................................................................................................................................................................................
Alarm Surveillance Historical Alarms
....................................................................................................................................................................................................................................
1350 OMS 9-15
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security User Management Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
System Management
Navigation
....................................................................................................................................................................................................................................
9-16 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security SMF Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
Trace Management
....................................................................................................................................................................................................................................
1350 OMS 9-17
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security SMF Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
Failure Management
FM - Workstation
✓ is Allowed
Workstation Administrator Constructor Operator Viewer
Do a Snapshot ✓ ✓ ✓
FM - OS Snapshot
✓ is Allowed
OS Snapshot Administrator Constructor Operator Viewer
Save Tape ✓ ✓ ✓
Lock ✓ ✓ ✓
Unlock ✓ ✓ ✓
Delete ✓ ✓ ✓
FM - Options
✓ is Allowed
Options Administrator Constructor Operator Viewer
Set Max ✓ ✓ ✓
Number of
Snapshots
Scheduler Management
....................................................................................................................................................................................................................................
9-18 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security SMF Macro Functions and Default User Profiles
....................................................................................................................................................................................................................................
Backup Management
Restore Management
Cleanup Management
....................................................................................................................................................................................................................................
1350 OMS 9-19
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Audit and Log Files
....................................................................................................................................................................................................................................
Audit files
The 1350 OMS configures the audit system provided in HP-UX to trace security-relevant
system calls and events. (Refer to the audevent HP-UX man page for details.)
The audit records are stored in two specific files that are located in two specific file
systems. Whenever the current file and file system that is in use is full, the system
automatically switches over to the second one. The 1350 OMS monitors this activity
every 5 minutes and saves the data that is stored in the dismissed file into the archive file
system.
The audit files that the HP-UX audit function manages are the following:
• /.AUDITING/1/audfile
• /.AUDITING/2/audfile
During the initial activation of an trusted-advanced profile, the tool creates the structure
that is used to store the audit files and to produce an output that is similar to the
following:
....................................................................................................................................................................................................................................
______________________________________________________________________
Analyze Mount Point:"/.AUDITING/1"
Request free: 121 MegaByte(s)
Evaluate size: 128 MegaByte(s)
Create Logical Volume x "/.AUDITING/1"
Extend Mount Point to 128 MByte
Making new file system (vxfs) on Mount Point
Mount /dev/vg00/lvol13 on /.AUDITING/1
Updating /etc/fstab x Mount Point
_____________________________________________________________________
=><date/time stamp>
=>END: MW_OS Extend/Create File(s) System
Executing "Secondary Audit log file" File System Configuration
=><date/time stamp>
=>START: MW_OS Extend/Create File(s)
System______________________________________________________________________
Analyze Mount Point:"/.AUDITING/2"
Request free: 121 MegaByte(s)
Evaluate size: 128 MegaByte(s)
Create Logical Volume x "/.AUDITING/2"
Extend Mount Point to 128 MByte
Making new file system (vxfs) on Mount Point
Mount /dev/vg00/lvol14 on /.AUDITING/2
Updating /etc/fstab x Mount Point
______________________________________________________________________
=><date/time stamp>
=>END: MW_OS Extend/Create File(s) System
When a file is saved in either /.ARCHIVE area, the filename adheres to the following
naming convention:
audfile-<date>-<time>.gz
Example:
audfile-2011_12_10-15:57:49.gz
The /.ARCHIVE file system is automatically created to store more than 10 audit files,
however, when the file system becomes full, the collected audit data is lost.
The current audit file is compressed and moved into the /.ARCHIVE directory each time
the 1350 OMS security reverts to the default HP-UX level through scsecurity revert.
Log files
Some HP-UX system log files are automatically stored in the /.ARCHIVE directory for the
following reasons:
• To keep and maintain a long system history
• To prevent the abnormal growth of the file
....................................................................................................................................................................................................................................
1350 OMS 9-21
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Audit and Log Files
....................................................................................................................................................................................................................................
These log files are compressed and renamed according to the following naming
convention:
<log prefix>-<date>-<time>.gz
Where:
<log prefix> is a unique file prefix that is defined for each log file.
<date> is the date of the move and compression date.
<time> is the time of the move and compression.
gz is the file type extension for gnu zip.
Example:
The /var/adm/cron/log is saved on January 1, 2011 at 15:57:59. In the /.ARCHIVE
directory, the respective log file is called:
cron.log-2011_01_01-15:57:49.gz
....................................................................................................................................................................................................................................
9-22 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Audit and Log Files
....................................................................................................................................................................................................................................
Encryption set up
The administrator can change the default security configuration so it archives both the
audit files and log files in encrypted format. To enable this functionality, the administrator
must change the settings of both the “ENCRYPT_ARCHIVE” (p. 9-29) and
“CHANGE_ENCRYPT_PASSWORD” (p. 9-28) parameters to YES.
Important! We recommend that the administrator sets the encryption policy for both of
these parameters before the security is activated. It is dangerous to change the encryption
policy after security is activated; and if it must be done, it must be done carefully.
When the ENCRYPT_ARCHIVE and CHANGE_ENCRYPT_PASSWORD parameters
are set to YES, the tool outputs a display that is similar to the following, which requests
the encryption password during the security setup:
....................................................................................................................................................................................................................................
1350 OMS 9-23
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Sample security.parms File
....................................................................................................................................................................................................................................
# Encrypt Archive
#
# NOTE: TO ACTIVATE THE ENCRYPT FUNCTIONALITY BOTH THE NEXT TWO VARIABLE MUST
BE SET TO "YES",
# AFTER THE FIRST ACTIVATION YOU CAN AVOID TO BE ASKED FOR THE "ENCRYPTION
PASSWORD CHANGE"
# SETTING TO "NO" THE VARIABLE CHANGE_ENCRYPT_PASSWORD
# ATTENTION: IF THE VALUE FOR THE ENCRYPT PASSWORD IS DEFINED|CHANGED YOU MUST
REMEMBER IT TO BE
# ABLE TO DECRYPT THE ENCRYPTED LOG FILES.
ENCRYPT_ARCHIVE="NO" ## Encrypt archive log files:"YES" or "NO"
in uppercase
CHANGE_ENCRYPT_PASSWORD="NO" ## Change encryption password:"YES"
or "NO" in uppercase
The following lines display information about un-trusted systems:
....................................................................................................................................................................................................................................
9-24 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Sample security.parms File
....................................................................................................................................................................................................................................
PASSWORD_MIN_SPECIAL_CHARS=1 ## Password minimum special characters
MIN_PASSWORD_LENGTH=7 ## Minimum password length
#
# end of UN-Trusted System parameters
The following lines display information about trusted systems:
# Auditing
#
# ATTENTION: DO NOT CHANGE BELOW THIS LINE AFTER THE FIRST APPLY OF THE
SECURITY
PRI_SWITCH=102400 ## Switch size of primary audit log file (kbytes)
SEC_SWITCH=102400 ## Switch size of secondary audit log file (kbytes)
....................................................................................................................................................................................................................................
1350 OMS 9-25
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security System Security Parameters
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
actions reported at follows:
- save the current custom file for reference
cp /SCINSTALL/security/data/custom/security.parms /
/SCINSTALL/security/data/custom/security.parms_save
- copy the default file in the custom directory
cp /SCINSTALL/security/lib/security.parms /
/SCINSTALL/security/data/custom/security.parms
- apply your personal customization on the custom file
- finally remove the old saved custom file
rm /SCINSTALL/security/data/custom/security.parms_save
....................................................................................................................................................................................................................................
1350 OMS 9-27
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security System Security Parameters
....................................................................................................................................................................................................................................
Table 9-1 System Security Parameters (continued)
CHANGE_ENCRYPT_PASSWORD
The CHANGE_ENCRYPT_PASSWORD system security parameter specifies whether
the audit and log archive encryption password can be changed. For the initial password
set up, changing this parameter setting is useful; however, when data exists in the archive,
we do not recommend changing the settings of this parameter. The
“ENCRYPT_ARCHIVE” (p. 9-29) is a related parameter. Refer to “Encryption set up”
(p. 9-23) for details.
The allowed values are YES and NO.
This parameter is an encryption parameter. This parameter and its values reside in the
following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
....................................................................................................................................................................................................................................
9-28 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security System Security Parameters
....................................................................................................................................................................................................................................
dlylntr
The dlylntr (delay between login tries) system security parameter specifies the maximum
number of seconds that are to elapse between login tries.
The allowed values are numbers that represent elapsed seconds.
This parameter is a Trusted System drive parameter. This parameter and its values reside
in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
ENCRYPT_ARCHIVE
The ENCRYPT_ARCHIVE system security parameter specifies whether audit and log
archive encryption should be turned on or off. The “CHANGE_ENCRYPT_PASS-
WORD” (p. 9-28) is a related parameter. Refer to “Encryption set up” (p. 9-23) for
details.
The allowed values are YES, to turn on the archive encryption, and NO, to turn off the
archive encryption.
This parameter is an encryption parameter. This parameter and its values reside in the
following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
gptm
The gptm (grace period time maximum) system security parameter specifies the
maximum number of days that are allowed for a grace period, or that period of time in
which users are allowed to change their passwords.
The allowed values are numbers that represent the number of days. The default value is
21 days.
This parameter is a Trusted System drive parameter, which is also used for password
aging. This parameter and its values reside in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
....................................................................................................................................................................................................................................
1350 OMS 9-29
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security System Security Parameters
....................................................................................................................................................................................................................................
llog
The llog (last log) system security parameter specifies the user inactivity time, which is
expressed in the number of days, that users have before their accounts are disabled
because they have not logged in to the system.
The allowed values are numbers that represent days; where the number 0 indicates
disabled. Note that setting this parameter to a value other than 0 can cause application
problems for the users.
This parameter is a Trusted System drive parameter. This parameter and its values reside
in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
lntmout
The lntmout (login time out) system security parameter specifies the number of seconds
that are to elapse when logging in to the system before users are disconnected from the
network.
The allowed values are numbers that represent elapsed seconds.
This parameter is a Trusted System drive parameter. This parameter and its values reside
in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
MIN_PASSWORD_LENGTH
The MIN_PASSWORD_LENGTH system security parameter specifies the minimum
number of characters that are allowed in a password.
The allowed value is a number that represents the number of characters. The default value
is 7characters.
This parameter is a password parameter that handles the structure of a password. This
parameter and its values reside in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
....................................................................................................................................................................................................................................
9-30 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security System Security Parameters
....................................................................................................................................................................................................................................
nullpw
The nullpw (null password) system security parameter specifies whether users can enter a
null password.
The allowed values are YES and NO. We strongly recommend that this password is set to
NO to prevent serious breaches in security.
This parameter is a Trusted System drive parameter. This parameter and its values reside
in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
PASSWORD_HISTORY_DEPTH
The PASSWORD_HISTORY_DEPTH system security parameter specifies the number
times that users must change their passwords before they are allowed to reuse the same
password.
The allowed value is a number from 1 to 10. The default value is 4.
This parameter is a Password parameter that handles changing a password. This
parameter and its values reside in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
PASSWORD_MAXDAYS
The PASSWORD_MAXDAYS system security parameter specifies the maximum
number of days in which a particular password can remain current; or, the number of days
in the lifetime of one particular password before a user is not allowed system access.
The allowed value is a number that represents the number of days. The default value is
180 days.
This parameter is a password parameter that handles the aging of a password. This
parameter and its values reside in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
....................................................................................................................................................................................................................................
1350 OMS 9-31
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security System Security Parameters
....................................................................................................................................................................................................................................
PASSWORD_MINDAYS
The PASSWORD_MINDAYS system security parameter specifies the minimum number
of days in which a particular password can remain current; or, the number of days in the
lifetime of one particular password before the user can change the password.
The allowed value is a number that represents the number of days. The default value is 0
days. Note: setting this parameter to a value other than 0 can cause application problems
for the users. The system prevents users from changing a password that is not older than
the specified number of days, which is the setting of the PASSWORD_MINDAYS.
This parameter is a password parameter that handles the aging of a password. This
parameter and its values reside in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
PASSWORD_MIN_DIGIT_CHARS
The PASSWORD_MIN_DIGIT_CHARS system security parameter specifies the
minimum number of digits (numbers) that are allowed in a password.
The allowed value is a number that represents the number of digits allowed. The default
value is one number.
This parameter is a password parameter that handles the structure of a password. This
parameter and its values reside in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
PASSWORD_MIN_SPECIAL_CHARS
The PASSWORD_MIN_SPECIAL_CHARS system security parameter specifies the
minimum number of special characters (such as *) that are allowed in a password.
The allowed value is a number that represents the number of special characters that are
allowed. The default value is one special character.
This parameter is a password parameter that handles the structure of a password. This
parameter and its values reside in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
....................................................................................................................................................................................................................................
9-32 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security System Security Parameters
....................................................................................................................................................................................................................................
PASSWORD_WARNDAYS
The PASSWORD_WARNDAYS system security parameter specifies the number of days
in which users are warned, upon their login to the system, that their current password is
scheduled to expire.
The allowed value is a number that represents the number of days. The default value is 14
days.
This parameter is a password parameter that handles the aging of a password. This
parameter and its values reside in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
rstrpw
The rstrpw (restrict trivial passwords) system security parameter specifies whether
passwords are to be checked for trivialities.
The allowed values are YES and NO.
This parameter is a Trusted System drive parameter. This parameter and its values reside
in the following file:
/SCINSTALL/security/data/custom/security.parms
SIT
The SIT (shell inactivity timeout) system security parameter specifies the value in
seconds that the ksh and sh shells can be left inactive before a timeout occurs and the user
is automatically locked out.
The allowed value is a number that represents the number of seconds that can elapse
before a timeout can occur; and the number 0 to disable the feature.
This parameter and its values reside in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
syschpw
The syschpw (system character password) system security parameter specifies whether
the system can generate passwords that are composed of only characters.
Since the “usrpick” (p. 9-35) password is set to YES, this parameter should not be set and
is not a valid option.
....................................................................................................................................................................................................................................
1350 OMS 9-33
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security System Security Parameters
....................................................................................................................................................................................................................................
This parameter is a Trusted System drive parameter. This parameter and its values reside
in the following file:
/SCINSTALL/security/data/custom/security.parms
sysltpw
The syschpw (system letter password) system security parameter specifies whether the
system can generate passwords that are composed of only letters.
Since the “usrpick” (p. 9-35) password is set to YES, this parameter should not be set and
is not a valid option.
This parameter is a Trusted System drive parameter. This parameter and its values reside
in the following file:
/SCINSTALL/security/data/custom/security.parms
syspnpw
The syspnpw (system pronounceable password) system security parameter forces the
system to generate a password that users can pronounce.
Since the “usrpick” (p. 9-35) password is set to YES, this parameter should not be set and
is not a valid option.
This parameter is a Trusted System drive parameter. This parameter and its values reside
in the following file:
/SCINSTALL/security/data/custom/security.parms
tmaxlntr
The tmaxlntr (maximum login tries) system security parameter specifies the maximum
number of unsuccessful login attempts before users are disconnected from the network.
The allowed values are numbers. The value of -1 indicates that a check is not to be
performed and a number greater than 0 indicates the number of allowed invalid attempts
before the users are disconnected from the network.
This parameter is a Trusted System drive parameter. This parameter and its values reside
in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
....................................................................................................................................................................................................................................
9-34 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security System Security Parameters
....................................................................................................................................................................................................................................
umaxlntr
The umaxlntr (user maximum login tries) system security parameter specifies the
maximum number of consecutive invalid/unsuccessful login attempts before a user
account is locked.
The allowed values are numbers. The value of -1 indicates that a check is not to be
performed and a number greater than 0 means the number of allowed invalid attempts to
log in to the system.
This parameter is a Trusted System drive parameter. This parameter and its values reside
in the following file:
/SCINSTALL/security/data/custom/security.parms
The scsecurity modify command line is used to change the initial value/setting of this
parameter.
usrpick
The usrpick (user pick) system security parameter specifies whether users can choose
their own passwords.
The allowed values are YES and NO.
Important! This parameter must always be set to YES.
This parameter is a Trusted System drive parameter. This parameter and its values reside
in the following file:
/SCINSTALL/security/data/custom/security.parms
WARN_USERS_LIST
The WARN_USERS_LIST system security parameter is a list of users, separated by blank
spaces, who are to be e-mailed of security problems. Note: the mail is restricted to 1350
OMS system recipients only. Refer to “Audit and log files functional overview”
(p. 9-20) for additional details.
The allowed values are a local username and a blank character space that separates one
user from the next.
This parameter is an advanced security parameter. This parameter and its values reside in
the following file:
/SCINSTALL/security/data/custom/security.parms
....................................................................................................................................................................................................................................
1350 OMS 9-35
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Prepare to Set Up Security
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Security Overview” (p. 9-3)
• “Security Profiles” (p. 9-8)
• “System Security Parameters” (p. 9-26)
Task
Complete the following steps to prepare for the security set up.
...................................................................................................................................................................................................
1 To avoid a reboot during the security set-up procedure, determine if you have the correct
software installed. If you do not have one or more pieces of the required software, the
security set up tool automatically activates the software install process and it can reboot
the system.
For the software that the 1350 OMS relies on and the software that is required for the
security set-up procedure, refer to “Security software requirements” (p. 9-3).
...................................................................................................................................................................................................
2 Review and select the appropriate security profile for your needs.
Refer to “Security Profiles” (p. 9-8) and “Access to the secure host” (p. 9-9) for details
and considerations. In addition, for High Availability systems, refer to “Security and
restrictions on High Availability configurations” (p. 9-10).
...................................................................................................................................................................................................
3 To customize security defaults parameters, change the values in the following file:
/SCINSTALL/security/data/custom/security.parms
Important! We strongly recommend that you make any changes before security
activation.
If you do make the modification when the security is configured, log in as root and enter
the following command to apply the new security values to the security configuration:
....................................................................................................................................................................................................................................
9-36 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Prepare to Set Up Security
....................................................................................................................................................................................................................................
...,sys,root # scsecurity security [Enter]
Important! We strongly recommend that you do not change the Trusted System
configuration with the HP® System Management Homepage (SMH).
Important! For High Availability configurations, the security must be configured at the
same level and with the same parameters set up on every system. A non-aligned security
setup can cause serious problems. Refer to “System Security Parameters” (p. 9-26) for
details.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 9-37
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Set Up Security with Any Profile
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Security Overview” (p. 9-3)
• “Security Profiles” (p. 9-8)
• “System Security Parameters” (p. 9-26)
• “Prepare to Set Up Security” (p. 9-36) task
Task
Complete the following steps to set up security with any profile, which includes the
trusted-base or trusted-advanced profile.
...................................................................................................................................................................................................
1 Complete all of the steps in the “Prepare to Set Up Security” (p. 9-36) task.
...................................................................................................................................................................................................
3 Enter the following command followed by the profile type that reflects the appropriate
security level for your installation:
...,sys,root # scsecurity <profile type> [Enter]
Where:
<profile type> is trusted-base or trusted-advanced.
....................................................................................................................................................................................................................................
9-38 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Set Up Security with Any Profile
....................................................................................................................................................................................................................................
Result: The scsecurity tool initially checks disk spaces and searches the server for
the required software. If the disk space is insufficient or at least one piece of software
is missing, the tool automatically activates the software install process and it can
reboot the system.
For the software that the 1350 OMS relies on and the software that is required for the
security set-up procedure, refer to “Security software requirements” (p. 9-3). For
details on the tool output and additional user responses, refer to “Security
configuration tool functional overview” (p. 9-3).
...................................................................................................................................................................................................
5 If you are configuring security with a trusted-advanced profile, enter and then re-enter
the new password for the security user when the tool outputs a display similar to the
following:
=><date/time stamp>
=>END: MW_OS Extend/Create File(s) System
Created Security Profile for Users
NOTE: For the active users the security profile setting
will be enabled at the next login.
Executing Security User Configuration
Executing 'security' user creation
Define password for user 'security'
Changing password for security
Last successful password change for security: NEVER
Last unsuccessful password change for security: NEVER
New password:
Re-enter new password:
New password: <enter the new password here>
Re-enter password: <enter the new password here again>
Result: The tool checks the password, and upon its acceptance of the new password,
it outputs a display similar to the following:
Password successfully changed
...................................................................................................................................................................................................
6 Complete the steps in the “Verify and Kill Processes” (p. 9-42) task.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 9-39
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Change a Manufacturer's Default Passwords
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Security Overview” (p. 9-3)
• “Prepare to Set Up Security” (p. 9-36) task
Task
Complete the following steps to change a manufacturer's default passwords.
...................................................................................................................................................................................................
3 When prompted to enter a new password, type a new password and confirm it without
echo entered characters.
Important! Passwords must meet the rules that are set for the security policy.
....................................................................................................................................................................................................................................
9-40 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Change a Manufacturer's Default Passwords
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 Optional, but strongly recommended: Periodically change the password to the root
account.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 9-41
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Verify and Kill Processes
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Prepare to Set Up Security” (p. 9-36) task
• “Set Up Security with Any Profile” (p. 9-38) task
Task
Complete the following steps to verify and kill processes.
...................................................................................................................................................................................................
{<date/time stamp>}
---------------------------------------
Deactivating Inetd Service: rtools
---------------------------------------
The following process(es) are associated with the inetd service "rtools".
They are most likely associated with a session which was initiated prior to
running Bastille. To disable a process see "kill(1)" man pages or reboot
the system
Active Processes:
###################################
rlogind
###################################
....................................................................................................................................................................................................................................
9-42 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Verify and Kill Processes
....................................................................................................................................................................................................................................
{<date/time stamp>}
---------------------------------------
Deactivating Inetd Service: bootps
---------------------------------------
The following process(es) are associated with the inetd service "bootps".
They are most likely associated with a session which was initiated prior to
running Bastille. To disable a process see "kill(1)" man pages or reboot
the system
Active Processes:
###################################
bootpd
###################################
...................................................................................................................................................................................................
2 Determine the process names that must be killed. Note: the process names are typically
displayed between the two hashed lines.
...................................................................................................................................................................................................
5 Enter the following command for each identified PID and press Enter.
...,sys,root# kill -15 <PID> [Enter]
...................................................................................................................................................................................................
6 Repeat Step 4 and Step 5 for each process that is in the TODO.txt file.
...................................................................................................................................................................................................
7 Ask all authorized users to log out of the current session and log back in so they can be
connected to the system through the secure connection.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 9-43
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Remove Security
....................................................................................................................................................................................................................................
Remove Security
When to use
Use this task to remove any existing security or to change the security profile.
Important! We do not recommend that the security configuration is reverted to that of
an unsecured configuration because it can affect password aging and the general
password definition.
Related information
See the following topic in this document:
• “Set Up Security with Any Profile” (p. 9-38)
• “Security user-allowed commands” (p. 9-9)
Task
Complete the following steps to remove any existing security or to change a security
profile.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
9-44 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Remove Security
....................................................................................................................................................................................................................................
Result: If any changes were made to the security configuration in the interim (either
manually or by other programs), the tool outputs a display that lists the changes.
...................................................................................................................................................................................................
3 If you are using the security revert to change a security profile, go to the “Set Up Security
with Any Profile” (p. 9-38) task to set up a security with a new profile.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 9-45
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Troubleshoot and Fix Old Password Problems
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “System Security Parameters” (p. 9-26)
hosta,operator # passwd
Changing password for operator
Old password:
Sorry.
hosta,operator #
Task
Complete the following step to fix a problem with an old password.
...................................................................................................................................................................................................
1 If you attempt to enter your old password, and your old password is longer than 8
characters, enter only the first 8 characters of the old password.
Result: The system accepts your old password.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
9-46 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Troubleshoot and Fix /etc/passwd File Problems
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “System Security Parameters” (p. 9-26)
Task
Complete the following steps to fix /etc/passwd file problems.
...................................................................................................................................................................................................
2 Use the following command to identify and fix the /etc/passwd error:
...,sys,root # pwck [Enter]
When using the pwck command, ignore irrelevant errors of the following type:
webadmin:*:40:1::/usr/obam/server/nologindir:/usr/bin/false
Login directory not found
goglobal:*:103:20:Graphon database user:/home/goglobal:/bin/sh
Login directory not found
....................................................................................................................................................................................................................................
1350 OMS 9-47
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Troubleshoot and Fix /etc/passwd File Problems
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
9-48 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Authorize Access to the Depot Machine
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Security Profiles” (p. 9-8)
Task
Complete the following steps to authorize access to the depot machine.
...................................................................................................................................................................................................
1 Enter the following command to grant access to the root user on the remote host:
..., root,sys # swacl -l host -M user:root@<hostname>:-r-t:
[Enter]
Result: The root user now has access on the remote host.
...................................................................................................................................................................................................
2 Enter the following command to remove access of the root user on the remote host:
..., root,sys # swacl -l host -D user:root@<hostname> [Enter]
Result: The root user no longer has access on the remote host.
...................................................................................................................................................................................................
3 Enter the following command to list the host ACL on the local host:
..., root,sys # swacl -l host [Enter]
Result: The host ACL is now listed on the local host
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 9-49
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Security Authorize Access to the Depot Machine
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
9-50 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
10 10 ® Printer Configurations
HP
Overview
Purpose
This chapter provides the 1350 OMS system administrator with the conceptual
information and the associated tasks that pertain to an HP® printer configurations.
Contents
...................................................................................................................................................................................................................................
1350 OMS 10-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
HP ® Printer Configurations Printer Configuration Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
10-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
HP ® Printer Configurations Configure a Printer in the Local Spooler Queue
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Printer Configuration Overview” (p. 10-2)
• “Start the Spooler” (p. 10-8)
Task
Complete the following steps to configure a printer in the local spool queue.
...................................................................................................................................................................................................
2 Enter the following command to initialize the hppi tool for JetDirect printer installation:
..,sys,root # hppi [Enter]
Result: The tool outputs the JetDirect banner page, which is followed by the main
menu:
***************************************************************
***** *****
***** ***** JetDirect Printer Installer for UNIX
***** ***** Verison E.10.18
***** *****
....................................................................................................................................................................................................................................
1350 OMS 10-3
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
HP ® Printer Configurations Configure a Printer in the Local Spooler Queue
....................................................................................................................................................................................................................................
***** ***** M A I N M E N U
***** *****
User: [root] OS: (HP-UX B.11.11)
I N V E N T
****************************************************************
1) Spooler Administration (super-user only)
2) JetDirect Configuration (super-user only)
- TCP/IP configurable parameters
3) Diagnostics:
- diagnose printing problems
?) Help q) Quit
Please enter a selection (q - quit):
...................................................................................................................................................................................................
Spooler:
1) Add printer to local spooler
2) Delete printer from local spooler
4) Install New Model Script
5) Remove Model Script
?) Help q) Quit
Please enter selection:
...................................................................................................................................................................................................
The latest model script can be downloaded from the web before creating
any queue. This can be done by enabling Realtime Model Script Update.The
Realtime Model Script Update can be Enabled/Disabled from the diagnostics menu.
....................................................................................................................................................................................................................................
10-4 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
HP ® Printer Configurations Configure a Printer in the Local Spooler Queue
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
The following is a list of suggested parameter values for this queue. You
may change any settings by selecting the corresponding non-zero numbers. The
values
will be used to configure this queue when '0' is selected.
To abort this configuration operation, press 'q'.
Configurable Parameters: Current Settings
------------------------ ----------------
1) Lp destination (queue) name: [<printername>_1]
2) Status Log [(No Log)]
3) Queue Class [(Not assigned)
4) Default Queue [NO]
5) Additional printer configuration...
...................................................................................................................................................................................................
9 If you are configuring the first print queue or if you want to define this printer as the new
default queue, enter a 4 at the following prompt:
Select an item for change, or '0' to configure (q - quit): 4
....................................................................................................................................................................................................................................
1350 OMS 10-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
HP ® Printer Configurations Configure a Printer in the Local Spooler Queue
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
10 If you want to set the banner page issue, at the next suggested parameter values menu,
enter 5 at the following prompt:
Select an item for change, or '0' to configure (q - quit): 5
Result: The tool outputs a display that is similar to the following:
11 If you want to set the banner page issue, enter 5 at the following prompt:
Select an item for change, or '0' to configure (q - quit): 5
Result: The Banner Page current setting is changed from [OFF] to [ON] and the tool
re-displays the submenu issued.
...................................................................................................................................................................................................
Ready to shut down the spooler and configure the new print queue.
The spooler will be running again after the configuration is done.
WARNING: If there are jobs currently being printed, and the page count is
enabled (i.e. when True End-of-Job is turned on), this shutdown and rerun
....................................................................................................................................................................................................................................
10-6 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
HP ® Printer Configurations Configure a Printer in the Local Spooler Queue
....................................................................................................................................................................................................................................
of the spooler may result in incorrect page count.
...................................................................................................................................................................................................
14 If the spooler is running, enter the following command to verify that a print job is not
queued:
lpstat -t
If the spooler is not running, the tool outputs the following message to remind you to start
the spooler:
15 At the Spooler Administration menu, enter q to exit the Spooler Administration menu.
Please enter selection: q [Enter]
q [Enter]
Result: The tool displays the Direct Printer Installation Main Menu.
...................................................................................................................................................................................................
16 At the Jet Direct Printer Installation Main Menu, enter q to exit the tool.
Please enter a selection (q - quit): q [Enter]
q [Enter]
Result: You have exited the tool.
...................................................................................................................................................................................................
17 Complete the steps in the “Start the Spooler” (p. 10-8) task.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 10-7
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
HP ® Printer Configurations Start the Spooler
....................................................................................................................................................................................................................................
Related information
See the following topics in this document::
• “Printer Configuration Overview” (p. 10-2)
• “Configure a Printer in the Local Spooler Queue” (p. 10-3)
Task
Complete the following steps to start the spooler.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
10-8 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
HP ® Printer Configurations Configure a Printer Booting upon Booting from the Local
System
....................................................................................................................................................................................................................................
Related information
See the following topics in this document:
• “Printer Configuration Overview” (p. 10-2)
• “Start the Spooler” (p. 10-8)
Task
Complete the following steps to configure a printer upon booting from the local system.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 10-9
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
HP ® Printer Configurations Configure a Printer Booting upon Booting from the Local
System
....................................................................................................................................................................................................................................
Result: You now have superuser privileges.
...................................................................................................................................................................................................
2 Enter the following command to initialize the hppi tool for JetDirect printer installation:
..,sys,root # hppi [Enter]
Result: The tool outputs the JetDirect banner page, which is followed by the main
menu:
****************************************************************
1) Spooler Administration (super-user only)
2) JetDirect Configuration (super-user only)
- TCP/IP configurable parameters
3) Diagnostics:
- diagnose printing problems
?) Help q) Quit
Please enter a selection (q - quit):
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
10-10 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
HP ® Printer Configurations Configure a Printer Booting upon Booting from the Local
System
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
8 At the following prompt, specify the printer name and the IP address of the printer that
should be added to the /etc/hosts file:
Add <Printer Name> and <Printer IP Address> to /etc/hosts? (y/n/
q, default=y) y
Result: The tool outputs a display similar to the following to remind you to update
your master source:
Following are optional parameters you may set for JetDirect. Select any non-
zero numbers to make the changes. The settings are used to create a
BOOTP/TFTP database when '0' is selected. To abort the operation, press
'q'
Other optional parameters:
-------------------------
1) Set printer location (uses tftp)
2) Set printer contact (uses tftp)
3) Set subnetmask
4) Set gateway
5) Set syslog (uses tftp)
6) Change idle timeout (uses tftp)
7) Create access list (up to 10 names). (Default: all allowed).
(uses tftp)
8) Other SNMP parameters: (uses tftp)
(GET/SET community name, trap and community name, authentication
trap)
9) Set HP JetDirect lpd banner page
....................................................................................................................................................................................................................................
1350 OMS 10-11
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
HP ® Printer Configurations Configure a Printer Booting upon Booting from the Local
System
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
10-12 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
HP ® Printer Configurations Configure a Printer Booting upon Booting from the Local
System
....................................................................................................................................................................................................................................
Result: The tool outputs a display that is similar to the following that requests you to
wait until the printer finishes its selftest.
If you are not ready for the next test (for example, the IP name has not
taken
affect in your DNS server), press 'q' to return to the configuration menu now.
...................................................................................................................................................................................................
14 At the following prompt, enter y to send the test files to the printer:
Do you want to send test file(s) to this printer (y/n, default=
n)? y [Enter]
Result: The tool outputs a display that is similar to the following that requests you to
wait until the printer finishes its selftest.
This test is using test files to demonstrate that data bytes can be
transmitted a
cross the HP JetDirect interface setup. As long as a few characters print out,
the test is successful.
The printer must be ready, i.e. online and not printing anything.
The following types of test files can be sent to the printer:
1) text file (if printer is in PCL or AUTO mode)
2) PostScript file (if printer is in PS or AUTO mode)
3) HP-GL/2 file (if it is a HPGL/2 plotter)
4) User supplied file
...................................................................................................................................................................................................
15 At the following prompt, enter 2 to indicate that the PostScript file should be transmitted:
Which one should be transmitted? (1/2/3/q, default=1) 2
Result: The tool displays output that is similar to the following that indicates that the
test file has been sent to the named printer:
....................................................................................................................................................................................................................................
1350 OMS 10-13
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
HP ® Printer Configurations Configure a Printer Booting upon Booting from the Local
System
....................................................................................................................................................................................................................................
Result: The tool outputs the JetDirect Main Menu.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
10-14 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
11 Troubleshooting
11
Overview
Purpose
This chapter provides the 1350 OMS system administrator with the conceptual
information and the associated tasks that pertain to troubleshooting the overall 1350
OMS.
Contents
...................................................................................................................................................................................................................................
1350 OMS 11-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
11-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Troubleshooting
General Troubleshooting
....................................................................................................................................................................................................................................
General Troubleshooting
Troubleshooting
Overview
Troubleshooting guidelines are provided in terms of symptoms and fixes, and any related
tasks that might accompany the fix.
# ifconfig lan0
lan0: flags=843<UP,BROADCAST,RUNNING,MULTICAST>
inet 10.12.20.234 netmask ffff0000 broadcast 10.12.255.255
#ifconfig lan1
lan1: flags=843<UP,BROADCAST,RUNNING,MULTICAST>
inet 10.12.21.10 netmask ffff0000 broadcast 10.12.255.255
Note: In the previous output, the subnet mask splits the IP address information into the
subnet and host. The bit that is set to 1 in the netmask identifies the subnet; the bit that is
set to 0 identifies the host. Since the netmask is provided as a hexadecimal bit
representation and the IP address and four figures are dot separated, it is difficult to
identify the two IP address that are masked by netmask, which provides the same subnet.
The easiest way to compare the broadcast information shown is by the ifconfig command.
In the previous output, the display of the same broadcast value indicates if two IP
addresses differ in their binary representation and if they are in the same subnet.
Note: The addressing scheme is designed for optimal network behavior. To improve
network throughput, use the HP® Auto Port Aggregation.
KRB5 XS: Cannot contact any KDC for requested realm while initializing krb5
FATAL Error while sending command to host = <hostname> -
Error = 5 (Cannot contact any KDC for requested realm)
at /alcatel/<release>/Kernel/lib/lib_perl/Remotizer.pm line <number>
The KDC daemon is not responding on the server that is identified as <hostname>.
Use the steps in the “Ping a Node” (p. 11-6) task to determine if the host can be reached.
If the host can be reached, log into that host server as root and stop/start the KDC daemon
by entering the following command:
...,root,sys $ /sbin/init.d/krbsrv stop ; /sbin/init.d/krbsrv start [Enter]
Important! When Kerberos is stopped and restarted, system malfunctions can occur.
....................................................................................................................................................................................................................................
11-4 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Troubleshooting
General Troubleshooting
....................................................................................................................................................................................................................................
Output similar to the following is displayed. Identify the process that has a 1 in the
parent Process Identifier (PID) column, which is the third column in the output
example. Wait a while and re-enter the same command. If the conmgr process has a 1
as a parent PID and it has the same PID in both the ps outputs, it is stable. If a line is
not displayed or if the two PIDs that are displayed are different, contact your
Alcatel-Lucent local customer service support team immediately.
....................................................................................................................................................................................................................................
1350 OMS 11-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Ping a Node
General Troubleshooting
....................................................................................................................................................................................................................................
Ping a Node
When to use
Use this task to ping a node/host; meaning, to verify if a node can communicate with the
local node/host.
Related information
See the following topic in this document:
• “Security Overview” (p. 9-3)
Task
Complete the following step to ping a host.
...................................................................................................................................................................................................
1 Enter the following command to ping the host through its IP address:
...,root,sys $ ping <IP address/hostname> <bytes> <packets>
Example:
,sys,root # ping <IP address/host name> 64 5
The command outputs a display similar to the following:
....................................................................................................................................................................................................................................
11-6 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Ping a Node
General Troubleshooting
....................................................................................................................................................................................................................................
Result: The system outputs host information as shown in the example. Any error or
output with packet loss equal to 100% means the machine is unreachable or unknown.
If the host is unknown, the system outputs a display that is similar to the following:
ping: host unknown
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 11-7
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Activate the KDC Log
General Troubleshooting
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Deactivate the KDC Log” (p. 11-10)
Task
Complete the following steps to activate the Kerberos KDC log.
...................................................................................................................................................................................................
1 Enter the following command to check free system space in the /var/adm/crash file:
...,root,sys $ bdf /var/adm/crash [Enter]
Result: The system outputs the crash file
...................................................................................................................................................................................................
2 In the /var/adm/crash file, check the Avail column to determine if more than 10,000
kilobytes are displayed.
...................................................................................................................................................................................................
3 Enter the following command lines to preserve a safe copy of the KDC start-up
procedure:
...,root,sys $ cd /sbin/init.d [Enter]
...,root,sys $ cp -p krbsrv krbsrv.save [Enter]
...................................................................................................................................................................................................
4 Using the vi editor, access the krbsrv file and replace the null file output in the kdcd start
command with the log file by changing the following line:
/opt/krb5/sbin/kdcd -l /dev/null
to:
/opt/krb5/sbin/kdcd -l /var/adm/crash/kdcd.log
....................................................................................................................................................................................................................................
11-8 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Activate the KDC Log
General Troubleshooting
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
7 Deactivate the KDC daemon log. Go to the “Deactivate the KDC Log” (p. 11-10) task for
details.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 11-9
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Deactivate the KDC Log
General Troubleshooting
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “Activate the KDC Log” (p. 11-8)
Task
Complete the following steps to deactivate the Kerberos KDC log.
...................................................................................................................................................................................................
1 Enter the following command lines to restore the saved KDC start-up configuration:
...,root,sys $ cd /sbin/init.d [Enter]
...,root,sys $ mv krbsrv.save [Enter]
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
11-10 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Overview
System / Environment
....................................................................................................................................................................................................................................
System / Environment
Overview
Purpose
This section explains problems that can arise regarding the system and system
environment.
Contents
....................................................................................................................................................................................................................................
1350 OMS 11-11
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting OS Percentage Usage
System / Environment
....................................................................................................................................................................................................................................
OS Percentage Usage
What to do
To investigate the Operating System (OS) percentage usage when the system appears too
slow, use the command top -s1.
The IDLE percentage of the machine must be greater than 0; if the IDLE percentage of
the machine is not greater than 0, problems can exist that are related to the following:
• Processes: too many processes are running and some of them can be looping.
• Memory: the memory usage is too high.
....................................................................................................................................................................................................................................
11-12 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Manage Semaphores
System / Environment
....................................................................................................................................................................................................................................
Manage Semaphores
When to use
Use this task to manage semaphores.
Related information
See the following topic in this document:
• “Activate the KDC Log” (p. 11-8)
Task
Complete the following steps to manage semaphores.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 11-13
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Unblock the Login to the 1350 OMS
System / Environment
....................................................................................................................................................................................................................................
Related information
This task does not have any related information.
Task
Complete the following steps to unlock the login to the 1350 OMS.
...................................................................................................................................................................................................
3 Log in as root and launch the following two commands to delete (rm) the loginDB.lock
file and to create an empty file:
rm /alu/Kernel/data/.loginDB.lock
echo > /alu/Kernel/data/.loginDB
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
11-14 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Remote Commands
System / Environment
....................................................................................................................................................................................................................................
Remote Commands
Remotizer
The Remotizer application allows to execute a command on a remote host:
/alu/Kernel/etc/Remotizer.pl RemoteExec <host> <unix command>
<user>
The IP address of the host must be defined in the file /etc/hosts .
For example: /alu/Kernel/etc/Remotizer.pl RemoteExec kaveri ll root
Note: this command can be used to execute commands with a different users (for
example to execute a command as root user instead of applicative user) on the local
host.
....................................................................................................................................................................................................................................
1350 OMS 11-15
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Kerberos Configuration
System / Environment
....................................................................................................................................................................................................................................
Kerberos Configuration
When to use
Use this task if a node is added to the 1350 OMS system configuration.
Related information
Kerberos configuration is listed in the following file:
opt/krb5/krb.conf
Task
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
11-16 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Kerberos Configuration
System / Environment
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 11-17
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Overview
System Installation and Customization
....................................................................................................................................................................................................................................
Overview
Purpose
This section collects problems that can arise during the system installation phase and
system customization phase.
Contents
....................................................................................................................................................................................................................................
11-18 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Troubleshoot 1350 OMS System License Problems
System Installation and Customization
....................................................................................................................................................................................................................................
Related information
This task does not have any related information.
Task
Complete the following steps to troubleshoot 1350 OMS system license problems.
...................................................................................................................................................................................................
1 To determine if any problems exist with the product license, access and read the contents
of the following log file:
/usr/Systems/Global_Instance_9.5.0_Master/maintenance/log/pmc2.log
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 11-19
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Troubleshoot 1350 OMS System License Problems
System Installation and Customization
....................................................................................................................................................................................................................................
MNT#7.1,1350_4_CPU#7.1,1350_4_CPU_NR6_UPG#7.1,1350_4_CPU_MNT#7.1,
1350_6_CPU#7.1, 1350_6_CPU_NR6_UPG#7.1,1350_6_CPU_MNT#7.1,1350_8_
CPU#7.1,1350_8_CPU_NR6_UPG#7.1,1350_8_CPU_MNT#7.1
,1350_4_CPU_HA_NR6_UPG#7.1,1350_4_CPU_HA_PLTFM#7.1,1350_6_CPU_HA_NR6_
UPG#7.1,1350_6_CPU_HA_PLTFM# 7.1,1350_8_CPU_HA_NR6_UPG#7.1,1350_8_
CPU_HA_PLTFM#7.1
<date/time stamp> ipb062 Global/PMC2: IMSERVER System status change:
STOP --> WORKING
<date/time stamp> ipb062 Global/PMC2: IM LICENSE RESULT: command =
START system
- Execution denied and Force system shutdown
CAUSE: license library error
<date/time stamp> ipb062 Global/PMC2: IMSERVER System status change:
WORKING --> STOP
...................................................................................................................................................................................................
5 Check the Poseidon license server upgrade and eventually restart. See Poseidon License
server restart.
...................................................................................................................................................................................................
7 Restart the Kerberos application. Stop and start Kerberos services. See “Kerberos
Configuration” (p. 11-16) section.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
11-20 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Remove the WDM Component from the 1350 OMS
System Installation and Customization
....................................................................................................................................................................................................................................
Related information
This task does not have any related information.
Task
Use this task to remove the WDM component from the 1350 OMS if the Remove.sh
-product WDM official patch is not available.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 11-21
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Remove the WDM Component from the 1350 OMS
System Installation and Customization
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 Enter the following command lines to remove the NMS and NMA directories:
rm -rf /alu/1350OMS9.5/NMS/WDM
rm -rf /alu/1350OMS9.5/NMA/SONET_GUISERVER
rm -rf /alu/1350OMS9.5/NMA/WDM_APPL
rm -rf /alu/1350OMS9.5/NMA/WDM_DB
rm -rf /alu/1350OMS9.5/NMA/WDM_GUISERVER
rm -rf /alu/1350OMS9.5/NMA/WDM_GWS
rm -rf /alu/1350OMS9.5/NMA/WDM_ORBIX
rm -rf /alu/1350OMS9.5/NMA/WDM_PLATFORM
rm -rf /alu/1350OMS9.5/NMA/WDM_REMOTE_EOMS
rm -rf /alcatel/NMS/WDM
rm -rf /alcatel/NMA/SONET_GUISERVER
rm -rf /alcatel/NMA/WDM_APPL
rm -rf /alcatel/NMA/WDM_DB
rm -rf /alcatel/NMA/WDM_GUISERVER
rm -rf /alcatel/NMA/WDM_GWS
rm -rf /alcatel/NMA/WDM_ORBIX
rm -rf /alcatel/NMA/WDM_PLATFORM
rm -rf /alcatel/NMA/WDM_REMOTE_EOMS
...................................................................................................................................................................................................
Important Notes
After the WDM application has been removed, continue to do the following:
• Perform a new WDM installation, custom, and system configuration.
• For an upgrade to the same WDM load, reload the same WDM using the following
commands:
cd /alu/Install_Wizard
....................................................................................................................................................................................................................................
11-22 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Remove the WDM Component from the 1350 OMS
System Installation and Customization
....................................................................................................................................................................................................................................
./Install.sh -force WDM
• In the system configuration phase, the MIB value of ORACLE_DB should be set
always to NEW. The load-to-load upgrade operation is not supported.
....................................................................................................................................................................................................................................
1350 OMS 11-23
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Troubleshoot Product Installation Failures (no space/file
Product Installation busy)
....................................................................................................................................................................................................................................
Product Installation
Related information
This task does not have any related information.
Task
Complete the following steps if the installation of the 1350 OMS fails.
...................................................................................................................................................................................................
3 If the problem that was encountered during installation was no space available, you will
need to extend the file system or the swap area.
To extend the file system, go to step Step 4.
To extend the swap area, go to step Step 5.
If you received the message
Access denied for remote hosts or local hosts during installation, go to
step Step 6.
...................................................................................................................................................................................................
4 If the problem encountered during installation was no space available, use the following
steps to extend a file system:
Enter the bdf command to get information about file system sizes.
To extend a file system, enter the following command line:
/SCINSTALL/bin/scextendfs <Filesystem name> <free disk space>
....................................................................................................................................................................................................................................
11-24 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Troubleshoot Product Installation Failures (no space/file
Product Installation busy)
....................................................................................................................................................................................................................................
Where:
• <filesystem name> is the name of the file system to be extended.
• <free disk space> is the total amount of disk space (in Megabytes) that will have
to be available after the scextendfs execution.
If the <filesystem name> does not exist, the command will create it.
According to the installation on the machine, keep following files controlled:
• The core file in the maintenance/core directory.
• The GEM server trace files under the EML instance directory.
• The DB log (Mirror Area) under the EML instance directory:
/usr/Systems/<INSTANCE>>/MirrorArea/axadmin/arch/<hostname>-bin.*
Delete the .arc files if necessary.
• The DB log (Mirror Area) under the SDH instance directory:
/usr/Systems/<INSTANCE>/MirrorArea/SDH_1-9.5.0/snml/arch
Delete the .arc files if necessary.
Example:
/usr/Systems/SDH_1_9.5.0_Master/MirrorArea/SDH_1-9.5.0/snml/arch
• The DB log (Mirror Area) under the PKT instance directory:
/usr/Systems/<INSTANCE>/MirrorArea/PKT_1-9.5.0/bmm/arch
Delete the .arc files if necessary.
Example:
/usr/Systems/PKT_1_9.5.0_Master/MirrorArea/PKT_1-9.5.0/bmml
Note: After you extend the file system, remember to force the packages installation
with the -force parameter. For example:
Install <SDH/EML/PKT/...> -force
...................................................................................................................................................................................................
5 If the problem encountered during installation was no space available, use the following
steps to extend a swap area:
Enter the swapinfo -t command to get information about the swap area.
To extend the swap area, enter the following command:
scextendfs SWAP xxxx
Execute a ps -ef | grep xxxx to have the PID of the process that block the copy and
stop the process using the command kill -9.
....................................................................................................................................................................................................................................
1350 OMS 11-25
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Troubleshoot Product Installation Failures (no space/file
Product Installation busy)
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
6 If you are installing a component from a local depot (and not the standard product
component repository) and you receive an
Access denied for remote hosts or local hosts message, verify the
security files that are authorizing access by remote hosts and users on local host.
For example, in the /.rhosts file, the line 151.98.28.227 root should be present.
This line allows the root user to execute any command on the 151.98.28.227 host.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
11-26 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Upgrade the MW-OS Application
Product Installation
....................................................................................................................................................................................................................................
Related information
This task does not have any related information.
Task
Complete the following steps to upgrade the MW-OS application.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
11-28 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Configure and Test the Centralized User-DB in a Distributed
Product Installation Environment
....................................................................................................................................................................................................................................
Related information
This task does not have any related information.
Task
Complete the following steps to configure and test the Centralized User-DB in a
distributed environment.
...................................................................................................................................................................................................
3 From the configuration that you created, perform the following basic tests:
1. As administrator, connect to each machine belonging to the TMN configuration.
2. Create a few new users. When creating the new users, include profile assignments.
3. For each newly created user, log in to each of the machines and verify that the profile
assignment menus that you enabled for the particular user are available. Base the
verification on the same content that is in the Distributed Configuration. Problems
related to profile content are not impacted by this feature.
4. Backup/Restore the users.
Other tests can be extended to have an exhaustive coverage of the features; but, the tests
that are provided in this step cover the tests that are not done in a security environment
(profile administration).
E...................................................................................................................................................................................................
N D O F S T E P S
SECTION: INDEX
GLOBAL_SERVICE: USER_LDAP_SERVER_HOST
GLOBAL_SERVICE: USER_LDAP_SPARE_HOST
GLOBAL_SERVICE: USER_LDAP_DOMAIN_SUFFIX
GLOBAL_SERVICE: USER_LDAP_DOMAIN_ADMINGROUP
GLOBAL_SERVICE: USER_LDAP_DOMAIN_ROOTDN
GLOBAL_SERVICE: USER_LDAP_DOMAIN_ROOTPW
GLOBAL_SOCKET: USER_LDAP_SERVER_SOCKET_PORT
GLOBAL_SOCKET: USER_LDAP_SERVER_SSL_PORT
GLOBAL_SOCKET: USER_LDAP_SPARE_SOCKET_PORT
....................................................................................................................................................................................................................................
11-30 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Configure and Test the Centralized User-DB in a Distributed
Product Installation Environment
....................................................................................................................................................................................................................................
GLOBAL_SOCKET: USER_LDAP_SPARE_SSL_PORT
SECTION_END:
SECTION: USER_LDAP_SERVER_HOST
SERVICE_VALUE: <LDAP SERVER IP ADDRESS>
KEYWORD_NAME: USER_LDAP_SERVER_HOST
SECTION_END:
SECTION: USER_LDAP_SPARE_HOST
SERVICE_VALUE:<NMS_LOCAL_IPADDRESS>
KEYWORD_NAME: USER_LDAP_SPARE_HOST
SECTION_END:
SECTION: USER_LDAP_DOMAIN_SUFFIX
SERVICE_VALUE: dc=alcatel,dc=com
KEYWORD_NAME: USER_LDAP_DOMAIN_SUFFIX
SECTION_END:
SECTION: USER_LDAP_DOMAIN_ADMINGROUP
SERVICE_VALUE: AdminGroup
KEYWORD_NAME: USER_LDAP_DOMAIN_ADMINGROUP
SECTION_END:
SECTION: USER_LDAP_DOMAIN_ROOTDN
SERVICE_VALUE: LdapMgr
KEYWORD_NAME: USER_LDAP_DOMAIN_ROOTDN
SECTION_END:
SECTION: USER_LDAP_DOMAIN_ROOTPW
SERVICE_VALUE: mGr*LDAP
KEYWORD_NAME: USER_LDAP_DOMAIN_ROOTPW
SECTION_END:
SECTION: USER_LDAP_SERVER_SOCKET_PORT
SERVICE_NUMBER:<LDAP PORT NUMBER>
SERVICE_NAME: ldap
KEYWORD_NAME: USER_LDAP_SERVER_SOCKET_PORT
SECTION_END:
SECTION: USER_LDAP_SERVER_SSL_PORT
SERVICE_NUMBER:<LDAP SSL PORT NUMBER>
SERVICE_NAME: ldaptls
KEYWORD_NAME: USER_LDAP_SERVER_SSL_PORT
SECTION_END:
SECTION: USER_LDAP_SPARE_SOCKET_PORT
SERVICE_NAME: spareldap
KEYWORD_NAME: USER_LDAP_SPARE_SOCKET_PORT
SECTION_END:
SECTION: USER_LDAP_SPARE_SSL_PORT
SERVICE_NAME: spareldaptls
KEYWORD_NAME: USER_LDAP_SPARE_SSL_PORT
SECTION_END:
....................................................................................................................................................................................................................................
1350 OMS 11-31
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Configure and Test the Centralized User-DB in a Distributed
Product Installation Environment
....................................................................................................................................................................................................................................
Note: The parameters that you must specify values for are the following:
• <LDAP SERVER IPADDRESS> is the IP address of the machine that acts/runs the
Centralized User-DB.
• <LDAP PORT NUMBER> is the ldap socket port used by the LDAP that is acting as
the Centralized User-DB.
• <LDAP SSL PORT NUMBER> is the ldap SSL socket port that is used by the LDAP
that is acting as the Centralized User-DB
If you do not know which port numbers to use, use the port numbers that other
applications are currently not using on the server. Check the /etc/services file for the
full list of port numbers that are currently in use. If you want to assign port numbers
before you install the machine, we recommend that you use the following ports
because they are typically free of IANA port number assignments:
• <LDAP PORT NUMBER> : 4992
• <LDAP SSL PORT NUMBER> : 4993
Note: Beginning with the 1350OMS 9.1.0.8.7 release, a template of the option file is
available as:
/alu/Install_Wizard/etc/UserDBOptions.cfg.template
This template must be customized with the specific host and ports values.
....................................................................................................................................................................................................................................
11-32 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Overview
Product Customization
....................................................................................................................................................................................................................................
Product Customization
Overview
Purpose
This section contains procedures that are useful for 1350 OMS product customizations.
Contents
Customize a 1350 OMS Component while Other Components Are Running 11-34
Perform a Manual Customization/De-customization (without using the Install 11-36
Wizard)
Perform a Fast Customization of the MS-GUI Package 11-38
Customizing WDM to Exclude the Remote eOMS 11-40
....................................................................................................................................................................................................................................
1350 OMS 11-33
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Customize a 1350 OMS Component while Other Components
Product Customization Are Running
....................................................................................................................................................................................................................................
Related information
This task does not have any related information.
Task
...................................................................................................................................................................................................
0 --> RUN
1 --> WRONG
2 --> STOP
4 --> CHANGE in progress
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 11-35
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Perform a Manual Customization/De-customization (without
Product Customization using the Install Wizard)
....................................................................................................................................................................................................................................
Related information
This task does not have any related information.
Task
Complete the following steps to perform a manual customization/de-customization
(without using the Install Wizard).
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 11-37
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Perform a Fast Customization of the MS-GUI Package
Product Customization
....................................................................................................................................................................................................................................
Related information
This task does not have any related information.
Task
Complete the following steps to perform a fast customization of the MS-GUI package.
...................................................................................................................................................................................................
2 Download the MSGUI software packages from the depot directory /alu/DEPOT.
...................................................................................................................................................................................................
4 Enter the following command line to customize and configure the MS-GUI:
cd /alu/Install_Wizard/etc/1350_ConfigMSGUI.sh
...................................................................................................................................................................................................
5 When the customization and configuration phase is finished, enter the following
command line on the master machine to re-enable the navigation to the EML external
application:
....................................................................................................................................................................................................................................
11-38 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Perform a Fast Customization of the MS-GUI Package
Product Customization
....................................................................................................................................................................................................................................
/alu/Kernel/bin/CustomNavigations.pl -sys EML -inst 1-9.5.0 -
isys EML -iinst 1-9.5.0
Note: In this example, the EML instance is 1.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 11-39
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Customizing WDM to Exclude the Remote eOMS
Product Customization
....................................................................................................................................................................................................................................
Related information
This task does not have any related information.
Task
Complete the following step to customize WDM so it excludes the remote eOMS.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
11-40 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting PMC2 Process Monitoring
System Applications Management
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 11-41
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting PMC2 Process Monitoring
System Applications Management
....................................................................................................................................................................................................................................
VIEW permission denied for system services or product
If the VIEW permission is denied, the two possible causes are the following:
• The user has tried to open the Process Monitor GUI too quickly and the system could
be still managing the security configuration structures. Retry to open the Process
Monitor GUI after a few seconds.
• If the problem still occurs, some ldap database structure could be damaged. If the
problem is related to the Global Instance, a work around could be to rebuild the
Global Instance ldap database.
Otherwise, if the problem is related to a specific process instance (e.g. EML_1,
SDH_1, PKT_1, ....), a work around would be to rebuild the process ldap database.
If the problem is related to more than one system, rebuild the entire ldap database.
1 Edit the /alu/Kernel/data/Semaphores.cfg file to change the duplicated value with a new
one.
For example PMC2_EOMS_1-9.5.0: 7187
In this case, the product and the instance involved are EOMS_1. (PR_IS in the text.)
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 11-43
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting SAS, UDM, LDAP
System Applications Management
....................................................................................................................................................................................................................................
1 To clean and repopulate ONLY the Global Instance database, enter the following
commands as the root user:
cd /usr/Systems/Global_Instance/LDAP
./script/Stop_LDAP_Service
rm -f data/db/*
/usr/sbin/slapadd -f conf/slapd.conf -l data/ldap_entry.ldif
find . -name /*.imported | /usr/local/bin/perl -ne 'chomp;$t=$_;s/
imported/import/;rename($t,$_)'
cp -p conf/DB_CONFIG data/db/
./script/Start_LDAP_Service
cd ../SEC/repository
find . -name /*.fad.imported | /usr/local/bin/perl -ne 'chomp;$t=$_;
s/fad.imported/fad/;rename($t,$_)'
find . -name /*.imported | /usr/local/bin/perl -ne 'chomp;$t=$_;s/
imported/import/;rename($t,$_)'
cd ../integration/script
/configSEC.pl Global Instance version
...................................................................................................................................................................................................
2 To clean and repopulate ONLY a product Instance database, enter the following
commands as the root user:
If EML_1 is the current EML instance, NMS_USER is axadmin (password is 1353sh); if
SDH_1 is the current SDH instance, NMS_USER is snml (password is system1); if
PKT_1 is the current PKT instance, NMS_USER is bmml (password is system1); if
WDM_1 is the current WDM instance, NMS_USER is wdm (password is lucent!123); if
EOMS_1 is the current EOMS instance, NMS_USER is oms (password is lucent!123).
cd /usr/Systems/<current instance>/LDAP
./script/Stop_LDAP_Service
rm -f data/db/*
/usr/sbin/slapadd -f conf/slapd.conf -l data/ldap_entry.ldif
find . -name /*.imported | /usr/local/bin/perl -ne 'chomp;$t=$_;s/
imported/import/;rename($t,$_)'
cp -p conf/DB_CONFIG data/db/
./script/Start_LDAP_Service
....................................................................................................................................................................................................................................
11-44 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting SAS, UDM, LDAP
System Applications Management
....................................................................................................................................................................................................................................
cd ../SEC/repository
find . -name /*.fad.imported | /usr/local/bin/perl -ne 'chomp;$t=$_;
s/fad.imported/fad/;rename($t,$_)'
find . -name /*.imported | /usr/local/bin/perl -ne 'chomp;$t=$_;s/
imported/import/;rename($t,$_)'
su <NMS_USER>
cd ../integration/script
./configSEC.pl <system> <instance with version>
exit
# cd /usr/Systems/EML_1_9.5.0_Master/LDAP/data/export/
# rm ExportedLDAPDB.ldif.gz ExportedUserDB.ldif.gz
# /usr/Systems/EML_1_9.5.0_Master/LDAP/script/ExportImportLdapDb.pl
export EML_1_9.5.0 notinteract
The lastest LDAP backup files are the following
/usr/Systems/EML_1_9.5.0_Master/LDAP/data/export/ExportedLDAPDB.ldif.gz
/usr/Systems/EML_1_9.5.0_Master/LDAP/data/export/ExportedUserDB.ldif.gz
1 Create the file to be imported (import.ldif), with the list of users to add to the
AdminGroup:
....................................................................................................................................................................................................................................
1350 OMS 11-45
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting SAS, UDM, LDAP
System Applications Management
....................................................................................................................................................................................................................................
dn:cn=AdminGroup,dc=alcatel,dc=com
objectClass: groupOfNames
member: cn=alcatel
member: cn=admin
[add other users if needed]
cn: AdminGroup
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
11-46 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Web Desktop Administration
System Applications Management
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
11-48 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Web Desktop Administration
System Applications Management
....................................................................................................................................................................................................................................
Select the user alcatel in the tree on the left panel and click on the Set Password
button on the bottom of the window. Enter and confirm the new password in the popup
window and confirm it with the Change button.
Execute the following command line to find the PID for SAS process.
ps -ef|grep DSAS|grep -v grep
Execute the following command:
kill -9 PID
Where: PID is the pid of the SAS process that was previously found.
....................................................................................................................................................................................................................................
1350 OMS 11-49
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Web Desktop Administration
System Applications Management
....................................................................................................................................................................................................................................
UDM problems
If you receive the following message under other windows and you do not acknowledge
this message, the Web Portal cannot be displayed:
UDM manager is not responding, user preference can not be loaded.
Note: Sometimes the UDM server does not respond even if it is running correctly.
Many times, you can remove the UDM problem by scratching the UDM persistency
files; but, be aware that this operation will remove all user settings:
/usr/Systems/Global_Instance/WACOMO/udm/udmrt/script/Stop_UDM_
Service
cd /usr/Systems/Global_Instance/WACOMO/udm/data/persistency/
rm -rf *
/usr/Systems/Global_Instance/WACOMO/udm/udmrt/script/Start_
UDM_Service
The UDM should now be able to get user connections.
Process blocked on a port
Enter the following command to determine which process uses a port (for example.
ssoLsmPort):
lsof | grep TCP | grep ssoLsmPort
If sockets are blocked on LISTEN:
lsof | grep TCP | grep ssoLsmPort | grep LISTEN | while read uno
pid due;
do kill -9 $pid; done
If blocked on a port (for example: ssoLsmPort):
lsof | grep TCP | grep ssoLsmPort | while read uno pid due; do
kill -9 $pid; done
Also see “Application does not start (needs an already used port)” (p. 11-65).
User <user name> not authenticated
If the following message is displayed:
User alcatel not authenticaed. Please retry.
The problem is due to one of the following
• The password is not correct. Please verify it.
• The LDAP database is corrupt. See “SAS, UDM, LDAP” (p. 11-44) to clean/rebuild
the database.
....................................................................................................................................................................................................................................
11-50 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Web Desktop Administration
System Applications Management
....................................................................................................................................................................................................................................
SSO Password Policy
Password settings can be changed using the following configuration file:
/alu/NMC/SSO//SSO/servers/sas/config/sec/pwdpolicy.properties
The instance is on the following:
/usr/Systems/Global_Instance/SSO/sas/config/sec/pwdpolicy.properties
The Web Portal must be able to access these settings, so configure the following in the
SSO param.cfg file:
/alu/NMC/SSO_INT//templates/osktemplate/servers/sas/config/param.cfg
The instance is on the following:
/usr/Systems/Global_Instance/SSO/sas/config/param.cfg
Make the following change:
Change:
DEFAULT_PASSWORD_POLICY "cn=defaultPwdPolicy"
To:
DEFAULT_PASSWORD_POLICY "file:pwdpolicy.properties"
If you modify the instance files, you must activate the modifications using the following
procedure::
• Exit from all open Web Portals.
• Stop and restart the SAS process using following commands:
/usr/Systems/Global_Instance/SSO/sas/script/Stop_SAS_Service
/usr/Systems/Global_Instance/SSO/sas/script/Start_SAS_Service
The pwdpolicy.properties file, with the default content, follows:
# ----------------------#
# DefaultPasswordPolicy #
# ----------------------#
# The following parameters are used to define a password policy.
# This one can then be populated into LDAP using policy.pl
# tool and references by DEFAULT_PASSWORD_POLICY parameters.
# However, this file can be also directly referenced by
# DEFAULT_PASSWORD_POLICY to be used as default password policy by
SAS.
# IMPORTANT NOTICE:
# In case this file is directly referenced, it is found in
# the order specified in the classpath parameter
# of the java command. The default order where this file should be
found
# (as defined in the classpath used in the start_sas.pl script) is:
# 1) in /sas/config
....................................................................................................................................................................................................................................
1350 OMS 11-51
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Web Desktop Administration
System Applications Management
....................................................................................................................................................................................................................................
# 2) in /data/server
# 3) in /sas/template/config
#
# Therefore, if you are using SEC, you should just check that /data/
server/.properties
# points to the correct SEC Server file or LDAP entry (this insures
that the exact same
# policy is used for SEC and for AWP Change Password feature).
# Otherwise you can just copy this file into /sas/config
# and modify it according to your requirements.
# DefaultPasswordPolicy parameters:
# ----------#
# MinLength #
# ----------#
# minimum number of mandatory charaters in the password
# The value can be specified either using the historical SEC
parameter
# or the new password policy parameter built from the LDAP schema.
# If both are specified, only the historical SEC paramater will be
# taken into account.
# Hardcoded value is 8
#com.alcatel.almap.sec.defaultPasswordPolicy.MinLength =8
almapPwdPolicy.almapPwdMinLength=8
# ----------#
# MinDigits #
# ----------#
# number of digits mandatory in the password
# The value can be specified either using the historical SEC
parameter
# or the new password policy parameter built from the LDAP schema.
# If both are specified, only the historical SEC paramater will be
# taken into account.
# Hardcoded value is 1
#com.alcatel.almap.sec.defaultPasswordPolicy.MinDigits=1
almapPwdPolicy.almapPwdMinDigit=1
# -----------#
# MinLetters #
# -----------#
# number of letters (uppercase or lowercase) mandatory in the
password
# The value can be specified either using the historical SEC
parameter
# or the new password policy parameter built from the LDAP schema.
# If both are specified, only the historical SEC paramater will be
# taken into account.
# The paramater almapPwdPolicy.almapPwdMinLetter can also be used
# Hardcoded value is 4
#com.alcatel.almap.sec.defaultPasswordPolicy.MinLetters=4
almapPwdPolicy.almapPwdMinLetter=4
# ------------#
....................................................................................................................................................................................................................................
11-52 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Web Desktop Administration
System Applications Management
....................................................................................................................................................................................................................................
# MinSpecials #
# ------------#
# number of special characters mandatory in the password
# The value can be specified either using the historical SEC
parameter
# or the new password policy parameter built from the LDAP schema.
# If both are specified, only the historical SEC paramater will be
# taken into account.
# The special characters list is specified in parameter
# almapPwdPolicy.almapPwdSpecialCharList.
# Hardcoded value is 2
#com.alcatel.almap.sec.defaultPasswordPolicy.MinSpecials=2
almapPwdPolicy.almapPwdMinSpecial=2
# ------------------------#
# almapPwdSpecialCharList #
# ------------------------#
# list of characters that should be considered as special
# when enforcing a minimum number of special characters policy (see
# almapPwdMinSpecial)
# WARNING : for specific / and " character, do not forget to preceed
it by a /
# Hardcoded value is `~!@#$%
&*()_+-={}|[]/:";'<>?,./
almapPwdPolicy.almapPwdSpecialCharList=`~!@#$%
&*()_+-={}|[]//:/";'<>?,./
# ---------------#
# MinUppperCases #
# ---------------#
# number of letters in upper case mandatory in the password
# The value can be specified either using the historical SEC
parameter
# or the new password policy parameter built from the LDAP schema.
# If both are specified, only the historical SEC paramater will be
# taken into account.
# Hardcoded value is 1
#com.alcatel.almap.sec.defaultPasswordPolicy.MinUppperCases=1
almapPwdPolicy.almapPwdMinUpperCase=1
# --------------#
# MinLowerCases #
# --------------#
# number of letters in lower case mandatory in the password
# The value can be specified either using the historical SEC
parameter
# or the new password policy parameter built from the LDAP schema.
# If both are specified, only the historical SEC paramater will be
# taken into account.
# Hardcoded value is 1
#com.alcatel.almap.sec.defaultPasswordPolicy.MinLowerCases=1
almapPwdPolicy.almapPwdMinLowerCase=1
# --------------------------#
....................................................................................................................................................................................................................................
1350 OMS 11-53
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Web Desktop Administration
System Applications Management
....................................................................................................................................................................................................................................
# almapPwdNbConsecutiveChar #
# --------------------------#
# maximum number of consecutive characters that can
# be used in a password. If value is set to 0,
# no restriction will apply.
# Hardcoded value is 2
almapPwdPolicy.almapPwdNbConsecutiveChar=2
# -------------------------#
# almapPwdNoUidCombination #
# -------------------------#
# indicates if the password can or cannot be a case-independent
# re-arrangement of the letters composing the user id (e.g. if the
user id is
# "hantz", the password can or cannot be "ZaNth".
# Hardcoded value is false
almapPwdPolicy.almapPwdNoUidCombination=false
# ----------------------#
# almapPwdMayContainUid #
# ----------------------#
# indicates if the password can or cannot contain
# (case-independently) the user id (e.g. if the user id is
# "hantz", the password can or cannot be "pwdHAnTZ01".
# Hardcoded value is true
almapPwdPolicy.almapPwdMayContainUid=true
# ------------------#
# almapPwdInHistory #
# ------------------#
# maximum number of used passwords stored in the password
# history. If value is 0, used password are not stored
# and may be reused.
# Hardcoded value is 5
almapPwdPolicy.almapPwdInHistory=5
# ---------------#
# almapPwdMinAge #
# ---------------#
# Number of seconds that must elapse since the previous
modification
# before the password can be changed again
# Hardcoded value is 86400 seconds (1 day)
almapPwdPolicy.almapPwdMinAge=86400
# ---------------#
# almapPwdMaxAge #
# ---------------#
# number of seconds after which a modified password will expire.
# If the value is set to 0, the password does not expire.
# the value must be greater than or equal to the value of
almapPwdMinAge
# Hardcoded value is 7776000 seconds (90 days)
almapPwdPolicy.almapPwdMaxAge=7776000
....................................................................................................................................................................................................................................
11-54 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Web Desktop Administration
System Applications Management
....................................................................................................................................................................................................................................
# ----------------------#
# almapPwdExpireWarning #
# ----------------------#
# number of seconds which is the period before a password is due to
expire.
# During this period (expirationDate - almapPwdExpireWarning), the
user
# will be notified at login that his password will expire soon and
that
# he should change it. Note that the value must be less than
almapPwdMaxAge.
# If the value is 0, then no warning will be issued before the
password
# expires.
# Hardcoded value is 2592000 (30 days)
almapPwdPolicy.almapPwdExpireWarning=2592000
# -----------------------------#
# almapPwdExpirationGraceDelay #
# -----------------------------#
# number of seconds after a password expiration during which the
user will
# still be allowed to login but will be forced to change his
password.
# After password expiration + grace delay (grace delay can be 0),
# the account is automatically locked,
# Hardcoded value is 1296000 (15 days)
almapPwdPolicy.almapPwdExpirationGraceDelay=1296000
# -------------------#
# almapPwdMaxFailure #
# -------------------#
# number of consecutive failed authentication attempts after which
the
# authentication is locked.
# Hardcoded value is 5
almapPwdPolicy.almapPwdMaxFailure=5
# -----------------------------#
# almapPwdFailureCountInterval #
# -----------------------------#
# Amount of time in seconds after which the authentication failure
attempt
# number is reset, even though no successful authentication
occurred.
# If the value is set to 0, the failure attempt number is only reset
by
# a successful authentication.
# Hardcoded value is 300 (5 minutes)
almapPwdPolicy.almapPwdFailureCountInterval=300
# ------------------------#
# almapPwdLockoutDuration #
# ------------------------#
....................................................................................................................................................................................................................................
1350 OMS 11-55
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Web Desktop Administration
System Applications Management
....................................................................................................................................................................................................................................
# Amount of time in seconds during which the password cannot be use
to
authenticate.
# If the value is set to 0, a reset of the administrator is
requested.
# Hardcoded value is 300 (5 minutes)
almapPwdPolicy.almapPwdLockoutDuration=300
# ------------------------#
# almapPwdMaxUnusedPeriod #
# ------------------------#
# Maximum amount of time in seconds after which, if no session has
been
opened,
# the password will be automatically locked.
# Hardcoded value is 0
almapPwdPolicy.almapPwdMaxUnusedPeriod=0
# ------------------#
# almapPwdAttribute #
# ------------------#
# the name of the attribute used as a password.
# Hardcoded value is userPassword
almapPwdPolicy.almapPwdAttribute=userpassword
# -------------------#
# almapPwdEncryption #
# -------------------#
# Indicates if the password should be encrypted or not before
# storing it into the LDAP directory
# Hardcoded value is true
almapPwdPolicy.almapPwdEncryption=true
# -----------------------#
# almapPwdMinDifferences #
# -----------------------#
# number of Differents in a number of character positions in the
password from
the last one
# Hardcoded value is 2
#almapPwdPolicy.almapPwdMinDifferences=2
almapPwdPolicy.almapPwdMinDifferences=2
....................................................................................................................................................................................................................................
11-56 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Cannot Connect to the Authentication Server
System Applications Management
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
11-58 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Work Arounds for the MS-GUI
System Applications Management
....................................................................................................................................................................................................................................
3 Enter the following command to restart the common server of the Global Instance:
ps -ef | grep -i comsvr_Global | grep -v grep | awk '{print $2}'
| xargs -i kill -9 {}
....................................................................................................................................................................................................................................
1350 OMS 11-59
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Work Arounds for the MS-GUI
System Applications Management
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
5 On the client machine, use ftp to manually retrieve the IntraSystemsNavigations.cfg file
from the /usr/Systems/EML_1/Kernel/data directory to the C:/tmp/runtimeDir/<host
ip address>/EML_1-9.5.0/Kernel/data client directory.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
11-60 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Work Arounds for the MS-GUI
System Applications Management
....................................................................................................................................................................................................................................
Recover menu items that are hidden/not sensitive
If menu items are hidden, for example EML, SDH, WDM, or PKT items are not
displayed on the Search menu, the reason can be one of the following:
1. The synchronization between SEC services and the common server is not correct.
Restart the common server using following command:
ps -ef | grep -i comsvr_Global | grep -v grep | awk '{print
$2}' | xargs -i kill -9 {}
Stop and restart the MSGUI.
2. If the previous action does not solve the problem, check the following file:
/usr/Systems/Global_Instance/COMMONSVR/conf/jacapi.properties
In the following line:
# list of the used sec servers, format=[ServerId/StandardNS/serverHost:serverPort,
serverId/StandardNS/serverHost:serverPort, ..]
com.alcatel.almap.sec.jacapi7.servers=1/PKT_1-9.5.0/151.98.179.80:5124,
2/WDM_1-9.5.0/151.98.179.80:5090,3/SDH_1-9.5.0/151.98.179.80:5055,4/EML_1-
9.5.0/151.98.179.80:5135
Insert the following:
SecServer_
Example:
# list of the used sec servers, format=[ServerId/StandardNS/serverHost:serverPort,
serverId/StandardNS/serverHost:serverPort, ..]
com.alcatel.almap.sec.jacapi7.servers=1/ SecServer_PKT_1-
9.5.0/151.98.179.80:5124,2/ SecServer_WDM_1-9.5.0/151.98.179.80:5090,3/
SecServer_SDH_1-9.5.0/151.98.179.80:5055,4/ SecServer_EML_1-
9.5.0/151.98.179.80:5135
Restart the common server using the following command:
ps -ef | grep -i comsvr_Global | grep -v grep | awk '{print
$2}' | xargs -i kill -9 {}
Stop and restart the MSGUI.
3. If the previous action does not solve the problem, a bad customization of the product
(e.g. EML) could exist. Stop the server for the product (see How to restart the
services) and re-customize the product.
If the items are present but not sensitive, the GUI server that is related to the system is not
correctly connected. See “Server is not correctly connected in the MS-GUI” (p. 11-62).
Only as an extreme work around, comment the content of the FADMapping.xml file:
/usr/Systems/Global_Instance-9.5.0/MSGUI/resources/FADMapping.xml
And restart the MS-GUI.
....................................................................................................................................................................................................................................
1350 OMS 11-61
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Work Arounds for the MS-GUI
System Applications Management
....................................................................................................................................................................................................................................
Server is not correctly connected in the MS-GUI
If the server is not correctly connected in the MS-GUI, look in the menu files, button
properties:
• If PKT is not connected, restart PktGuiServer on the master (or presentation )
machine. Find the PID with the following command:
ps -ef | grep -i PktGui
Enter the following command:
Kill -9 PID
• If MAP is not connected, restart TopoGuiServer on the master (or presentation )
machine. Find the PID with the following command:
ps -ef | grep -i Topo
Enter the following command:
Kill -9 PID
• If TDM is not connected, restart TdmGuiServer on the master (or presentation )
machine. Find the PID with the following command:
ps -ef | grep -i TdmGui
Enter the following command:
Kill -9 PID
• If TM is not connected, restart PnmGs on the master (or presentation ) machine. Find
the PID with the following command:
ps -ef | grep -i Pnm_GS
Enter the following command:
Kill -9 PID
• If WDM is not connected, restart the WDM GUI server on the master (or presentation
) machine.
The WDM GUI server can be restarted using the following procedure:
Login as wdm user.
Enter the following command lines:
/usr/Systems/WDM_1/guiServer/wdm/script/wdm_stop.sh
/usr/Systems/WDM_1/guiServer/wdm/script/wdm_start.sh
/usr/Systems/WDM_1/guiServer/sonet/script/sonet_stop.sh
/usr/Systems/WDM_1/guiServer/sonet/script/sonet_start.sh
....................................................................................................................................................................................................................................
11-62 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Work Arounds for Database Management
System Applications Management
....................................................................................................................................................................................................................................
su - snml
. /snml1/.snmlrc
....................................................................................................................................................................................................................................
1350 OMS 11-63
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Work Arounds for Database Management
System Applications Management
....................................................................................................................................................................................................................................
/usr/Systems/SDH_1/ORACLE/databases/dbnml/etc/stop_db immediate
/usr/Systems/SDH_1/ORACLE/databases/dbnml/etc/start_db
Note: To determine if there is enough disk space, execute the following command:
su - snml
. /snml1/.snmlrc
sqlplus sys/manager as sysdba
If the space is reduced, enter the following command to remove archive files
usr/Systems/SDH_1_9.5.0_Master/MirrorArea/SDH_1-9.5.0/snml/arch:
rm *.arch
/opt/lucent/oms/oms_setup
/opt/lucent/cache/cache_setup
/opt/lucent/platform/bin/lt_add_controller -install
/opt/lucent/platform/bin/lt_add_controller -type NMA -name EML_1_NMA
....................................................................................................................................................................................................................................
11-64 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting General Work Arounds for Application Problems
System Applications Management
....................................................................................................................................................................................................................................
ascurim_corba_socket_EOMS_1-9.5.0 5087/tcp
# Added by OS-Kernel (Relocatable Service) <date/time stamp>
ASCURIM__1_EOMS_1-9.5.0 5175/tcp
# Added by OS-Kernel (Relocatable Service) <date/time stamp>
ASCURIM__2_EOMS_1-9.5.0 5176/tcp
# Added by OS-Kernel (Relocatable Service) <date/time stamp>
Use the command netstat -an | grep 5175 to display the state of the port. Output
similar to the following is displayed:
Oracle monitor application is down but there are active oracle processes
If the oracle_monitor_process is down but the command
ps -u axadmin | grep oracle returns an existing process, we suggest that you, as
the axadmin user on EML master server, manually shutdown the current oracle instance.
Note: oracle is also the password that you have to enter.
cd /usr/Systems/EML_*Master/eml/EMLIMSNA/script/
. set_sna_env
sqlplus /nolog
SQL*Plus: Release 10.2.0.3.0 - Production on <date/time stamp>
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
SQL> connect as sysdba;
Enter user-name: oracle
Enter password: Connected.
SQL> shutdown abort;
....................................................................................................................................................................................................................................
11-66 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Work Arounds for File System Management
System Applications Management
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 11-67
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Work Arounds for File System Management
System Applications Management
....................................................................................................................................................................................................................................
To completely clean PKT tables, complete the following steps
1. Stop all PKT applications, except Oracle Database.
2. Connect to the system using the su -bmmml command.
3. Launch the following script:
/usr/Systems/PKT_1/databases/dbbmml/admin/create/
CleanTables.sh
4. Restart the PKT application.
....................................................................................................................................................................................................................................
11-68 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Abbreviations
NMA Basic Debug/Configuration Notes
....................................................................................................................................................................................................................................
Logging
Description
The NMA includes two basic sets of logs, each of which can be modified while the server
is up-and-running:
• Debug/Trace logs, which trace the NMA server actions.
• TL1 logs, which trace the TL1 sent to and received from the NE messages.
Trace/Debug logs
Trace logs are located in the maintenance/gemtrace directory. The basic log files are the
following:
• gemServer_ems.trace
• gemServer_ems.error
• tmfserver.trace
• tmfserver.error
• jboss_gemServer_ems.log
When logs reach a maximum size, a new log file is created and the old logs are
renumbered. The logs contain the following:
• gemServer_ems.trace and gemServer_ems.error
These logs contain tracing for NMA logged from NMA code. If NMA catches an error
and logs it, it will be in these files. At the default INFO level, this log contains major
events such as starting/completing domain alignment and TL1 commands and their
time to completion (TL1 responses are not logged here).
• tmfserver.trace and tmfserver.error
These logs contain tracing for the TMF server.
• jboss_gemServer_ems.log
This file contains log records from JBoss itself, which includes error messages from
exceptions that are thrown by NMA, but are not caught by NMA (caught by JBoss) .
Additionally, a jboss_gemServer.stdout file captures the standard output of the Java
process. Generally, this file is not used, but thread dumps are written to this file.
These log files are based on a log4j logging package from the Apache group
(http://logging.apache.org). The log4j-defined server-configuration file that controls
logging for the TMF server is the following:
TMF/data/log4j.tmfServer.xml
This file, which can be modified, is located in the following directory:
EMLIMGEM3/jboss/server/ems/conf/log4j.xml
....................................................................................................................................................................................................................................
1350 OMS 11-69
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Logging
NMA Basic Debug/Configuration Notes
....................................................................................................................................................................................................................................
The logging system is based on a hierarchy of named loggers, the base of which is
com.alcatel.gem.trace.
Two additional loggers are the following:
– com.alcatel.gem.trace.tl1pc
– com.alcatel.gem.trace.exsnmp
Jboss logging is also based on the same log4j package and detailed logging of JBoss
is also possible. A sample file (Log4J.xml) gives examples for turning on more
detailed JBoss logging, shows how to write to new files, and shows how to set the log
level to specific values for various named loggers.
TL1 logs
TL1 logs are also implemented using log4j, but are not controlled by a typical log4j
configuration file because the logger names are the NE names are therefore dynamic.
Configuration of these files is through the typical configuration used by end users.
TL1 logs are at a low level and they are unprocessed other than basic TL1 parsing. The
content of the TL1 log is basically what comes from the NE−the exact text of the TL1
command, responses, events, and acknowledgements. RTRV-PM commands/responses
are filtered out by defaul, which is controlled by a configuration value.
The TL1 log also shows entries when a session is opened, closed, and fails. TL1
command failure is also logged. One TL1 log file is set for each NE that rolls based on
time (not size) and thus can get large.
The following file:
EMLIMGEM3/jboss/server/ems/deploy/properties-service.xml
contains configuration parameters to control the TL1 logs. Most parameters are well
documented in the XML comments in this file. Changes to TL1 logging do not take affect
until supervision is stopped and restarted. The server does not have to be restarted.
Two additional parameters are available:
• tl1comm.neLogMaxDaysKept determines the number of days of TL1 logs that are
kept. The default is 7. The value can range from [1, 14].
• If tl1comm.includeInLogPM is true, RTRV-PM-* commands and responses are
included in the TL1 logs.
....................................................................................................................................................................................................................................
11-70 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Logging
NMA Basic Debug/Configuration Notes
....................................................................................................................................................................................................................................
The configuration file EMLIMGEM3/jboss/server/ems/deploy/properties-service.xml
can also contain these values.
The following configuration parameters control this logging:
• neIOLogPath controls which directory these I/O logs are created in. The directory
must already exist.
• neIOLogFlag controls the logging. Possible values are in, out, or both. Any other
value implies the feature is off. The in value logs all input from the NE. The out value
logs all output to the NE, and both logs both input and output.
Possible values are the following
– in logs all input to the NE
– out logs all output from the NE.
– both logs both input and output to the NE.
– Any other value besides in, out, or both implies that the feature is off.
When turned on, at supervision time, a file named tl1io_xxxxx.debug is be created that
contains all characters sent over this socket based on the configuration. If multiple NEs
are sharing the same socket (GNE with RNEs), all characters are logged to the same file.
This is a character-by-character log and has no knowledge of TL1 of the NEs involved.
This file also never rolls. Everything from socket open to close is logged into the same
file and the file is never removed. It must be manually removed. Changes to this
configuration require stopping/starting supervision. You should only use this log to debug
cases where the NE generates illegal TL1 that the normal parsing rejects and thus is not
seen in the normal TL1 logs. Do not leave this logging on for long time because you will
run out of disk space.
....................................................................................................................................................................................................................................
1350 OMS 11-71
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Configuration
NMA Basic Debug/Configuration Notes
....................................................................................................................................................................................................................................
Configuration
Description
The NMA/JBoss combination includes a large number of configuration files to control,
but NMA only adds a few of its own. One is designated for parameters that the end user
can modify. Others should be determined at installation time and not changed.
....................................................................................................................................................................................................................................
11-72 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Configuration
NMA Basic Debug/Configuration Notes
....................................................................................................................................................................................................................................
The following jython script can generate a new value that limits supervision to 100
NEs:
– from com.alcatel.gem.des import Mangle
– print Mangle.mangle (‘100’)
The output value can be used directly.
• jboss-mysql.force.innodb forces JBoss to create tables of the type InnoDB, which
should only be used with MySQL.
Other Configuration
Other configuration values are usually based on built in JBoss values. These can generally
be found in two places.
• Files in the EMLIMGEM3/jboss/server/ems/deploy are scanned by Jboss and are
loaded when possible. Avoid saving backup files and other files in this directory.
JBoss will scan them and try to deploy them. Saving a jar file in this directory is a
sure way to cause problems. Contained directories may also cause problems, but it
depends on the directory and the rules for loading the contents of the contained
directory. For example, anything in the jms directory will be treated just like files in
the deploy directory. Files in the gem.ear directory are not reloaded if the
gem.ear/META-INF/application.xml file (or the jboss-app.xml file) are not also
modified (touched). It is safer to simply not keep backup copies in this directory.
• Files in the EMLIMGEM3/jboss/server/ems/conf directory are loaded by JBoss on
startup only. The log4j.xml file is the only exception. Documentation on most of these
files (and some in the deploy directory) can be found at the JBoss web site
(http://labs.jboss.com/jbossas/docs/index.html).
....................................................................................................................................................................................................................................
1350 OMS 11-73
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Troubleshooting Configuration
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
11-74 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
12 GSP and MP Configuration
12
Overview
Purpose
This chapter provides the 1350 OMS system administrator with the conceptual
information and the associated tasks that pertain to the Guardian Service Processor (GSP)
and the Management Processor (MP).
Contents
...................................................................................................................................................................................................................................
1350 OMS 12-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration GSP and MP Overview
....................................................................................................................................................................................................................................
Functional requirements
To use the system console, the administrator must use a local VT100 terminal or a PC
with a VT100 terminal emulator.
The GSP can be configured so the system console can be used through a LAN
connection. In addition, GSP rev B provides web console functionality.
If a PC with the VT100 terminal emulator is in use, the administrator must have an
RS-232, 9-24 pin male/male cable adapter.
....................................................................................................................................................................................................................................
12-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Configure the GSP
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “GSP and MP Overview” (p. 12-2)
Leaving Console Mode-you may lose write access. When Console Mode
returns,
....................................................................................................................................................................................................................................
1350 OMS 12-3
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Configure the GSP
....................................................................................................................................................................................................................................
type
Ecf to get console write access
...................................................................................................................................................................................................
1 At the GSP> prompt, enter the following command to modify LAN connections:
lc [Enter]
Result: The GSP outputs a display that is similar to the following:
....................................................................................................................................................................................................................................
12-4 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Configure the GSP
....................................................................................................................................................................................................................................
Result: The GSP outputs a display that is similar to the following that shows the
current IP address and prompts you for a modification decision:
3 At the following prompt, enter Y to modify the current IP address that is displayed:
Do you want to modify it? (Y/[N]) Y [Enter]
...................................................................................................................................................................................................
4 At the following prompt, enter the current IP address of the GSP LAN:
Enter new IP Address: <GSP LAN IP Address> [Enter]
Result: The GSP outputs a display that is similar to the following:
New IP Address: <GSP LAN IP Address>
...................................................................................................................................................................................................
5 At the following prompt, confirm the current IP address of the GSP LAN if it is correct:
New IP Address: <GSP LAN IP Address>
Confirm? (Y/[N]) Y [Enter]
Result: The GSP outputs a display that is similar to the following:
* IP Address will be updated.
In a series of prompts, the GSP prompts you for modifications to the hostname, subnet
mask, and gateway.
...................................................................................................................................................................................................
6 At the following prompts, enter the appropriate information regarding the GSP host name:
Current GSP Host Name: uninitialized
Do you want to modify it? (Y/[N]) Y [Enter]
Enter new GSP Host Name: <hostname> [Enter]
Result: The GSP outputs a display that is similar to the following:
-> GSP Host Name will be updated.
The GSP now prompts for the current subnet mask.
...................................................................................................................................................................................................
7 At the following prompts, enter the appropriate information regarding the subnet mask:
Current Subnet Mask: 255.255.255.0
Do you want to modify it? (Y/[N]) Y [Enter]
....................................................................................................................................................................................................................................
1350 OMS 12-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Configure the GSP
....................................................................................................................................................................................................................................
Enter new Subnet Mask: <subnet mask> [Enter]
Result: The GSP outputs a display that is similar to the following:
-> Subnet Mask will be updated.
The GSP now prompts for the current gateway.
...................................................................................................................................................................................................
8 At the following prompts, enter the appropriate information regarding the gateway:
Current Gateway: 127.0.0.1
Do you want to modify it? (Y/[N]) (Default will be IP Address Y
Enter new Gateway: <gateway IP address> [Enter]
New Gateway: <gateway IP address>
Confirm? (Y/[N]) Y [Enter]
Result: The GSP outputs a display that is similar to the following and the GSP
prompt reappears:
E...................................................................................................................................................................................................
N D O F S T E P S
1 At the GSP> prompt, enter the following command to modify the security options so you
can configure the administrator profile:
so [Enter]
Result: The GSP outputs a display that is similar to the following:
This command allow you to modify the security options and access control.
GSP wide parameters are:
. Login Timeout: 1 minutes.
. Number of Password Faults allowed: 3
. Flow Control Timeout: 5 minutes.
...................................................................................................................................................................................................
2 At the following prompt, enter n so the GSP wide parameters are not modified:
Do you want to modify the GSP wide parameters? (Y/[N]) n
....................................................................................................................................................................................................................................
12-6 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Configure the GSP
....................................................................................................................................................................................................................................
Result: The GSP outputs a display that is similar to the following about the first user
profile. Note all the fields are empty:
3 At the following prompt, enter y so you can modify the user number 1 parameters:
Do you want to modify the user number 1 parameters? (Y/[N]/Q to
quit) y
Result: The GSP outputs a series of prompts about the current and new user name.
...................................................................................................................................................................................................
4 At the following prompts, enter the required information for the current and new user
name:
Current User's Name [Enter]
Enter new User's Name root [Enter]
New User's Name root [Enter]
Confirm? (Y/[N]) Y [Enter]
Result: The GSP outputs a message similar to the following about current and new
user name.
-> User's Name will be updated.
The GSP now prompts you for organizational name changes.
...................................................................................................................................................................................................
5 At the following prompt, enter n so you do not modify the organization name:
Current Organization's Name:
Do you want to modify it? (Y/[N]) N
Result: The GSP outputs a series of prompts about the user name for the login.
...................................................................................................................................................................................................
6 At the following prompts, enter the required information for the user name for the login.
Logging in as root is not mandatory.
Enter new Login root [Enter]
....................................................................................................................................................................................................................................
1350 OMS 12-7
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Configure the GSP
....................................................................................................................................................................................................................................
Enter new Login for confirmation root [Enter]
Result: The GSP outputs a message similar to the following about the current and
new user name.
-> Login will be updated.
The GSP now prompts you for password changes.
...................................................................................................................................................................................................
7 At the following prompts, enter the required information for the password, which is not
displayed:
Do you want to modify the current password? (Y/[N]) Y
Enter new Password <type new password here> [Enter]
Enter new Password for confirmation
<re-type new password here> [Enter]
Result: The GSP outputs a message similar to the following about the password.
-> Password will be updated.
The GSP now prompts you for dial-back options.
...................................................................................................................................................................................................
8 At the following prompt, enter n so you do not modify the dial-back options:
Current Dial-back configuration: Disabled
Do you want to modify it? (Y/[N]) N
Result: The GSP outputs a series of prompts about the access level.
...................................................................................................................................................................................................
9 At the following prompts, enter the required information for the access level:
Current Access Level: Operator
Do you want to modify it? (Y/[N]) Y
Enter new Access Level (Operator / Administrator) A [Enter]
New Access Level: Administrator
Confirm? (Y/[N]): Y [Enter]
Result: The GSP outputs a message similar to the following about the access level.
-> Access level will be updated.
The GSP now prompts you for mode options.
...................................................................................................................................................................................................
10 At the following prompts, enter the required information for the mode:
Current Mode: Single
....................................................................................................................................................................................................................................
12-8 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Configure the GSP
....................................................................................................................................................................................................................................
Do you want to modify it? (Y/[N]) Y
Enter new Mode (Single / Multiple): M [Enter]
New Mode: Multiple
Confirm? (Y/[N]): Y [Enter]
Result: The GSP outputs a message similar to the following about the mode.
-> Mode will be updated.
The GSP now prompts you for user state options.
...................................................................................................................................................................................................
11 At the following prompts, enter the required information for the current user state:
Current User's state: Disabled
Do you want to modify it? (Y/[N]) Y
Enter new User's state (Enabled / Disabled): E [Enter]
New User's state: Enabled
Confirm? (Y/[N]): Y [Enter]
Result: The GSP outputs a message similar to the following about the user.
-> User's will be updated.
The GSP now outputs a display similar to the following for the second user profile:
12 At the following prompt, enter q to quit the prompting sequence so the second user
profile is not modified:
Do you want to modify the user number 2 parameters? (Y/[N]/Q to
quit) q
Result: The GSP outputs a message similar to the following:
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1350 OMS 12-9
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Configure the GSP
....................................................................................................................................................................................................................................
Task 4: Configure the LAN Access
Complete the following steps to configure the LAN access.
...................................................................................................................................................................................................
1 At the GSP> prompt, enter the following command to enable LAN access:
el [Enter]
Result: The GSP outputs a display that is similar to the following:
....................................................................................................................................................................................................................................
12-10 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Verify Access to the GSP LAN Console
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “GSP and MP Overview” (p. 12-2)
Task
Complete the following steps to verify access to the GSP LAN console.
...................................................................................................................................................................................................
Trying...
Connected to .......
Escape character is '
]'.
Local flow control off
Service Processor login: root
Service Processor password:
Hewlett-Packard Guardian Service Processor
9000/800/L1000-36 System Name:
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1350 OMS 12-11
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Verify Access to the GSP LAN Console
....................................................................................................................................................................................................................................
[Read only - use Ecf for console write access.]
<Ctrl>+E c f [Enter]
Result: The GSP displays output that is similar to the following:
[bumped user - ]
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
12-12 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Access to the GSP Console
....................................................................................................................................................................................................................................
Related information
See the following topic in this document:
• “GSP and MP Overview” (p. 12-2)
Task
Complete the following steps to access the GSP console.
...................................................................................................................................................................................................
1 Complete the steps in the “Task 1: Access the GSP” (p. 12-3) task.
...................................................................................................................................................................................................
2 At the GSP> prompt, enter the following command to get into console mode in the GSP:
co [Enter]
Result: The GSP outputs a display that is similar to the following:
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
12-14 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Configure the MP
....................................................................................................................................................................................................................................
Configure the MP
When to use
Use this task to configure the Management Processor (MP).
Related information
See the following topic in this document:
• “GSP and MP Overview” (p. 12-2)
Task
Complete the following steps to configure the Management Processor (MP).
...................................................................................................................................................................................................
3 At the following prompts, enter the Admin login and password to access the MP:
MP password:
MP login: Admin
MP password: Admin
Result: The tool outputs a welcome screen, followed by a display that is similar to
the following:
MP MAIN MENU:
CO: Consoles
....................................................................................................................................................................................................................................
1350 OMS 12-15
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Configure the MP
....................................................................................................................................................................................................................................
VFP: Virtual Front Panel (partition status)
CM: Command Menu
CL: Console Logs
SL: Show chassis Logs
HE: Help
X: Exit Connection
Note at any time you can enter HE to get help on any MP function.
...................................................................................................................................................................................................
4 At the MP> prompt, enter the CM command to access the Command Menu:
MP> CM
Result: The tool outputs the MP:CM> prompt and a display that is similar to the
following:
Enter HE to get a list of available commands
...................................................................................................................................................................................................
5 At the MP:CM> prompt, enter the LC command to access the LAN console:
Result: The tool outputs a display that is similar to the following:
7 At the following prompts, enter the appropriate information regarding the IP address:
Current IP Address is: 127.0.0.1
....................................................................................................................................................................................................................................
12-16 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Configure the MP
....................................................................................................................................................................................................................................
Do you want to modify it? (Y/[N]) Y [Enter]
Enter new IP Address: <new IP Address> [Enter]
New IP Address will be: ....<new IP Address>
Please confirm (Y/[N]) Y
-> IP Address will be updated.
Result: The tool now prompts for the network name that is to be assigned to the MP.
...................................................................................................................................................................................................
8 At the following prompts, enter the appropriate information regarding the network name
that is to be assigned to the MP:
Current MP Network Name is: notdefined
Do you want to modify it? (Y/[N]) Y [Enter]
Enter new MP Network Name : <new MP Network Name> [Enter]
New MP Network Name will be: ...<new MP Network Name>
Please confirm (Y/[N]) Y
-> MP Network Name will be updated.
Result: The tool now prompts for information on the subnet mask.
...................................................................................................................................................................................................
9 At the following prompts, enter the appropriate information regarding the subnet mask:
Current Subnet Mask is: 255.0.0.0
Do you want to modify it? (Y/[N]) Y [Enter]
Enter new Subnet Mask : <new Subnet Mask> [Enter]
New Subnet Mask will be: .... <new Subnet Mask>
Please confirm (Y/[N]) Y
-> Subnet Mask will be updated.
Result: The tool now prompts for the current IP address that is to be assigned to the
gateway.
...................................................................................................................................................................................................
10 At the following prompts, enter the appropriate information regarding the gateway:
Current Gateway is: 0.0.0.0
Do you want to modify it? (Y/[N])<Default is the IP Address>
Y [Enter]
....................................................................................................................................................................................................................................
1350 OMS 12-17
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
GSP and MP Configuration Configure the MP
....................................................................................................................................................................................................................................
Enter new Gateway : <new Gateway> [Enter]
New Gateway will be: .... .... <new Gateway>
Please confirm (Y/[N]) Y
-> Gateway will be updated.
Result: The tool now displays output similar to the following to indicate that it has
updated all parameters:
-> Parameters have been updated.
...................................................................................................................................................................................................
11 Use telnet to check the connection from another system. If the connection fails, use the
EL command to determine if access is enabled.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
12-18 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
13 File System Management
13
Overview
Purpose
This chapter provides the 1350 OMS network administrator with the conceptual
information that pertains to the File System Management of the 1350 OMS.
Contents
...................................................................................................................................................................................................................................
1350 OMS 13-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
File System Management File System Management Overview
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
13-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
File System Management File System Management Tools
....................................................................................................................................................................................................................................
scmirrorfs
The scmirrorfs tool is used to set up the Disk Mirror/UX configuration on a system in
which the mirror configuration has been not done or has been lost (for example, after a
restore from backup). The scmirrorfs tool requires the Disk Mirror/UX software be
installed and the disk configuration to adhere to the functional requirements specified in
“File System Management functional requirements” (p. 13-2).
Refer to the following sections of this document for additional information on scmirrorfs:
• Chapter 6, “Mirror Disks”
• “Mirror Configurations” (p. 5-20)
• “Run the scmirrorfs Tool to Set Up the Mirrored Configuration” (p. 5-44)
....................................................................................................................................................................................................................................
1350 OMS 13-3
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
File System Management File System Management Tools
....................................................................................................................................................................................................................................
scextendfs
The scextendfs tool is used to extend or to create a file system during the system
installation phase. The tool automatically computes the amount of disk space requested,
including the space for the mirror configuration, and it issues the request for an additional
new disk configuration when needed.
Formats:
scextendfs [-l <log file>] [-O] <Mount Point> <Required Space> [<VolGroup>]
scextendfs [-l <log file>] [-O] -f<File>
scextendfs -a <MountPoint>
scextendfs [-i]
scextendfs [-h]
Where:
-l <log file> specifies an output log file that differs from the default log file
(/SCINSTALL/log/scextendfs.log).
-O specifies that disk overhead is to be added. The overhead is computed as 10% of the
amount of space that is already in use in the specified file system, plus the required space.
<MountPoint> specifies the file system that is to be extended through the mount point. If
a file does not exist with this name, the tool creates a new file system and the related
mount point directory.
<ReqSpace> specifies the required space. This value is managed as file system size
during the creation, or the free space that is required when the file system exists. (Note no
action is taken when the existing file system has more free space available that what is
required.)
<VolGroup> specifies the volume group name for the file system. This parameter is
allowed only during the creation of a new file system. If the volume group does not exit,
the tool creates it.
-f <File> specifies the file that was written in the file system list and the relative space
that was required. The syntax is the following:
<MountPoint> <ReqSpace> [<VolGroup>]
This syntax allows a single command to extend or to create an additional file system.
-a specifies that the specified file system can be extended to the remaining volume group
free space.
-i specifies that the current disk configuration should be made visible.
-h specifies that a description of the procedure call should be provided.
Example:
....................................................................................................................................................................................................................................
13-4 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
File System Management File System Management Tools
....................................................................................................................................................................................................................................
This example illustrates how to extend a file system to have 20% more free space.
1. Use the bdf command to determine the file system size:
...,sys,root # bc
2228224/100*20
445640
445640/1024 <kilo to mega byte conversion>
435
<Ctrl d>
3. Extend the file system with the scextendfs tool:
scdeletefs
The scdeletefs tool is used to remove a file system that was created with scextendfs.
Important! When scdeletefs removes a file system, that file system cannot be
restored; meaning, the removal of the file system cannot be reversed.
Formats:
scdeletefs [-l <log file>] <Mount Point>
scdeletefs [-l <log file>] -f<File>
scextendfs -g swap
scextendfs [-i]
....................................................................................................................................................................................................................................
1350 OMS 13-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
File System Management File System Management Tools
....................................................................................................................................................................................................................................
scextendfs [-h]
Where:
-l <log file> specifies an output log file that differs from the default log file
(/SCINSTALL/log/scextendfs.log).
<MountPoint> specifies the file system that is to be deleted through the mount point.
-g swap specifies to swap the area garbage collection, which removes more used swap
areas. This command is typically used to remove any TMN applications.
-i specifies that the current disk configuration should be made visible.
-h specifies that a description of the procedure call should be provided.
....................................................................................................................................................................................................................................
13-6 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Appendix A: List of
Abbreviations
Abbreviations
List
Abbreviation Meaning
ACL Access Control List
Alt_boot Alternate Boot Device
ANTP Alcatel-Lucent network time protocol
CDE Common Desktop Environment
cdfs/CDfs Compact-Disk Filesystem
CLI Command Line Interface
CLNP Connectionless Network Protocol
CMISE Common Management Information Service
Element
CNA CMISE Network Adapter
DAT Digital Audio Tape
DLT Digital Linear Tape
DNS Domain Name Service, Domain Name
System, or Domain Name Server
DVD Digital Video Disk/Digital Versatile Disk
DWDM Dense Wavelength Division Multiplexing
EML Element Management Layer
eOMS embedded Optical Management System
ETSI European Telecommunications Standards
Institute
FTP File Transfer Protocol
...................................................................................................................................................................................................................................
1350 OMS A-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
List of Abbreviations Abbreviations
....................................................................................................................................................................................................................................
Abbreviation Meaning
GID group ID
GENOS generic OS-to-OS
GNE Gateway Network Element
GPS global positioning satellite
GSP HP® Guardian Service Processor
GUI Graphical User Interface
HA High Availability
hfs/HFS Hierarchical File System
HTML HyperText Markup Language
inetd super-server daemon that manages Internet
services
IPR Independent Peripheral Release
IRT Ignite Recovery Tape
ISA Industry Standard Architecture
KDC Key Distribution Log (Kerberos)
lan/LAN Local Area Network
LVM Logical Volume Manager
MP Management Processor
MIB Management Information Base
MPLS Multiple Protocol Label Switching
MW-INT Middleware Interface
MW-OS Middle Ware Operating System
NA Network Adapter
NE Network Element
NIO new input/output (java)
narrow input/output in reference to a bus
NMA Network Management Application
NML Network Management Layer
NMS Network Management System
NTP network time protocol
OI Open Interface
OSI Open Systems Interconnection
....................................................................................................................................................................................................................................
A-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
List of Abbreviations Abbreviations
....................................................................................................................................................................................................................................
Abbreviation Meaning
PDF Portable Document Format
PKT Packet
PID Process Identifier
Pri_boot Primary Boot Device
PVG Physical Volume Group
rcp remote copy file; UNIX command
rhost remote host; UNIX command
rlogin remote login; UNIX command
RTC real-time clock
SAN Storage Area Network
scdisk scan disk
scp secure copy; UNIX command
SCSI Small Computer System Interface
SDH Synchronous Digital Hierarchy
SEC Security; as in security database
SMH HP® System Management Homepage
sequential access media a tape device
SML Service Management Layer
SNMP Simple Network Management Protocol
SONET Synchronous Optical Network
SP service pack
ssh/SSH Secure Shell
SWP Software Package (descriptors)
TCP/IP Transmission Control Protocol/Internet
Protocol
TL1 Transaction Language 1
TP termination point
TMN Telecommunications Management Network
TMPLS Transport—Multiple Protocol Label
Switching
TNA TL1 Network Adapter
UID user ID
....................................................................................................................................................................................................................................
1350 OMS A-3
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
List of Abbreviations Abbreviations
....................................................................................................................................................................................................................................
Abbreviation Meaning
VA virtual array
vg/volgroup volume group
vgchange volume group change
VPN Virtual Private Network
VT virtual terminal
wan/WAN Wide Area Network
WDM Wavelength Division Multiplexing
XDMCP X Display Manager Control Protocol
XoS XML-over-socket
....................................................................................................................................................................................................................................
A-4 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Index
B Backup and recovery Run scbackup for a Local Disk Backup task, 5-24
backup restrictions, 5-10 Run scdisk_read_check to Read and Check the Disk
task, 5-21
Boot from the IRT task, 5-34
Run the scmirrorfs Tool to Set Up the Mirrored
Console messages during reboot from IRT, 5-16 Configuration task, 5-44
console restriction during, 5-10 scbackup functional overview, 5-6
full mirror faults and troubleshooting, 5-11 scbackup-screstore version incompatibility, 5-10
full system recovery phases, 5-13 screstore checks and messages, 5-16
full system recovery purpose, 5-13 Scripts that fail during the reboot from the IRT, 5-15
functional definition, 5-2 split operation problems, 5-11
IRT rebooting errors, 5-15 system crashes, 5-11
IRT recovery, 5-14 time-out expiration, 5-11
log files and troubleshooting, 5-11 tools, 5-3
login messages, 5-11 troubleshoot Current host is different from..., 5-17
....................................................................................................................................................................................................................................
1350 OMS IN-1
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Index
....................................................................................................................................................................................................................................
Verify the Readability of the fbackup Tape task, 5-33 gptm (grace period time) system security parameter,
9-29
................................................................................................
GSP
C CD-ROM
Access the GSP Console task, 12-13
eject a CD-ROM, 8-7
Configure the GSP task, 12-3
CHANGE_ENCRYPT_PASSWORD system security
parameter, 9-28 Verify Access to the GSP LAN Console task, 12-11
Commands ................................................................................................
D dlylntr (delay between login tries) system security cautions regarding File System Management, 13-3
parameter, 9-29 HP® printer
DNSADD, 4-5 configuration tool, 10-2
DNSCHANGE, 4-5 Configure a Printer in the Local Spooler Queue task,
DNSREMOVE, 4-5 10-3
....................................................................................................................................................................................................................................
IN-2 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Index
....................................................................................................................................................................................................................................
llog (last log) system security parameter, 9-30 Align All Group Member Nodes to a Specified
Member Node task, 4-17
lntmout (login time out) system security parameter, 9-30
Align One Group Member Node to Another Group
Logs
Member Node task, 4-18
Activate the Kerberos KDC log task., 11-8
basic functions, 4-5
Deactivate the Kerberos KDC log task., 11-10
Change a Server to the Current DNS Configuration
................................................................................................ task, 4-46
M Management Processor (MP) Change the Gateway IP Address and Hostname task,
4-42
Configure the MP task, 12-15
Change the Hostname of a Remote Node task, 4-34
MIN_PASSWORD_LENGTH system security
parameter, 9-30 Change the Hostname the Current/Local Node task,
4-37
Mirror disks
Change the IP Address a Remote Node task, 4-26
configuration example, 6-3
Change the IP Address the Current/Local Node task,
configuration methods, 6-2 4-30
Configure the Mirror Disk/UX® task, 6-6
Change the Subnetwork Mask task, 4-41
Install Mirror Disk/UX task, 6-4
Establish a Group and Initialize Node Name
purpose, 6-2 Management Persistent Data task, 4-7
rebuild restriction during backup/recovery, 5-10 external nodes, 4-3
................................................................................................ functional restrictions, 4-6
Node Name Management tool Remove a Server from the Current DNS
Configuration task, 4-48
Add a New External Node to the Group task, 4-12
security features, 4-5
Add a New Node to the Group task, 4-9
working group, 4-3
Add a New Server to the Current DNS Configuration
task, 4-44 nullpw (null password) system security parameter, 9-31
....................................................................................................................................................................................................................................
1350 OMS IN-3
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Index
....................................................................................................................................................................................................................................
................................................................................................ encryption set up, 9-23
P PASSWORD_HISTORY_DEPTH system security gptm (grace period time) system security parameter,
parameter, 9-31 9-29
PASSWORD_MAXDAYS system security parameter, llog (last login) system security parameter, 9-30
9-31 lntmout (login time out) system security parameter,
PASSWORD_MIN_DIGIT_CHARS system security 9-30
parameter, 9-32 location and access to the system security
PASSWORD_MIN_SPECIAL_CHARS system security parameters, 9-26
parameter, 9-32 log files, 9-21
PASSWORD_MINDAYS system security parameter, MIN_PASSWORD_LENGTH system security
9-32 parameter, 9-30
PASSWORD_WARNDAYS system security parameter, nullpw (null password) system security parameter,
9-33 9-31
................................................................................................ PASSWORD_HISTORY_DEPTH system security
parameter, 9-31
R rstrpw (restrict trivial passwords) system security
parameter, 9-33 PASSWORD_MAXDAYS system security
parameter, 9-31
................................................................................................
PASSWORD_MIN_DIGIT_CHARS system security
S Safety information, xiii
parameter, 9-32
scdeletefs, 13-5 PASSWORD_MIN_SPECIAL_CHARS system
scextendsfs, 13-4 security parameter, 9-32
....................................................................................................................................................................................................................................
IN-4 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Index
....................................................................................................................................................................................................................................
SIT (shell inactivity timeout) system security tmaxlntr (maximum login tries) system security
parameter, 9-33 parameter, 9-34
software requirements, 9-3 TMF
syschpw (system character password) system rebuild the TMF server database, 11-63
security parameter, 9-33
Troubleshooting
sysltpw (system letter password) system security
cannot contact any KDC for requested realm, 11-4
parameter, 9-34
KDC daemon log file, 11-5
syspnpw (system pronounceable password) system
security parameter, 9-34 network configuration problems, 11-3
tmaxlntr (maximum login tries) system security Ping a Node task, 11-6
parameter, 9-34 ticket is ineligible for postdating, 11-3
Troubleshoot and Fix /etc/passwd File Problems, unable to connect ConnectionManager, 11-4
9-47
................................................................................................
Troubleshoot and Fix Old Password Problems., 9-46
U umaxlntr (user maximum login tries) system security
types of system security parameters, 9-27
parameter, 9-35
umaxlntr (user maximum login tries) system security
usrpick (user pick) system security parameter, 9-35
parameter, 9-35
................................................................................................
user-allowed commands, 9-9
usrpick (user pick) system security parameter, 9-35 W WARN_USERS_LIST system security parameter, 9-35
Verify and Kill Processes task, 9-42 Web Portal, 1-4, 1-4
T Tasks
....................................................................................................................................................................................................................................
1350 OMS IN-5
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011
Index
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
IN-6 1350 OMS
8DG42146LAAA-Vol1 9.5
Issue 1 October 2011