TELDAT-TRAP-SPI-MIB

All MIBs › TELDAT-TRAP-SPI-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 SPI (stateful packet inspection) firewall 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-SPI-MIB?

TELDAT-TRAP-SPI-MIB is a Teldat, S.A. vendor-specific MIB that defines the SNMP notification objects and NOTIFICATION-TYPE definitions generated by the SPI (mobile agent/keep-alive) event subsystem on Teldat routers. It models sixteen distinct SPI events (spiEventObjects1 through spiEventObjects16) covering agent initialization success/failure, keep-alive (KA/KAI/KAO/KAR) message exchange with a management server, SIM/ICC-ID validation errors, protocol version mismatches, and retransmission-limit conditions, each carrying parameters like spi9-server-ip, spi5-state, and spi16-data. Because the module is trap-only, it exposes no polled counters directly — its value for monitoring comes from correlating received notifications (spiNotification1 through spiNotification16) against expected agent behavior to detect SPI communication failures or misconfigured mobile agents. It depends on the base TELDAT-MIB for the telEventTraps registration point and is deployed alongside Teldat's SPI (Stateful/Session Peer Interface) mobile management feature; administrators managing fleets of Teldat routers can download the TELDAT-TRAP-SPI-MIB file to load it into their MIB browser and configure trap handling.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-SPI-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 routers
Teldat SPI mobile-agent-capable devices

Monitoring Examples

An operator's trap receiver watches for spiNotification9 (SPI initialization failure) carrying spi9-agent-name and spi9-server-ip; repeated occurrences for the same agent, without a corresponding spiNotification1 (successful initialization) or spiNotification11/12/13 keep-alive traps afterward, would indicate the SPI agent cannot reach its management server.

What Can Be Monitored

