CISCO-PPPOE-MIB

        Cisco PPPoE sessions management MIB Module.
    
Source file
CISCO-PPPOE-MIB
Last revised
Identity
ciscoPppoeMIB
Base OID
1.3.6.1.4.1.9.9.194
Imported Objects
ATM-MIB atmVclEntry atmVclVci atmVclVpi
ATM-TC-MIB AtmVcIdentifier AtmVpIdentifier
CISCO-QOS-PIB-MIB Percent
CISCO-SMI ciscoMgmt
IF-MIB ifDescr ifIndex
Q-BRIDGE-MIB VlanId VlanIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Gauge32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC MacAddress TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-PPPOE-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-PPPOE-MIB::ciscoPppoeMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-PPPOE-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-PPPOE-MIB::ciscoPppoeMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (49)
.1.3.6.1.4.1.9.9.194
.1.3.6.1.4.1.9.9.194.1
.1.3.6.1.4.1.9.9.194.1.1
.1.3.6.1.4.1.9.9.194.1.1.1
.1.3.6.1.4.1.9.9.194.1.1.10
.1.3.6.1.4.1.9.9.194.1.1.11
.1.3.6.1.4.1.9.9.194.1.1.12
.1.3.6.1.4.1.9.9.194.1.1.13
.1.3.6.1.4.1.9.9.194.1.1.14
.1.3.6.1.4.1.9.9.194.1.1.2
.1.3.6.1.4.1.9.9.194.1.1.3
.1.3.6.1.4.1.9.9.194.1.1.4
.1.3.6.1.4.1.9.9.194.1.1.5
.1.3.6.1.4.1.9.9.194.1.1.6
.1.3.6.1.4.1.9.9.194.1.1.7
.1.3.6.1.4.1.9.9.194.1.1.8
.1.3.6.1.4.1.9.9.194.1.1.9
.1.3.6.1.4.1.9.9.194.1.2
.1.3.6.1.4.1.9.9.194.1.2.1
.1.3.6.1.4.1.9.9.194.1.2.1.1
.1.3.6.1.4.1.9.9.194.1.2.1.1.1
.1.3.6.1.4.1.9.9.194.1.3
.1.3.6.1.4.1.9.9.194.1.3.1
.1.3.6.1.4.1.9.9.194.1.3.1.1
.1.3.6.1.4.1.9.9.194.1.3.1.1.1
.1.3.6.1.4.1.9.9.194.1.3.1.1.2
.1.3.6.1.4.1.9.9.194.1.3.1.1.3
.1.3.6.1.4.1.9.9.194.1.3.1.1.4
.1.3.6.1.4.1.9.9.194.1.3.1.1.5
.1.3.6.1.4.1.9.9.194.1.4
.1.3.6.1.4.1.9.9.194.1.4.1
.1.3.6.1.4.1.9.9.194.1.4.1.1
.1.3.6.1.4.1.9.9.194.1.4.1.1.1
.1.3.6.1.4.1.9.9.194.1.4.1.1.2
.1.3.6.1.4.1.9.9.194.1.4.1.1.3
.1.3.6.1.4.1.9.9.194.1.4.1.1.4
.1.3.6.1.4.1.9.9.194.1.4.1.1.5
.1.3.6.1.4.1.9.9.194.1.4.1.1.6
.1.3.6.1.4.1.9.9.194.1.5
.1.3.6.1.4.1.9.9.194.1.5.1
.1.3.6.1.4.1.9.9.194.1.5.2
.1.3.6.1.4.1.9.9.194.1.5.3
.1.3.6.1.4.1.9.9.194.1.5.4
.1.3.6.1.4.1.9.9.194.1.5.5
.1.3.6.1.4.1.9.9.194.2
.1.3.6.1.4.1.9.9.194.2.0
.1.3.6.1.4.1.9.9.194.3
.1.3.6.1.4.1.9.9.194.3.1
.1.3.6.1.4.1.9.9.194.3.2
Dependencies (21) 9 direct · 12 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Conformance Groups (8)
A collection of objects providing information about the
PPPoE sessions on a system.
.1.3.6.1.4.1.9.9.194.3.2.1
A collection of objects specifying PPPoE protocol
related configuration on the VCL.
.1.3.6.1.4.1.9.9.194.3.2.2
A collection of objects providing information about the
number of sessions on the VCL.
.1.3.6.1.4.1.9.9.194.3.2.3
The collection of notifications used to indicate
high PPPoE session volume information(e.g, the
number of current PPPoE sessions exceeds threshold
setting for the system or a VCL).
.1.3.6.1.4.1.9.9.194.3.2.4
A collection of objects providing PPPoE per-interface
session state counts and configured threshold
informations.
.1.3.6.1.4.1.9.9.194.3.2.5
A collection of objects providing the session limit or
throttling configuration. There are various Limitation
we can impose on PPPoE Sessions it may be limit based on
client-MAC or VLAN When ever the limitation is crossed
we send out traps.
.1.3.6.1.4.1.9.9.194.3.2.6
This group is collection of notify objects which are
used to carry notify information along with certain
traps which implements Session restriction such as
limit or throttling.
.1.3.6.1.4.1.9.9.194.3.2.7
This group is collection of notify objects used to
send traps on various session restriction crossed.
.1.3.6.1.4.1.9.9.194.3.2.8
Compliance Statements (2)

