- #Cisco ise 2.4 high disk space utilization bug upgrade
- #Cisco ise 2.4 high disk space utilization bug full
- #Cisco ise 2.4 high disk space utilization bug free
In my case the logs take up 8GB of uncompressed space - if I remove the logs, then I am left with 149MB of uncompressed data.
Sadly (and weirdly) the logs are in there. If you run the du -k command over the resultant directory called 'backup' contained in the tar bundle, you will get a nice summary of the type of data that is backed up. gpg -d mybackup.gpg > mybackup.tarĪnd then untar the bundle with tar -xvf mybackup.tar I copied my latest 410MB backup to a Linux server and unencrypted the file with gpg. You can easily analyse what's inside an ISE backup file.
#Cisco ise 2.4 high disk space utilization bug free
sys/fs/cgroup : 0% used ( 0 of 32905156)Īll internal filesystems have sufficient free spaceĪs far as the SNMP trap config in ADE-OS is concerned, below is the line of config that alerts when 80% space is used (i.e.
#Cisco ise 2.4 high disk space utilization bug full
I understand Cisco's stance on controlling access to the full CLI, but without controls built into the product to report on these (CLI or GUI), it makes administration and understanding the system when testing upgrades feel like I am flying blind.īelow is the show disk of the MnT that was shown previously in GUI format.ĭisk repository: 5% used (1420416 of 30106488) Ultimately what is required is an accurate measure of how disk is used between radius logs, tacacs logs, system logs, local logs, and anything else which consumes space (operating system, temp files, dump files, etc). It's feasible that compression could get the backup-logs down to a very small size, but without a working restore of the backup-logs its impossible to tell. In our environment the config backup is 762mb, operational is 23.5gb, and backup-logs is 730mb.
#Cisco ise 2.4 high disk space utilization bug upgrade
I think your comment about local and system logs not being part of the config/operational backups is where I struggle the most to understand the ISE backups and are in reality the probable reason for the disk utilisation discrepancy.Īt a high level, I am still in a pickle with regards to the disk utilisation, testing the 2.1 -> 2.2 upgrade process, and issues with the backup-logs not restoring (error about 'invalid backup file version'). Ironically, I think that the operational backup and backup-logs files should be much larger.Ĭhyps: We have the operational data set to purge after 90 days, but your comments about issues with retention of excessive transaction data are interesting - I will keep a close eye on this. I also have similar concerns about config backups being large (ours are ~700mb), but they work so I am relucant to question it.
Maybe thats a reason to push ahead to 2.3! Could you check the output from show disk for me so that I can compare what it reports compared to the GUI? Thanks for the replies, I appreciate your time.Īrne: Unfortunately we are running ISE 2.1 (reasonably solid and reliable), so dont get the database utilisation currently. I don't make operational backups - this is where I would expect logs to be kept. I don't have more than 200 endpoints in my DB either. That worries me because that is supposed to be a config backup (what is it backing up? No way that I have been configuring 400MB worth of stuff). When I do a config backup in my prod system it keeps growing and it's currently 400MB. If you search this forum you will find a discussion I wrote on this topic. You cannot trap at a volume/mount point level - it applies to entire disk. 20% free) - I have tested this and it seems to work. There is an SNMP trap that I have also set to alert if the entire disk system usage is above 80% (i.e. If you want to monitor the disk usage on each node then use the show disk command. I could probably stretch my retention period to 1 year at this level of low activity. The other one on the left that I highlighted in red appears to represent 13GB worth of radius logs so far. I think the right-most, thin blue bar represents the TACACS usage (but trying to hover over that is tricky - I think I was hovering over it but it didn't say it was for TACACS). You can decide how many days' worth of Radius and TACACS logs you want to keep I don't fully grasp it either but ISE 2.3 does try to display the disk usage of the MnT nodes at least.
0 kommentar(er)
