coral fault manager · 2015. 6. 29. · 2 about this manual coral fault manager (cfm) installation...

I

Coral

Fault Manager

(CFM)

Installation Manual

Creating a new world of IPportunities

(Edition 3)

© Copyright by TADIRAN TELECOM LTD., 2005-2009.All rights reserved worldwide.

The Coral is Protected by U.S. Patents 6,594,255; 6,598,098; 6,608,895; 6,615,404

All trademarks contained herein are the property of their respective holders.

The information contained in this document is proprietary and is subject to all relevant copyright, patent and other laws protecting intellectual property, as well as any specific agreement protecting TADIRAN TELECOM LTD.'s (herein referred to as the "Manufacturer") rights in the aforesaid information. Neither this document nor the information contained herein may be published, reproduced or disclosed to third parties, in whole or in part, without the express, prior, written permission of the Manufacturer. In addition, any use of this document or the information contained herein for any purposes other than those for which it was disclosed is strictly forbidden.

The Manufacturer reserves the right, without prior notice or liability, to make changes in equipment design or specifications.

Information supplied by the Manufacturer is believed to be accurate and reliable. However, no responsibility is assumed by the Manufacturer for the use thereof nor for the rights of third parties which may be effected in any way by the use thereof.

Any representation(s) in this document concerning performance of the Manufacturer's product(s) are for informational purposes only and are not warranties of future performance, either express or implied. The Manufacturer's standard limited warranty, stated in its sales contract or order confirmation form, is the only warranty offered by the Manufacturer in relation thereto.

This document may contain flaws, omissions or typesetting errors; no warranty is granted nor liability assumed in relation thereto unless specifically undertaken in the Manufacturer's sales contract or order confirmation. Information contained herein is periodically updated and changes will be incorporated into subsequent editions. If you have encountered an error, please notify the Manufacturer. All specifications are subject to change without prior notice.

CFM (Coral Fault Manager) Ins

Table of Contents

TO

C

About this Manual ........................................................................................... 1

Intended Audience ................................................................................... 1

Document Structure ................................................................................. 2

Related Documentation............................................................................ 3

Glossary ................................................................................................... 4

About the CFM ................................................................................................ 5

Overview .................................................................................................. 5

System Architecture ................................................................................. 6

CFM Functionality .................................................................................... 8

SNMP-NMS Functionality....................................................................... 10

Product Specifications............................................................................ 13

Getting Started .............................................................................................. 15

Prerequisites .......................................................................................... 15

Installation Procedure............................................................................. 19

CFM-SP Installation and Configuration ......................................................... 21

CFM-SP Installation Procedure.............................................................. 21

Linux CentOS Installation....................................................................... 22

CFM Server IP Address Configuration ................................................... 26

Complementary Utility Software Installation and Configuration ............. 28

CFM License Key Insertion .................................................................... 31

CFM-SP Installation ............................................................................... 31

CFM-SP Configuration ........................................................................... 34

tallation Manual i

TO

C

SNMP Installation and Configuration ............................................................ 45

SNMPc Installation Procedure ............................................................... 45

SNMPc Installation ................................................................................. 46

CFM Backup File Import......................................................................... 47

CFM Server Association......................................................................... 48

SNMPc Configuration............................................................................. 50

SNMPc Workstation Installation ............................................................. 65

Coral System Procedures ............................................................................. 67

PI Database Programming ..................................................................... 67

External Serial-to-IP Converter Configuration ........................................ 69

SNMP Specifications..................................................................................... 71

Functional Requirements ....................................................................... 71

Traps ...................................................................................................... 72

ii CFM (Coral Fault Manager) Installation Manual

C

1

oral Fault Manager (CFM) Ins

About this Manual

1

The Coral Fault Manager (CFM) Installation Manual is designed for field use by Coral

system installation and service personnel with basic IP knowledge.

This manual describes how to install and configure the CFM system, and complies

with CFM Version 7.xx.

Intended Audience

This manual is intended for authorized technicians installing the CFM. Familiarity

with Coral systems and basic IP knowledge are required.

tallation Manual About this Manual 1

1

Document Structure

The following table provides a detailed outline of each chapter.

Where it is

What it is about When to use it

Chapter 1 About this Manual (this chapter)

To learn about this manual. This chapter introduces the manual structure, describes the target audience, and includes a list of related documentation.

Chapter 2 About the CFM To learn about: The CFM application System terminology Installation steps System planning

Chapter 3 Getting Started For rapid complete installations in the field

Chapter 4 CFM-SP Installation and Configuration

To install and configure Linux CentOS and CFM-SP

Chapter 5 SNMP Installation and Configuration

To install and configure the SNMPc Network Manager

Chapter 6 Coral System Procedures To set up and coordinate communication between the CFM and the Coral system

Chapter 7 SNMP Specifications To add an SNMP-NMS to the system. This chapter includes concise specifications required for integrating a standard SNMP-NMS with the Coral CFM.

2 About this Manual Coral Fault Manager (CFM) Installation Manual

1

Related Documentation

For further information about Coral systems and other information related to the CFM

not in the scope of this manual, see the following documentation:

Subject Manual

Using the CFM Coral Fault Manager (CFM) User Guide

Maintaining the CFM Coral Fault Manager (CFM) Maintenance and Database Support

Integrating the CFM with an external NMS

Coral Fault Manager (CFM) Integration Specification with External NMS

Coral Installation and Hardware Reference Manual

Coral CDRS 200 Coral CDRS 200E Coral FlexiCom 200 Base Unit Coral FlexiCom 200 Expansion Unit Coral FlexiCom 300, 400, 5000 Coral FlexiCom 6000 Coral IPx 500 Coral IPx 800 Coral IPx 3000 Coral IPx 4000 Coral IPx Office

STIP Serial To IP (STIP) Reference Manual

MAP Coral Control Cards (for IPx 500, 800, 3000 and FlexiCom 200, 300, 400, 5000) Installation Procedure and Hardware Reference Manual

Program Interface (Coral database)

Program Interface and Database Reference Manual for Coral Versions 15 or higher

CFM database MySQL documentation Coral Fault Manager (CFM) Maintenance and

Database Support

SNMPc Network Manager

Contact Castle Rock Computing for details.

Coral Fault Manager (CFM) Installation Manual About this Manual 3

1

Glossary

CFM ..............................Coral Fault Manager: The name of the system presented in this manual.

CFM-SP .......................Coral Fault Manager SNMP: A proprietary application that receives alarm information from Coral systems, analyzes it and when applicable, reports it as SNMP trap to the SNMP-NMS server.

SNMP-NMS server .......A standard SNMP monitoring application capable of receiving and reporting SNMP traps. This is an external application not provided by the manufacturer.For example: SNMPc Network Manager (in this manual), HP OpenView, CA.

SNMP workstation.........Client for remote access to the SNMP-NMS server. This is an external application.

SNMP traps...................Unsolicited messages sent from a device that is being monitored by an SNMP-NMS server.

CFM alarm event .........Alarm event (according to CFM-SP analysis). An alarm event is a change in a Coral alarm state. The change means an alarm situation starts (set), an alarm situation clears (clear), or a change in a system counter indicates some alarm related transient event.

4 About this Manual Coral Fault Manager (CFM) Installation Manual

C

2


About the CFM

2

Overview

The Coral Fault Manager (CFM) system provides IT and communication managers

with the information needed to efficiently service Coral systems anywhere in the

world. The CFM ensures successful troubleshooting and recommends corrective

measures.

The CFM is a Linux-based application, integrated with a Windows based SNMP, that

interacts with the Coral systems or networks to rapidly and efficiently detect errors.

The CFM collects alarms and error messages from the Coral systems, assigns severity,

eliminates redundant alarms, and displays the information with recommendations in