OID .1.3.6.1.4.1.9.9.194.3.1.1
The compliance statement for entities which implement
the Cisco Basic PPPoE MIB.
Required groups

OID .1.3.6.1.4.1.9.9.194.3.1.2
The compliance statement for entities which implement
the Cisco Basic PPPoE MIB.
Required groups
Object refinements
ObjectAccessSyntaxDescription
cPppoeSystemPerMacSessionlimit readonly
The minimum access to this object is read only
cPppoeSystemPerMacIWFSessionlimit readonly
The minimum access to this object is read only
cPppoeSystemPerMacThrottleRatelimit readonly
The minimum access to this object is read only
cPppoeSystemPerVLANlimit readonly
The minimum access to this object is read only
cPppoeSystemPerVLANthrottleRatelimit readonly
The minimum access to this object is read only
cPppoeSystemPerVClimit readonly
The minimum access to this object is read only
cPppoeSystemPerVCThrottleRatelimit readonly
The minimum access to this object is read only
cPppoeSystemSessionLossThreshold readonly
The minimum access to this object is read only
cPppoeSystemSessionLossPercent readonly
The minimum access to this object is read only
Notifications / Traps (12)
NameOIDDescription
.1.3.6.1.4.1.9.9.194.2.0.1
A notification indicating that number of active
sessions on the system exceeded system sessions
threshold value. System sessions threshold value
is indicated by cPppoeSystemThresholdSessions.

An agent must not generate more than one
cPppoeSessionThresholdTrap `trap-event` in a
30 second period, where a `trap-event` is the
transmission of a single trap PDU to a list of
trap destinations. If additional `the number of
PPPoE sessions exceeds threshold` condition
occur within the 30 second `throttling` period,
then these trap-events should be suppressed by
the agent. An NMS should periodically check the
value of cPppoeCurrSessions to detect any
missed cPppoeVcSessionThresholdTrap trap-events,
e.g. due to throttling or transmission loss.
Where 30 is the `throttling` period of trap-event.
.1.3.6.1.4.1.9.9.194.2.0.10
A notification indicating that number of PPPoE session
initiated via a particular interface has dropped below
the configured value for that interface.
The interface details can be referred via ifDescr object,
and the configured watermark can be referred through
cPppoePerInterfaceSessionLossThreshold object.

There will be only one trap send whenever
count drops, further low count won't generate trap.
Number of PPPoE sessions count need to cross
the watermark and drop below watermark to generate
trap again.

An agent must not generate more than one
cPppoePerInterfaceSessionLossThresholdTrap `trap-event`
in a 30 second period, where a `trap-event` is the
transmission of a single trap PDU to a list of
trap destinations. If the PPPoE session count keep on
fluctuating around the watermark during 30 seconds, then
these trap-events should be suppressed by agent.
.1.3.6.1.4.1.9.9.194.2.0.11
A notification indicating that percentage of PPPoE session
lost globally over a duration of time has crossed the
configured threshold. The configured percentage water mark
can be referred through cPppoeSystemSessionLossPercent
object.
.1.3.6.1.4.1.9.9.194.2.0.12
A notification indicating that percentage of PPPoE sessions
lost has crossed configured threshold value for a
particular interface. The interface details can be referred
through ifDescr object, and the configured threshold for
the interface can be referred through
cPppoePerInterfaceSessionLossPercent.
.1.3.6.1.4.1.9.9.194.2.0.2
A notification indicating that number of active
sessions on the VC exceeded vc sessions
threshold value. VC sessions threshold value is
indicated by cPppoeVcThresholdSessions.

An agent must not generate more than one
cPppoeVcSessionThresholdTrap `trap-event` in a
30 second period, where a `trap-event` is the
transmission of a single trap PDU to a list of
trap destinations. If additional `the number of
PPPoE sessions exceeds threshold` condition
occur within the 30 second `throttling` period,
then these trap-events should be suppressed by
the agent. An NMS should periodically check the
value of cPppoeVcCurrSessions to detect any
missed cPppoeVcSessionThresholdTrap trap-events,
e.g. due to throttling or transmission loss.
Where 30 is the `throttling` period of trap-event.
.1.3.6.1.4.1.9.9.194.2.0.3
A notification indicating that number of active session
from a particular client Ethernet MAC address has reached
the configured per MAC limit. There won't be any more
session possible from this client MAC address.

