module04 ems training

7/27/2019 Module04 EMS Training

1/129

Infrastructure for All-IP Broadband Mobile Wireless Accelerating Access Anywhere

Module 4: Using the EMS

Jay WeitzenAirvana Performance Engineering


2/129

Confidential & Proprietary 2

Module Contents

EMS overview and architecture Using the EMS for element configuration Configuring and managing data collection Configuring and managing logging Configuring and managing alarms Using the EMS for software upgrade


3/129


EMS Features

Intuitive, web-based for remote access User-configurable data collection Real-time alarm/event reporting Built using reliable and proven technology

AdventNet WebNMS framework Sun hardware

Oracle database Veritas high-availability software Above combination results in a robust, scalable system

Warm-standby HA solution automatic, no user intervention: 2.1 Release Feature Capability to easily develop NMS/OSS northbound

interfaces for integrating operators existing systems,thereby leveraging existing tools and processes


4/129


Module Contents

EMS overview and architecture Using the EMS for element configuration Configuring and managing alarms Configuring and managing data collection Configuring and managing logging Using the EMS for software upgrade


5/129


System Architecture


6/129


Product Structure

NortelDO-EMS


7/129


Data Collection Architecture


8/129


Performance Management / Data Collection

Reliable and efficient bulk statistics transfer Flexible user configurable data collection via

DC Template (what statistics to collect?) DC Configuration (how often and from which nodes?)

TCP/IP socket based data collection from NE toEMS

Collected data stored as files on EMS Server for

use by operators reporting and analysisapplication


9/129


Configuration Management

HTTP based configuration management Configuration data is stored in both NEs as well as

the EMS database. Manual configuration

Via GUI based clients or Command LineInterface

Group operations applied to one or more NEs at

the same time Operator/user activity log


10/129


Fault Management

EMS Server processes traps, events and alarmsand makes events and alarms available to web

based clients. Traps are mapped to events and then correlated to

alarms.

Alarm severity propagation from component tonode level Active alarm monitoring/auditing

EMS Client is notified of new alarms or alarmstatus changes by the EMS Server.

Java Fault Manager for near real-time alarm status


11/129


Licensing

EMS software - licensed per Sun Solarisserver/machine

Oracle 8i Enterprise Edition database licensed per named/non-concurrent user and/or processor

Veritas software licensed per Sun Solarisserver/machine


12/129


SNMP Trap to Alarm / Alert Mapping


13/129


Security Management

EMS Server is assumed to be located in a secure private LAN.

Server side user/password authentication Communication between clients and EMS Server within the LAN is via HTTP.

Communication between clients outside the LANand EMS Server Via HTTPS

Via VPN tunnel Multiple levels of user access as defined by

administrator


14/129


Auto-Discovery

User configurable auto-discovery policy via the seed.file

Typical configurable parameters include: IP address range(s) and subnet(s) Discovery interval

Supports enabling and disabling discovery processdynamically via EMS client Discovered nodes are:

Added to the database, including their configurationand alarm information

For performance reasons, auto-discovery is

disabled as the default setting.


15/129


High Availability Architecture: 2.1 Release

Sun StorEdge D1000 Disk Array436GB (12 @ 36GB)

Netra 20 Server w/Quad Fast Ethernet

Netra 20 Server w/Quad Fast Ethernet

Management LAN

Primary Node Standby Node

UltraSCSI UltraSCSI

Dual Dedicated Heartbeat Polling

Approx. 5 minutes to fail-over =warm-standby

Automatic - no user intervention Single IP address for EMS clients &NEs increases usability whileminimizing bandwidth consumption


16/129


Standalone EMS Server System Requirements

Sun Fire 280R Server or Netra 20 (2) 1.015 GHz UltraSPARC III processors 2 GB RAM 2 x 36 GB internal hard disk 10/100 Ethernet interface Two power supplies DVD/CD-ROM drive, graphics card, 21 monitor, keyboard, mouse Sun StorEdge MultiPack with 72.8GB external disk to mirror the system disk for

reliability

Sun StorEdge L7 Tape Autoloader, DLT8000, 280 GB (tape drive for backup) need to qualify

Software Solaris 8 operating system Oracle 8i Enterprise Edition v8.1.7 (separately orderable) Veritas Database Edition for Oracle Enterprise Edition, Solaris, v3.5 (separately

orderable)

EMS web based client Microsoft Internet Explorer 5.5 or higher

Netscape Navigator 4.7 or higher


17/129


