Installation manual

Adding a Direct Volume
Adding a Share
CLI Storage-Management Guide 8-15
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 direct 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.
(For instructions on configuring critical routes, refer back to “Identifying a Critical
Route” on page 6-15 of the CLI Network-Management Guide.)
From gbl-ns-vol-shr mode, use the
critical command to designate the current share as
a critical resource:
critical
For example, this command sequence designates the “corporate” share as a critical
share:
bstnA6k(gbl)# namespace medco
bstnA6k(gbl-ns[medco])# volume /vol
bstnA6k(gbl-ns-vol[medco~/vol])# share corporate
bstnA6k(gbl-ns-vol-shr[medco~/vol~corporate])# critical
bstnA6k(gbl-ns-vol-shr[medco~/vol~corporate])# ...
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.
From gbl-ns-vol-shr mode, use the
no critical command to make the current share
non-critical:
no critical
For example, this command sequence removes the “generic” share from the list of
critical shares:
bstnA6k(gbl)# namespace medco
bstnA6k(gbl-ns[medco])# volume /vol