UNSOLVED
filesys option command
Hi there ...
Is anybody had used and successfully recieved mail alert with
``filesys optoin set warning-space-usage ``
``filesys option set critical-space-usage``
command ?
I know this should be issued SE@ Mode ( reset can be done as Admin mode ) to set .
But not sure this setting bring both alerts to be sent ( warrning and Critical ) when hits critical level of % ?
thanks !
richbinstead
62 Posts
801
0
Posted July 13th, 2016 03:00
Hi Aya,
Our engineering team have confirmed this isn't working as expected and is a bug. I'm waiting for further confirmation as to the release that this fixed is planned for.
cheers, Rich.
richbinstead
62 Posts
801
0
Posted July 20th, 2016 06:00
Hi Aya,
Just a quick update to let you know I've not forgotten about this -- it's pending an update from engineering who I'll be chasing later this week.
cheers, Rich.
richbinstead
62 Posts
801
0
Posted July 28th, 2016 01:00
Hi Aya,
Engineering are estimating a fix to be included in DDOS 6.1 for this as it's a low priority issue.
cheers, Rich.
richbinstead
62 Posts
801
0
Posted July 7th, 2016 05:00
Hi ayas,
Both the options, warning-space-usage and critical-space-usage, should be able to be set as the default sysadmin user, but as you appear to have found don't set correctly unless you are in SE mode. This I believe is a bug which I'll be raising with our engineering team shortly.
For example:
=================================================
sysadmin@dd4200# filesys option show warning-space-usage
warning-space-usage percentage is: 50
sysadmin@dd4200# filesys option set warning-space-usage 60
sysadmin@dd4200# filesys option show warning-space-usage
warning-space-usage percentage is: 50
=================================================
The recommendation is to set the critical-space-usage percentage higher than the warning-space-usage percentage.
However once the thresholds are exceeded you should find an alert of type WARNING for the warning-space-usage and a CRITICAL alert for the critical-space-usage. These should be no different to a normal alert, so once they are triggered an email/SNMP trap etc should be sent, depending upon your configuration. You should also see the alerts in the 'alerts show current' command once they are triggered. However I've yet to test this fully yet, so it could be that the bug I mention above is causing them to not be generated correctly.
I will update you once I have feedback from our engineering team.
cheers, Rich.