An agent must not generate more than one
cPppoeSystemSessionPerMACLimitNotif `trap-event` in a
30 second period, where a `trap-event` is the
transmission of a single trap PDU to a list of
trap destinations. If additional `the number of
PPPoE MAC sessions exceeds the allowed limit` condition
occur within the 30 second `throttling` period,
then these trap-events should be suppressed by
the agent.
.1.3.6.1.4.1.9.9.194.2.0.4
A notification indicating that the number of new PPPoE
session requests coming in over a configured time
interval, from a particular client Ethernet MAC address,
has crossed rate limit cPppoeSystemPerMacThrottleRatelimit.
The client MAC address on which this event happened is
referred through object cPppoeSystemSessionClientMacAddress

An agent should generate single
cPppoeSystemSessionPerMACThrottleNotif trap for configured
time interval.
.1.3.6.1.4.1.9.9.194.2.0.5
A notification indicating that number of active session on
a Vlan has reached the maximum limit. There won't be any
new PPPoE session possible on this Vlan. The maximum limit
can be referred through object cPppoeSystemPerVLANlimit.
The Vlan ID of vlan can be referred though object
cPppoeSystemSessionVlanID. If Vlan is QinQ,
cPppoeSystemSessionInnerVlanID refers the
inner Vlan id. In case the vlan is not QinQ
cPppoeSystemSessionInnerVlanID will be zero. The interface
details can be referred through ifDescr object.

An agent must not generate more than one
cPppoeSystemSessionPerVLANLimitNotif `trap-event` in a
30 second period, where a `trap-event` is the
transmission of a single trap PDU to a list of
trap destinations. If additional `the number of
PPPoE sessions on this Vlan exceeds the allowed limit`
condition occur within the 30 second `throttling` period,
then these trap-events should be suppressed by
the agent.
.1.3.6.1.4.1.9.9.194.2.0.6
A notification indicating that the number of new PPPoE
session request coming on a particular Vlan, over a
configured time interval has reached rate limit.
The rate limit is referred through object
cPppoeSystemPerVLANthrottleRatelimit.
The Vlan ID of vlan can be referred though object
cPppoeSystemSessionVlanID. If Vlan is QinQ,
cPppoeSystemSessionInnerVlanID refers the
inner Vlan Id. In case the vlan is not QinQ
cPppoeSystemSessionInnerVlanID will be zero. The
interface details can be referred through ifDescr object.

An agent should generate single
cPppoeSystemSessionPerVLANThrottleNotif trap for the
configured time interval
.1.3.6.1.4.1.9.9.194.2.0.7
A notification indicating that number of active sessions
for a ATM VCI/VPI has crossed the configured maximum
limit. No more session would be possible on this VC
interface. The maximum limit can be referred through
object cPppoeSystemPerVClimit, The ATM VC details are
referred via objects cPppoeSystemSessionVci, and
cPppoeSystemSessionVpi. The Interface details can be
referred via ifDescr object.

An agent must not generate more than one
cPppoeSystemSessionPerVCLimitTrap `trap-event` in a
30 second period, where a `trap-event` is the
transmission of a single trap PDU to a list of
trap destinations. If additional `the number of
PPPoE sessions on this VC exceeds the allowed limit`
condition occur within the 30 second `throttling` period,
then these trap-events should be suppressed by
the agent.
.1.3.6.1.4.1.9.9.194.2.0.8
A notification indicating that the number of new PPPoE
session request coming on a particular ATM VC, over a
configured time interval has reached rate limit.
The rate limit referred is referred through object
cPppoeSystemPerVLANthrottleRatelimit.
The ATM VC details are referred via objects
cPppoeSystemSessionVci and cPppoeSystemSessionVpi.
The Interface details can be referred via ifDescr object.

An agent should generate single
cPppoeSystemSessionPerVLANThrottleNotif trap for the
configured time interval
.1.3.6.1.4.1.9.9.194.2.0.9
A notification indicating that number of PPPoE session
count dropped below configured global threshold
watermark. There will be only one trap send whenever
count drops, further low count won't generate trap.
Number of PPPoE sessions count need to cross
the watermark and drop below watermark to generate
trap again. The configured watermark can be referred
through object cPppoeSystemSessionLossThreshold.

An agent must not generate more than one
cPppoeSystemSessionLossThresholdTrap `trap-event` in a
30 second period, where a `trap-event` is the
transmission of a single trap PDU to a list of
trap destinations. If the PPPoE session count keep on
fluctuating around the watermark during 30 seconds, then
these trap-events should be suppressed by agent.