Need for network management and NMS
Operations, Administration, Maintenance, and Provisioning
Network management architecture and organization
Concept of Network Operations Center
Perspectives of network management
Network management system
Look-ahead of network management technology
*
*
Telephone Network
Modern network evolution from Telephone /
Telecommunications Network Characteristics of Telephone
network Reliable - does what is expected of it Dependable -
always there when you need it (remember 911?) Good quality
(connection) - hearing each other well Reasons for QoS: Good
planning, design, and implementation Good operation and
management of network Migration to new technologies – e.g.,
From analog to digital technology
*

*
Notes
Telephone Network Model
Notice the hierarchy of switches5 levels of switches and 3
types of trunksLoop: between telephone/PBX and end
officeDirect trunk between two end-officesToll-connecting
trunk: end office to any toll officeToll (internal) trunk: between
toll offices Primary and secondary routes programmed
Automatic routing Where is the most likely failure? Use of
Operations Systems to ensure QoS
*
*
OSSs / NOC
Operations Support Systems (OSSs) help manage the operation
of networks OSSs in telecommunications monitor: Analog
network parameters: S/N ratio, transmission loss, call blockage,
etc. Digital network parameters: Packet loss, Packet delay,
Throughput, QoS, etc. Real-time management of network Trunk
(logical entity between switches / nodes) maintenance system
measures loss and S/N Trunks not meeting QoS removed before

customer notices poor quality Traffic measurement systems
measure call drops and blockage. Additional switches or routers
planned to keep the call blockage or drops below acceptable
level OSSs distributed at central offices and customer premises
Network management done centrally from Network Operations
Center (NOC)
*
*
Notes
Data and Telecommunication Network
Computer data is carried over long distance by telephone
(telecommunication network) Output of telephone is analog and
output of computers is digital Modem is used to “modulate” and
“demodulate” computer data to analog format and back Clear
distinction between the two networks is getting fuzzier with
modern multimedia networks
*

*
Notes
Migration to Digital Technology
Analog transmission migrated to digital transmission Analog
sources converted to digital signals CPE (Customer Premises
equipment) included digital PBX (Private Branch Exchanges)
Analog bandwidth hierarchy migrated to synchronous digital
hierarchy
*
*
Notes
DCE with LAN
DCE.. Distributed Computing Environment Driving
technologies for DCE: Desktop processor LAN LAN - WAN
network

*
*
Notes
LAN-WAN Network
Major impacts of DCE: No more monopolistic service provider
No centralized IT controller Hosts doing specialized function
Client/Server architecture formed the core of DCE network
Figure 1.5(b) Remote LANs Interconnected by WAN
*
*
Notes
Client/Server Model
Post office analogy; clerk the server, and the customer the
client Client always initiates requests Server always responds
Notice that control is handed over to the receiving entity.
Request
Response

*
*
Notes
Client/Server Examples
*
*
Notes
TCP/IP Based Networks
TCP/IP is a suite of protocols Internet is based on TCP/IP IP is
Internet protocol at the network layer level TCP is connection-
oriented transport protocol and ensures end-to-end connection
UDP is connectionless transport protocol and provides datagram
service Internet email and much of the network mgmt. messages

are based on UDP/IP ICMP part of TCP/IP suite
*
*
Notes
Internet Configuration
Walk through the scenario of email from Joe to Sally
*
*
Notes
Architecture, Protocols and Standards
Communication architecture Modeling of communication
systems, comprising Functional components Operations
interfaces between them Communication protocols Operational

procedures Intra- and inter-modules Communication standards
Agreement between manufacturers on protocols of
communication equipment on Physical characteristics
Operational procedures Examples: (Students to call out)
*
*
Notes
Communication Architecture
Inter-layer interface: user and service provider Peer-layer
protocol interface Analogy of hearing-impaired student Role of
intermediate systems Gateway: Router with protocol conversion
as gateway to an autonomous network or subnet
*
*

