cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2677
Views
0
Helpful
15
Replies

% pvc already member of PPPoA dialer pool

johanhanekom
Level 1
Level 1

Hi,

I'm trying to establish a second connection to a different ISP using a single ATM/HWIC-ADSL Line as per this document: http://www.cisco.com/en/US/docs/ios/12_4t/12_4t15/mpppoec.html

The router is running Cisco IOS Software, 1841 Software (C1841-ADVSECURITYK9-M), Version 12.4(24)T3, RELEASE SOFTWARE (fc2)

When i try to add the second dial-pool-number to ATM I get the following error:

Enter configuration commands, one per line.  End with CNTL/Z.

rtr(config)#interface ATM0/0/0

rtr(config-if)# pvc 8/35

rtr(config-if-atm-vc)#  oam-pvc 0

rtr(config-if-atm-vc)#  pppoe-client dial-pool-number 3

% pvc already member of PPPoA dialer pool

rtr(config-if-atm-vc)# !

rtr(config-if-atm-vc)#!

Current Config is: 

!

interface ATM0/0/0

no ip address

no ip redirects

no ip unreachables

no ip proxy-arp

ip flow ingress

no ip mroute-cache

no atm ilmi-keepalive

pvc 8/35

  oam-pvc 0

  pppoe-client dial-pool-number 1

!

!

interface Dialer0

description Primary ISP

no ip redirects

no ip unreachables

no ip proxy-arp

ip mtu 1452

ip flow ingress

ip nat outside

ip virtual-reassembly

encapsulation ppp

dialer pool 1

dialer-group 1

!

interface Dialer2

Secondary ISP

ip address negotiated

no ip redirects

no ip unreachables

no ip proxy-arp

ip mtu 1452

ip flow ingress

ip virtual-reassembly

encapsulation ppp

dialer pool 3

dialer-group 3

no cdp enable

!

Regards,

Johan Hanekom

1 Accepted Solution

Accepted Solutions

Hi Johan,

Well, at least I know now exactly what you are trying to accomplish but the funny thing is that I do not know why your router prevents you from doing that. It definitely should, and your original way of configuration was correct.

You are absolutely correctly trying to run a new PPPoE client over the same PVC which should be supported on IOSes 12.4(15)T and newer. However, despite running IOS 12.4(24)T3, your router does not accept running a second PPPoE client on the same PVC. Even more strange, the router complains that the PVC is already in a PPPoA dialer pool which is illogical as you are not running PPPoA.

This may be an IOS bug. Do you have an option of upgrading to either the newest 12.4T or 15.0M IOS? Using a G.SHDSL interface in my lab, I could configure my router to establish two PPPoE sessions over a single ATM PVC exactly as the original document suggested:

interface ATM0/1/0

no ip address

no atm ilmi-keepalive

!

pvc 1/32

  oam-pvc 0

  pppoe-client dial-pool-number 2

  pppoe-client dial-pool-number 1

!

!

interface Dialer1

ip address negotiated

encapsulation ppp

dialer pool 1

!

!

interface Dialer2

ip address negotiated

encapsulation ppp

dialer pool 2

!

Router#show ip int brief

Interface                  IP-Address      OK? Method Status                Protocol

FastEthernet0/0            unassigned      YES unset  administratively down down

FastEthernet0/1            unassigned      YES unset  administratively down down

Serial0/0/0                unassigned      YES unset  administratively down down

Serial0/0/1                unassigned      YES unset  administratively down down

ATM0/1/0                   unassigned      YES unset  up                    up 

Dialer1                    192.0.2.2       YES IPCP   up                    up 

Dialer2                    192.0.2.1       YES IPCP   up                    up 

Virtual-Access1            unassigned      YES unset  up                    up 

Virtual-Access2            unassigned      YES unset  up                    up 

The router is running Cisco IOS Software, 1841 Software (C1841-ADVIPSERVICESK9-M), Version 15.0(1)M3, RELEASE SOFTWARE (fc2).

