PEA-L2CP-IPDSLAM

All MIBs › PEA-L2CP-IPDSLAM

Organization: Ericsson Diax A/S - Denmark

Last Updated: 2005-10-10

Category: DSL and Broadband

Description: Manages Layer 2 Control Protocol (L2CP) tunneling and disposition policies on the Ericsson Diax IP DSLAM.

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 PEA-L2CP-IPDSLAM?

PEA-L2CP-IPDSLAM is an Ericsson (Ericsson Diax A/S) MIB that implements L2CP, a protocol used between a BRAS and an IP DSLAM (per draft-wadhwa-gsmp-l2control-configuration-00) to report DSL line status changes up to the broadband access server. It defines l2cpPortTable, indexed by the DSLAM's lineIndex, with per-line objects l2cpEnable, l2cpPartitionId (for multi-BRAS partitioning of the DSLAM), l2cpAccessLoopCircuitId (a WT-101-style circuit ID built from an access-node identifier and slot string), l2cpPortStatus (showTime/idle/silent), and l2cpLineTransmissionSystem (ADSL1/2/2+, VDSL1/2, SDSL). Two notifications, l2cpPortDownEvent and l2cpPortUpEvent, carry a rich set of bound objects - including ADSL transmit/attainable rate and interleave-delay objects imported from ADSL-LINE-MIB - so the BRAS can learn line-rate parameters the moment a subscriber's line comes up or drops. Rather than tunneling traffic itself, the MIB's real function is line-event signaling and per-port circuit-ID addressing for the DSLAM, and it is deployed on Ericsson Diax IP DSLAMs supporting BRAS-based subscriber management; engineers can look up the PEA-L2CP-IPDSLAM download when working with this Ericsson DSLAM line.

IPNetwork Monitor allows you to monitor SNMP objects defined in PEA-L2CP-IPDSLAM. 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

Ericsson Diax A/S IP DSLAM platforms

Monitoring Examples

An operator subscribes to l2cpPortDownEvent/l2cpPortUpEvent traps and cross-checks l2cpPortStatus for the affected lineIndex; a port reporting idle or silent immediately after an unsolicited l2cpPortDownEvent with l2cpTrapReason indicating portConditionsChanged points to a subscriber CPE that has gone offline rather than an administrative shutdown.

What Can Be Monitored

per-line L2CP enable/partition configuration
DSL line status (showTime/idle/silent)
access loop circuit ID composition
DSL transmission system type per line
port up/down event notifications and trap reasons
ADSL rate/interleave-delay parameters carried in port-up events

Imported Objects

From ADSL-LINE-MIB

adslAtucChanConfInterleaveMaxTxRate	OBJECT-TYPE
adslAtucChanConfInterleaveMinTxRate	OBJECT-TYPE
adslAtucChanConfMaxInterleaveDelay	OBJECT-TYPE
adslAtucChanCurrTxRate	OBJECT-TYPE
adslAtucChanInterleaveDelay	OBJECT-TYPE
adslAtucCurrAttainableRate	OBJECT-TYPE
adslAturChanConfInterleaveMaxTxRate	OBJECT-TYPE
adslAturChanConfInterleaveMinTxRate	OBJECT-TYPE
adslAturChanConfMaxInterleaveDelay	OBJECT-TYPE
adslAturChanCurrTxRate	OBJECT-TYPE
adslAturChanInterleaveDelay	OBJECT-TYPE
adslAturCurrAttainableRate	OBJECT-TYPE

From DIESEL-SMI

peaIpDslam

OBJECT-IDENTITY

From PEA-ADSL-IPDSLAM

adslLineXTransAtucActual

OBJECT-TYPE

From PEA-BRIDGE-IPDSLAM

lineIndex

OBJECT-TYPE

From PEM-STANDARD

eventTime	OBJECT-TYPE
eventTypePem	OBJECT-TYPE
managedObjectClass	OBJECT-TYPE
managedObjectInstance	OBJECT-TYPE
perceivedSeverity	OBJECT-TYPE
probableCause	OBJECT-TYPE
sequenceNumber	OBJECT-TYPE

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using l2cpPortStatus OID:

