Application Laye, 4 it SL Network Management 6.18 SIP SNMP) Protoco! p protocol itself. It defines hoy, re actual SNM jon is exchangs ment stations: operations define the various how they are created and use pings describe how SNMP can be derlying internet works, such ag - thsi ed between SNMP agents any network manage! the SNMP protocol ge messages 270 SNMP transport MPF used over various Un ‘rcpAP, IPX and others. It is simply an application program that has a client on the manager and a server onthe age: SNMP alos manager to perform following three important tasks: 1, Retrieve any information from an agent database ieve variables defined by the agent) (ie. rte 2, Store/update the value in an agent database, 43. Receive alerts from agents in case of problems. PDUs {Protocol Data Units) : ‘SNMP version 3 define 8 message types for achieving the objectives mentioned above. Five of them are as shown in Table 5.18.1. Note that all these messages are exchanged as simple PDUs (Protocol Data Units) or simple UDP packets between manager and agent. = Since these messages are simple request-response pairs, they do nat require any connection/session to be established. Therefore, TCP is not requited in this case. Table 5.18.1: SNMP messages Description The manager (client) sends this message to the agent (server) 10 request for the value of an agent variable. GetNextRequest | If the agent variables are in the form of a table, the manager cannot Use the GetRequest message, as it does ot know where the current table pointer is located. This message |S Used in such cases. GetResponse | The agent replies to a managers GetRequest or GetNextRequest messages using this message. TNS message contains the values of the variables requested for by 1° manager. = —__————— © Scanned with OKEN Scanneri J ncn (Comp, Som SMSETED a Description ~ _Diferent elds in POU format areas follows Mes The manager can ask the agent | 4. POU type: SetReqves! store a particular value in an agont pein sing lt merece This field is used for defining the type of POU. There are ferent types of PDUs in SNMP. They are as tsted in The agent can report an errorerany | _8.lferent types of POUS in SNMP, They oe a nea Tp such evento the manager using thie || Table 5.182 message Table 5.10.2: Different types of SNMP PDUs ows five SNMP messages. a Tag rig S181 stows fie SNMP messages, Type attiex) | Type fey As tet-rosponse GetRequest | Ay GatsuikRequest GetNedRequest | A, InformRequest Got - next -requost = “3 = upp Response | As Trepiswwrva) | A, uP | aor-msponse _ | UOF pot ‘1 SetRequest | As Report A 162 |" get -moquost 2 Request ID: Trap SNMP, agent (6-723) Fig. 5.18.1 : Five SNMP messages SNMP manager InformRequest : , The InformRequest PDU is not shown in Fig, 5.18.1, but this PDU is sent from one manager to another remote ‘manager, in order to obtain the values of some vatigbles from agents under the control of remote ‘manager. The remote manager will send @ Response PDU as a response. Report : ‘The report POU is also not shown in Fig. 5.18.1. But itis designed to report some type of errors between ‘managers, However itis not in use yet. 5.18.1 Format : SNMP POU ———_____—-+4 eT Requost Eror | varbind 10 Index st Fig 5.18.2 shows the format of eight SNMP PDUs. ~ The contents of this field are same as the sequence number used by the manager in a Request PDU. ~The agent repeats the same number in its fesponse, Hence Request ID field is used for matching a request with response. 3. Error status : — This is an integer which is included only in the response PDUs. It is used to indicate the type of errors reported by the agent. ~~ The value of error status in the request PDUs is always zero. Different types of possible errors are 2s given in Table 5.183, Table 5.18.3: Types of errors Status. | Error Meaning o°_| Noerror There is no error. 1 | tooBig Response too big to fit in one. message. 2__| noSuchName_| No variable exists. 3° | badValue Invalid value has been given for storage. 4 | readonly Can't modify the value. 5 _| gener Other errors. 4. Non-tepeaters : — The non-repeaters field is used only in field in the 7 GetBulkRequest. The empty error status rete va arate as request PDUs is replaced by non-repeaters (6-1993) Fig. .18.2: SNMP PDU format contents. : SF Techrnouietgé Finn 7 pupientie © Scanned with OKEN Scanner5 ‘AGN (Comp. ‘Sem, SMSBTE Error indox : the evnor Index Is an offset, tts duty fs to tell the manager about the variable causing the error. 6. Max-ropetition : the Similar tothe —non-tepeaters field max-repetition field fs also used only in GetBulkRequest and it replaces the empty error Index field in the request Pous. 7. VarBind tist = This field id a set of variables. The values of these variables correspond to those values the manager wants to retrieve or set. ~ These values for GetRequest and GetNextRequest are null. Messages : — In SNMP only a POU is not sent, instead the POU is embedded in a message. A message is made of four elements arranged sequentially. These four elements are : Version, Global Data, Security Parameters and Scope PDU as shown in Fig. 5.18.3 Variable Variable Value { 1 Example : GaiRequest POU (6-2208 Fig. 5.18.3 : SNMP message = Out of these four elements, the version and SecurityParameters elements are simple data type and the remaining are sequences, — The four elements are as given below : Version : This field is used to define the version of the SNMP and 1 is an INTEGER data type field. The current version of SNMP is 3. © Scanned with OKEN Scanner36 2. 3. 4. Application Layer GlobalData : ‘As shown in Fig. 5.18.3, this field is made of fou, elements. of simple data type arranged in g sequential manner. These four elements are as follows :1D, MaxSize, Flags and SecurityModel, SecurityParameter : This element is in the form of a very complex sequence. The complexity is dependent on the type of security provision in SNMPV3. ScopePDU : This element of SNMPV3 is made of two simple data types and the actual PDU. In Fig. 5.18.3 the GetRequest PDU has been shown as an example. The VarBindList sequence contains one or more sequences called VarBind, and each VarBind Consists of two simple data elements namely : Variable and Value. © Scanned with OKEN Scanner