Performing Initial Configuration with the CLI
Infiniband Upgrade Procedures for Q3.2010
Configuration Rules and Guidelines
Associating a LUN with an FC initiator group
Associating a LUN with an FC initiator group
Scripting Aliases for Initiators and Initiator Groups
Supported InfiniBand Client-Side Data Protocols
Supported Fiber Channel Initiators
Configuring FC Client Multipathing
Configuring Solaris Initiators
Configuring Windows Initiators
Windows Tunables - Microsoft DSM Details
Configuring VMware ESX Initiators
Solaris iSCSI/iSER and MPxIO Considerations
Creating an Analytics Worksheet
Adding an iSCSI target with an auto-generated IQN
Adding an iSCSI target with a specific IQN and RADIUS authentication
Adding an iSCSI initiator which uses CHAP authentication
Adding an iSCSI initiator group
Storage Array Type Plugin (satp)
Configuration Changes in a Clustered Environment
Clustering Considerations for Storage
Clustering Considerations for Networking
Clustering Considerations for Infiniband
Preventing 'Split-Brain' Conditions
This section contains preference settings for your locality, session properties, and SSH keys.
|
When logged into the BUI, you can set the above preferences for your account, but you cannot set other user account preferences.
Preferences may be set in the CLI under configuration users. The following example shows enabling advanced analytics for the "brendan" user account:
caji:> configuration users
caji:configuration users> select brendan
caji:configuration users brendan> preferences
caji:configuration users brendan preferences> show
Properties:
locale = C
login_screen = status/dashboard
session_timeout = 15
advanced_analytics = false
Children:
keys => Manage SSH public keys
caji:configuration users brendan preferences> set advanced_analytics=true
advanced_analytics = true (uncommitted)
caji:configuration users brendan preferences> commit
Set your own preferences in the CLI under configuration preferences. The following example shows setting a session annotation for your own account:
twofish:> configuration preferences
twofish:configuration preferences> show
Properties:
locale = C
login_screen = status/dashboard
session_timeout = 15
session_annotation =
advanced_analytics = false
Children:
keys => Manage SSH public keys
twofish:configuration preferences> set session_annotation="Editing my user preferences"
session_annotation = Editing my user preferences (uncommitted)
twofish:configuration preferences> commit
These may be needed when automating the execution of CLI scripts from another host. The following shows the addition of an SSH key from the CLI:
caji:> configuration preferences keys
caji:configuration preferences keys> create
caji:configuration preferences key (uncommitted)> set type=DSA
caji:configuration preferences key (uncommitted)> set key="...DSA key text..."
key = ...DSA key text...== (uncommitted)
caji:configuration preferences key (uncommitted)> set comment="fw-log1"
comment = fw-log1 (uncommitted)
caji:configuration preferences key (uncommitted)> commit
caji:configuration preferences keys> show
Keys:
NAME MODIFIED TYPE COMMENT
key-000 10/12/2009 10:54:58 DSA fw-log1
The key text is just the key text itself (usually hundreds of characters), without spaces.