Besides that, does the show atm pvc ppp produce any interesting output? That should show you PPPoA sessions - if there are any which they should not, according to your configuration.

Best regards,

Peter

View solution in original post

15 Replies 15

Peter Paluch
Cisco Employee
Cisco Employee

Johan,

I doubt that what you are trying to accomplish is realistic. A single ATM PVC that provides the data delivery within the basic DSL service is a point-to-point data conduit. It has only a single end terminated at one particular ISP (simplified a bit but basically valid). You cannot have a single PVC go to two different ISPs. If you want to use a single DSL interface to connect to two different ISPs then

  • Either you have to configure a separate PVC identified by a different set of VPI/VCI that is directed towards your second ISP, and you then assign your Dialer interfaces each to a different dialer pool, hence to a different PVC
  • Or you use the same PVC and assign both Dialer interfaces to the same dialer pool but the PAP/CHAP username configured on each Dialer will contain a unique ID of the ISP, for example:

interface Dialer0

encapsulation ppp

ppp chap hostname user@isp1.com

ppp chap password XXX

dialer pool 1

ip address negotiated

!

interface Dialer2

encapsulation ppp

ppp chap hostname user@isp2.com

ppp chap password XXX

dialer pool 1

ip address negotiated

!

The unique login will then help your DSL service provider to properly tunnel your session towards your two ISPs.

Best regards,

Peter

Hi Peter

I changed the config but now dialer2 is not connecting even with a static route:

ip route 172.29.1.0 255.255.255.0 Dialer2 permanent

rtr#sh ip int brief
Interface                  IP-Address      OK? Method Status                Protocol
FastEthernet0/0            xxx.xxx.97.1     YES NVRAM  up                    up
FastEthernet0/1            unassigned      YES NVRAM  up                    up
ATM0/0/0                   unassigned      YES NVRAM  up                    up
NVI0                       xxx.xxx.97.1     YES unset  up                    up
Virtual-Access1            unassigned      YES unset  up                    up
Virtual-Access2            unassigned      YES unset  up                    up
Virtual-Access3            unassigned      YES unset  up                    up
Dialer0                    xxx.xxx.102.167  YES IPCP   up                    up
Dialer1                    xxx.xx.199.236  YES IPCP   up                    up
Dialer2                    unassigned      YES NVRAM  up                    up
Loopback0                  xxx.xxx.6.50     YES NVRAM  up                    up
rtr#

Regards,

Johan Hanekom

Hello Johan,

Can you please post your current configuration? It is difficult to debug a configuration that is not known ...

Best regards,

Peter

Hi Peter

See below:


Regards,

Johan Hanekom

Current configuration : 12356 bytes
!
interface ATM0/0/0
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
ip flow ingress
no ip mroute-cache
no atm ilmi-keepalive
pvc 8/35
  oam-pvc 0
  pppoe-client dial-pool-number 1
!
!
interface Dialer0
description ISP1
ip address negotiated
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1452
ip flow ingress
ip nat outside
ip virtual-reassembly
encapsulation ppp
dialer pool 1
ppp chap password 7 xxxxxxxxxxxxxxxxxxxxxxxx
ppp pap sent-username user@isp1.com password 7 xxxxxxxxxxxxxxxxxxxxxxxxx
service-policy output EDGE-VOICE
!

interface Dialer2
description ISP2
ip address negotiated
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1452
ip flow ingress
ip virtual-reassembly
encapsulation ppp
dialer pool 1
no cdp enable
ppp authentication chap pap callin
ppp chap hostname user@dsl-isp2.com
ppp chap password 7 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ppp pap sent-username user@dsl-isp2.com password 7 xxxxxxxxxxxxxxxxxxxxxxxxxxx
!

Johan,

The problem that the route through Dialer2 does not appear in your routing table is based on the fact that the Dialer2 has not received any IP address from your ISP - basically, it has not become an IP-operational interface. Why is that I cannot say right now. Perhaps the Dialer2 was not able at all to negotiate a connection to your ISP.

