TELDAT-TRAP-BAN-MIB

All MIBs › TELDAT-TRAP-BAN-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Teldat Router Management, Teldat Trap Notifications

Description: Defines Teldat router BAN (bandwidth management) 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-BAN-MIB?

TELDAT-TRAP-BAN-MIB is a Teldat router-specific MIB defining SNMP trap notifications generated by the router's bridge-layer event subsystem (the object naming convention 'ban' reflects Teldat's internal event source rather than a bandwidth-management feature). It exposes per-event varbind data captured at trigger time: bridge port, frame direction, frame length, source and destination MAC addresses, SAP values, and RIF (Route Information Field) routing data. Its monitoring role is oriented toward layer-2 fault and security event detection rather than classic hardware health metrics like temperature or CPU — traps fire when the bridging subsystem observes anomalous frames, letting an operator flag issues such as unexpected MAC pairs, bridging loops, or spoofed source addresses on a specific port. It is built on Teldat's private enterprise MIB tree and assumes an underlying 802.1D-style bridge implementation providing the event source data. It's deployed on Teldat routers/bridges in branch-office and WAN environments where layer-2 bridging is active and SNMP trap monitoring is used to catch anomalous bridged traffic. Network engineers evaluating or troubleshooting this functionality can download the TELDAT-TRAP-BAN-MIB file directly to load it into their MIB browser.

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

Monitoring Examples

When a banNotifications trap fires, its varbinds ban1-source-mac-address and ban1-dest-mac-address identify the MAC pair involved while ban1-bridge-port names the port where the event occurred; ban1-direction and ban1-len describe the frame's direction and size. An admin seeing repeated traps referencing the same unexpected source MAC across different ban1-bridge-port values would suspect MAC spoofing or a bridging loop on that segment.

What Can Be Monitored

