Fault & Performance Management

Contents

1
2 3 4

Introduction

IBM Tivoli Netcool

PRTG Network Monitor

Conclusion

Basic Components of Network Management

Basic Parts of Network Management

Network Management Dimensions

Management Function

Management Function: Whats in Your Toolbox

Fault Management Configuration Management Accounting Managment Performance Management

Security Management

Fault Management
Fault Management: The goal of fault management is to detect, log, notify users of, and (to the extent possible) automatically fix network problems to keep the network running effectively

Performance Management
Performance Management: The goal of performance management is to measure and make available various aspects of network performance so that internetwork performance can be maintained at an acceptable level

Contents

1
2 3 4

Introduction

IBM Tivoli Netcool

PRTG Network Monitor

Conclusion

Architecture Tivoli Network Manager

10

Architecture Tivoli Netcool/OMNIbus

11

ObjectServer
The ObjectServer is the in-memory database server at the core of Tivoli
Netcool/OMNIbus. Event information is forwarded to the ObjectServer from external programs such as probes and gateways. This information is stored and managed in database tables, and displayed in the Active Event List (AEL) in the Web GUI, or in the desktop event list. Deduplication

Automation

12

Probe

Probes connect to an event source, detect and acquire event data, and forward the data to the ObjectServer as alerts. Probes use the logic specified in a rules file to manipulate the event elements before converting them into fields of an alert in the ObjectServer alerts.status table.

Each probe is uniquely designed to acquire event data from a specific source. Types of Probes: Device, Log file, Database, API, CORBA, Miscellaneous

13

Gateway

Netcool/OMNIbus gateways enable you to exchange alerts between ObjectServers and complementary thirdparty applications, such as databases, helpdesk or Customer Relationship Management (CRM) systems.

14

Data Flow

15

Contents

1
2 3 4

Introduction

IBM Tivoli Netcool

PRTG Network Monitor

Conclusion

16

Key Features
What PRTG Can Be Used For: Monitor and alert for uptimes/downtimes or slow servers. Monitor and account bandwidth and network device usage. Monitor system usage (CPU loads, free memory, free disk space etc.). Classify network traffic by source/destination and content. Discover unusual, suspicious or malicious activity with devices or users. Measure QoS and VoIP parameters and control service level

agreements (SLA).
Discover and assess network devices. Monitor fail-safe using a failover cluster setup.

17

Architecture
Type System Part Part PRTG Core Server This is the central part of a PRTG installation and includes data storage, web server, report engine, a notification system, and more. Probe The part of PRTG on which the actual monitoring is performed. There are local probes, remote probes, and cluster probes available. All monitoring data is forwarded to the central core server. User Interface Ajax Web Interface The Ajax-based web interface is used for configuration of devices and sensors, as well as the review of monitoring results. Also system administration and user management are configured here. Enterprise Console A native Windows application (former Windows GUI) as alternative to the web interface to manage your monitoring. With the Enterprise Console, you can connect to different independent PRTG core server installations and review data at a glance! Smart Phone Apps Monitor your network on the go with PRTG and the smart phone apps for iOS and Android. System Administration Programs PRTG Server Administrator Used to configure basic core server settings, such as administrator login, web server IPs and port, probe connection settings, cluster mode, system language, and more. PRTG Probe Administrator Used to configure basic probe settings such as name of the probe, IP and server connection settings, and more.

18

Core server & Probe

The core server is the heart of your PRTG system and performs the following processes: Configuration management for object monitoring

Management and configuration of the connected probes

Cluster management Database for monitoring results Notification management including a mail server for email delivery Report generator and scheduler User account management Data purging (culling data that is older than 365 days, for example)

Web server and API server

19

Core server & Probe

On a probe, the sensors created on a device perform the actual monitoring. The probe receives its configuration from the core server, runs the monitoring processes and delivers monitoring results back to the core server. The PRTG core server inside the corporate LAN (bottom right) is able to

monitor services and servers in the entire Local Area Network (LAN).
Additional so-called Remote Probes can be created by the user in order to achieve monitoring of multiple locations, or for several other scenarios. They are using SSL-secured connections to the core and allow to securely monitor services and systems inside remote networks which are not openly accessible, or secured by firewalls.

20

Object Hierachy
- Probe - Group - Device - Sensor: Services (SMTP, FTP, HTTP,...) CPU load, RAM Netflow - Channel: Downtime, down bandwidth Percentage of used memory

21

Sensor Technologies
Monitoring via SNMP

Monitoring via WMI

Monitoring Bandwidth via Packet Sniffing Monitoring Bandwidth via Flows Bandwidth Monitoring Comparison Monitoring Quality of Service Monitoring Email Round Trip

22

Monitoring via SNMP

SNMP can be used to monitor bandwidth usage of routers and switches on a port-by-port basis, as well as device readings such as memory, CPU load, etc. The queried devices must support SNMP.

23

Monitoring Bandwidth via Packet Sniffing

SNMP can be used to monitor bandwidth usage of routers and switches on a port-by-port basis, as well as device readings such as memory, CPU load, etc. The queried devices must support SNMP.

24

Monitoring Quality of Service

For Quality of Service measurements, two sensors are available:
QoS (Quality of Service) Sensor Monitors VoIP relevant network parameters by testing network connection quality between two probes. QoS (Quality of Service) Round Trip Sensor Monitors VoIP relevant network parameters by testing network connection quality between two probes. Traffic is measured bidirectional.

Cisco IP SLA Sensor

Monitors VoIP relevant network parameters through IP SLA results from Cisco devices (via SNMP).

25

Contents

1
2 3 4

Introduction

IBM Tivoli Netcool

PRTG Network Monitor

Conclusion

26

Architecture

27

Fault Management
Fault management functionality includes the following: Network monitoring, including basic alarm management as well as more advanced alarm processing functions Basic Alarm Management Functions: collecting alarms, maintaining accurate & current lists of alarms, visualizing alarms and network state. Advance Alarm Management Functions: alarm forwarding function, another function allows network operators to acknowledge alarms, clearing of alarms, alarm & event filtering, alarm & event correlation. Fault diagnosis, root cause analysis, and troubleshooting Maintaining historical alarm logs Trouble ticketing Proactive fault management

28

Performance Management

Performance management functionality includes the following:

Performance metrics: link, load, QoS, .... Collecting Performance Data Monitoring and Tuning Network for Performance (KPIs)

29

Thank you

Q&A

30