Remove the ppp authentication chap pap callin command and do not replace it with any other similar command. Then please shutdown the Di2 interface and start these debugs:

debug pppoe events

debug ppp negotiation

debug ppp authentication

After all these debugs are in place, enter the no shutdown command on the Di2 interface, capture the debug output and post it here please for further analysis. Thanks!

Best regards,

Peter

Hi Peter

I've remove the ppp auth and no change. see below:

rtr(config)#interface dialer 2

rtr(config-if)#shutdown

rtr(config-if)#

rtr#

000090: *Jul 13 18:07:39.190 PCTime: Di2 DDR: dialer shutdown complete

000091: *Jul 13 18:07:40.322 PCTime: %SYS-5-CONFIG_I: Configured from console by spme on vty0 (xxx.xxx.5.92)

000092: *Jul 13 18:07:41.190 PCTime: %LINK-5-CHANGED: Interface Dialer2, changed state to administratively down

rtr#

rtr#

rtr#debug pppoe events

PPPoE protocol events debugging is on

rtr#debug ppp negotiation

PPP protocol negotiation debugging is on

rtr#debug ppp authentication

PPP authentication debugging is on

rtr#conf

rtr#configure t

rtr#configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

rtr(config)#int

rtr(config)#interface di

rtr(config)#interface dialer 2

rtr(config-if)#no su

rtr(config-if)#no sh

rtr(config-if)#no shutdown

rtr(config-if)#

000093: *Jul 13 18:08:08.278 PCTime: %LINK-3-UPDOWN: Interface Dialer2, changed state to up

rtr(config-if)#

rtr(config-if)#

rtr(config-if)#

rtr#sh ip int br

Interface                  IP-Address      OK? Method Status                Protocol

FastEthernet0/0            xxx.xxx.97.1     YES NVRAM  up                    up

FastEthernet0/1            unassigned      YES NVRAM  up                    up

ATM0/0/0                   unassigned      YES NVRAM  up                    up

NVI0                       xxx.xxx.97.1     YES unset  up                    up

Virtual-Access1            unassigned      YES unset  up                    up

Virtual-Access2            unassigned      YES unset  up                    up

Virtual-Access3            unassigned      YES unset  up                    up

Dialer0                    xxx.xxx.102.167  YES IPCP   up                    up

Dialer1                    xxx.xxx.199.236  YES IPCP   up                    up

Dialer2                    unassigned      YES NVRAM  up                    up

Loopback0                  xxx.xxx.6.50     YES NVRAM  up                    up

Regards,

Johan Hanekom

Hi Peter

When I shutdown Dialer0, Dialer2 connected, see below:

Regards,

Johan Hanekom

rtr(config)#interface dialer0

rtr(config-if)#shu

rtr(config-if)#shutdown

000096: *Jul 13 18:14:39.450 PCTime:  PPPoE : Shutting down client session

000097: *Jul 13 18:14:39.450 PCTime: [0]PPPoE 52008: O PADT  R:0017.5a88.4524 L:0024.97c2.2488 8/35  ATM0/0/0

000098: *Jul 13 18:14:39.450 PCTime: Vi3 IPCP: Remove link info for cef entry xxx.xxx.86.1

000099: *Jul 13 18:14:39.450 PCTime: Vi3 PPP: Sending Acct Event[Down] id[4]

000100: *Jul 13 18:14:39.450 PCTime: Vi3 IPCP: State is Closed

000101: *Jul 13 18:14:39.450 PCTime: Vi3 PPP SSS: Send DISCONNECT to mgr_hdl[2F000003]

000102: *Jul 13 18:14:39.454 PCTime: Vi3 PPP: Phase is ESTABLISHING, renegotiate LCP

000103: *Jul 13 18:14:39.454 PCTime: Vi3 PPP: Authorization NOT required

000104: *Jul 13 18:14:39.454 PCTime: Vi3 PPP: No remote authentication for call-out