bridge event source/destination MAC address
bridge port of triggering frame
frame direction and length
SAP and RIF data of triggering frame

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
banTrapsMIB	1.3.6.1.4.1.2007.1.4.109			This Module Information Base file is defined for managing received SNMP notifications generated by the BAN event subsystem.
banEventsGroup	1.3.6.1.4.1.2007.1.4.109.1
banEventObjects1	1.3.6.1.4.1.2007.1.4.109.1.1			Event BAN.1 I-frame packet. Direction is 'in' or 'out' of the router. Shows the bridge port number. Shows the full RIF (routing information field) of the packet. Shows up to 20 bytes of the packet after the SSAP field. The length is the amount of data in the packet after the SSAP field in the packet.
STR ban1_direction	1.3.6.1.4.1.2007.1.4.109.1.1.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.1
I32 ban1_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.1.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.1
I32 ban1_len	1.3.6.1.4.1.2007.1.4.109.1.1.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.1
STR ban1_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.1.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.1
STR ban1_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.1.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.1
I32 ban1_source_sap	1.3.6.1.4.1.2007.1.4.109.1.1.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.1
I32 ban1_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.1.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.1
STR ban1_rif_data	1.3.6.1.4.1.2007.1.4.109.1.1.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.1
banEventObjects2	1.3.6.1.4.1.2007.1.4.109.1.2			Event BAN.2 RR packet.
STR ban2_direction	1.3.6.1.4.1.2007.1.4.109.1.2.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.2
I32 ban2_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.2.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.2
I32 ban2_len	1.3.6.1.4.1.2007.1.4.109.1.2.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.2
STR ban2_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.2.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.2
STR ban2_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.2.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.2
I32 ban2_source_sap	1.3.6.1.4.1.2007.1.4.109.1.2.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.2
I32 ban2_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.2.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.2
STR ban2_rif_data	1.3.6.1.4.1.2007.1.4.109.1.2.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.2
banEventObjects3	1.3.6.1.4.1.2007.1.4.109.1.3			Event BAN.3 The configured BAN bridge port is not a bridge port.
I32 ban3_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.3.1	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.3
banEventObjects4	1.3.6.1.4.1.2007.1.4.109.1.4			Event BAN.4 The configured BAN bridge port has been initialized from a BAN point of view.
I32 ban4_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.4.1	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.4
banEventObjects5	1.3.6.1.4.1.2007.1.4.109.1.5			Event BAN.5 Every frame sent by the NCP must match the configured Boundary Node Identifier (BNI) MAC address.
STR ban5_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.5.1	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.5
STR ban5_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.5.2	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.5
STR ban5_bni_mac	1.3.6.1.4.1.2007.1.4.109.1.5.3	DisplayString	accessible-for-notify	Parameter 'bni-mac' in event BAN.5
I32 ban5_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.5.4	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.5
banEventObjects6	1.3.6.1.4.1.2007.1.4.109.1.6			Event BAN.6 The configured BAN bridge port is not a Frame Relay DLCI bridge port.
I32 ban6_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.6.1	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.6
banEventObjects8	1.3.6.1.4.1.2007.1.4.109.1.8			Event BAN.8 The outgoing frame was filtered by BAN because it was NOT an RFC 1490 bridged Token-Ring frame, without preserved FCS, which is OUI type 9. This is the only type of frame expected by the NCP. Another bridge type frame is being sent: 1 and 7 are Ethernet, 2 and 8 are 802.4, 3 is Token-Ring with FCS, 4 and 10 are FDDI, 11 is 802.6, 14 is 802.1d Hello BPDU, 15 is SRB Hello BPDU.
I32 ban8_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.8.1	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.8
I32 ban8_oui_type	1.3.6.1.4.1.2007.1.4.109.1.8.2	Integer32	accessible-for-notify	Parameter 'oui-type' in event BAN.8
banEventObjects9	1.3.6.1.4.1.2007.1.4.109.1.9			Event BAN.9 The outgoing frame was filtered by BAN because the frame's destination address did not equal the BAN DLCI address. This is done to protect the NCP.
STR ban9_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.9.1	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.9
STR ban9_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.9.2	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.9
I32 ban9_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.9.3	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.9
STR ban9_ban_dlci_address	1.3.6.1.4.1.2007.1.4.109.1.9.4	DisplayString	accessible-for-notify	Parameter 'ban-dlci-address' in event BAN.9
banEventObjects10	1.3.6.1.4.1.2007.1.4.109.1.10			Event BAN.10 The BAN bridge port behavior is being dynamically forced to transparent bridging off, spanning tree off. This is required for BAN.
I32 ban10_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.10.1	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.10
banEventObjects11	1.3.6.1.4.1.2007.1.4.109.1.11			Event BAN.11 The BAN bridge port is configured for DLSw terminated. However, DLSw is not in this build.
I32 ban11_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.11.1	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.11
banEventObjects13	1.3.6.1.4.1.2007.1.4.109.1.13			Event BAN.13 The outgoing frame was filtered by BAN because the BAN port is set to DLSw switching, but the frame was not a DLSw frame since the DLSw source routing segment and bridge number were not in the RIF (routing information field) of the frame. This is done to protect the NCP.
STR ban13_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.13.1	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.13
STR ban13_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.13.2	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.13
I32 ban13_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.13.3	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.13
I32 ban13_segment_ban	1.3.6.1.4.1.2007.1.4.109.1.13.4	Integer32	accessible-for-notify	Parameter 'segment-ban' in event BAN.13
STR ban13_rif_data	1.3.6.1.4.1.2007.1.4.109.1.13.5	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.13
banEventObjects14	1.3.6.1.4.1.2007.1.4.109.1.14			Event BAN.14 RNR packet.
STR ban14_direction	1.3.6.1.4.1.2007.1.4.109.1.14.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.14
I32 ban14_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.14.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.14
I32 ban14_len	1.3.6.1.4.1.2007.1.4.109.1.14.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.14
STR ban14_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.14.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.14
STR ban14_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.14.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.14
I32 ban14_source_sap	1.3.6.1.4.1.2007.1.4.109.1.14.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.14
I32 ban14_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.14.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.14
STR ban14_rif_data	1.3.6.1.4.1.2007.1.4.109.1.14.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.14
banEventObjects15	1.3.6.1.4.1.2007.1.4.109.1.15			Event BAN.15 REJ packet.
STR ban15_direction	1.3.6.1.4.1.2007.1.4.109.1.15.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.15
I32 ban15_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.15.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.15
I32 ban15_len	1.3.6.1.4.1.2007.1.4.109.1.15.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.15
STR ban15_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.15.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.15
STR ban15_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.15.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.15
I32 ban15_source_sap	1.3.6.1.4.1.2007.1.4.109.1.15.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.15
I32 ban15_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.15.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.15
STR ban15_rif_data	1.3.6.1.4.1.2007.1.4.109.1.15.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.15
banEventObjects16	1.3.6.1.4.1.2007.1.4.109.1.16			Event BAN.16 TEST-C (Test command) packet.
STR ban16_direction	1.3.6.1.4.1.2007.1.4.109.1.16.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.16
I32 ban16_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.16.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.16
I32 ban16_len	1.3.6.1.4.1.2007.1.4.109.1.16.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.16
STR ban16_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.16.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.16
STR ban16_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.16.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.16
I32 ban16_source_sap	1.3.6.1.4.1.2007.1.4.109.1.16.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.16
I32 ban16_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.16.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.16
STR ban16_rif_data	1.3.6.1.4.1.2007.1.4.109.1.16.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.16
banEventObjects17	1.3.6.1.4.1.2007.1.4.109.1.17			Event BAN.17 TEST-R (Test response) packet.
STR ban17_direction	1.3.6.1.4.1.2007.1.4.109.1.17.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.17
I32 ban17_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.17.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.17
I32 ban17_len	1.3.6.1.4.1.2007.1.4.109.1.17.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.17
STR ban17_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.17.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.17
STR ban17_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.17.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.17
I32 ban17_source_sap	1.3.6.1.4.1.2007.1.4.109.1.17.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.17
I32 ban17_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.17.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.17
STR ban17_rif_data	1.3.6.1.4.1.2007.1.4.109.1.17.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.17
banEventObjects18	1.3.6.1.4.1.2007.1.4.109.1.18			Event BAN.18 XID-C (XID command) packet.
STR ban18_direction	1.3.6.1.4.1.2007.1.4.109.1.18.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.18
I32 ban18_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.18.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.18
I32 ban18_len	1.3.6.1.4.1.2007.1.4.109.1.18.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.18
STR ban18_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.18.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.18
STR ban18_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.18.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.18
I32 ban18_source_sap	1.3.6.1.4.1.2007.1.4.109.1.18.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.18
I32 ban18_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.18.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.18
STR ban18_rif_data	1.3.6.1.4.1.2007.1.4.109.1.18.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.18
banEventObjects19	1.3.6.1.4.1.2007.1.4.109.1.19			Event BAN.19 XID-R (XID response) packet.
STR ban19_direction	1.3.6.1.4.1.2007.1.4.109.1.19.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.19
I32 ban19_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.19.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.19
I32 ban19_len	1.3.6.1.4.1.2007.1.4.109.1.19.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.19
STR ban19_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.19.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.19
STR ban19_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.19.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.19
I32 ban19_source_sap	1.3.6.1.4.1.2007.1.4.109.1.19.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.19
I32 ban19_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.19.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.19
STR ban19_rif_data	1.3.6.1.4.1.2007.1.4.109.1.19.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.19
banEventObjects20	1.3.6.1.4.1.2007.1.4.109.1.20			Event BAN.20 SABME packet.
STR ban20_direction	1.3.6.1.4.1.2007.1.4.109.1.20.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.20
I32 ban20_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.20.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.20
I32 ban20_len	1.3.6.1.4.1.2007.1.4.109.1.20.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.20
STR ban20_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.20.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.20
STR ban20_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.20.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.20
I32 ban20_source_sap	1.3.6.1.4.1.2007.1.4.109.1.20.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.20
I32 ban20_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.20.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.20
STR ban20_rif_data	1.3.6.1.4.1.2007.1.4.109.1.20.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.20
banEventObjects21	1.3.6.1.4.1.2007.1.4.109.1.21			Event BAN.21 UA packet.
STR ban21_direction	1.3.6.1.4.1.2007.1.4.109.1.21.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.21
I32 ban21_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.21.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.21
I32 ban21_len	1.3.6.1.4.1.2007.1.4.109.1.21.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.21
STR ban21_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.21.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.21
STR ban21_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.21.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.21
I32 ban21_source_sap	1.3.6.1.4.1.2007.1.4.109.1.21.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.21
I32 ban21_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.21.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.21
STR ban21_rif_data	1.3.6.1.4.1.2007.1.4.109.1.21.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.21
banEventObjects22	1.3.6.1.4.1.2007.1.4.109.1.22			Event BAN.22 DM packet.
STR ban22_direction	1.3.6.1.4.1.2007.1.4.109.1.22.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.22
I32 ban22_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.22.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.22
I32 ban22_len	1.3.6.1.4.1.2007.1.4.109.1.22.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.22
STR ban22_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.22.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.22
STR ban22_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.22.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.22
I32 ban22_source_sap	1.3.6.1.4.1.2007.1.4.109.1.22.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.22
I32 ban22_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.22.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.22
STR ban22_rif_data	1.3.6.1.4.1.2007.1.4.109.1.22.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.22
banEventObjects23	1.3.6.1.4.1.2007.1.4.109.1.23			Event BAN.23 DISC packet.
STR ban23_direction	1.3.6.1.4.1.2007.1.4.109.1.23.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.23
I32 ban23_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.23.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.23
I32 ban23_len	1.3.6.1.4.1.2007.1.4.109.1.23.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.23
STR ban23_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.23.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.23
STR ban23_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.23.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.23
I32 ban23_source_sap	1.3.6.1.4.1.2007.1.4.109.1.23.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.23
I32 ban23_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.23.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.23
STR ban23_rif_data	1.3.6.1.4.1.2007.1.4.109.1.23.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.23
banEventObjects24	1.3.6.1.4.1.2007.1.4.109.1.24			Event BAN.24 FRMR packet.
STR ban24_direction	1.3.6.1.4.1.2007.1.4.109.1.24.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.24
I32 ban24_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.24.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.24
I32 ban24_len	1.3.6.1.4.1.2007.1.4.109.1.24.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.24
STR ban24_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.24.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.24
STR ban24_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.24.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.24
I32 ban24_source_sap	1.3.6.1.4.1.2007.1.4.109.1.24.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.24
I32 ban24_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.24.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.24
STR ban24_rif_data	1.3.6.1.4.1.2007.1.4.109.1.24.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.24
banEventObjects25	1.3.6.1.4.1.2007.1.4.109.1.25			Event BAN.25 Other packet than those specifically called out above. Look at the data shown to determine exactly what type of frame it is.
STR ban25_direction	1.3.6.1.4.1.2007.1.4.109.1.25.1	DisplayString	accessible-for-notify	Parameter 'direction' in event BAN.25
I32 ban25_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.25.2	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.25
I32 ban25_len	1.3.6.1.4.1.2007.1.4.109.1.25.3	Integer32	accessible-for-notify	Parameter 'len' in event BAN.25
STR ban25_source_mac_address	1.3.6.1.4.1.2007.1.4.109.1.25.4	DisplayString	accessible-for-notify	Parameter 'source-mac-address' in event BAN.25
STR ban25_dest_mac_address	1.3.6.1.4.1.2007.1.4.109.1.25.5	DisplayString	accessible-for-notify	Parameter 'dest-mac-address' in event BAN.25
I32 ban25_source_sap	1.3.6.1.4.1.2007.1.4.109.1.25.6	Integer32	accessible-for-notify	Parameter 'source-sap' in event BAN.25
I32 ban25_dest_sap	1.3.6.1.4.1.2007.1.4.109.1.25.7	Integer32	accessible-for-notify	Parameter 'dest-sap' in event BAN.25
STR ban25_rif_data	1.3.6.1.4.1.2007.1.4.109.1.25.8	DisplayString	accessible-for-notify	Parameter 'rif-data' in event BAN.25
banEventObjects26	1.3.6.1.4.1.2007.1.4.109.1.26			Event BAN.26 All frames are being dropped. The port has been configured for DLSw termination, but DLSw is not running.
I32 ban26_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.26.1	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.26
banEventObjects27	1.3.6.1.4.1.2007.1.4.109.1.27			Event BAN.27 The configured BAN bridge port is not a source routing bridge port.
I32 ban27_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.27.1	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.27
banEventObjects28	1.3.6.1.4.1.2007.1.4.109.1.28			Event BAN.28 All bridged frames, in and out, are being dropped. The BAN port did not initialize.
I32 ban28_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.28.1	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.28
banEventObjects29	1.3.6.1.4.1.2007.1.4.109.1.29			Event BAN.29 When SR-TB conversion is enabled on the bridge, the BAN DLCI MAC address of the bridging DLCI must be unique. This restriction does not apply if SR-TB is disabled.
I32 ban29_bridge_port	1.3.6.1.4.1.2007.1.4.109.1.29.1	Integer32	accessible-for-notify	Parameter 'bridge-port' in event BAN.29
STR ban29_ban_dlci_address	1.3.6.1.4.1.2007.1.4.109.1.29.2	DisplayString	accessible-for-notify	Parameter 'ban-dlci-address' in event BAN.29
banNotifications	1.3.6.1.4.1.2007.1.4.109.2
banNotificationsPrefix	1.3.6.1.4.1.2007.1.4.109.2.0
NTF banNotification1	1.3.6.1.4.1.2007.1.4.109.2.0.1			Notification of Event BAN.1 Message: 'T$1:I-FRAME port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban1-direction $2: ban1-bridge-port $3: ban1-len $4: ban1-source-mac-address $5: ban1-dest-mac-address $6: ban1-source-sap $7: ban1-dest-sap $8: ban1-rif-data I-frame packet. Direction is 'in' or 'out' of the router. Shows the bridge port number. Shows the full RIF (routing information field) of the packet. Shows up to 20 bytes of the packet after the SSAP field. The length is the amount of data in the packet after the SSAP field in the packet.
NTF banNotification2	1.3.6.1.4.1.2007.1.4.109.2.0.2			Notification of Event BAN.2 Message: 'T$1:RR port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban2-direction $2: ban2-bridge-port $3: ban2-len $4: ban2-source-mac-address $5: ban2-dest-mac-address $6: ban2-source-sap $7: ban2-dest-sap $8: ban2-rif-data RR packet.
NTF banNotification3	1.3.6.1.4.1.2007.1.4.109.2.0.3			Notification of Event BAN.3 Message: 'port $1 is not a bridge port' Parameters list: $1: ban3-bridge-port The configured BAN bridge port is not a bridge port.
NTF banNotification4	1.3.6.1.4.1.2007.1.4.109.2.0.4			Notification of Event BAN.4 Message: 'port $1 initialized' Parameters list: $1: ban4-bridge-port The configured BAN bridge port has been initialized from a BAN point of view.
NTF banNotification5	1.3.6.1.4.1.2007.1.4.109.2.0.5			Notification of Event BAN.5 Message: 'frame dropped $1->$2, not BNI source address $3, port $4' Parameters list: $1: ban5-source-mac-address $2: ban5-dest-mac-address $3: ban5-bni-mac $4: ban5-bridge-port Every frame sent by the NCP must match the configured Boundary Node Identifier (BNI) MAC address.
NTF banNotification6	1.3.6.1.4.1.2007.1.4.109.2.0.6			Notification of Event BAN.6 Message: 'port $1 is not a Frame Relay bridge port' Parameters list: $1: ban6-bridge-port The configured BAN bridge port is not a Frame Relay DLCI bridge port.
NTF banNotification7	1.3.6.1.4.1.2007.1.4.109.2.0.7			Notification of Event BAN.7 Message: '---' Reserved for possible future use.
NTF banNotification8	1.3.6.1.4.1.2007.1.4.109.2.0.8			Notification of Event BAN.8 Message: 'frame filtered, port $1, OUI bridge type $2' Parameters list: $1: ban8-bridge-port $2: ban8-oui-type The outgoing frame was filtered by BAN because it was NOT an RFC 1490 bridged Token-Ring frame, without preserved FCS, which is OUI type 9. This is the only type of frame expected by the NCP. Another bridge type frame is being sent: 1 and 7 are Ethernet, 2 and 8 are 802.4, 3 is Token-Ring with FCS, 4 and 10 are FDDI, 11 is 802.6, 14 is 802.1d Hello BPDU, 15 is SRB Hello BPDU.
NTF banNotification9	1.3.6.1.4.1.2007.1.4.109.2.0.9			Notification of Event BAN.9 Message: 'frame filtered $1->$2, port $3, da not BAN DLCI address $4' Parameters list: $1: ban9-source-mac-address $2: ban9-dest-mac-address $3: ban9-bridge-port $4: ban9-ban-dlci-address The outgoing frame was filtered by BAN because the frame's destination address did not equal the BAN DLCI address. This is done to protect the NCP.
NTF banNotification10	1.3.6.1.4.1.2007.1.4.109.2.0.10			Notification of Event BAN.10 Message: 'port $1 forcing: TB,STP off' Parameters list: $1: ban10-bridge-port The BAN bridge port behavior is being dynamically forced to transparent bridging off, spanning tree off. This is required for BAN.
NTF banNotification11	1.3.6.1.4.1.2007.1.4.109.2.0.11			Notification of Event BAN.11 Message: 'port $1 DLSw term but DLSw is not in the build' Parameters list: $1: ban11-bridge-port The BAN bridge port is configured for DLSw terminated. However, DLSw is not in this build.
NTF banNotification12	1.3.6.1.4.1.2007.1.4.109.2.0.12			Notification of Event BAN.12 Message: '---' Reserved for possible future use.
NTF banNotification13	1.3.6.1.4.1.2007.1.4.109.2.0.13			Notification of Event BAN.13 Message: 'frame filtered $1->$2, port $3, DLSw snbn $4 not in RIF $5' Parameters list: $1: ban13-source-mac-address $2: ban13-dest-mac-address $3: ban13-bridge-port $4: ban13-segment-ban $5: ban13-rif-data The outgoing frame was filtered by BAN because the BAN port is set to DLSw switching, but the frame was not a DLSw frame since the DLSw source routing segment and bridge number were not in the RIF (routing information field) of the frame. This is done to protect the NCP.
NTF banNotification14	1.3.6.1.4.1.2007.1.4.109.2.0.14			Notification of Event BAN.14 Message: 'T$1:RNR port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban14-direction $2: ban14-bridge-port $3: ban14-len $4: ban14-source-mac-address $5: ban14-dest-mac-address $6: ban14-source-sap $7: ban14-dest-sap $8: ban14-rif-data RNR packet.
NTF banNotification15	1.3.6.1.4.1.2007.1.4.109.2.0.15			Notification of Event BAN.15 Message: 'T$1:REJ port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban15-direction $2: ban15-bridge-port $3: ban15-len $4: ban15-source-mac-address $5: ban15-dest-mac-address $6: ban15-source-sap $7: ban15-dest-sap $8: ban15-rif-data REJ packet.
NTF banNotification16	1.3.6.1.4.1.2007.1.4.109.2.0.16			Notification of Event BAN.16 Message: 'T$1:TST-C port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban16-direction $2: ban16-bridge-port $3: ban16-len $4: ban16-source-mac-address $5: ban16-dest-mac-address $6: ban16-source-sap $7: ban16-dest-sap $8: ban16-rif-data TEST-C (Test command) packet.
NTF banNotification17	1.3.6.1.4.1.2007.1.4.109.2.0.17			Notification of Event BAN.17 Message: 'T$1:TST-R port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban17-direction $2: ban17-bridge-port $3: ban17-len $4: ban17-source-mac-address $5: ban17-dest-mac-address $6: ban17-source-sap $7: ban17-dest-sap $8: ban17-rif-data TEST-R (Test response) packet.
NTF banNotification18	1.3.6.1.4.1.2007.1.4.109.2.0.18			Notification of Event BAN.18 Message: 'T$1:XID-C port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban18-direction $2: ban18-bridge-port $3: ban18-len $4: ban18-source-mac-address $5: ban18-dest-mac-address $6: ban18-source-sap $7: ban18-dest-sap $8: ban18-rif-data XID-C (XID command) packet.
NTF banNotification19	1.3.6.1.4.1.2007.1.4.109.2.0.19			Notification of Event BAN.19 Message: 'T$1:XID-R port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban19-direction $2: ban19-bridge-port $3: ban19-len $4: ban19-source-mac-address $5: ban19-dest-mac-address $6: ban19-source-sap $7: ban19-dest-sap $8: ban19-rif-data XID-R (XID response) packet.
NTF banNotification20	1.3.6.1.4.1.2007.1.4.109.2.0.20			Notification of Event BAN.20 Message: 'T$1:SABME port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban20-direction $2: ban20-bridge-port $3: ban20-len $4: ban20-source-mac-address $5: ban20-dest-mac-address $6: ban20-source-sap $7: ban20-dest-sap $8: ban20-rif-data SABME packet.
NTF banNotification21	1.3.6.1.4.1.2007.1.4.109.2.0.21			Notification of Event BAN.21 Message: 'T$1:UA port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban21-direction $2: ban21-bridge-port $3: ban21-len $4: ban21-source-mac-address $5: ban21-dest-mac-address $6: ban21-source-sap $7: ban21-dest-sap $8: ban21-rif-data UA packet.
NTF banNotification22	1.3.6.1.4.1.2007.1.4.109.2.0.22			Notification of Event BAN.22 Message: 'T$1:DM port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban22-direction $2: ban22-bridge-port $3: ban22-len $4: ban22-source-mac-address $5: ban22-dest-mac-address $6: ban22-source-sap $7: ban22-dest-sap $8: ban22-rif-data DM packet.
NTF banNotification23	1.3.6.1.4.1.2007.1.4.109.2.0.23			Notification of Event BAN.23 Message: 'T$1:DISC port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban23-direction $2: ban23-bridge-port $3: ban23-len $4: ban23-source-mac-address $5: ban23-dest-mac-address $6: ban23-source-sap $7: ban23-dest-sap $8: ban23-rif-data DISC packet.
NTF banNotification24	1.3.6.1.4.1.2007.1.4.109.2.0.24			Notification of Event BAN.24 Message: 'T$1:FRMR port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban24-direction $2: ban24-bridge-port $3: ban24-len $4: ban24-source-mac-address $5: ban24-dest-mac-address $6: ban24-source-sap $7: ban24-dest-sap $8: ban24-rif-data FRMR packet.
NTF banNotification25	1.3.6.1.4.1.2007.1.4.109.2.0.25			Notification of Event BAN.25 Message: 'T$1:OTHER port=$2 len=$3 $4->$5 $6->$7 $8' Parameters list: $1: ban25-direction $2: ban25-bridge-port $3: ban25-len $4: ban25-source-mac-address $5: ban25-dest-mac-address $6: ban25-source-sap $7: ban25-dest-sap $8: ban25-rif-data Other packet than those specifically called out above. Look at the data shown to determine exactly what type of frame it is.
NTF banNotification26	1.3.6.1.4.1.2007.1.4.109.2.0.26			Notification of Event BAN.26 Message: 'frame dropped, port $1, port is DLSw term, but DLSw is not initialized' Parameters list: $1: ban26-bridge-port All frames are being dropped. The port has been configured for DLSw termination, but DLSw is not running.
NTF banNotification27	1.3.6.1.4.1.2007.1.4.109.2.0.27			Notification of Event BAN.27 Message: 'port $1 is not a source routing bridge port' Parameters list: $1: ban27-bridge-port The configured BAN bridge port is not a source routing bridge port.
NTF banNotification28	1.3.6.1.4.1.2007.1.4.109.2.0.28			Notification of Event BAN.28 Message: 'frame dropped, port $1, port is not initialized' Parameters list: $1: ban28-bridge-port All bridged frames, in and out, are being dropped. The BAN port did not initialize.
NTF banNotification29	1.3.6.1.4.1.2007.1.4.109.2.0.29			Notification of Event BAN.29 Message: 'port $1, BAN DLCI address $2 is a duplicate with SR-TB enabled' Parameters list: $1: ban29-bridge-port $2: ban29-ban-dlci-address When SR-TB conversion is enabled on the bridge, the BAN DLCI MAC address of the bridging DLCI must be unique. This restriction does not apply if SR-TB is disabled.

RFC description

Event notification management for Teldat BAN subsystem capturing bridged frame and packet analysis event traps.

Start monitoring Teldat router/bridge (bridge-layer frame/MAC anomaly 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-BAN-MIB

What Is TELDAT-TRAP-BAN-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description