Vendor Specific Attributes for IAS - What Needs to be Done?
Can somebody explain the necessary VSA attributes for configuring standard PEAP authentication against a Windows 2003 IAS RADIUS server? Is this a requirement to do so? If so, what is the syntax and procedure for doing so?
Re: Vendor Specific Attributes for IAS - What Needs to be Done?
If you are simply going to authenticate dial-in users, based on their username/password, via Radius, then this will be possible using standard IETF attributes that both Cisco IOS as well as Microsoft's IAS support without additional configuration.If you want to use any vendor-specific functionality, then you can go for VSAs.
Examples for vendor-specific functionality where extra configuration on IAS is needed would be per-user attributes such as per-user static routes or per-user access lists, as these are implemented using Cisco VSA's. Similary, Microsoft VSA's need to be used if Microsoft proprietary functions, such as MPPE, are to be used. This document might be of use for you:
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...