Q1. Compare between SNMP vl, SNMP v2 and SNMP v3.

Cotent SNMPv1 SNMPv2 SNMPv3

Version SNMPv1 was the first SNMPv2 currently SNMPv3 is the newest
version of SNMP exists in at least three version of SNMP.
flavors, SNMPv2c,
SNMPv2u, and
SNMPv2
protocol operations Simple Similarity: Get, SNMPv3 uses
request/ response GetNext, Set Changes: SNMPv2 protocol
protocol. Protocol Trap message format operations and its PDU
operations :Get, New protocol message format
GetNext, Set, and Trap operations GetBulk and
Inform
Security No security from SNMPv2 failed to Its primary feature is
someone with access to improve on security. enhanced security.
the network
Complexity Performance and More powerful but SNMPv3 focuses on
security limitations. more complex than improving the security
SNMPv1 aspect.
Message Format Five Seven messages instead Implements SNMP v1
messages(GetRequest,, of five (inform-request, and v2 specifications
GetNextRequest, get-bulk-request) along with proposed
SetRequest, Trap, new features.
Response)
Protocol An open, standard Simple The "EngineID"
protocol, Streamlined request/response Identifier in SNMPv3
protocol protocol uniquely identifies each
SNMP entity.
MIB Defines limited, easily Defines general Can configure agents to
implemented MIB of framework with which provide a number of
scalar variables and MIB defined and levels of access to MIB
two dimensional tables constructed
Plaintext community Yes Yes No
strings
Encrypted traffic, No Yes Yes
Detection of
malformed packets
Susceptible to brute- Yes Yes No
force attacks,
Susceptible to buffer-
overflow attacks
Susceptible to injection Yes No No
attacks
Q2.What is RMON (Remote Network Monitoring)?
ANS: RMON is a method of collecting and analysing information from remote network elements
(NES)
• RMON provides the information to determine where to place the boundaries between
collision and broadcast domains, functions provided by LAN switches and routes.
• RMON agent attached to a local network element captures information and statistics on
protocols and traffic activity communicates the information back to a central RMON
management console for processing
• RMON is especially critical when managing a switched Lan environment because LAN
segments which previously served many users are now micro segmented. This micro
segmentation creates more segments to manage closer to the user.
• RMON LAN troubleshooting can be performed proactively with the engineer using RMON
agents to look for things that are abnormal based on the threshold criteria.
• RMON probes can provide a great deal of information on performance of your LAN and
WAN, capturing protocol traffic patterns that enable trending of protocol performance.
• RMON can catch utilization patterns that are exceeding thresholds and alerts the engineer to
take action.
• All of these monitoring can be done remotely and thus eliminates the need for on side LAN
managers to watch the LAN performance.

• Figure shows a
network where
remote SNMP
devices are
monitored through
an SNMP
management
platform.
• An RMON probe is also placed on Ethernet LAN. RMON groups operate at the MAC layer
while newer RMON groups operate at the network layer and above.
• RFC 1757 defines 10RMON groups where each collects information on variables and sends
it back to central management station for analysis.
• Statistics: Maintains error and Utilization statistics for the specific LAN segments
being monitored by RMON agent. E.g.: CRC/alignment, multicast, broadcast.
• History: Obtains statistical samples such as packet count, error count and utilization
and sore them for lateral retrieval.
• Alarm: Administration control of sampling interval and threshold for any variable
monitored by RMON agent. E.g.: absolute or relative values, rising/falling
thresholds.
• Host: Host traffic measurements such as packets or bytes sent and received, errors
etc.
 • Host Top N: Reporting on Top N Host statistics.
• Traffic Matrix: Stores errors and statistics between source and destination nodes on a
network
• Filter: Provides a filter engine for packet recognition
• Event: Time and data stamped logging and printing of events
• Packet Capture: Buffering criteria for packets that match filter criteria
• Token Ring: Configuration and statistical information on source routing and statistics
on a ring
• RMON 2 provides new groups that operate at the network layer and higher