Notes
OSI Reference Model
Importance of the knowledge of layer structure in NM
*
*
Notes
OSI Layers and Services
Importance of services offered by different layers and the
protocol conversion at different layers in NM
*
LayerNo.
Layer Name
Salient services provided by the layer
1

Physical
-Transfers to and gathers from the physical medium raw bit data
-Handles physical and electrical interfaces to the transmission
medium
2
Data link
-Consists of two sublayers: Logical link control (LLC) and
Media access control (MAC)
-LLC: Formats the data to go on the medium; performs error
control and flow control
-MAC: Controls data transfer to and from LAN; resolves
conflicts with other data on LAN
3
Network
Forms the switching / routing layer of the network
4
Transport
-Multiplexing and de-multiplexing of messages from
applications
-Acts as a transparent layer to applications and thus isolates
them from the transport system layers
-Makes and breaks connections for connection-oriented
communications
-Flow control of data in both directions
5
Session

-Establishes and clears sessions for applications, and thus
minimizes loss of data during large data exchange
6
Presentation
-Provides a set of standard protocols so that the display would
be transparent to syntax of the application
-Data encryption and decryption
7
Application
-Provides application specific protocols for each specific
application and each specific transport protocol system
*
Notes
PDU Communication Model
What is the relevance of PDU model in NM?
*
*

Notes
Gateway
cc: mail from a station in Novel IPX network to an Internet
station with SMTP email
*
*
Notes
OSI and Internet
Simplicity of Internet; specifies only layers 3 and 4 Integrated
application layers over Internet Commonality of layers 1 and 2 -
IEEE standard
*
*

Notes
Application Protocols
Internet user OSI user
Telnet Virtual Terminal
File Transfer Protocol File Transfer Access & Mgmt
Simple Mail Transfer Message-oriented Text
Protocol Interchange Standard
Simple Network Common Management
Management Protocol Information Protocol
*
*
Notes
Broadband Network

Figure 1.19 Broadband Network Segments and Technologies
*
*
Notes
Broadband Access Networks
*
*
Notes
Centrally Managed Network Issues

© Mani Subramanian 2010INMS: Integrated Network
Management SystemEMS: Element Management SystemINMS
integrates alarms from multiple EMSsEach EMS manages a
domain and passes the relevant events to the INMS
*
*
Notes
Some Common Network Problems
Loss of connectivity (connectivity and node failures) Duplicate
IP address(e.g. with multiple system administrators)
Intermittent problems Network configuration issuesE.g. Power
-problemsThe cause of failure is
a mystery Performance problems
*
*

Notes
Challenges of IT Managers
Reliability Non-real time problems Rapid technological
advance Managing client/server environment Scalability
Troubleshooting tools and systems Trouble prediction
Standardization of operations - NMS helps Centralized
management vs. “sneaker-net”
*
*
Notes
Network Management
OAMP Operations AdministrationAdministrate overall goals,
policies, and procedures of NM Maintenance Provisioning
*

*
Notes
NM Functional Flow Chart
© Mani Subramanian 2010NOC is responsible for service
restoration when failureSelf-healing: when restoration is done
automaticallyRestoration does not include fixing the cause of
the problemI&M responsibilityA Trouble Ticket is generated
and followed up for problem resolution
Configuration management: static, running, and planning
*
*
Notes
Dumbbell Architecture
Message exchange between NMSs managing different
domainsManagement information data (type, id, status of
managed objects)and management controls (setting and
changing configuration of an object)
© Mani Subramanian 2010Network management vs Network

system and service managementNetwork management is
concerned with network equipment and the connectivity among
themNetwork system and service management: manage the
system resources in the network and network services
May need installation/integration of multiple NMSsStandards
for interoperabilityNetwork management dumbbell architecture
for interoperabilityApplication services: e.g. fault and
configuration managementManagement protocols: e.g. CMIP
and SNMPTransport protocols: first 4 layers of OSI and first 2
layers of Internet model
*
*
Notes
NM Components
© Mani Subramanian 2010The agent can be:An embedded
agent in a network elementEMS communicating with agents
embedded in the network elementsThe agent communicates to
the NMS the relevant dataResponse to a polled query from the
NMSTriggered by a local alarm
*

