Module04 EMS Training

Module 4: Using the EMS
Jay Weitzen Airvana Performance Engineering
Infrastructure for All-IP Broadband Mobile Wireless Accelerating Access Anywhere
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
Confidential & Proprietary
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
Confidential & Proprietary 3
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
System Architecture
Product Structure
Nortel DO-EMS
Data Collection Architecture
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 to EMS Collected data stored as files on EMS Server for use by operators reporting and analysis application
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 Line Interface Group operations applied to one or more NEs at the same time Operator/user activity log
Fault Management
EMS Server processes traps, events and alarms and makes events and alarms available to web based clients. Traps are mapped to events and then correlated to alarms. Alarm severity propagation from component to node level Active alarm monitoring/auditing EMS Client is notified of new alarms or alarm status changes by the EMS Server. Java Fault Manager for near real-time alarm status
Licensing
EMS software - licensed per Sun Solaris server/machine Oracle 8i Enterprise Edition database licensed per named/non-concurrent user and/or processor Veritas software licensed per Sun Solaris server/machine
11
SNMP Trap to Alarm / Alert Mapping
12
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 LAN and EMS Server
Via HTTPS Via VPN tunnel
Multiple levels of user access as defined by administrator

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 process dynamically via EMS client Discovered nodes are:
Added to the database, including their configuration and alarm information
For performance reasons, auto-discovery is disabled as the default setting.

High Availability Architecture: 2.1 Release

Management LAN Primary Node
Dual Dedicated Heartbeat Polling
Standby Node
Netra 20 Server w/Quad Fast Ethernet UltraSCSI UltraSCSI
Netra 20 Server w/Quad Fast Ethernet
Approx. 5 minutes to fail-over = warm-standby Automatic - no user intervention Single IP address for EMS clients & NEs increases usability while minimizing bandwidth consumption
Sun StorEdge D1000 Disk Array 436GB (12 @ 36GB)
15
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
16
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 PCI adapters (one for each server, for high availability heartbeat private network) Replace Sun StorEdge MultiPack with 436GB Sun StorEdge D1000 Disk Array Replace Veritas Database Edition for Oracle with Veritas Database Edition for Oracle/HA
17
18
Using the EMS for Element Configuration EMS administrative functions Configuration functions Alarm details Software download
19
Starting / Stopping EMS Server

Stopping from Sun server Oracle and EMS are started immediately after a reboot If the EMS is stopped, starting on Sun server:
Run startnms.sh as emsadmin in from $EMS_HOME/WebNMS/bin directory Type Ctrl C in the same xterm that you start the server
Stopping from a client

User must have System Admin privilege to perform this operation. Click on the SystemAdmin option on the Tree Panel and select Shut Down Server
20
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
21
Login Screen
22
Menu and Panel Structure
23
System Administration Options
24
Viewing Log Files
25
EMS System Resource Information
26
Main Menu
27
Checking EMS Version Information
28
Adding a New Node
29
Add Trap Listener to a DOM
30
Add Trap Listener Screen
31
Deleting a Node
32
NE Configuration Synchronization
All configuration synchronization is one way:
NE to EMS It is not possible to load a saved configuration file from the 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
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
34
Download Configuration from NE (Manual Synch)
35
Network Topology Menu
36
Performance Menu
37
Network Database Networks Menu
38
Network Database Nodes Menu
39
Network Database DOMs Menu
40
DOM Configuration Menu
41
DOM Configuration Sub-Menu
42
Network Database RNC Menu
43
Device Panel View Indicates actual status of all vital components 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
RNC Device Panel View
45
Network Database Sectors Menu
46
Network Database Carrier Menu
47
Network Database SectorElement Menu
48
Network Database IS856Neighbor Info
49
Add Neighbor to a Sector Element
50
Add Sector Element Neighbor
51
Potential Sector Element Neighbor List
52
Network Database Cards Menu
53
Network Database Interface Menu
54
Network Database PDSN Menu
55
Network Database TrapListener Menu
56
Management Tools MIB Manager Menu
57
Management Tools Policy Manager
58
Policy Details
59
System Administration Menu
60
Logging Out
61
EMS Online Help
62
63
Fault Management Events Menu
64
Fault Management Alarms View
65
Alarm Detail View
66
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
67
Configuring E-mail Service (System Administration)
68
Define Alarm E-mail or Pager Notification
69
70
Configuring and Managing Data Collection MIB overview Data collection overview Interface utilization statistics Number of active sessions on RNC Limitations of collection statistics Live data view
71
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 and counters. There are public and private MIBs or a MIB may have both public and private sections. Current Internet standard MIB is MIB-II
72
MIB Browser
73
MIB - II
74
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.
75
Walking the MIB
76
SNMP Get
77
Configuring and Managing Data Collection MIB Overview Data Collection Overview Interface Utilization Statistics Number of Active Sessions on RNC Limitations of Collection Statistics Live Data View
78
Statistics Administration Screen
79
Viewing Data Collection Templates
80
Configuring Data Collection Template
81
Configuring Data Collection Template Data Collection Templates can contain elements from multiple MIBs. All elements within a Data Collection Template must be indexed by the same value.
82
Defining Data Collection Configuration
83
Defining Data Collection Configuration Make sure to select appropriate network elements in the configuration. Many Data Collection templates have elements 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 data collection to the element.
Defining Data Collection Configuration Data Collection Templates have version information. If a Template updates, it does not automatically propagate into Data Collection Configurations that are using the Template.
85
Sending Data Collection Configuration to NE
86
Showing the Running DC Tasks on NE

