M and MSM Series
cancel
Showing results for 
Search instead for 
Did you mean: 

MSM760 Log Help

 
PaulC1
Occasional Visitor

MSM760 Log Help

We have had various issues with our wifi which is an msm760 with approximately 150 AP's, (HP560, MSM460 primarily)

We an SSID with Radius enabled but sometimes users just cannot connect or if they are connected they sometimes get kicked off and then struggle to reconnect.  The signal stregth is good in all areas.

I looked at the logs from the MSM760 and there are an awful lot of entries (1000's) as below at a rate of 10+ a second.

The ip/id/port are different for each entry.

Discarding RADIUS Accounting Request (id='36') from RADIUS Client (ip-address='169.254.0.60',port='32880') because of missing username. (Check your RADIUS Secret configuration.)

 

Does anybody know what may be causing the issue.

Thanks in advance if anybody can offer any assistance.

 

15 REPLIES 15
RamKrish
Valued Contributor

Re: MSM760 Log Help

Whole log might help to see what other relevant logs along with this accounting messages.

Who is the Radius server?  (Microsoft NPS ? or other?)

Do you really need to use Accounting? is Radius accounting configured properly?

May be a wired trace on your radius server might help to see what kind of radius replies going to the controller.

Do you have a screen snap of your VSC settings?

Regards
Ram
hpehh
Occasional Visitor

Re: MSM760 Log Help

Hello PaulC1,

 

do you found a solution for this problem? I get the same type of error every 5 sec. on the MSM760. It happened after an update on firmware 6.6.2.0-22792. We don't use RADIUS Accounting but authenticate through RADIUS against OpenLDAP.

 

Thank you! 

Transport
Advisor

Re: MSM760 Log Help

The error suggest the wrong key used between wireless controller and radius-server.
When the the controller can't authenticate against the radius, it can't see if the username excists or not. Hence the error about the username.

Please check is the keys are correct on your controller AND radius server


See screenshots attached.

Highlighted
richlo
Occasional Visitor

Re: MSM760 Log Help

I have a customer with the same error under 6.6.2:

iprulesmgr: Discarding RADIUS Accounting Request (id='99') from RADIUS Client (ip-address='169.254.0.59',port='34006') because of missing username. (Check your RADIUS Secret configuration.)

Was setting the correct key between the radius server and the controller the answer?

Thanks,

RO

 

OX-ITS
Occasional Visitor

Re: MSM760 Log Help

We're having the same problem, also 6.6.2. Setting the "correct" key isn't the awnser in our case.

To make it more fun, the Radius accounting to our Windows NPS/Radius server is working perfectly, even though we get these messages. We don't have any other Radius connections to/from the MSM controller.

When rebooting the messages dissapear for a few minutes, but sadly return if they never have left.

We're lacking the know-how to find what (or who) is causing these messages, looking at one of the many logs doesn't reveal us much.

Teufel Martin
Occasional Advisor

Re: MSM760 Log Help

We are haveing the same in out Logfiles:

iprulesmgr: Discarding RADIUS Accounting Request (id='218') from RADIUS Client (ip-address='169.254.0.50',port='36226') because of missing username. (Check your RADIUS Secret configuration.)

 

Has anyone a solution or some info on that issue?

KindRegards

Martin

CraigS1971
Valued Contributor

Re: MSM760 Log Help

Hi Paul and Martin,

Run your radius server in debug mode and write the output to a file.
Check that the username and password are reaching the radius server correctly.

The command may look like this depending on the OS and radius server:
/usr/sbin/radiusd -d /usr/local/pf/raddb/ -X -xx | tee radius_debug.log

Search for something like this: (rdomingo + P@ssw0rd)

Thu Feb 25 08:19:05 2016 : Info: performing user authorization for rdomingo
Thu Feb 25 08:19:05 2016 : Info:  <------>expand: (uid=%{User-Name}) -> (uid=rdomingo)
Thu Feb 25 08:19:05 2016 : Info:  <------>expand: o=csir -> o=csir
Thu Feb 25 08:19:05 2016 : Debug:   ldap_get_conn: Checking Id: 0
Thu Feb 25 08:19:05 2016 : Debug:   ldap_get_conn: Got Id: 0
Thu Feb 25 08:19:05 2016 : Debug:   performing search in o=csir, with filter (uid=rdomingo)
Thu Feb 25 08:19:05 2016 : Info: Added the eDirectory password P@ssw0rd in check items as Cleartext-Password

 

You can also search for messages regarding incorrect authentication from clients ie MSM controller ip address.

Regards,

Craig.

Teufel Martin
Occasional Advisor

Re: MSM760 Log Help

Hi Craig!

 

Thanks for your Reply.

I looked into the radiusserver Logs, but didn't help me. I didn't find there any specifc Radius Audit Requests.

One interesting thing is the originating IP adress of the failed Radius-Requests. These are all 169.254.x.x adresses. Why does the MSM have/use them?? We are running a Teaming Setup with two MSMs and the faild Radiusrequests are only reported on one of the systems. The MSMs are on the Same Subnet.

Kind Regards

Martin

CraigS1971
Valued Contributor

Re: MSM760 Log Help

Hi Martin,

The APIPA addresses (169.254.x) are normally a DHCP problem.

Do you use DHCP for your APs or controllers?

Check that your controllers have valid static ip address and also check the AP ip addresses.

Regards,

Craig.