*
Notes
Interoperability
Message exchange between NMSs managing
different domains
Figure 1.26 Network Management Interoperability
© Mani Subramanian 2010Each NMS can superimpose the data
from the otherPresent an integrated picture to the network
administrator
*
*
Notes
Network Management Perspectives
Network ManagementDomains (based on geographic, vendor,
technology) + protocols + network and transmission
technologies Service ManagementQoS parameters + SLA
between service provider and customerCommunication services:
internet, Virtual Private Network, real-time interactive audio
applications that run on them Service and Network Provisioning

Application Management e-Commerce Management Inventory
ManagementInventory of equipment (active components
forming nodes of the network) and facilities (passive
components linking the nodes) Integrated Management Business
Management Information Management Management Protocols
Management Technologies
*
*
Notes
Infrastructure Perspective
Domains Protocols Technologies Transmission Media
Transmission Modes Service Functions
*
*
Notes
Service Perspective

Communication Services Computing Services Content Services
IT Services Application Services
*
*
Notes
Status and Future Trends
Status: SNMP managementLimitations: Poll-based + use of
scalar values Limited CMIP managementObject-oriented but
complexity of specifications of managed objects Operations
systemsUNIX for high-end systems Polled systemsNetwork
traffic overhead Current Focus: Object-oriented approach
Service and policy management Business management Web-
based client management Future Trends Web-based
management? XML based management
*
Regional Center
Class 1 switch
Sectional Center
Class 2 switch
Primary Center

Class 3 switch
Toll Center
Class 4 switch
End Office
Class 5 switch
Regional Center
Class 1 switch
Sectional Center
Class 2 switch
Primary Center
Class 3 switch
Toll Center
Class 4 switch
End Office
Class 5 switch
Voice
Voice
To other
Regional centers
Sectional centers
Primary centers
Toll centers
End offices
To other
Primary centers
Toll centers
End offices
To other
Class 4 toll points
End offices
Figure 1.1 Telephone Network Model
Legend:
Loop
Direct Trunk
Toll-Connecting Trunk
Toll Trunk

Terminal
Modem
Voice
Terminal
Modem
Modem
Voice
Host
Data communication network
Telecommunication network
Figure 1.3 Data and Telecommunication Networks
Loop
Loop
Loop
Terminal
Communications
controller
Terminal
Front end
processor
Host
Data communication network
Telecommunication network
Figure 1.4 Digital Data and Telecommunication Networks
PBX
Voice
PBX
Voice
Voice
Voice
Ethernet
Workstation
Workstation
Host
Host
Workstation

Fgure 1.5(a) Hosts and Workstations on Local LAN
LAN A
LAN B
LAN C
Bridge /
Router
Bridge /
Router
Bridge /
Router
WAN
communication link
Client
Server
Control
transfer
Control
transfer
Figure 1.6 Simple Client-Server Model
Client A
Client Z
Server
(a) Server with Multiple Clients
Client
(joe.stone)
Domain
Name
Server
Mail server
(b) Dual Role of Client-Server
Figure 1.7 Client-Server in Distributed Computing Environment
Bridge
to [email protected]
LAN A
LAN B
LAN C

Bridge /
Router
Bridge /
Router
Bridge /
Router
LAN Y
LAN Z
LAN X
Bridge /
Router
Bridge /
Router
Bridge /
Router
WAN
Workstation
Mail Server
Figure 1.8 Internet Configuration
Mail Server
Workstation
Gateway
Gateway
Domain
Name
Server
Workstation
(Joe)
PC (Sally)
User A
Application Layers
Transport Layers
User Z
Application Layers
Transport Layers
Physical Medium

Peer-Protocol Interface
(a) Direct Communication between End Systems
User A
Application Layers
Transport Layers
User Z
Application Layers
Transport Layers
Physical Medium
Peer-Protocol Interface
(b) Communication between End Systems via an Intermediate
System
Transport Layer
Conversion
Figure 1.10 Basic Communication Architecture
System A
Intermediate system
System Z
Physical Medium
User / Application program
Application
Layer 7
Presentation
Layer 6
Session
Layer 5
Transport
Layer 4
Network
Layer 3
Data link
Layer 2
Physical
Layer 1
Physical medium
Figure 1.11 OSI Protocol Layers

