04. Protokol Dan Aplikasi Network Management (Rev)

8/8/2019 04. Protokol Dan Aplikasi Network Management (Rev)

http://slidepdf.com/reader/full/04-protokol-dan-aplikasi-network-management-rev 1/56

Manajemen Penyelenggaraan Jaringan

Modul-04

Network ManagementProtocols and Application



Simple Network Management Protocol

(SNMP)



What is SNMP?

Simple Network Management Protocol (SNMP) is awidely used protocol designed to facilitate themanagement of network devices from a centrallocation.

SNMP designed originally for the management of devices such as routers and switches, its usage hasgrown rapidly to encompass the monitoring of nearlyany electronic device one can think of.

SNMP is now used to monitor and manage televisionbroadcast studios, automated fare collection systems,airborne military platforms, energy distributionsystems, emergency radio networks, and much more

Kanda Rachmat

Oktober 2010

Manajemen Penyelenggaraan Jaringan Semester Ganjil 2010-2011

3



Simple Network ManagementProtocol

(SNMP)

Kanda Rachmat

Oktober 20104Manajemen Penyelenggaraan Jaringan Semester Ganjil 2010-

2011

A framework for managing devices in anInternet using TCP/IP.

Provides a set of fundamental operations for

monitoring and maintaining an Internet.An application-level protocol allows it to

monitor devices made by differentmanufacturers installed on different

physical networks.



SNMP Manager/AgentModel

SNMP bekerja berdasarkan manager/agent model yang terdiri darimanager , agent , database yang menyimpan informasimanajemen, managed objects, dan network protocol.

Manager menyediakan interface antara manusia (networkmanager) dengan management system.

Agent menyediakan interface antara manager dengan perangkatyang di-managed .

Manager dan agent menggunakan sebuah Management Information Base (MIB) dengan perintah-perintah yang sederhanauntuk pertukaran informasi.

MIB berisi variabel-variabel individual dari dari setiap komponenperangkat/sistem yang disusun dengan tree structure.

Kanda Rachmat

Oktober 2010


5



Kanda Rachmat

Oktober 2010


6

SNMP Manager/AgentModel

Management

Database

Management

Database

ManagedObject

Management System Managed Element

Network Protocol

Manager Agent



Structure of SNMP-basedManagement Services

Kanda Rachmat

Oktober 2010


7

NETWORK MANAGEMENT

STATION

Agent A

MI

B

Agent B

MIB

Agent C

MIB

Agent D

MIB

Agent E

MI

B

Database SQL

Display Station

SNMP

SNMPSNMP

SNMP

SNMPServer

Switch

Sub-agent

Wiring

Hub Router

Mux

SQL (Structured Query Language)



SNMP Basic Ideas

A manager checks an agent by requestinginformation that reflects the behavior of the agent.

A manager forces an agent to perform atask by resetting values in the agentdatabase.

An agent contributes to the managementprocess by warning the manager of anunusual situation.

Kanda Rachmat


2011



Some Typical Uses of SNMP

Monitoring device performance

Detecting device faults, or recovery fromfaults

Collecting long term performance data

Remote configuration of devices

Remote device control

Kanda Rachmat

Oktober 2010


9



SNMP Architecture

Manager

Managed device

Agent

Management Information Base(MIB)

Kanda Rachmat

Oktober 2010


10



Manager

A manager or management system is a separateentity that is responsible to communicate withthe SNMP agent implemented network devices.

This is typically a computer that is used to run

one or more network management systemsManager’s key functions:

o Queries agents

o Gets responses from agents

o

Sets variables in agentso Acknowledges asynchronous events from agents

Kanda Rachmat

Oktober 2010


11



Managed Device

A managed device or the network elementis a part of the network that requires someform of monitoring and management e.g.

routers, switches, servers, workstations,printers, UPSs, etc..

Kanda Rachmat

Oktober 2010


12



Agent The agent is a program that is packaged within the network

element.

