TELDAT-TRAP-SCEP-MIB

All MIBs › TELDAT-TRAP-SCEP-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: IP Security and VPN, Teldat Router Management, Teldat Trap Notifications

Description: Defines Teldat router SCEP (certificate enrollment) event trap notifications.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is TELDAT-TRAP-SCEP-MIB?

This Teldat-proprietary MIB defines SNMP trap notifications for the SCEP (Simple Certificate Enrollment Protocol) subsystem on Teldat routers, covering certificate request and enrollment events with a CA server. It exposes event data such as the request type, the SCEP server's IP address, application/client identifiers, and free-text reason or message strings describing the outcome of an enrollment attempt. It is a software-status monitor for the router's PKI/certificate lifecycle rather than a hardware monitor: administrators use it to detect failed or delayed certificate enrollments, which can otherwise silently break VPN or management authentication once a certificate expires. It builds on the industry SCEP protocol conventions for certificate enrollment, even though the MIB itself is Teldat's proprietary trap representation. It is deployed on Teldat routers configured for automated certificate enrollment in VPN or secure-management deployments. Engineers can download the TELDAT-TRAP-SCEP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-SCEP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Teldat router

Monitoring Examples

An administrator would monitor scep1-request-type and scep1-server-ip-address to confirm which type of enrollment request was sent and to which CA/SCEP server, and would inspect scep2-reason together with scep2-app-or-client when an enrollment attempt fails to determine whether the router or the application component was responsible. scep9-Error-description and scep10-information-txt/scep11-information-txt supply human-readable diagnostic text for troubleshooting a rejected or malformed certificate request. Because certificate renewal failures can silently break IPsec/VPN authentication, these traps are typically wired into alerting so operators can intervene before a certificate actually expires.

What Can Be Monitored

SCEP enrollment request type
SCEP server address
enrollment failure reason
certificate error descriptions

Imported Objects

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString

From TELDAT-MIB

telEventTraps

OBJECT-IDENTITY

OIDs

