|
|
3.2.3. Operations Supported on Management Information
Connected: An Internet Encyclopedia
3.2.3. Operations Supported on Management Information
Up:
Connected: An Internet Encyclopedia
Up:
Requests For Comments
Up:
RFC 1157
Up:
3. The SNMP Architecture
Up:
3.2. Elements of the Architecture
Prev: 3.2.2. Representation of Management Information
Next: 3.2.4. Form and Meaning of Protocol Exchanges
3.2.3. Operations Supported on Management Information
3.2.3. Operations Supported on Management Information
The SNMP models all management agent functions as alterations or
inspections of variables. Thus, a protocol entity on a logically
remote host (possibly the network element itself) interacts with the
management agent resident on the network element in order to retrieve
(get) or alter (set) variables. This strategy has at least two
positive consequences:
- It has the effect of limiting the number of essential
management functions realized by the management agent to
two: one operation to assign a value to a specified
configuration or other parameter and another to retrieve
such a value.
- A second effect of this decision is to avoid introducing
into the protocol definition support for imperative
management commands: the number of such commands is in
practice ever-increasing, and the semantics of such
commands are in general arbitrarily complex.
The strategy implicit in the SNMP is that the monitoring of network
state at any significant level of detail is accomplished primarily by
polling for appropriate information on the part of the monitoring
center(s). A limited number of unsolicited messages (traps) guide
the timing and focus of the polling. Limiting the number of
unsolicited messages is consistent with the goal of simplicity and
minimizing the amount of traffic generated by the network management
function.
The exclusion of imperative commands from the set of explicitly
supported management functions is unlikely to preclude any desirable
management agent operation. Currently, most commands are requests
either to set the value of some parameter or to retrieve such a
value, and the function of the few imperative commands currently
supported is easily accommodated in an asynchronous mode by this
management model. In this scheme, an imperative command might be
realized as the setting of a parameter value that subsequently
triggers the desired action. For example, rather than implementing a
"reboot command," this action might be invoked by simply setting a
parameter indicating the number of seconds until system reboot.
Next: 3.2.4. Form and Meaning of Protocol Exchanges
Connected: An Internet Encyclopedia
3.2.3. Operations Supported on Management Information
|
|
|
 |

|
 |
|
Protect yourself from cyberstalkers, identity thieves, and those who would snoop on you.
| |
Stop spam from invading your inbox without losing the mail you want. We give you more control over your e-mail than any other service.
| |
Block popups, ads, and malicious scripts while you surf the net through our anonymous proxies.
| |
Participate in Usenet, host your web files, easily send anonymous messages, and more, much more.
| |
All private, all encrypted, all secure, all in an easy to use service, and all for only $5.95 a month!
|
|
Service Details
|
|
 |
|