PPPoGEC Cisco ASR 1001

[Renzo tovar]

Hi Cisco Professional,

We want to implementing PPPoE over port-channel (using subinterfaces L2) in Cisco ASR 1001 routers, my question is if this router support this feature?, in the other hand i've see  documents about this theme, pls check these links:

http://www.cisco.com/en/US/docs/ios/ios_xe/cether/configuration/guide/ce_lnkbndl_xe.html

http://www.cisco.com/en/US/docs/ios-xml/ios/cether/configuration/xe-3s/ce-ieee-link-bndl-xe.html

My IOS version Cisco ASR 1001 is:

System image file is "bootflash:/asr1001-universalk9.03.04.00.S.151-3.S.bin"

We want this configuration on the router,

no     interface     GigabitEthernet0/0/0.25

interface     port-channel     10.25

description     TURBONETT     PUBLICA     UT

encapsulation     dot1Q     25

ip     address     10.17.44.254     255.255.252.0

!

no     interface     GigabitEthernet0/0/0.52

interface     port-channel     10.52

description     TURBONETT-UT

encapsulation     dot1Q     52

pppoe     enable     group     global

pppoe     max-sessions     4000

!

no     interface     GigabitEthernet0/0/0.61

interface     port-channel     10.61

description     Turbonett-Sector-A

encapsulation     dot1Q     61

pppoe     enable     group     global

pppoe     max-sessions     4000

Kind Regards,

Renzo Tovar

[Manuel Rodriguez · Accepted solution]

Hi Renzo,

PPPoEoVLAN on GEC (LACP mode) is supported as of XE 3.7. I see that you are using XE 3.4 here so I would suggest to move to XE 3.7 and try this feature.

This is a sample configuration for the feature:

interface GigabitEthernet2/1/0

no ip address

negotiation auto

channel-group 2 mode active

!

interface GigabitEthernet3/1/0

no ip address

negotiation auto

channel-group 2 mode active

lacp port-priority 65000

!

interface Port-channel2

no ip address

load-interval 30

no negotiation auto

lacp max-bundle 1

lacp fast-switchover

!

interface Port-channel2.200

encapsulation dot1Q 200

pppoe enable group global

!

interface Port-channel2.500

encapsulation dot1Q 500 second-dot1q 1500

pppoe enable group global

!

As you can see, both PPPoEoVLAN and  PPPoEoQinQ are supported.

Hope this helps.

Best regards.

[Renzo tovar]

Hi Manuel,

I've had a huge question?, if Cisco documents tell us that this feature PPPoE on GEC is supported in XE 3.7, why this is working in cisco XE 3.4.

Please could you clarify this theme?, OK if exists error on cisco's documents vulnerabilities might occur if you use this feature on XE3.4?

sh ver | i image file

System image file is "bootflash:/asr1001-universalk9.03.04.00.S.151-3.S.bin"

sh pppoe summary per subinterface

PTA  : Locally terminated sessions

FWDED: Forwarded sessions

TRANS: All other sessions (in transient state)

TOTAL     PTA   FWDED   TRANS

TOTAL                            2653    2653       0       0

Port-channel10.63                2041    2041       0       0

Port-channel10.146                204     204       0       0

Port-channel10.152                 84      84       0       0

Port-channel10.269                 33      33       0       0

Port-channel10.1402               291     291       0       0

sh run int port-channel 10.63

Building configuration...

Current configuration : 105 bytes

!

interface Port-channel10.63

description PPPoE

encapsulation dot1Q 63

pppoe enable group global

end

CMT-CSC001001-A1#

#sh int port-channel 10.63

Port-channel10.63 is up, line protocol is up

Hardware is GEChannel, address is 5057.a883.6dc9 (bia 5057.a883.6dc9)

Description: PPPoE

MTU 1500 bytes, BW 2000000 Kbit/sec, DLY 10 usec,

reliability 255/255, txload 25/255, rxload 3/255

Encapsulation 802.1Q Virtual LAN, Vlan ID  63.

ARP type: ARPA, ARP Timeout 04:00:00

Keepalive set (10 sec)

Last clearing of "show interface" counters never

Regards,

Renzo Tovar

[Manuel Rodriguez]

Hi Renzo,

The features are tipically are added progresivelly in the code. This means that, once the developers start working on a feature in a platform, they start adding code in the SW releases. However, the features is are only officially supported as of the release the Business Units state (normally on documentation). At that point, they consider the feature includes all the requirements needed for it to be used by customers and the feature has been tested by them. This is why probably it works in your case with a previous relaease than the one is stated in the documents as supported. However, if you try to use the feature on an unsupported release, and you face any issue with it, you will not get support from TAC nor the developers since the feature is being used in a release where it is not supported.

I hope this clarifies your questions.

Best regards.