GeoDesy FSO Giga Next series - Manual (Page 51)

GeoDesy Kft.
H-1116 Budapest, Kondorfa str. 6
SNMP itself is a simple request/response protocol. NMSs can send multiple
requests without receiving a response. Six SNMP operations are defined:
Get --
Allows the NMS to retrieve an object instance from the agent.
GetNext -- Allows the NMS to retrieve the next object insta
within an agent. In SNMPv1, when an NMS wants to retrieve all elements of a table
from an agent, it initiates a Get operation, followed by a series of GetNext
operations.
GetBulk --
New for SNMPv2. The GetBulk operation was added
acquire large amounts of related information without initiating repeated get
operations. GetBulk was designed to virtually eliminate the need for GetNext
operations.
Set --
Allows the NMS to set values for object instances within an agent.
Trap -- Used by the agent to asynchronously Inform the NMS of some event. The
SNMPv2 trap message is designed to replace the SNMPv1 trap message.
Inform --
New for SNMPv2. The Inform
send trap information to another.
SNMPv1 messages (packets) contain two parts
and a community name. The second part contains the actual SNMP protocol data
unit (PDU) specifying the operation to be performed ("Get," "Set," and so on) and the
object instances involved in the operation.
format.
Figure 3: SNMP v1 Message Format
* Trap messages have a slightly different format; for information on this format,
consult the appropriate SNMP specification.
The version field is used to ensure that all network elements are running software
based on the same SNMP version. The communit
environment for a set of NMSs using that community name. NMSs within the
community can be said to exist within the same administrative domain. Because
Telefon: 06
. 6-8.
E-mail: info@geodesy
http://www.
51
Horváth Holding
Investment PLC.
ple request/response protocol. NMSs can send multiple
requests without receiving a response. Six SNMP operations are defined:
Allows the NMS to retrieve an object instance from the agent.
Allows the NMS to retrieve the next object instance from a table or list
within an agent. In SNMPv1, when an NMS wants to retrieve all elements of a table
from an agent, it initiates a Get operation, followed by a series of GetNext
New for SNMPv2. The GetBulk operation was added to make it easier to
acquire large amounts of related information without initiating repeated get
operations. GetBulk was designed to virtually eliminate the need for GetNext
Allows the NMS to set values for object instances within an agent.
Used by the agent to asynchronously Inform the NMS of some event. The
SNMPv2 trap message is designed to replace the SNMPv1 trap message.
New for SNMPv2. The Inform operation was added to allow one NMS to
send trap information to another.
SNMPv1 messages (packets) contain two parts1. The first part contains a
. The second part contains the actual SNMP protocol data
he operation to be performed ("Get," "Set," and so on) and the
object instances involved in the operation. Figure 3 illustrates the SNMPv1 message
Figure 3: SNMP v1 Message Format
* Trap messages have a slightly different format; for information on this format,
consult the appropriate SNMP specification.
The version field is used to ensure that all network elements are running software
based on the same SNMP version. The community name assigns an access
environment for a set of NMSs using that community name. NMSs within the
community can be said to exist within the same administrative domain. Because
Telefon: 06-1-481-2050
Fax.: 06-1-481-2049
[email protected]
http://www.geodesy-fso.com
Horváth Holding
Investment PLC.
ple request/response protocol. NMSs can send multiple
requests without receiving a response. Six SNMP operations are defined:
Allows the NMS to retrieve an object instance from the agent.
nce from a table or list
within an agent. In SNMPv1, when an NMS wants to retrieve all elements of a table
from an agent, it initiates a Get operation, followed by a series of GetNext
to make it easier to
acquire large amounts of related information without initiating repeated get-next
operations. GetBulk was designed to virtually eliminate the need for GetNext
Allows the NMS to set values for object instances within an agent.
Used by the agent to asynchronously Inform the NMS of some event. The
SNMPv2 trap message is designed to replace the SNMPv1 trap message.
operation was added to allow one NMS to
. The first part contains a version
. The second part contains the actual SNMP protocol data
he operation to be performed ("Get," "Set," and so on) and the
illustrates the SNMPv1 message
* Trap messages have a slightly different format; for information on this format,
The version field is used to ensure that all network elements are running software
y name assigns an access
environment for a set of NMSs using that community name. NMSs within the
community can be said to exist within the same administrative domain. Because