000105: *Jul 13 18:14:39.454 PCTime: Vi3 LCP: O CONFREQ [Closed] id 3 len 10

000106: *Jul 13 18:14:39.454 PCTime: Vi3 LCP:    MagicNumber 0x25993B6A (0x050625993B6A)

000107: *Jul 13 18:14:39.454 PCTime: PPPoE: Vi3: No Session, Packet Discarded

000108: *Jul 13 18:14:39.478 PCTime: %DIALER-6-UNBIND: Interface Vi3 unbound from profile Di0

000109: *Jul 13 18:14:39.490 PCTime: Vi3 PPP: Block vaccess from being freed [0x10]

000110: *Jul 13 18:14:39.490 PCTime: Di0 DDR: dialer shutdown complete

000111: *Jul 13 18:14:39.506 PCTime: %LINK-3-UPDOWN: Interface Virtual-Access3, changed state to down

000112: *Jul 13 18:14:39.522 PCTime: Vi3 PPP: Sending Acct Event[Down] id[4]

000113: *Jul 13 18:14:39.522 PCTime: Vi3 LCP: State is Closed

000114: *Jul 13 18:14:39.522 PCTime: Vi3 PPP: Phase is DOWN

000115: *Jul 13 18:14:39.522 PCTime: Vi3 PPP: Unlocked by [0x10] Still Locked by [0x2]

000116: *Jul 13 18:14:39.522 PCTime: Vi3 PPP: Unlocked by [0x2] Still Locked by [0x0]

000117: *Jul 13 18:14:39.522 PCTime: Vi3 PPP: Free previously blocked vaccess

000118: *Jul 13 18:14:39.550 PCTime: Di0 IPCP: Remove route to xxx.xxx.86.1

000119: *Jul 13 18:14:39.562 PCTime: %ADJ-5-PARENT: Midchain parent maintenance for IP midchain out of Tunnel1 661488C0 - looped chain attempting to stack

000120: *Jul 13 18:14:40.450 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to down

000121: *Jul 13 18:14:40.494 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to down

000122: *Jul 13 18:14:40.494 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel1, changed state to down

000125: *Jul 13 18:14:59.502 PCTime: Sending PADI: vc=8/35

000126: *Jul 13 18:14:59.510 PCTime: PPPoE 0: I PADO  R:0017.5a88.4524 L:0024.97c2.2488 8/35  ATM0/0/0

000127: *Jul 13 18:15:01.550 PCTime:  PPPOE: we've got our pado and the pado timer went off

000128: *Jul 13 18:15:01.550 PCTime: OUT PADR from PPPoE Session

000129: *Jul 13 18:15:01.558 PCTime: PPPoE 58563: I PADS  R:0017.5a88.4524 L:0024.97c2.2488 8/35  ATM0/0/0

000130: *Jul 13 18:15:01.562 PCTime: IN PADS from PPPoE Session

000131: *Jul 13 18:15:01.562 PCTime: %DIALER-6-BIND: Interface Vi3 bound to profile Di2

000132: *Jul 13 18:15:01.562 PCTime: PPPoE: Virtual Access interface obtained.

000133: *Jul 13 18:15:01.562 PCTime: PPPoE : encap string prepared

000134: *Jul 13 18:15:01.562 PCTime: [0]PPPoE 58563: data path set to Virtual Acess

000135: *Jul 13 18:15:01.562 PCTime: Vi3 PPP: Phase is DOWN, Setup

000136: *Jul 13 18:15:01.566 PCTime: Vi3 PPP: Using dialer call direction

000137: *Jul 13 18:15:01.566 PCTime: Vi3 PPP: Treating connection as a callout

000138: *Jul 13 18:15:01.566 PCTime: Vi3 PPP: Session handle[8A00000C] Session id[0]

000139: *Jul 13 18:15:01.566 PCTime: Vi3 PPP: Phase is ESTABLISHING, Active Open

000140: *Jul 13 18:15:01.566 PCTime: Vi3 PPP: Authorization NOT required

