09-16-2013 04:01 AM
friends,
When i am trying to connect PPPoE Sessions through ASR 9010 running XR 4.3.1 , I see BRAS is sending many attributes as unsupported. Even standard attributes like Framed-Protocol & Service-Type are shown as unsupported.
Can someone tell me the reason for it?? and how it can be fixed??
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: Picking the rad id 196:0 sockfd 0x1001AC90
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: Send Access-Request to 192.168.1.100:1812 id 196, len 290
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: rctx 0x1012e90c added successfully
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: authenticator D4 1E 46 55 80 C2 4C BE - 42 38 1B 77 C1 9E 01 DC
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: Vendor-Specific [26] 27
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: Vendor-Specific [26] 41
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: Acct-Session-Id [44] 10 00000074
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: NAS-Port-Id [87] 11 0/0/1/264
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: Vendor-Specific [26] 17
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: User-Name [1] 13 test123
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: Service-Type [6] 6 Unsupported[33554432]
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: User-Password [2] 18 *
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: Unsuppoted attribute.
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: Vendor-Specific [26] 33
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: Vendor-Specific [26] 34
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: NAS-Port-Type [61] 6 Unsupported[603979776]
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: Framed-Protocol [7] 6 Unsupported[16777216]
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: Called-Station-Id [30] 16 782b.cbd6.ac41
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: Event-Timestamp [55] 6 81606226
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: Nas-Identifier [32] 14 ASR-9010-BNG
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: Got global deadtime 0
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: RADIUS: NAS-IP-Address [4] 6 192.168.254.100
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: Using global deadtime = 0 sec
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: Start timer thread rad_ident 196 remote_port 1812 remote_addr 0x4ef21d7c, socket 268545168 rctx 0x1012e90c
RP/0/RSP0/CPU0:Sep 16 15:27:16.303 : radiusd[1114]: Successfully sent packet and started timeout handler for rctx 0x1012e90c
RP/0/RSP0/CPU0:Sep 16 15:27:16.328 : radiusd[1114]: rctx found is 0x1012e90c
RP/0/RSP0/CPU0:Sep 16 15:27:16.328 : radiusd[1114]: Radius packet decryption complete with rc = 0
RP/0/RSP0/CPU0:Sep 16 15:27:16.328 : radiusd[1114]: RADIUS: Received from id 196 192.168.1.100:1812, Access-Accept, len 38
RP/0/RSP0/CPU0:Sep 16 15:27:16.328 : radiusd[1114]: RADIUS: authenticator 4D 3C 8B F9 8D 54 07 52 - 47 E6 D6 09 D4 50 FF 6E
RP/0/RSP0/CPU0:Sep 16 15:27:16.328 : radiusd[1114]: RADIUS: Service-Type [6] 6 Unsupported[33554432]
RP/0/RSP0/CPU0:Sep 16 15:27:16.328 : radiusd[1114]: Unsuppoted attribute.
RP/0/RSP0/CPU0:Sep 16 15:27:16.328 : radiusd[1114]: RADIUS: Framed-Protocol [7] 6 Unsupported[16777216]
RP/0/RSP0/CPU0:Sep 16 15:27:16.328 : radiusd[1114]: Freeing server group transaction_id (8600005D)
09-17-2013 02:12 PM
Don't worry about that, that is just the internal decoding of the attribute and enum.
there is nothing to be fixed if the radius packet is properly recieved by the radius server and based on what I see here the attribute is packed correctly, just not printed in human readable format easily, which is just a debugggin thing.
xander
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide