Brocade Fabric OS Command Reference (Supporting Fabric OS v7.3.0) User Manual

Page 259

Advertising
background image

Fabric OS Command Reference

229

53-1003131-01

cryptoCfg

2

To reclaim all WWNs associated with a member node when no containers are present on the node:

switch:admin> cryptocfg --reclaimWWN -membernode 10:00:00:05:33:13:7a:e8

Warning: WWN reclaim operation may result in momentary IO disruption.

Make sure that the Membernodes are not hosting any container.

ARE YOU SURE (yes, y, no, n): [no] y

Operation succeeded.

Please use "cryptocfg --commit" to commit the configuration.

Please eject the membernode from the EG "cryptocfg

--eject -membernode 10:00:00:05:33:13:7a:e8".

Then deregister the membernode "cryptocfg --dereg

-membernode 10:00:00:05:33:13:7a:e8".

On the membernode [10:00:00:05:33:13:7a:e8]

execute "cryptocfg --reclaimWWN -cleanup".

To display the crypto-target containers affected by the reclaim operation:

switch:admin> cryptocfg --reclaimWWN -membernode membernode \

10:00:00:05:33:13:7a:e8 -list

Following is the list of containers using the reclaimed WWN base.

[ 1] H183SB182_1

[ 2] H183SB182_2

[ 3] H183SB182_3

[ 4] H183SB182_4

[ 5] H183SB182_5

[ 6] H183SB182_6

Operation succeeded.

To clean up the stale crypto configurations from the ejected member node.

switch:admin> cryptocfg --reclaimWWN -cleanup

Warning: There are stale (Container|HA|Tape) cryptodb \

configurations. Please confirm to delete them.

ARE YOU SURE (yes, y, no, n): [no] y

Warning: These are the list of crypto configuration \

files to be cleaned up:

Inside /etc/fabos/mace (crypto_dek.db.0, crypto_dev.db.0, \

crypto_hac.db.0, crypto_pool.db.0, crypto_wwn.db.0).

ARE YOU SURE (yes, y, no, n): [yes] y

Operation Succeeded.

FUNCTION

5. Transaction management

SYNOPSIS

cryptocfg --help transcfg

cryptocfg --commit [-force]

cryptocfg --transabort transaction_ID

cryptocfg --transshow

DESCRIPTION

Use these cryptoCfg commands to manage the transaction mechanism for those functions that require
configuration changes to be committed before they take effect. These functions include "3. High
Availability (HA) cluster configuration" and "4. Storage device configuration and management"

Transaction commands must be invoked on the group leader.

Advertising