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 am starting to see on a few of my ISE 2.3 customers that the reports are being limited to 500 lines both in the report in ISE and on the local CSV export. The repository export works just fine. I have other 2.3 customers that can do up to 5000 lines which is what the reports should be limited to.
Any thoughts on why this is showing up?
Solved! Go to Solution.
The only known issue I am aware is CSCvh32034 but it specific to active sessions report and repository exports also have the issue.
We would need more info, such as which report(s) and check DEBUG log files, etc. Good to engage Cisco TAC.
That bug is not visible to me. I am seeing this in the RADIUS authentication report not the Current Active Sessions report. I will open a TAC case on it.
Paul Haferman
Office- 920.996.3011
Cell- 920.284.9250
I did open a TAC case on this, 683910973. TAC is telling me the bug is only going to be fixed in 2.4. I am not sure if this is even this right bug as this is affecting all reports.
Let's take it offline and follow it up with TAC directly.
Has there been any updates/fixes on this? I am currently running in to the same issue on ISE 2.3 patch 2.
It turns out the local CSV export in recent ISE releases is now limited to 500 due to performance concerns. Please export to a repository for any results > 500 entries.
Just curios, performance concerns for what? 500 line lines is mostly useless.
Sent from my iPhone
I think it's along the line that ISE app server needs to buffer the query result sets into memory for local CSV exports.
I'm not sure I like this decision, especially with the introduction of the larger Nodes like the Super MnT. A warning is fine but give me the option of slowing down my MnT/PAN to run some reports.
What a stupid design. Is there any possibility to improve this function in the future release?