Scribd
Upload
9 views2 pages

SNMP Protocol

Uploaded by

preenu mittan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
9 views2 pages

SNMP Protocol

Uploaded by

preenu mittan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Snmp:- (simple network management protocol.

)
Defined by IETF(internet engineering task force) & used to manage network. Internet standard protocol
for collecting & organizing information about managed devices on IP N/W.

Supported by most of the devices such as Hub,Switch,Router,Bridge etc.

Components:-

1. Manager:- centralized system used to monitor n/w.

An SNMP manager is a computer that is configured to poll SNMP agent for information. The
management component, when only discussing its core functionality, is actually a lot less
complex than the client configuration, because the management component simply requests
data.

The manager can be any machine that can send query requests to SNMP agents with the correct
credentials. Sometimes, this is implemented as part of a monitoring suite, while other times this
is an administrator using some simple utilities to craft a quick request.

Almost all of the commands defined in the SNMP protocol (we will go over these in detail later)
are designed to be sent by a manager component. These
include GetRequest, GetNextRequest, GetBulkRequest, SetRequest, InformRequest,
and Response. In addition to these, a manager is also designed to respond to Trap,
and Response messages.

2. Agent:- s/w management s/w module installed on managed device (Router,Hub etc).

SNMP agents do the bulk of the work. They are responsible for gathering information about the
local system and storing them in a format that can be queried.updating a database called the
“management information base”, or MIB.

The MIB is a hierarchical, pre-defined structure that stores information that can be queried or
set. This is available to well-formed SNMP requests originating from a host that has
authenticated with the correct credentials (an SNMP manager).

The agent computer configures which managers should have access to its information. It can
also act as an intermediary to report information on devices it can connect to that are not
configured for SNMP traffic. This provides a lot of flexibility in getting your components online
and SNMP accessible.

SNMP agents respond to most of the commands defined by the protocol. These
include GetRequest, GetNextRequest, GetBulkRequest, SetRequest and InformRequest. In
addition, an agent is designed to send Trap messages.

3. Management Information Base:- consists information of resources that are to be managed.


The MIB is a database that follows a standard that the manager and agents adhere to. It is a
hierarchical structure that, in many areas, is globally standardized, but also flexible enough to
allow vendor-specific additions.

The MIB structure is best understood as a top-down hierarchical tree. Each branch that forks off
is labeled with both an identifying number (starting with 1) and an identifying string that are
unique for that level of the hierarchy. You can use the strings and numbers interchangeably.

To refer to a specific node of the tree, you must trace the path from the unnamed root of the
tree to the node in question. The lineage of its parent IDs (numbers or strings) are strung
together, starting with the most general, to form an address. Each junction in the hierarchy is
represented by a dot in this notation, so that the address ends up being a series of ID strings or
numbers separated by dots. This entire address is known as an object identifier, or OID.

SNMP message:-

1. GetRequest:- manager sends to request data from agent.


A Get message is sent by a manager to an agent to request the value of a specific OID. This
request is answered with a Response message that is sent back to the manager with the data.

2. GetNextRequest:- sent to discover what data is available on Agent.


A GetNext message allows a manager to request the next sequential object in the MIB. This is a
way that you can traverse the structure of the MIB without worrying about what OIDs to query.

3. GetBulkRequest:- used to retrieve large data at once by manager from Agent.


This manager to agent request functions as if multiple GetNext requests were made. The reply
back to the manager will contain as much data as possible (within the constraints set by the
request) as the packet allows.
4. SetRequest:- used by manager to set the value of object on agent.
A Set message is sent by a manager to an agent in order to change the value held by a variable
on the agent. This can be used to control configuration information or otherwise modify the
state of remote hosts. This is the only write operation defined by the protocol.

5. Response:- sent by agent to manager upon a request from manager.


This message, sent by an agent, is used to send any requested information back to the manager.
It serves as both a transport for the data requested, as well as an acknowledgement of receipt of
the request. If the requested data cannot be returned, the response contains error fields that
can be set with further information. A response message must be returned for any of the above
requests, as well as Inform messages.

6. Trap:- send by agent being requested by manager. sent when fault occur. A trap message is
generally sent by an agent to a manager. Traps are asynchronous notifications in that they are
unsolicited by the manager receiving them. They are mainly used by agents to inform managers
of events that are happening on their managed devices.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy