Cisco Bug: CSCte15982 - PPPoE PADS processed on incorrect subinterface PVC on c878
Jan 31, 2017
- Cisco IOS
Known Affected Releases
Symptoms: When a Cisco 877 DSL router running Cisco IOS Release 12.4(24)T2 is connected to a 3rd party DSLAM running in 4-wire mode, entering the <CmdBold>clear pppoe all<noCmdBold> command may result in a PADS received on one PVC being incorrectly processed on a subinterface associated with a different PVC, which results in two PPPoE sessions transmitting data packets on the same PVC. Conditions: This symptom is observed under the following working scenario: CPE#show pppoe session 2 client sessions Uniq ID PPPoE RemMAC Port Source VA State SID LocMAC VA-st N/A 7 xxxx.xxxx.xxxx ATM0.38 Di0 Vi1 UP xxxx.xxxx.xxxx VC: 0/38 UP N/A 8 xxxx.xxxx.xxxx ATM0.40 Di1 Vi2 UP xxxx.xxxx.xxxx VC: 0/40 UP After 'clear pppoe all': CPE#clear pppoe all CPE#show pppoe session 2 client sessions Uniq ID PPPoE RemMAC Port Source VA State SID LocMAC VA-st N/A 9 xxxx.xxxx.xxxx ATM0.40 Di0 Vi1 UP xxxx.xxxx.xxxx VC: 0/40 UP N/A 10 xxxx.xxxx.xxxx ATM0.40 Di1 Vi2 UP xxxx.xxxx.xxxx VC: 0/40 UP controller DSL 0 mode atm line-mode 4-wire enhanced dsl-mode shdsl symmetric annex B interface ATM0.38 point-to-point pvc data 0/38 pppoe-client dial-pool-number 1 interface ATM0.40 point-to-point pvc voip 0/40 pppoe-client dial-pool-number 2 interface Dialer0 ip address negotiated encapsulation ppp dialer pool 1 keepalive 60 ppp pap sent-username email@example.com password 0 data interface Dialer1 ip address negotiated encapsulation ppp dialer pool 2 keepalive 60 ppp pap sent-username firstname.lastname@example.org password 0 voip 1. This symptom is not reproducible when running in 2-wire G.SHDSL mode. It is reproducible only when running "line-mode 4-wire enhanced". 2. The symptom is reproducible running Cisco IOS Release 12.4(15)T7, Release 12.4(15)T10, Release 12.4(20)T, Release 12.4(22)T, Release 12.4(22)T1, Release 12.4(24)T, Release 12.4(24)T1, Release 12.4(24)T2, Release 15.0(1)M. 3. The symptom can be triggered three ways: 3A. 'reload' 3B. If 'reload' results in correct behavior, 'clear pppoe all'. 3C. If 'reload' results in correct behavior, any subsequent event which results in both PPPoE sessions being torn down simultaneously. 5. The symptom is not reproducible if any packet layer debugs are enabled, such as 'debug pppoe packet' or 'debug atm packet'.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases