Transcript management interface - Universitas Dian Nuswantoro

Network Management
L. Budi Handoko, M.Kom.
([email protected] /
[email protected])
Dian Nuswantoro University
Course Content (Syllabus)
1.
2.
3.
4.
Network Management Overview.
1.
2.
3.
Network Management Definition
Network Manager (Performer and Tools)
Network Monitor (What, When and Where)
1.
2.
Dimension of Management (Interoperability, Subject, Life Cycle, Layer)
Function and Reference Model (FCAPS, OAM&P, FAB, eTOM)
1.
2.
3.
4.
Management Information (Terminology, MIB)
Management Communication Patern (Layer, Interactions)
Management Protocol (SNMP, CLI, Syslog, Netconf, Netflow, IPFIX)
Management Organization (Scaling, Mediation)
1.
2.
3.
Management Integration (Needs, Challanges, Approach)
Service Level Management (Identification, Definition, Managing)
Management Metrics (Impact, Effectiveness)
Management Perspectives.
Management Bulding Blocks.
Applied Network Management.
References
• Alexander Clemm Ph.D, Network Management
Fundamentals, Cisco Press, 2006
• Extra :
▫ http://www.dmoz.org/Computers/Software/Netw
orking/Network_Management
▫ http://www.dmoz.org/Computers/Software/Inter
net/Network_Management
▫ http://www.slac.stanford.edu/xorg/nmtf/nmtftools.html
Grading Guidelines
• Middle Exam (30%)
• Final Exam (30%)
• Assignments (40%), consisting :
▫
▫
▫
▫
Individual Assignment
Group Assignment
Attendance
Project or Challange (If Any...)
Network Management
Refers to activities, methods, procedures and
tools that pertain to the operation,
administration, maintenance, and
provisioning
 Running -> Monitoring -> Understanding
 Carried out of a Network Operations Center