• Network Layer and Application Layer Host

• Network Layer and Application Layer Matrix
• Protocol Directory
• Protocol distribution
• User defined History
• Address Mapping
• Configuration groups
• Today the application of remote monitoring and control extends from fields such as:
• Smart grid
• Structural health monitoring
• Pipeline sensors
• Patient monitoring
• Desktop/server monitoring

The Common Management Information Service (CMIS) is the service interface specified in ITU. It
defines the service interface that is implemented by the Common Management Information Protocol
(CMIP) as specified in ITU-T Recommendation.
The OSI CMISE management services are presented in figure1.
Q3.Describe the services offered by CMISE

OSI CMISE management services

Management operation services:
• M-CREATE – Create an instance of a managed object
• M-DELETE – Delete an instance of a managed object
• M-GET – Request managed object attributes (for one object or a set of objects)
• M-CANCEL-GET – Cancel an outstanding GET request
• M-SET – Set managed object attributes
• M-ACTION – Request an action to be performed on a managed object

Management notification services:

 • M-EVENT-REPORT

Management association services:

• M-INITIALIZE
• M-TERMINATE
• M-ABORT

Q4. What are the limitations of SNMP v1

ANS:
• SNMP has issues with SNMP request handling and with SNMP trap handling in both agents
and managers.
• In essence, the advisory said what everybody everywhere all ready knew: that SNMPv1 is
insecure and its use can expose system to exploitation.
• It further found specific vulnerabilities for a limited set of SNMP agents that could lead to
DOS attacks, buffer under run exploits, and other nastiness.
• The source of these was found to be in the vendor-specific functions written to parse ASN.1
formatted MIB definitions, but fortunately not in ASN.1 itself.
• These vulnerabilities were immediately addressed by most vendors and by HP through
patches to NNM 6.2 and other HP products.
• SNMP PDU size limitations: This is a concern when using data collections. When there are
many collections configured, there may be excessive fragmentations attributable to NNM
SNMP operations. An implementation of this [SNMP] protocol need not accept messages.
• SNMP may not be suitable for the management of truly large networks because of the
performance limitations of polling.
• SNMP is not well suited for retrieving large volumes of data, such as an entire routing table.

• SNMP traps are unacknowledged & may not be delivered.

• SNMP provides only trivial authentication i.e. it is suitable for monitoring rather than
control.
• SNMP does not support explicit actions i.e., an action is taken by changing a parameter or
setting an object value (indirectly).
• SNMP does not support manager-to-manager communications.

• Limited errors codes

• Limited notifications

• Limited performance

• Transport dependence
 • Lack of hierarchies

• Lack of security

Q5.Compare between CMIS/CMIP and SNMP

Attributes SNMP CMIS/CMIP

Meaning. The Simple Network Common Management
Management Protocol (SNMP), Information Protocol (CMIP) is
which is located in application an interface for network
layer, is part of the management in the Open
Transmission Control Protocol / Systems Interconnection (OSI)
Internet Protocol (TCP/IP) Reference Model.
network architecture
Information Model SMI GDMO
Function SNMP is responsible for Supports information exchange
exchanging data between between network management
network devices stations and management agents
and also supports access to
managed information in the
managed objects.
Protocol GET, SET, TRAP M-GET, M-SET, M-ACTION,
M-CREATE
Services Internet Management, SNMP Telecomm Management, CMIP
uses UDP datagram. uses connection-oriented
sessions
Complexity As a comparison, SNMP only In CMIP, the variables or
employs the operation attributes operations are seen as very
and the notifications structures, complex and sophisticated data
with many attributes.(Trap
messages).
Organization IETF ISO/ITU
Supporting operations IETF ISO/ITU
Supporting operations SNMP only supports 5 CMIP consists of 11 operations
operations.
Security SNMP uses a community name, CMIP is used for its security, as
which is not even encrypted, it supports authorization, access
SNMP uses polling control, and security logs,
CMIP uses reporting.
Q6.Short Note : SNMP
ANS:SNMP:
1. SNMP Stands for Simple Network Management Protocol.
2. It is a framework for managing devices in an internet using the TCP/IP protocol suite.
3. It is an Application Level Protocol.
4. It provides a set of fundamental operations for monitoring and maintaining an internet.
5. SNMP uses the concept of manager and agent.
6. That is, a manager, usually a host, controls and monitors a set of agents, usually routers.