any standard browser.

The CFM system consists of a Linux-based CFM-SP server, a Windows-based

SNMP-NMS server, and the monitored Coral sites. (Redundant CFM-SP and

SNMP-NMS servers can be added for system maintenance and survivability.)

The Coral systems or networks send information messages and alarms to the CFM-SP

server through the MAP card or a serial (RS-232) to IP converter, such as a STIP

device. (Coral IPx Office systems are equipped with built-in MAP-equivalent

software and therefore do not require an additional card or converter). The CFM-SP

forwards alarm status information to the SNMP NMS in the form of SNMP traps.

The SNMP-NMS displays the monitored Coral sites as icons with the appropriate

alarm colors. Users at remote sites can double-click the icons to connect to the CFM

database and view a detailed status of each monitored Coral system.

For a graphic presentation of the CFM system, see System Architecture below.

tallation Manual About the CFM 5

2

System Architecture

The following diagrams identify the various components of the CFM system in both

single and redundant scenarios.

Figure 1 CFM Single System

CoralSystem 1

CoralSystem 2

CoralSystem n

CFM - SPLinux PC 1

WorkStation

IP Network

WorkStation

SNMP-NMS

server

SNMPWork

station

SNMPWork

station

SNMPWork

station

SNMPWork

station

6 About the CFM Coral Fault Manager (CFM) Installation Manual

2

Figure 2 CFM with Redundancy

CoralSystem 1

CoralSystem 2

CoralSystem n

CFM - SPLinux PC 2

CFM - SPLinux PC 1

Station

IP Network

WorkStation

SNMP-NMSserver

SNMP-NMSserver

SNMPWork

station

SNMPWork

station

SNMPWork

station

SNMPWork

station

Coral Fault Manager (CFM) Installation Manual About the CFM 7

2

CFM Functionality

The CFM-SP receives and monitors alarm information from the Coral. It attaches a

severity level to this information, filters out redundant data, and gathers current and

historical alarm information in its internal SQL database. Every two minutes, the

CFM-SP sends the Coral alarm status information to the SNMP-NMS.

The CFM initializes, checks the list of monitored Coral systems and establishes a TCP

connection with each of the Coral systems according to the TCP socket (IP address:

TCP port) specified in its data base. Failure to establish a TCP connection results in a

specific CFM alarm event.

The SNMP-NMS can be configured to poll the MIB (Management Information Base)

periodically and to issue a local alarm if a monitored MIB does not respond. This

mechanism sends an alert if the SNMP-NMS and the CFM-SP servers lose IP

connection.

The Coral alarm events are sent under two conditions:

The entire alarm state of a specific Coral site is sent every 15 minutes.

A message is sent out immediately if an alarm is lost or there is a new alarm.

Messages from the Coral are sent in a proprietary binary format and can only be read

in the CFM-SP.

When a new information event is sent by a Coral, the CFM-SP analyzes it upon

receipt. The CFM checks the new message to see if it falls under the criteria of a CFM

alarm event; for instance, if there is a change in the alarm state compared to the

previous recording of the same alarm state. If there is a change, the CFM correlates

the specific alarm with an associated severity value as defined in its database. When

the severity value for an alarm is zero, the alarm is ignored. If the severity is greater

than zero, the CFM does the following:

Updates the relevant current alarm status

Recalculates the overall alarm status of the relevant Coral

Reports overall alarm status change (as SNMP trap) to the SNMP-NMS

Records the alarm event in the CFM history database


2

The following is a description of each of the components of the CFM system.

Table 1 CFM Components

The SNMP trap includes information of the overall severity for each monitored Coral.

Once the NMS receives the relevant icon associated with a specific Coral, it updates

the color to reflect the current overall state of that Coral.

When the SNMP-NMS operator double clicks an icon associated with a Coral, a

standard browser window opens. This allows the user to retrieve more detailed alarm

information. The alarm information accessible via the browser is retrieved from the

CFM-SP.

The CFM sends a constant flow of traps to the SNMP-NMS as a background process

even if there are no new CFM alarm events. This is done to keep the SNMP-NMS

color presentation of the Coral icons up to date even after accidental temporary loss of

communication between the CFM-SP and the SNMP-NMS.

Component Description

CFM-SP Gathers proprietary information from Coral system and attaches a priority or severity level to each alarm

Filters redundant messages Gathers current and historical message information in

its internal SQL based database Generates SNMP traps to send to the designated

SNMP-NMS serversSee Chapter 4, CFM-SP Installation and Configuration on page 21 for more information.

SNMP server Gives a graphic display of the monitored Coral site status with colored icons that represent the severity of the systems’ state

Groups multiple Coral sites in a hierarchical format that allows the user to drill down through the groups to locate a specific Coral site

Allows remote client workstations to access itSee Chapter 5, SNMP Installation and Configuration on page 45 for more information.

SNMP workstation Allows for remote accessing and using of the SNMP application that resides on the SNMP server

Serial-to-IP converter (STIP), MAP card

Interfaces the Coral RS-232 output to the CFM. This component is not required for Coral IPx Office* systems.

* Coral IPx Office systems are equipped with built-in MAP-equivalent software and therefore do not require an additional card or converter


2

SNMP-NMS Functionality

The SNMP-NMS is an external application; its operational specifications may vary

from product to product. The following features are standard:

Icon Presentation of the CFM-SP on page 1-11

Background Map on page 1-11

Multi Level Icon Hierarchy on page 1-12

Email and SMS on page 1-12

These features are generally available in most of the popular products in this category.

This manual assumes Castle Rock Computing's SNMPc Network Manager 7 is used.

For an overall description of features and requirements that apply to all SNMP

applications used with the CFM, see Chapter 7, SNMP Specifications on page 71.

Icon Presentation of Monitored Objects

The CFM application displays, through the SNMP-NMS, each monitored Coral site as

a separate icon that can have one of 5 colors. The color coding represents the Coral's

overall fault state as follows:

Gray—no corresponding Coral definition in the CFM (the operator should call

a CFM technician to fix this)

Green—no active faults

Blue—minor alarm

Yellow—major

Red—critical

The color coding listed above is recommended. Color coding may be re-configured in

some of the SNMP-NMS products. For details, ask your network management

administrator.

The following figure is an example of an SNMP-NMS icon presentation:


2

Figure 3 SNMP-NMS

Icon Presentation of the CFM-SP

The CFM-SP, with a redundant CFM system, can be represented in the SNMP as one

or more icons. The icons:

Indicate CFM-SP fault or loss of connection between the CFM-SP and

SNMP-NMS. Color coding is the same as the Coral icons.

Provide access to a specific CFM-SP for configuration or generation of

network-wide alarm reports. To access a specific CFM-SP, double click its

icon. A browser window opens that connects to the corresponding CFM-SP

Reports page.

Background Map

Most SNMP-NMS products allow a user to configure background maps or diagrams,

such as a building scheme. Icons may be dragged and placed anywhere on the map.

Background maps are for presentation purposes only and have no effect on CFM

functionality.


2

Multi Level Icon Hierarchy

Icons can be arranged in groups. The icons of each group can be placed in their own

map/diagram. The whole group can be represented, in a higher level hierarchy map,

as a single icon. Several group icons can be represented by a single icon in a higher

level hierarchy map. The color of an icon that represents several other icons is the

color of the icon with the highest severity among the subgroup icons.

Email and SMS

Check with the systems administrator to find out if the SNMP-NMS has the capability

to send alerts for new alarms according to specified criteria via email, or SMS.

Other SNMP- NMS Functions

SNMP-NMS systems generally support various additional services such as reports,

MIB browsing, trap viewing, etc. CFM architecture makes limited or no use of these

features, as most of the alarm information and logic is gathered in the CFM-SP itself.

