3 - SNMPv1

Download as pdf or txt
Download as pdf or txt
You are on page 1of 20

MRS.

RANIA AZAD
DEPARTMENT OF COMPUTER NETWORK
TECHNICAL COLLEGE OF INFORMATICS
SULAIMANI POLYTECHNIC UNIVERSITY
RANIA.AZAD@SPU.EDU.IQ

CHAPTER 03: SNMPV1


PART 1
YOU WILL LEARN

¡ SNMP community

¡ SNMP Community Profile

¡ SNMP PDU structures for each SNMP Message


SNMP TWO-TIER ORGANIZATION
MODEL

SNMP SNMP SNMP


Manager Manager Manager

SNMPAgent Network Agent

Network Network
Element Element

Multiple SNMP managers communicating with a single SNMP agent or one Manager communicate with
Multiple Agents
SNMP COMMUNITY

¡ SNMP Community: Pairing of two application entities


¡ Relationship between an Agent and Managers.

¡ SNMP Entities:
• SNMP application entities
- Reside in management stations and network elements (Manager
and agent)

• SNMP protocol entities


- PDU
SNMP COMMUNITY
• Community name
¡ Type: String of octets
¡ Used to validate the SNMP messages (Sent with each
request/answer)
¡ plaintext passwords-like.
¡ Default community name: “public”.
¡ Not secured in SNMPv1 - no encryption

• Two applications in the same community can communicate with each


other
SNMP COMMUNITY
COMMUNITY PROFILE
¡ Community profile = MIB view + access mode
¡ SNMP MIB view
¡ An agent is programmed to view only a subset of managed objects of a
network element
¡ SNMP Access mode
¡ Each community name is assigned an access mode: read-only and read-write
¡ 4 access modes (privileges) on each object :
¡ not-accessible,
¡ read-only,
¡ write-only,
¡ and read-write.
COMMUNITY PROFILE
ACCESS POLICY
¡ Access Policy = SNMP community +
SNMP community profile
¡ SNMP access policy is an Administration
model
¡ Manager manages Community profile 1
and 2 using :
¡ Agent 1: Cisco Router
¡ Agent 2: HP Printer
¡ Manager has total privilege on monitoring
both Cisco Router and HP Printer
Manager 1
(Community 1)

Community 1

Community Profile 1
Agent 1
Community Profile 2 Agent 2

Manager 3
(Community 1, Community 2)

Community 2

Community Profile 3
Agent 3
Community Profile 4 Agent 4

Manager 2
(Community 2)
PROTOCOL ENTITIES

¡ Protocol entities support application entities


¡ Message encapsulated and transmitted
SNMP MESSAGE

¡ SNMP Message consist of:


Message ::=
¡ Version Number: SEQUENCE {
¡ Describes the SNMP version (3 versions) version INTEGER {version-1(0)},
community OCTET STRING,
¡ Ensuring compatibility between versions during the data ANY
communications }

¡ SNMPv1 = 0

¡ Community String
¡ Protocol Data Unit: the body of the message.

version community data


SET/GET PDU
PDU- request- error- error-
type
variable-bindings
id status index

¡ PDU type
¡ Is an integer value that indicates the PDU type (message
type)
¡ Request ID:
¡ Unique ID/number of each request.
¡ track a message and indicate loss of a message (using
timeout)
¡ Match a request and the corresponding response.
ERROR-STATUS AND ERROR-INDEX
¡ error-status:
¡ indicate the type of error
¡ Always zero in a request
¡ error-index
¡ indicate the first variable with
error (position of the first
error in the list of variables)
¡ If there are more than one error
in the variable-bindings?
¡ Only the first error is indicated.
VARIABLE BINDING
var-bind 1 var-bind 2 var-bind n
name value name value ... name value

¡ Variable bindings
¡ A set of Object name-value
¡ Object Name: The numeric OID of the MIB object
¡ Object Value:
¡ Get Request: empty value
¡ Set Request : the value of the object is placed

¡ Adv: one request to get all values in one response listing all values
SNMPV1 TRAP PDU

PDU- Agent Generic Specific Time


type
Entreprise
Address Trap Type Trap Type Stamp
variable-bindings

¡ PDU Type = 4
¡ Enterprise
¡ Indicate the source of the trap (sysObjectID)
¡ Agent address
¡ Indicate the IP address of a trap source.
¡ Generic trap:
¡ Indicates the type of the trap : 7 types.
¡ Specific trap
¡ Enterprise specific trap.
¡ Time stamp:
¡ Elapsed time since last re-initialization
¡ Time elapsed between the last initialization of the network entity and the generation of the trap.
TRAP TYPE

Generic Trap Type Description (brief)


coldStart(0) Sending protocol entity is reinitializing itself;
agent's configuration or protocol entity
https://oidref.com/
implementation may be altered
warmStart(1) Sending protocol entity is reinitializing itself;
agent configuration or protocol entity
implementation not altered
linkDown(2) Failure of one of the communication links
linkUp(3) One of the links has come up
authenticationFailure(4) Authentication failure
egpNeighborLoss(5) Loss of EGP neighbor
enterpriseSpecific(6) Enterprise-specific trap
GENERIC TRAP EXAMPLE
ENTERPRISE TRAP EXAMPLE
QUESTIONS?

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