I) SNMP Manager:
1. A manager or management system is a separate entity that is responsible to communicate
with the SNMP agent implemented network devices.
2. This is typically a computer that is used to run one or more network management systems.
3. SNMP Manager’s key functions:
a. Queries agents.
b. Gets responses from agents.
c. Sets variables in agents.
d. Acknowledges asynchronous events from agents.
II) Managed Devices:
1. A managed device or the network element is a part of the network that requires some form
of monitoring and management
2. Example: Routers, Switches, Servers, Workstations, Printers, UPSs, etc.
III) SNMP Agent:
1. The agent is a program that is packaged within the network element.
2. It makes information available to the SNMP manager, when it is queried for.
 3. These agents could be standard (e.g. Net-SNMP) or specific to a vendor (e.g. HP insight
agent)
4. SNMP agent’s key functions:
a. Collects management information about its local environment.
b. Stores and retrieves management information as defined in the MIB.
c. Signals an event to the manager.
d. Acts as a proxy for some non–SNMP manageable network node.
IV) Management Information Base (MIB):
1. Every SNMP agent maintains an information database describing the managed device
parameters.
2. The SNMP manager uses this database to request the agent for specific information and
further translates the information as needed for the Network Management System (NMS).
3. This commonly shared database between the Agent and the Manager is called Management
Information Base (MIB).
4. MIB contains standard set of statistical and control values defined for hardware nodes on a
network.
5. MIB files are the set of questions that a SNMP Manager can ask the agent.
6. Agent collects these data locally and stores it, as defined in the MIB.

Q7.List various event correlation techniques and explain one in detail.

Several correlation techniques are used to isolate and localize fault in networks. All are based on (1)
Detecting and filtering of events (2) Correlating observed events to isolate and localize the fault
either topologically or functionally (3) Identifying the cause of the problem. In all three cases,
different reasoning methods distinguish one technique from another.
Six approaches to correlation techniques:
(1) Rule-based reasoning (2) Model-based reasoning (3) Case-based reasoning (4) Codebook (5)
State transition graph model (6) Finite state machine model
• Rule-Based Reasoning :

i) Rule-based reasoning (RBR) is the earliest form of correlation technique. It is also known
by many other names, including rule-based expert system, expert system, production system,
and blackboard system.
ii) It has a working memory, an inference engine and a knowledge base. The three levels
representing the three components are the data level, control level, and knowledge level,
respectively.
 iii) The knowledge base contains expert knowledge as to (1) definition of a problem in the
network and (2) action that needs to be taken if a particular condition occurs.
iv) The knowledge base information is rule-based in the form of if-then or condition-action,
containing rules that indicate which operations are to be performed when.
v) The working memory contains, as working memory elements, the topological and state
information of the network being monitored.
vi) The working memory recognizes when the network goes into a faulty state.
vii) The inference engine, in cooperation with the knowledge base, compares the current
state with the left side of the rule-base and finds the closest match to output the right side of
the rule. The knowledge base then executes an action on the working memory element.
viii) the rule-based paradigm is interactive among the three components and is iterative.
Several strategies are available for the rule-based paradigm.
ix) A specific strategy is implemented in the inference engine. When a specific rule has been
chosen, an action is performed on the working memory element, which can then initiate
another event. This process continues until the correct state is achieved in the working
memory.
x) Rules are established in the knowledge base from the expertise of people in the field. The
rule is an exact match and the action is very specific.
xi) If the antecedent and action in the rule do not match, the paradigm breaks and it is called
brittle. However, it can be fixed by adding more rules, but doing so increases the database
size and degrades performance, called a knowledge acquisition bottleneck.
xii) As the number of working memory elements grows, memory requirements grow
exponentially. In addition, the action is specific, which can cause unwanted behavior.
xiii) For example, we can define the alarm condition for packet loss as follows:
If packet loss < 10% alarm green
If packet loss => 10% < 15% alarm yellow
If packet loss => 15% alarm red
xiv) The left side conditions are the working memory elements, which if detected would
execute the appropriate rule defined in the rule-base
xv) This action could cause the alarm condition to flip back and forth in boundary cases. An
application of fuzzy logic is used to remedy this problem, but it is difficult to implement.
• An RBR-Based Correlation Example :

