Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerScaleOneFS CLI Command Reference

isi quota settings notifications create

Creates a default notification rule.

Syntax

isi quota settings notifications create
  --threshold {hard | soft | advisory}
  --condition {exceeded | denied | violated | expired}
  --schedule <string>
  --holdoff <duration>
  [--action-alert {yes | no}]
  [--action-email-owner {yes | no}]
  [--action-email-address<address>]
  [--email-template <path>]
  [--verbose]

Options

--threshold
Specifies the threshold type. The following values are valid:
hard
Sets an absolute limit for disk usage. Attempts to write to disk are generally denied if the request violates the quota limit.
soft
Specifies the soft threshold. Allows writes to disk above the threshold until the soft grace period expires. Attempts to write to disk are denied thereafter.
advisory
Sets the advisory threshold. For notification purposes only. Does not enforce limitations on disk write requests.
--condition
Specifies the quota condition on which to send a notification. The following values are valid:
denied
Specifies a notification when a hard threshold or soft threshold outside of its soft grace period causes a disk write operation to be denied.
exceeded
Specifies a notification when disk usage exceeds the threshold. Applies to only soft thresholds within the soft-grace period.
violated
Specifies a notification when disk usage exceeds a quota threshold but none of the other conditions apply.
expired
Specifies a notification when disk usage exceeds the soft threshold and the soft-grace period has expired.
--schedule <string>
Specifies the date pattern at which recurring notifications are made.

Specify in the following format:

"<interval> [<frequency>]"

Specify <interval> in one of the following formats:

  • Every [{other | <integer>}] {weekday | day}
  • Every [{other | <integer>}] week [on <day>]
  • Every [{other | <integer>}] month [on the <integer>]
  • Every [<day>[, ...] [of every  [{other | <integer>}] week]]
  • The last {day | weekday | <day>} of every [{other | <integer>}] month
  • The <integer> {weekday | <day>} of every [{other | <integer>}] month
  • Yearly on <month> <integer>
  • Yearly on the {last | <integer>} [weekday | <day>] of <month>

Specify <frequency> in one of the following formats:

  • at <hh>[:<mm>] [{AM | PM}]
  • every [<integer>] {hours | minutes} [between <hh>[:<mm>] [{AM | PM}] and <hh>[:<mm>] [{AM | PM}]]
  • every [<integer>] {hours | minutes} [from <hh>[:<mm>] [{AM | PM}] to <hh>[:<mm>] [{AM | PM}]]

You can optionally append "st", "th", or "rd" to <integer>. For example, you can specify "Every 1st month"

Specify <day> as any day of the week or a three-letter abbreviation for the day. For example, both "saturday" and "sat" are valid.

--holdoff <duration>
Specifies the length of time to wait before generating a notification.

Specify <duration> in the following format:

<integer> <units>

The following <units> are valid:

Y
Specifies years
M
Specifies months
W
Specifies weeks
D
Specifies days
H
Specifies hours
s
Specifies seconds
--action-alert {yes | no}
Generates an alert when the notification condition is met.
--action-email-owner {yes | no}
Specifies that an email be sent to a user when the threshold is crossed. Requires --action-email-address.
--action-email-address <address>
Specifies the email address of user to be notified. Specify --action-email-address for each additional email address of user to notify.
--email-template <path>
Specifies the path in /ifs to the email template.
{--verbose | -v}
Displays more detailed information.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\