|
Table Of Contents
Monitoring PPPoE Sessions with SNMP
Prerequisites for Monitoring PPPoE Sessions with SNMP
Restrictions for Monitoring PPPoE Sessions with SNMP
Information About Monitoring PPPoE Sessions with SNMP
Benefits of Monitoring PPPoE Sessions with SNMP
How to Configure SNMP Monitoring of PPPoE Sessions
Enabling PPPoE Session Count SNMP Traps
Configuring the PPPoE Session-Count Threshold for the Router Using VPDN Groups
Configuring the PPPoE Session-Count Threshold for the Router Using BBA Groups
Configuring the PPPoE Session-Count Threshold for a PVC
Configuring the PPPoE Session-Count Threshold for a VC Class
Configuring the PPPoE Session-Count Threshold for an ATM PVC Range
Configuring the PPPoE Session-Count Threshold for an Individual PVC Within a Range
Verifying PPPoE Session-Count Thresholds
Monitoring and Maintaining PPPoE Session Counts and SNMP Notifications
Configuration Examples for Monitoring PPPoE Sessions with SNMP
Configuring PPPoE Session-Count SNMP Traps: Example
PPPoE Session-Count Threshold for the Router: Example
PPPoE Session-Count Threshold for a PVC: Example
PPPoE Session-Count Threshold for a VC Class: Example
PPPoE Session-Count Threshold for a PVC Range: Example
PPPoE Session-Count Threshold for an Individual PVC Within a PVC Range: Example
Feature Information for Monitoring PPPoE Sessions with SNMP
Monitoring PPPoE Sessions with SNMP
First Published: May 2, 2005Last Updated: July 24, 2009The PPPoE Session Count Management Information Base feature provides the ability to use Simple Network Management Protocol (SNMP) to monitor in real time the number of PPP over Ethernet (PPPoE) sessions configured on permanent virtual circuits (PVCs) and on a router.
This MIB also supports two SNMP traps that generate notification messages when a PPPoE session-count threshold is reached on any PVC or on the router. The PPPoE session-count thresholds can be configured using the sessions max limit and pppoe max-sessions commands.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Monitoring PPPoE Sessions with SNMP" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•Prerequisites for Monitoring PPPoE Sessions with SNMP
•Restrictions for Monitoring PPPoE Sessions with SNMP
•Information About Monitoring PPPoE Sessions with SNMP
•How to Configure SNMP Monitoring of PPPoE Sessions
•Configuration Examples for Monitoring PPPoE Sessions with SNMP
•Feature Information for Monitoring PPPoE Sessions with SNMP
Prerequisites for Monitoring PPPoE Sessions with SNMP
•You must understand the concepts described in the "Preparing for Broadband Access Aggregation" module.
•PPPoE sessions must be established using the procedures in the "Providing Protocol Support for Broadband Access Aggregation of PPPoE Sessions" module.
Restrictions for Monitoring PPPoE Sessions with SNMP
The snmp-server enable traps pppoe command enables SNMP traps only. It does not support inform requests.
Information About Monitoring PPPoE Sessions with SNMP
In order to perform monitoring of PPPoE sessions with SNMP, you should understand the following concepts:
•Benefits of Monitoring PPPoE Sessions with SNMP
Network Management Protocol
SNMP is a network management protocol used almost exclusively in TCP/IP networks. SNMP provides a means to monitor and control network devices and to manage configurations, statistics collection, performance, and security. SNMP version 2 supports centralized and distributed network management strategies and includes improvements in the Structure of Management Information (SMI), protocol operations, management architecture, and security.
PPPoE Session Count MIB
Note Effective with Cisco IOS Release 12.2(28)SB, the pppoe limit max-sessions command is replaced by the sessions max limit command in BBA group configuration mode. See the sessions max limit command for more information.
A MIB is a database of network management information that is used and maintained by a network management protocol, such as SNMP. The value of a MIB object can be changed or retrieved using SNMP commands, usually through a network management system.
The PPPoE Session Count MIB uses two SNMP traps that generate notification messages when a PPPoE session-count threshold is reached on any PVC or on the router. The PPPoE session-count thresholds can be configured using the pppoe limit max-sessions and pppoe max-sessions commands.
Table 1 describes the objects and tables supported by the PPPoE Session-Count MIB. For a complete description of the MIB, see the PPPoE Sessions Management MIB file CISCO-PPPOE-MIB.my, available through Cisco.com at the following URL: http://www.cisco.com/go/mibs.
Benefits of Monitoring PPPoE Sessions with SNMP
The monitoring of PPPoE sessions with SNMP provides the following benefits:
•It helps manage the number of PPPoE sessions configured on a router or PVC by sending notification messages when the PPPoE session threshold has been reached.
•It provides a way of tracking PPPoE session information over time.
How to Configure SNMP Monitoring of PPPoE Sessions
This section contains the following procedures:
•Enabling PPPoE Session Count SNMP Traps (required)
•Configuring the PPPoE Session-Count Threshold for the Router Using VPDN Groups (optional)
•Configuring the PPPoE Session-Count Threshold for the Router Using BBA Groups (optional)
•Configuring the PPPoE Session-Count Threshold for a PVC (optional)
•Configuring the PPPoE Session-Count Threshold for a VC Class (optional)
•Configuring the PPPoE Session-Count Threshold for an ATM PVC Range (optional)
•Configuring the PPPoE Session-Count Threshold for an Individual PVC Within a Range (optional)
•Verifying PPPoE Session-Count Thresholds (optional)
•Monitoring and Maintaining PPPoE Session Counts and SNMP Notifications (optional)
Enabling PPPoE Session Count SNMP Traps
Perform this task to enable SNMP traps that send notification messages when PPPoE session thresholds have been reached.
SUMMARY STEPS
1. enable
2. configure terminal
3. snmp-server enable traps pppoe
4. exit
DETAILED STEPS
Configuring the PPPoE Session-Count Threshold for the Router Using VPDN Groups
Note Effective with Cisco IOS Release 12.2(28)SB, the pppoe limit max-sessions command is replaced by the sessions max limit command in BBA group configuration mode. See the sessions max limit command for more information.
Perform this task to configure the PPPoE session-count threshold for the router using VPDN groups.
SUMMARY STEPS
1. enable
2. configure terminal
3. vpdn-group name
4. accept-dialin
5. protocol pppoe
6. virtual-template template-number
7. pppoe limit max-sessions number-of-sessions [threshold-sessions number-of-sessions]
8. exit
DETAILED STEPS
Configuring the PPPoE Session-Count Threshold for the Router Using BBA Groups
Perform this task to configure the PPPoE session-count threshold for the router using BBA groups.
SUMMARY STEPS
1. enable
2. configure terminal
3. bba-group pppoe global
4. virtual-template template-number
5. sessions max limit number-of-sessions [threshold number-of-sessions]
6. exit
DETAILED STEPS
Configuring the PPPoE Session-Count Threshold for a PVC
Perform this task to configure the PPPoE session-count threshold for a PVC.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface atm number [point-to-point | multipoint]
4. pvc [name] vpi/vci
5. pppoe max-sessions number-of-sessions [threshold-sessions number-of-sessions]
6. exit
DETAILED STEPS
Configuring the PPPoE Session-Count Threshold for a VC Class
Perform this task to configure the PPPoE session-count threshold for a VC class.
SUMMARY STEPS
1. enable
2. configure terminal
3. vc-class atm name
4. pppoe max-sessions number-of-sessions [threshold-sessions number-of-sessions]
5. exit
DETAILED STEPS
Configuring the PPPoE Session-Count Threshold for an ATM PVC Range
1. enable
2. configure terminal
3. interface atm number [point-to-point | multipoint]
4. range [range-name] pvc start-vpi/start-vci end-vpi/end-vci
5. pppoe max-sessions number-of-sessions [threshold-sessions number-of-sessions]
6. exit
DETAILED STEPS
Configuring the PPPoE Session-Count Threshold for an Individual PVC Within a Range
Perform this task to configure the PPPoE session-count threshold for an individual PVC within an ATM PVC range.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface atm number [point-to-point | multipoint]
4. range [range-name] pvc start-vpi/start-vci end-vpi/end-vci
5. pvc-in-range [pvc-name] [vpi/vci]
6. pppoe max-sessions number-of-sessions [threshold-sessions number-of-sessions]
7. exit
DETAILED STEPS
Verifying PPPoE Session-Count Thresholds
Use the following task to verify PPPoE session-count thresholds:
SUMMARY STEPS
1. enable
2. more system:running config
DETAILED STEPS
Step 1 enable
Use this command to enable privileged EXEC mode. Enter your password when prompted.
Router> enableStep 2 more system:running config
Use this command to display the running configuration.
Router# more system:running configBuilding configuration...Current configuration:!version 12.3no service udp-small-serversno service tcp-small-servers!hostname Router2!...!end
Monitoring and Maintaining PPPoE Session Counts and SNMP Notifications
Perform the following task to monitor PPPoE sessions counts and SNMP notifications:
SUMMARY STEPS
1. enable
2. debug snmp packets
3. debug pppoe errors interface atm interface-number
4. debug pppoe events interface atm interface-number vc vci-value
5. show vpdn [session] [packets] [tunnel] [all]
DETAILED STEPS
Step 1 enable
Use this command to enable privileged EXEC mode. Enter your password when prompted.
Router> enableStep 2 debug snmp packets
Use this command to display information about every SNMP packet sent or received by the router:
Router# debug snmp packetsSNMP: Packet received via UDP from 172.16.63.17 on Ethernet0SNMP: Get-next request, reqid 23584, errstat 0, erridx 0sysUpTime = NULL TYPE/VALUEsystem.1 = NULL TYPE/VALUEsystem.6 = NULL TYPE/VALUESNMP: Response, reqid 23584, errstat 0, erridx 0sysUpTime.0 = 2217027system.1.0 = Cisco Internetwork Operating System Softwaresystem.6.0 =SNMP: Packet sent via UDP to 172.16.63.17Step 3 debug pppoe errors interface atm interface-number
Use this command to display PPPoE protocol errors that prevent a session from being established or errors that cause an established session to be closed:
Router# debug pppoe errors interface atm 1/0.10PPPoE protocol errors debugging is onRouter#00:44:30:PPPoE 0:Max session count(1) on mac(00b0.c2e9.c470) reached.00:44:30:PPPoE 0:Over limit or Resource low. R:00b0.c2e9.c470 L:ffff.ffff.ffff 0/101ATM1/0.10Step 4 debug pppoe events interface atm interface-number vc vci-value
Use this command to display PPPoE protocol messages about events that are part of normal session establishment or shutdown:
Router# debug pppoe events interface atm 1/0.10 vc 101PPPoE protocol events debugging is onRouter#00:41:55:PPPoE 0:I PADI R:00b0.c2e9.c470 L:ffff.ffff.ffff 0/101 ATM1/0.1000:41:55:PPPoE 0:O PADO, R:00b0.c2e9.c470 L:0001.c9f0.0c1c 0/101 ATM1/0.1000:41:55:PPPoE 0:I PADR R:00b0.c2e9.c470 L:0001.c9f0.0c1c 0/101 ATM1/0.1000:41:55:PPPoE :encap string prepared00:41:55:[3]PPPoE 3:Access IE handle allocated00:41:55:[3]PPPoE 3:pppoe SSS switch updated00:41:55:[3]PPPoE 3:AAA unique ID allocated00:41:55:[3]PPPoE 3:No AAA accounting method list00:41:55:[3]PPPoE 3:Service request sent to SSS00:41:55:[3]PPPoE 3:Created R:0001.c9f0.0c1c L:00b0.c2e9.c470 0/101 ATM1/0.1000:41:55:[3]PPPoE 3:State REQ_NASPORT Event MORE_KEYS00:41:55:[3]PPPoE 3:O PADS R:00b0.c2e9.c470 L:0001.c9f0.0c1c 0/101 ATM1/0.1000:41:55:[3]PPPoE 3:State START_PPP Event DYN_BIND00:41:55:[3]PPPoE 3:data path set to PPP00:41:57:[3]PPPoE 3:State LCP_NEGO Event PPP_LOCAL00:41:57:PPPoE 3/SB:Sent vtemplate request on base Vi200:41:57:[3]PPPoE 3:State CREATE_VA Event VA_RESP00:41:57:[3]PPPoE 3:Vi2.1 interface obtained00:41:57:[3]PPPoE 3:State PTA_BIND Event STAT_BIND00:41:57:[3]PPPoE 3:data path set to Virtual Access00:41:57:[3]PPPoE 3:Connected PTAStep 5 show vpdn [session] [packets] [tunnel] [all]
Use this command to display information about active Level 2 Forwarding (L2F) protocol tunnel and message identifiers on a VPDN:
Router# show vpdn session%No active L2TP tunnels%No active L2F tunnelsPPPoE Session Information Total tunnels 1 sessions 1PPPoE Session InformationSID RemMAC LocMAC Intf VASt OIntf VC1 0010.7b01.2cd9 0090.ab13.bca8 Vi4 UP AT6/0 0/10
Configuration Examples for Monitoring PPPoE Sessions with SNMP
This section provides the following configuration examples:
•Configuring PPPoE Session-Count SNMP Traps: Example
•PPPoE Session-Count Threshold for the Router: Example
•PPPoE Session-Count Threshold for a PVC: Example
•PPPoE Session-Count Threshold for a VC Class: Example
•PPPoE Session-Count Threshold for a PVC Range: Example
•PPPoE Session-Count Threshold for an Individual PVC Within a PVC Range: Example
Configuring PPPoE Session-Count SNMP Traps: Example
The following example shows how to enable the router to send PPPoE session-count SNMP notifications to the host at the address 10.64.131.20:
snmp-server community public RWsnmp-server enable traps pppoesnmp-server host 10.64.131.20 version 2c public udp-port 1717PPPoE Session-Count Threshold for the Router: Example
Note Effective with Cisco IOS Release 12.2(28)SB, the pppoe limit max-sessions command is replaced by the sessions max limit command in BBA group configuration mode. See the sessions max limit command for more information.
The following example shows a limit of 4000 PPPoE sessions configured for the router through VPDN groups. The PPPoE session-count threshold is set at 3000 sessions, so when the number of PPPoE sessions on the router reaches 3000, an SNMP trap will be generated.
vpdn enableno vpdn logging!vpdn-group 1
accept-dialin
protocol pppoevirtual-template 1
pppoe limit max-sessions 4000 threshold-sessions 3000The following example shows a limit of 4000 PPPoE sessions configured for the router through BBA groups. The PPPoE session-count threshold is set at 3000 sessions, so when the number of PPPoE sessions on the router reaches 3000, an SNMP trap will be generated.
bba-group pppoe global
virtual-template 1
sessions max limit 4000 threshold 3000PPPoE Session-Count Threshold for a PVC: Example
The following example shows a limit of five PPPoE sessions configured for the PVC. The PPPoE session-count threshold is set at three sessions, so when the number of PPPoE sessions on the PVC reaches three, an SNMP trap will be generated.
interface ATM 0/0/0ip address 10.0.0.1 255.255.255.0no atm ilmi-keepalive
pvc 5/120protocol ip 10.0.0.2 broadcastpppoe max-sessions 5 threshold-sessions 3protocol pppoe
PPPoE Session-Count Threshold for a VC Class: Example
The following example shows a limit of seven PPPoE sessions configured for a VC class called "main." The PPPoE session-count threshold is set at three sessions, so when the number of PPPoE sessions for the VC class reaches three, an SNMP trap will be generated.
vc-class atm mainpppoe max-sessions 7 threshold-sessions 3PPPoE Session-Count Threshold for a PVC Range: Example
The following example shows a limit of 20 PPPoE sessions configured for the PVC range. The PPPoE session-count threshold will also be 20 sessions because when the session-count threshold has not been explicitly configured, it defaults to the PPPoE session limit. An SNMP trap will be generated when the number of PPPoE sessions for the range reaches 20.
interface ATM 0/0/0.3 point-to-point
range pvc 3/100 3/105pppoe max-sessions 20protocol pppoe
PPPoE Session-Count Threshold for an Individual PVC Within a PVC Range: Example
The following example shows a limit of ten PPPoE sessions configured for pvc1. The PPPoE session-count threshold is set at three sessions, so when the number of PPPoE sessions for the PVC reaches three, an SNMP trap will be generated.
interface atm 6/0.110 multipointrange range1 pvc 100 4/199pvc-in-range pvc1 3/104pppoe max-sessions 10 threshold-sessions 3Where to Go Next
•If you want to establish PPPoE session limits for sessions on a specific PVC or VLAN configured on an L2TP access concentrator, refer to the "Establishing PPPoE Session Limits per NAS Port" module.
•If you want to use service tags to enable a PPPoE server to offer PPPoE clients a selection of service during call setup, refer to the "Offering PPPoE Clients a Selection of Services During Call Setup" module.
•If you want to enable an L2TP access concentrator to relay active discovery and service selection functionality for PPPoE over an L2TP control channel to a LNS or tunnel switch, refer to the "Enabling PPPoE Relay Discovery and Service Selection Functionality" module.
•If you want to configure the transfer upstream of the PPPoX session speed value, refer to the "Configuring Upstream Connection Speed Transfer" module.
•If you want to identify a physical subscriber line for RADIUS communication with a RADIUS server, refer to the "Identifying the Physical Subscriber Line for RADIUS Access and Accounting" module.
•If you want to configure a Cisco Subscriber Service Switch, refer to the "Configuring Cisco Subscriber Service Switch Policies" module.
Additional References
The following sections provide references related to monitoring PPPoE sessions with SNMP.
Related Documents
Related Topic Document TitleBroadband access aggregation concepts
Tasks for preparing for broadband access aggregation
Configuring PPPoE sessions
Providing Protocol Support for Broadband Access Aggregation of PPPoE Sessions
Establishing PPPoE session limits for sessions on a specific PVC or VLAN configured on an L2TP access concentrator
Using service tags to enable a PPPoE server to offer PPPoE clients a selection of service during call setup
Offering PPPoE Clients a Selection of Services During Call Setup
Enabling an L2TP access concentrator to relay active discovery and service selection functionality for PPPoE over an L2TP control channel to a LNS or tunnel switch
Enabling PPPoE Relay Discovery and Service Selection Functionality
Configuring the transfer upstream of the PPPoX session speed value
Identifying a physical subscriber line for RADIUS communication with a RADIUS server
Identifying the Physical Subscriber Line for RADIUS Access and Accounting
Configuring a Cisco Subscriber Service Switch
Standards
MIBs
MIBs MIBs LinkPPPoE Session Count MIB
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Feature Information for Monitoring PPPoE Sessions with SNMP
Table 2 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(1)DC or later releases appear in the table.
For information on a feature in this technology that is not documented here, see the "Configuring Broadband Access Aggregation Features Roadmap."
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 2 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
Table 2 Feature Information for Monitoring PPPoE Sessions with SNMP
Feature Name Releases Feature Configuration InformationPPPoE Session Count MIB
12.2(1)DC
12.2(8)T
12.2(33)SRCThis feature provides the ability to use Simple Network Management Protocol (SNMP) to monitor in real time the number of PPP over Ethernet sessions configured on permanent virtual circuits (PVCs) and on a router.
The following sections provide information about this feature:
•"Information About Monitoring PPPoE Sessions with SNMP" section
•"How to Configure SNMP Monitoring of PPPoE Sessions" section
The following commands were introduced or modified: pppoe limit max-sessions, pppoe max-sessions, sessions max limit.
Glossary
ATM—Asynchronous Transfer Mode. The international standard for cell relay in which multiple service types (such as voice, video, or data) are conveyed in fixed-length (53-byte) cells. Fixed-length cells allow cell processing to occur in hardware, thereby reducing transit delays. ATM is designed to take advantage of high-speed transmission media, such as E3, SONET, and T3.
MIB—Management Information Base. Database of network management information that is used and maintained by a network management protocol such as SNMP. The value of a MIB object can be changed or retrieved using SNMP commands, usually through a network management system (NMS). MIB objects are organized in a tree structure that includes public (standard) and private (proprietary) branches.
PVC—Permanent Virtual Circuit. Virtual circuit that is permanently established. PVCs save bandwidth associated with circuit establishment and teardown in situations where certain virtual circuits must exist all the time. In ATM terminology, PVC also stands for permanent virtual connection.
SNMP—Simple Network Management Protocol. An application-layer protocol that provides a message format for communication between SNMP managers and agents and is exclusively used in TCP/IP networks. SNMP provides a means to monitor and control network devices and to manage configurations, statistics collection, performance, and security.
trap—A message from an SNMP agent alerting the SNMP manager to a condition on the network.
VCI—Virtual Channel Identifier. 16-bit field in the header of an ATM cell. The VCI, together with the VPI, is used to identify the next destination of a cell as it passes through a series of ATM switches on its way to its destination. ATM switches use the VPI/VCI fields to identify the next network VCL that a cell needs to transit on its way to its final destination.
VCL—Virtual Channel Link. Connection between two ATM devices.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flip Video, Flip Video (Design), Flipshare (Design), Flip Ultra, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0907R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2005-2009 Cisco Systems, Inc. All rights reserved.