i) Figure2 is used here to illustrate an implementation of RBR. It shows a four-layer

network.
ii) Backbone router A is linked to router B. Hub C is connected to router B and has four
servers, D1-D4, in its LAN.
 iii) Without a correlation engine, failure in the interface of router A will generate an alarm.
This fault then propagates to router B, hub C, and finally to servers D1 -D4, Time delay is
involved in alarm generation.
iv) In general, propagation of faults and the time delay associated with them need to be fully
recognized in fault management.

Fig2: An RBR-Based
Correlation Example
Scenario
v) Four correlation rules
are specified in Figure3.
vi) Rule 0 has no
associated condition
with, but rules 1-3 are
conditional. To allow for
propagation time, a correlation window of 20 seconds is set.

Q 8.State & Explain service Architecture of TMN.

ANS:TMN layered architecture:
The TMN services are grouped and presented as TMN layered architecture.
ii. The lowest layer is the network element layer comprising network elements such as switches,
routers, bridges, transmission facilities, etc.
iii. The next layer, the network element management layer, which manages the network elements.
iv. The third layer is the network management layer, which manages the network. The network
management functions in this layer include bandwidth, performance, and quality of service, end-to-
end flow control, and network congestion control.
v. The network element layer and network element management layer is vendor dependent, whereas
the network management layer is not.
vi. The service management layer is concerned with managing the services provided by a network
service provider to customers or to other network service providers.
vii. They include services such as billing, order processing, complaints, and trouble ticket handling.
The top layer is the business management layer. It is concerned with managing the operations of a
communications business, including fiscal considerations, human resource needs, project
management, and customer needs and satisfaction.
viii. The TMN reference point between the various service layers is q3. It is the standard interface
between the operations system, network element, and mediation functions.
ix. TMN management services are classified by OSI system management functional area. These
areas are the five OSI application functions, configuration management, fault management,
performance management, security management, and accounting management.
x. The TMN management services and the system management functional areas are presented in
Figure2.

xi. The four TMN management services—business, service, network, and element—are at the top of
the hierarchy. They invoke the system management functions defined as the five components
comprising the system management functional areas: configuration, fault, performance, security,
and accounting.
xii. The management applications in the system functional areas perform either system management
functions or TMN functions. The TMN function blocks OSF, WSE NEE ME and QAF consist of
TMN functional components such as the NMF and MIB. The data communication function (DCF),
although not part of the TMN function blocks, is included for completeness.
xiii. The system management functions include object management and alarm management. we
could have embedded the system management functions in TMN function blocks and TMN
functional components, but we show them separately in order to present a non-OSI environment.
xiv. the OSI primitive services of M-GET, M-SET, and so on. Equivalent SNMP services are GET-
REQUEST, SET-REQUEST, and so on. The TMN environment is a distributed environment.
xv. The applications communicate remotely with the communication transport service by means of
the RPC. In the OSI model, the RPC is accomplished with ROSE and ACSE. The former does the
remote operation and the latter establishes and releases the application association. In the SNMP
management model, the remote
operation is accomplished by
using the RPC and TCP/IP.

Q 9.Explain with neat

