OPERATIONAL DEFECT DATABASE
...
...
radius-server attribute 31 mac format unformatted radius-server attribute 32 include-in-access-req radius-server attribute 32 include-in-access-req format %h.%d radius-server attribute 32 include-in-accounting-req radius-server attribute 32 include-in-accounting-req format %h.%d The switch config doesnt show %h.%d but that is because it should send FQDN by default. Using the radius-server attribute 32 include-in-access-req command makes it possible to identify the network access server (NAS) manufacturer to the RADIUS server by sending RADIUS attribute 32 (NAS-Identifier) in an access-request or accounting-request. If you configure the format argument, the string sent in attribute 32 will include an IP address, a hostname, or a domain name; otherwise, the Fully Qualified Domain Name (FQDN) is sent by default. I tried with string "cisco' radius-server attribute 32 include-in-accounting-req format cisco %h.%d, but still no luck. 2019/01/16 23:18:21.909 {smd_R0-0}{1}: [radius] [24179]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS(00000000): Sending a IPv4 Radius Packet(retransmit) 2019/01/16 23:18:21.909 {smd_R0-0}{1}: [radius] [24179]: UUID: 0, ra: 0, TID: 0 (info): RADIUS: Event-Timestamp [55] 6 1 2019/01/16 23:18:21.909 {smd_R0-0}{1}: [radius] [24179]: UUID: 0, ra: 0, TID: 0 (info): RADIUS: Nas-Identifier [32] 22 "cisco switch-lab-ks." 2019/01/16 23:18:21.909 {smd_R0-0}{1}: [radius] [24179]: UUID: 0, ra: 0, TID: 0 (info): RADIUS: NAS-IP-Address [4] 6 10.106.56.158 2019/01/16 23:18:21.909 {smd_R0-0}{1}: [radius] [24179]: UUID: 0, ra: 0, TID: 0 (info): RADIUS: Service-Type [6] 6 Unsupported [16777216] 2019/01/16 23:18:21.909 {smd_R0-0}{1}: [radius] [24179]: UUID: 0, ra: 0, TID: 0 (info): RADIUS: User-Name [1] 14 "nac-rad-test" Same with accouting.
radius-server attribute 31 mac format unformatted radius-server attribute 32 include-in-access-req radius-server attribute 32 include-in-access-req format %h.%d radius-server attribute 32 include-in-accounting-req radius-server attribute 32 include-in-accounting-req format %h.%d The switch config doesnt show %h.%d but that is because it should send FQDN by default. Using the radius-server attribute 32 include-in-access-req command makes it possible to identify the network access server (NAS) manufacturer to the RADIUS server by sending RADIUS attribute 32 (NAS-Identifier) in an access-request or accounting-request. If you configure the format argument, the string sent in attribute 32 will include an IP address, a hostname, or a domain name; otherwise, the Fully Qualified Domain Name (FQDN) is sent by default. I tried with string "cisco' radius-server attribute 32 include-in-accounting-req format cisco %h.%d, but still no luck. 2019/01/16 23:18:21.909 {smd_R0-0}{1}: [radius] [24179]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS(00000000): Sending a IPv4 Radius Packet(retransmit) 2019/01/16 23:18:21.909 {smd_R0-0}{1}: [radius] [24179]: UUID: 0, ra: 0, TID: 0 (info): RADIUS: Event-Timestamp [55] 6 1 2019/01/16 23:18:21.909 {smd_R0-0}{1}: [radius] [24179]: UUID: 0, ra: 0, TID: 0 (info): RADIUS: Nas-Identifier [32] 22 "cisco switch-lab-ks." 2019/01/16 23:18:21.909 {smd_R0-0}{1}: [radius] [24179]: UUID: 0, ra: 0, TID: 0 (info): RADIUS: NAS-IP-Address [4] 6 10.106.56.158 2019/01/16 23:18:21.909 {smd_R0-0}{1}: [radius] [24179]: UUID: 0, ra: 0, TID: 0 (info): RADIUS: Service-Type [6] 6 Unsupported [16777216] 2019/01/16 23:18:21.909 {smd_R0-0}{1}: [radius] [24179]: UUID: 0, ra: 0, TID: 0 (info): RADIUS: User-Name [1] 14 "nac-rad-test" Same with accouting.
None.
The result is same with or without ?format %h.%d? which is that it is only sending the hostname of switch in attribute 32 for accounting. I will need to see if we can find any known issue in internal DB, else we might have to check with development. radius-server attribute 6 on-for-login-auth radius-server attribute 32 include-in-access-req radius-server attribute 32 include-in-accounting-req format cisco %h.%d radius-server attribute 31 mac format unformatted radius-server dead-criteria time 5 tries 3 radius-server deadtime 1 switch-lab-ks#show platform software trace message smd switch active R0 ........................... 2019/01/15 20:45:39.720 [tdllib] [7418]: UUID: 0, ra: 0, TID: 0 (note): NOT need to update epoch /tmp/tdlresolve/epoch_dir//2019_01_15_19_09_1643.epoch --- DECODE 9641:9641:69 DONE --- 2019/01/15 20:45:39.720 [tdllib] [7418]: UUID: 0, ra: 0, TID: 0 (note): NOT need to update epoch /tmp/tdlresolve/epoch_dir//2019_01_15_19_09_1643.epoch 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS(00000000): Started 5 sec timeout 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Event-Timestamp [55] 6 1547585125 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Acct-Status-Type [40] 6 Start [1] 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Acct-Authentic [45] 6 Remote [3] 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Acct-Session-Id [44] 10 "00000009" 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: NAS-Port [5] 6 50153 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: NAS-Port-Type [61] 6 Ethernet [15] 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: NAS-Port-Id [87] 25 "TenGigabitEthernet1/1/1" 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Nas-Identifier [32] 15 "switch-lab-ks" 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: NAS-IP-Address [4] 6 10.106.56.158 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Calling-Station-Id [31] 19 "A0-36-9F-E2-85-71" 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Called-Station-Id [30] 19 "0C-D0-F8-D8-9E-B5" 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Cisco AVpair [1] 12 "method=mab" 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Vendor, Cisco [26] 18 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Cisco AVpair [1] 43 "audit-session-id=9E386A0A0000002153426028" 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Vendor, Cisco [26] 49 2019/01/15 20:45:35.484 [radius] [7418]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Acct-Delay-Time [41] 6 5 RADIUS: authenticator 9a 40 c2 72 de 9f 27 8c - af 15 ae 2e e5 8f 19 81 radius-server attribute 44 include-in-access-req default-vrf radius-server attribute 6 on-for-login-auth radius-server attribute 32 include-in-access-req radius-server attribute 32 include-in-accounting-req format cisco %h.%d radius-server attribute 31 mac format unformatted radius-server dead-criteria time 5 tries 3 radius-server deadtime 1 radius-server key cisco radius server nac-radius-server-1 Even in access-request it doesn't show it is sending the correct format but this is automater test user. 2019/01/15 21:29:37.837 [radius] [7386]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS(00000000): Started a sec timeout 2019/01/15 21:29:37.837 [aaa-author] [7386]: UUID: 0, ra: 0, TID: 0 (debug): VALID SG handle 2019/01/15 21:29:37.837 [radius] [7386]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Nas-Identifier [32] 15 "switch-lab-ks" 2019/01/15 21:29:37.837 [radius] [7386]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: NAS-IP-Address [4] 6 10.106.56.158 2019/01/15 21:29:37.837 [radius] [7386]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Service-Type [6] 6 Unsupported [16777216] 2019/01/15 21:29:37.837 [radius] [7386]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: User-Name [1] 14 "nac-rad-test" 2019/01/15 21:29:37.837 [radius] [7386]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: User-Password [2] 18 * 2019/01/15 21:29:37.837 [radius] [7386]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Acct-Delay-Time [41] 6 20 RADIUS: authenticator 0d d2 ae 7c 13 1d df a2 - d6 a9 1c 8c 3f f3 98 03 2019/01/15 21:29:37.837 [radius] [7386]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS: Retransmit to (172.18.124.135:1812,1813) for id 1812/11 2019/01/15 21:29:37.837 [radius] [7386]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS(00000000): Request timed out! 2019/01/15 21:29:34.809 [radius] [7386]: UUID: 0, ra: 0, TID: 0 (debug): RADIUS(00000000): Started The only difference i see is cisco string getting added when i used it in access-request but not in accounting. This happens on 16.6.2, 16.6.3 and 16.9.2
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
