P-660R-D Series User’s Guide
105
Chapter 9 Remote Management Configuration
An SNMP managed network consists of two main types of component: agents and a manager.
An agent is a management software module that resides in a managed device (the ZyXEL
Device). An agent translates the local management information from the managed device into
a form compatible with SNMP. The manager is the console through which network
administrators perform network management functions. It executes applications that control
and monitor managed devices.
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.
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:
• 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 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.
9.6.1 Supported MIBs
The ZyXEL Device 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.
9.6.2 SNMP Traps
The ZyXEL Device will send traps to the SNMP manager when any one of the following
events occurs:
Table 37
SNMP Traps
TRAP # TRAP NAME
DESCRIPTION
0
coldStart (defined in
RFC-1215
)
A trap is sent after booting (power on).
1
warmStart (defined in
RFC-1215
)
A trap is sent after booting (software reboot).
6
whyReboot (defined in ZYXEL-
MIB)
A trap is sent with the reason of restart before
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.).
6b
For fatal error:
A trap is sent with the message of the fatal code if the
system reboots because of fatal errors.
Summary of Contents for P-660R-D Series
Page 1: ...P 660R D Series ADSL2 Router User s Guide Version 3 40 7 2006 Edition 1...
Page 2: ......
Page 10: ...P 660R D Series User s Guide 9 Customer Support...
Page 30: ...P 660R D Series User s Guide 29 Chapter 1 Getting To Know Your ZyXEL Device...
Page 66: ...P 660R D Series User s Guide 65 Chapter 4 WAN Setup...
Page 80: ...P 660R D Series User s Guide 79 Chapter 5 LAN Setup...
Page 96: ...P 660R D Series User s Guide 95 Chapter 7 Static Route...
Page 100: ...P 660R D Series User s Guide 99 Chapter 8 Dynamic DNS Setup...
Page 110: ...P 660R D Series User s Guide 109 Chapter 9 Remote Management Configuration...
Page 122: ...P 660R D Series User s Guide 121 Chapter 10 Universal Plug and Play UPnP...
Page 128: ...P 660R D Series User s Guide 127 Chapter 11 System...
Page 134: ...P 660R D Series User s Guide 133 Chapter 12 Tools...
Page 140: ...P 660R D Series User s Guide 139 Chapter 14 Troubleshooting...
Page 160: ...P 660R D Series User s Guide 141 Appendix C Wall mounting Instructions...
Page 184: ...P 660R D Series User s Guide 8 Appendix E IP Addresses and Subnetting...
Page 186: ...P 660R D Series User s Guide 2 Appendix F Command Interpreter...
Page 192: ...P 660R D Series User s Guide 4 Appendix H Splitters and Microfilters...