000141: *Jul 13 18:15:01.566 PCTime: Vi3 PPP: No remote authentication for call-out

000142: *Jul 13 18:15:01.566 PCTime: Vi3 LCP: O CONFREQ [Closed] id 1 len 10

000143: *Jul 13 18:15:01.566 PCTime: Vi3 LCP:    MagicNumber 0x259991D2 (0x0506259991D2)

000144: *Jul 13 18:15:01.566 PCTime: %LINK-3-UPDOWN: Interface Virtual-Access3, changed state to up

000145: *Jul 13 18:15:01.578 PCTime: Vi3 LCP: I CONFACK [REQsent] id 1 len 10

000146: *Jul 13 18:15:01.578 PCTime: Vi3 LCP:    MagicNumber 0x259991D2 (0x0506259991D2)

000147: *Jul 13 18:15:03.550 PCTime: Vi3 LCP: Timeout: State ACKrcvd

000148: *Jul 13 18:15:03.550 PCTime: Vi3 LCP: O CONFREQ [ACKrcvd] id 2 len 10

000149: *Jul 13 18:15:03.550 PCTime: Vi3 LCP:    MagicNumber 0x259991D2 (0x0506259991D2)

000150: *Jul 13 18:15:03.558 PCTime: Vi3 LCP: I CONFACK [REQsent] id 2 len 10

000151: *Jul 13 18:15:03.558 PCTime: Vi3 LCP:    MagicNumber 0x259991D2 (0x0506259991D2)

000152: *Jul 13 18:15:03.582 PCTime: Vi3 LCP: I CONFREQ [ACKrcvd] id 2 len 18

000153: *Jul 13 18:15:03.582 PCTime: Vi3 LCP:    MRU 1492 (0x010405D4)

000154: *Jul 13 18:15:03.582 PCTime: Vi3 LCP:    AuthProto PAP (0x0304C023)

000155: *Jul 13 18:15:03.582 PCTime: Vi3 LCP:    MagicNumber 0x5D7E9938 (0x05065D7E9938)

000156: *Jul 13 18:15:03.582 PCTime: Vi3 LCP: O CONFNAK [ACKrcvd] id 2 len 8

000157: *Jul 13 18:15:03.582 PCTime: Vi3 LCP:    MRU 1500 (0x010405DC)

000158: *Jul 13 18:15:03.594 PCTime: Vi3 LCP: I CONFREQ [ACKrcvd] id 3 len 18

000159: *Jul 13 18:15:03.594 PCTime: Vi3 LCP:    MRU 1500 (0x010405DC)

000160: *Jul 13 18:15:03.594 PCTime: Vi3 LCP:    AuthProto PAP (0x0304C023)

000161: *Jul 13 18:15:03.594 PCTime: Vi3 LCP:    MagicNumber 0x5D7E9938 (0x05065D7E9938)

000162: *Jul 13 18:15:03.594 PCTime: Vi3 LCP: O CONFACK [ACKrcvd] id 3 len 18

000163: *Jul 13 18:15:03.594 PCTime: Vi3 LCP:    MRU 1500 (0x010405DC)

000164: *Jul 13 18:15:03.594 PCTime: Vi3 LCP:    AuthProto PAP (0x0304C023)

000165: *Jul 13 18:15:03.594 PCTime: Vi3 LCP:    MagicNumber 0x5D7E9938 (0x05065D7E9938)

000166: *Jul 13 18:15:03.594 PCTime: Vi3 LCP: State is Open

000167: *Jul 13 18:15:03.594 PCTime: Vi3 PPP: Phase is AUTHENTICATING, by the peer

000168: *Jul 13 18:15:03.594 PCTime: Vi3 PAP: Using hostname from interface PAP

000169: *Jul 13 18:15:03.594 PCTime: Vi3 PAP: Using password from interface PAP

000170: *Jul 13 18:15:03.594 PCTime: Vi3 PAP: O AUTH-REQ id 1 len 36 from "user@dsl-isp2.com"

