Changes account settings.
account ‑modify
[‑account account‑id‑or‑fqn]
[‑fullName full‑name]
[‑password]
[‑email email‑address]
[‑phone phone‑number]
[‑name new‑account‑name]
[‑role { admin1 | admin2 | monitor | support}]
[{‑enable | ‑disable}]
[‑passwordDuration duration‑in‑days]
[{‑sessionKey | ‑u admin‑user ‑oracleFS oracle‑fs‑system}]
[{‑outputformat | ‑o} { text | xml }]
[{‑timeout timeout‑in‑seconds | ‑verify | ‑usage | ‑example | ‑help}]
Full name
Password duration
Email address
Phone number
Account name
Role
Account availability status (enabled or disabled)
Disabling an account that has active sessions does not terminate the sessions. You cannot change the Primary administrator role that is permanently assigned to the /administrator account. Also, you cannot change the Oracle Customer Support role that is permanently assigned to the /pillar account.
If one or more administrators are logged in to a specific account, you cannot modify the role for that account until all of the administrators log out. However, changes to the other fields are permitted, including resetting the password and disabling the account. These changes take effect immediately after the administrators end their sessions.
When logging in, if a non-primary administrator fails to enter the correct password after making a maximum number of attempts, the Oracle FS System automatically disables the account. Use the system ‑modify ‑maximumFailedLogins command to change the maximum number of failed attempts that are permitted before an account is disabled. Because the default /administrator and /pillar accounts are required for basic administration, that account cannot be disabled even if the maximum number of failed attempts has been reached.
To prevent security breaches, frequently change the passwords of the /administrator and /pillar accounts and provide access to the current password through a restricted site.
To enable an administrator-defined account that has been disabled, log in with the /administrator account or an Administrator 1 account and run the account ‑modify ‑enable command.
To disable an account, run the account ‑modify ‑disable command.
Specifies the fully qualified name (FQN) or unique identifier (ID) of the account. Account names are case sensitive.
If you do not supply an account name, the account under which you are currently logged in will be modified.
Disables the specified account.
Enables the specified account.
Specifies the name of the account owner. If the full name contains spaces, enclose the entire name inside double quotation marks. For example: “Tyler Leslie Mendoza”.
Specifies the account name. Use double quotation marks around names containing dashes.
Requests that the administrator provide a new password.
Specifies the number of days that the password that the administrator provides is valid. When the password expires, the Oracle FS System prompts the account user to provide a new password.
Specifies the phone number of the account owner. The Oracle FS System does not verify the validity of the phone number.
Administration
Configuration
Recovery
Create, modify, or delete administrator accounts
Modify Call‑Home settings.
Create, modify, or delete LUNs, File Servers, and filesystems.
Modify system-wide settings.
Modify software configurations
Modify hardware configurations.
Shut down the Oracle FS System.
Authorizes the administrator to perform support operations as instructed by Oracle Customer Support. This role does not authorize the administrator to modify or delete data resources, system alerts, or administrator accounts.
The following global options can be used for fully formed fscli commands:
The command completes successfully.
The command returns with an error.
The session times out.
Inspects the validity of the command syntax, not the semantics. Used to test the structure of a command without running the command. Does not determine whether errors would be produced if you issue a structurally correct command with the input provided.
Directs the CLI to prompt you to supply a session key when you issue the command. The CLI displays Sessionkey: as the prompt. To obtain a session key, log in with the ‑returnKey option specified. After the session is established, the session key is displayed in STDOUT. If you request a session key, the ‑sessionkey option is required syntax for all commands that are issued in a given session. In environments with more than one Oracle FS System, the session key is used to determine to which Oracle FS System to direct the command for validation. Session keys are also used to establish two or more CLI sessions when using a shared administrator account.