Enabling the agent allows it to collect the managementinformation database from the device locally and makes itavailable to the SNMP manager, when it is queried for.

These agents could be standard (e.g. Net-SNMP) or specific toa vendor (e.g. HP insight agent)

SNMP agent’s key functions:o Collects management information about its local environment

o Stores and retrieves management information as defined in the MIB.

o Signals an event to the manager.

o Acts as a gateway for some non–SNMP manageable network node

Kanda Rachmat

Oktober 2010


13



Management InformationBase (MIB)

Kanda Rachmat

Oktober 2010


14

Every SNMP agent maintains an information database describing themanaged device parameters. The SNMP manager uses this databaseto request the agent for specific information and further translatesthe information as needed for the Network Management System(NMS). This commonly shared database between the Agent and theManager is called Management Information Base (MIB).

Typically these MIB contains standard set of statistical and controlvalues defined for hardware nodes on a network. SNMP also allowsthe extension of these standard values with values specific to aparticular agent through the use of private MIBs.

In short, MIB files are the set of questions that a SNMP Manager canask the agent. Agent collects these data locally and stores it, as

defined in the MIB. So, the SNMP Manager should be aware of thesestandard and private questions for every type of agent



Object Identifier (OID) Management Information Base (MIB) is a collection of Information for

managing network element. The MIBs comprises of managed objectsidentified by the name Object Identifier (Object ID or OID). EachIdentifier is unique and denotes specific characteristics of a manageddevice. When queried for, the return value of each identifier could bedifferent e.g. Text, Number, Counter, etc...

There are two types of Managed Object or Object ID: Scalar and

Tabular.Scalar:

o Scalar Object define a single object instance

o E.g.: Device’s vendor name, the result can be only one.

Tabular:

o Tabular object defines multiple related object instance that are groupedtogether in MIB tables

o E.g.: CPU utilization of a Quad Processor, this would give me a result foreach CPU separately, means there will be 4 results for that particularObject ID.

Kanda Rachmat

Oktober 2010


15



Structure of ManagementInformation (SMI)

Structure and Identification of ManagementInformation.

The SMI defines the rules for how managed objectsare described and how management protocols may

access these objects.

Functions:o To name objects

o To define the type of data to be stored in an object

o To show how to encode data for transmission over thenetwork

SMI requires each managed object (router,variables in a router, etc) has a unique name

Kanda Rachmat


2011



Naming

Integer dot representation

Name dot notation

Example:

iso.org.dod.internet.mgmt.mib-21.3.6.1.2.1

All objects managed by SNMP are given anobject identifier. The object identifier

always start with 1.3.6.1.2.1

Kanda Rachmat


2011



Kanda Rachmat

Oktober 2010

Manajemen Penyelenggaraan Jaringan Semester Ganjil 2010-

201118



The first group defines the node administratoro (1) for ISO

o (2) for CCITTo (3) for the joint ISO-CCITT

The second group for the ISO node administratordefines (3) for use by other organization.

The third group defines (6) for the use of the U.S.

Department of Defense (DoD). In the fourth group the DOD has not indicated how itwill manage its group, so the Internet communityassumed (1) for its own.

The fifth group was approved to be:o (1) for the use of OSI directory in the Interneto (2) for objects identification for management purposeso (3) for objects identification for experimental purposeso (4) for objects identification for private use

Kanda Rachmat

Oktober 201019


2011



Approach to obtaininformation

There are two approaches for themanagement system to obtaininformation from SNMPo Trap

o Polling

Kanda Rachmat

Oktober 201020


2011





SNMP Polling

The network management system periodicallyqueries the network devices for information.

The advantage is network the managementsystem is in control and knows the “big picture”.

The disadvantage is the amount of delay fromwhen the event occurs to when it’s noticed. Short interval, network bandwidth is wasted

Long interval, response to event is too slow

Kanda Rachmat

Oktober 201022


2011



SNMP Trap/Polling