Redundant EMS Server System Requirements

To the Standalone EMS Server System Requirements Add an additional Sun Fire 280R Server or Netra 20

Add two Sun Quad Fast Ethernet 10/100BaseT PCIadapters (one for each server, for high availabilityheartbeat private network)

Replace Sun StorEdge MultiPack with 436GB SunStorEdge D1000 Disk Array

Replace Veritas Database Edition for Oracle with VeritasDatabase Edition for Oracle/HA


18/129


Module Contents

EMS overview and architecture Using the EMS for element configuration Configuring and managing alarms Configuring and managing data collection Configuring and managing logging Using the EMS for software upgrade


19/129


Using the EMS for Element Configuration

EMS administrative functions Configuration functions Alarm details Software download


20/129


Starting / Stopping EMS Server

Oracle and EMS are startedimmediately after a reboot

If the EMS is stopped,starting on Sun server: Run startnms.sh as emsadmin

in from$EMS_HOME/WebNMS/bindirectory

Stopping from Sun server Type Ctrl C in the same

xterm that you start the

server Stopping from a client

User must have System

Admin privilege to performthis operation. Click on the SystemAdmin

option on the Tree Panel

and select Shut DownServer


21/129


EMS Server Directory Structure

EMS Home directory: /opt/ems Some important directories are found under the

this directory /opt/ems/WebNMS: bin/ consists of EMS server administrative shell scripts conf/ consists of all EMS server configuration files for

customization dcFiles/ consists of all data collection files logs/ consists of all EMS server log files mibs/ consists of all supported SNMP MIBs ne_file/ consists of all NEs logs and debug files ne_software/ consists of all NE software images


22/129


Login Screen


23/129


Menu and Panel Structure


24/129


System Administration Options


25/129


Viewing Log Files


26/129


EMS System Resource Information


27/129


Main Menu


28/129


Checking EMS Version Information


29/129


Adding a New Node


30/129


Add Trap Listener to a DOM


31/129


Add Trap Listener Screen


32/129


Deleting a Node


33/129


NE Configuration Synchronization

All configuration synchronization is one way: NE to EMS

It is not possible to load a saved configuration file fromthe EMS

After an NE is added to EMS, a configuration

synchronization occurs The EMS periodically polls the NE for system

uptime If the system uptime is not the expected time, a

configuration synchronization will occur


34/129


Configuration Synchronization (Contd)

If the NE is configured via the EMS: Changes are sent to the NE

The configuration is written/saved If the NE is configured via the CLI:

Trap is sent to EMS EMS is updated to reflect new configuration The configuration is NOT written/saved


35/129


Download Configuration from NE (Manual Synch)


36/129


Network Topology Menu


37/129


Performance Menu


38/129


Network Database Networks Menu


39/129


Network Database Nodes Menu


40/129


Network Database DOMs Menu


41/129


DOM Configuration Menu


42/129


DOM Configuration Sub-Menu


43/129


Network Database RNC Menu


44/129


Device Panel View

Indicates actual status of all vitalcomponents and card types in each slot for

DOM and RNC Object sensitive menu actions Device panel status is updated

asynchronously via Java RMI Status change can be triggered by SNMP

traps or detected by periodic status polling

REQUIRES Java Client Plugin


45/129


RNC Device Panel View


46/129


Network Database Sectors Menu


47/129


Network Database Carrier Menu


48/129


Network Database SectorElement Menu


49/129


Network Database IS856Neighbor Info


50/129


Add Neighbor to a Sector Element


51/129


Add Sector Element Neighbor


52/129


Potential Sector Element Neighbor List


53/129


Network Database Cards Menu


54/129


Network Database Interface Menu


55/129


Network Database PDSN Menu


56/129


Network Database TrapListener Menu


57/129


Management Tools MIB Manager Menu


58/129


Management Tools Policy Manager


59/129


Policy Details


60/129


System Administration Menu


61/129


Logging Out

EMS O li H l


62/129


EMS Online Help

M d l C


63/129


Module Contents

EMS overview and architecture Using the EMS for element configuration Configuring and managing alarms Configuring and managing data collection

Configuring and managing logging Using the EMS for software upgrade

F l M E M


64/129


Fault Management Events Menu

F l M Al Vi


65/129


Fault Management Alarms View

Al D t il Vi


66/129


Alarm Detail View

Al D t il Vi (C td)


67/129


Alarm Detail View (Contd)

Events show corresponding events Annotate enter user comments

