ASR9K PPPoE ERROR - bad session data

Vladimir Miropolskyj · ‎02-12-2015

In a month the second case all are disconnected Rrroyesessii and new aren't connected not to reboot a router yet.

Messages

RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: Bundle-Ether100.10: I dst ffff.ffff.ffff src bcee.7bed.90a0: len 46 0x11090000000c01010000010300040001000000000000000000000000000000000000000000000000000000000000
RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]: Bundle-Ether100.10 peer-mac bcee.7bed.90a0
RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]: vlan-id-outer 600
RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]: Service-name:
RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]: Host-uniq: 00010000
RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: Bundle-Ether100.10: O dst bcee.7bed.90a0 src e4c7.227c.ea0b: len 31 0x11070000001901010000010300040001000001020009415352394b2d424e47
RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADO-Sent]: Bundle-Ether100.10 peer-mac bcee.7bed.90a0
RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADO-Sent]: vlan-id-outer 600
RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: Bundle-Ether100.10: I dst ffff.ffff.ffff src 0860.6e24.0390: len 46 0x11090000000c01010000010300040001000000000000000000000000000000000000000000000000000000000000
RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]: Bundle-Ether100.10 peer-mac 0860.6e24.0390
RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]: vlan-id-outer 88
RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]: Service-name:
RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: Bundle-Ether100.10: O dst 5404.a68e.2160 src e4c7.227c.ea0b: len 31 0x11070000001901010000010300040001000001020009415352394b2d424e47
RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADO-Sent]: Bundle-Ether100.10 peer-mac 5404.a68e.2160
RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADO-Sent]: vlan-id-outer 210
RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: Bundle-Ether100.10: I dst ffff.ffff.ffff src 5404.a6e6.81d4: len 46 0x11090000000c01010000010300040001000000000000000000000000000000000000000000000000000000000000
RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADI-Recv]: Bundle-Ether100.10 peer-mac 5404.a6e6.81d4
RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADI-Recv]: vlan-id-outer 32
RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADI-Recv]: Service-name:
RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADI-Recv]: Host-uniq: 00010000
RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: Bundle-Ether100.10: O dst 5404.a6e6.81d4 src e4c7.227c.ea0b: len 31 0x11070000001901010000010300040001000001020009415352394b2d424e47
RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADO-Sent]: Bundle-Ether100.10 peer-mac 5404.a6e6.81d4
RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: Bundle-Ether100.10: I dst ffff.ffff.ffff src 60a4.4c8c.8ddc: len 46 0x11090000000c01010000010300040001000000000000000000000000000000000000000000000000000000000000
RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: [PADI-Recv]: Bundle-Ether100.10 peer-mac 60a4.4c8c.8ddc
RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: [PADI-Recv]: vlan-id-outer 60
RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: [PADI-Recv]: Service-name:
RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: [PADI-Recv]: Host-uniq: 00010000
RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: [PADI-Recv]: ERROR - bad session data
RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: Bundle-Ether100.10: O dst 60a4.4c8c.8ddc src e4c7.227c.ea0b: len 31 0x11070000001901010000010300040001000001020009415352394b2d424e47

ASR9001

ROM: System Bootstrap, Version 2.04(20140227:092320) [ASR9K ROMMON]

How to fight against it? before such it wasn't noticed

xthuijs · ‎02-17-2015

hi vladimir,

I checked the source code when this error is set. this is seen when a session stage packet is received that has no valid idb (aka subscriber interface) for the session ID that was found in the packet together with the vlan tags.

Now this is a PADI, so it is not a session packet to start with.

Next I see that the function that sets this error is only called for on data packets when the opcode is 0x00 in your case the opcode is 0x09 which is a PADI.

what I am thinking that is happening here is that the punt software has provided incorrect pointers to the start of the packet due to a sw bug.

I would like to request if you can evaluate xr513 for this as I see some fixes in 512/513 relating to the punt handling sw that might be of benefit here.

regards

xander

Vladimir Miropolskyj · ‎02-19-2015

Thanks Alexander,

the other day I will update on 5.1.3,

then I will write about results.