When an event occurs, the network devicegenerates a simple trap.

The management system then polls the networkdevice to get the necessary information.

The management system also does low frequencypolling as a backup to the trap.

Kanda Rachmat

Oktober 201023


2011



SNMP Operation

Managers can be viewed as Clients; andAgents, as Servers. The operations betweenManagers and Agents are quite simple:o “get” commands are sent by a Manager to an Agent to

request data values defined by a MIB. The Agent will respond

with the requested values. Closely related requests are“getnext” and “getbulk”.

o A Manager can also send “set” commands to an Agent. If theMIB defines a data object as read-write, then the Agent willaccept the data value sent with the “set” command andprocess it appropriately (store it or execute appropriate

action).o Agents will send unsolicited “traps” (alarms) to Managers to

alert them to important events.

Kanda Rachmat

Oktober 2010


201124



Types of SNMP Packets GetRequest

o

Retrieves the value of a variable or a set of variables GetNextRequest

o Used to retrieve values of entries in a table

GetBulkRequesto Retrieves a large amount of datao Used instead of multiple GetRequest and GetNextRequest.

SetRequesto Set (store) a value in a variable

Responseo Response to GetRequest or GetNextRequest; contains values or variables

requested.

Trapo Sent from agent to manager to report an event.

InformRequesto Sent from one manager to another remote manager to get a value of some

value from agents under control of the remote manager.

Reporto Designed to report some type of errors between managers (not currently

used)

Kanda Rachmat

Oktober 201025


2011



Types of MIB Modules

Standard: These are the standard MIBs currentlydesigned to capture the core aspects of theparticular technology.

Experimental: Temporary and if achievesstandardization then it is placed in the standardmodule.

Enterprise-specific: Vendor specific MIBs thatprovide additional management capabilities for

those features that require it.

Kanda Rachmat

Oktober 201026


2011



Strengths of SNMP

Widespread popularity

Many standard MIBs available

Agents have low impact on monitoredsystem resources

Well suited to monitoring

Many products available

Kanda Rachmat

Oktober 2010


201127



Weaknesses of SNMP

Not as comprehensive as some other protocols

Not bandwidth efficient

Complicated message encoding rules

Security has been on on-going concern. SNMPv3was developed in response to this issue.

UDP, or other connectionless, protocol is used,which creates issues regarding verification of operations: Trap-Send verification (did it reallyreach the Manager?); Verification (success) of any“set” operation to an Agent. However, cleverlydesigned MIBs and Manager logic can overcomethese problems

Kanda Rachmat

Oktober 2010


201128



TelecommunicationsManagement Network

(TMN)



What is TMN? TMN is an acronym for Telecommunications Management

Network.

TMN standards efforts generally refer to the functionalarchitecture model and interface specifications createdand supported by the International TelecommunictionsUnion - Telecommunications Divsion (ITU- T) and other

national and international standards organizations

The term “TMN” refers to a collection of systems thatsupport the management needs of network and serviceproviders for planning, provisioning, installing, maintaining,operating, and administering telecommunicationsnetworks and services.

Kanda Rachmat

Oktober 2010


201130



TMN and TelecommunicationsNetworks

Kanda Rachmat

Oktober 2010


201131

Data CommunicationNetwork

NetworkElement

NetworkElement

NetworkElement

NetworkElement

Operations

System

Operations

System

Operations

System

TMN TMN

Telecommunications Network

Telecommunication Service

OperatorWorkstati

on



Basic Concept

The basic concept behind a TMN is to provide anorganized architecture to enable various types of OSSsand/or telecommunications equipment to work togetherfor the exchange of management information.

In defining this concept, TMN standards bodies recognize

that many network and service providers have largeinfrastructures of existing OSSs, networks, andequipment already in place which must beaccommodated within the architecture.

The TMN functional architecture has been designed

intentionally to accommodate a broad range of operations solutions.

Kanda Rachmat

Oktober 2010