Select an Ericsson Diax A/S IP DSLAM platform (BRAS-DSLAM L2CP line signaling) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type l2cpPortStatus into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The current status of a DSL line as seen from L2CP — showTime (active), idle (deactivated on purpose), or silent (CPE turned off). On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 'showTime', since that indicates the condition this object reports has changed to one worth investigating. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
peaL2cpIpDslam	1.3.6.1.4.1.193.72.300.35			The IP DSLAM software supports a number of standard and proprietary MIBs. This MIB module defines objects for the management via SNMP of L2CP functionality in the IP DSLAM. L2CP is a protocol to be used between BRAS and DSLAM and it is described in detail in draft-wadhwa-gsmp-l2control-configuration-00.
peaL2cpIpDslamObjects	1.3.6.1.4.1.193.72.300.35.5
OCT l2cpAccessNodeId	1.3.6.1.4.1.193.72.300.35.5.2	OCTET STRING	read-write	Specifies the first part of the access loop circuit id (l2cpAccessLoopCircuitId) used in port up / port down notifications (for addressing the port). If not set, the IP DSLAM will use defaults as described for l2cpAccessLoopCircuitId.
OCT l2cpSlotString	1.3.6.1.4.1.193.72.300.35.5.4	OCTET STRING	read-write	Specifies the middle part of the access loop circuit id (l2cpAccessLoopCircuitId) known as 'Slot'. Any kind of string can be used, as long as the guidelines from WT-101 are followed. Note: '/' '.' ':' should not be used for separators as they are already in use. If not set, the IP DSLAM will use defaults as described for l2cpAccessLoopCircuitId.
T/F l2cpForcePortEvents	1.3.6.1.4.1.193.72.300.35.5.7	TruthValue	read-write	Setting this parameter to true will force the IP-DSLAM to send PORT UP / PORT DOWN events for all DSL lines which has L2CP enabled. (l2cpPortUpEvent/l2cpPortDownEvent traps) Reading this parameter will always return false.
INT l2cpDslTransmissionSystem	1.3.6.1.4.1.193.72.300.35.5.9	INTEGER	accessible-for-notify	The DSL transmission system. Obsolete - replaced by l2cpLineTransmissionSystem.
l2cpPortTable	1.3.6.1.4.1.193.72.300.35.5.10		not-accessible	A list of entries in the L2CP port Table.
l2cpPortEntry	1.3.6.1.4.1.193.72.300.35.5.10.1		not-accessible	An entry containing port objects for the subscriber line identified by lineIndex.
T/F l2cpEnable	1.3.6.1.4.1.193.72.300.35.5.10.1.1	TruthValue	read-write	Enable of L2CP features in the IP-DSLAM for the specific port. The L2CP as specified by draft-wadhwa-gsmp-l2control-configuration-00 allows the BRAS to monitor and control certain parameters in the IP-DSLAM. If True, L2CP is enabled for the particular DSL line.
U32 l2cpPartitionId	1.3.6.1.4.1.193.72.300.35.5.10.1.2	Unsigned32	read-write	This parameters specify which partition the port belongs to. This allows multiple BRASs to control parts (partitions) of the IP-DSLAM with the L2CP.
OCT l2cpAccessLoopCircuitId	1.3.6.1.4.1.193.72.300.35.5.10.1.3	OCTET STRING	read-write	Specifies the string access loop circuit id used in port up / port down notifications (for addressing the port). The format complies with WT-101 from the DSL Forum. If this parameter is not written the string is initialized in the following manner: Access-Node-Identifier part precedence: 1. If l2cpAccessNodeId is set, this string is used. 2. Otherwise if relayAgentEdaIp is set this string is used. 3. Otherwise the IP address of the management interface is used. Slot part precedence: 1. If l2cpSlotString is set, this string is used. 2. Otherwise if relayAgentEdaNodeId is set this number is used. (formatted with 2 chars for ExtNo/SubRAck, 2 chars for PortLevel1/ Slot and 2 chars for PortLevel2/Reserved. A total of 6 chars.) 3. Otherwise a default slot '1' is used.
INT l2cpPortStatusEx	1.3.6.1.4.1.193.72.300.35.5.10.1.4	INTEGER	read-only	Show the current status of a DSL line as seen from L2CP. showTime = DSL line is active. idle = DSL line is not active. (De-activated on purpose) silent = DSL line is not active. (eg. CPE turned off)
INT l2cpTrapReason	1.3.6.1.4.1.193.72.300.35.5.10.1.5	INTEGER	read-only	Shows the reason for the latest l2cpPortDownEvent/l2cpPortUpEvent sent from the port. portTrapsNeverSent = Traps have never been sent for this port. portConditionsChanged = Trap sent since a change occured on the DSL line. portEventForced = Trap was forced by l2cpForcePortEvents. portNowEnabled = Trap sent since L2CP was enabled for this port. portNowDisabled = Trap sent since L2CP was disabled for this port. portMadeSRA = Trap sent since the DSL line made a seamless rate adaptation. portAdminStatusChanged = Trap sent since the admin status changed for this port.
INT l2cpLineTransmissionSystem	1.3.6.1.4.1.193.72.300.35.5.10.1.6	INTEGER	read-only	The DSL transmission system. Replaces l2cpDslTransmissionSystem and is now readable.
peaL2cpIpDslamTraps	1.3.6.1.4.1.193.72.300.35.10
peaL2cpIpDslamTrapsEntry	1.3.6.1.4.1.193.72.300.35.10.0
NTF l2cpPortDownEvent	1.3.6.1.4.1.193.72.300.35.10.0.1			A l2cpPortDownEvent trap signifies that the SNMPv2 entity, acting in an agent role, has detected that the adslIfOperStatus object for one of its communication links is about to enter the down state. This trap is used in the L2CP in order to signal port down. This is an internally used notification. Valid from: EDA 2.2 MA1 Parameters 1: Managed object class IP DSLAM Port 2: Managed object ID (MAC + PortNo) 3: Sequence number (Alarm sequence number) 4: Perceived severity Warning 5: Event time (Timestamp is retrieved from a SNTP server) 6: Event type Other 7: Probable cause Other 8: Partition ID (ID of the partition) 9: Access Loop Circuit ID (Identifier of the port) 10: Transmission system { ADSL1, ADSL2, ADSL2plus, VDSL1, VDSL2, SDSL } 11: Actual Data Rate Upstream ITU-T G.997, section 7.5.2.1 12: Actual Data Rate Downstream ITU-T G.997, section 7.5.2.1 13: DSL line state { IDLE or SILENT } 14: Trap reason { CONDITIONS_CHANGED, EVENT_FORCED, L2CP_ENABLED or L2CP_DISABLED }
NTF l2cpPortUpEvent	1.3.6.1.4.1.193.72.300.35.10.0.2			A l2cpPortDownEvent trap signifies that the SNMPv2 entity, acting in an agent role, has detected that the adslIfOperStatus object for one of its communication links is about to enter the down state. This trap is used in the L2CP in order to signal port up. This is an internally used notification. Valid from: EDA 2.2 MA1 Parameters 1: Managed object class IP DSLAM Port 2: Managed object ID (MAC + PortNo) 3: Sequence number (Alarm sequence number) 4: Perceived severity Warning 5: Event time (Timestamp is retrieved from a SNTP server) 6: Event type Other 7: Probable cause Other 8: Partition ID (ID of the partition) 9: Access Loop Circuit ID (Identifier of the port) 10: Transmission system { ADSL1, ADSL2, ADSL2plus, VDSL1, VDSL2, SDSL } 11: Actual Data Rate Upstream ITU-T G.997, section 7.5.2.1 12: Actual Data Rate Downstream ITU-T G.997, section 7.5.2.1 13: Minimum Data Rate Upstream (fast/interleaved) ITU-T G.997, section 7.3.2.1.1 14: Minimum Data Rate Downstream (fast/interleaved)ITU-T G.997, section 7.3.2.1.1 15: Attainable Data Rate Upstream ITU-T G.997, section 7.5.1.13 16: Attainable Data Rate Downstream ITU-T G.997, section 7.5.1.12 17: Maximum Data Rate Upstream (fast/interleaved) ITU-T G.997, section 7.3.2.1.3 18: Maximum Data Rate Downstream (fast/interleaved)ITU-T G.997, section 7.3.2.1.3 19: Maximum Interleaving Delay Upstream ITU-T G.997, section 7.3.2.2 20: Actual Interleaving Delay Upstream ITU-T G.997, section 7.5.2.3 21: Maximum Interleaving Delay Downstream ITU-T G.997, section 7.3.2.2 22: Actual Interleaving Delay Downstream ITU-T G.997, section 7.5.2.3 23: DSL line state { SHOWTIME } 24: Trap reason { CONDITIONS_CHANGED, EVENT_FORCED, L2CP_ENABLED or L2CP_DISABLED } Note: The following RAM parameters are not supported yet Minimum Low Power Data Rate Upstream ITU-T G.997, section 7.3.2.1.5 Minimum Low Power Data Rate Downstream ITU-T G.997, section 7.3.2.1.5

RFC description

Ericsson IP DSLAM L2CP protocol for BRAS-DSLAM communication and control management.

Start monitoring Ericsson Diax A/S IP DSLAM platforms (BRAS-DSLAM L2CP line signaling) 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 PEA-L2CP-IPDSLAM