diagram SNMPv1
PDU formats.
ANS:
SNMPvl PDU Format:
i. The SNMPv1 PDU is relatively simple in format as figure shows.
ii. The SNMPv1 PDU travels in UDP that, in turn, is transported in IP.
iii. The Request/Response PDU2 simply has a Version field, a community string, a PDU Type
indicator, the Request ID, Error Status, Error Index, and the Variable Bindings.
iv. The Trap PDU begins in a similar fashion to the Request/Response PDU in that it has Version
field, a Community String, and a PDU Type indicator, but from this point until the Variable
Bindings, the PDU structure is somewhat different.
v. For the Trap PDU, we then have an Enterprise field, an Agent Address field, Generic and
Enterprise Specific trap indicators, potentially some Padding, and a Time Stamp.
vi. Standard SNMP Request/Response PDUs use UDP Port 161.
vii. SNMP Trap PDUs use UDP Port 162
viii. SNMPvl is essentially a simple request-response protocol. Each SNMPv1 message contains a
Message Header and a Protocol Data Unit (PDU).
ix. The message header contains a version field and a community name. The version identifies the
version number of the protocol (e.g. for RFC 1157, version-1 is used).
x. An SNMP community refers to a pairing of an SNMP agent with some arbitrary set of SNMP
application entities.
xi. Thus, the community name in the SNMP message helps in defining an access environment for
the set of NMSs using that community name.
xii. Five different types of SNMP PDUs are defined, which includeGetRequest, GetNextRequest,
GetResponse, SetRequest and Trap.
The details of the PDUs are as follows:
• GetRequest:

i. This PDU is generated by a protocol entity only at the behest of its SNMP application entity (this
also applies for GetNextRequest and SetRequest PDU).
ii. The error-status and error-index in GetRequest PDU is always set to 0. This is because error
codes are generated only for a response, not for a request.
iii. In case no error occurs, the receiver of the GetRequest PDU responds back with GetResponse
PDU, which contains the name and the value corresponding to each object in the received variable
binding list.
• GetNextRequest:

i. This PDU is identical to GetRequest PDU, except that the PDU type is different.
ii. In case no error occurs, the receiver of the GetNextRequest PDU responds back with a
GetResponse PDU, which contains the name and the value of the immediate successor
corresponding to each object in the received variable binding list.
iii. GetNextRequest is useful in traversing a conceptual table of objects maintained in an MIB.
• GetResponse:

GetResponse PDU is generated as a response to a GetRequest, GetNextRequest or SetRequest

PDU.
• SetRequest:

i. This PDU is used to set values of object instances within an agent. In case no error occurs, then
for each object named in the variable binding list of the received message, the corresponding value
is assigned to the variable.
ii. A GetResponse PDU is also generated to inform the sender of the results of the SetRequest.

SNMPvl PDU Format

• Trap:

i. Traps are unsolicited message sent by the agents to the NMS. They are sent asynchronously to
inform the NMS of the occurrence of some event. Trap PDUs do not elicit a response from the
receiver.
ii. Except the Trap PDU, the message format for the remaining PDUs is identical. Each PDU
contains the following fields:
• Request-ID: This field is used to distinguish between multiple outstanding requests i.e. it is
used to associate an incoming response with an outstanding request.
• Error status: A non-zero value of this field indicates that an exception condition has
occurred.
• Error index: In case of exception condition, this field identifies the variable in the list that
caused the exception.

Q10.Discuss M3 interface in ATM network management.

M3 Interface: Customer Network Management of Public Networks
The M3 management interface is between the private NMS and the public NMS. It allows
customers to monitor and configure their portions of the public ATM network.
a customer would typically interact with the public NMS via the carrier management system.
Two classes of M3 requirements are shown: status and configuration monitoring (class I), and
virtual configuration control (class II).
• Class I requirements are those that a public NMS offers to the customer, monitoring and
management of configuration, fault, and performance of a specific customer's portion of a
public ATM network.
• This service is offered only for a permanent virtual circuit (PVC) configuration.

