Installation manual

Adding a Managed Volume
Adding a Share
9-38 CLI Storage-Management Guide
Designating the Share as Critical (optional)
If the current switch has a redundant peer, you have the option to designate the current
share as critical. Skip to the next section if this switch is not configured for
redundancy.
If the volume software loses contact with one of its critical (and enabled) shares, the
ARX initiates a failover. The failover is accepted by the redundant peer as long as the
peer has full access to all critical shares, critical routes, and the quorum disk. If the
peer is unable to access any of these critical resources, no failover occurs.
As explained in the direct-volume chapter (recall “Designating the Share as Critical
(optional)” on page 8-15), you can use the
critical command to designate the current
share as a critical resource. For example, this command sequence designates the
“bills” share as a critical share:
bstnA6k(gbl)# namespace wwmed
bstnA6k(gbl-ns[wwmed])# volume /acct
bstnA6k(gbl-ns-vol[wwmed~/acct])# share bills
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~bills])# critical
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~bills])# ...
Removing Critical-Share Status
By default, shares are not critical. If the switch loses contact with a non-critical share,
the volume operates in a degraded state and the switch does not initiate a failover. Use
the
no critical command described earlier (“Removing Critical-Share Status” on
page 8-15). For example, this command sequence removes the “bills2” share from the
list of critical shares:
bstnA6k(gbl)# namespace wwmed
bstnA6k(gbl-ns[wwmed])# volume /acct
bstnA6k(gbl-ns-vol[wwmed~/acct])# share bills2
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~bills2])# no critical
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~bills2])# ...