TELDAT-TRAP-FLT-MIB

All MIBs › TELDAT-TRAP-FLT-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Teldat Router Management, Teldat Trap Notifications

Description: Defines Teldat router FLT (filter) 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-FLT-MIB?

TELDAT-TRAP-FLT-MIB is a Teldat, S.A. proprietary MIB defining SNMP notifications generated by the FLT (filter) event subsystem on Teldat routers. Its varbind objects cover structure type, filter/packet offset, allocated cache-entry count, and system-name fields for four notification levels, referenced by seven numbered fltNotification traps. As a notification MIB it lets an administrator receive detailed filter-subsystem event alerts (offset, cache allocation) from a Teldat router's packet-filtering engine. It is deployed on Teldat, S.A. routers. Engineers can download the TELDAT-TRAP-FLT-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-FLT-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, S.A. routers

Monitoring Examples

An administrator investigates an fltNotification3 trap and reads flt3-cache-entries-allocated to diagnose a filter cache-allocation event on a Teldat router.

What Can Be Monitored

packet-filter (FLT) subsystem event notifications

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
fltTrapsMIB	1.3.6.1.4.1.2007.1.4.2			This Module Information Base file is defined for managing received SNMP notifications generated by the FLT event subsystem.
fltEventsGroup	1.3.6.1.4.1.2007.1.4.2.1
fltEventObjects1	1.3.6.1.4.1.2007.1.4.2.1.1			Event FLT.1 This message is generated when the filtering subsystem cannot allocate the memory to hold a data structure to hold filtering information. This results in a filter not being built.
STR flt1_structure_type	1.3.6.1.4.1.2007.1.4.2.1.1.1	DisplayString	accessible-for-notify	Parameter 'structure-type' in event FLT.1
fltEventObjects2	1.3.6.1.4.1.2007.1.4.2.1.2			Event FLT.2 This message is generated when the maximum offset in a filter is larger than the length of a packet. The filter is not applied to the packet.
I32 flt2_filter_offset	1.3.6.1.4.1.2007.1.4.2.1.2.1	Integer32	accessible-for-notify	Parameter 'filter-offset' in event FLT.2
I32 flt2_packet_offset	1.3.6.1.4.1.2007.1.4.2.1.2.2	Integer32	accessible-for-notify	Parameter 'packet-offset' in event FLT.2
fltEventObjects3	1.3.6.1.4.1.2007.1.4.2.1.3			Event FLT.3 This message is generated if a filter is attempting to create a cache entry but cannot do so because there is no available memory on the heap. Instead, an existing entry is reused from the filter.
I32 flt3_cache_entries_allocated	1.3.6.1.4.1.2007.1.4.2.1.3.1	Integer32	accessible-for-notify	Parameter 'cache-entries-allocated' in event FLT.3
fltEventObjects4	1.3.6.1.4.1.2007.1.4.2.1.4			Event FLT.4 A filter is being created for the router system identified by system-name.
STR flt4_system_name	1.3.6.1.4.1.2007.1.4.2.1.4.1	DisplayString	accessible-for-notify	Parameter 'system-name' in event FLT.4
fltEventObjects5	1.3.6.1.4.1.2007.1.4.2.1.5			Event FLT.5 A filter produced a cache hit. System-name is the system name of a filter that was previously created.
STR flt5_system_name	1.3.6.1.4.1.2007.1.4.2.1.5.1	DisplayString	accessible-for-notify	Parameter 'system-name' in event FLT.5
fltEventObjects6	1.3.6.1.4.1.2007.1.4.2.1.6			Event FLT.6 A filter produced a match, but with no cache hit. System-name is the system name of a filter that was previously created.
STR flt6_system_name	1.3.6.1.4.1.2007.1.4.2.1.6.1	DisplayString	accessible-for-notify	Parameter 'system-name' in event FLT.6
fltEventObjects7	1.3.6.1.4.1.2007.1.4.2.1.7			Event FLT.7 A filter was applied to a block a data, but not match was found. System-name is the system name of a filter that was previously created.
STR flt7_system_name	1.3.6.1.4.1.2007.1.4.2.1.7.1	DisplayString	accessible-for-notify	Parameter 'system-name' in event FLT.7
fltNotifications	1.3.6.1.4.1.2007.1.4.2.2
fltNotificationsPrefix	1.3.6.1.4.1.2007.1.4.2.2.0
NTF fltNotification1	1.3.6.1.4.1.2007.1.4.2.2.0.1			Notification of Event FLT.1 Message: 'No free memory to create a $1' Parameters list: $1: flt1-structure-type This message is generated when the filtering subsystem cannot allocate the memory to hold a data structure to hold filtering information. This results in a filter not being built.
NTF fltNotification2	1.3.6.1.4.1.2007.1.4.2.2.0.2			Notification of Event FLT.2 Message: 'Cannot apply filter (offset $1), to packet of length $2' Parameters list: $1: flt2-filter-offset $2: flt2-packet-offset This message is generated when the maximum offset in a filter is larger than the length of a packet. The filter is not applied to the packet.
NTF fltNotification3	1.3.6.1.4.1.2007.1.4.2.2.0.3			Notification of Event FLT.3 Message: 'No memory to cache packet (maximum $1)' Parameters list: $1: flt3-cache-entries-allocated This message is generated if a filter is attempting to create a cache entry but cannot do so because there is no available memory on the heap. Instead, an existing entry is reused from the filter.
NTF fltNotification4	1.3.6.1.4.1.2007.1.4.2.2.0.4			Notification of Event FLT.4 Message: 'Creating filter for system $1' Parameters list: $1: flt4-system-name A filter is being created for the router system identified by system-name.
NTF fltNotification5	1.3.6.1.4.1.2007.1.4.2.2.0.5			Notification of Event FLT.5 Message: 'Filter cache hit, system $1' Parameters list: $1: flt5-system-name A filter produced a cache hit. System-name is the system name of a filter that was previously created.
NTF fltNotification6	1.3.6.1.4.1.2007.1.4.2.2.0.6			Notification of Event FLT.6 Message: 'Filter match, system $1' Parameters list: $1: flt6-system-name A filter produced a match, but with no cache hit. System-name is the system name of a filter that was previously created.
NTF fltNotification7	1.3.6.1.4.1.2007.1.4.2.2.0.7			Notification of Event FLT.7 Message: 'Filter miss, system $1' Parameters list: $1: flt7-system-name A filter was applied to a block a data, but not match was found. System-name is the system name of a filter that was previously created.

RFC description

MIB for managing FLT event subsystem SNMP notifications and filtering system events.

Start monitoring Teldat, S.A. routers (packet-filter subsystem 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-FLT-MIB

What Is TELDAT-TRAP-FLT-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description