Pick Up/Unpick take ownership of an alarm Annotation show all annotations History show alarm history Merge show all annotations and alarm history Clear reset alarm state/severity to clear Delete remove alarm from database

C fi i E il S i (S t Ad i i t ti )


68/129


Configuring E-mail Service (System Administration)

D fi Al E il P g N tifi ti


69/129


Define Alarm E-mail or Pager Notification

Module Contents


70/129


Module Contents

EMS overview and architecture Using the EMS for element configuration

Configuring and managing alarms Configuring and managing data collection



71/129

MIB


72/129


MIB

Management Information Base Almost all networking gear is based on MIBs.

Routers, Switches etc. Registry of a Windows machine.

Supplies a tree-like schema for objects andcounters.

There are public and private MIBs or a

MIB may have both public and private sections. Current Internet standard MIB is MIB-II

MIB Browser


73/129


MIB Browser

MIB II


74/129


MIB - II

SNMP


75/129


SNMP

Simple Network Management Protocol SNMPv2 is common, SNMPv3 is latest

Used to query and write to MIBs SNMP set: sets a value such as turning an

Ethernet interface up or down. SNMP get: queries the MIB for the current

value of an object.


76/129

SNMP Get


77/129


SNMP Get

Configuring and Managing Data Collection


78/129



MIB Overview Data Collection Overview

Interface Utilization Statistics Number of Active Sessions on RNC

Limitations of Collection Statistics Live Data View

Statistics Administration Screen


79/129


Statistics Administration Screen

Viewing Data Collection Templates


80/129


Viewing Data Collection Templates

Configuring Data Collection Template


81/129





82/129



Data Collection Templates can containelements from multiple MIBs.

All elements within a Data CollectionTemplate must be indexed by the same

value.

Defining Data Collection Configuration


83/129





84/129



Make sure to select appropriate network elements in the configuration.

Many Data Collection templates haveelements that are specific to RNCs or

DOMs.This screen will not produce a warning if

the wrong element is selected. The error will be seen when trying to the datacollection to the element.



85/129



Data Collection Templates have versioninformation.

If a Template updates, it does notautomatically propagate into Data

Collection Configurations that are using theTemplate.

Sending Data Collection Configuration to NE


86/129


Sending Data Collection Configuration to NE

Showing the Running DC Tasks on NE


87/129


Showing the Running DC Tasks on NE

AIRVANA-07>show data-collectionMax. Individual buffer size : 128 KB.

High Backup Threshold : 65536 KB.

Low Backup Threshold : 51200 KB.

DC Listener IP Address : 10.10.64.4

DC Listener Port : 9009

Current status of Data Collection configurations present in this node:

ConfigName Status

----------------------------------------------

Mark_Session_Collection active

Ethernet_Utilization active

Viewing Data Collection Files


88/129


Viewing Data Collection Files

Sample Data Collection File


89/129


Sample Data Collection File



90/129


g g g g




Default Data Collection Template


91/129


p

Data Collection Configuration


92/129


g

Data Collection Files


93/129




94/129


g g g g




Data Collection Template


95/129


p

Data Collection Configuration


96/129


g

Data Collection Configuration Summary


97/129


g y

Data Collection Configuration Push


98/129


g

Show Data Collection from CLI


99/129


AIRVANA-07> show data-collectionMax. Individual buffer size : 128 KB.High Backup Threshold : 65536 KB.Low Backup Threshold : 51200 KB.DC Listener IP Address : 10.12.0.90DC Listener Port : 9009

Current status of Data Collection configurations present in this node:

ConfigName Status----------------------------------------------Interface_Utilization activeRNC_Sessions_Counters active

Limitations Of Collection Statistics


100/129


Stats Can be Intrusive to Operation of Network Element

Process Not User Friendly Post-Processing of Text Files

Recommended Collection Statistics


101/129


Nortel NTP specifies 22 data collection templates. These 22 templates are the default for the 2.1

release. They are available in a patch for the 2.0.4.9release.

These templates are configured to maximizesystem performance and operational visibility intosystem operation.

Developed jointly between Airvana performanceengineering and Nortel core CDMA engineering.


102/129

Live Data Views


103/129


Live Data View Types


104/129


Multi-Instance One node, 1 OID, multipleinstances

Example is Octets in on several interfaces of same node.

Multi-Node Single OID, single instance,multiple nodes Example is Octets in on same interface of

several different RBSs. Make sure the instance IDs are the same in

each node.