201132



OS and OSS

An Operating System (OS) is software, consistingof programs and data, that runs on computersand manages the computer hardware andprovides common services for efficient execution

of various application software The integrated entity of management software,

operating system and hardware is defined asOperations Support System from the perspective

of a telecommunications service provider.

Kanda Rachmat

Oktober 2010


201133



TMN Functional AreasPrinsip TMN adalah mengelompokkan fungsi manajemen ke dalam lima

areaConfiguration Management

Pengontrolan/pengendalian, identifikasi dan pengumpulan data dari, danmemberikan data kepada network elements

Fault Management

Mendeteksi, mengisolasi, dan melakukan perbaikan atas ketidak normalan

operasi jaringan telekomunikasiPerformance Management

Mengevaluasi dan melaporkan perilaku perangkat sistem telekomunikasi danefektivitas network atau network elements

Accounting Management

Pengukuran penggunaan layanan jaringan dan menentukan besarnya biaya

penggunaan tersebut.Security Management

Memfasilitasi pencegahan dan pendeteksian penggunaan ilegal terhadapsumberdaya dan layanan jaringan, serta langkah-langkah preventive dancorrective terhadap upaya-upaya security violation

Kanda Rachmat

Oktober 2010


201134



TMN Functional Layers

TMN membedakan fungsionalitasmanajemen kedalam tingkatan-tingkatan, dari yang terendah berupamanajemen network element, sampaiyang tertinggi berupa manajemen bisniskorporasi

Tingkatan tersebut biasanyadirepresentasikan dalam bentuk

piramida yang terdiri dari:o Business Management Layer (BML)

o Service Management Layer (SML)

o Network Management Layer (NML)

o Element Management Layer (EML)

o Network Element (NE)

Kanda Rachmat

Oktober 2010


201135

Business

Management

Service

Management

Network

Management

Element

Management

Network

Elements



Kanda Rachmat

Oktober 2010


201136

Business ManagementLayer (BML)

BML has responsibility for the total enterprise

BML has the following principal roles:

o Supporting the decision-making process for the optimalinvestment and use of new telecommunications resources

o Supporting the management of OA&M (Operations,Administration and Maintenance) related budget

o Supporting the supply and demand of OA&M relatedmanpower

o Maintaining aggregate data about the total enterprise

Service Management Layer



Kanda Rachmat

Oktober 2010

Manajemen Penyelenggaraan

Jaringan Semester Ganjil 2010-2011

37

Service Management Layer(SML)

Service management is concerned with, and responsible for, the

contractual aspects of services that are being provided to customersor available to potential new customers.

Some of the main functions of this layer are service order handling,complaint handling and invoicing

The service management layer has the following principal roles:o Interfacing with customers and other administrators

o Interaction with service providers

o maintaining statistical data (e.g. QOS)

o interaction between services

o Interaction with BML and NML

SML supported by service level agreements, performance logs, alarm

logs, resource usage distribution, workforce management, andreporting tools

SML is responsible for all negotiations and resulting contractualagreements between a (potential) customer and the service(s)offered to this customer

Network Management



Network ManagementLayer (NML)

Kanda Rachmat

Oktober 2010



38

The network management layer has theresponsibility for the management of a network assupported by the element management layer

The network management layer has the followingprincipal roles:o The control and coordination of the network view of all

network elements within its scope or domain

o The provision, cessation or modification of networkcapabilities for the support of service to customers

o

The maintenance of network capabilitieso Maintaining statistical, log and other data about the

network and interact with the service manager layer onperformance, usage, availability, etc.

l



Element ManagementLayer (EML)

The element management layer manages eachnetwork element on an individual or group basis andsupports an abstraction of the functions provided bythe network management layer

The element management layer has the followingprincipal roles:o Control and coordination of a subset of network elements on

an individual NEF basis

o Control and coordination of a subset of network elements on

collective basiso Maintaining statistical, log and other data about elements

within its scope of control

