270-702-020R11.0_Issue_1.pdf

Title page

Alcatel-Lucent 5400

Linux Control Platform | Release 11.0

Alarm Management

270-702-020R11.0

Issue 1 | June 2015

Alcatel-Lucent – Internal

Proprietary – Use pursuant to Company instruction

Proprietary Use pursuant to Company instruction

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 © 2015 Alcatel-Lucent. All rights reserved.

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

Alcatel-Lucent without its written authorization.

Notice

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

change.

The registered trademark Linux ® is used pursuant to a sublicense from LMI, the exclusive licensee of Linus Torvalds, owner of the mark on a world-wide

basis.

PICMG, the AdvancedTCA name and logos, the ATCA name and logo, and the PICMG logo are registered trademarks of the PCI Industrial Computers

Manufacturers Group.

The AdvancedMC name and logo are trademarks of the PCI Industrial Computers Manufacturers Group.

Conformance statements

Refer to Appendix C, “Conformance statements”

Security statement

In rare instances, unauthorized individuals make connections to the telecommunications network through the use of remote access features. In such an event,

applicable tariffs require that the customer pay all network charges for traffic. Alcatel-Lucent cannot be responsible for such charges and will not make any

allowance or give any credit for charges that result from unauthorized access.

Limited warranty

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

Licenses

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

Developed by Alcatel-Lucent

Proprietary Use pursuant to Company instruction



Contents

About this document

Purpose ............................................................................................................................................................................................ viivii

What's new ..................................................................................................................................................................................... viivii

Safety information ..................................................................................................................................................................... viiiviii

Intended audience ...................................................................................................................................................................... viiiviii

How to use this document ....................................................................................................................................................... viiiviii

Conventions used ....................................................................................................................................................................... viiiviii

Related documentation ............................................................................................................................................................ viiiviii

How to order ................................................................................................................................................................................. ixix

Technical support .......................................................................................................................................................................... ixix

Document support ........................................................................................................................................................................ ixix

How to comment ............................................................................................................................................................................ xx

1 About alarm management

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

Alarm groups description ....................................................................................................................................................... 1-21-2

Network event categories description ............................................................................................................................... 1-61-6

State or status and alarm indicators on the MI-agent ................................................................................................... 1-81-8

2 Accessing alarm information

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

To display alarms, alarm details and alarm clearance procedures .......................................................................... 2-22-2

To display alarms using the CLI ....................................................................................................................................... 2-122-12

To print, save alarms and events ....................................................................................................................................... 2-142-14

To save, print alarms and events to a maintenance terminal .................................................................................. 2-162-16

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



iii

To create a filter for monitoring informational alarms ............................................................................................. 2-192-19

To pick up or unpick an alarm ........................................................................................................................................... 2-212-21

3 Clearing alarms

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

To clear an alarm manually ................................................................................................................................................... 3-23-2

To clear alarms using the CLI .............................................................................................................................................. 3-33-3

A Command descriptions

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

Commands descriptions

startMI .......................................................................................................................................................................................... A-2A-2

stopMI .......................................................................................................................................................................................... A-3A-3

B Hazard statements

Safety statements and common cautions

Structure of safety statements .............................................................................................................................................. B-1B-1

Common cautions and warnings ........................................................................................................................................ B-3B-3

C Conformance statements

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

Eco-environmental statements ............................................................................................................................................ C-2C-2

Glossary

Index

Contents

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

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

iv Alcatel-Lucent – Internal


5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

List of figures

C-1 Electronic products symbol ................................................................................................................................... C-3C-3

C-2 Batteries symbol ........................................................................................................................................................ C-3C-3

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



v

List of figures

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

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

vi Alcatel-Lucent – Internal


5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

About this documentAbout this document

Purpose

The purpose of this document is to describe alarm management tasks for the 5400 Linux

CP.

Starting from release CP5.1, 5400 Linux CP is available as a tenant in a virtual system

that is not 5400 Linux CP-administered. The 5400 Linux CP-administered configuration

(traditional configuration) is equivalent to a combined “Landlord and Tenant”

configuration. The two modes “Landlord” and “Tenant” are defined as follows:

• Landlord

– The Landlord is the entity that provides shared resources of the facility, power,

cooling, hardware management, and network connectivity to one or more tenants.

The Landlord also provides a management domain for the allocation of the

resources.

• Tenant

– The Tenant is an entity with rights to some portion of the shared resources

provided by the Landlord and to deploy and manage those resources under its own

control within the Landlord's infrastructure.

– The Tenant is an application, which has been adapted to remove native

system-level dependencies related to hardware and configuration management.

These concerns are delegated to a Landlord.

– The Tenant application can run in environments that provide a suitable Landlord.

Note: The Tenant is only responsible for managing its software and services and is

not responsible for managing the underlying hardware.

What's new

This is the first issue of the document for Release CP 11.0. This document does not have

any updates from the previous software release.

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



vii

Safety information

For your safety, this document contains safety statements. Safety statements are given at

points where risks of damage to personnel, equipment, and operation may exist. Failure to

follow the directions in a safety statement may result in serious consequences.

Intended audience

The audience for this document includes:

• 5400 Linux CP maintenance technicians

• 5400 Linux CP specialists

• 5400 Linux CP operators

How to use this document

This document is intended to be used as a reference for all the 5400 Linux CP alarm

management tasks.

Note: Some details in this document will only apply when 5400 Linux CP is

administering an ATCA-based system (i.e. is in Landlord mode). In general this

document is all applicable to any ATCA-based system. Information related to some

hardware alarms and configuration will not be present when 5400 Linux CP is not

administering an ATCA-based system.

Conventions used

The following table summarizes presentation conventions:

Convention Information Type

output A system output message

cd /bin A command entered by the user

Enter Keyboard entries

<IP Address> Variable parameters

filename File name

Tools->Discovery User interface string

APx Variable entities

Related documentation

• Alcatel-Lucent 5400 Linux Control Platform System Guide, 270-702-011

• Alcatel-Lucent 5400 Linux Control Platform Hardware Description, 270-702-012

• Alcatel-Lucent 5400 Linux Control Platform User Interface, 270-702-013

About this document

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

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

viii Alcatel-Lucent – Internal