OID symbolic	OID numeric	Type	Access	Description
scepTrapsMIB	1.3.6.1.4.1.2007.1.4.147			This Module Information Base file is defined for managing received SNMP notifications generated by the SCEP event subsystem.
scepEventsGroup	1.3.6.1.4.1.2007.1.4.147.1
scepEventObjects1	1.3.6.1.4.1.2007.1.4.147.1.1			Event SCEP.1 Request SCEP in progress. First step to success depends on whether tcp establishes connection.
STR scep1_request_type	1.3.6.1.4.1.2007.1.4.147.1.1.1	DisplayString	accessible-for-notify	Parameter 'request-type' in event SCEP.1
IP scep1_server_ip_address	1.3.6.1.4.1.2007.1.4.147.1.1.2	IpAddress	accessible-for-notify	Parameter 'server-ip-address' in event SCEP.1
scepEventObjects2	1.3.6.1.4.1.2007.1.4.147.1.2			Event SCEP.2 Reset session SCEP by application or client SCEP, in a normal way (app), aborting (app), by error (client), or by timeout (app or client).
STR scep2_reason	1.3.6.1.4.1.2007.1.4.147.1.2.1	DisplayString	accessible-for-notify	Parameter 'reason' in event SCEP.2
STR scep2_app_or_client	1.3.6.1.4.1.2007.1.4.147.1.2.2	DisplayString	accessible-for-notify	Parameter 'app-or-client' in event SCEP.2
scepEventObjects3	1.3.6.1.4.1.2007.1.4.147.1.3			Event SCEP.3 Session SCEP with server closed.
IP scep3_server_ip_address	1.3.6.1.4.1.2007.1.4.147.1.3.1	IpAddress	accessible-for-notify	Parameter 'server-ip-address' in event SCEP.3
scepEventObjects4	1.3.6.1.4.1.2007.1.4.147.1.4			Event SCEP.4 Received message.
STR scep4_msg	1.3.6.1.4.1.2007.1.4.147.1.4.1	DisplayString	accessible-for-notify	Parameter 'msg' in event SCEP.4
scepEventObjects5	1.3.6.1.4.1.2007.1.4.147.1.5			Event SCEP.5 Message to be sent.
STR scep5_msg	1.3.6.1.4.1.2007.1.4.147.1.5.1	DisplayString	accessible-for-notify	Parameter 'msg' in event SCEP.5
scepEventObjects6	1.3.6.1.4.1.2007.1.4.147.1.6			Event SCEP.6 Session SCEP with server whose IP address is shown has just been opened.
IP scep6_server_ip_address	1.3.6.1.4.1.2007.1.4.147.1.6.1	IpAddress	accessible-for-notify	Parameter 'server-ip-address' in event SCEP.6
scepEventObjects9	1.3.6.1.4.1.2007.1.4.147.1.9			Event SCEP.9 A http header has been received with error description.
STR scep9_Error_description	1.3.6.1.4.1.2007.1.4.147.1.9.1	DisplayString	accessible-for-notify	Parameter 'Error-description' in event SCEP.9
scepEventObjects10	1.3.6.1.4.1.2007.1.4.147.1.10			Event SCEP.10 Processed information (whose type is shown) is not valid.
STR scep10_information_txt	1.3.6.1.4.1.2007.1.4.147.1.10.1	DisplayString	accessible-for-notify	Parameter 'information-txt' in event SCEP.10
scepEventObjects11	1.3.6.1.4.1.2007.1.4.147.1.11			Event SCEP.11 Internal error while processing information whose type is shown.
STR scep11_information_txt	1.3.6.1.4.1.2007.1.4.147.1.11.1	DisplayString	accessible-for-notify	Parameter 'information-txt' in event SCEP.11
scepEventObjects12	1.3.6.1.4.1.2007.1.4.147.1.12			Event SCEP.12 Server SCEP has closed its session.
IP scep12_server_ip_address	1.3.6.1.4.1.2007.1.4.147.1.12.1	IpAddress	accessible-for-notify	Parameter 'server-ip-address' in event SCEP.12
scepEventObjects13	1.3.6.1.4.1.2007.1.4.147.1.13			Event SCEP.13 Message SCEPReq completely sent to the indicated server.
IP scep13_server_ip_address	1.3.6.1.4.1.2007.1.4.147.1.13.1	IpAddress	accessible-for-notify	Parameter 'server-ip-address' in event SCEP.13
scepEventObjects14	1.3.6.1.4.1.2007.1.4.147.1.14			Event SCEP.14 The message response to receive is bytes-to-read long.
I32 scep14_bytes_to_read	1.3.6.1.4.1.2007.1.4.147.1.14.1	Integer32	accessible-for-notify	Parameter 'bytes-to-read' in event SCEP.14
scepEventObjects15	1.3.6.1.4.1.2007.1.4.147.1.15			Event SCEP.15 It is shown the number of bytes read until now.
I32 scep15_bytes_read	1.3.6.1.4.1.2007.1.4.147.1.15.1	Integer32	accessible-for-notify	Parameter 'bytes-read' in event SCEP.15
scepNotifications	1.3.6.1.4.1.2007.1.4.147.2
scepNotificationsPrefix	1.3.6.1.4.1.2007.1.4.147.2.0
NTF scepNotification1	1.3.6.1.4.1.2007.1.4.147.2.0.1			Notification of Event SCEP.1 Message: 'Request type $1 (destination $2) in progress' Parameters list: $1: scep1-request-type $2: scep1-server-ip-address Request SCEP in progress. First step to success depends on whether tcp establishes connection.
NTF scepNotification2	1.3.6.1.4.1.2007.1.4.147.2.0.2			Notification of Event SCEP.2 Message: 'Reset session SCEP (reason $1) by $2' Parameters list: $1: scep2-reason $2: scep2-app-or-client Reset session SCEP by application or client SCEP, in a normal way (app), aborting (app), by error (client), or by timeout (app or client).
NTF scepNotification3	1.3.6.1.4.1.2007.1.4.147.2.0.3			Notification of Event SCEP.3 Message: 'Session SCEP (destination $1) closed' Parameters list: $1: scep3-server-ip-address Session SCEP with server closed.
NTF scepNotification4	1.3.6.1.4.1.2007.1.4.147.2.0.4			Notification of Event SCEP.4 Message: 'Received message $1' Parameters list: $1: scep4-msg Received message.
NTF scepNotification5	1.3.6.1.4.1.2007.1.4.147.2.0.5			Notification of Event SCEP.5 Message: 'Send message: $1' Parameters list: $1: scep5-msg Message to be sent.
NTF scepNotification6	1.3.6.1.4.1.2007.1.4.147.2.0.6			Notification of Event SCEP.6 Message: 'Session SCEP (destination $1) opened' Parameters list: $1: scep6-server-ip-address Session SCEP with server whose IP address is shown has just been opened.
NTF scepNotification7	1.3.6.1.4.1.2007.1.4.147.2.0.7			Notification of Event SCEP.7 Message: 'Header no type http' Header received is no a valid http header.
NTF scepNotification8	1.3.6.1.4.1.2007.1.4.147.2.0.8			Notification of Event SCEP.8 Message: 'No content length received' There is no content length received, or it is 0.
NTF scepNotification9	1.3.6.1.4.1.2007.1.4.147.2.0.9			Notification of Event SCEP.9 Message: 'Http hdr received. Error: $1' Parameters list: $1: scep9-Error-description A http header has been received with error description.
NTF scepNotification10	1.3.6.1.4.1.2007.1.4.147.2.0.10			Notification of Event SCEP.10 Message: 'Invalid information $1' Parameters list: $1: scep10-information-txt Processed information (whose type is shown) is not valid.
NTF scepNotification11	1.3.6.1.4.1.2007.1.4.147.2.0.11			Notification of Event SCEP.11 Message: 'Error while processing $1' Parameters list: $1: scep11-information-txt Internal error while processing information whose type is shown.
NTF scepNotification12	1.3.6.1.4.1.2007.1.4.147.2.0.12			Notification of Event SCEP.12 Message: 'Server session SCEP (from $1) closed' Parameters list: $1: scep12-server-ip-address Server SCEP has closed its session.
NTF scepNotification13	1.3.6.1.4.1.2007.1.4.147.2.0.13			Notification of Event SCEP.13 Message: 'Message SCEPReq sent to $1' Parameters list: $1: scep13-server-ip-address Message SCEPReq completely sent to the indicated server.
NTF scepNotification14	1.3.6.1.4.1.2007.1.4.147.2.0.14			Notification of Event SCEP.14 Message: 'Bytes from server to read: $1' Parameters list: $1: scep14-bytes-to-read The message response to receive is bytes-to-read long.
NTF scepNotification15	1.3.6.1.4.1.2007.1.4.147.2.0.15			Notification of Event SCEP.15 Message: 'Bytes read: $1' Parameters list: $1: scep15-bytes-read It is shown the number of bytes read until now.
NTF scepNotification16	1.3.6.1.4.1.2007.1.4.147.2.0.16			Notification of Event SCEP.16 Message: 'SCEP process aborted by user' SCEP process is aborted because user introduced an Abort command from console.
NTF scepNotification17	1.3.6.1.4.1.2007.1.4.147.2.0.17			Notification of Event SCEP.17 Message: 'Message dropped by abort command' A message was in parsing process while an Abort command was issued, so when parsing finished, the message was discarded.

RFC description

SNMP notification events for Simple Certificate Enrollment Protocol (SCEP) request and session management.

Start monitoring Teldat routers with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download TELDAT-TRAP-SCEP-MIB

What Is TELDAT-TRAP-SCEP-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description