All MIBs › TELDAT-TRAP-L2TP-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 L2TP tunnel 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-L2TP-MIB?
TELDAT-TRAP-L2TP-MIB is a Teldat-specific notification-only MIB defining SNMP traps generated by the router's L2TP (Layer 2 Tunneling Protocol) event subsystem, used for tunneling PPP sessions such as remote-access VPNs. It contains no polled data tables, only numbered trap definitions (l2tp2 through l2tp7 in the sample set) carrying varbinds like tunnel ID, packet type, remote IP address, diagnostic message, and old/new tunnel state. Its monitoring value is fault/event-oriented: these traps notify an operator when an L2TP tunnel changes state or when diagnostic conditions occur, which is directly useful for detecting VPN tunnel instability or unexpected disconnects. It depends on the underlying L2TP tunneling implementation and typically works alongside PPP session monitoring for the tunneled sessions. It is deployed on Teldat routers acting as L2TP servers or clients for remote-access or site-to-site VPN tunnels, and administrators can get the TELDAT-TRAP-L2TP-MIB download to configure trap monitoring in their SNMP tools.
IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-L2TP-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 acting as L2TP tunnel endpoint
Monitoring Examples
As a trap-only MIB with no data tables, monitoring means capturing events at an SNMP trap receiver: l2tp6-TunnelID paired with l2tp6-OldState and l2tp6-NewState reports a tunnel's state transition, letting an administrator detect a tunnel that unexpectedly dropped from an established to a down state. l2tp3-RemoteIPAddress and l2tp3-Packet-type on other trap variants identify which remote peer and packet type triggered an event, useful for pinpointing a specific misbehaving VPN peer. l2tp2-DiagnosticMessage would carry a human-readable diagnostic string for troubleshooting a specific failure. l2tpEventsGroup defines the overall set of L2TP trap events the device can emit.
This MIB depends on
Related MIBs
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 |
|---|---|---|---|---|
| l2tpTrapsMIB | 1.3.6.1.4.1.2007.1.4.172 | This Module Information Base file is defined for managing received SNMP notifications generated by the L2TP event subsystem. | ||
| l2tpEventsGroup | 1.3.6.1.4.1.2007.1.4.172.1 | |||
| l2tpEventObjects2 | 1.3.6.1.4.1.2007.1.4.172.1.2 | Event L2TP.2 The error printed occurred while reading the configuration. | ||
| STR l2tp2_DiagnosticMessage | 1.3.6.1.4.1.2007.1.4.172.1.2.1 | DisplayString | accessible-for-notify | Parameter 'DiagnosticMessage' in event L2TP.2 |
| l2tpEventObjects3 | 1.3.6.1.4.1.2007.1.4.172.1.3 | Event L2TP.3 A packet has been received from a remote peer. Local Tunnel ID, packet type and peer IP address are shown in this message. | ||
| I32 l2tp3_TunnelID | 1.3.6.1.4.1.2007.1.4.172.1.3.1 | Integer32 | accessible-for-notify | Parameter 'TunnelID' in event L2TP.3 |
| STR l2tp3_Packet_type | 1.3.6.1.4.1.2007.1.4.172.1.3.2 | DisplayString | accessible-for-notify | Parameter 'Packet-type' in event L2TP.3 |
| IP l2tp3_RemoteIPAddress | 1.3.6.1.4.1.2007.1.4.172.1.3.3 | IpAddress | accessible-for-notify | Parameter 'RemoteIPAddress' in event L2TP.3 |
| l2tpEventObjects4 | 1.3.6.1.4.1.2007.1.4.172.1.4 | Event L2TP.4 A packet has been sent to a remote peer. Local Tunnel ID, packet type and peer IP address are shown in this message. | ||
| I32 l2tp4_TunnelID | 1.3.6.1.4.1.2007.1.4.172.1.4.1 | Integer32 | accessible-for-notify | Parameter 'TunnelID' in event L2TP.4 |
| STR l2tp4_Packet_type | 1.3.6.1.4.1.2007.1.4.172.1.4.2 | DisplayString | accessible-for-notify | Parameter 'Packet-type' in event L2TP.4 |
| IP l2tp4_RemoteIPAddress | 1.3.6.1.4.1.2007.1.4.172.1.4.3 | IpAddress | accessible-for-notify | Parameter 'RemoteIPAddress' in event L2TP.4 |
| l2tpEventObjects5 | 1.3.6.1.4.1.2007.1.4.172.1.5 | Event L2TP.5 A new tunnel has been created. Local Tunnel ID is shown in the message. | ||
| I32 l2tp5_TunnelID | 1.3.6.1.4.1.2007.1.4.172.1.5.1 | Integer32 | accessible-for-notify | Parameter 'TunnelID' in event L2TP.5 |
| l2tpEventObjects6 | 1.3.6.1.4.1.2007.1.4.172.1.6 | Event L2TP.6 The tunnel has changed its state. Local Tunnel ID, old state and new state are shown in the message. | ||
| I32 l2tp6_TunnelID | 1.3.6.1.4.1.2007.1.4.172.1.6.1 | Integer32 | accessible-for-notify | Parameter 'TunnelID' in event L2TP.6 |
| STR l2tp6_OldState | 1.3.6.1.4.1.2007.1.4.172.1.6.2 | DisplayString | accessible-for-notify | Parameter 'OldState' in event L2TP.6 |
| STR l2tp6_NewState | 1.3.6.1.4.1.2007.1.4.172.1.6.3 | DisplayString | accessible-for-notify | Parameter 'NewState' in event L2TP.6 |
| l2tpEventObjects7 | 1.3.6.1.4.1.2007.1.4.172.1.7 | Event L2TP.7 An Start-Control-Connection-Request packet has been received from a remote peer. Peer IP address is shown in the message. | ||
| IP l2tp7_RemoteIPAddress | 1.3.6.1.4.1.2007.1.4.172.1.7.1 | IpAddress | accessible-for-notify | Parameter 'RemoteIPAddress' in event L2TP.7 |
| l2tpEventObjects8 | 1.3.6.1.4.1.2007.1.4.172.1.8 | Event L2TP.8 The router is creating the stuctures for a pseudowire. | ||
| STR l2tp8_pseudowire_name | 1.3.6.1.4.1.2007.1.4.172.1.8.1 | DisplayString | accessible-for-notify | Parameter 'pseudowire-name' in event L2TP.8 |
| STR l2tp8_associated_interface | 1.3.6.1.4.1.2007.1.4.172.1.8.2 | DisplayString | accessible-for-notify | Parameter 'associated-interface' in event L2TP.8 |
| IP l2tp8_source_ip | 1.3.6.1.4.1.2007.1.4.172.1.8.3 | IpAddress | accessible-for-notify | Parameter 'source-ip' in event L2TP.8 |
| IP l2tp8_destination_ip | 1.3.6.1.4.1.2007.1.4.172.1.8.4 | IpAddress | accessible-for-notify | Parameter 'destination-ip' in event L2TP.8 |
| l2tpEventObjects9 | 1.3.6.1.4.1.2007.1.4.172.1.9 | Event L2TP.9 The pseudowire associated interface is now UP. The router tries to establish the pseudoeire session. | ||
| STR l2tp9_interface_name | 1.3.6.1.4.1.2007.1.4.172.1.9.1 | DisplayString | accessible-for-notify | Parameter 'interface-name' in event L2TP.9 |
| STR l2tp9_pseudowire_name | 1.3.6.1.4.1.2007.1.4.172.1.9.2 | DisplayString | accessible-for-notify | Parameter 'pseudowire-name' in event L2TP.9 |
| l2tpEventObjects10 | 1.3.6.1.4.1.2007.1.4.172.1.10 | Event L2TP.10 A session already exists for the pseudowire and not need to be created. | ||
| STR l2tp10_pseudowire_name | 1.3.6.1.4.1.2007.1.4.172.1.10.1 | DisplayString | accessible-for-notify | Parameter 'pseudowire-name' in event L2TP.10 |
| I32 l2tp10_tunnel_id | 1.3.6.1.4.1.2007.1.4.172.1.10.2 | Integer32 | accessible-for-notify | Parameter 'tunnel-id' in event L2TP.10 |
| I32 l2tp10_session_id | 1.3.6.1.4.1.2007.1.4.172.1.10.3 | Integer32 | accessible-for-notify | Parameter 'session-id' in event L2TP.10 |
| l2tpEventObjects11 | 1.3.6.1.4.1.2007.1.4.172.1.11 | Event L2TP.11 The session has changed its state. Local Tunnel/Session IDs, old state and new state are shown in the message. | ||
| I32 l2tp11_TunnelID | 1.3.6.1.4.1.2007.1.4.172.1.11.1 | Integer32 | accessible-for-notify | Parameter 'TunnelID' in event L2TP.11 |
| I32 l2tp11_SessionID | 1.3.6.1.4.1.2007.1.4.172.1.11.2 | Integer32 | accessible-for-notify | Parameter 'SessionID' in event L2TP.11 |
| STR l2tp11_OldState | 1.3.6.1.4.1.2007.1.4.172.1.11.3 | DisplayString | accessible-for-notify | Parameter 'OldState' in event L2TP.11 |
| STR l2tp11_NewState | 1.3.6.1.4.1.2007.1.4.172.1.11.4 | DisplayString | accessible-for-notify | Parameter 'NewState' in event L2TP.11 |
| l2tpEventObjects12 | 1.3.6.1.4.1.2007.1.4.172.1.12 | Event L2TP.12 A new session within a tunnel has been created. Local Tunnel and Session IDs are shown in the message. | ||
| I32 l2tp12_TunnelID | 1.3.6.1.4.1.2007.1.4.172.1.12.1 | Integer32 | accessible-for-notify | Parameter 'TunnelID' in event L2TP.12 |
| I32 l2tp12_SessionID | 1.3.6.1.4.1.2007.1.4.172.1.12.2 | Integer32 | accessible-for-notify | Parameter 'SessionID' in event L2TP.12 |
| l2tpEventObjects13 | 1.3.6.1.4.1.2007.1.4.172.1.13 | Event L2TP.13 The pseudowire cannot be registered in the down net because the net does not allowed registration.. | ||
| STR l2tp13_pseudowire_name | 1.3.6.1.4.1.2007.1.4.172.1.13.1 | DisplayString | accessible-for-notify | Parameter 'pseudowire-name' in event L2TP.13 |
| STR l2tp13_net_name | 1.3.6.1.4.1.2007.1.4.172.1.13.2 | DisplayString | accessible-for-notify | Parameter 'net-name' in event L2TP.13 |
| l2tpEventObjects14 | 1.3.6.1.4.1.2007.1.4.172.1.14 | Event L2TP.14 The pseudowire has been successfully created. | ||
| STR l2tp14_pseudowire_name | 1.3.6.1.4.1.2007.1.4.172.1.14.1 | DisplayString | accessible-for-notify | Parameter 'pseudowire-name' in event L2TP.14 |
| l2tpEventObjects15 | 1.3.6.1.4.1.2007.1.4.172.1.15 | Event L2TP.15 The pseudowire can not be created due to one of the following reasons: the interface is unkown, there is already a peer registered or an internal error. | ||
| STR l2tp15_pseudowire_name | 1.3.6.1.4.1.2007.1.4.172.1.15.1 | DisplayString | accessible-for-notify | Parameter 'pseudowire-name' in event L2TP.15 |
| STR l2tp15_cause_of_error | 1.3.6.1.4.1.2007.1.4.172.1.15.2 | DisplayString | accessible-for-notify | Parameter 'cause-of-error' in event L2TP.15 |
| l2tpEventObjects17 | 1.3.6.1.4.1.2007.1.4.172.1.17 | Event L2TP.17 A tunnel has been deleted. Local Tunnel ID is shown in the message. | ||
| I32 l2tp17_TunnelID | 1.3.6.1.4.1.2007.1.4.172.1.17.1 | Integer32 | accessible-for-notify | Parameter 'TunnelID' in event L2TP.17 |
| l2tpEventObjects18 | 1.3.6.1.4.1.2007.1.4.172.1.18 | Event L2TP.18 A session has been deleted. Local Tunnel and Session IDs are shown in the message. | ||
| I32 l2tp18_TunnelID | 1.3.6.1.4.1.2007.1.4.172.1.18.1 | Integer32 | accessible-for-notify | Parameter 'TunnelID' in event L2TP.18 |
| I32 l2tp18_SessionID | 1.3.6.1.4.1.2007.1.4.172.1.18.2 | Integer32 | accessible-for-notify | Parameter 'SessionID' in event L2TP.18 |
| l2tpEventObjects19 | 1.3.6.1.4.1.2007.1.4.172.1.19 | Event L2TP.19 An L2TP error has occurred. Specific error message follows. | ||
| STR l2tp19_ErrorMessage | 1.3.6.1.4.1.2007.1.4.172.1.19.1 | DisplayString | accessible-for-notify | Parameter 'ErrorMessage' in event L2TP.19 |
| l2tpEventObjects20 | 1.3.6.1.4.1.2007.1.4.172.1.20 | Event L2TP.20 Elastic-store underrun has been detected, the last received packet and a copy will be added to the elastic-store buffer. | ||
| I32 l2tp20_BufferLevel | 1.3.6.1.4.1.2007.1.4.172.1.20.1 | Integer32 | accessible-for-notify | Parameter 'BufferLevel' in event L2TP.20 |
| l2tpEventObjects21 | 1.3.6.1.4.1.2007.1.4.172.1.21 | Event L2TP.21 Elastic-store overrun has been detected, the last received packet will be dropped. | ||
| I32 l2tp21_BufferLevel | 1.3.6.1.4.1.2007.1.4.172.1.21.1 | Integer32 | accessible-for-notify | Parameter 'BufferLevel' in event L2TP.21 |
| l2tpEventObjects26 | 1.3.6.1.4.1.2007.1.4.172.1.26 | Event L2TP.26 A data packet has been received for an L2TP session with no L2TP handler. Datagram is discarded. | ||
| I32 l2tp26_TunnelID | 1.3.6.1.4.1.2007.1.4.172.1.26.1 | Integer32 | accessible-for-notify | Parameter 'TunnelID' in event L2TP.26 |
| I32 l2tp26_SessionID | 1.3.6.1.4.1.2007.1.4.172.1.26.2 | Integer32 | accessible-for-notify | Parameter 'SessionID' in event L2TP.26 |
| l2tpEventObjects27 | 1.3.6.1.4.1.2007.1.4.172.1.27 | Event L2TP.27 An error has ocurred while sending received L2TP session data through its associated PPP/L2TP interface. Data is discarded. | ||
| I32 l2tp27_TunnelID | 1.3.6.1.4.1.2007.1.4.172.1.27.1 | Integer32 | accessible-for-notify | Parameter 'TunnelID' in event L2TP.27 |
| I32 l2tp27_SessionID | 1.3.6.1.4.1.2007.1.4.172.1.27.2 | Integer32 | accessible-for-notify | Parameter 'SessionID' in event L2TP.27 |
| STR l2tp27_IfcName | 1.3.6.1.4.1.2007.1.4.172.1.27.3 | DisplayString | accessible-for-notify | Parameter 'IfcName' in event L2TP.27 |
| STR l2tp27_L2TP_Session_Name | 1.3.6.1.4.1.2007.1.4.172.1.27.4 | DisplayString | accessible-for-notify | Parameter 'L2TP-Session-Name' in event L2TP.27 |
| l2tpEventObjects28 | 1.3.6.1.4.1.2007.1.4.172.1.28 | Event L2TP.28 A data packet has been received for an L2TP session and has been sent successfully through its associated interface. | ||
| I32 l2tp28_TunnelID | 1.3.6.1.4.1.2007.1.4.172.1.28.1 | Integer32 | accessible-for-notify | Parameter 'TunnelID' in event L2TP.28 |
| I32 l2tp28_SessionID | 1.3.6.1.4.1.2007.1.4.172.1.28.2 | Integer32 | accessible-for-notify | Parameter 'SessionID' in event L2TP.28 |
| STR l2tp28_L2TP_Session_Name | 1.3.6.1.4.1.2007.1.4.172.1.28.3 | DisplayString | accessible-for-notify | Parameter 'L2TP-Session-Name' in event L2TP.28 |
| STR l2tp28_IfcName | 1.3.6.1.4.1.2007.1.4.172.1.28.4 | DisplayString | accessible-for-notify | Parameter 'IfcName' in event L2TP.28 |
| l2tpEventObjects29 | 1.3.6.1.4.1.2007.1.4.172.1.29 | Event L2TP.29 A data packet has been received from a interface and has been sent successfully through its associated L2TP session. | ||
| I32 l2tp29_TunnelID | 1.3.6.1.4.1.2007.1.4.172.1.29.1 | Integer32 | accessible-for-notify | Parameter 'TunnelID' in event L2TP.29 |
| I32 l2tp29_SessionID | 1.3.6.1.4.1.2007.1.4.172.1.29.2 | Integer32 | accessible-for-notify | Parameter 'SessionID' in event L2TP.29 |
| STR l2tp29_IfcName | 1.3.6.1.4.1.2007.1.4.172.1.29.3 | DisplayString | accessible-for-notify | Parameter 'IfcName' in event L2TP.29 |
| STR l2tp29_L2TP_Session_Name | 1.3.6.1.4.1.2007.1.4.172.1.29.4 | DisplayString | accessible-for-notify | Parameter 'L2TP-Session-Name' in event L2TP.29 |
| l2tpEventObjects30 | 1.3.6.1.4.1.2007.1.4.172.1.30 | Event L2TP.30 An error has ocurred while sending received PPP data through its associated L2TP session. Data is discarded. | ||
| I32 l2tp30_TunnelID | 1.3.6.1.4.1.2007.1.4.172.1.30.1 | Integer32 | accessible-for-notify | Parameter 'TunnelID' in event L2TP.30 |
| I32 l2tp30_SessionID | 1.3.6.1.4.1.2007.1.4.172.1.30.2 | Integer32 | accessible-for-notify | Parameter 'SessionID' in event L2TP.30 |
| STR l2tp30_IfcName | 1.3.6.1.4.1.2007.1.4.172.1.30.3 | DisplayString | accessible-for-notify | Parameter 'IfcName' in event L2TP.30 |
| STR l2tp30_L2TP_Session_Name | 1.3.6.1.4.1.2007.1.4.172.1.30.4 | DisplayString | accessible-for-notify | Parameter 'L2TP-Session-Name' in event L2TP.30 |
| l2tpEventObjects33 | 1.3.6.1.4.1.2007.1.4.172.1.33 | Event L2TP.33 The L2TP virtual interface is unable to get a user or domain from the associated PPP interface. | ||
| STR l2tp33_L2TPInterface | 1.3.6.1.4.1.2007.1.4.172.1.33.1 | DisplayString | accessible-for-notify | Parameter 'L2TPInterface' in event L2TP.33 |
| l2tpEventObjects34 | 1.3.6.1.4.1.2007.1.4.172.1.34 | Event L2TP.34 The L2TP virtual interface cannot establish a new L2TP session for this user/domain. | ||
| STR l2tp34_L2TPInterface | 1.3.6.1.4.1.2007.1.4.172.1.34.1 | DisplayString | accessible-for-notify | Parameter 'L2TPInterface' in event L2TP.34 |
| STR l2tp34_User | 1.3.6.1.4.1.2007.1.4.172.1.34.2 | DisplayString | accessible-for-notify | Parameter 'User' in event L2TP.34 |
| l2tpEventObjects35 | 1.3.6.1.4.1.2007.1.4.172.1.35 | Event L2TP.35 An L2TP event has occurred. Specific event message follows. | ||
| STR l2tp35_EventMessage | 1.3.6.1.4.1.2007.1.4.172.1.35.1 | DisplayString | accessible-for-notify | Parameter 'EventMessage' in event L2TP.35 |
| l2tpEventObjects36 | 1.3.6.1.4.1.2007.1.4.172.1.36 | Event L2TP.36 An L2TP debug has occurred. Specific debug message follows. | ||
| STR l2tp36_DebugMessage | 1.3.6.1.4.1.2007.1.4.172.1.36.1 | DisplayString | accessible-for-notify | Parameter 'DebugMessage' in event L2TP.36 |
| l2tpEventObjects37 | 1.3.6.1.4.1.2007.1.4.172.1.37 | Event L2TP.37 Shows Attribute Information. | ||
| STR l2tp37_AttributeType | 1.3.6.1.4.1.2007.1.4.172.1.37.1 | DisplayString | accessible-for-notify | Parameter 'AttributeType' in event L2TP.37 |
| STR l2tp37_AttributeValue | 1.3.6.1.4.1.2007.1.4.172.1.37.2 | DisplayString | accessible-for-notify | Parameter 'AttributeValue' in event L2TP.37 |
| STR l2tp37_MandatoryYesNo | 1.3.6.1.4.1.2007.1.4.172.1.37.3 | DisplayString | accessible-for-notify | Parameter 'MandatoryYesNo' in event L2TP.37 |
| STR l2tp37_HiddenYesNo | 1.3.6.1.4.1.2007.1.4.172.1.37.4 | DisplayString | accessible-for-notify | Parameter 'HiddenYesNo' in event L2TP.37 |
| l2tpEventObjects38 | 1.3.6.1.4.1.2007.1.4.172.1.38 | Event L2TP.38 The Tie Breaker has been done and one side has won. | ||
| STR l2tp38_who_has_won | 1.3.6.1.4.1.2007.1.4.172.1.38.1 | DisplayString | accessible-for-notify | Parameter 'who-has-won' in event L2TP.38 |
| IP l2tp38_peer_address | 1.3.6.1.4.1.2007.1.4.172.1.38.2 | IpAddress | accessible-for-notify | Parameter 'peer-address' in event L2TP.38 |
| l2tpEventObjects39 | 1.3.6.1.4.1.2007.1.4.172.1.39 | Event L2TP.39 The session has been rejected because there is no peer with this address and this remote end identifier. | ||
| I32 l2tp39_tunnel_ID | 1.3.6.1.4.1.2007.1.4.172.1.39.1 | Integer32 | accessible-for-notify | Parameter 'tunnel-ID' in event L2TP.39 |
| IP l2tp39_peer_address | 1.3.6.1.4.1.2007.1.4.172.1.39.2 | IpAddress | accessible-for-notify | Parameter 'peer-address' in event L2TP.39 |
| STR l2tp39_remote_end_id_received | 1.3.6.1.4.1.2007.1.4.172.1.39.3 | DisplayString | accessible-for-notify | Parameter 'remote-end-id-received' in event L2TP.39 |
| l2tpEventObjects40 | 1.3.6.1.4.1.2007.1.4.172.1.40 | Event L2TP.40 The Session Tie Breaker has been done and one side has won. | ||
| STR l2tp40_who_has_won | 1.3.6.1.4.1.2007.1.4.172.1.40.1 | DisplayString | accessible-for-notify | Parameter 'who-has-won' in event L2TP.40 |
| IP l2tp40_peer_address | 1.3.6.1.4.1.2007.1.4.172.1.40.2 | IpAddress | accessible-for-notify | Parameter 'peer-address' in event L2TP.40 |
| l2tpEventObjects41 | 1.3.6.1.4.1.2007.1.4.172.1.41 | Event L2TP.41 One IPoFR packet has been processed | ||
| STR l2tp41_From | 1.3.6.1.4.1.2007.1.4.172.1.41.1 | DisplayString | accessible-for-notify | Parameter 'From' in event L2TP.41 |
| STR l2tp41_To | 1.3.6.1.4.1.2007.1.4.172.1.41.2 | DisplayString | accessible-for-notify | Parameter 'To' in event L2TP.41 |
| I32 l2tp41_PacketLength | 1.3.6.1.4.1.2007.1.4.172.1.41.3 | Integer32 | accessible-for-notify | Parameter 'PacketLength' in event L2TP.41 |
| I32 l2tp41_DCLI | 1.3.6.1.4.1.2007.1.4.172.1.41.4 | Integer32 | accessible-for-notify | Parameter 'DCLI' in event L2TP.41 |
| IP l2tp41_IPSource | 1.3.6.1.4.1.2007.1.4.172.1.41.5 | IpAddress | accessible-for-notify | Parameter 'IPSource' in event L2TP.41 |
| IP l2tp41_IPDest | 1.3.6.1.4.1.2007.1.4.172.1.41.6 | IpAddress | accessible-for-notify | Parameter 'IPDest' in event L2TP.41 |
| I32 l2tp41_Protocol | 1.3.6.1.4.1.2007.1.4.172.1.41.7 | Integer32 | accessible-for-notify | Parameter 'Protocol' in event L2TP.41 |
| l2tpEventObjects42 | 1.3.6.1.4.1.2007.1.4.172.1.42 | Event L2TP.42 One FR LMI packet has been processed | ||
| STR l2tp42_From | 1.3.6.1.4.1.2007.1.4.172.1.42.1 | DisplayString | accessible-for-notify | Parameter 'From' in event L2TP.42 |
| STR l2tp42_To | 1.3.6.1.4.1.2007.1.4.172.1.42.2 | DisplayString | accessible-for-notify | Parameter 'To' in event L2TP.42 |
| I32 l2tp42_PacketLength | 1.3.6.1.4.1.2007.1.4.172.1.42.3 | Integer32 | accessible-for-notify | Parameter 'PacketLength' in event L2TP.42 |
| I32 l2tp42_DCLI | 1.3.6.1.4.1.2007.1.4.172.1.42.4 | Integer32 | accessible-for-notify | Parameter 'DCLI' in event L2TP.42 |
| STR l2tp42_Status_Enquiry | 1.3.6.1.4.1.2007.1.4.172.1.42.5 | DisplayString | accessible-for-notify | Parameter 'Status-Enquiry' in event L2TP.42 |
| l2tpEventObjects43 | 1.3.6.1.4.1.2007.1.4.172.1.43 | Event L2TP.43 One FR packet has been processed | ||
| STR l2tp43_From | 1.3.6.1.4.1.2007.1.4.172.1.43.1 | DisplayString | accessible-for-notify | Parameter 'From' in event L2TP.43 |
| STR l2tp43_To | 1.3.6.1.4.1.2007.1.4.172.1.43.2 | DisplayString | accessible-for-notify | Parameter 'To' in event L2TP.43 |
| I32 l2tp43_PacketLength | 1.3.6.1.4.1.2007.1.4.172.1.43.3 | Integer32 | accessible-for-notify | Parameter 'PacketLength' in event L2TP.43 |
| I32 l2tp43_DCLI | 1.3.6.1.4.1.2007.1.4.172.1.43.4 | Integer32 | accessible-for-notify | Parameter 'DCLI' in event L2TP.43 |
| l2tpEventObjects44 | 1.3.6.1.4.1.2007.1.4.172.1.44 | Event L2TP.44 One packet has been processed | ||
| STR l2tp44_TunnelName | 1.3.6.1.4.1.2007.1.4.172.1.44.1 | DisplayString | accessible-for-notify | Parameter 'TunnelName' in event L2TP.44 |
| STR l2tp44_From | 1.3.6.1.4.1.2007.1.4.172.1.44.2 | DisplayString | accessible-for-notify | Parameter 'From' in event L2TP.44 |
| STR l2tp44_To | 1.3.6.1.4.1.2007.1.4.172.1.44.3 | DisplayString | accessible-for-notify | Parameter 'To' in event L2TP.44 |
| I32 l2tp44_PacketLength | 1.3.6.1.4.1.2007.1.4.172.1.44.4 | Integer32 | accessible-for-notify | Parameter 'PacketLength' in event L2TP.44 |
| STR l2tp44_Buffer | 1.3.6.1.4.1.2007.1.4.172.1.44.5 | DisplayString | accessible-for-notify | Parameter 'Buffer' in event L2TP.44 |
| l2tpEventObjects45 | 1.3.6.1.4.1.2007.1.4.172.1.45 | Event L2TP.45 The time of life of a packet inside the disordered queue has expired, the expected packet is considered lost, the packet from the queue is extracted and sent throgh the base interface. | ||
| I32 l2tp45_pckt_sequence_number | 1.3.6.1.4.1.2007.1.4.172.1.45.1 | Integer32 | accessible-for-notify | Parameter 'pckt-sequence-number' in event L2TP.45 |
| I32 l2tp45_remaining_queue_size | 1.3.6.1.4.1.2007.1.4.172.1.45.2 | Integer32 | accessible-for-notify | Parameter 'remaining-queue-size' in event L2TP.45 |
| l2tpEventObjects46 | 1.3.6.1.4.1.2007.1.4.172.1.46 | Event L2TP.46 And old packet has been received, the router will discard this packet. | ||
| I32 l2tp46_pckt_sequence_number | 1.3.6.1.4.1.2007.1.4.172.1.46.1 | Integer32 | accessible-for-notify | Parameter 'pckt-sequence-number' in event L2TP.46 |
| I32 l2tp46_expected_sequence_number | 1.3.6.1.4.1.2007.1.4.172.1.46.2 | Integer32 | accessible-for-notify | Parameter 'expected-sequence-number' in event L2TP.46 |
| l2tpEventObjects47 | 1.3.6.1.4.1.2007.1.4.172.1.47 | Event L2TP.47 We are extracting and sending a packet from the disordered queue because it is the following packet of the last sent packet. | ||
| I32 l2tp47_sequence_number | 1.3.6.1.4.1.2007.1.4.172.1.47.1 | Integer32 | accessible-for-notify | Parameter 'sequence-number' in event L2TP.47 |
| I32 l2tp47_queue_size | 1.3.6.1.4.1.2007.1.4.172.1.47.2 | Integer32 | accessible-for-notify | Parameter 'queue-size' in event L2TP.47 |
| l2tpEventObjects48 | 1.3.6.1.4.1.2007.1.4.172.1.48 | Event L2TP.48 We are adding a packet to the disordered queue because it is inside the receive window. | ||
| I32 l2tp48_sequence_number | 1.3.6.1.4.1.2007.1.4.172.1.48.1 | Integer32 | accessible-for-notify | Parameter 'sequence-number' in event L2TP.48 |
| I32 l2tp48_expected_sequence_number | 1.3.6.1.4.1.2007.1.4.172.1.48.2 | Integer32 | accessible-for-notify | Parameter 'expected-sequence-number' in event L2TP.48 |
| I32 l2tp48_queue_size | 1.3.6.1.4.1.2007.1.4.172.1.48.3 | Integer32 | accessible-for-notify | Parameter 'queue-size' in event L2TP.48 |
| l2tpEventObjects49 | 1.3.6.1.4.1.2007.1.4.172.1.49 | Event L2TP.49 We are adding a packet to the disordered queue because it is inside the window. | ||
| I32 l2tp49_received_sequence_number | 1.3.6.1.4.1.2007.1.4.172.1.49.1 | Integer32 | accessible-for-notify | Parameter 'received-sequence-number' in event L2TP.49 |
| I32 l2tp49_expected_sequence_number | 1.3.6.1.4.1.2007.1.4.172.1.49.2 | Integer32 | accessible-for-notify | Parameter 'expected-sequence-number' in event L2TP.49 |
| l2tpEventObjects50 | 1.3.6.1.4.1.2007.1.4.172.1.50 | Event L2TP.50 We are flushing the disordered packet queue. | ||
| I32 l2tp50_sent_sequence_number | 1.3.6.1.4.1.2007.1.4.172.1.50.1 | Integer32 | accessible-for-notify | Parameter 'sent-sequence-number' in event L2TP.50 |
| I32 l2tp50_remaining_queue_size | 1.3.6.1.4.1.2007.1.4.172.1.50.2 | Integer32 | accessible-for-notify | Parameter 'remaining-queue-size' in event L2TP.50 |
| l2tpEventObjects51 | 1.3.6.1.4.1.2007.1.4.172.1.51 | Event L2TP.51 The pattern insertion structure is being created | ||
| STR l2tp51_interface_name | 1.3.6.1.4.1.2007.1.4.172.1.51.1 | DisplayString | accessible-for-notify | Parameter 'interface-name' in event L2TP.51 |
| STR l2tp51_pseudowire_name | 1.3.6.1.4.1.2007.1.4.172.1.51.2 | DisplayString | accessible-for-notify | Parameter 'pseudowire-name' in event L2TP.51 |
| l2tpEventObjects52 | 1.3.6.1.4.1.2007.1.4.172.1.52 | Event L2TP.52 The pattern insertion process has succeed | ||
| STR l2tp52_interface_name | 1.3.6.1.4.1.2007.1.4.172.1.52.1 | DisplayString | accessible-for-notify | Parameter 'interface-name' in event L2TP.52 |
| STR l2tp52_pseudowire_name | 1.3.6.1.4.1.2007.1.4.172.1.52.2 | DisplayString | accessible-for-notify | Parameter 'pseudowire-name' in event L2TP.52 |
| l2tpEventObjects53 | 1.3.6.1.4.1.2007.1.4.172.1.53 | Event L2TP.53 The pattern insertion process has failed | ||
| STR l2tp53_interface_name | 1.3.6.1.4.1.2007.1.4.172.1.53.1 | DisplayString | accessible-for-notify | Parameter 'interface-name' in event L2TP.53 |
| STR l2tp53_pseudowire_name | 1.3.6.1.4.1.2007.1.4.172.1.53.2 | DisplayString | accessible-for-notify | Parameter 'pseudowire-name' in event L2TP.53 |
| l2tpEventObjects54 | 1.3.6.1.4.1.2007.1.4.172.1.54 | Event L2TP.54 An L2TP event call has occurred. Specific event message follows. | ||
| STR l2tp54_EventMessage | 1.3.6.1.4.1.2007.1.4.172.1.54.1 | DisplayString | accessible-for-notify | Parameter 'EventMessage' in event L2TP.54 |
| l2tpEventObjects56 | 1.3.6.1.4.1.2007.1.4.172.1.56 | Event L2TP.56 Pattern insertion multicast and waiting for establish session | ||
| STR l2tp56_interface_name | 1.3.6.1.4.1.2007.1.4.172.1.56.1 | DisplayString | accessible-for-notify | Parameter 'interface-name' in event L2TP.56 |
| STR l2tp56_pseudowire_name | 1.3.6.1.4.1.2007.1.4.172.1.56.2 | DisplayString | accessible-for-notify | Parameter 'pseudowire-name' in event L2TP.56 |
| l2tpNotifications | 1.3.6.1.4.1.2007.1.4.172.2 | |||
| l2tpNotificationsPrefix | 1.3.6.1.4.1.2007.1.4.172.2.0 | |||
| NTF l2tpNotification1 | 1.3.6.1.4.1.2007.1.4.172.2.0.1 | Notification of Event L2TP.1 Message: 'L2TP subsystem started successfully.' L2TP subsystem started successfully. | ||
| NTF l2tpNotification2 | 1.3.6.1.4.1.2007.1.4.172.2.0.2 | Notification of Event L2TP.2 Message: 'Error reading config: $1' Parameters list: $1: l2tp2-DiagnosticMessage The error printed occurred while reading the configuration. | ||
| NTF l2tpNotification3 | 1.3.6.1.4.1.2007.1.4.172.2.0.3 | Notification of Event L2TP.3 Message: 'tunnel $1: Incoming $2 from $3' Parameters list: $1: l2tp3-TunnelID $2: l2tp3-Packet-type $3: l2tp3-RemoteIPAddress A packet has been received from a remote peer. Local Tunnel ID, packet type and peer IP address are shown in this message. | ||
| NTF l2tpNotification4 | 1.3.6.1.4.1.2007.1.4.172.2.0.4 | Notification of Event L2TP.4 Message: 'tunnel $1: Outgoing $2 to $3' Parameters list: $1: l2tp4-TunnelID $2: l2tp4-Packet-type $3: l2tp4-RemoteIPAddress A packet has been sent to a remote peer. Local Tunnel ID, packet type and peer IP address are shown in this message. | ||
| NTF l2tpNotification5 | 1.3.6.1.4.1.2007.1.4.172.2.0.5 | Notification of Event L2TP.5 Message: 'New tunnel with ID $1 has been created' Parameters list: $1: l2tp5-TunnelID A new tunnel has been created. Local Tunnel ID is shown in the message. | ||
| NTF l2tpNotification6 | 1.3.6.1.4.1.2007.1.4.172.2.0.6 | Notification of Event L2TP.6 Message: 'Tunnel with ID $1 changed state from $2 to $3' Parameters list: $1: l2tp6-TunnelID $2: l2tp6-OldState $3: l2tp6-NewState The tunnel has changed its state. Local Tunnel ID, old state and new state are shown in the message. | ||
| NTF l2tpNotification7 | 1.3.6.1.4.1.2007.1.4.172.2.0.7 | Notification of Event L2TP.7 Message: 'Incoming SCCRQ from $1' Parameters list: $1: l2tp7-RemoteIPAddress An Start-Control-Connection-Request packet has been received from a remote peer. Peer IP address is shown in the message. | ||
| NTF l2tpNotification8 | 1.3.6.1.4.1.2007.1.4.172.2.0.8 | Notification of Event L2TP.8 Message: 'Creating pseudowire $1 interface: $2 source IP: $3 destination IP: $4' Parameters list: $1: l2tp8-pseudowire-name $2: l2tp8-associated-interface $3: l2tp8-source-ip $4: l2tp8-destination-ip The router is creating the stuctures for a pseudowire. | ||
| NTF l2tpNotification9 | 1.3.6.1.4.1.2007.1.4.172.2.0.9 | Notification of Event L2TP.9 Message: 'Associated interface $1 is up, establishing $2' Parameters list: $1: l2tp9-interface-name $2: l2tp9-pseudowire-name The pseudowire associated interface is now UP. The router tries to establish the pseudoeire session. | ||
| NTF l2tpNotification10 | 1.3.6.1.4.1.2007.1.4.172.2.0.10 | Notification of Event L2TP.10 Message: 'Session already exists for pseudowire $1, tunnel: $2, session id: $3' Parameters list: $1: l2tp10-pseudowire-name $2: l2tp10-tunnel-id $3: l2tp10-session-id A session already exists for the pseudowire and not need to be created. | ||
| NTF l2tpNotification11 | 1.3.6.1.4.1.2007.1.4.172.2.0.11 | Notification of Event L2TP.11 Message: 'Session of tunnel $1 with ID $2 changed state from $3 to $4' Parameters list: $1: l2tp11-TunnelID $2: l2tp11-SessionID $3: l2tp11-OldState $4: l2tp11-NewState The session has changed its state. Local Tunnel/Session IDs, old state and new state are shown in the message. | ||
| NTF l2tpNotification12 | 1.3.6.1.4.1.2007.1.4.172.2.0.12 | Notification of Event L2TP.12 Message: 'New session for tunnel $1 with ID $2 has been created' Parameters list: $1: l2tp12-TunnelID $2: l2tp12-SessionID A new session within a tunnel has been created. Local Tunnel and Session IDs are shown in the message. | ||
| NTF l2tpNotification13 | 1.3.6.1.4.1.2007.1.4.172.2.0.13 | Notification of Event L2TP.13 Message: 'The pseudowire $1 cannot be registered at interface $2' Parameters list: $1: l2tp13-pseudowire-name $2: l2tp13-net-name The pseudowire cannot be registered in the down net because the net does not allowed registration.. | ||
| NTF l2tpNotification14 | 1.3.6.1.4.1.2007.1.4.172.2.0.14 | Notification of Event L2TP.14 Message: 'Pseudowire $1 was successfully created' Parameters list: $1: l2tp14-pseudowire-name The pseudowire has been successfully created. | ||
| NTF l2tpNotification15 | 1.3.6.1.4.1.2007.1.4.172.2.0.15 | Notification of Event L2TP.15 Message: 'Can not create pseudowire $1 due to $2' Parameters list: $1: l2tp15-pseudowire-name $2: l2tp15-cause-of-error The pseudowire can not be created due to one of the following reasons: the interface is unkown, there is already a peer registered or an internal error. | ||
| NTF l2tpNotification16 | 1.3.6.1.4.1.2007.1.4.172.2.0.16 | Notification of Event L2TP.16 Message: '----' Reserved for possible future use. | ||
| NTF l2tpNotification17 | 1.3.6.1.4.1.2007.1.4.172.2.0.17 | Notification of Event L2TP.17 Message: 'A tunnel with ID $1 has been deleted' Parameters list: $1: l2tp17-TunnelID A tunnel has been deleted. Local Tunnel ID is shown in the message. | ||
| NTF l2tpNotification18 | 1.3.6.1.4.1.2007.1.4.172.2.0.18 | Notification of Event L2TP.18 Message: 'A session with ID $1/$2 has been deleted' Parameters list: $1: l2tp18-TunnelID $2: l2tp18-SessionID A session has been deleted. Local Tunnel and Session IDs are shown in the message. | ||
| NTF l2tpNotification19 | 1.3.6.1.4.1.2007.1.4.172.2.0.19 | Notification of Event L2TP.19 Message: 'L2TP error: $1' Parameters list: $1: l2tp19-ErrorMessage An L2TP error has occurred. Specific error message follows. | ||
| NTF l2tpNotification20 | 1.3.6.1.4.1.2007.1.4.172.2.0.20 | Notification of Event L2TP.20 Message: 'Elastic-store underrun detected, buffer level $1' Parameters list: $1: l2tp20-BufferLevel Elastic-store underrun has been detected, the last received packet and a copy will be added to the elastic-store buffer. | ||
| NTF l2tpNotification21 | 1.3.6.1.4.1.2007.1.4.172.2.0.21 | Notification of Event L2TP.21 Message: 'Elastic-store overrun detected, buffer level $1' Parameters list: $1: l2tp21-BufferLevel Elastic-store overrun has been detected, the last received packet will be dropped. | ||
| NTF l2tpNotification22 | 1.3.6.1.4.1.2007.1.4.172.2.0.22 | Notification of Event L2TP.22 Message: '----' Reserved for possible future use. | ||
| NTF l2tpNotification23 | 1.3.6.1.4.1.2007.1.4.172.2.0.23 | Notification of Event L2TP.23 Message: '----' Reserved for possible future use. | ||
| NTF l2tpNotification24 | 1.3.6.1.4.1.2007.1.4.172.2.0.24 | Notification of Event L2TP.24 Message: '----' Reserved for possible future use. | ||
| NTF l2tpNotification25 | 1.3.6.1.4.1.2007.1.4.172.2.0.25 | Notification of Event L2TP.25 Message: '----' Reserved for possible future use. | ||
| NTF l2tpNotification26 | 1.3.6.1.4.1.2007.1.4.172.2.0.26 | Notification of Event L2TP.26 Message: 'session $1/$2 has no L2TP handler available' Parameters list: $1: l2tp26-TunnelID $2: l2tp26-SessionID A data packet has been received for an L2TP session with no L2TP handler. Datagram is discarded. | ||
| NTF l2tpNotification27 | 1.3.6.1.4.1.2007.1.4.172.2.0.27 | Notification of Event L2TP.27 Message: 'session $1/$2: error while sending data through $3 interface from $4' Parameters list: $1: l2tp27-TunnelID $2: l2tp27-SessionID $3: l2tp27-IfcName $4: l2tp27-L2TP-Session-Name An error has ocurred while sending received L2TP session data through its associated PPP/L2TP interface. Data is discarded. | ||
| NTF l2tpNotification28 | 1.3.6.1.4.1.2007.1.4.172.2.0.28 | Notification of Event L2TP.28 Message: 'session out $1/$2: data received from $3 sent to associated $4 interface' Parameters list: $1: l2tp28-TunnelID $2: l2tp28-SessionID $3: l2tp28-L2TP-Session-Name $4: l2tp28-IfcName A data packet has been received for an L2TP session and has been sent successfully through its associated interface. | ||
| NTF l2tpNotification29 | 1.3.6.1.4.1.2007.1.4.172.2.0.29 | Notification of Event L2TP.29 Message: 'session in $1/$2: data received from $3 interface sent to $4 L2TP session' Parameters list: $1: l2tp29-TunnelID $2: l2tp29-SessionID $3: l2tp29-IfcName $4: l2tp29-L2TP-Session-Name A data packet has been received from a interface and has been sent successfully through its associated L2TP session. | ||
| NTF l2tpNotification30 | 1.3.6.1.4.1.2007.1.4.172.2.0.30 | Notification of Event L2TP.30 Message: 'session $1/$2: error while sending data from $3 interface to $4 L2TP session' Parameters list: $1: l2tp30-TunnelID $2: l2tp30-SessionID $3: l2tp30-IfcName $4: l2tp30-L2TP-Session-Name An error has ocurred while sending received PPP data through its associated L2TP session. Data is discarded. | ||
| NTF l2tpNotification31 | 1.3.6.1.4.1.2007.1.4.172.2.0.31 | Notification of Event L2TP.31 Message: '----' Reserved for possible future use. | ||
| NTF l2tpNotification32 | 1.3.6.1.4.1.2007.1.4.172.2.0.32 | Notification of Event L2TP.32 Message: '----' Reserved for possible future use. | ||
| NTF l2tpNotification33 | 1.3.6.1.4.1.2007.1.4.172.2.0.33 | Notification of Event L2TP.33 Message: '$1 Ifc Cannot get user/domain' Parameters list: $1: l2tp33-L2TPInterface The L2TP virtual interface is unable to get a user or domain from the associated PPP interface. | ||
| NTF l2tpNotification34 | 1.3.6.1.4.1.2007.1.4.172.2.0.34 | Notification of Event L2TP.34 Message: '$1 Ifc Cannot establish tunn/sess ($2)' Parameters list: $1: l2tp34-L2TPInterface $2: l2tp34-User The L2TP virtual interface cannot establish a new L2TP session for this user/domain. | ||
| NTF l2tpNotification35 | 1.3.6.1.4.1.2007.1.4.172.2.0.35 | Notification of Event L2TP.35 Message: 'EVENT: $1' Parameters list: $1: l2tp35-EventMessage An L2TP event has occurred. Specific event message follows. | ||
| NTF l2tpNotification36 | 1.3.6.1.4.1.2007.1.4.172.2.0.36 | Notification of Event L2TP.36 Message: 'DEBUG: $1' Parameters list: $1: l2tp36-DebugMessage An L2TP debug has occurred. Specific debug message follows. | ||
| NTF l2tpNotification37 | 1.3.6.1.4.1.2007.1.4.172.2.0.37 | Notification of Event L2TP.37 Message: 'AVP:$1,$2 Mandatory:$3, Hidden:$4' Parameters list: $1: l2tp37-AttributeType $2: l2tp37-AttributeValue $3: l2tp37-MandatoryYesNo $4: l2tp37-HiddenYesNo Shows Attribute Information. | ||
| NTF l2tpNotification38 | 1.3.6.1.4.1.2007.1.4.172.2.0.38 | Notification of Event L2TP.38 Message: 'TIE BREAKER: $1 the Tie Breaker with peer $2' Parameters list: $1: l2tp38-who-has-won $2: l2tp38-peer-address The Tie Breaker has been done and one side has won. | ||
| NTF l2tpNotification39 | 1.3.6.1.4.1.2007.1.4.172.2.0.39 | Notification of Event L2TP.39 Message: 'tnnl: $1: Rejected session ICRQ, no peer ($2) with Remote End ID: $3' Parameters list: $1: l2tp39-tunnel-ID $2: l2tp39-peer-address $3: l2tp39-remote-end-id-received The session has been rejected because there is no peer with this address and this remote end identifier. | ||
| NTF l2tpNotification40 | 1.3.6.1.4.1.2007.1.4.172.2.0.40 | Notification of Event L2TP.40 Message: 'TIE BREAKER: $1 the Session Tie Breaker with peer $2' Parameters list: $1: l2tp40-who-has-won $2: l2tp40-peer-address The Session Tie Breaker has been done and one side has won. | ||
| NTF l2tpNotification41 | 1.3.6.1.4.1.2007.1.4.172.2.0.41 | Notification of Event L2TP.41 Message: 'fr data $1->$2, len=$3: dcli=$4, ipsrc=$5, ipdst=$6, prot=$7' Parameters list: $1: l2tp41-From $2: l2tp41-To $3: l2tp41-PacketLength $4: l2tp41-DCLI $5: l2tp41-IPSource $6: l2tp41-IPDest $7: l2tp41-Protocol One IPoFR packet has been processed | ||
| NTF l2tpNotification42 | 1.3.6.1.4.1.2007.1.4.172.2.0.42 | Notification of Event L2TP.42 Message: 'fr lmi data $1->$2, len=$3: dcli=$4 $5' Parameters list: $1: l2tp42-From $2: l2tp42-To $3: l2tp42-PacketLength $4: l2tp42-DCLI $5: l2tp42-Status-Enquiry One FR LMI packet has been processed | ||
| NTF l2tpNotification43 | 1.3.6.1.4.1.2007.1.4.172.2.0.43 | Notification of Event L2TP.43 Message: 'fr data $1->$2, len=$3: dcli=$4' Parameters list: $1: l2tp43-From $2: l2tp43-To $3: l2tp43-PacketLength $4: l2tp43-DCLI One FR packet has been processed | ||
| NTF l2tpNotification44 | 1.3.6.1.4.1.2007.1.4.172.2.0.44 | Notification of Event L2TP.44 Message: 'data remote:$1 $2->$3, len=$4: packet:$5' Parameters list: $1: l2tp44-TunnelName $2: l2tp44-From $3: l2tp44-To $4: l2tp44-PacketLength $5: l2tp44-Buffer One packet has been processed | ||
| NTF l2tpNotification45 | 1.3.6.1.4.1.2007.1.4.172.2.0.45 | Notification of Event L2TP.45 Message: 'Timer expired, sending packet $1, queue size is $2' Parameters list: $1: l2tp45-pckt-sequence-number $2: l2tp45-remaining-queue-size The time of life of a packet inside the disordered queue has expired, the expected packet is considered lost, the packet from the queue is extracted and sent throgh the base interface. | ||
| NTF l2tpNotification46 | 1.3.6.1.4.1.2007.1.4.172.2.0.46 | Notification of Event L2TP.46 Message: 'Old packet $1 received is being discarded, expected $2' Parameters list: $1: l2tp46-pckt-sequence-number $2: l2tp46-expected-sequence-number And old packet has been received, the router will discard this packet. | ||
| NTF l2tpNotification47 | 1.3.6.1.4.1.2007.1.4.172.2.0.47 | Notification of Event L2TP.47 Message: 'Sending packet $1 from disordered queue, queue size is $2' Parameters list: $1: l2tp47-sequence-number $2: l2tp47-queue-size We are extracting and sending a packet from the disordered queue because it is the following packet of the last sent packet. | ||
| NTF l2tpNotification48 | 1.3.6.1.4.1.2007.1.4.172.2.0.48 | Notification of Event L2TP.48 Message: 'Adding packet $1 to disordered queue, expected $2, queue size is $3' Parameters list: $1: l2tp48-sequence-number $2: l2tp48-expected-sequence-number $3: l2tp48-queue-size We are adding a packet to the disordered queue because it is inside the receive window. | ||
| NTF l2tpNotification49 | 1.3.6.1.4.1.2007.1.4.172.2.0.49 | Notification of Event L2TP.49 Message: 'Received packet $1 out of window, expected seq num $2' Parameters list: $1: l2tp49-received-sequence-number $2: l2tp49-expected-sequence-number We are adding a packet to the disordered queue because it is inside the window. | ||
| NTF l2tpNotification50 | 1.3.6.1.4.1.2007.1.4.172.2.0.50 | Notification of Event L2TP.50 Message: 'Flushing disordered packet queue, sending packet $1, queue size is $2' Parameters list: $1: l2tp50-sent-sequence-number $2: l2tp50-remaining-queue-size We are flushing the disordered packet queue. | ||
| NTF l2tpNotification51 | 1.3.6.1.4.1.2007.1.4.172.2.0.51 | Notification of Event L2TP.51 Message: 'Creating pattern insertion structure for peer ifc=$1 pw=$2' Parameters list: $1: l2tp51-interface-name $2: l2tp51-pseudowire-name The pattern insertion structure is being created | ||
| NTF l2tpNotification52 | 1.3.6.1.4.1.2007.1.4.172.2.0.52 | Notification of Event L2TP.52 Message: 'Pattern insertion process success for peer ifc=$1 pw=$2' Parameters list: $1: l2tp52-interface-name $2: l2tp52-pseudowire-name The pattern insertion process has succeed | ||
| NTF l2tpNotification53 | 1.3.6.1.4.1.2007.1.4.172.2.0.53 | Notification of Event L2TP.53 Message: 'Pattern insertion process fail for peer ifc=$1 pw=$2' Parameters list: $1: l2tp53-interface-name $2: l2tp53-pseudowire-name The pattern insertion process has failed | ||
| NTF l2tpNotification54 | 1.3.6.1.4.1.2007.1.4.172.2.0.54 | Notification of Event L2TP.54 Message: 'EVENT CALL: $1' Parameters list: $1: l2tp54-EventMessage An L2TP event call has occurred. Specific event message follows. | ||
| NTF l2tpNotification55 | 1.3.6.1.4.1.2007.1.4.172.2.0.55 | Notification of Event L2TP.55 Message: 'EVENT CALL: Disable this event to enable EVENT CALL events' Disable this event to enable EVENT CALL events | ||
| NTF l2tpNotification56 | 1.3.6.1.4.1.2007.1.4.172.2.0.56 | Notification of Event L2TP.56 Message: 'Pattern insertion multicast. Waiting session for peer ifc=$1 pw=$2' Parameters list: $1: l2tp56-interface-name $2: l2tp56-pseudowire-name Pattern insertion multicast and waiting for establish session |
RFC description
Manages SNMP traps for Teldat L2TP (Layer 2 Tunneling Protocol) event notifications on routers; vendor-private L2TP trap definitions.
Start monitoring Teldat router acting as L2TP tunnel endpoint (tunnel 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.