356
V6100 and V7122 User Guide
Trap - A message generated asynchronously by network devices. It is an unsolicited
message from an agent to the manager.
Each of these message types fulfills a particular requirement of Network Managers:
Get Request - Specific values can be fetched via the ‘get’ request to determine the
performance and state of the device. Typically, many different values and parameters
can be determined via SNMP without the overhead associated with logging into the
device, or establishing a TCP connection with the device.
Get Next Request - Enables the SNMP standard network managers to ‘walk’ through all
SNMP values of a device (via the ‘get-next’ request) to determine all names and values
that an operant device supports. This is accomplished by beginning with the first SNMP
object to be fetched, fetching the next name with a ‘get-next’, and repeating this
operation.
Set Request - The SNMP standard provides a method of effecting an action associated
with a device (via the ‘set’ request) to accomplish activities such as disabling interfaces,
disconnecting users, clearing registers, etc. This provides a way of configuring and
controlling network devices via SNMP.
Trap Message - The SNMP standard furnishes a mechanism by which devices can
‘reach out’ to a Network Manager on their own (via a ‘trap’ message) to notify or alert the
manager of a problem with the device. This typically requires each device on the network
to be configured to issue SNMP traps to one or more network devices that are awaiting
these traps.
The above message types are all encoded into messages referred to as Protocol Data Units
(PDUs) that are interchanged between SNMP devices.
SNMP MIB Objects
The SNMP MIB is arranged in a tree-structured fashion, similar in many ways to a disk
directory structure of files. The top level SNMP branch begins with the ISO ‘internet’
directory, which contains four main branches:
The ‘mgmt’ SNMP branch - Contains the standard SNMP objects usually supported (at
least in part) by all network devices.
The ‘private’ SNMP branch - Contains those ‘extended’ SNMP objects defined by
network equipment vendors.
The ‘experimental’ and ‘directory’ SNMP branches - Also defined within the ‘internet’ root
directory, these branches are usually devoid of any meaningful data or objects.
Содержание TP-1610
Страница 28: ...28 V6100 and V7122 User Guide Reader s Notes ...
Страница 48: ...48 V6100 and V7122 User Guide Reader s Notes ...
Страница 72: ...72 V6100 and V7122 User Guide Reader s Notes ...
Страница 80: ...80 V6100 and V7122 User Guide Reader s Notes ...
Страница 151: ...V6100 and V7122 User Guide 151 Figure 83 Log off Prompt 2 Click OK in the prompt the Web session is logged off ...
Страница 152: ...152 V6100 and V7122 User Guide Reader s Notes ...
Страница 262: ...262 V6100 and V7122 User Guide Reader s Notes ...
Страница 284: ...284 V6100 and V7122 User Guide Reader s Notes ...
Страница 291: ...V6100 and V7122 User Guide 291 Figure 95 V7122 Startup Process ...
Страница 324: ...324 V6100 and V7122 User Guide Reader s Notes ...
Страница 354: ...354 V6100 and V7122 User Guide Reader s Notes ...
Страница 374: ...374 V6100 and V7122 User Guide Reader s Notes ...
Страница 382: ...382 V6100 and V7122 User Guide Figure 130 Example of a User Information File Reader s Notes ...
Страница 392: ...392 V6100 and V7122 User Guide Reader s Notes ...
Страница 409: ...V6100 and V7122 User Guide 409 Reader s Notes ...
Страница 413: ...V6100 and V7122 User Guide 413 Reader s Notes ...
Страница 425: ...V6100 and V7122 User Guide 425 Figure 145 UDP2File Utility Reader s Notes ...
Страница 431: ...V6100 and V7122 User Guide 431 Reader s Notes ...
Страница 447: ...V6100 and V7122 User Guide 447 Reader s Notes ...
Страница 449: ...V6100 and V7122 User Guide 449 Figure 146 Connection Module CM Figure 147 OSN Server Figure 148 Hard Drive Module HDMX ...
Страница 483: ...V6100 and V7122 User Guide 483 Reader s Notes ...
