
Configuring SNMP, RMON, BOOTP, DHCP, and RARP Services
2-6 114070 Rev. B
Severity Levels
Event and trap messages are always associated with one of five severity levels.
T
able 2-1 describes the severity levels and lists the code that corresponds to each
one. This guide does not cover Debug messages, because these are for Bay
Networks internal use only.
Refer to Event Messages for Routers and BNX Platforms for detailed information
about entities and severity levels.
SNMP Trap Format
Some third party network management applications, such as NetExpert,
OpenView, and SunNet, allow you to trigger a desired operation when a specific
SNMP trap is received. This section describes the SNMP trap format.
The router or BNX platform transmits Bay Networks event log traps as a 32-bit
value as follows:
• Octets 1 and 2 (the most significant 16 bits) of the specific trap ID contain
values of 1 and 0 respectively to identify a Bay Networks event log trap.
• Octet 3 of the specific trap ID contains a code that identifies the software
entity that generated the trap.
• Octet 4 of the specific ID contains the event code that, in conjunction with the
entity code, uniquely identifies the event.
Table 2-1. Severity Levels
Severity Description Code
Information Indicates routine events that usually require no action. 2
Warning Indicates that a service acted in an unexpected manner. 4
Fault Indicates a major service disruption, usually caused by a
configuration, network, or hardware problem. The entities
involved keep restarting until the problem is resolved.
8
Trace Indicates information about each packet that traversed the
network. Bay Networks recommends viewing this type of trap
message only when diagnosing network problems.
10
Debug Indicates information that Bay Networks Customer Support
uses. These messages are not documented.
1
Komentáře k této Příručce