Browsing CFM by Double Clicking an Icon

Each SNMP-NMS icon represents a monitored Coral or CFM-SP server, and is

configured in a way that double clicking it opens an HTML-CFM site related to that

specific object. It displays the related information through a standard browser.


2

Product Specifications

CFM-SP is proprietary software. CFM-SP runs under a Linux operating system and

interacts with several other supporting software packages to produce the functionality

described in CFM Functionality, page 8.

The following software packages are installed on a CFM-SP PC or server:

CentOS 4.1 or CentOS 4.5 (see Prerequisites, page 15 for details)

Apache – HTTP server

MySQL – SQL server

Net-SNMP – SNMP agent

PHP version 4 (for CentOS 4.1) or PHP version 5 (for CentOS 4.5)

Mod_SSL

Open SSL

One USB CFM License Key (dongle)


NOTES:

C

3


Getting Started

3

This chapter lists the required equipment and installation procedures of the CFM

system components.

Prerequisites

The CFM must be installed on a computer running on a Linux CentOS operating

system. There are two manufacturer supplied CentOS versions available (see Table 2).

CentOS 4.1 can only be installed on a PC; CentOS 4.5 can be installed on both a PC

and server.

While the CentOS 4.1 installation is simple and automated, CentOS 4.5 is a manual

installation requiring some expertise on the part of the installer. When installing on a

PC any standard computer complying with the minimum requirements specified in

Table 4 can be used. When installing on a server, one of the servers specified in

Table 3 must be used.

Table 2 CentOS Installation Options

CentOSVersion

Computer Type Included in CFM package

Installation Method

PC Server CentOS Software

Complementary Utility and CFM Software

4.1*

* Note: It is recommended to install CentOS Verion 4.1 when installing on a PC.

— 3 CDs 2 CDs Automatic

4.5 1 DVD 2 CDs Manual

tallation Manual Getting Started 15

3

Server Prerequisites

You can run CFM-SP with CentOS 4.5 on one of the following Dell servers:

Install the CFM-SP only on servers with the specifications provided in the following table. For further details, refer to the relevant Dell server documentation. (Configurations are subject to change without notice.)

Table 3 CFM Server Options

Using a server that does not comply with the specifications below could result in

installation errors and system malfunctions. In addition, the CFM software must be

installed only on one of the servers shown in the table or on a server that may be

approved from time to time by Tadiran. Any attempt to install the software on other types

of servers will void the warranty and support from Tadiran.

Component

Server type

Dell PowerEdge R200

Dell PowerEdge 1950

Dell PowerEdge 2950 III

CPU Dual Core Intel Pentium E2180 at 2.0GHz1MB cache 800MHz FSB

2x Quad-Core Xeon E5410 at 2.33GHz 2x6MB cache1333MHz FSB

2x Quad-Core Xeon E5405 at 2.0GHz2x6MB cache1333MHz FSB

Memory 2GB 4GB

Hard drive 2X160GB (mirroring)

2X160GB (mirroring) Hot plug

3X160GBHot plug

RAID controller

SAS 6i, RAID 1 SAS 6i, RAID 5

DVD 24XIDE internal CD-RW/DVD ROM drive

Rack mounting rails

Versa rails static for 4 post round hole racks

Rack chassis with static versa rails

Rack chassis with no rack rails included

16 Getting Started Coral Fault Manager (CFM) Installation Manual

3

PC Prerequisites

You can run CFM-SP with CentOS 4.1/4.5 on a PC complying with the minimum

requirements specified in the following table.

Table 4 CFM PC — Minimum Hardware Requirements

Network Interface Card

Gigabit Ethernet interface

Power One non-redundant 345W power supply

2X redundant 670W power supply

Redundant 750W power supply with dual cords

Operating Temperature

10-35°C (50-95°F)

Heat Dissipation

2700 BTU/hr

Component

Server type

Dell PowerEdge R200

Dell PowerEdge 1950

Dell PowerEdge 2950 III

Component Requirements

CPU Pentium III 600MHz or equivalent. Recommended: Pentium III 1GHz or equivalent

Memory 512MB RAM

Hard disk space 20GB

Connection IP network connection (broadband, LAN, wireless)

DVD drive 24XIDE internal CD-RW/DVD ROM drive

Server grade platform Recommended

Coral Fault Manager (CFM) Installation Manual Getting Started 17

3

Coral System Prerequisites

The CFM works with Coral systems that have the following card or software versions

installed:

Table 5 Coral Software/ MAP Card Requirements

Table 6 CFM Supported by Coral Version

SNMP-NMS Server Prerequisites

The SNMP application runs on a standard Windows PC. This application is not

supplied and can be SNMPc Network Manager by Castle Rock Computing or any

other equivalent SNMP network management software.

For minimum hardware and software requirements, refer to the relevant product

documentation.

The following software is installed on the PC:

Microsoft Windows (not supplied; the required version depends on the SNMP

network management application)

SNMP network management application (not supplied)

Component Minimum Versions

Coral main software Version 14.66.37 or higher (excluding Version 14.67). For detailed information, see Table 6 below.

MAP card MAP Version 8.08 or higher for Coral software Version 15.5 or higher

IPx Office*

* Coral IPx Office systems are equipped with built-in MAP-equivalent software and therefore do not require an additional card or converter

MAP/PUGW software Version 7 or higher

CFM Application

Coral Software Version

14.66.36or lower

14.66.37 - 14.66.99

14.67 15 15.5 or higher

With MAP card No No No No Yes

With STIP unit or other converter

No Yes No Yes Yes

IPx Office No No No Yes Yes

18 Getting Started Coral Fault Manager (CFM) Installation Manual

3

SNMP Workstation Prerequisites

SNMP workstations are installed SNMP software that allows their users to remotely

access the SNMP-NMS server. Refer to the relevant product documentation.

Installation Procedure

Installing the CFM system involves the following procedures:

1 CFM-SP Installation and Configuration, page 21

2 SNMP Installation and Configuration, page 45

3 SNMPc Workstation Installation, page 65

4 Coral System Procedures, page 67

Coral Fault Manager (CFM) Installation Manual Getting Started 19

NOTES:

C

4


CFM-SP Installation and Configuration

4

This chapter discusses the installation and configuration of the CentOS Linux

platform (in relation to compatibility with the CFM) and CFM-SP.

See CFM PC — Minimum Hardware Requirements, page 17 for a list of required hardware

and software equipment.

CFM-SP Installation Procedure

Installing and configuring the CFM-SP includes the following procedures (order is of

importance):

1 Linux CentOS Installation, page 22

2 CFM Server IP Address Configuration, page 26

3 Complementary Utility Software Installation and Configuration, page 28

4 CFM License Key Insertion, page 31

5 CFM-SP Installation, page 31

6 CFM-SP Configuration, page 34

The CFM-SP Configuration procedure (Step 5) can be performed through the Web browser of any connected workstation. However, it is recommended to access and configure the CFM-SP parameters from the SNMP-NMS server after the SNMP installation and setup (see Chapter 5, SNMP Installation and Configuration on page 45).

tallation Manual CFM-SP Installation and Configuration 21

4

Linux CentOS Installation

The CFM must be installed on a Linux CentOS PC or server. Two CentOS versions

can be used for this purpose, as follows:

CentOS Release 4.1 — Use this version to automatically install CentOS on a

PC according to the specifications described in Table 4 on page 17.

CentOS Release 4.5 — Use this version to a manually install CentOS on a PC

(as above) or on one of the Dell servers specified in Table 3 on page 16.

CentOS Release 4.1 Installation (Recommended)

When installing CentOS Release 4.1, the software package includes three CDs labeled

CentOS Installation Customized for CFM.

To begin the installation process, insert CD1 into the CD drive of the server. Follow

