Avaya Configuring SNMP, BOOTP, DHCP, and RARP Services Manuel d'utilisateur Page 35

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 146
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 34
SNMP, BootP, DHCP, and RARP Concepts
303542-A Rev 00
2-5
An event log message provides a brief description of an event, along with the
event code associated with that event.
A trap is an event that the router transmits to the network management station.
SNMP allows you to configure which event log messages the agent sends to the
network management station as traps. You select these traps based on slot,
protocol entity, and severity level. You can also specify up to 50 exceptions, which
are traps that the agent always sends, or never sends, regardless of slot and
regardless of how you configure the trap parameters. For information about how
to specify which traps the agent sends, seeConfiguring Traps on the Router
” on
page 3-19.
Protocol Entities
Events are always associated with a particular protocol entity. An entity is the
software that generates a message. Entities include Bay Networks software
dedicated to the operation of a software service, such as Trivial File Transfer
Protocol (TFTP) and IP, and the GAME
®
operating system.
Both events and entities are assigned entity codes. Together, this pair uniquely
identifies a Bay Networks router platform event. For a complete list of entities
(both their abbreviations and full names) and associated entity codes, see Event
Messages for Routers.
Severity Levels
Event and trap messages are always associated with a severity level. Table 2-1
describes the severity levels and gives the code that corresponds to each one. This
guide does not cover Debug messages, because they are for Bay Networks internal
use only.
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
(continued)
Vue de la page 34
1 2 ... 30 31 32 33 34 35 36 37 38 39 40 ... 145 146

Commentaires sur ces manuels

Pas de commentaire