Layer
No.
Layer Name
Salient services provided by the layer
1
Physical
-Transfers to and gathers from the physical medium raw
bit data
-Handles physical and electrical interfaces to the
transmission medium
2
Data link
-Consists of two sublayers: Logical link control (LLC) and
Media access control (MAC)
-LLC: Formats the data to go on the medium; performs
error control and flow control
-MAC: Controls data transfer to and from LAN; resolves
conflicts with other data on LAN
3
Network
Forms the switching / routing layer of the network
4
Transport
-Multiplexing and de-multiplexing of messages from
applications
-Acts as a transparent layer to applications and thus
isolates them from the transport system layers
-Makes and breaks connections for connection-oriented
communications
-Flow control of data in both directions
5
Session
-Establishes and clears sessions for applications, and
thus minimizes loss of data during large data exchange
6
Presentation

-Provides a set of standard protocols so that the display
would be transparent to syntax of the application
-Data encryption and decryption
7
Application
-Provides application specific protocols for each specific
application and each specific transport protocol system
User A
Application
End System A
Physical Medium
Figure 1.13 PDU Communication Model between End Systems
Presentation
Session
Transport
Network
Data link
Physical
User Z
Application
End System Z
Presentation
Session
Transport
Network
Data link
Physical
UD
(A) PCI
(P) PCI
(A) PDU
(S) PCI
(N) PCI
(T) PCI
(P) PDU
(S) PDU

(D) PCI
(T) PDU
(N) PDU
UD
(D)PDU Data stream
SNICP
SNDCP
SNDAP
Transport
Data link
SNICP
SNDCP-SN
SNDAP-SN
Transport
Data link-SN
SNDCP-SN
SNDAP-SN
Transport
Data link
SNICP
SNDCP
SNDAP
Physical-SN
Data link-SN
Physical
Physical-SN
Physical
Subnetwork Medium
Network Medium
System A
Gateway System N
Subnet system N1
N
Z
A
N1

N2
N3
DTE-N1
DTE-A
A-N-Z Standard Network
N-N1-N2-N3 Subnetwork under Node N
(a) Network configuration
(b) Protocol Communication
Figure 1.16 Gateway Communication to Private Subnetwork
Application
Presentation
Session
Transport
Network
SNICP
SNDCP
SNDAP
Data Link
Physical
Application Specific
Protocols
Transport
Connection-
less: UDP
Connection-
oriented: TCP
Network
IP
Not Specified
OSI
INTERNET
Figure 1.17 Comparison of OSI and Internet Protocol Layer
Models
OSI User
VT
FTAM

MOTIS
CMIP
SNMP
SMTP
FTP
Terminal
Application
File Transfer
Mail / Message
Transfer
Management
Application
Presentation Layer
Transport Layer
TELNET
Internet User
Figure 1.18 Application Specific Protocols in ISO and Internet
Models
Edge
Router
Cable
DSL
Fixed
Wireless
Mobile
Wireless
Satellite
PON
Residential
Gateway
LAN
WLAN
HomePlug
Bluetooth
HomePNA
Cable

Access
Network
CPE
Network
IP
ATM
WAN
UWB
Firewire
MPLS
IP / ATM
WAN
Business
Customers
Cable Modem
Customer
Network
OC-n /
STS-n
Link
HFC
Network
Cable
Modem
DSL
Customer
Network
xDSL
Modem
Telephone
Loop
Fixed
Wireless
Customer
Network
Cable

Modem
Head End
Central
Office
Equipment
Router/
ATM Switch
Router/
ATM Switch
Terrestrial
Wireless
Satellite Communication
Access
Point
Network
Mobile
Unit
BSU
G-3 Wireless
BSU
Figue 1.20 Broadband Access Networks
EMS
Network
Element
Domain
EMS
Network
Element
Domain
EMS
Network
Element
Domain
INMS
Figure 1.21 Case History 2:
Centrally Managed Network Issues

