TELDAT-TRAP-FLOW-MIB

All MIBs › TELDAT-TRAP-FLOW-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Teldat Router Management, Teldat Trap Notifications

Description: Defines Teldat router FLOW (traffic flow) 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-FLOW-MIB?

TELDAT-TRAP-FLOW-MIB is a Teldat proprietary, notification-only SNMP MIB that defines the trap varbinds emitted by the router's traffic-flow (FLOW) event subsystem, likely tied to NAT/firewall session tracking. It groups numbered event definitions (flow1 through flow4, under flowEventsGroup/flowNotifications) carrying flow state, source/destination IP address, protocol, session expiry, and, for server-side flows, server IP, port, and length. Operationally it is a fault/event monitor for the session-tracking software path: it lets a management station learn asynchronously about flow-state transitions and expirations, which is useful for correlating traffic anomalies, verifying NAT/firewall session behavior, or investigating why a particular client-server flow was aged out. As with Teldat's other TRAP-* modules it depends on the standard SNMPv2-SMI/SNMPv2-TC notification conventions and Teldat's private enterprise OID tree. It is deployed on Teldat routers performing NAT, firewalling, or flow-based traffic management where session lifecycle visibility supports troubleshooting. Engineers can download the TELDAT-TRAP-FLOW-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-FLOW-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

This module defines only notification objects and their varbinds rather than a polled flow table, so there is no GET-based monitoring scenario; it is trap-only. An SNMP trap receiver would inspect flow2-source-ip/flow2-destination-ip/flow2-protocol together with flow2-expiry to see which session aged out and when, and flow4-srvr-ip/flow4-srvr-port for the server side of a specific tracked flow.

What Can Be Monitored

