Generates SAS messages from the specified Controller to the partner Controller and from the specified Controller to the Drive Enclosures. This command is used for testing purposes.
topology ‑generateTraffic ‑controller controller‑id‑or‑fqn ‑numberBytes number‑of‑bytes [{‑iterations number‑of‑iterations | ‑seconds number‑of‑seconds}] [{‑sessionKey | ‑u admin‑user ‑oracleFS oracle‑fs‑system}] [{‑outputformat | ‑o} { text | xml }] [{‑timeout timeout‑in‑seconds | ‑verify | ‑usage | ‑example | ‑help}]
Use the topology ‑generateTraffic command as instructed by Oracle Customer Support to test the connections and cabling. Before issuing the subcommand, the Oracle Customer Support representative might instruct you to disable the automatic management of the Backend SAS interconnect by using a topology ‑modify ‑manualMode command. The Oracle Customer Support representative might also request that you issue a controller ‑list ‑details command to test the SAS HBAs before generating traffic.
Specifies the fully qualified name (FQN) or the unique identifier (ID) of a Controller from which the traffic is generated. The traffic is sent to the partner Controller.
Identifies the number of times that the traffic generation repeats. The ‑iterations option is not allowed in conjunction with the ‑seconds option.
Specifies the number of bytes to transfer from the Controller to all of the components to which the Controller is physically connected.
Identifies the length of time, in seconds, that the traffic is generated. The ‑seconds option is not allowed in conjunction with the ‑iterations option.
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.
For diagnostic purposes, Oracle Customer Support instructs you to generate a burst of traffic from a Controller to the partner Controller and to all of the Drive Enclosures that are connected to the Controller.
The fully qualified name of the Controller: /CONTROLLER-01
The number of bytes to generate: 32
$ fscli topology ‑generateTraffic ‑controller /CONTROLLER-01 ‑numberBytes 32