Network
Management
Network
Provisioning
Network
Operations
Network
Maintenance
Planning
Design
Fault Management
Trouble Ticket
Administration
Network Installation
Network Repairs
Facilities Installation
& Maintenance
Routine Network
Tests
Fault Management / Service Restoration
Configuration Management
Performance Management / Traffic Management
Security Management
Accounting Management
Reports Management
Inventory Management
Data Gathering & Analyses
Figure 1.22 Network Management Functional Groupings
Engineering Group
- Network Planning &
Design
Operations Group
NOC
- Network Operations
I
& M Group

-Network Installation &
Maintenance
Fault TT
Configuration Data
TT Restoration
Performance & Traffic Data
Installation
Figure 1.23 Network Management Functional Flow Chart
New
Technology
Network
Users
Management
Decision
Vendor A
(b) Services and Protocols
Application
Services
Management
Protocol
Transport
Protocols
Objects
Objects
Vendor B
Objects
Objects
Figure 1.24 Network Management Dumbbell Architecture
NMS
Network
Agent
Network
Agent
Network
Objects
Network

Objects
Figure 1.25 Network Management Components
NMS
Vendor A
Network
Agent
Network
Agent
Network
Objects
Network
Objects
NMS
Vendor B
Network
Agent
Network
Agent
Network
Objects
Network
Objects
Messages
Services & Protocols
Week 7 Assignment – BE
Business Ethics – Week 7 Assignment
LEED
Investigate LEED (Leadership in energy and Environmental
Design) building designs. Should all new buildings be required
by law to adopt LEED design standards and conform to the
LEED rating system?
Write a 2-3 page, APA style paper addressing the above issue.
Students can learn about LEED on the U.S. Green Building
Council’s website:
· http://www.usgbc.org/DisplayPage.aspx?CategoryID=19

Provide 3-5 APA style references both inline and at the end of
the paper to support your analysis. Please write in 3rdperson.
Note: This is your opportunity to demonstrate your knowledge
of the week’s theory linked to personal opinion and outside
evidence.
Your paper should reflect scholarly writing and current APA
standards. Please include citations to support your ideas.
Chapter 3 Basic Foundations: Standards, Models,
and Language
Chapter 3
Basic Foundations:
Standards, Models, and Language
Network Management: Principles and Practice ©
Mani Subramanian 2010
1
*
Objectives
Standards, Models, and Language needed for network
management

Network Models
OSI
Internet
TMN
IEEE 802
Web-based
Management communication protocols
SNMP
CMIP
XML
CORBA
ASN.1 language
Syntax
Macro
Basic encoding rule
Management application functions
2
and Language
*
Introduction

Standards
Standards organizations
Protocol standards of transport layers
Protocol standards of management (application) layer
Management Models
Language
and Language
Notes
3
Table 3.1 Network Management Standards
4
and LanguageStandardSalient PointsOSI/CMIP: Common
Management Information Protocol International standard
(International Standard Organization: ISO/Open System
Interconnection: OSI)
Management of data communications network - LAN and WAN
Deals with all 7 layers

Most complete
Object oriented
Well structured and layered
7. Consumes large resource in implementationInternet/SNMP:
Simple Network Management Protocol Industry standard
(Internet Engineering Task Force: IETF)
Originally intended for management of Internet components,
currently adopted for WAN and telecommunication systems
Easy to implement
Most widely implementedTMN: Telecommunication
Management Network International standard (ITU-T)
Management of telecommunications network
Based on OSI network management framework
Addresses both network and administrative aspects of
management
enhanced Telecommunications Operations Map (eTOM) is a
guidebook for business processes for implementing TMN using
NGOSS (New Generation OSS) frameworkIEEE IEEE standards
adopted internationally
Addresses LAN and MAN management
Adopts OSI standards significantly
Deals with first two layers of OSI RMWeb-based Management
Web-Based Enterprise Management (WBEM)
Java Management Extension (JMX)
XML-Based Network Management
CORBA-based Network Management