the prompts to insert CD2 and CD3. Once the installation process has been completed,

an automatic reboot is performed.

CentOS Release 4.5 Installation

When installing CentOS Release 4.5, the software package includes one DVD labeled

CentOS Installation Customized for CFM.

Do not plug in the CFM License key (dongle) until the CentOS Installation is completed (see CFM License Key Insertion, page 31).

To install and configure CentOS Release 4.5:

1 Insert the CentOS Installation Customized for CFM disk into the DVD drive.

The CentOS main screen is displayed.

2 Type linux and press ENTER. The Welcome to CentOS-4 i386 screen is

displayed.

3 Select the Skip option and press ENTER.

4 Click Next. The Language Selection screen is displayed.

5 Select a language to use for the installation (U.S. English is recommended)

and click Next. The keyboard Configuration screen is displayed.

6 Select the appropriate language (English is recommended) and click Next. The

Installation Type screen is displayed.

22 CFM-SP Installation and Configuration Coral Fault Manager (CFM) Installation Manual

4

7 Select the Custom option and click Next. The Disk Partitioning Setup screen

is displayed.

8 Ensure the default option is selected (Automatic partitioning) and click Next.

The Automatic Partitioning screen is displayed.

9 Ensure the default option is selected (Remove all Linux partitions on this

system) and click Next. A Warning is displayed.

10 After reading the warning, click Yes to continue. The Disk Setup screen is

displayed.

11 Click Next. The Boot Loader Configuration screen is displayed.

12 Leave the default settings unchanged and click Next. The Network

Configuration screen is displayed.

13 Leave the default settings unchanged and click Next. The Firewall

Configuration screen is displayed.

14 Select the No firewall option. From the Enable SELinux drop-down list

located at the bottom of the screen, select Disabled and then click Next. A

Warning is displayed.

15 After reading the warning, click Proceed to continue. The Additional

Language Support screen is displayed.

16 Select the default language for the system (English (USA) is recommended)

and click Next. The Time Zone Selection screen is displayed.

17 Select the appropriate time zone according to your location and click Next.

The Set Root Password screen is displayed.

18 Type eciipg in the Root Password and Confirm text boxes, and click Next.

The Package Group Selection screen is displayed.

19 Configure settings of the following categories:

a Desktops

X Window System – leave default setting unchanged

GNOME Desktop Environment – leave default setting unchanged

KDE Desktop Environment – select the check box

b Applications

Editors – leave default setting unchanged

Engineering and Scientific – leave default setting unchanged

Graphical Internet – leave default setting unchanged

Office/Productivity – clear the check box

Coral Fault Manager (CFM) Installation Manual CFM-SP Installation and Configuration 23

4

Sound and Video – clear the check box

Authoring and Publishing – leave default setting unchanged

Text-based Internet – leave default setting unchanged

Graphics – leave default setting unchanged

Games and Entertainment – leave default setting unchanged

c Servers

Server Configuration Tools – select the check box

Web Server – click Details, select all the options, and click OK.

Mail Server – leave default setting unchanged

Windows File Server – select the check box

DNS Name Server – leave default setting unchanged

FTP Server – select the check box

PostgreSQL. Database – leave default setting unchanged

MySQL. Database – click Details, select all the options, and click OK.

News Server – leave default setting unchanged

Network Servers – select the check box

Legacy Network Server – select the check box

d Development

Development Tools – click Details, select all the options, and click OK.

X Software Development – leave default setting unchanged

GNOME Software Development – select the check box

KDE Software Development – select the check box

Legacy Software Development – select the check box

e System

Administration Tools – select the check box

System Tools – click Details, select the mc option, and click OK. Ensure

that the check boxes of the other packages remain as they are.

Printing Support – leave default setting unchanged

f Miscellaneous

Everything – leave default setting unchanged

Minimal – leave default setting unchanged

20 Click Next. The About to Install screen is displayed.


4

21 Click Next and wait for the installation process to complete. Note that

installing the packages may take a few minutes.

22 Once the installation is complete, the Installation Completed screen is

displayed. Remove the disk from the DVD drive and reboot the server.

23 Once the server reboots, the Welcome screen is displayed.

24 Click Next. The License Agreement screen is displayed.

25 Click Next. The Date & Time screen is displayed. Select the current local date

and time and click Next. The Display screen is displayed.

26 Click Next. The System User screen is displayed. Fill in the text boxes as

required and click Next. The Additional CDs screen is displayed.

27 Click Next. The Finish Setup screen is displayed indicating that CentOS setup

is complete.

28 Click Next. The CentOS GNOME Logon screen is displayed.

29 Log on by typing first the Username (root) and then the Password (eciipg).

The CentOS GNOME desktop is displayed.


4

CFM Server IP Address Configuration

After rebooting for the first time, perform the following procedure to assign an

allocated static IP address to the CFM server.

After performing the above automatic installation, CentOS sessions run in GNOME (not KDE) mode by default. If you choose to use KDE mode, you will have to adapt the steps below accordingly.

1 On the CentOS icon toolbar, click the Applications icon, and select

System Settings>Network. The Network Configuration dialog box is displayed.

Figure 4 Network Configuration Dialog Box

2 Ensure that the row with the device ending in ‘0’ is selected and click Edit.

The Ethernet Device dialog box is displayed.


4

Figure 5 Ethernet Device Dialog Box

3 Select the Statically set IP address option.

4 In the Address text box, type in the IP address of this server.

5 In the Subnet mask text box, type in the subnet mask used for the network.

6 In the Default gateway address text box, type in the address of the gateway to

which the computer is connected.

7 Click OK to return to the Network Configuration dialog box.

8 Select File>Save to save the configuration.

9 Select Yes in the question box that is displayed and click OK.

10 Reboot the server to implement the configuration in the network.


4

Complementary Utility Software Installation and Configuration

The Complementary Utility Software is part of the Linux CentOS software bundle. It

is installed and configured on the CFM server, and allows the CFM to work properly

with Linux CentOS.

The following procedure describes:

The installation of the utility software

The setting up of services in the Service Configuration window

To install and configure the Complementary Utility Software:

1 If required, log on to the CFM server.

2 Insert the CFM CD1 into the CD drive. A CD icon should appear on the

desktop; if it does not, the installation must be performed from a terminal

window, as described in Utility Installation through Terminal Window, page 30.

3 Double-click the CD icon. Depending on which CentOS release you installed,

one of the following windows is displayed (Figure 6 and Figure 7).

Figure 6 cdrom Window (for CentOS 4.1)


4

Figure 7 cdrecorder1 Window (for CentOS 4.5)

4 If you are running CentOS 4.1, double-click install_disk1 or, if you are

running CentOS 4.5, select the corresponding install_disk1 file from the

CentOS_4.5_RAID directory. The Run or Display dialog box is displayed.

5 Click Run in Terminal. A terminal window opens and automatically runs the

install.exe file. Note that this step may take a few minutes to complete.

After the installation finishes, the terminal window displays the

Configuration Section and several prompts. Press ENTER in response for

each prompt without specifying any value.

When the configuration is completed, the terminal window displays the

message Disk1 INSTALLATION SUCCESSFUL.

6 Press ENTER to close the terminal window.

7 Close the cdrom window.

8 Right-click the CD icon on the desktop and select Eject to remove the CD

from the CD-drive.

Tip:

If the CD drive remains closed, open a terminal window, type eject and

press ENTER.


4

Utility Installation through Terminal Window

Use this procedure if after inserting the CFM CD1 in the CD drive, the CD icon does

not appear on the desktop.

To perform the utility installation from a terminal window:


System Tools>Terminal. (You can click the terminal window icon, , instead

if it is available on the toolbar or desktop.)