• Examples of this service are (1) retrieving performance and configuration information for a
UNI link and (2) public NMS reporting of a UNI link failure via an alarm or trap message to
the user NMS.
• Class II service provides greater capability to the user, who can request the public NMS to
add, delete, or change virtual connections between pairs of the customer's UNIs.
• An example would be a customer wanting to establish a new virtual path or increase the
number of virtual circuits in a given virtual path.
• A customer network management (CNM) manages both private and public ATM networks.
A CNM agent residing in the public ATM network provides the M3 service.
• The service is limited to the portion of the public service provider's network that the user's
circuit traverses. If the user's circuit traverses multiple service providers, a separate interface
with each provider is needed.
• The CNM sends requests to the carrier management system (see Figure1), which acts as an
agent to the CNM. The carrier management system then invokes the request on the network
elements or other NMS and returns the responses to CNM.
M5 Interface:
• The final interface M5 is between the NMSs of two service providers. It is most complicated
of all interfaces.
• M5 supports interactions and exchange of management information between any two public
networks.
• M5 supports interactions and exchange of management information between any two public
networks.
For M1, M2, M4 Refer (Discuss Ml, M2 and M4 interface in ATM network management) asked in
May 2015.

Q.11 Differentiate RMON and SNMP.

Attributes SNMP
Meaning The Simple Network
Management Protocol (SNMP),
which is located in application
layer, is part of the
Transmission Control Protocol /
Internet Protocol (TCP/IP)
network architecture
Information Model SMI
Function SNMP is responsible for
exchanging data between
network devices
Protocol GET, SET, TRAP p
Services Internet Management, SNMP
uses UDP datagrams
Complexity SNMP only employs the
operation attributes and the
notifications
Organization IETF
Supporting operations SNMP only supports 5
operations
Security SNMP uses a community name, Offer security features like
which is not even encrypted, antivirus and backup solutions
SNMP uses polling
Access In terms of data access, SNMP
retrieves individual items of
information also SNMP
Uses SNMP used in Local Area
Networks (LANs), SNMP is
widely used because of its
Year 1998(ver.3) 1
RMON
Remote Monitoring (RMON) is
a standard monitoring
specification that enables
various network monitors and
console systems to exchange
network monitoring data
Management Information Base
(MIB)
RMON provides standard
information that a network
administrator can use to
monitor, analyze, and
troubleshoot a group of
distributed LANs
rotocolDir, protocolDist,
addressMap, nlHost, nlMatrix,
alHost, alMatrix, userHistory,
probeConfig
MIB module for SNMP that
describes objects that permit
advanced network management
capabilities
Complex nature of the available
functions in the RMON MIB
modules
IETF
RMON1 MIB consists of ten
groups, and RMON2 MIB adds
ten more groups
Perform analysis and collect
statistical information on the
data collected on a subnet,
freeing the managing station
from this task
simplicity To monitor and
troubleshoot LANs
993 (RFC 1513), 1995 (RFC
1757), 1997 (RFC 2021)
Q 12 M1 M2 M3 M4 and M5 ATM interfaces
• The Network Management Working Group of the ATM Forum has developed an end-to-end
generic management model that encompasses private and public networks and lays out standards
for interworking between them.
• The model defines gateways between SNMP and CMIP systems, and between standards-based and
proprietary systems.
• Five key management interfaces are defined in this model; they are labelled M1 through M5
• M1 and M2 are the interfaces between a private NMS and either an end user or a private network,
respectively. The end user can be a workstation, ATM switch, or any ATM device. A private ATM
network is an enterprise network.
• A private network management system can access its own network-related information in a public
network via an M3 interface to the public network management system.
• The public NMS responds to the private NMS via the M3 interface with the relevant information
or takes the action requested.
• The M4 interface is between the public NMS and the public network. The final interface, M5, is
between the NMSs of two service providers. The ATM Forum has not yet specified this interface.
• The ATM framework defines five different M-interfaces for management see Figure .