Live data View Types (Contd)


105/129


Multi-OID View Different OIDs (in atemplate), single node, single instance

Example Octets In and Octets Out of sameinterface of same node

Use Data Collection Templates here

MIB OID Aliases Gives you the ability toattach simple alias names to MIB objects.

What are Live Data Views?


106/129


Dynamic graphical representation of MIBgets

Used only for objects that are numeric for example, interface octets in is numeric

interface description not numeric Displays object values vs. time Limit of 9 OIDs on any graph

Live Data View Builder


107/129



108/129

Logging Subsystem


109/129



110/129

Configuring NE Logging On the EMS


111/129


Node->Node Menu->Show Cards->Card (Example BIOSC card)->Card Menu(Example BIOSC Menu)->ConfigLogFacilityMgr->Click on LogFacility

Configuring NE Logging CLI


112/129


AIRVANA-07>en

AIRVANA-07#config

Enter configuration commands, one per line. End with CTRL-Z.

AIRVANA-07(config)#logging trap severity 12 pcf-sig

AIRVANA-07(config)#logging buffer trap severity 12 pcf-sig

AIRVANA-07(config)#logging monitor trap severity 12 pcf-sig

AIRVANA-07(config)#logging start pcf-sig

pcf-sig logging enabled

AIRVANA-07(config)#

Log File Management On NE


113/129


Log File Transfer Policy on EMS


114/129


Log File Transfer Policy on EMS (Contd)


115/129



116/129

Finding Log Files On the EMS


117/129


Finding Log Files On the NE


118/129


AIRVANA-07#shell

AIRVANA-07(shell)(disk0:/)#cd logs

AIRVANA-07(shell)(disk0:logs)#ls

size date time name

---------- ------ ----- ---------------

32768 Apr 25 05:14 ./

32768 Apr 25 13:10 ../

2398 Apr 10 18:31 swdnllog.txt

2032 Apr 10 18:32 rnc041003183140.bin

8108 Apr 23 17:19 rnc041003184048.bin1964 Apr 23 17:29 rnc042303212226.bin

682 Apr 23 17:40 rnc042303213738.bin

5768 Apr 23 18:21 rnc042303214127.bin

28 Apr 23 18:21 rnc042303182159.bin

2254 Apr 23 18:39 rnc042303222329.bin

278 Apr 23 21:29 rnc042303212922.bin

Free MBytes 38089

Searching the Log Files


119/129


AIRVANA-07>show logging file for abis04-25-03 14:07:34.800 S=03 C=010301 F=0032 ID=0016 ABIS:: SendHello: peer 10.12.0.248 timed out

04-25-03 14:07:34.800 S=03 C=010301 F=0032 ID=0011 ABIS:: Close connection to 10.12.0.248, fd 53

AIRVANA-07>show logging file match SendHello

04-25-03 14:07:34.800 S=03 C=010301 F=0032 ID=0016 ABIS:: SendHello: peer 10.12.0.248 timed out

AIRVANA-07>show logging file time from 04-25-03:14:05:00 to 04-25-03:14:08:00

04-25-03 14:07:34.800 S=03 C=010301 F=0032 ID=0016 ABIS:: SendHello: peer 10.12.

0.248 timed out

04-25-03 14:07:34.800 S=03 C=010301 F=0032 ID=0011 ABIS:: Close connection to 10

.12.0.248, fd 53

Transferring Log Files


120/129


Binary FTP of log file from NE to EMS Log Files are converted from binary to

ASCII on the EMS

Applicable Technical Bulletins (TSBs)


121/129


Default logging levels Log file management

Default DC Templates Log File parsing

Module Contents


122/129


EMS overview and architecture Using the EMS for element configuration

Configuring and managing alarms Configuring and managing data collection


Software Download Process


123/129


New image FTPd to selected NE(s) Either immediately or at a scheduled time, a

command is sent from the EMS to the NE(s) toactivate the new image (causing a system re-boot).

User can view outstanding software downloadtasks and abort tasks, if necessary.

Specific documentation is available for eachsoftware upgrade. Read it before upgrading.

Download process is limited to 10 RN/DOMs at atime

Software Download


124/129



125/129


126/129

EMS Online Help


127/129


EMS HTML Online Help Features


128/129


Index Full-text search

Bookmarks or favorites Context-sensitivity support (screen-based

help) Tabbed display with collapsible table of

contents


129/129

End of ModuleThank You

Accelerating Access Anywhere

module04 ems training

Documents