A terminal window opens with the [root@localhost ~]# command line prompt

displayed.

Figure 8 Terminal Window

2 After the prompt, type mount /media/cdrom and press ENTER.

3 Type cd /media/cdrom and press ENTER.

4 Type ./install_disk1 (or, if you are running CentOS 4.5, type

.CentOS_4.5_RAID/install_disk1)and press ENTER. The window runs the

install.exe file.

After the installation finishes, the terminal window displays the

Configuration Section and several prompts. Press ENTER in response for

each prompt without specifying any value.

When the configuration is completed, the terminal window displays the

message Disk1 INSTALLATION SUCCESSFUL.

5 Press ENTER to close the terminal window.

6 Eject the CD: Type eject after the command-line prompt and press ENTER.


4

CFM License Key Insertion

Prior to installing the CFM-SP software, plug in the supplied CFM license key

(dongle) into a USB port.

CFM-SP Installation

The CFM-SP software is installed on the CFM server after the installation and

configuration of CentOS and Complementary Utility software described in the

previous sections.

The CFM-SP software installation also includes a CFM license check. Prior to starting

this procedure, ensure your CFM license key (dongle) is available.

Use this procedure also to upgrade the CFM-SP with an new version.

To install CFM-SP:

1 Insert the CFM CD2 into the CD drive. A CD icon should appear on the

desktop. If it does not, the installation must be performed from a terminal

window, as described in CFM-SP Installation through Terminal Window, page 32.

2 Double-click the CD icon. The cdrom (CentOS 4.1) or cdrecorder (CentOS

4.5) window is displayed.

3 Double-click install_disk2 if you are running CentOS 4.1 or, if you are

running CentOS 4.5, select the corresponding install_disk2 file from the

CentOS_4.5_RAID directory. The Run or Display dialog box is displayed.

4 Click Run in Terminal. A terminal window opens and automatically runs the

install.exe file.After the installation finishes, the terminal window displays the

message CFM INSTALLATION SUCCESSFUL.

5 Press ENTER. The system starts the CFM application. This process includes

organizing the MySQL database and may take up to five minutes.

If the message MISSING OR INVALID LOCK DEVICE is displayed, the

CFM license key is faulty or missing. Contact the manufacturer for help.

6 Press ENTER to close the application and the terminal window.



from the CD-drive.


4

CFM-SP Installation through Terminal Window

Use this procedure if after inserting the CFM CD2 in the CD drive, the CD icon does

not appear on the desktop.

To perform the CFM-SP installation from a terminal window:


System Tools>Terminal. (You can click the terminal window icon, , instead

if it is available on the toolbar or desktop.)

A terminal window opens with the [root@localhost ~]# command line prompt

displayed.

2 After the prompt, type mount /media/cdrom and press ENTER.

3 Type cd /media/cdrom and press ENTER.

4 Type ./install_disk2 (or, if you are running CentOS 4.5, type

.CentOS_4.5_RAID/install_disk2)and press ENTER. The window runs the

install.exe file. After the installation finishes, the terminal window displays the

message CFM INSTALLATION SUCCESSFUL.

5 Press ENTER. The system starts the CFM application. This process includes

organizing the MySQL database and may take up to five minutes.

If the message MISSING OR INVALID LOG DEVICE is displayed, the

CFM license key is faulty or missing. Contact the manufacturer for help.

6 Press ENTER to close the application and the terminal window.



from the CD-drive.

9 Restart the system.


4

Services Configuration

To configure service settings:


System Settings>Server Settings>Services. The Service Configuration window

opens.

Figure 9 Service Configuration Window

2 In the left pane, scroll down to the iptables service and clear the check box.

3 If not already selected, select the check boxes of the following services:

httpd

mysqld

snmpd

snmptrapd

vsftpd

4 Click Save on the toolbar and close the window.

5 Restart the system.


4

CFM-SP Configuration

This section describes how to configure the CFM-SP to ensure functional

communication with the Coral systems and the SNMP-NMS server or servers.

CFM-SP configuration and maintenance is performed through the Web-based

HISTORY CFM FROM MYSQL User Interface. For a detailed description of using

the User Interface capabilities and options, refer to the Coral Fault Manager (CFM)

User Guide (see Related Documentation, page 3).

This section includes the following procedures:

Accessing CFM-SP Maintenance Parameters, page 35

Configuring General Parameters, page 37

Defining Coral Site Information, page 39

Configuring Messages for STIP, page 42

Defining Message Severity, page 43

Setting User Interface Language, page 44

Monitoring the CFM Database, page 44

The implementation of changes in the system takes up to five minutes once they have been saved.


4

Accessing CFM-SP Maintenance Parameters

To access the CFM-SP maintenance options:

1 Do either of the following:

In the SNMPc Management Console window, double-click the CFM icon.

(To learn about how to access the SNMPc application, see Chapter 5, SNMP

Installation and Configuration on page 45.)

On a workstation connected to the CFM system, open the Web browser and

enter http://<CFM IP address>/cfm/show1.php in the Address bar.

(Replace <CFM IP address> with the IP address of the CFM server.)

The History CFM Web portal is displayed.

Figure 10 HISTORY CFM Web Portal

2 Select CFM maintenance and click OK. The Login page is displayed.

3 Enter the default Username Administrator and the default Password vladimir.

4 Click Enter. The page displays five options.

5 Next to Enter maintenance, click OK. The CFM parameters page is

displayed.


4

Figure 11 CFM Parameters Page

6 Configure the CFM parameters using the Maintenance Menu options at the

bottom of the page, as described in the following procedures.

7 Close the Web browser.


4

Configuring General Parameters

General parameters include the number and type of traps (alarms) sent to the

SNMP-NMS servers, as well as the IP location of these servers.

In the current CFM version, you can define up to two internal and/or up to five

SNMP-NMS servers. While the traps sent to internal servers are constantly updated

(refreshed), only new traps are sent to external SNMP-NMS servers.

Traps to internal and external servers do not use the same format. The internal trap format is described in Traps, page 72. For a detailed description of external traps, refer to CFM Integration Specification with External NMS (see Related Documentation, page 3).

To set general parameters:

1 At the bottom of the CFM parameters page (see Figure 11), select Edit

General from the Maintenance Menu and click OK. The General information

page is displayed.

Figure 12 CFM General Information Page


4

2 Set the general parameters as follows:

3 In the Trap Destinations table, define the SNMP NMS server or servers to

which the CFM alarms are to be sent. Specify the following for each server:

TRAP DESTINATION ADDR – Enter the IP address of the server.

TRAP TYPE – Select CFM_SERVER for an internal server (such as an

SNMPc server) or NMS_SERVER for an external server. (You can define

up to two internal and up to five external servers.)

COMMENT – Enter an optional description of the server.

4 To save the changes, click Save. (To discard the changes, click the Back icon

on your Web browser toolbar.) The Changes have been saved page is

displayed.

5 To return to the CFM parameters page, click Return to Maintenance.

Parameter Description

Maximum Concurrent Alarms to NMS(Default: 10)

The maximum number of new alarms (traps) the CFM server sends at the same time to the SNMP-NMS.Depending on the SNMP application, these alarms can be forwarded to operators per email or SMS.

Lowest Severity to NMS(Default: 1)

The minimum severity of alarms that are sent to the SNMP-NMS. Alarms of lower severity are not sent.To learn more about severity codes of Coral messages, see Defining Message Severity, page 43.


4

Defining Coral Site Information

The site details must be added for each Coral to be monitored by and displayed in the

CFM. Up to 256 sites can be defined.

Use the following procedures to define which Coral sites are included in the CFM

system:

Adding or Updating Coral Sites below

Deleting Coral Sites, page 41

In the CFM, only one Coral device (unit) is allowed per Coral site.