SPI agent initialization success/failure events
keep-alive (KA/KAI/KAO/KAR) message exchange events
ICC-ID/MSISDN/protocol-version validation errors
message retransmission-limit-reached events
unknown message type errors

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
spiTrapsMIB	1.3.6.1.4.1.2007.1.4.223			This Module Information Base file is defined for managing received SNMP notifications generated by the SPI event subsystem.
spiEventsGroup	1.3.6.1.4.1.2007.1.4.223.1
spiEventObjects1	1.3.6.1.4.1.2007.1.4.223.1.1			Event SPI.1 Initialization successfully when a SPI agent is configured.
STR spi1_agent_name	1.3.6.1.4.1.2007.1.4.223.1.1.1	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.1
spiEventObjects2	1.3.6.1.4.1.2007.1.4.223.1.2			Event SPI.2 SPI agent message don't send due ICC-ID is not available.
STR spi2_agent_name	1.3.6.1.4.1.2007.1.4.223.1.2.1	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.2
I32 spi2_state	1.3.6.1.4.1.2007.1.4.223.1.2.2	Integer32	accessible-for-notify	Parameter 'state' in event SPI.2
spiEventObjects3	1.3.6.1.4.1.2007.1.4.223.1.3			Event SPI.3 Received SPI message error due protocol version param.
I32 spi3_prot_ver	1.3.6.1.4.1.2007.1.4.223.1.3.1	Integer32	accessible-for-notify	Parameter 'prot-ver' in event SPI.3
STR spi3_agent_name	1.3.6.1.4.1.2007.1.4.223.1.3.2	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.3
I32 spi3_state	1.3.6.1.4.1.2007.1.4.223.1.3.3	Integer32	accessible-for-notify	Parameter 'state' in event SPI.3
spiEventObjects4	1.3.6.1.4.1.2007.1.4.223.1.4			Event SPI.4 Received SPI message error due MSISDN is not associated to agent.
STR spi4_msisdn	1.3.6.1.4.1.2007.1.4.223.1.4.1	DisplayString	accessible-for-notify	Parameter 'msisdn' in event SPI.4
STR spi4_agent_name	1.3.6.1.4.1.2007.1.4.223.1.4.2	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.4
I32 spi4_state	1.3.6.1.4.1.2007.1.4.223.1.4.3	Integer32	accessible-for-notify	Parameter 'state' in event SPI.4
spiEventObjects5	1.3.6.1.4.1.2007.1.4.223.1.5			Event SPI.5 Correct KAR message has been received.
STR spi5_agent_name	1.3.6.1.4.1.2007.1.4.223.1.5.1	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.5
IP spi5_ip_org	1.3.6.1.4.1.2007.1.4.223.1.5.2	IpAddress	accessible-for-notify	Parameter 'ip-org' in event SPI.5
I32 spi5_port_org	1.3.6.1.4.1.2007.1.4.223.1.5.3	Integer32	accessible-for-notify	Parameter 'port-org' in event SPI.5
I32 spi5_state	1.3.6.1.4.1.2007.1.4.223.1.5.4	Integer32	accessible-for-notify	Parameter 'state' in event SPI.5
spiEventObjects6	1.3.6.1.4.1.2007.1.4.223.1.6			Event SPI.6 Correct SIM message has been received.
STR spi6_agent_name	1.3.6.1.4.1.2007.1.4.223.1.6.1	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.6
IP spi6_ip_org	1.3.6.1.4.1.2007.1.4.223.1.6.2	IpAddress	accessible-for-notify	Parameter 'ip-org' in event SPI.6
I32 spi6_port_org	1.3.6.1.4.1.2007.1.4.223.1.6.3	Integer32	accessible-for-notify	Parameter 'port-org' in event SPI.6
I32 spi6_state	1.3.6.1.4.1.2007.1.4.223.1.6.4	Integer32	accessible-for-notify	Parameter 'state' in event SPI.6
spiEventObjects7	1.3.6.1.4.1.2007.1.4.223.1.7			Event SPI.7 Correct RKAO message has been received.
STR spi7_agent_name	1.3.6.1.4.1.2007.1.4.223.1.7.1	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.7
IP spi7_ip_org	1.3.6.1.4.1.2007.1.4.223.1.7.2	IpAddress	accessible-for-notify	Parameter 'ip-org' in event SPI.7
I32 spi7_port_org	1.3.6.1.4.1.2007.1.4.223.1.7.3	Integer32	accessible-for-notify	Parameter 'port-org' in event SPI.7
I32 spi7_state	1.3.6.1.4.1.2007.1.4.223.1.7.4	Integer32	accessible-for-notify	Parameter 'state' in event SPI.7
spiEventObjects8	1.3.6.1.4.1.2007.1.4.223.1.8			Event SPI.8 Error, Unknown message type has been received.
I32 spi8_msg_type	1.3.6.1.4.1.2007.1.4.223.1.8.1	Integer32	accessible-for-notify	Parameter 'msg-type' in event SPI.8
STR spi8_agent_name	1.3.6.1.4.1.2007.1.4.223.1.8.2	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.8
IP spi8_ip_org	1.3.6.1.4.1.2007.1.4.223.1.8.3	IpAddress	accessible-for-notify	Parameter 'ip-org' in event SPI.8
I32 spi8_port_org	1.3.6.1.4.1.2007.1.4.223.1.8.4	Integer32	accessible-for-notify	Parameter 'port-org' in event SPI.8
I32 spi8_state	1.3.6.1.4.1.2007.1.4.223.1.8.5	Integer32	accessible-for-notify	Parameter 'state' in event SPI.8
spiEventObjects9	1.3.6.1.4.1.2007.1.4.223.1.9			Event SPI.9 Initialization failure when a SPI agent is configured.
STR spi9_agent_name	1.3.6.1.4.1.2007.1.4.223.1.9.1	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.9
IP spi9_server_ip	1.3.6.1.4.1.2007.1.4.223.1.9.2	IpAddress	accessible-for-notify	Parameter 'server-ip' in event SPI.9
I32 spi9_server_udp_port	1.3.6.1.4.1.2007.1.4.223.1.9.3	Integer32	accessible-for-notify	Parameter 'server-udp-port' in event SPI.9
spiEventObjects10	1.3.6.1.4.1.2007.1.4.223.1.10			Event SPI.10 SPI agent timer has been triggered.
STR spi10_timer	1.3.6.1.4.1.2007.1.4.223.1.10.1	DisplayString	accessible-for-notify	Parameter 'timer' in event SPI.10
STR spi10_agent_name	1.3.6.1.4.1.2007.1.4.223.1.10.2	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.10
I32 spi10_state	1.3.6.1.4.1.2007.1.4.223.1.10.3	Integer32	accessible-for-notify	Parameter 'state' in event SPI.10
spiEventObjects11	1.3.6.1.4.1.2007.1.4.223.1.11			Event SPI.11 KA message has been send to server.
STR spi11_agent_name	1.3.6.1.4.1.2007.1.4.223.1.11.1	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.11
IP spi11_ip_org	1.3.6.1.4.1.2007.1.4.223.1.11.2	IpAddress	accessible-for-notify	Parameter 'ip-org' in event SPI.11
I32 spi11_port_org	1.3.6.1.4.1.2007.1.4.223.1.11.3	Integer32	accessible-for-notify	Parameter 'port-org' in event SPI.11
I32 spi11_state	1.3.6.1.4.1.2007.1.4.223.1.11.4	Integer32	accessible-for-notify	Parameter 'state' in event SPI.11
spiEventObjects12	1.3.6.1.4.1.2007.1.4.223.1.12			Event SPI.12 KAI message has been send to server.
STR spi12_agent_name	1.3.6.1.4.1.2007.1.4.223.1.12.1	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.12
IP spi12_ip_org	1.3.6.1.4.1.2007.1.4.223.1.12.2	IpAddress	accessible-for-notify	Parameter 'ip-org' in event SPI.12
I32 spi12_port_org	1.3.6.1.4.1.2007.1.4.223.1.12.3	Integer32	accessible-for-notify	Parameter 'port-org' in event SPI.12
I32 spi12_state	1.3.6.1.4.1.2007.1.4.223.1.12.4	Integer32	accessible-for-notify	Parameter 'state' in event SPI.12
spiEventObjects13	1.3.6.1.4.1.2007.1.4.223.1.13			Event SPI.13 KAO message has been send to server.
STR spi13_agent_name	1.3.6.1.4.1.2007.1.4.223.1.13.1	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.13
IP spi13_ip_org	1.3.6.1.4.1.2007.1.4.223.1.13.2	IpAddress	accessible-for-notify	Parameter 'ip-org' in event SPI.13
I32 spi13_port_org	1.3.6.1.4.1.2007.1.4.223.1.13.3	Integer32	accessible-for-notify	Parameter 'port-org' in event SPI.13
I32 spi13_state	1.3.6.1.4.1.2007.1.4.223.1.13.4	Integer32	accessible-for-notify	Parameter 'state' in event SPI.13
spiEventObjects14	1.3.6.1.4.1.2007.1.4.223.1.14			Event SPI.14 Max. number of KAI message retransmisions reached.
STR spi14_agent_name	1.3.6.1.4.1.2007.1.4.223.1.14.1	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.14
I32 spi14_state	1.3.6.1.4.1.2007.1.4.223.1.14.2	Integer32	accessible-for-notify	Parameter 'state' in event SPI.14
spiEventObjects15	1.3.6.1.4.1.2007.1.4.223.1.15			Event SPI.15 Max. number of KA message retransmisions reached.
STR spi15_agent_name	1.3.6.1.4.1.2007.1.4.223.1.15.1	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.15
I32 spi15_state	1.3.6.1.4.1.2007.1.4.223.1.15.2	Integer32	accessible-for-notify	Parameter 'state' in event SPI.15
spiEventObjects16	1.3.6.1.4.1.2007.1.4.223.1.16			Event SPI.16 Detailed Data received from SPI server.
STR spi16_agent_name	1.3.6.1.4.1.2007.1.4.223.1.16.1	DisplayString	accessible-for-notify	Parameter 'agent-name' in event SPI.16
I32 spi16_state	1.3.6.1.4.1.2007.1.4.223.1.16.2	Integer32	accessible-for-notify	Parameter 'state' in event SPI.16
IP spi16_ip_org	1.3.6.1.4.1.2007.1.4.223.1.16.3	IpAddress	accessible-for-notify	Parameter 'ip-org' in event SPI.16
I32 spi16_leng	1.3.6.1.4.1.2007.1.4.223.1.16.4	Integer32	accessible-for-notify	Parameter 'leng' in event SPI.16
STR spi16_data	1.3.6.1.4.1.2007.1.4.223.1.16.5	DisplayString	accessible-for-notify	Parameter 'data' in event SPI.16
spiNotifications	1.3.6.1.4.1.2007.1.4.223.2
spiNotificationsPrefix	1.3.6.1.4.1.2007.1.4.223.2.0
NTF spiNotification1	1.3.6.1.4.1.2007.1.4.223.2.0.1			Notification of Event SPI.1 Message: 'SPI initialized sucessfully for agent:$1' Parameters list: $1: spi1-agent-name Initialization successfully when a SPI agent is configured.
NTF spiNotification2	1.3.6.1.4.1.2007.1.4.223.2.0.2			Notification of Event SPI.2 Message: 'Tx message error due ICC-ID is not available. agent:$1, state:$2' Parameters list: $1: spi2-agent-name $2: spi2-state SPI agent message don't send due ICC-ID is not available.
NTF spiNotification3	1.3.6.1.4.1.2007.1.4.223.2.0.3			Notification of Event SPI.3 Message: 'Rx message error due protocol version ($1) agent:$2, state:$3' Parameters list: $1: spi3-prot-ver $2: spi3-agent-name $3: spi3-state Received SPI message error due protocol version param.
NTF spiNotification4	1.3.6.1.4.1.2007.1.4.223.2.0.4			Notification of Event SPI.4 Message: 'Rx message error due MSISDN ($1) agent:$2, state:$3' Parameters list: $1: spi4-msisdn $2: spi4-agent-name $3: spi4-state Received SPI message error due MSISDN is not associated to agent.
NTF spiNotification5	1.3.6.1.4.1.2007.1.4.223.2.0.5			Notification of Event SPI.5 Message: 'Rx message KAR for agent:$1, Server IP address:$2, Server UDP port$3, state:$4' Parameters list: $1: spi5-agent-name $2: spi5-ip-org $3: spi5-port-org $4: spi5-state Correct KAR message has been received.
NTF spiNotification6	1.3.6.1.4.1.2007.1.4.223.2.0.6			Notification of Event SPI.6 Message: 'Rx message SIM for agent:$1, Server IP address:$2, Server UDP port$3, state:$4' Parameters list: $1: spi6-agent-name $2: spi6-ip-org $3: spi6-port-org $4: spi6-state Correct SIM message has been received.
NTF spiNotification7	1.3.6.1.4.1.2007.1.4.223.2.0.7			Notification of Event SPI.7 Message: 'Rx message RKAO for agent:$1, Server IP address:$2, Server UDP port$3, state:$4' Parameters list: $1: spi7-agent-name $2: spi7-ip-org $3: spi7-port-org $4: spi7-state Correct RKAO message has been received.
NTF spiNotification8	1.3.6.1.4.1.2007.1.4.223.2.0.8			Notification of Event SPI.8 Message: 'Rx message type unknown($1 for agent:$2, Server IP address:$3, Server UDP port$4, state:$5' Parameters list: $1: spi8-msg-type $2: spi8-agent-name $3: spi8-ip-org $4: spi8-port-org $5: spi8-state Error, Unknown message type has been received.
NTF spiNotification9	1.3.6.1.4.1.2007.1.4.223.2.0.9			Notification of Event SPI.9 Message: 'SPI initialization failure agent $1, Server IP address:$2, Server UDP port$3' Parameters list: $1: spi9-agent-name $2: spi9-server-ip $3: spi9-server-udp-port Initialization failure when a SPI agent is configured.
NTF spiNotification10	1.3.6.1.4.1.2007.1.4.223.2.0.10			Notification of Event SPI.10 Message: '$1 timer triggered agent:$2, state:$3' Parameters list: $1: spi10-timer $2: spi10-agent-name $3: spi10-state SPI agent timer has been triggered.
NTF spiNotification11	1.3.6.1.4.1.2007.1.4.223.2.0.11			Notification of Event SPI.11 Message: 'Tx KA message agent:$1, Server IP address:$2, Server UDP port$3, state:$4' Parameters list: $1: spi11-agent-name $2: spi11-ip-org $3: spi11-port-org $4: spi11-state KA message has been send to server.
NTF spiNotification12	1.3.6.1.4.1.2007.1.4.223.2.0.12			Notification of Event SPI.12 Message: 'Tx KAI message agent:$1, Server IP address:$2, Server UDP port$3, state:$4' Parameters list: $1: spi12-agent-name $2: spi12-ip-org $3: spi12-port-org $4: spi12-state KAI message has been send to server.
NTF spiNotification13	1.3.6.1.4.1.2007.1.4.223.2.0.13			Notification of Event SPI.13 Message: 'Tx KAO message agent:$1, Server IP address:$2, Server UDP port$3, state:$4' Parameters list: $1: spi13-agent-name $2: spi13-ip-org $3: spi13-port-org $4: spi13-state KAO message has been send to server.
NTF spiNotification14	1.3.6.1.4.1.2007.1.4.223.2.0.14			Notification of Event SPI.14 Message: 'Tx nkair retransmisions reached, agent:$1, state:$2' Parameters list: $1: spi14-agent-name $2: spi14-state Max. number of KAI message retransmisions reached.
NTF spiNotification15	1.3.6.1.4.1.2007.1.4.223.2.0.15			Notification of Event SPI.15 Message: 'Tx nkar retransmisions reached, agent:$1, state:$2' Parameters list: $1: spi15-agent-name $2: spi15-state Max. number of KA message retransmisions reached.
NTF spiNotification16	1.3.6.1.4.1.2007.1.4.223.2.0.16			Notification of Event SPI.16 Message: 'Data received from Server agent:$1 st:$2 (SvrIP:$3,$4 bytes):$5' Parameters list: $1: spi16-agent-name $2: spi16-state $3: spi16-ip-org $4: spi16-leng $5: spi16-data Detailed Data received from SPI server.

RFC description

SNMP notification events for SPI agent initialization, availability, and state changes.

Start monitoring Teldat SPI mobile-agent-capable devices (agent keep-alive/SIM-validation event traps) 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-SPI-MIB

What Is TELDAT-TRAP-SPI-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description