NETWORK MANAGEMENT SYSTEM FOR STUDENT

1. NETWORK MANAGEMENT
SYSTEM

2. CONCEPTS
T H E I N T E R N AT I O N A L O R G A N I Z AT I O N F O R
S TA N D A R D I Z AT I O N ( I S O ) N E T W O R K
M A N A G E M E N T F O R U M D I V I D E D N E T W O R K
M A N A G E M E N T I N T O F I V E F U N C T I O N A L
A R E A S :
FA U LT M A N A G E M E N T
C O N F I G U R AT I O N M A N A G E M E N T
S E C U R I T Y M A N A G E M E N T
P E R F O R M A N C E M A N A G E M E N T
A C C O U N T I N G M A N A G E M E N T

3. NETWORK MANAGEMENT
 Network management is the process of controlling a
complex data network to maximize its efficiency and
productivity
 The overall goal of network management is to help with
the complexity of a data network and to ensure that data
can go across it with maximum efficiency and transparency
to the users

4. FAULT MANAGEMENT
IS THE PROCESS OF LOCATING PROBLEMS, OR FAULTS, ON
THE DATA NETWORK
IT INVOLVES THE FOLLOWING STEPS:
Detect the fault
Determine exactly where the fault is
Isolate the rest of the network from the failure so that it can
continue to function
Reconfigure or modify the network in such a way as to
minimize the impact
Repair or replace the failed components
Tests: connectivity, data integrity, response-time, ….

5. CONFIGURATION MANAGEMENT
 THE CONFIGURATION OF CERTAIN NETWORK DEVICES
CONTROLS THE BEHAVIOR OF THE DATA NETWORK
 CONFIGURATION MANAGEMENT IS THE PROCESS OF
FINDING AND SETTING UP (CONFIGURING) THESE
CRITICAL DEVICES
 INVOLVES FOLLOWING STEPS:
 Installation of new hardware/software
 Tracking changes in control configuration
 Who, what and why? - network topology
 Revert/undo changes
 Change management
 Configuration audit
 Does it do what was intended

6. SECURITY MANAGEMENT
 Is the process of controlling access to information on the data network
 Provides a way to monitor access points and records information on a
periodic basis
 Provides audit trails and sounds alarms for security breaches
 Several security measures are provided:
 Security services: generating, distributing, storing of encryption
keys for services
 Exception alarm generation, detection of problems
 Uniform access control to resources
 Backups, data security
 Security logging

7. PERFORMANCE MANAGEMENT
 Involves measuring the performance of the network hardware, software, and media
 Examples of measured activities are:
› What is the level of capacity utilization?
› Is there excessive traffic?
› Has throughput been reduced to unacceptable levels?
› Are there bottlenecks?
› Is response time increasing?
› What is the error rates?
› Indicators: availability, response time, accuracy service
throughput, utilization efficiency

8. ACCOUNTING MANAGEMENT
 Involves tracking individual’s utilization and grouping of network resources to ensure that users have
sufficient resources
 Involves granting or removing permission for access to the network
 Identifying consumers and suppliers of network resources - users and groups
 Mapping network resources consumption to customer identity
 Billing

9. NETWORK MANAGEMENT
PROTOCOLS
 A simple protocol defines common data formats and parameters
and allows for easy retrieval of information
 A complex protocol adds some change capability and security
 An advanced protocol remotely executes network management
tasks, is independent of the network protocol layer
 Managed objects: functions provided by the network
 Element Management Systems (EMS): managing a specific portion
of the network (may manage a sync lines, multiplexers, routers)
 Managers of Manager Systems (Mom): integrate together
information from several EMS

10. NETWORK MANAGEMENT PROTOCOLS
So where is technology today?
• The most common protocols are:
• SNMP (Simple Network Management Protocol)
• SNMPv2 (SNMP version 2)
• CMIS/CMIP (Common Management Information Services/Common Management
Information Protocol)

11. NETWORK MANAGEMENT
REQUIREMENTS
•Example of approach
Controlling strategic assets
Controlling complexity
Improving service
Balancing various needs: performance,
availability, security, cost
Reducing downtime
Controlling costs

12. ADVANTAGES OF USING SNMP
Standardized
universally supported
Extendible
Portable
allows distributed management access
lightweight protocol

13. SNMP
 There are two approaches for the management system
to obtain information from SNMP
Traps
Polling

14. TRAP
T R A P S A R E U N R E Q U E S T E D E V E N T R E P O R T S T H AT A R E S E N T TO A
M A N A G E M E N T S Y S T E M BY A N S N M P A G E N T P R O C E S S
W H E N A T R A P PA B L E E V E N T O C C U RS , A T R A P M E S S A G E I S G E N E R AT E D BY
T H E A G E N T A N D I S S E N T TO A T R A P D E S T I N AT I O N ( A S P E C I F I C ,
C O N F I G U R E D N E T WO R K A D D R E S S )
M A N Y E V E N T S C A N B E C O N F I G U R E D TO S I G N A L A T R A P, L I K E A N E T WO R K
C A B L E FA U LT, FA I L I N G N I C O R H A R D D R I V E , A “G E N E R A L P R OT E C T I O N
FA U LT ”, O R A P OW E R S U P P LY FA I LU R E
T R A P S C A N A L S O B E T H R OT T L E D - - YO U C A N L I M I T T H E N U M B E R O F
T R A P S S E N T P E R S E C O N D F R O M T H E A G E N T
T R A P S H AV E A P R I O R I T Y A S S O C I AT E D W I T H T H E M - - C R I T I C A L , M A J O R ,
M I N O R , WA R N I N G , M A R G I N A L , I N F O R M AT I O N A L , N O R M A L , U N K N OW N

15. TRAP RECEIVERS
•Traps are received by a management application.
•Management applications can handle the trap in a few ways:
•Poll the agent that sent the trap for more information about the event, and the status of the rest of the
machine.
•Log the reception of the trap.
•Completely ignore the trap.
Management applications can be set up to send off an e-mail, call a voice
mail and leave a message, or send an alpha-numeric page to the network
administrator’s pager that says:
Your PDC just Blue-Screened at 03:46AM. Have a nice day. :)

16. SNMP MIBS
 Traps are unrequested event reports that are sent to a management system by an SNMP agent process
 When a trappable event occurs, a trap message is generated by the agent and is sent to a trap
destination (a specific, configured network address)
 Many events can be configured to signal a trap, like a network cable fault, failing NIC or Hard Drive, a
“General Protection Fault”, or a power supply failure
 Traps can also be throttled -- You can limit the number of traps sent per second from the agent
 Traps have a priority associated with them -- Critical, Major, Minor, Warning, Marginal, Informational,
Normal, Unknown

17. SNMP MIBS
•Types of MIB Modules
 Standard: These are the standard MIBS currently designed to capture the core
aspects of the particular technology
 Experimental: Temporary and if achieves standardization then it is placed in
the standard module
 Enterprise-specific: Vendor specific MIBS that provide additional management
capabilities for those features that require it

18. CIMS/CIMP
THE OSI FRAMEWORK IS AN OBJECT-ORIENTED PARADIGM
Objects have attributes, generate events, and perform
actions
Objects are scoped by numerous hierarchies for the
purpose of inheritance or containment
ALTHOUGH THE OSI MODEL “SOUNDS NEAT”, IT IS MUCH
MORE COMPLICATED AND IS NOT VERY COMMON

19. THANK YOU