Adding or Updating Coral Sites1 At the bottom of the CFM parameters page (see Figure 11), select Edit site

information from the Maintenance Menu and click OK. The Site details page

is displayed.

Figure 13 CFM Site Details Page


4

2 Add or update a Coral site definition as follows:



displayed.



CORAL NAME The name of the Coral site.

NOTE: You cannot update the Coral name of an already defined site.

IP ADDRESS For Coral IPx Office systems: the Coral IP address For Corals using a MAP card: the MAP IP address For Corals connected to a STIP or other

serial-to-IP converter: the IP address of the STIP or converter

NOTE: Do not use the same IP address for different sites.

IP PORT The IP port of the Coral, MAP card, STIP, or other converter

IP PORT RELAY The second IP port of the STIP used for monitoring external devices. This field is only relevant for STIP-connected Corals.

URL NAME The Coral name in Latin letters as included in its URL address. If this field is empty and the CORAL NAME (see above) includes only Latin letters, the CORAL NAME value is also used as the URL NAME.

NOTE: You cannot update the URL name of an already defined site.


4

Deleting Coral Sites1 At the bottom of the CFM parameters page (see Figure 11), select Delete site

information from the Maintenance Menu and click OK. The Delete sites page

is displayed.

Figure 14 CFM Delete Sites Page

2 In the Site Name box, click the Coral site to be deleted. You can select

multiple sites by pressing the SHIFT or CTRL keys while clicking.

3 Click Delete selection. (To cancel the deletion, click the Back icon on your

Web browser toolbar.) The Changes have been saved page is displayed.



4

Configuring Messages for STIP

This procedure must only be performed if the Corals use STIP converters.

A STIP port can monitor up to four devices and check whether they are currently

operating (active) or not. You can set the severity and text of the resulting messages.

To configure STIP messages:

1 At the bottom of the CFM parameters page (see Figure 11), select Messages

definition from the Maintenance Menu and click OK. The STIP message

configuration table is displayed.

Figure 15 CFM STIP Message Configuration

2 For each STIP INPUT STATUS message, specify the following:

Message severity – in the Severity column, assign the message a Coral

severity level between 0 (normal) and 3 (critical)

Displayed text – in the Fault Type column, enter the message text. For

each inactive message, the text must be preceded by Cleared:.



displayed.



4

Defining Message Severity

The CFM attaches an alarm severity level to each message. The following severity

codes are used:

0 – Normal, no alarm issued for the message

1 – Minor alarm

2 – Major alarm

3 – Critical alarm

To change the severity level of messages:

1 At the bottom of the CFM parameters page (see Figure 11), select Severity

definition from the Maintenance Menu and click OK. The Severity definition

page is displayed.

Figure 16 CFM Severity Definition Page

2 In the SEVERITY column, change the severity code for the relevant messages

where required.



displayed.



4

Setting User Interface Language

The CFM user interface and the messages are displayed in English by default. You can

configure the system to use another language instead. Currently available options are

English, Russian, and Chinese.

To change the user interface language:

1 At the bottom of the CFM parameters page (see Figure 11), select Language

definition from the Maintenance Menu and click OK. The Language

definition page is displayed.

Figure 17 CFM Language Definition Page

2 From the Language drop-down list, select the language and click Change

Language. (To discard the change, click the Back icon on your Web browser

toolbar.) The Changes have been saved page is displayed.


Monitoring the CFM Database

The CFM User Interface includes a Database Support option, from which the CFM

database can be archived, exported, and restored.

It is recommended to perform these functions through MySQL, since the CFM

Database Support requires TFTP server access. Refer to the MySQL documentation

for detailed instructions.

For instructions on how to use the CFM Database Support option, refer to the

CFM Maintenance and Database Support manual (see Related Documentation, page 3).


C

5


SNMP Installation and Configuration

5

000

This chapter describes how to install and configure the SNMP-NMS server for the

CFM system. Proper SNMP installation and configuration is crucial for the proper

transmission of alarm information.

This chapter assumes that Castle Rock’s SNMPc Network Manager 7 is the SNMP application used in the CFM system. However, any standard SNMP network management application, such as HP OpenView, can be integrated with the system (see Chapter 7, SNMP Specifications on page 71).

SNMPc Installation Procedure

Installing and configuring the SNMPc includes the following procedures (order is of

importance):

1 SNMPc Installation, page 46

2 CFM Backup File Import, page 47

3 CFM Server Association, page 48

4 SNMPc Configuration, page 50

5 SNMPc Workstation Installation, page 65

tallation Manual SNMP Installation and Configuration 45

5

SNMPc Installation

Install the SNMPc Network Manager on the SNMPc server.

SNMPc Network Manager is an external software application offered by Castle Rock

Computing. Refer to the Castle Rock Web site for general information, purchase

options, and product documentation.

Basic guidelines about how to set up the network structure and elements in SNMPc

Network Manager for the CFM system are provided in SNMPc Configuration, page 50

and are subject to changes depending on the application version.

46 SNMP Installation and Configuration Coral Fault Manager (CFM) Installation Manual

5

CFM Backup File Import

The CFM software comes with a sample network configuration backup file. It is

recommended to import this file into the SNMPc application as described below, and

then adjust or change the configuration to suit the setup of your network, as described

in SNMPc Configuration, page 50.

Alternatively, you can define your network configuration from scratch. However, this

requires additional programming of SNMPc status and SNMP trap color-coding

(see Setting up Alarm Color Coding for Icons, page 59).

To import (restore) the sample CFM backup file:

1 On the SNMPc server, create a new directory under

C:\Program Files\SNMPc Network Manager\ and rename it to backup

(all letters lowercase).

2 Insert the CFM CD2 into the CD drive of the server and display its contents in

a Windows Explorer window.

3 Under the SNMPc_v7_DB_Restore directory, select last_backup and copy it

into the backup directory created in Step 1 above.

4 Click start and then select SNMPc Network Manager>Startup System. The

SNMPc Management Console window opens.

5 Click the File menu and select Restore. The Restore Files dialog box is

displayed.

Figure 18 Restore Files Dialog Box

6 Select last_backup and click Restore.

Coral Fault Manager (CFM) Installation Manual SNMP Installation and Configuration 47

5

CFM Server Association

The SNMPc server must know the assigned static IP address of the CFM server in

order to work with the CFM. For this purpose, the CFM server name and IP address

must be defined in the SNMPc hosts file, as described in the following procedure.

To define the CFM server name and IP address in the SNMPc server:

1 Find the file: Open a Microsoft Windows Explorer window and run a search

for hosts.

Figure 19 hosts File Search

2 Open the hosts file (all lowercase letters) with Microsoft Word.

3 After the last line in the hosts file, type in the CFM IP address, three spaces

later type in the CFM server name, and press ENTER.

If you use the sample backup file (see CFM Backup File Import, page 47), the

CFM server name is CFM3.


5

Figure 20 hosts File with CFM IP Address added

4 If a redundant CFM server is available, type in the IP address of the redundant

server, three spaces later type in the name of the server, and press ENTER.

5 Save and then close the hosts file.


5

SNMPc Configuration

The proper configuration of the SNMPc server is crucial for its operation with the

CFM server.

This section describes the basic procedures required for setting up the Coral devices

and the CFM server in the SNMPc Network Manager. Details in these procedures may

vary depending on the version of the application. Refer to the Castle Rock Computing

documentation for further information.

The SNMPc configuration includes the following procedures (order is of importance):

Accessing the SNMPc Network Manager, page 51

Defining Submaps, page 52

Defining Coral Devices, page 54

Defining the CFM Server, page 57

Setting up Alarm Color Coding for Icons, page 59

Creating a Backup File, page 64


5

Accessing the SNMPc Network Manager