. (1) M1/M2 Interface:

Management of ATM
Network Element
• The M1 interface is
between an SNMP
management system and
an SNMP agent in an ATM device, as shown in Figure.

• Four entities,
ifInNUcastPkts,
ifOutNUcastPkts,
ifOutQLen, and ifspecific
have been depricated.
• Interim Local Management
Interface (ILMI), which is an
implementation of the M1 /M2 interfaces, enables the exchange of status, configuration, accounting
and control information between any two ATM devices - such as two ATM switches - across a user-
to-network interface (UNI).
• For ILMI to function, every ATM switch or network terminator and every ATM network that
deploys a public or private network UNI must be equipped with a UNI Management Entity (UME)
which supports an ILMI MIB.
• Two adjacent (or peer) UMEs can communicate using the common attributes provided by the
ILMI.
(2) M3 Interface: Customer Network Management of Public Networks.
• The Customer Network Management (CNM) interface defines the interaction taking place
between the customer and carrier management systems in order to give the customer a view into the
carrier’s network.
• Ultimately, carriers plan to extend their CNM offerings so that network managers will have real-
time control over the services they use.
• Currently, the most characteristic capabilities of CNM for ATM networks are the performance of
tests, the reception of event notifications, the definition of traps, the administration and generation
of trouble reports, the support of security features, and the retrieval of configuration, usage, and
performance information from the M3 MIB that defines objects for the customer portion of a public
network.
• The CNM applications may regarded as an example of the classical Manager/Agent model.
• A CNM application is acting as a manager that communicates with a CNM agent residing in an
ATM network.
• The CNM agent is capable of supplying the required management information and carrying out
management tasks related to the managed resources.
• It communicates with the carrier’s Network Management System (NMS) which comprises the
whole set of management functions supported by the carrier. Therefore, the CNM agent usually
supports only the portion of these management functions that pertain to the service provided to the
customer. The interfacing between a CNM agent and a NMS should be based in open standards, in
order to ensure that the CNM agent is flexible
(3) M4 Interface: Public Network Management
• The M4 interface specifies requirements for managing individual network elements.
• It defines a protocol-independent MIB that identifies the information items to be exchanged
between ATM devices and the system that manages them.
• This MIB is a logical information tree, consisting of managed entities, that provides a framework
for the development of protocol-specific MIBs, such as those based on SNMP or CMIP, that would
potentially enable the management of ATM networks consisting of diverse devices of heterogeneous
nature.
• Another aspect of the M4 interface, revealing its potential for integrated network management, is
its relationship with TMN.
• Specifically, M4 addresses the interactions between the lower three TMN layers, namely the
Element Layer, the Element Management Layer and the Network Management Layer.
• Furthermore, the M4 specification addresses almost every area of ATM management (i.e., fault,
performance, configuration, and security management). Undeniably, it is a complete specification
that makes 8 provisions for managing both the current and the future public
(4) M5 Interface:
• The Final Interface M5 is between the NMSs of two service providers. It is most complicated of
all interfaces.
• M5 supports interaction & exchange of management information between any two public
networks.
Types Interaction Purpose Services Protocol
M1 CPE / NMS Management of SNMP
user terminal
equipment
M2 P-Switch / NMS Management of Similar to M4 SNMP
the ATM private
network
M3 NMS / NML Management Public network SNMP
interaction configuration and
between private status gathering.,
and public ii.,Add & deletion
domains of pre-authorized
VCs., iii.new
connection request
M4 NML / EML Management of Fault and CMIP,(Q3),or
or,EML / NE NE's and EMLs performance SNMP
management,
ii.,Configuration
and circuit
provisioning,
iii.,accounting
M5 NML / NML Management Cross public No standard yet
interaction network
between different management
owned public
domains
ILMI Private/public Service control Service activation, ILMI - SNMP
service assurance
(maintenance),
usage metering
(performance,
billing)