Kanda Rachmat

Oktober 2010



39



Common Management Information Protocol (CMIP), an OSI protocolused with the Common Management Information Services (CMIS),supports information exchange between network managementapplications and management agents.

CMIS defines a system of network management information services.CMIP supplies an interface that provides functions which maybe used

to support both ISO and user-defined management protocols CMIP uses an ISO reliable connection-oriented transport mechanism

and has built in security that supports access control, authorizationand security logs. The management information is exchangedbetween the network management application and managementagents thru managed objects. Managed objects are a characteristic of

a managed device that can be monitored, modified or controlled andcan be used to perform tasks

Kanda Rachmat

Oktober 2010



40

TMN Protocol – CMIP



Network Management Basedon the CMIP/CMIS

Kanda Rachmat

Oktober 2010



41



Common Management InformationService Element (CMISE)

Access to managed information in the managedobjects is provided by CMISE that uses CMIP toissue requests for management services.

The management services provided by

CMIP/CMISE can be organized into two distinctgroups:o management operation services, initiated by a

manager to request that an agent provide certain

services or informationo notification services, used by the management

agents to inform the managers that some event or set of events have occurred.

Kanda Rachmat

Oktober 2010



42



Definition of Service Elements

Kanda Rachmat

Oktober 2010



43

Management operation serviceso M-CREATE - Create an instance of a managed object

o M-DELETE - Delete an instance of a managed object

o M-GET - Request managed object attributes (for one object or aset of objects)

o M-CANCEL-GET - Cancel an outstanding GET request

o M-SET - Set managed object attributes

o M-ACTION - Request an action to be performed on a managedobject

Management notification serviceso M-EVENT-REPORT - Send events occurring on managed

objects

Ad t f CMIP



Advantages of CMIP overSNMP

CMIP variables not only relay information, butalso can be used to perform tasks. This isimpossible under SNMP.

CMIP is a safer system as it has built in security

that supports authorization, access control, andsecurity logs.

CMIP provides powerful capabilities that allowmanagement applications to accomplish more

with a single request.CMIP provides better reporting of unusual

network conditions

Kanda Rachmat

Oktober 2010



44



Integrated Network

Management

Kanda Rachmat

Oktober 2010



45



Introduction

Managing a network involves a great variety of functionso Monitoring devices in the network

o Service provisioning

o Diagnosing networking problems

o

Planning for optimum network performanceo Detecting security breaches

o Assessing the impact of planned network maintenance onexisting services and customers

o Etc.

This means that all management functionality needto be provided in one holistic solution, as opposedto providing the functionality in multiple, separateparts that essentially form separate islands.

Kanda Rachmat

Oktober 2010



46



Benefits of IntegratedManagement

Kanda Rachmat

Oktober 2010



47

Management tasks do not rely on manual procedures and leavelittle to chance

Integrated management systems reduce the need for trainingand increase the pool of available personnel that can carry outoperational tasks

Integrated management infrastructure facilitates managementof the management itself

Integrated management infrastructure reduces or eliminates theneed to keep the same data redundantly in multiple locations

Integrated management infrastructure helps reduce themanagement load on the managed network

Integrated management infrastructure makes it easier to havemanagement information available whenever and wherever it isneeded



Non-integrated Management

Sept 2010



48

Database

Planning

DatabaseData

baseDatabase

EMS

DatabaseData

baseDatabase

Service Provisioning

DatabaseData

baseDatabase

CRM

Database

Customer Inventory

Database

Service Inventory

Database

Equipment Inventory



Integrated Management

Sept 2010



49

DatabaseIntegrated Management

Different Perspectives on



Different Perspectives onManagement Integration

Needs The Equipment Vendor

Perspective

The Enterprise Perspective The Service Provider Perspective

Kanda Rachmat

Oktober 2010



50

Th E i t V d



The Equipment VendorPerspective

Kanda Rachmat

Oktober 2010



51

Equipment