traffic flow state transitions
flow source/destination IP, protocol, and expiry events

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
flowTrapsMIB	1.3.6.1.4.1.2007.1.4.218			This Module Information Base file is defined for managing received SNMP notifications generated by the FLOW event subsystem.
flowEventsGroup	1.3.6.1.4.1.2007.1.4.218.1
flowEventObjects1	1.3.6.1.4.1.2007.1.4.218.1.1			Event FLOW.1 client state changed
STR flow1_state	1.3.6.1.4.1.2007.1.4.218.1.1.1	DisplayString	accessible-for-notify	Parameter 'state' in event FLOW.1
flowEventObjects2	1.3.6.1.4.1.2007.1.4.218.1.2			Event FLOW.2 new flow created
IP flow2_source_ip	1.3.6.1.4.1.2007.1.4.218.1.2.1	IpAddress	accessible-for-notify	Parameter 'source-ip' in event FLOW.2
IP flow2_destination_ip	1.3.6.1.4.1.2007.1.4.218.1.2.2	IpAddress	accessible-for-notify	Parameter 'destination-ip' in event FLOW.2
STR flow2_protocol	1.3.6.1.4.1.2007.1.4.218.1.2.3	DisplayString	accessible-for-notify	Parameter 'protocol' in event FLOW.2
I32 flow2_expiry	1.3.6.1.4.1.2007.1.4.218.1.2.4	Integer32	accessible-for-notify	Parameter 'expiry' in event FLOW.2
flowEventObjects3	1.3.6.1.4.1.2007.1.4.218.1.3			Event FLOW.3 flow matched
IP flow3_source_ip	1.3.6.1.4.1.2007.1.4.218.1.3.1	IpAddress	accessible-for-notify	Parameter 'source-ip' in event FLOW.3
IP flow3_destination_ip	1.3.6.1.4.1.2007.1.4.218.1.3.2	IpAddress	accessible-for-notify	Parameter 'destination-ip' in event FLOW.3
STR flow3_protocol	1.3.6.1.4.1.2007.1.4.218.1.3.3	DisplayString	accessible-for-notify	Parameter 'protocol' in event FLOW.3
I32 flow3_expiry	1.3.6.1.4.1.2007.1.4.218.1.3.4	Integer32	accessible-for-notify	Parameter 'expiry' in event FLOW.3
flowEventObjects4	1.3.6.1.4.1.2007.1.4.218.1.4			Event FLOW.4 netflow v9 packet sent
IP flow4_srvr_ip	1.3.6.1.4.1.2007.1.4.218.1.4.1	IpAddress	accessible-for-notify	Parameter 'srvr-ip' in event FLOW.4
I32 flow4_srvr_port	1.3.6.1.4.1.2007.1.4.218.1.4.2	Integer32	accessible-for-notify	Parameter 'srvr-port' in event FLOW.4
I32 flow4_length	1.3.6.1.4.1.2007.1.4.218.1.4.3	Integer32	accessible-for-notify	Parameter 'length' in event FLOW.4
I32 flow4_flows	1.3.6.1.4.1.2007.1.4.218.1.4.4	Integer32	accessible-for-notify	Parameter 'flows' in event FLOW.4
STR flow4_template	1.3.6.1.4.1.2007.1.4.218.1.4.5	DisplayString	accessible-for-notify	Parameter 'template' in event FLOW.4
flowEventObjects5	1.3.6.1.4.1.2007.1.4.218.1.5			Event FLOW.5 netflow v5 packet sent
IP flow5_srvr_ip	1.3.6.1.4.1.2007.1.4.218.1.5.1	IpAddress	accessible-for-notify	Parameter 'srvr-ip' in event FLOW.5
I32 flow5_srvr_port	1.3.6.1.4.1.2007.1.4.218.1.5.2	Integer32	accessible-for-notify	Parameter 'srvr-port' in event FLOW.5
I32 flow5_length	1.3.6.1.4.1.2007.1.4.218.1.5.3	Integer32	accessible-for-notify	Parameter 'length' in event FLOW.5
I32 flow5_flows	1.3.6.1.4.1.2007.1.4.218.1.5.4	Integer32	accessible-for-notify	Parameter 'flows' in event FLOW.5
flowEventObjects6	1.3.6.1.4.1.2007.1.4.218.1.6			Event FLOW.6 flow deleted
IP flow6_source_ip	1.3.6.1.4.1.2007.1.4.218.1.6.1	IpAddress	accessible-for-notify	Parameter 'source-ip' in event FLOW.6
IP flow6_destination_ip	1.3.6.1.4.1.2007.1.4.218.1.6.2	IpAddress	accessible-for-notify	Parameter 'destination-ip' in event FLOW.6
STR flow6_protocol	1.3.6.1.4.1.2007.1.4.218.1.6.3	DisplayString	accessible-for-notify	Parameter 'protocol' in event FLOW.6
flowEventObjects7	1.3.6.1.4.1.2007.1.4.218.1.7			Event FLOW.7 an ip fragment has been ignored
IP flow7_source_ip	1.3.6.1.4.1.2007.1.4.218.1.7.1	IpAddress	accessible-for-notify	Parameter 'source-ip' in event FLOW.7
IP flow7_destination_ip	1.3.6.1.4.1.2007.1.4.218.1.7.2	IpAddress	accessible-for-notify	Parameter 'destination-ip' in event FLOW.7
STR flow7_protocol	1.3.6.1.4.1.2007.1.4.218.1.7.3	DisplayString	accessible-for-notify	Parameter 'protocol' in event FLOW.7
flowEventObjects8	1.3.6.1.4.1.2007.1.4.218.1.8			Event FLOW.8 an ipsec packet has been ignored
IP flow8_source_ip	1.3.6.1.4.1.2007.1.4.218.1.8.1	IpAddress	accessible-for-notify	Parameter 'source-ip' in event FLOW.8
IP flow8_destination_ip	1.3.6.1.4.1.2007.1.4.218.1.8.2	IpAddress	accessible-for-notify	Parameter 'destination-ip' in event FLOW.8
STR flow8_protocol	1.3.6.1.4.1.2007.1.4.218.1.8.3	DisplayString	accessible-for-notify	Parameter 'protocol' in event FLOW.8
flowEventObjects9	1.3.6.1.4.1.2007.1.4.218.1.9			Event FLOW.9 ip packtet ignored due to sampling
IP flow9_source_ip	1.3.6.1.4.1.2007.1.4.218.1.9.1	IpAddress	accessible-for-notify	Parameter 'source-ip' in event FLOW.9
IP flow9_destination_ip	1.3.6.1.4.1.2007.1.4.218.1.9.2	IpAddress	accessible-for-notify	Parameter 'destination-ip' in event FLOW.9
STR flow9_protocol	1.3.6.1.4.1.2007.1.4.218.1.9.3	DisplayString	accessible-for-notify	Parameter 'protocol' in event FLOW.9
I32 flow9_sampling_factor	1.3.6.1.4.1.2007.1.4.218.1.9.4	Integer32	accessible-for-notify	Parameter 'sampling-factor' in event FLOW.9
flowNotifications	1.3.6.1.4.1.2007.1.4.218.2
flowNotificationsPrefix	1.3.6.1.4.1.2007.1.4.218.2.0
NTF flowNotification1	1.3.6.1.4.1.2007.1.4.218.2.0.1			Notification of Event FLOW.1 Message: 'Client $1' Parameters list: $1: flow1-state client state changed
NTF flowNotification2	1.3.6.1.4.1.2007.1.4.218.2.0.2			Notification of Event FLOW.2 Message: 'New flow created $1->$2 protocol $3 expiry $4' Parameters list: $1: flow2-source-ip $2: flow2-destination-ip $3: flow2-protocol $4: flow2-expiry new flow created
NTF flowNotification3	1.3.6.1.4.1.2007.1.4.218.2.0.3			Notification of Event FLOW.3 Message: 'Flow matched $1->$2 protocol $3 expiry $4' Parameters list: $1: flow3-source-ip $2: flow3-destination-ip $3: flow3-protocol $4: flow3-expiry flow matched
NTF flowNotification4	1.3.6.1.4.1.2007.1.4.218.2.0.4			Notification of Event FLOW.4 Message: 'NetflowV9 packet sent to $1:$2 length $3 number of flows $4 template $5' Parameters list: $1: flow4-srvr-ip $2: flow4-srvr-port $3: flow4-length $4: flow4-flows $5: flow4-template netflow v9 packet sent
NTF flowNotification5	1.3.6.1.4.1.2007.1.4.218.2.0.5			Notification of Event FLOW.5 Message: 'NetflowV5 packet sent to $1:$2 length $3 number of flows $4' Parameters list: $1: flow5-srvr-ip $2: flow5-srvr-port $3: flow5-length $4: flow5-flows netflow v5 packet sent
NTF flowNotification6	1.3.6.1.4.1.2007.1.4.218.2.0.6			Notification of Event FLOW.6 Message: 'Flow deleted $1->$2 protocol $3' Parameters list: $1: flow6-source-ip $2: flow6-destination-ip $3: flow6-protocol flow deleted
NTF flowNotification7	1.3.6.1.4.1.2007.1.4.218.2.0.7			Notification of Event FLOW.7 Message: 'IP fragment ignored $1->$2 protocol $3' Parameters list: $1: flow7-source-ip $2: flow7-destination-ip $3: flow7-protocol an ip fragment has been ignored
NTF flowNotification8	1.3.6.1.4.1.2007.1.4.218.2.0.8			Notification of Event FLOW.8 Message: 'Ipsec packet ignored $1->$2 protocol $3' Parameters list: $1: flow8-source-ip $2: flow8-destination-ip $3: flow8-protocol an ipsec packet has been ignored
NTF flowNotification9	1.3.6.1.4.1.2007.1.4.218.2.0.9			Notification of Event FLOW.9 Message: 'IP packet sampled $1->$2 protocol $3 factor $4' Parameters list: $1: flow9-source-ip $2: flow9-destination-ip $3: flow9-protocol $4: flow9-sampling-factor ip packtet ignored due to sampling
NTF flowNotification10	1.3.6.1.4.1.2007.1.4.218.2.0.10			Notification of Event FLOW.10 Message: 'IP packet procesing error' ip packtet processing error

RFC description

Teldat FLOW event subsystem SNMP notifications for network flow monitoring.

Start monitoring Teldat router (NAT/firewall traffic-flow state-change 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-FLOW-MIB

What Is TELDAT-TRAP-FLOW-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description