Notes
OSI Architecture and Model
Organization
Network management components
Functions of components
Relationships
Information
Structure of management information (SMI)
Syntax and semantics
Management information base (MIB)
Organization of management information
Object-oriented
and Language
5
Notes

Communication
Transfer syntax with bidirectional messages
Transfer structure (PDU)
Functions
Application functions
Configure components
Monitor components
Measure performance
Secure information
Usage accounting
and Language
OSI Architecture and Model (cont.)
6
Notes
SNMP Architecture and Model
Organization
Same as OSI model
Information

Same as OSI, but scalar
Communication
Messages less complex than OSI and unidirectional
Transfer structure (PDU)
Functions
Application functions
Fault management
Configuration management
Account management
Performance management
Security management
and Language
7
Notes
TMN Architecture
Addresses management of telecommunication networks

Based on OSI model
Superstructure on OSI network
Addresses network, service, and business management
and Language
8
Organizational Model
Manager
Sends requests to agents
Monitors alarms
Houses applications
Provides user interface
Agent
Gathers information from objects
Configures parameters of objects
Responds to managers’ requests
Generates alarms and sends them to managers
Managed object

Network element that is managed
Houses management agent
All objects are not managed / manageable
and Language
9
Notes
Two-Tier Model
Managed vs unmanaged objects/elements
Agent built into network element
Example: Managed hub, managed router
An agent can manage multiple elements
Example: Switched hub, ATM switch
MDB is a physical database
Unmanaged objects are network elements that are not managed
- both physical (unmanaged hub) and logical (passive elements)
and Language

10
Notes
Three-Tier Model
Middle layer plays the dual role
Agent to the top-level manager
Manager to the managed objects
Example of middle level: Remote monitoring agent (RMON)
and Language
11

Notes
Manager of Managers
Agent NMS manages the domain
MoM presents integrated view of domains
Domain may be geographical, administrative, vendor-specific
products, etc.
and Language
12
Notes
Peer NMSs
Dual role of both NMSs
Network management system acts as peers

Dumbbell architecture discussed in Chapter 1
Notice that the manager and agent functions are processes and
not systems
For example, two network service providers need to exchange
management
information between them
and Language
13
Information Model: Analogy
Figure in a book uniquely identified by
ISBN, Chapter, and Figure number in that hierarchical order
ID: {ISBN, chapter, figure}
The three elements above define the syntax
Semantics is the meaning of the three entities according to
Webster’s
dictionary
The information comprises syntax and semantics about an
object

and Language
Notes
14
Notes
Structure of Management Information (SMI)
SMI defines for a managed object
Syntax
Semantics
Plus additional information such as status
Example
sysDescr: { system 1 }
Syntax: OCTET STRING
Definition: "A textual description of the entity. "
Access: read-only
Status: mandatory
and Language
15

Notes
Management Information Base (MIB)
Information base contains information about objects
Organized by grouping of related objects
Defines relationship between objects
It is NOT a physical database. It is a virtual database that is
compiled into management module
and Language
16

Notes
Information Base View: An Analogy
Fulton County library system has many branches
Each branch has a set of books
The books in each branch is a different set
The information base of the county has the view (catalog) of all
books
The information base of each branch has the catalog of books
that belong to that branch.
That is, each branch has its view (catalog) of the information
base
Let us apply this to MIB view
and Language
17
Notes
MIB View and Access of an Object
A managed object has many attributes - its information base
There are several operations that can be performed on the

objects
A user (manager) can view and perform only certain
operations on the object by invoking the management agent
The view of the object attributes that the agent perceives is the
MIB view
The operation that a user can perform is the MIB access
and Language
18
Notes
Management Data Base / Information Base
Distinction between MDB and MIB
MDB physical database; e.g., Oracle, Sybase
MIB virtual database; schema compiled into management
software.
An NMS can automatically discover a managed object, such
as a hub, when added to the network
The NMS can identify the new object as hub only after the
MIB schema of the hub is compiled into NMS software.