AIRVANA-07>show data-collection Max. Individual buffer size : 128 KB. High Backup Threshold Low Backup Threshold DC Listener IP Address DC Listener Port : 65536 KB. : 51200 KB. : 10.10.64.4 : 9009
Current status of Data Collection configurations present in this node: ConfigName Mark_Session_Collection Ethernet_Utilization Status active active
----------------------------------------------
87
Viewing Data Collection Files
88
Sample Data Collection File
89
90
Default Data Collection Template
91
Data Collection Configuration
92
Data Collection Files
93
94
Data Collection Template
95
Data Collection Configuration
96
Data Collection Configuration Summary
97
Data Collection Configuration Push
98
Show Data Collection from CLI

AIRVANA-07>show data-collection Max. Individual buffer size : 128 KB. High Backup Threshold : 65536 KB. Low Backup Threshold : 51200 KB. DC Listener IP Address : 10.12.0.90 DC Listener Port : 9009 Current status of Data Collection configurations present in this node: ConfigName Status ---------------------------------------------Interface_Utilization active RNC_Sessions_Counters active
99
Limitations Of Collection Statistics Stats Can be Intrusive to Operation of Network Element Process Not User Friendly Post-Processing of Text Files
100
Recommended Collection Statistics

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.9 release. These templates are configured to maximize system performance and operational visibility into system operation. Developed jointly between Airvana performance engineering and Nortel core CDMA engineering.
102
Live Data Views
103
Live Data View Types Multi-Instance One node, 1 OID, multiple instances
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) Multi-OID View Different OIDs (in a template), single node, single instance
Example Octets In and Octets Out of same interface of same node Use Data Collection Templates here
MIB OID Aliases Gives you the ability to attach simple alias names to MIB objects.
105
What are Live Data Views? Dynamic graphical representation of MIB gets 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
106
Live Data View Builder
107
108
Logging Subsystem
109
Logging Levels Levels 1-32 Default level of 3 for all components 6-32 are debug levels with increasing granularity Logging can be enabled per component
110
Configuring NE Logging On the EMS

Node->Node Menu->Show Cards->Card (Example BIOSC card)->Card Menu(Example BIOSC Menu)->Config LogFacilityMgr->Click on LogFacility
111
Configuring NE Logging CLI
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)#
112
Log File Management On NE
113
Log File Transfer Policy on EMS
114
Log File Transfer Policy on EMS (Contd)
115
Log File Cleanup Policy on EMS
116
Finding Log Files On the EMS
117
Finding Log Files On the NE

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.bin 1964 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
118
Searching the Log Files

AIRVANA-07>show logging file for abis 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 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
119
Transferring Log Files Binary FTP of log file from NE to EMS Log Files are converted from binary to ASCII on the EMS
120
Applicable Technical Bulletins (TSBs) Default logging levels Log file management Default DC Templates Log File parsing
121
122
Software Download Process

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) to activate the new image (causing a system re-boot). User can view outstanding software download tasks and abort tasks, if necessary. Specific documentation is available for each software upgrade. Read it before upgrading. Download process is limited to 10 RN/DOMs at a time
123
Software Download
124
Software Download Operation
125
Software Download Operation (Contd)
126
EMS Online Help
127
EMS HTML Online Help Features Index Full-text search Bookmarks or favorites Context-sensitivity support (screen-based help) Tabbed display with collapsible table of contents
128
End of Module Thank You
Accelerating Access Anywhere

Module04 EMS Training

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Module04 EMS Training

Caricato da

Copyright:

Formati disponibili

Module 4: Using the EMS

Jay Weitzen Airvana Performance Engineering

Infrastructure for All-IP Broadband Mobile Wireless Accelerating Access Anywhere

Confidential & Proprietary

Confidential & Proprietary

Confidential & Proprietary

Confidential & Proprietary

Data Collection Architecture

Confidential & Proprietary

Performance Management / Data Collection

Confidential & Proprietary

Confidential & Proprietary

Confidential & Proprietary

SNMP Trap to Alarm / Alert Mapping

Confidential & Proprietary

Multiple levels of user access as defined by administrator

For performance reasons, auto-discovery is disabled as the default setting.

High Availability Architecture: 2.1 Release

Netra 20 Server w/Quad Fast Ethernet UltraSCSI UltraSCSI

Netra 20 Server w/Quad Fast Ethernet

Sun StorEdge D1000 Disk Array 436GB (12 @ 36GB)

Confidential & Proprietary

Standalone EMS Server System Requirements

EMS web based client

Confidential & Proprietary

Redundant EMS Server System Requirements

Confidential & Proprietary

Confidential & Proprietary

Confidential & Proprietary

Starting / Stopping EMS Server

Stopping from a client

Confidential & Proprietary

EMS Server Directory Structure

Confidential & Proprietary

Confidential & Proprietary

Menu and Panel Structure

Confidential & Proprietary

System Administration Options

Confidential & Proprietary

Viewing Log Files

Confidential & Proprietary

EMS System Resource Information

Confidential & Proprietary

Confidential & Proprietary

Checking EMS Version Information

Confidential & Proprietary

Adding a New Node

Confidential & Proprietary

Add Trap Listener to a DOM

Confidential & Proprietary

Add Trap Listener Screen

Confidential & Proprietary

Confidential & Proprietary

Configuration Synchronization (Contd) If the NE is configured via the EMS:

If the NE is configured via the CLI:

Confidential & Proprietary

Download Configuration from NE (Manual Synch)

Confidential & Proprietary

Network Topology Menu

Confidential & Proprietary

Confidential & Proprietary

Network Database Networks Menu

Confidential & Proprietary