Private Traps and MIB Files
Traps are used to signal status changes to the manager while avoiding additional traffic:
-
LEDs (profileLED): This trap is sent if the LED state changes.
-
communications ports (port502StatusChange): This trap is sent if port502Status changes.
-
I/O scanning health value (ioScanStatusChange): This trap is sent if ioScanStatus changes.
-
global data health value (glbDataStatusChange): This trap is sent if glbDataStatus changes.
-
Web service (webStatusChange): This trap is sent if webStatus changes.
-
address server (addressServerStatusChange): This trap is sent if addressServerStatus changes.
-
NTP service (see below)
-
SMTP service (see below)
Private traps can:
Private traps are described in the MIB ASN.1 description, which is contained in a .mib text file.
-
NTP status (ntpStatusChange): This trap is sent if ntpStatus changes.
-
server change (ntpServerChange): This trap is sent if the NTP component switches from the Primary NTP server to the standby NTP server or vice versa.
-
link server status change (ntpLnkSrvStatusChange): This trap is sent if the NTP link server status changes.
-
leap second (ntpLeapSecond): This trap is sent when leap seconds are inserted.
-
DST change (ntpDSTChange): This trap notifies the manager that the NTP server time has changed from either:
-
SMTP status change (smtpStatusChange): This trap is sent if smtpStatus of the email service referenced by emailIndex changes.
-
SMTP link to server status (smtpLnkSrvChange): This trap is sent when the smtpLnkSrvStatus of the email service referenced by emailIndex changes. The trap is sent when the service tries to send an email. Every 30 minutes a periodic test checks the connection to the SMTP server.