and Language
19
Notes
Managed Object
Managed objects can be
Network elements (hardware, system)
Hubs, bridges, routers, transmission facilities
Software (non-physical)
Programs, algorithms
Administrative information
Contact person, name of group of objects (IP group)
and Language
20

Notes
Management Information Tree
and Language
Each managed object occupies a node in the tree
21
Notes

OSI Management Information Tree
iso International Standards Organization
itu International Telecommunications Union
dodDepartment of Defense
Designation:
iso 1
org 1.3
dod 1.3.6
internet 1.3.6.1
and Language
22
Notes
Type
Name
Syntax
Definition
Status
Access

Instance
Object Type and Instance
Example of a circle
“circle” is syntax
Semantics is definition from dictionary “A plane figure
bounded by a single
curved line, every point of which is of equal distance from the
center of the
figure.”
Analogy of nursery school
and Language
23
Notes
Managed Object: Internet Perspective
object ID unique ID
and descriptor and name for the object
syntax used to model the object
access access privilege to a managed object
status implementation requirements
definition textual description of the semantics

of object type
and Language
24
Notes
object class managed object
attributes attributes visible at its boundary
operations operations which may be applied to it
behaviour behavior exhibited by it in response to
operation
notifications notifications emitted by the object
Managed Object: OSI Perspective
and Language

25
Notes
Packet Counter Example
and Language
26

Notes
Internet vs. OSI Managed Object
Scalar object in Internet vs. Object-oriented approach in OSI
OSI characteristics of operations, behavior, and notification
are part of communication model in Internet: get/set and
response/alarm
Internet syntax is absorbed as part of OSI attributes
Internet access is part of OSI security model
Internet status is part of OSI conformance application
OSI permits creation and deletion of objects; Internet does
not: Enhancement in SNMPv2
and Language
27
Notes
Mgmt. Communication Model
In Internet requests/responses, in OSI operations
In Internet traps and notifications (SNMPv2), in OSI
notifications

and Language
28
Notes
Transfer Protocols
Internet is based on SNMP; OSI is based on CMIP
OSI uses CMISE (Common Management Information Service
Element) application with CMIP
OSI specifies both c-o and connectionless transport protocol;
SNMPv2 extended to c-o, but rarely used
and Language
29

Abstract Syntax Notation One
ASN.1 is more than a syntax; it’s a language
Addresses both syntax and semantics
Two types of syntax
Abstract syntax: set of rules that specify data type and
structure for information storage
Transfer syntax: set of rules for communicating information
between systems
Makes application layer protocols independent of lower layer
protocols
Can generate machine-readable code: Basic Encoding Rules
(BER) is used in management modules
and Language
Notes
30

Notes
Backus-Nauer Form (BNF)
Definition:
<name> ::= <definition>
Rules:
<digit> ::= 0|1|2|3|4|5|6|7|8|9
<number> ::= <number> | <digit> <number>
<op> ::= +|-|x|/
<SAE> ::= <number>|<SAE>|<SAE><op><SAE>
Example:
9 is primitive 9
19 is construct of 1 and 9
619 is construct of 6 and 19
BNF is used for ASN.1 constructs
Constructs developed from primitives
The above example illustrates how numbers are constructed
from the primitive <digit>
Simple Arithmetic Expression entity (<SAE>) is constructed
from the primitives <digit> and <op>
and Language
31

Notes
Simple Arithmetic Expression
<SAE> ::= <number> | <SAE><op><number>
Example: 26 = 13 x 2
Constructs and primitives
and Language
32
Notes
Type and Value
Assignments
<BooleanType> ::= BOOLEAN

<BooleanValue> ::= TRUE | FALSE
ASN.1 module is a group of assignments
person-name Person-Name::=
{
first "John",
middle “T",
last "Smith"
}
and Language
<BooleanType> ::= BOOLEAN
Data type assignment
<BooleanValue> ::= TRUE | FALSE
Value assignment
TRUE (All capital letters)
Keywords
33
Notes
Data Type: Example 1