000171: *Jul 13 18:15:03.646 PCTime: Vi3 LCP: I CONFREQ [Open] id 1 len 14

000172: *Jul 13 18:15:03.646 PCTime: Vi3 LCP:    AuthProto PAP (0x0304C023)

000173: *Jul 13 18:15:03.646 PCTime: Vi3 LCP:    MagicNumber 0xE23FB9E9 (0x0506E23FB9E9)

000174: *Jul 13 18:15:03.650 PCTime: Vi3 PPP: Sending Acct Event[Reneg] id[B]

000175: *Jul 13 18:15:03.650 PCTime: Vi3 PPP: Phase is TERMINATING

000176: *Jul 13 18:15:03.650 PCTime: Vi3 PPP: Authorization NOT required

000177: *Jul 13 18:15:03.650 PCTime: Vi3 PPP: No remote authentication for call-out

000178: *Jul 13 18:15:03.650 PCTime: Vi3 PPP: Phase is ESTABLISHING

000179: *Jul 13 18:15:03.650 PCTime: Vi3 LCP: O CONFREQ [Open] id 3 len 10

000180: *Jul 13 18:15:03.650 PCTime: Vi3 LCP:    MagicNumber 0x259999FA (0x0506259999FA)

000181: *Jul 13 18:15:03.650 PCTime: Vi3 LCP: O CONFACK [Open] id 1 len 14

000182: *Jul 13 18:15:03.650 PCTime: Vi3 LCP:    AuthProto PAP (0x0304C023)

000183: *Jul 13 18:15:03.650 PCTime: Vi3 LCP:    MagicNumber 0xE23FB9E9 (0x0506E23FB9E9)

000184: *Jul 13 18:15:03.662 PCTime: Vi3 LCP: I CONFACK [ACKsent] id 3 len 10

000185: *Jul 13 18:15:03.662 PCTime: Vi3 LCP:    MagicNumber 0x259999FA (0x0506259999FA)

000186: *Jul 13 18:15:03.662 PCTime: Vi3 LCP: State is Open

000187: *Jul 13 18:15:03.662 PCTime: Vi3 PPP: Phase is AUTHENTICATING, by the peer

000188: *Jul 13 18:15:03.662 PCTime: Vi3 PAP: Using hostname from interface PAP

000189: *Jul 13 18:15:03.662 PCTime: Vi3 PAP: Using password from interface PAP

000190: *Jul 13 18:15:03.662 PCTime: Vi3 PAP: O AUTH-REQ id 2 len 36 from "user@dsl-isp2.com"

000191: *Jul 13 18:15:04.030 PCTime: Vi3 PAP: I AUTH-ACK id 2 len 5

000192: *Jul 13 18:15:04.030 PCTime: Vi3 PPP: Phase is FORWARDING, Attempting Forward

000193: *Jul 13 18:15:04.030 PCTime: Vi3 PPP: Queue IPCP code[1] id[1]

000194: *Jul 13 18:15:04.046 PCTime: Vi3 PPP SSS: Receive SSS-Mgr Connect-Local

000195: *Jul 13 18:15:04.046 PCTime: Vi3 PPP: Phase is ESTABLISHING, Finish LCP

000196: *Jul 13 18:15:04.046 PCTime: Vi3 PPP: Phase is UP

000197: *Jul 13 18:15:04.046 PCTime: Vi3 IPCP: O CONFREQ [Closed] id 1 len 10

000198: *Jul 13 18:15:04.046 PCTime: Vi3 IPCP:    Address 0.0.0.0 (0x030600000000)

000199: *Jul 13 18:15:04.046 PCTime: Vi3 PPP: Process pending ncp packets

000200: *Jul 13 18:15:04.046 PCTime: Vi3 IPCP: Redirect packet to Vi3

000201: *Jul 13 18:15:04.046 PCTime: Vi3 IPCP: I CONFREQ [REQsent] id 1 len 10

