This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC! We will not comment or assist with your TAC case in these forums.
Please see How to Ask the Community for Help for other best practices.
I wanted to provide some feedback after a TAC case of mine revealed a deeper understanding of how the ISE Sponsor Portal health check works. I am referring to the brilliant BRKSEC-3699 which gives us examples of how to do it.
When I initially used this in my ISE 2.2 deployment I followed the ISE 1.3 Example verbatim in my F5 LTM and all was working well. And then one day I modified my Sponsor Portal and then it broke the health check. Here is why ... it's obvious now, in retrospect, but I didn't realise that the GET string example above was referring to the Portal Name. The BRKSEC example works well as long as you don't customise the Portal Name.
Solved! Go to Solution.