10-18-2024 12:34 PM
CSCwh73915 - Static IP Assignment not working using attribute msRADIUSFramedIPAddress when posture is enabled.
Solution:
We can assign static IP, if we use parameter radius ip address= msRADIUSFramedIPAddress in Posture unknown authorization profile.
Then there is no need to assign the radius ip address parameter in COA Authorization .
I have tested and its working fine.
1. posture unknown authz profile have parameter radius ip address= msRADIUSFramedIPAddress. --> Will have same static IP for that user
2.once its complaince , COA , authz profile - required applied.
10-21-2024 10:53 AM
What exactly is your question?
https://community.cisco.com/t5/security-documents/how-to-ask-the-community-for-help/ta-p/3704356
04-02-2026 06:26 PM
Hi @kothare ,
Thank you, thank you, thank you! Your workaround fixed the issue for me. That makes so much sense! The IP address is assigned with the 1st authorization profile from ISE, not the 2nd.
For those that do not understand, the bug CSCwh73915 does NOT have a workaround listed. @kothare was kind enough to post a solution. Thank you!
I had the IP address attribute specified in the posture compliant authorization profile, the 2nd one used. Once I moved it to the posture redirect authorization profile, the 1st one used, it works!
Thank you again!
Tom
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