000202: *Jul 13 18:15:04.046 PCTime: Vi3 IPCP:    Address xxx.xxx.255.250 (0x03069BEFFFFA)

000203: *Jul 13 18:15:04.050 PCTime: Vi3 IPCP: O CONFACK [REQsent] id 1 len 10

000204: *Jul 13 18:15:04.050 PCTime: Vi3 IPCP:    Address xxx.xxx.255.250 (0x03069BEFFFFA)

000205: *Jul 13 18:15:04.058 PCTime: Vi3 IPCP: I CONFNAK [ACKsent] id 1 len 10

000206: *Jul 13 18:15:04.058 PCTime: Vi3 IPCP:    Address xxx.xxx.1.2 (0x0306AC1D0102)

000207: *Jul 13 18:15:04.058 PCTime: Vi3 IPCP: O CONFREQ [ACKsent] id 2 len 10

000208: *Jul 13 18:15:04.058 PCTime: Vi3 IPCP:    Address xxx.xxx.1.2 (0x0306AC1D0102)

000209: *Jul 13 18:15:04.070 PCTime: Vi3 IPCP: I CONFACK [ACKsent] id 2 len 10

000210: *Jul 13 18:15:04.070 PCTime: Vi3 IPCP:    Address xxx.xxx.1.2 (0x0306AC1D0102)

000211: *Jul 13 18:15:04.070 PCTime: Vi3 IPCP: State is Open

000212: *Jul 13 18:15:04.070 PCTime: Di2 IPCP: Install negotiated IP interface address xxx.xxx.1.2

000213: *Jul 13 18:15:04.074 PCTime: Di2 IPCP: Install route to xxx.xxx.255.250

000214: *Jul 13 18:15:04.078 PCTime: Vi3 IPCP: Add link info for cef entry xxx.xxx.255.250

000215: *Jul 13 18:15:05.046 PCTime: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to up

Johan,

I have to apologize. During the time, I overlooked that what you are using is PPPoA. Unfortunately, that makes my idea with different usernames useless.

Originally, I thought you are using PPPoE. The PPPoE would allow you to create two distinct sessions over a single PVC and each of these sessions could be forwarded to a different ISP. Unfortunately, with PPPoA, it is not possible. PPPoA simply takes PPP frames, chops them into ATM cells and carries them over the ATM PVC circuit to the aggregation router at the ISP. Because there can be only a single PPP session established over the PVC here, it is not possible to have simultaneous sessions running over the same PVC to two different ISPs. Because the PVC is currently used by the Di0 interface, shutting and activating the Di2 interface did not have any effect because there was no free PVC for Di2. I suspect that if you deactivated Di0 and activated Di2, the Di2 would come up and the Di0 would be unable to come up.

The only options I see now is either to convert to PPPoE - which depends on your DSL service provider - or to really get another PVC.

I apologize for not catching this sooner in the process.

Best regards,

Peter

Hi Peter

No problem, how can I convert my config to PPPoE?

Regards,

Johan Hanekom

Johan,

Please forgive me once again. I am a total idiot. Seeing no output from the "debug pppoe events" and referring to your thread name, I assumed you are running PPPoA.

However, the fact is that you are indeed running a PPPoE (the "pppoe-client dial-pool-member" command under your PVC), and I have blindly missed that as well. I am really getting senile or something...

Let me go over the original article you have referenced once more, and perhaps test something in my lab, but it may take some time. So far, just please accept my apologies for constantly confusing you.

Best regards,

Peter

Hi Johan,

Well, at least I know now exactly what you are trying to accomplish but the funny thing is that I do not know why your router prevents you from doing that. It definitely should, and your original way of configuration was correct.

You are absolutely correctly trying to run a new PPPoE client over the same PVC which should be supported on IOSes 12.4(15)T and newer. However, despite running IOS 12.4(24)T3, your router does not accept running a second PPPoE client on the same PVC. Even more strange, the router complains that the PVC is already in a PPPoA dialer pool which is illogical as you are not running PPPoA.

