TELDAT-TRAP-FLT-MIB: View SNMP OID List / Download MIB

VENDOR: TELDAT, S.A.


 Home MIB: TELDAT-TRAP-FLT-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC, TELDAT-MIB

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 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.
             flt1_structure_type 1.3.6.1.4.1.2007.1.4.2.1.1.1 displaystring no-access
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.
             flt2_filter_offset 1.3.6.1.4.1.2007.1.4.2.1.2.1 integer32 no-access
Parameter 'filter-offset' in event FLT.2
             flt2_packet_offset 1.3.6.1.4.1.2007.1.4.2.1.2.2 integer32 no-access
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.
             flt3_cache_entries_allocated 1.3.6.1.4.1.2007.1.4.2.1.3.1 integer32 no-access
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.
             flt4_system_name 1.3.6.1.4.1.2007.1.4.2.1.4.1 displaystring no-access
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.
             flt5_system_name 1.3.6.1.4.1.2007.1.4.2.1.5.1 displaystring no-access
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.
             flt6_system_name 1.3.6.1.4.1.2007.1.4.2.1.6.1 displaystring no-access
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.
             flt7_system_name 1.3.6.1.4.1.2007.1.4.2.1.7.1 displaystring no-access
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
             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.
             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.
             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.
             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.
             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.
             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.
             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.