NPS - Unknown Vendor-ID 311

Question

_{Tuesday, June 26, 2012 10:54 AM}

Hello,

I have a couple of load balancers that authenticate with my NPS servers, however I am getting a syslog message

"httpd: rc_avpair_gen: received VSA attribute with unknown Vendor-Id 311"

In my Network Policy for the devices I have added "Vendor-Specific : RADIUS Standard" under the Vendor Specific settings (as the load balancer docs say).

I've also done a wireshark capture and can see the "AVP: l=12  t=Vendor-Specific(26) v=Microsoft(311)" being sent from the NPS to the device.

Anyone have any ideas how to clear this httpd message?

Thanks,

Peter

All replies (7)

_{Thursday, July 5, 2012 10:21 AM ✅Answered}

Hi,

To find out the cause of the issue, a lot of logs are necessary. I suggest that you can create a case to microsoft for further troubleshooting the issue.

Best Regards

Scott Xie

_{Wednesday, June 27, 2012 7:56 AM}

Hi Peter,

Thank you for the post.

Please open the NPS network policy--Settings--Routing and Remote Access--Multilink and Bandwidth Allocation Protocol, set the value to "Do not allow Multilink connections". Here is a similar thread.
http://social.technet.microsoft.com/Forums/en-CA/winserverNAP/thread/8c2ffe23-7e40-4a19-bb06-a5c76e5006c2

If there are more inquiries on this issue, please feel free to let us know.
 
Regards

Rick Tan

TechNet Community Support

_{Wednesday, June 27, 2012 10:06 AM}

Hi Rick,

After setting this I see the vendor ID has changed to 0... these messages happen every 60 seconds (revalidation interval on the device)

httpd: rc_avpair_gen: received VSA attribute with unknown Vendor-Id 0

Any ideas?

Thanks

_{Thursday, June 28, 2012 10:14 AM}

Hi,

ID 311 means Microsoft. Does the NPS authenticate work sccessfully? It is possible that the load balancer doesn't support the vendor ID 311.

Best Regards

Scott Xie

_{Thursday, June 28, 2012 2:35 PM}

Yea the load balancer authenticates on the correct Policy and works as expected.  Since I turned off the "Multilink and Bandwidth Allocation Protocol" its been returning ID 0 rather than 311

_{Thursday, July 5, 2012 12:40 PM}

Ah ok thanks Scott, hoped it wasnt going to come to that for a message that is only an annoyance more than anything else!

_{Saturday, July 7, 2012 4:56 AM}

Nice weekend Peter,

Yes, if there isn't any business impact, it doesn't worth that. However, it is hard to know the root cause of that message based on the current information. Thanks for understanding.

Best Regard

Scott Xie