To open and customize the SNMPc Management Console window:

1 Click start and then select SNMPc Network Manager>Startup System. The

SNMPc Management Console window opens.

2 From the View menu, click Toolbars, and make sure all toolbars are selected.

3 From the View menu, click Selection Tool. The imported or defined Coral

sub-networks (submaps) and CFM icons are displayed in the Selection Tool

pane.

Figure 21 SNMPc Network Manager Window


5

Defining Submaps

Submap elements, or subnets, are used for representing Coral sub-networks in the

SNMPc application.

Add new, edit, or delete submaps as required. If you have imported the sample backup

file (see CFM Backup File Import, page 47), its submaps are displayed in the Selection

Tool pane. You can delete them and define your submaps instead or modify them to

suit your network requirements.

Once you have set up a submap, you can define the Coral devices belonging to this

submap (see Defining Coral Devices, page 54).

To define a submap:

1 In the Selection Tool pane, click the Map tab if required.

2 Add or modify a submap.

To add a new submap: From the Insert menu, select Map Object>Submap.

To modify an existing submap: In the Selection Tool pane, right-click the

submap and select Properties.

The submap Map Object Properties dialog box is displayed with the General

tab selected.

Figure 22 Map Object Properties Dialog Box for Submap

3 In the Label text box, enter the name of the submap.

4 Optionally click the Attributes tab and set bitmap-related parameters.


5

Do not define an Address for a submap.

5 To save and close, click OK.

Repeat this procedure to define further submaps.

To delete a submap:

1 In the Selection Tool pane, click the submap.

2 From the Edit menu, select Delete. A confirmation dialog box is displayed.

3 Click Yes. The submap is removed from the Selection Tool pane.

Deleting a submap also deletes all devices under this submap.


5

Defining Coral Devices

Device elements are used for representing Coral sites in the SNMPc application. Each

Coral device must be created and configured individually to be displayed in the

SNMPc.

Coral devices must be assigned to a submap, therefore make sure the relevant submap

exists before defining the device. See Defining Submaps, page 52 for details.

If you have imported the sample backup file (see CFM Backup File Import, page 47), its

Coral devices are assigned to its submaps displayed in the Selection Tool pane. You

can select any submap and add new, edit, or delete the Coral devices assigned to this

submap.

To define a Coral device:


2 Select a submap.

3 Add or modify a Coral device belonging to the submap.

To add a new Coral device: From the Insert menu, select

Map Object>Device.

To modify an existing Coral device: In the Selection Tool pane, click the

submap node to display its Coral devices, right-click the relevant device,

and select Properties.

The device Map Object Properties dialog box is displayed with the General

tab selected.

Figure 23 Map Object Properties Dialog Box for Device

Coral IP address


5

4 In the Label text box, enter the Coral name.

5 In the Address text box, enter the IP address as follows:

For an Coral IPx Office—the IP address of the Coral

For a Coral connected to IP through a MAP—the MAP IP address

For a Coral connected to IP through a STIP or other R-232–to–IP

converter—the converter IP address

6 Click the Access tab.

7 In the Attrib box, select Trap Community. Enter netman (lowercase letters

only) in the Value text box.

8 Click the Attributes tab.

Figure 24 Map Object Attributes for Coral Device


5

9 The Attributes parameters and their values are displayed in the Attrib box. To

set a parameter, select it and enter its value in the Value box. The following

parameters need to be defined:


Repeat this procedure to define further Coral devices.

To delete a device:

1 In the Selection Tool pane, click node submap to which the device belongs and

select the device.

2 From the Edit menu, select Delete. A confirmation dialog box is displayed.

3 Click Yes. The submap is removed from the Selection Tool pane.

Deleting a submap also deletes all devices under this submap.


Exec Program Enter the path to the Coral configuration GUI as follows:http://<CFM server name>/cfm/<Coral name>.htm

Replace <CFM server name> with the CFM name specified in the hosts file (see CFM Server Association, page 48) and <Coral name> with the URL Name of the Coral site (see Adding or Updating Coral Sites, page 39). If you use the backup file, the set CFM server name value is cfm3.Double-clicking the Coral device icon will open the relevant CFM Events and State page in your Web browser. For further information about CFM reports and system maintenance, refer to the CFM User Guide (see Related Documentation, page 3.)

Poll Interval Set this parameter to 0 (no polling).


5

Defining the CFM Server

The CFM server is configured as a stand-alone device that does not belong to any

Coral sub-network. An additional CFM server can be defined for redundancy.

The sample backup file includes a CFM server. If you have imported this file (see CFM

Backup File Import, page 47), you can leave the CFM parameter values as they are,

except for the Address.

To define the CFM server:


2 Add or modify the CFM server device.

Add: From the Insert menu, select Map Object>Device.

Modify: In the Selection Tool pane, right-click the CFM device and select

Properties.

The device Map Object Properties dialog box is displayed with the General

tab selected.

3 In the Label text box, enter the name of the CFM server. (In the backup file,

the name of the CFM server is CFM.)

4 In the Address text box, enter the IP address of the CFM server.

5 Click the Attributes tab.

Figure 25 Map Object Attributes for CFM Server


5

6 The Attributes parameters and their values are displayed in the Attrib box. To

set a parameter, select it and enter its value in the Value box. The following

parameters need to be defined:


Repeat this procedure to define a redundant CFM server, if available.


Exec Program Enter the path to the CFM Reports and Maintenance page as follows:

http://<CFM server name>/cfm/show1.phpReplace <CFM server name> with the name specified in the hosts file (see CFM Server Association, page 48). If you use the backup file, the set value is cfm3.Double-clicking the CFM icon will open the CFM Reports and Maintenance page in your Web browser. For further information about CFM reports and system maintenance, refer to the CFM User Guide (see Related Documentation, page 3.)

Poll Interval The interval in seconds between the polling attempts. The recommended value is 30.

Polling Agent The server that runs the polling software. By default this is localhost (the CFM server itself). If another device is used for polling, enter its IP address instead.


5

Setting up Alarm Color Coding for Icons

The following settings are required for the system to use the proper alarm color

coding:

Tuning Event Actions for SNMPc Status Polling below—for CFM server alarms

Tuning Event Actions for SNMP Traps, page 62—for Coral site alarms

The sample backup file comes with preconfigured color coding settings. If you use the sample backup file (see CFM Backup File Import, page 47), there is no need to define the color coding.

Tuning Event Actions for SNMPc Status Polling1 In the Selection Tool pane, select the Event tab. The Event tab displays the

Event Actions tree.

2 Click the Snmpc-Status-Polling node to expand it and display its alarm items.

Figure 26 Event Tab — SNMPc Status Polling


5

3 For each of the Snmpc-Status-Polling items do the following:

a Right-click the item and select Insert Event Filter. The Add Event Filter

dialog box is displayed.

b Click the Actions tab.

Figure 27 SNMPc Status Polling — Add Event Filter Dialog Box (Actions Tab)


5

c From the Set Priority drop-down list, select the alarm priority as follows:

d To save and close, click OK.

4 Verify you have followed Step 3 above for each Snmpc-Status-Polling item.

Item Priority

pollDeviceDown Critical-Red

pollNoResponse Major-Yellow

pollRequestRejected Major-Yellow

pollResponse Normal-Green

pollServiceDown Critical-Red

pollServicePollFailed Major-Yellow

pollServiceResponding Normal-Green

pollStatusTestFail Minor-Magenta

pollStatusTestPass Normal-Green


5

Tuning Event Actions for SNMP Traps1 In the Selection Tool pane, select the Event tab. The Event tab displays the

Event Actions tree.

2 Click the SnmpcTraps node to expand it and display its alarm items.

Figure 28 Event Tab — SNMPc Traps