(NOC)
Network Management
• Operation
▫ Keeping the network (and service) up and run
▫ Monitoring network to spot problem ASAP
• Administration
▫ Keeping track of resource
▫ “housekeeping” to keep network under control
• Maintenance
▫ Perform repairs and upgrades
▫ Corrective and preventive measures to make network
run “better”
• Provisioning
▫ Configuring resource to support the service
Network Management
• The Importance
▫
▫
▫
▫
Reason
Cost
Quality
Revenue
• The Player
▫ Service Provider
▫ Enterprise IT Dept.
▫ End User
• Provider
▫ Equipment Vendor
▫ 3rd Party App. Vendor
▫ System Integrator
NOC (Network Operations Center)
• A place to do monitoring for network operations
/ activity
• To spot any problem to network operations
• A palace for Network Administrator
Management Tools
• Craft Terminals (Device Managers)
provide a user-friendly way for humans to interact with individual network equipment
• Network Analyzers (packet sniffers / packet analyzers / traffic analyzers)
view and analyze current traffic on a network, generally to understand the way in which the
network is behaving and to diagnose and troubleshoot particular problems
• Element Managers
systems that are used to manage equipment in a network
• Management Platforms
general-purpose management applications that are used to manage networks
• Collectors and Probes
auxiliary systems that offload applications from simple functions
• Intrusion Detection Systems (IDS)
help network providers to detect suspicious communication patterns on the network that might
be indicative of an ongoing attack
• Performance Analysis Systems
enable users to analyze traffic and performance data, with the goal of recognizing trends and
patterns in that traffic
• Alarm Management Systems
specialized in collecting and monitoring alarms from the network
Management Tools (Continuous)
• Trouble Ticket Systems
used to track how problems in a network (such as those that are indicated by alarms)
are being resolved
• Work Order Systems
used to assign and track individual maintenance jobs in a network
• Workflow Management Systems and Workflow Engines
helps manage the execution of workflows
• Inventory Systems
used to track the assets of a network provider
▫ Network inventory
▫ Service inventory
• Service Provisioning Systems
facilitate the deployment of services over a network, such as Digital Subscriber Line
(DSL) or telephone service for residential customers of large service providers
• Service Order–Management Systems
used to manage orders for services by customers of large service providers
• Billing Systems
Network Management Component
• The Network Device
The first main component in network management consists of the device
that must be managed.
• Management Agent
To be managed, a network element must offer a management interface
through which a managing system can communicate with the network
element for management purposes. Consists of three main parts :
• The management interface handles management communication.
• The Management Information Base (MIB) is a conceptual data
store that contains a management view of the device being managed.
• The core agent logic translates between the operation of the
management interface, the MIB, and the actual device.
• Management Information, MOs, MIBs, and Real Resources
In general, many aspects of a network device (such as a router or a switch)
are important for its management. (MO = Managed Object)
Anatomy of Management Agent
MIB Output Example
SNMPv2-MIB::sysDescr.0 = STRING: Server Storage Area Network
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (134802511) 15 days, 14:27:05.11
SNMPv2-MIB::sysContact.0 = STRING: L. Budi Handoko <[email protected]>
SNMPv2-MIB::sysName.0 = STRING: SAN
SNMPv2-MIB::sysLocation.0 = STRING: Gedung E Universitas Dian Nuswantoro Semarang
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (61) 0:00:00.61
SNMPv2-MIB::sysORID.1 = OID: SNMP-MPD-MIB::snmpMPDMIBObjects.3.1.1
SNMPv2-MIB::sysORID.2 = OID: SNMP-USER-BASED-SM-MIB::usmMIBCompliance
SNMPv2-MIB::sysORID.3 = OID: SNMP-FRAMEWORKMIB::snmpFrameworkMIBCompliance
SNMPv2-MIB::sysORID.4 = OID: SNMPv2-MIB::snmpMIB
SNMPv2-MIB::sysORID.5 = OID: TCP-MIB::tcpMIB
SNMPv2-MIB::sysORID.6 = OID: IP-MIB::ip
SNMPv2-MIB::sysORID.7 = OID: UDP-MIB::udpMIB
SNMPv2-MIB::sysORID.8 = OID: SNMP-VIEW-BASED-ACM-MIB::vacmBasicGroup
Aspects Interest to Network Management
• The version of installed software must be remotely determined, to decide
which devices need to have a new software patch installed.
• Utilization of ports must be assessed, to determine whether capacity
upgrades are necessary or whether surplus capacity could be redeployed.
• Environmental data is monitored to determine temperature and voltages, to
ensure that a device is not overheating.
• Fans are monitored to help remotely determine what is causing device
temperature to rise.
• Packet counters for different interfaces must be monitored; for example,
sudden jumps in certain types of packet counts could indicate that a
network is under a certain type of attack, such as a so-called denial-ofservice (DoS) attack.
• Protocol timeout parameters must be configured to fine-tune network
communication performance.
• Firewall rules that define a security policy must be configured (for example,
“Discard packets of a certain type unless they originate from an address
with a certain prefix”).
Differences in Network Equipment
Management Perspectives
• The Dimensions of Management
▫
▫
▫
▫
▫
▫
▫
Understanding The Dimensions
Management Interoperability
Management Subject
Management Life Cycle
Management Layer
Management Function
Management Process and Organization
• Management Functions and Reference Models (Getting
Organized)
▫
▫
▫
▫
FCAPS
OAM&P: The Other FCAPS
FAB and eTOM
How It All Relates and What It Means
Network Management Dimensions
Management Interoperability
Management Subject
• Network management, in a narrower sense, deals with the
management of communication networks and the resources in the
network that are required to establish end-to-end communications.
For example, this includes the routers and switches in a network, or
the communications backbone of a service provider.
• System management deals with the management of end systems
that are connected to networks. For example, this includes hosts and
servers in a data center, or personal computers on users’ desktops.
• Application management deals with the management of
applications that are deployed on systems that are interconnected
over a network. For example, this includes corporate e-mail
applications and security software that is supposed to be running on
computers.
Management Life Cycle
A Basic Management Life Cycle
Management Life Cycle (Planning)
Before any actual operations can take place, networks
must be planned. Based on current and forecasted user
needs, network equipment is selected, and its placement in
the network and location for installation determined. The
topology must be planned, taking into account resilience
and redundancy. Lines might have to be leased to
interconnect different sites. Capacities must be
determined, and the possibility of future growth must be
taken into account. An enterprise also must decide which
aspects of the network to run itself and which services to
buy from outside service providers. In all of this, cost and
budget constraints must be considered.
Management Life Cycle (Deployment)
When planning is completed, networks need to be
deployed. This means that equipment must be
installed and turned up. Deployment can involve its
own unique set of management procedures. For
example, when a piece of equipment is first installed,
it generally does not have an IP address. This means
that, at first, it cannot be reached remotely, including
from remote management applications. If the device
is installed by a network technician, this is not much
of a problem because the initial configuration steps
can occur through a console directly connected to the
device.
Management Life Cycle (Operation)
After turn-up and installation, the regular
operation of the network follows. This is where
many of the most typical activities that are
associated with network management take place:
monitoring the network, troubleshooting,
conducting performance tuning, collecting
performance statistics and accounting data, and
so forth.
Management Life Cycle
(Decommissioning)
Eventually, network equipment might have to be
decommissioned in an orderly manner. There can
be many reasons for decommissioning. For
example, new technologies replace old ones and
lead to a general network upgrade, or
requirements might have changed and certain
types of network equipment are no longer needed.
Management Layer
• A well-established categorization of
management layers for the management of
networks is the TMN hierarchy.
• TMN refers to a set of standards by the
International Telecommunications Union (ITUT) for the specification of a Telecommunications
Management Network (hence, the acronym
TMN).
Management Layer (TMN Layers)
Management Layer (TMN Layers)
• Element Management
The element management layer involves managing
the individual devices in the network and keeping
them running. This includes functions to view and
change a network element’s configuration, to
monitor alarm messages emitted from elements in
the network, and to instruct network elements to
run self-tests.
Management Layer (TMN Layers)
• Network Management
The next layer in the TMN hierarchy is the network
management layer. In the context of TMN, network
management refers just to this one layer. In this
section, the term is accordingly used in a narrower
sense than elsewhere in this book, where it refers
not only to one of several management layers, but to
the discipline of managing networks as a whole.
Management Layer (TMN Layers)
• Service Management
Service management is concerned with managing
the services that the network provides and ensuring
that those services are running smoothly and
functioning as intended.
Management Layer (TMN Layers)
• Business Management
Business management deals with managing the
business associated with providing services and all
the required support functions. This includes topics
as diverse as billing and invoicing, helpdesk
management, business forecasting, and many more.
Management Layer (TMN Layers)
• Network Element
A fifth layer of the hierarchy is often forgotten: the
network element itself—the management agent, in
effect. The network element is involved with the
management functionality that the network element
itself supports, independent of any management
system.