Provisioning

DeviceMonitori

ng

Backup,Restore

Devices – Vendor A

Integration

Scope



The Enterprise Perspective

The scope of integrated management becomeslarger in the case of a small to medium-sizeenterprise that needs to manage a network thatincludes a wide range of different types of

devices from different vendors. In such environments, typically a variety of

element management systems (EMSs) aredeployed, each addressing the management

needs for equipment of different vendors andeach used independently of one another

Kanda Rachmat

Oktober 2010



52



The Enterprise Perspective

Kanda Rachmat

Oktober 2010



53

Equipment

Provisioning

DeviceMonitori

ng

Backup,Restore

…..

Devices – Vendor A Equipment

Provisioning

DeviceMonitori

ng

Backup,Restore

…..

Devices – Vendor B

Network-levelAdministration

ElementManagement

…....Network

MonitoringEnd-to-End

Provisioning

IntegrationScope

Th S i P id



The Service ProviderPerspective

Integrated management for service providers includesservice management and business managementfunctionality.

This means that the scope of management integration isno longer just “horizontal”. Instead, the need forintegration becomes “vertical” as well.

Horizontal integration:o The same management functionality for increasing numbers of

managed devices and device types to be integrated

Vertical integration:o Integration of entirely categories and layers of management

functions

Kanda Rachmat

Oktober 2010



54

The Service Provider



The Service ProviderPerspective

Kanda Rachmat

Oktober 2010



55

Equipment

Provisioning

DeviceMonitori

ng

Backup,Restore

…..

Devices – Vendor A

IntegrationScope

Equipment

Provisioning

DeviceMonitori

ng

Backup,Restore

…..

Devices – Vendor B

Network-levelAdministration

Any Vendor

ElementManagementAny Vendor

…....Network

MonitoringAny Vendor

End-to-EndProvisioning

Service LevelMonitoring

…....

BillingCompanyInventory

Management…....

CustomerManagement

Service-OrderManagement

ServicesProvisioning –

Service A

ServicesProvisioning –

Service B

Vertica

l

Integ

ration

R f



References “Network Management Standard ”, Aiko Prass , University of Tweente, The

Netherlands (http://www.simpleweb.org)

“Introduction to SNMP”, Aiko Prass , University of Tweente, The Netherlands (http://www.simpleweb.org)

“Network Management Lecture”, Prof. S. Gosh, Dept. of Computer Science &Engineering, Indian Institute of Technology Kharagpur ((http://www.youtube.com

“SNMP Tutorial: An Introduction to SNMP “ (http://www.dpstele.com/layers/l2/snmp_tutorials.php)

“SNMP Tutorial” (http://www.manageengine.com/network-monitoring/what-is-snmp.html

“Simple Network Management Protocol (SNMP)“ (http://www.eogogics.com/talkgogics/tutorials/SNMP)

“ITU-T Recommendation M.3010”

“CMIP & CMIS” (http://www.javvin.com/protocolCMIP.html )

“Communication Networks Management ”, Second Edition – Kornel Terplan

“Telecom Operations Management Solutions With NetExpert TM “ – Kornel Terplan

“Network Management Fundamentals”, Alexander Clemm, Ph.D.

Kanda Rachmat Manajemen Penyelenggaraan

http://www.simpleweb.org/


http://www.youtube.com/

http://www.dpstele.com/layers/l2/snmp_tutorials.php

http://www.manageengine.com/network-monitoring/what-is-snmp.html

http://www.eogogics.com/talkgogics/tutorials/SNMP

http://www.javvin.com/protocolCMIP.html

http://www.javvin.com/protocolCMIP.html

http://www.eogogics.com/talkgogics/tutorials/SNMP

http://www.manageengine.com/network-monitoring/what-is-snmp.html

http://www.dpstele.com/layers/l2/snmp_tutorials.php

http://www.youtube.com/



Documents

04. Protokol Dan Aplikasi Network Management (Rev)