3 For each of the SnmpcTraps items do the following:

a Right-click the item and select Insert Event Filter. The Add Event Filter

dialog box is displayed.

b Click the Actions tab.


5

Figure 29 SNMPc Traps— Add Event Filter Dialog Box (Actions Tab)

c From the Set Priority drop-down list, select the alarm priority as follows:

d In the Clear Events box, individually select and click Yes to clear each

item in the box.

(Clear) is now displayed after each of these items.

e To save and close, click OK.

4 Verify you have followed Step 3 above for each SnmpcTraps item.

Item Priority

authenticationFailure Normal-Green

coldStart Critical-Red

egpNeighborLoss Warning-Blue

linkDown Warning-Blue

linkUp Normal-Green

warmStart Major-Yellow


5

Creating a Backup File

Once you have completed the SNMPc configuration as described in the previous

steps, it is recommended you create a backup. In cases of data corruption, this backup

can be used to restore the configuration (see CFM Backup File Import, page 47).

This procedure can be performed directly on the SNMPc server or remotely from an

installed SNMPc workstation (see SNMPc Workstation Installation, page 65). In either

case, the backup will be stored on the server, not on the workstation.

To create a backup:

1 On the SNMPc server, make sure a directory called backup (all letters

lowercase) exists under C:\Program Files\SNMPc Network Manager\.

2 On the SNMPc Management Console window (see Figure 21), click the File

menu and select Backup. The Backup Files dialog box is displayed.

Figure 30 Backup Dialog Box

3 Select last_backup and click Backup.


5

SNMPc Workstation Installation

The SNMPc workstation allows the end-user to view the status, alarms, and error

messages of all the Coral units in the system.

For details about the installation and use of the SNMPc workstation, refer to the

documentation of the used SNMPc product.


NOTES:

C

6


Coral System Procedures

6

This chapter describes the procedures that are required to allow Coral units to operate

with the CFM system:

PI Database Programming below

External Serial-to-IP Converter Configuration, page 69

PI Database Programming

The installation of the CFM in the Coral system has considerable impact on the system

database.

Use the Coral Program Interface (PI) to verify that each of the parameters detailed

below is set correctly. Refer to the Program Interface and Database Reference Manual

for more information (see Related Documentation, page 3).

The CFM works only with Coral PI Software Version 15 or higher.

Feature Authorization (Route: FEAT,1)

DISPLAY CURRENT indicates which features are authorized for use in this Coral

system.

CFM

This feature item must be set to Yes in order to authorize the Coral system to send

diagnostic and alarm messages to the CFM application. If it is set to No, contact your

dealer.

tallation Manual Coral System Procedures 67

6

Message Control (Route: MSG,2,0)

FAILURE REPORT

This item displays (Yes) or hides (No) CFM information messages provided by the

Coral system, as they occur.

FAILURE REPORT must be set to Yes to use the CFM feature in the Coral system.

Message Destination (Route: MSG,2,2)

DIAG

The DIAG item identifies the PI terminal port number to which the requested CFM

messages are sent.

Do not use KB0 for dual control IPx 3000, 4000 and FlexiCom 5000, 6000 systems. KB0 is reserved for maintenance purposes.

KeySet Definition (Route: KEY)

SEND FAILURE REPORT

This item determines whether or not a keyset station in UNDEFINED state is reported

to the CFM system. For each station to be reported, SEND FAILURE REPORT must

be set to Yes.

SLT Definition (Route: SLT)

SEND FAILURE REPORT

This item determines whether or not a SLT station in LOCKOUT state is reported to

the CFM system. For each station to be reported, SEND FAILURE REPORT must be

set to Yes.

68 Coral System Procedures Coral Fault Manager (CFM) Installation Manual

6

External Serial-to-IP Converter Configuration

Coral systems without installed MAP cards require an external serial-to-IP converter

(except for Coral IPx Office systems). This converter can be a STIP or a third-party

product.

The converter is required to translate the Coral information from its serial format into

IP format.

STIP

The STIP has four serial ports for four Coral systems. Configure the STIP to ensure

functional communication between the STIP, the Coral systems, and the CFM. For

instructions, refer to the STIP Reference Manual (see Related Documentation, page 3).

Configure the STIP before you plug it into the Coral.

Plug only one Coral into a STIP. The CFM will display inaccurate colors for the icons if more than one Coral are plugged into the same STIP.

Third-Party Serial-to-IP Converters

Instead of the STIP, any RS-232 to Ethernet converter can be used to interface the

Coral RS-232 output to the CFM, for example Lantronix UDS-10. Contact the

relevant manufacturer for details.

Coral Fault Manager (CFM) Installation Manual Coral System Procedures 69

NOTES:

C

7


SNMP Specificationsfor Integration with CFM

7

The CFM system integrates any standard SNMP Network management application,

such as Castle Rock SNMPc Network Manager or HP OpenView.

This chapter is intended for IT NMS professionals specializing in SNMP. It includes

concise specifications required for integrating a standard SNMP NMS with the Coral

CFM. See also Chapter 5, SNMP Installation and Configuration on page 45.

Functional Requirements

An object monitored in the CFM system is either a Coral unit or a CFM server. Each

monitored object is represented by a graphical object (icon).

Each graphical object presents the monitored object by a color code. The

recommended color coding is described in Setting up Alarm Color Coding for Icons,

page 59.

Each graphical object provides a link to a predefined URL. Click an icon results in

opening a browser with the specified URL. The following table describes the URL

format used in the CFM system.

Table 7 URL Format for CFM Objects Object Type URL Format

Coral site http://<CFM IP address>/cfm/<object name>.htmlReplace <CFM IP address> with the IP address of the (default or redundant) CFM server and <object name> with the URL name of the Coral site as defined in the CFM-SP (see Adding or Updating Coral Sites, page 39).

CFM server http://<CFM IP address>/cfm/show1.phpReplace <CFM IP address> with the IP address of the (default or redundant) CFM server.

tallation Manual SNMP Specifications for Integration with CFM 71

7

Coral objects are non-SNMP devices, therefore they are monitored through PING

commands.

CFM server objects use standard SNMP MIB-II and are monitored through MIB-II

polling.

Traps

Traps are only associated with Coral objects. The association of a trap with a

monitored object is performed via the IP address (agent address) of the object. This IP

address is indicated in the trap message.

Traps are sent every 2 minutes or upon receipt of a new alarm from a Coral site.

The trap message format follows the guidelines of RFC1157, Clause 4.1.6. The

message information is mapped as follows:

The following table specifies some of the mapping fields:

Table 8 Message Traps and Meanings

Version Community PDU type Enterprise Agent Address

Generic trap

Specific trap

Time Stamps

Variable - bindings

Name Function/Value

Version 0 (for SNMP Protocol Version 1)

Community “public)

PDU type TRAP

Agent Address Coral IP address (UGW IP address, MAP IP address, or the IP address of the serial-to-IP converter)

Generic trap Trap type: 0—coldStart 1—warmStart 2—linkDown 3—linkUp

Specific trap 0

72 SNMP Specifications for Integration with CFM Coral Fault Manager (CFM) Installation Manual

International HeadquartersTadiran Telecom Ltd.18 Hasivim Street P.O.Box 7607Petach Tikva 49170 IsraelTel. +972-3-9262000, Fax. +972-3-9262310

http://www.tadirantele.com

USA HeadquartersTadiran Telecom, Inc.4 Tri Harbor CourtPort Washington, NY 11050Tel. +1-516-632-7200, Fax. +1-516-632-7210

Cora lIns ta l l a t ion Manua lEd i t ion 3 M ay - 2009

TMFau l t Manager (CFM)

coral fault manager · 2015. 6. 29. · 2 about this manual coral fault manager (cfm) installation...

Documents