5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

• Alcatel-Lucent 5400 Linux Control Platform Configuration Management,

270-702-014

• Alcatel-Lucent 5400 Linux Control Platform Security Management, 270-702-015

• Alcatel-Lucent 5400 Linux Control Platform Performance Management, 270-702-016

• Alcatel-Lucent 5400 Linux Control Platform Observation Counters Dictionary,

270-702-017

• Alcatel-Lucent 5400 Linux Control Platform Log Management, 270-702-018

• Alcatel-Lucent 5400 Linux Control Platform Alarm Management, 270-702-020

• Alcatel-Lucent 5400 Linux Control Platform Alarm Dictionary, 270-702-021

• Alcatel-Lucent 5400 Linux Control Platform Free and Open Source Software

Copyright Notice and Licenses, 270-702-028

• Alcatel-Lucent 5400 Linux Control Platform Hardware Maintenance, 270-702-030

• Alcatel-Lucent 5400 Linux Control Platform Software Maintenance, 270-702-031

• Alcatel-Lucent Virtual Machine Management and Host Infrastructure Guide,

9YZ-06688-AAAO-PCZZA

How to order

To order Alcatel-Lucent documents contact your local sales representative or use Online

Customer Support (OLCS) (https://support.alcatel-lucent.com).

Technical support

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

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

information.

Document support

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

the following telephone numbers.

From United States

• If you are using a landline, a cellular phone or VoIP, dial this number: 1-888-582-3688

From other countries

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

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

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

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

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

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

About this document

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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



ix

https://support.alcatel-lucent.com



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

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

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

How to comment

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

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

([email protected]).

About this document

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

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

x Alcatel-Lucent – Internal


5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

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



mailto:[email protected]


1 1About alarm management

Overview

Purpose

This chapter provides an overview of alarm management tasks performed using the

MI-Agent.

Contents

Alarm groups description 1-2

Network event categories description 1-6

State or status and alarm indicators on the MI-agent 1-8

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



1-1

Alarm groups description

Overview

This section explains the major groups associated with an alarm. These different

categories can be observed in the MI-GUI under Fault Management ---> Alarms . The

alarm types, alarm severities and probable causes are defined in the CCITT standard

X.733.

Though the alarm details are available in the X.733 standards, the 3GPP standards are

used which are based off X.733 standards.

Introduction

Alarms appearing in the alarm log are all propagated events with the severities: Warning,

Minor, Major, Indeterminate and Critical. All other events stay only in the event log.

To maintain the system, only the alarm log is required. The event log is informational

only and is not required for system maintenance.

Note: The Alarm MI can handle alarm triggers at a rate of 6000 per 5 minutes.

Conditions within network elements or the platform itself could cause a burst of

alarms at a higher rate than this. If this occurs, alarm processing may be delayed. As

the network is recovering, alarm clearing may also be delayed.

Alarm types

The Alarm Type field is shown as a column in the alarms window on the MI-GUI, and as

eventType on the properties of an alarm.

Alarm Type Explanation

Communication

Alarm

An alarm of this type is principally associated with the procedures and/or

processes required to convey information from one point to another.

Quality of Service

Alarm

An alarm of this type is principally associated with degradation in the

quality of a service.

Processing Error

Alarm

An alarm of this type is principally associated with a software or

processing fault.

Equipment Alarm An alarm of this type is principally associated with an equipment fault.

Environmental

Alarm

An alarm of this type is principally associated with a condition relating to

an enclosure in which the equipment resides.

Integrity Violation For security alarms: duplicate information, information missing,

information modification detected, information out of sequence or

unexpected information.

About alarm management Alarm groups description

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

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

1-2 Alcatel-Lucent – Internal


5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Alarm Type Explanation

Operational

violation

For security alarms: denial of service, out of service, procedural error, or

unspecified reason.

Physical violation

Alarm

For security alarms: cable tamper, intrusion detection or unspecified

reason.

Security service or

mechanism

violation Alarm

For security alarms: authentication failure, breach of confidentiality,

non-repudiation failure, unauthorized access attempt, or unspecified

reason.

Time domain

violation Alarm

For security alarms: delayed information, key expired or out of hours

activity.

Note: The security alarms are displayed on the MI GUI Alarms window only for users

with “secadmin” role for LCP_MIGUI application. The security alarms are not sent

northbound to any Element Manager.

The logs pertaining to the security alarms are available in the following location of the

active MI host: /var/log/security.log

Alarm severity

The Severity field appears as a column in the alarms window on the MI-GUI, and as a

field on the alarm details.

Severity Explanation

Critical The Critical severity level indicates that a service affecting condition has

occurred and an immediate corrective action is required. Such a severity can be

reported, for example, when a managed object becomes out of service and its

capability must be restored.

Major The Major severity level indicates that a service affecting condition has

developed and an urgent corrective action is required. Such a severity can be

reported, for example, when there is a severe degradation in the capability of the

managed object and its full capability must be restored.

Minor The Minor severity level indicates the existence of a non-service affecting fault

condition and that corrective action should be taken to prevent a more serious

(for example, service affecting) fault. Such a severity can be reported, for

example, when the detected alarm condition is not currently degrading the

capacity of the managed object.

Warning The Warning severity level indicates the detection of a potential or impending

service affecting fault, before any significant effects have been felt. Action

should be taken to diagnose (if necessary) and correct the problem and to

prevent it from becoming a more serious service-affecting fault.


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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



1-3


Indetermi-

nate

The Indeterminate severity level indicates that the severity level is not

determined by the sending element.

Cleared The Cleared severity level indicates the clearing of one or more previously

reported alarms. This alarm clears all the alarms for this managed object that

have the same Alarm type, Probable cause and Specific problems (if given).

Multiple associated notifications may be cleared by using the Correlated

notifications parameter .

Note: The severity filter, !clear can be used to show all active (not cleared) alarms in the

system.

There are also alarms with informational severity. These alarms appear under the events

log and are therefore described at the events part.

Cause of alarms

The Probable Cause field is shown as a column in the alarms window on the MI-GUI,

and as stringProbableCause field on the properties of an alarm. It gives an indication on

the most likely cause of this alarm and the related problem.

Two examples of probable causes available on the MI-Agent are explained below. The

description is retrieved from the ITU-T X.733 specification. For a complete description of

the probable causes refer to the X.733 and other standards listed under the reference part.

Probable Cause Explanation

Communication Protocol Error A communication protocol has been violated

Configuration or Customizing

Error

A system or device generation or customizing parameter has

been specified incorrectly, or is inconsistent with the actual

configuration

Alarm categories

The alarm category is shown in the Alarm Summary View, as a field on the alarm

details, and can optionally be added as a column to the alarms view window. This

category is used to group all alarms on a system additionally to the given severity. The

different category types can also be used as criteria within custom views.

Category Category related to:

CP Hosts The hosts of the 5400 Linux CP

CP HW The hardware of the 5400 Linux CP


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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Category Category related to:

CP Services The services on top of the 5400 Linux CP

Topology The physical architecture of the network

Reference

The following specifications were used with relation to the alarms and events:

• Telecommunication management; Fault Management; Part 2: Alarm Integration

Reference Point (IRP): Information Service (IS) , 3GPP TS 32.111-2

• Telecommunication management; Fault Management; Part 3: Alarm Integration

Reference Point (IRP): Common Object Request Broker Architecture (CORBA)

Solution Set (SS), 3GPP TS 32.111-3

• Generic network information model , ITU-T M.3100

• Information technology - Open Systems Interconnection - Structure of management

information: Definition of management information, ITU-T X.721

• Information technology - Open Systems Interconnection - Systems Management:

Alarm reporting function, ITU-T X.733

• Information technology - Open Systems Interconnection - Systems Management:

Security alarm reporting function , ITU-T X.736


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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



1-5

Network event categories description

Overview

This section explains the specific network events which are observed in the MI-GUI

under Fault Management ----> Events.

Introduction

All events received by the MI-Agent are logged in the events log. All events with the

severities: Warning, Minor, Major, Indeterminate and Critical are propagated to an

alarm in the alarm log. Other event types (for example with the severities, Info or State)

are not propagated to the alarm log but only stay in the event log.

To maintain the system, only the alarm log is sufficient. The event log is informational

only and is not required for system maintenance.

Severity description

Events use all the standard severities used for alarms. Here only the event-specific

severities are described. For a description of the standard severities, refer to the alarm

categories description.


Info The severity Informational is used for alarms which do not require action to be

taken.

Because this severity is not according to the X.733 standard these alarms are not

propagated to the alarm log and show only in the event log.

State This severity event is used to indicate that a state change happened to a managed

object on the MI-Agent. These states all follow X.731, refer to this standard for

more information.

Event details

Details about the particular events can be retrieved by viewing the details for a specific

event. The event details and in particular the Message field provides enough information

to understand the cause of this event.

Custom Views

Certain types of events can be filtered out of the extensive event log by using Custom

Views on the menu bar. One example is the custom view for informational alarms which

can be viewed separately in a sub folder under Events.

About alarm management Network event categories description

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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Reference

For more information about the possible navigation options to perform fault management

on the MI-GUI, refer to Alcatel-Lucent 5400 Linux Control Platform User Interface,

270-702-013.

About alarm management Network event categories description

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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



1-7

State or status and alarm indicators on the MI-agent

Overview

This topic describes the state or status indicators and alarms that users can encounter on

MI-Agent screens.

All SNEs use the X.731 standard to represent the state or status.

State or status indicators

On various MI-Agent screens, users can view state or status indicators that reflect the

current state of network elements.

Icon Tooltip Condition causing icon

Unknown When the unknown status is set.

Unequipped When the notInstalled bit (Availability status) is set.

Initializing When the isInitializing (Procedural status) bit is set.

Growth When the isSuspended (Control status) and the isOffline

(Availability status) bits are set, and the Usage state is idle.

In Test When the inTest (Availability status) bit is set.

Inhibited When the isOffline (Availability status) bits are set and the

Usage state is set to Active.

Disabled and Failed

Disabled -

swversion

Disabled -

swversion and

Locked

Disabled and

Locked

When the Operational state is set to Disabled and the

Administrative state is set to Locked.

Disabled with

Dependency

When the Operational state is set to Disabled and the

isDependency (Availability status) bits are set.

Disabled When the Operational state is set to Disabled.

Overloaded When the isDegraded (Availability status) bit is set and the

Usage state is set to Busy.

Degraded When the isDegraded (Availability status) bit is set.

Standby If the Standby status is set to EITHER Hot Standby or Cold

Standby.

Standby and Cold

About alarm management State or status and alarm indicators on the MI-agent

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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Icon Tooltip Condition causing icon

Standby Cold and

Locked

Standby and Hot

Standby Hot and

Locked

Enabled When the Operational state is set to Enabled.

Enabled and

Locked

When the Operational state is set to Enabled and the

Administrative state is set to Locked.

X731 state and

status not supported

When the Operational state is set to Not Relevant.

Invalid

Combination of

State and Status

When none of the above conditions are true.

Alarm indicators

The following table shows the alarms that are displayed when a corresponding fault

condition exists:

Icon Color of icon Condition Definition

Red Critical This level indicates that a service

affecting condition has occurred that

requires an immediate corrective action.

Yellow Major This level indicates that a service

affecting condition has developed that

requires an urgent corrective action.

Gray Minor This level indicates the existence of a

non-service affecting fault condition;

corrective action should be taken to

prevent a more serious (for example,

service affecting) fault.

Light Blue Indeterminate This level indicates that the severity

level currently cannot be determined.


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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



1-9

Icon Color of icon Condition Definition

Dark Blue Warning This level indicates the detection of a

potential or impending service-affecting

fault, before any significant effects have

been felt. Action should be taken to

diagnose (if necessary) and correct the

problem and to prevent it from

becoming a more serious

service-affecting fault.


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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

2 2Accessing alarm

information

Overview

Purpose

This chapter explains the different ways to access alarm information using the MI-Agent.

Contents

To display alarms, alarm details and alarm clearance procedures 2-2

To display alarms using the CLI 2-12

To print, save alarms and events 2-14

To save, print alarms and events to a maintenance terminal 2-16

To create a filter for monitoring informational alarms 2-19

To pick up or unpick an alarm 2-21

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



2-1

To display alarms, alarm details and alarm clearance

procedures

Purpose

This procedure demonstrates how the MI Agent is used to display alarms and their details,

as well as to get to the alarm clearance procedures.

Before you begin

Ensure that TLS is enabled in the client side browser, before launching the MI GUI. To

enable TLS in Internet Explorer, go to Tools > Internet Options > Advanced tab >

Security and check Use TLS option.

Procedure

To display alarm details, perform the following steps:

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

1 Launch the MI GUI using Microsoft Internet Explorer ®6.0 or higher version.

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

2 A number of ways are available to display alarms. Select an option.

If you want to Then

Display all active alarms (using the

tree view)

From the tree view:

1. Click Fault Management.

2. Click Alarms.

Display all active/cleared alarms

(using the alarm counts seen on the

right pane of the MI window)

From the alarm counts on the right pane of the MI

window, click Total.

Display alarms for a specific SNE

(using the map view)

From the map view:

1. Click the desired SNE.

2. From the main toolbar, select View->Alarms.

Display alarms for SNEs of the same

type such as MGW (using the alarm

count panel)

From the alarm count panel on the right side of the MI

window, Click the desired SNE

Accessing alarm information To display alarms, alarm details and alarm clearance

procedures

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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Result: In the map view, if you have selected an option that also displays cleared

alarms, a Show Active button appears in the upper right-hand corner of the map view.

Click this button to display only active alarms.

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

3 For a specific alarm,

If you want to Then

Get more detail Double-click an alarm to see more details. Alternatively,

right-click the desired alarm and select Details.

Get the alarm clearance procedure

(at this moment this is only available

for 5400 Linux CP alarms)

Right-click the desired alarm and select Help.

The alarm clearance procedure appears in a new

window.

Details result: The screen displays more information about the alarm.

To get additional information, Properties button can be used.

Alarm details

The following table provides a description of the functionality buttons that are available

on the Alarm Details screen.

Button Description

Pick Up By selecting the Pick Up option, you are assigned as the owner of

the alarm. The owner field is listed in the alarm properties. When

executed, the owner field populates and a record of the activity is

also noted in the annotations block. Unpick releases the owner for

this alarm.

Annotate The Annotate option is used to add notes to an alarm for future

reference. For example, the solution to a problem resolved by the

user can be entered in Alarm Annotate.

This enables other users to solve the same problem with less effort,

by just reading the Annotations for this alarm. This is in addition to

any system or user actions on the alarm, which are recorded

automatically.

Properties The Properties option enables a small window containing additional

alarm information.


procedures

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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



2-3

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

Button Description

View history The View History option can be used to view the status of alarms

added, updated, or deleted.

Merge The Merge option combines the history and the annotations for the

alarm and presents them in Annotations for this alarm.

Close This option closes the 5400 Linux CP Alarms details screen.

Alarms window

The Alarms window:


procedures

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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Alarms window menus

The menus on the Alarms window are:

• Custom Views

• Edit

• View

• Actions

Custom Views options

Refer to the explanation of Custom Views menu in the Alcatel-Lucent 5400 Linux Control

Platform User Interface, 270-702-013.

Edit menu options

Edit menu option descriptions:

Menu options Description

Configure → Alarm Filters

This option is recommended

only for Support personnel and

not for users.

To configure alarm filters.

Pick Up or Unpick To pick up an alarm or unpick an alarm that you picked up

earlier. Your login name will show as the owner for the alarm.

Clear To manually clear an alarm that is no longer active.

Search To search in the Alarms window.

View menu options

View menu option descriptions:

Menu options Descriptions

Details To view details of the selected alarm.

Events To open the Network Events window that shows the events

that are related to the alarms.

Refresh To refresh the content of the Alarms window.

Help To display online help for the selected alarm.


procedures

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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



2-5

Action menu options

Action menu option descriptions:


Save Alarms to Server To save alarm information to a file on a remote server.

Save Alarms to LMT/RMT To save alarm information to a file on a maintenance terminal.

Print Alarms to LMT/RMT To print alarm information to a maintenance terminal.

Alarms details window

The window that is used to view details.


procedures

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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Annotate

This window is used to add or modify annotations:


procedures

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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



2-7

Properties / Alarm User Properties

This window is used to view alarm user properties:


procedures

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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Search alarms window

The window that is used to search in alarms.


procedures

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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



2-9

Events window

This window is used to view all the events.

Events window menu options

The menus on the Events window are:

• Custom Views

• Edit

• View

• Actions.

Events Custom Views options

Refer to the explanation of Custom Views menu in the Alcatel-Lucent 5400 Linux Control

Platform User Interface, 270-702-013.


procedures

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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Edit menu options

Edit menu option descriptions:


Configure → Event Parsers

This option is recommended only

for Support personnel and not for

users.

To configure event parsers.

Configure → Event Filters

This option is recommended only

for Support personnel and not for

users.

To configure event filters.

Search To search in the Network Events window.

Note: There are right-click operations on all managed objects on the GUI to show

related events/alarms for those objects. These create a filtered view of alarms just for

that object.

Event View menu options

View menu option descriptions:


Details To view details of the selected network event.

Alarms To open the Alarms window.

Refresh To refresh the content of the Alarms window.

Events Action menu options

Action menu option descriptions:


Save Events to Server To save event information to a file on the server.

Save Events to LMT/RMT To save event information to a file on a local or remote

maintenance terminal.

Print Events to LMT/RMT To print event information to a local or remote

maintenance terminal.


procedures

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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



2-11

To display alarms using the CLI

Purpose

This procedure describes how to list alarms, using the alarm_cli command.

Before you begin

Pre-requisites

• IP address of the active MI Agent

• User name and password for the MI Agent

Contact your system administrator to obtain the IP address of the active MI Agent.

Required configuration

This procedure assumes that the MI Agent server is up and running and you have access

to the active MI through SSH or SOL connection.

The Serial over Lan (SOL) capability is ATCA-specific and does not exist when 5400

Linux CP is a tenant on the HP hardware.

Note: For the reason of security, the alarm_cli is under RBAC control. To execute

the commands, the users must have the following RBAC roles on LCP_CLI

application.

• operator role: to list non-security alarms only

• secadmin role: to list all alarms, including security alarms

Procedure

Perform the following steps to list alarms:

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

1 From a maintenance terminal, bring up a command window and access the active MI

Agent through SSH or SOL, using the command:

ssh root <IP address>

Result: A login prompt appears

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

2 Type the user name and password for the MI Agent.

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

3 To list all the active alarms, execute the following command:

alarm_cli --list ALL

Accessing alarm information To display alarms using the CLI

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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

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

4 To list active alarms that match a specific criteria, execute the following command:

alarm_cli --list propertyName1="propertyValue1" propertyName2=

"propertyValue2"

You can specify multiple propertyName=propertyValue pairs in the command.

The propertyName flag can be:

• severity (1-Critical, 2-Major, 3-Minor, 4-Warning)

• category

• eventType

• stringseverity

• message

• entity

• managedObjectInstance

• source

• groupName

• alarmID

• alarmName

• additionalText

• stringProbableCause

• eventType

• probableCause

• securityAlarmIndicator

• specificProblem

For example:

alarm_cli --list eventType="Processing Error Alarm"

additionalText="Clearing all alarms for this resource"

This command will list all the alarms with eventType "Processing Error Alarm" and

additionalText "Clearing all alarms for this resource".

Note: A quotation mark is mandatory for strings with blanks. If no alarm matches the

criteria, the CLI exits with proper user message.

Accessing alarm information To display alarms using the CLI

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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



2-13

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

To print, save alarms and events

Purpose

This procedure provides the steps that are required to print or save alarm or event

information.

The saved or printed information can be used for off-line trouble analysis purposes.

Before you begin

Required user skills

A general knowledge on the operation of GUI interfaces and the UNIX operation system

is required to perform this procedure.

Requirements

To print alarm or event information, a printer must be installed.

Procedure

Complete the following steps:

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

1 At the MI-Agent open a Events or an Alarm view.

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

2 On the menu bar, click Actions.

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

3 If you want to Then

Save alarm information to a file Click Save Alarms to Server to save alarm information

to a file on a remote server.

Click Save Alarms to LMT/RMT to save alarm

information to a file on a maintenance terminal.

Continue with Step 4

Save event information to a file Click Save Events to Server to save event information

to a file on a remote server.

Click Save Events to LMT/RMT to save event

information to a file on a maintenance terminal.

Continue with Step 4.

Print the alarm information Click Print Alarms to LMT / RMT.

End of procedure.

Accessing alarm information To print, save alarms and events

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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

If you want to Then

Print the event information Click Print Events to LMT / RMT.

End of procedure.

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

4 In the Properties view, enter a filename in the File Name field.

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

5 Click Save File.

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

6 Click Close.

The file is saved in the MI-Agent host at: /opt/AdventNet/WebNMS/state/

Accessing alarm information To print, save alarms and events

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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



2-15

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

To save, print alarms and events to a maintenance terminal

Purpose

This topic describes the steps required to print or save alarm or event information to a

maintenance terminal (MT).

The saved or printed information can be used for off-line trouble analysis purposes.

Important! The data that is saved is what is currently displayed on the page of the

alarms or events list. For example, if the page length is set to 25, only the 25 alarms

displayed on that page will be saved to the MT.

Before you begin

Requirements

To print alarm or event information, a printer must be installed.

Print or save information

Perform the following steps to print or save information:

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

1 At the MI-Agent open a Network Events or Alarm view.

Important! Notice that this procedure uses alarm examples but the same steps are

used to save or print event information.

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

2 On the Menu bar, click Actions.

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

3 If you want to Then

save alarm or event

information to a file

on the MT

click Save Events to MT or Save Events to MT as appropriate.

Continue with Step 4

print the alarm or

event information,

click Print.

End of procedure.

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

4 In the following window select or enter a filename in the File Name field.

If an existing file name is selected or typed in, it is overwritten with the data currently on

the alarms page.

Accessing alarm information To save, print alarms and events to a maintenance terminal

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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

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

5 Click Save File.

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

6 Click Close.

The location of the saved file is in MT at the specified location.

Save / Print alarm or event information window

This window is used to save/print alarm or event information to a file.


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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



2-17

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

Properties view window

This window is used to save an alert file on the remote server.


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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

To create a filter for monitoring informational alarms

Before you begin

This procedure describes how to create a filter (custom view) in the fault management

event log on the MI-Agent. After creating this custom view, the 5400 Linux CP related

informational alarms are grouped within the events log. For a description on the meaning

of the different alarms, see “Alarm groups description” (p. 1-2) and “Network event

categories description” (p. 1-6).

Procedure

To create a filter for monitoring informational alarms, complete the following steps:

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

1 On the MI-Agent tree view, select Fault management->Events.

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

2 Right-click and select Custom Views->Add Custom View.

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

3 In the Filter View Name field, rewrite a descriptive text for this custom view (for

example 5400 Linux CP informational alarms) .

Note: The name of the custom view must not contain a single-quote character.

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

4 Select Info under the Severity menu.

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

5 Click Additional Criteria and add the following (case sensitive) :

Check box Property Name Match criteria

Enable alarmName LSS*

Note: The additional criteria are added in the additional filter criteria (these filter

criteria are not visible in the main window).

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

6 Click OK.

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

7 Click Select Props To View and ensure that the following options are enabled:

• Severity

• Date

Accessing alarm information To create a filter for monitoring informational alarms

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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



2-19

• entity

• Managed Object

• Message

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

8 Click Additional table columns.

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

9 Click More for every row and add the following:

Check box Display Name Property name

Enable Alarm Name alarmName

Enable Alarm Type eventType

Enable Probable Cause stringProbableCause

Enable Specific Problem specificProblem

Note: The additional properties are added in the additional properties data (the added

properties are not visible in the main properties window).

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

10 Click OK.

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

11 Click Tree Node Properties tab. In the Frame Title field, type a descriptive text for the

created custom view (for example 5400 Linux CP informational alarms ).

Note: The name of the view must not contain a single-quote character.

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

12 Click Apply filter.

Result The filter is added and 5400 Linux CP informational alarms are displayed

when they are present in the event log.

Optionally move the name column to the beginning to get the alarm name.

Accessing alarm information To create a filter for monitoring informational alarms

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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

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

To pick up or unpick an alarm

Purpose

This procedure shows how to pick and unpick an alarm. An alarm is typically picked to

indicate to other maintenance personnel that you are working on this alarm.

Before you begin

Requirements

To pick up or unpick an alarm, the user must be logged on to the web-based user interface

of the MI-Agent and be at the main screen of theMI-Agent.

Procedure

Perform the following steps:

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

1 Get to the alarm window and request the details for an alarm as described in “To display

alarms, alarm details and alarm clearance procedures” (p. 2-2).

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

2 On the alarm detail window, click Pick Up.

Result: The annotations part of the window indicates that you have picked up this

alarm.

After an alarm is picked up, the button changes to UnPick and the owner field changes

to the login name of the person who executed the pickup command.

UnPick is used to indicate that work is no longer being performed on this alarm.

Accessing alarm information To pick up or unpick an alarm

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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



2-21

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

Accessing alarm information To pick up or unpick an alarm

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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

3 3Clearing alarms

Overview

Purpose

This chapter provides the procedures to clear alarms that do not self-clear after corrective

action has been performed on the 5400 Linux CP.

Contents

To clear an alarm manually 3-2

To clear alarms using the CLI 3-3

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



3-1

To clear an alarm manually

Purpose

Use this procedure to clear an alarm when it does not clear by itself after corrective action

has been performed.

Before you begin

Important! Use this procedure only when alarms do not clear by themselves after

corrective action is taken. Alarms are designed to self-clear and it is rare for alarms

not to clear once they are corrected. Clearing an alarm prior to corrective action could

result in system errors.

Observe the following:

Requirements

To display and then clear alarms, the user must be logged on to the web-based user

interface of the MI-Agent.

Procedure

Perform the following steps to clear alarms:

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

1 To display alarms, refer to “To display alarms, alarm details and alarm clearance

procedures” (p. 2-2).

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

2 Once displayed, you can clear one or multiple alarms by using the Shift or Control key

and selecting the alarms that you want to clear.

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

3 On the menu bar select Edit -> Clear.

Clearing alarms To clear an alarm manually

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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

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

To clear alarms using the CLI

Purpose

This procedure provides information on how to clear alarms, using the alarm_cli

command.

Related information

Alarm clearing operations performed using the alarm_cli command are logged to

syslog, under audit trail. The syslog file includes necessary alarm and user information for

audit purpose.

Important! Clearing an alarm does not suppress the alarm. That is, if you clear an

alarm and the condition of that alarm still persists, the alarm may be regenerated. The

alarm_cli command should be used sparingly because it could possibly hide a real

problem.

Before you begin

Pre-requisites

Before you begin, ensure that:

• You have the IP address of the active MI Agent

Contact your system administrator to obtain the IP address of the active MI Agent.

• You have the user name and password for the MI Agent

• MI Agent server is up and running

• You have access to the active MI through SSH or SOL connection.

The Serial over Lan (SOL) capability is ATCA-specific and does not exist when 5400

Linux CP is a tenant on the HP hardware.

Note: For the reason of security, the alarm_cli is under RBAC control. To execute

the commands, the users must have proper RBAC roles on LCP_CLI application.

• operator role: to clear non-security alarms only

• secadmin role: to clear all alarms, including the security alarms

Procedure

Perform the following steps to clear alarms:

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

1 From a maintenance terminal, bring up a command window and access the active MI

Agent through SSH or SOL, using the command:

ssh root <IP address>

Clearing alarms To clear alarms using the CLI

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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



3-3

Result: A login prompt appears

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

2 Type the user name and password for the MI Agent.

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

3 To clear all the active alarms, execute the following command:

alarm_cli --clear ALL

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

4 To clear the active alarms that match a specific criteria, execute the following command:

alarm_cli --clear propertyName1="propertyValue1" propertyName2=

"propertyValue2"

You can specify multiple propertyName=propertyValue pairs in the command.

The propertyName flag can be:

• severity (1-Critical, 2-Major, 3-Minor, 4-Warning)

• category

• eventType

• stringseverity

• message

• entity

• managedObjectInstance

• source

• groupName

• alarmID

• alarmName

• additionalText

• stringProbableCause

• eventType

• probableCause

• securityAlarmIndicator

• specificProblem

For example:

alarm_cli --clear eventType="Processing Error Alarm"

additionalText="Clearing all alarms for this resource"

This clears the alarms with eventType "Processing Error Alarm" and additionalText

"Clearing all alarms for this resource".


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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Note:

1. If the alarm matching criteria includes security and non-security alarms, and if the

user does not have secadmin role, then only the non-security alarms are cleared.

2. The quotation mark is mandatory for strings that include blank space in it.

3. If no alarms match the criteria, the CLI exits with proper user message.


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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



3-5

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


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

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



5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Appendix A: Command

descriptions

Overview

Purpose

This appendix describes the command descriptions that are used in the procedures

performed in this guide.

Contents

Commands descriptions A-2

startMI A-2

stopMI A-3

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



A-1

1234567890123456789012345678901212345678901234567890123456789123456789012345678901234567890121234567890123456789012345678912345678901234567890123456789012123456789012345678901234567891234567890123456789012345678901212345678901234567890123456789123456789012345678901234567890121234567890123456789012345678912345678901234567890123456789012123456789012345678901234567891234567890123456789012345678901212345678901234567890123456789123456789012345678901234567890121234567890123456789012345678912345678901234567890123456789012123456789012345678901234567891234567890123456789012345678901212345678901234567890123456789123456789012345678901234567890121234567890123456789012345678912345678901234567890123456789012123456789012345678901234567891234567890123456789012345678901212345678901234567890123456789123456789012345678901234567890121234567890123456789012345678912345678901234567890123456789012123456789012345678901234567891234567890123456789012345678901212345678901234567890123456789123456789012345678901234567890121234567890123456789012345678912345678901234567890123456789012123456789012345678901234567891234567890123456789012345678901212345678901234567890123456789123456789012345678901234567890121234567890123456789012345678912345678901234567890123456789012123456789012345678901234567891234567890123456789012345678901212345678901234567890123456789


startMI

Description

This command starts the MI Service (combined in an RCC virtual cluster) that are

dedicated to providing this service.

Examples for processes that are started:

• PMAgent: PM file processing

• trapfwd: MI trap receiver daemon

• webnms: WebNMS server.

Command syntax

The command syntax is startMI.

Additional information

Additional information and references:

• This command should be executed on the MI host, using the lss login.

This command should be executed on the OAM&P host, using the lss login.

• This command only starts the MI Service where the RCC process is already running.

• This command is an alias for: MIcmd start vc.

The system response is depicted below:

> startMI

rc=0

Complete RCCvcOnline successfully: Wait for State Change.

.......

state of MI virtual cluster is A - Active

state of MI host primary virtual machine is A - Active

state of MI host alternate virtual machine is S - Standby

Please connect your client to the web server at 1.2.3.4 on port:

9090

>

Command descriptions


startMI

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

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

A-2 Alcatel-Lucent – Internal


5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

stopMI

Description

This command stops the MI Service (combined in an RCC virtual cluster) that are

dedicated to providing this service.

Command syntax

The command syntax for stopMI is stopMI.

Additional information

NOTICE

Service-disruption hazard

When applying the command:

• The service(s) provided by the specified RCC virtual cluster(s) will be lost.

Examples of processes that are stopped:

– The webnms server providing MI-GUI access

– The local zone transfers to the external DNS.

– Alarms, logging, asserts and measurements.

• If both the MI Service and the CNFG Service are unavailable, it is possible that call

processing is lost due to a connection loss to the external DNS.

• The external floating IP addresses related to the specified RCC virtual cluster will

become unavailable!

Note: Use the command with caution.

Additional information:

• This command should be executed on the MI host, using the lss login.

This command should be executed on the OAM&P host, using the lss login.

• This command is an alias for: MIcmd stop vc.

System response

The system response on receiving a stopMI command is depicted below:



stopMI

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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



A-3

1234567890123456789012345678901212345678901234567890123456789123456789012345678901234567890121234567890123456789012345678912345678901234567890123456789012123456789012345678901234567891234567890123456789012345678901212345678901234567890123456789123456789012345678901234567890121234567890123456789012345678912345678901234567890123456789012123456789012345678901234567891234567890123456789012345678901212345678901234567890123456789123456789012345678901234567890121234567890123456789012345678912345678901234567890123456789012123456789012345678901234567891234567890123456789012345678901212345678901234567890123456789123456789012345678901234567890121234567890123456789012345678912345678901234567890123456789012123456789012345678901234567891234567890123456789012345678901212345678901234567890123456789123456789012345678901234567890121234567890123456789012345678912345678901234567890123456789012123456789012345678901234567891234567890123456789012345678901212345678901234567890123456789123456789012345678901234567890121234567890123456789012345678912345678901234567890123456789012123456789012345678901234567891234567890123456789012345678901212345678901234567890123456789

> stopMI

rc=0

Complete RCCvcOffline successfully: Wait for State Change.

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

state of MI virtual cluster is O - Offline

state of MI host primary virtual machine is O - Offline

state of MI host alternate virtual machine is O - Offline

>



stopMI

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

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

A-4 Alcatel-Lucent – Internal


5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Appendix B: Hazard statements


Structure of safety statements

Overview

This topic describes the components of safety statements that appear in this document.

General structure

Safety statements include the following structural elements:

Item Structure element Purpose

1 Safety alert symbol Indicates the potential for personal injury

(optional)

2 Safety symbol Indicates hazard type (optional)

3 Signal word Indicates the severity of the hazard

SAMPLELifting this equipment by yourself can result in injurydue to the size and weight of the equipment.

Always use three people or a lifting device to transportand position this equipment. [ABC123]

CAUTION

Lifting hazard

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



B-1

Item Structure element Purpose

4 Hazard type Describes the source of the risk of damage or

injury

5 Safety message Consequences if protective measures fail

6 Avoidance message Protective measures to take to avoid the hazard

7 Identifier The reference ID of the safety statement

(optional)

Signal words

The signal words identify the hazard severity levels as follows:

Signal word Meaning

DANGER Indicates an extremely hazardous situation which, if not avoided, will

result in death or serious injury.

WARNING Indicates a hazardous situation which, if not avoided, could result in

death or serious injury.

CAUTION Indicates a hazardous situation which, if not avoided, could result in

minor or moderate injury.

NOTICE Indicates a hazardous situation not related to personal injury.

Hazard statements


Structure of safety statements

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

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

B-2 Alcatel-Lucent – Internal


5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Common cautions and warnings

Common cautions

WARNING

Overhead-load hazard

Cabinet eyebolts can break, severely damaging the cabinet, if a crane is used to lift the

cabinet into an upright position.

Ensure that the cabinet is in an upright position before transportation by crane.

WARNING

Electric-shock hazard

There is a danger of electric shock if the grounding system is inadequate.

You must comply with the grounding requirements for the grounding system.

CAUTION

Lifting hazard

Lifting this equipment by yourself can result in injury due to the size and weight of the

equipment.

Always use three people or a lifting device to transport and position this equipment.

NOTICE

ESD hazard

Electronic components can be destroyed by electrostatic discharge (ESD).

Circuit packs must therefore always be kept in antistatic covers. Use the original

antistatic packaging if possible.

Always observe the general ESD instructions.

NOTICE

Overhead-load hazard

Connectors on the roof of the cabinet can be damaged during transport by the crane

hook, lifting harness, or chains causing damage to the unit.

Avoid any contact between connectors and heavy lifting equipment. Operate with caution.

Hazard statements



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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



B-3

NOTICE

Service-disruption hazard

Condensation can occur in the network element during transport, especially on moving

from outside to closed rooms. Condensation can cause malfunctioning of the circuit

packs.

Ensure that circuit packs and shelves have reached room temperature and are dry before

taking them into operation.

All hazard statements that are not specific to individual procedures are mentioned in this

topic. Hazard statements describe risks, primarily to personnel, that are relevant to

procedures performed during the deployment and/or use of Alcatel-Lucent products.

Failure to avoid the hazards can have serious consequences.

Hazard statements



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

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

B-4 Alcatel-Lucent – Internal


5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Appendix C: Conformance

statements

5400 Linux CP compliance summary

Purpose

This topic provides a summary of compliance of the 5400 Linux CP.

Compliance

The 5400 Linux CP is compliant with the following specifications:

• Telcordia Technologies GR-1089-CORE Sections 2, 3, 4, 5, 6, 7, 8, and 9 (Issue 4,

2006)

• Telcordia Technologies GR-63-CORE Sections 2, 3, 4.0, 4.1, 4.2, 4.3, 4.4, 4.5, 4.6,

and 4.7 (Ed 03, 2006)

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



C-1

Eco-environmental statements

Introduction

This topic provides the eco-environmental statements that apply to Alcatel-Lucent

systems.

Packaging collection and recovery requirements

Countries, states, localities, or other jurisdictions may require that systems be established

for the return and/or collection of packaging waste from the consumer, or other end user,

or from the waste stream. Additionally, reuse, recovery, and/or recycling targets for the

return and/or collection of the packaging waste may be established.

For more information regarding collection and recovery of packaging, and packaging

waste within specific jurisdictions, contact the Alcatel-Lucent Services - Environmental

Health and Safety organization.

For installations not performed by Alcatel-Lucent, contact the Alcatel-Lucent Customer

Support Center at the following telephone number: +1 630 224 4672, prompt 2 (for all

countries).

Recycling / take-back / disposal of product

Electronic products and batteries bearing or referencing the Figure C-1, “Electronic

products symbol” (p. C-3) and Figure C-2, “Batteries symbol” (p. C-3) must be collected

and treated at the end of their useful life, in compliance with applicable European Union

and other local legislation. They must not be disposed of as part of unsorted municipal

waste. Due to materials that may be contained in the product and batteries, such as heavy

metals, the environment and human health may be negatively impacted as a result of

inappropriate disposal.

Note 1: For electronic products put on the market in the European Union, a solid bar

under the crossed-out wheeled bin indicates that the product was put on the market after

13 August 2005.

Conformance statements Eco-environmental statements

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

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

C-2 Alcatel-Lucent – Internal


5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Note 2: For batteries put on the market in the European Union, a chemical symbol Hg

(mercury), Cd (cadmium), or Pb (lead), or a combination of those symbols, beneath the

cross-out wheeled bin indicates that the battery contains the corresponding heavy metals.

In compliance with legal requirements and contractual agreements, where applicable,

Alcatel-Lucent offers to provide for the collection and treatment of Alcatel-Lucent

products bearing the logo at the end of their useful life, or products displaced by

Alcatel-Lucent equipment offers.

For information regarding take-back, recycling, or disposal of equipment by

Alcatel-Lucent or for equipment take-back requests, visit the Alcatel-Lucent Take-Back

web page (http://www.alcatel-lucent.com/product_takeback) or contact Alcatel-Lucent

Takeback Support ([email protected]). For technical information on product

treatment, consult the the Alcatel-Lucent Recycling Information web page

(http://www.alcatel-lucent.com/product_recycling).

Material content compliance - RoHS 2 directive

European Union (EU) Directive 2011/65/EU, “Restriction of the use of certain Hazardous

Substances in electrical and electronic equipment” (RoHS 2), restricts the use of lead,

mercury, cadmium, hexavalent chromium, and certain flame retardants in electrical and

Figure C-1 Electronic products symbol

Figure C-2 Batteries symbol


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

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



C-3

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




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

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

electronic equipment. This Directive applies to electrical and electronic products placed

on the EU market after 2 January 2013, with various exemptions, including an exemption

for lead solder in network infrastructure equipment. Alcatel-Lucent products shipped to

the EU after 2 January 2013 comply with the EU RoHS 2 Directive. Alcatel-Lucent

ensures that equipment is assessed in accordance with the Harmonised Standard

EN50581:2012 (CENELEC) on “Technical documentation for the assessment of electrical

and electronic products with respect to the restriction of hazardous substances”.


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

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

C-4 Alcatel-Lucent – Internal


5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Glossary

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

Numerics

3GPP

Third-Generation Partnership Project

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

C CCITT

Comité Consultatif International Téléphonique et Télégraphique. The CCITT, now known as the

ITU-T (for Telecommunication Standardization Sector of the International Telecommunications

Union), is the primary international body for fostering cooperative standards for

telecommunications equipment and systems.

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

E ESD

Electrostatic Discharge

EU

European Union

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

G GUI

Graphical User Interface

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

L LMT

Local Maintenance Terminal

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

M MI

Management Interface

MT

Maintenance Terminal

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

R RCC

Reliable Cluster Computing

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



GL-1

RMT

Remote Maintenance Terminal

RoHS

Restriction of the use of certain Hazardous Substances

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

S SNE

Subnetwork Element

Glossary

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

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

GL-2 Alcatel-Lucent – Internal


5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Index

A alarm_cli, 2-12, 3-3

alarms

alarm management, 1-1

alarm type, 1-2

category, 1-2

clear using CLI, 3-3

clearance procedures, 2-2

description of, 1-8

display, 2-2

display using CLI, 2-12

manual clearing, 3-2

pick up, 2-21

print, save, 2-14

probable cause, 1-2

save to MT, 2-16

severity, 1-2

unpick, 2-21

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

C cautions and warnings, B-3

compliance

RoHS, C-2

WEEE, C-2

compliance summary, C-1

create

filter for informational alarms,

2-19

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

D document support, ix

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

E eco-environmental statement, C-2

events

save to MT, 2-16

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

F filter for informational alarms

create, 2-19

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

H hazardous substances

RoHS 2 directive, C-3

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

I indicators

alarm indicators, 1-8

alarm state/status, 1-8

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

M manual clearing

alarms, 3-2

material content compliance, C-3

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

N network events

severity, 1-6

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

O operational commands

startMI, A-2

stopMI, A-3

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

P phone numbers

for document support, ix

print, save

alarms, 2-14

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

R RoHS 2 directive, C-3

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

5400 Linux CP

270-702-020R11.0

Issue 1 June 2015



IN-1

Index

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

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

IN-2 Alcatel-Lucent – Internal


5400 Linux CP

270-702-020R11.0

Issue 1 June 2015

Documents

270-702-020R11.0_Issue_1.pdf