Module name starts with capital letters
Data types:
Primitives: NULL, GraphicString
Constructs
Alternatives : CHOICE
List maker: SET, SEQUENCE
Repetition: SET OF, SEQUENCE OF:
Difference between SET and SEQUENCE
and Language
34
Notes
Data Type: Example 2
SEQUENCE OF SEQUENCE makes table of rows
and Language

35
Notes
ASN.1 Symbols
Symbol Meaning
::= Defined as
| or, alternative, options of a list
- Signed number
-- Following the symbol are comments
{} Start and end of a list
[] Start and end of a tag
() Start and end of subtype
.. Range
and Language
36

Notes
CHOICE
SET
SEQUENCE
OF
NULL
Keyword Examples
Keywords are in all UPPERCASE letters
and Language
37
Notes
ASN.1 Data Type Conventions

and Language
Module: group of assignments that are related to each other
Advantages of modules: can be imported or exported
Example of MIB definition module:
RFC1213-MIB DEFINITIONS ::= BEGIN
…
END
38
Notes
Data Type: Structure & Tag
Structure defines how data type is built
Tag uniquely identifies the data type
and Language

39
Notes
Structure
Simple
PageNumber ::= INTEGER
ChapterNumber ::= INTEGER
Structure / Construct
BookPageNumber ::=
SEQUENCE
{ChapterNumber, Separator, PageNumber
Example: {1-1, 2-3, 3-39}
Tagged
Derived from another type; given a new ID
In Fig. 3-14, INTEGER is either universal or
application specific
Other types:
CHOICE, ANY
BookPages ::= SEQUENCE OF { BookPageNumber}
or
BookPages ::=

SEQUENCE OF
{
SEQUENCE
{ChapterNumber, Separator, PageNumber}
}
and Language
40
Notes
Tag
Example:
BOOLEAN Universal 1
INTEGER Universal 2
research Application [1] (Figure 3.13)
product-based Context-specific under research [0]
and Language
Tag uniquely identifies a data type

Comprises class and tag number
Class:
- Universal - always true
Application-independent
- Application - only in the application used
Can override universal class tag number
EmployeeNumber ::=[APPLICATION 2] IMPLICIT
INTEGER
- Context-specific - specific context in application
- Private - used extensively by commercial vendors
41
Notes
Enumerated Integer
ENUMERATED is a special case of INTEGER
Example: RainbowColors(5) is orange
and Language

42
Notes
ASN.1 Module Example
and Language
43

Chapter 3 Basic Foundations: Standards,
Models, and Language
44
Notes
Object Name
internet OBJECT IDENTIFIER ::=
{ISO(1) ORG(3) DOD(6) INTERNET(1)}
and Language
45

Notes
TLV Encoding
and Language
TLV Type, length, and value are components
of the structure
Type has 3 subcomponents
- P/C: primitive (simple) or Construct
Example, INTEGER belongs to universal class
Is a primitive data type and has a tag value of 2
So the type is 00 0 00010
46

Notes
Macro
Macro is used to create new data types
Example:
and Language
47
Notes
Functional Model
Configuration management
Set and change network configuration component parameters
Set up alarm thresholds
Fault management
Detection and isolation of failures in network
Trouble ticket administration

Performance management
Monitor performance of network
Security management
Authentication
Authorization
Encryption
Accounting management
Functional accounting of network usage
and Language
48
Network
Management
Information
Model
Organization
Model
Functional
Model
Communication

Model
Manager
Managed objects
MDB
MIB
Agent process
MDB Management Database
MIB Management Information Base
OSI
Functional Model
Fault
Management
Configuration
Management
Performance
Management
Security
Management
Accounting
Management

Chapter 1Data Communications and Network Mana.docx

Recommended

Recommended

More Related Content

Similar to Chapter 1Data Communications and Network Mana.docx

Similar to Chapter 1Data Communications and Network Mana.docx (20)

More from walterl4

More from walterl4 (20)

Recently uploaded

Recently uploaded (20)

Chapter 1Data Communications and Network Mana.docx