ZyXEL Communications Corporation OX253P Manual De Usuario
Chapter 13 The Remote Management Screens
OX253P User’s Guide
138
The managed devices contain object variables/managed objects that define each
piece of information to be collected about a device. Examples of variables include
such as number of packets received, node port status etc. A Management
Information Base (MIB) is a collection of managed objects. SNMP allows a
manager and agents to communicate for the purpose of accessing these objects.
The OX253P supports MIB II that is defined in RFC-1213 and RFC-1215. The focus
of the MIBs is to let administrators collect statistical data and monitor status and
performance.
piece of information to be collected about a device. Examples of variables include
such as number of packets received, node port status etc. A Management
Information Base (MIB) is a collection of managed objects. SNMP allows a
manager and agents to communicate for the purpose of accessing these objects.
The OX253P supports MIB II that is defined in RFC-1213 and RFC-1215. The focus
of the MIBs is to let administrators collect statistical data and monitor status and
performance.
SNMP itself is a simple request/response protocol based on the manager/agent
model. The manager issues a request and the agent returns responses using the
following protocol operations:
model. The manager issues a request and the agent returns responses using the
following protocol operations:
• Get - Allows the manager to retrieve an object variable from the agent.
• GetNext - Allows the manager to retrieve the next object variable from a table
• GetNext - Allows the manager to retrieve the next object variable from a table
or list within an agent. In SNMPv1, when a manager wants to retrieve all
elements of a table from an agent, it initiates a Get operation, followed by a
series of GetNext operations.
• Set - Allows the manager to set values for object variables within an agent.
• Trap - Used by the agent to inform the manager of some events.
• Trap - Used by the agent to inform the manager of some events.
13.5.1 SNMP Traps
The OX253P sends traps to the SNMP manager when any of the following events
occurs:
occurs:
Table 53 SNMP Traps
TRAP #
TRAP NAME
DESCRIPTION
0
coldStart (defined in
RFC-1215)
RFC-1215)
A trap is sent after booting (power on).
1
warmStart (defined in
RFC-1215)
RFC-1215)
A trap is sent after booting (software reboot).
4
authenticationFailure
(defined in RFC-1215)
(defined in RFC-1215)
A trap is sent to the manager when receiving any
SNMP get or set requirements with the wrong
SNMP get or set requirements with the wrong
community (password).
6
whyReboot
A trap is sent with the reason of restart before
rebooting when the system is going to restart (warm
start).
rebooting when the system is going to restart (warm
start).
6a
For intentional reboot:
A trap is sent with the message "System reboot by
user!" if reboot is done intentionally, (for example,
download new files, CI command "sys reboot", etc.).
user!" if reboot is done intentionally, (for example,
download new files, CI command "sys reboot", etc.).
6b
For fatal error:
A trap is sent with the message of the fatal code if the
system reboots because of fatal errors.
system reboots because of fatal errors.