This may be an IOS bug. Do you have an option of upgrading to either the newest 12.4T or 15.0M IOS? Using a G.SHDSL interface in my lab, I could configure my router to establish two PPPoE sessions over a single ATM PVC exactly as the original document suggested:

interface ATM0/1/0

no ip address

no atm ilmi-keepalive

!

pvc 1/32

  oam-pvc 0

  pppoe-client dial-pool-number 2

  pppoe-client dial-pool-number 1

!

!

interface Dialer1

ip address negotiated

encapsulation ppp

dialer pool 1

!

!

interface Dialer2

ip address negotiated

encapsulation ppp

dialer pool 2

!

Router#show ip int brief

Interface                  IP-Address      OK? Method Status                Protocol

FastEthernet0/0            unassigned      YES unset  administratively down down

FastEthernet0/1            unassigned      YES unset  administratively down down

Serial0/0/0                unassigned      YES unset  administratively down down

Serial0/0/1                unassigned      YES unset  administratively down down

ATM0/1/0                   unassigned      YES unset  up                    up 

Dialer1                    192.0.2.2       YES IPCP   up                    up 

Dialer2                    192.0.2.1       YES IPCP   up                    up 

Virtual-Access1            unassigned      YES unset  up                    up 

Virtual-Access2            unassigned      YES unset  up                    up 

The router is running Cisco IOS Software, 1841 Software (C1841-ADVIPSERVICESK9-M), Version 15.0(1)M3, RELEASE SOFTWARE (fc2).

Besides that, does the show atm pvc ppp produce any interesting output? That should show you PPPoA sessions - if there are any which they should not, according to your configuration.

Best regards,

Peter

Johan,

One more addition. If the Cisco Feature Navigator (http://cisco.com/go/fn) is to be trusted then the multiple PPPoE clients on ATM PVCs on 1841 routers are supported only in the 15.0M and newer IOSes with the Advanced IP Services feature set. That would be congruent with my experiments performed on the 15.0(1)M3.

Best regards,

Peter

Hi Peter

Thanks for the update and the brilliant support, unfortunately the router doesn’t have enough memory to run 15.0M.

I’ll try 12.4 (24) T5 and see if it works, according to the release notes there was a problem in the version I’m running, see below:

http://www.cisco.com/en/US/docs/ios/12_4t/release/notes/124TCAVS.html

CSCtd74943

Symptoms: Multiple PPPoE clients cannot be configured on a single ATM VC.

Conditions: This symptom is observed under all conditions.

Regards,

Johan Hanekom

johanhanekom
Level 1
Level 1

Hi Peter

Just a quick update, I've upgraded to IOS 12.4(24)T5 and this resolve my problem.

interface ATM0/0/0

no ip address

no ip redirects

no ip unreachables

no ip proxy-arp

ip flow ingress

no ip mroute-cache

no atm ilmi-keepalive

pvc 8/35

  oam-pvc 0

  pppoe-client dial-pool-number 3

  pppoe-client dial-pool-number 1

!

!

sh ip int brief

Interface                  IP-Address      OK? Method Status                Protocol

FastEthernet0/0            xxx.xxx.97.1     YES NVRAM  up                    up

FastEthernet0/1            unassigned      YES NVRAM  up                    up

ATM0/0/0                   unassigned      YES NVRAM  up                    up

NVI0                       xxx.xxx.97.1     YES unset  up                    up

Virtual-Access1            unassigned      YES unset  up                    up

Virtual-Access2            unassigned      YES unset  up                    up

Virtual-Access3            unassigned      YES unset  up                    up

Virtual-Access4            unassigned      YES unset  up                    up

Dialer0                    xxx.xxx.86.125   YES IPCP   up                    up

Dialer1                    xxx.xxx.33.208    YES IPCP   up                    up

Dialer2                    xxx.xxx.1.2      YES IPCP   up                    up

Loopback0                  xxx.xxx.6.50     YES NVRAM  up                    up

Thanks again.

Regards,

Johan Hanekom

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco