Use
Use
Displays current cluster information. The last two lines only appear during a parallel
17 |
Displays current cluster information. The last two lines only appear during a parallel
17 |
Displays current cluster information. The last two lines only appear during a parallel
17 |
This is necessary because
This is necessary because
This is necessary because
This command runs locally (in the execution cluster) when submitted by a running job.
18 |This command runs locally (in the execution cluster) when submitted by a running job.
18 |This command runs locally (in the execution cluster) when submitted by a running job.
18 |This command runs locally (in the execution cluster) when submitted by a running job.
18 |%
20 | The option
This command runs locally (in the execution cluster) when submitted by a running job.
18 |%
20 | The option
This command runs locally (in the execution cluster) when submitted by a running job.
18 |%
20 | The option
The following notes and notices might appear in this guide:
The following notes and notices might appear in this guide:
The following notes and notices might appear in this guide:
This command runs locally (in the execution cluster) when submitted by a running job.
18 |
20 | The option %
This command runs locally (in the execution cluster) when submitted by a running job.
18 |
20 | The option %
This command runs locally (in the execution cluster) when submitted by a running job.
18 |
20 | The option %
At the top tier of the CLI the command classes can be seen by double-tapping the
24 |
A command class has a descendant structure built on command foundations.
31 |Each command class is in a section. Special commands are in separate sections. 32 | Because special commands have no descendant commands, they are not command 33 | classes.
34 |At the top tier of the CLI the command classes can be seen by double-tapping the
24 |
A command class has a descendant structure built on command foundations.
31 |Each command class is in a section. Special commands are in separate sections. 32 | Because special commands have no descendant commands, they are not command 33 | classes.
34 |At the top tier of the CLI the command classes can be seen by double-tapping the
24 |
A command class has a descendant structure built on command foundations.
31 |Each command class is in a section. Special commands are in separate sections. 32 | Because special commands have no descendant commands, they are not command 33 | classes.
34 |From the
From the
From the
Using
Some reports provide a more detailed view of your project's progress, allowing you to view the progression of your project's subordinate tasks towards their targets. This provides more nuanced reporting and manipulation, ensuring that you can manage your project more effectively.
28 |You use the
22 | The flow definition you are submitting may contain pre-defined events that trigger the flow.
24 | When you submit this flow using the
You use the
22 | The flow definition you are submitting may contain pre-defined events that trigger the flow.
24 | When you submit this flow using the
You use the
22 | The flow definition you are submitting may contain pre-defined events that trigger the flow.
24 | When you submit this flow using the
Notifications are the communication tool for alarms. They follow the structure 25 | derived from:
ABC 3413 SNMP-NOTIFICATION-MIB
28 |ABC 3014 NOTIFICATION-LOG-MIB
31 |ABC 3413 SNMP-TARGET-MIB
34 |ABC 3877 Alarm MIB
37 |Managers can review alarm models in the Alarm MIB to determine if a 40 | notification is of interest for alarm management. If no entries in the 41 | alarmModelTable can match a particular notification, then that notification is not 42 | relevant to the alarm models defined.
43 |Information in the alarm model such as the Notification ID or the description specify 44 | which error or warning condition the alarm indicates. If the ITU-ALARM-MIB is also 45 | supported, additional information is provided via the probable cause.
46 |Notifications are the communication tool for alarms. They follow the structure 25 | derived from:
ABC 3413 SNMP-NOTIFICATION-MIB
28 |ABC 3014 NOTIFICATION-LOG-MIB
31 |ABC 3413 SNMP-TARGET-MIB
34 |ABC 3877 Alarm MIB
37 |Managers can review alarm models in the Alarm MIB to determine if a 40 | notification is of interest for alarm management. If no entries in the 41 | alarmModelTable can match a particular notification, then that notification is not 42 | relevant to the alarm models defined.
43 |Information in the alarm model such as the Notification ID or the description specify 44 | which error or warning condition the alarm indicates. If the ITU-ALARM-MIB is also 45 | supported, additional information is provided via the probable cause.
46 |Notifications are the communication tool for alarms. They follow the structure 25 | derived from:
ABC 3413 SNMP-NOTIFICATION-MIB
28 |ABC 3014 NOTIFICATION-LOG-MIB
31 |ABC 3413 SNMP-TARGET-MIB
34 |ABC 3877 Alarm MIB
37 |Managers can review alarm models in the Alarm MIB to determine if a 40 | notification is of interest for alarm management. If no entries in the 41 | alarmModelTable can match a particular notification, then that notification is not 42 | relevant to the alarm models defined.
43 |Information in the alarm model such as the Notification ID or the description specify 44 | which error or warning condition the alarm indicates. If the ITU-ALARM-MIB is also 45 | supported, additional information is provided via the probable cause.
46 |Using
Some reports provide a more detailed view of your project's progress, allowing you to view the progression of your project's subordinate tasks towards their targets. This provides more nuanced reporting and manipulation, ensuring that you can manage your project more effectively.
28 |For specific information see:
Using
Some reports provide a more detailed view of your project's progress, allowing you to view the progression of your project's subordinate tasks towards their targets. This provides more nuanced reporting and manipulation, ensuring that you can manage your project more effectively.
28 |For specific information see:
Faulted/not faulted physical drive notifications share these MIB references:
The 25 | physical drive not faulted notification is sent when a physical 26 | device enters either the online or hot spare state.
27 | 28 |The
For advanced table management, use the whole toolbar.
28 |If no targets are set, then the classifier is available for all elements on 44 | all nodes.
45 |Faulted/not faulted physical drive notifications share these MIB references:
The 25 | physical drive not faulted notification is sent when a physical 26 | device enters either the online or hot spare state.
27 | 28 |The
For advanced table management, use the whole toolbar.
28 |If no targets are set, then the classifier is available for all elements on 44 | all nodes.
45 |Faulted/not faulted physical drive notifications share these MIB references:
The 25 | physical drive not faulted notification is sent when a physical 26 | device enters either the online or hot spare state.
27 | 28 |The
For advanced table management, use the whole toolbar.
28 |If no targets are set, then the classifier is available for all elements on 44 | all nodes.
45 |A limiter controls the value of a threshold, providing control over when 24 | actions are executed. They can be used to apply actions after a threshold (like 25 | number of connections) is exceeded, or can be used to define a control system to 26 | manage the amount of bandwidth on the network.
27 |Limiters are used in:
limit threshold condition
30 |published expressions template
33 |A limiter controls the value of a threshold, providing control over when 24 | actions are executed. They can be used to apply actions after a threshold (like 25 | number of connections) is exceeded, or can be used to define a control system to 26 | manage the amount of bandwidth on the network.
27 |Limiters are used in:
limit threshold condition
30 |published expressions template
33 |A limiter controls the value of a threshold, providing control over when 24 | actions are executed. They can be used to apply actions after a threshold (like 25 | number of connections) is exceeded, or can be used to define a control system to 26 | manage the amount of bandwidth on the network.
27 |Limiters are used in:
limit threshold condition
30 |published expressions template
33 |To divert to a host destination when your packets need to be backed up on a separate 24 | server.
25 |This is the default selection.
38 |The displayed header size changes based on the type selected.
42 |The input fields displayed below the payload diagram vary with the header 48 | selected.
49 |Rather than relying on a single cluster administrator for your
An administrator can delegate specific sub-sets of rights to 29 | sub-administrators, with the ability to manage other users within their domain or to project 30 | owners with limited control over data resources within their domain.
31 |Administrators can quickly and easily make changes to a wide range of
Rather than relying on a single cluster administrator for your
An administrator can delegate specific sub-sets of rights to 29 | sub-administrators, with the ability to manage other users within their domain or to project 30 | owners with limited control over data resources within their domain.
31 |Administrators can quickly and easily make changes to a wide range of
To divert to a host destination when your packets need to be backed up on a separate 24 | server.
25 |This is the default selection.
38 |The displayed header size changes based on the type selected.
42 |The input fields displayed below the payload diagram vary with the header 48 | selected.
49 |To divert to a host destination when your packets need to be backed up on a separate 24 | server.
25 |This is the default selection.
38 |The displayed header size changes based on the type selected.
42 |The input fields displayed below the payload diagram vary with the header 48 | selected.
49 |Rather than relying on a single cluster administrator for your
An administrator can delegate specific sub-sets of rights to 29 | sub-administrators, with the ability to manage other users within their domain or to project 30 | owners with limited control over data resources within their domain.
31 |Administrators can quickly and easily make changes to a wide range of
The command foundation is a minimum of one word at the CLI prompt that combines at
25 | least one attribute, and resolves to a command itself, whether or not there are more
26 | optional attributes and/or parameters
27 | available:
The syntax section
33 | lists all the variations of the command foundation with available
34 | attributes and parameters, as in:
Attributes that 42 | concatenate with the command foundation are listed in a table.
Sub-attributes 44 | are concatenated with attributes and listed in a table.
Parameters that 46 | concatenate with attributes, sub-attributes, and other parameters 47 | are listed in a table.
Lists and defines 49 | the output columns provided by the command foundation.
Provides references for terminology expressed in command output. Usually an RFC, internal MIB, or
51 | industry standard specifications, as in
The command foundation is a minimum of one word at the CLI prompt that combines at
25 | least one attribute, and resolves to a command itself, whether or not there are more
26 | optional attributes and/or parameters
27 | available:
The syntax section
33 | lists all the variations of the command foundation with available
34 | attributes and parameters, as in:
Attributes that 42 | concatenate with the command foundation are listed in a table.
Sub-attributes 44 | are concatenated with attributes and listed in a table.
Parameters that 46 | concatenate with attributes, sub-attributes, and other parameters 47 | are listed in a table.
Lists and defines 49 | the output columns provided by the command foundation.
Provides references for terminology expressed in command output. Usually an RFC, internal MIB, or
51 | industry standard specifications, as in
The command foundation is a minimum of one word at the CLI prompt that combines at
25 | least one attribute, and resolves to a command itself, whether or not there are more
26 | optional attributes and/or parameters
27 | available:
The syntax section
33 | lists all the variations of the command foundation with available
34 | attributes and parameters, as in:
Attributes that 42 | concatenate with the command foundation are listed in a table.
Sub-attributes 44 | are concatenated with attributes and listed in a table.
Parameters that 46 | concatenate with attributes, sub-attributes, and other parameters 47 | are listed in a table.
Lists and defines 49 | the output columns provided by the command foundation.
Provides references for terminology expressed in command output. Usually an RFC, internal MIB, or
51 | industry standard specifications, as in
Capture file names must be entered with a relative pathname. The absolute path is 25 | determined when a file is received, when the relative path is appended to a default 26 | absolute path prefix.
27 |
28 | Current directory (".") and parent directory ("..") indicators are
30 | not allowed in the relative path definition.
The default absolute path is
The file name that you enter is a prefix, to which is added an 8-digit
40 | number followed by
When files are being written, a temporary file is used. The temporary 51 | file cannot be read. When a flush occurs, the file is renamed and can be 52 | read.
53 |Capture file names must be entered with a relative pathname. The absolute path is 25 | determined when a file is received, when the relative path is appended to a default 26 | absolute path prefix.
27 |
28 | Current directory (".") and parent directory ("..") indicators are
30 | not allowed in the relative path definition.
The default absolute path is
The file name that you enter is a prefix, to which is added an 8-digit
40 | number followed by
When files are being written, a temporary file is used. The temporary 51 | file cannot be read. When a flush occurs, the file is renamed and can be 52 | read.
53 |Capture file names must be entered with a relative pathname. The absolute path is 25 | determined when a file is received, when the relative path is appended to a default 26 | absolute path prefix.
27 |
28 | Current directory (".") and parent directory ("..") indicators are
30 | not allowed in the relative path definition.
The default absolute path is
The file name that you enter is a prefix, to which is added an 8-digit
40 | number followed by
When files are being written, a temporary file is used. The temporary 51 | file cannot be read. When a flush occurs, the file is renamed and can be 52 | read.
53 |By default, timeout and wait time are set to 360 and 10 respectively, but can be 18 | changed to suit each individual job-forwarding queue.
19 |Jobs submitted to queue pend in an execution cluster for up to the specified number 35 | of timeout seconds before returning to the submission cluster for rescheduling. Jobs 36 | can be forwarded to the same cluster once again after wait time, in seconds.
37 |
40 |
and in
Thus the cluster reselection timeout and wait time are given by:
timeout = 50x20 seconds = 1000 seconds
47 |wait time = 10x20 seconds = 200 seconds
50 |By default, timeout and wait time are set to 360 and 10 respectively, but can be 18 | changed to suit each individual job-forwarding queue.
19 |Jobs submitted to queue pend in an execution cluster for up to the specified number 35 | of timeout seconds before returning to the submission cluster for rescheduling. Jobs 36 | can be forwarded to the same cluster once again after wait time, in seconds.
37 |
40 |
and in
Thus the cluster reselection timeout and wait time are given by:
timeout = 50x20 seconds = 1000 seconds
47 |wait time = 10x20 seconds = 200 seconds
50 |By default, timeout and wait time are set to 360 and 10 respectively, but can be 18 | changed to suit each individual job-forwarding queue.
19 |Jobs submitted to queue pend in an execution cluster for up to the specified number 35 | of timeout seconds before returning to the submission cluster for rescheduling. Jobs 36 | can be forwarded to the same cluster once again after wait time, in seconds.
37 |
40 |
and in
Thus the cluster reselection timeout and wait time are given by:
timeout = 50x20 seconds = 1000 seconds
47 |wait time = 10x20 seconds = 200 seconds
50 |Once resources are registered within
Once resources are registered within
Once resources are registered within
A cluster that is not properly configured is displayed in yellow. A cluster that is
20 | offline is displayed in red. The
A troubleshooting tab is displayed, showing the results from the diagnostic test 36 | performed on the selected entity.
37 |A cluster that is not properly configured is displayed in yellow. A cluster that is
20 | offline is displayed in red. The
A troubleshooting tab is displayed, showing the results from the diagnostic test 36 | performed on the selected entity.
37 |A cluster that is not properly configured is displayed in yellow. A cluster that is
20 | offline is displayed in red. The
A troubleshooting tab is displayed, showing the results from the diagnostic test 36 | performed on the selected entity.
37 |You can change your password after you log on to
Select the
Yes. You can create custom data
20 | views that provide analytics specific to the needs of your project in the
You can generate customized queries on the tasks, clusters, and targets in your
27 |
Within the
If the data views in the
Click on the
You can change your password after you log on to
Select the
Yes. You can create custom data
20 | views that provide analytics specific to the needs of your project in the
You can generate customized queries on the tasks, clusters, and targets in your
27 |
Within the
If the data views in the
Click on the
You can change your password after you log on to
Select the
Yes. You can create custom data
20 | views that provide analytics specific to the needs of your project in the
You can generate customized queries on the tasks, clusters, and targets in your
27 |
Within the
If the data views in the
Click on the
Enabling the metadata settings in
The
Enabling the metadata settings in
The
Enabling the metadata settings in
The
Jobs are forwarded to the execution cluster based on swp, mem, type, ncpu, model, boolean 17 | resources, cpu factors, and user-defined shared resource requirements. In some cases, however, 18 | jobs may reach the execution cluster and find other required resources are not available. The 19 | cluster reselection policy sets the length of time jobs pend, and allows returned jobs to be 20 | forwarded to other execution clusters that may have different resources available.
21 |Intelligence is built into execution clusters so that in the event that required resources are 22 | no longer available on a given execution cluster, the job will be automatically forwarded to an 23 | execution cluster that does have the required resources.
24 |The time forwarded jobs spend in being forwarded between execution clusters before returning to the submission cluster 25 | for rescheduling can be configured for each queue.
26 |The wait time before the same job is returned to the same execution cluster can also be set.
27 | Both values are defined in
32 | timeout* The timeout value can be customized based on average job runtime and
39 | timeout = MAX(job_runtime, ( wait_time*
Jobs are forwarded to the execution cluster based on swp, mem, type, ncpu, model, boolean 17 | resources, cpu factors, and user-defined shared resource requirements. In some cases, however, 18 | jobs may reach the execution cluster and find other required resources are not available. The 19 | cluster reselection policy sets the length of time jobs pend, and allows returned jobs to be 20 | forwarded to other execution clusters that may have different resources available.
21 |Intelligence is built into execution clusters so that in the event that required resources are 22 | no longer available on a given execution cluster, the job will be automatically forwarded to an 23 | execution cluster that does have the required resources.
24 |The time forwarded jobs spend in being forwarded between execution clusters before returning to the submission cluster 25 | for rescheduling can be configured for each queue.
26 |The wait time before the same job is returned to the same execution cluster can also be set.
27 | Both values are defined in
32 | timeout* The timeout value can be customized based on average job runtime and
39 | timeout = MAX(job_runtime, ( wait_time*
Jobs are forwarded to the execution cluster based on swp, mem, type, ncpu, model, boolean 17 | resources, cpu factors, and user-defined shared resource requirements. In some cases, however, 18 | jobs may reach the execution cluster and find other required resources are not available. The 19 | cluster reselection policy sets the length of time jobs pend, and allows returned jobs to be 20 | forwarded to other execution clusters that may have different resources available.
21 |Intelligence is built into execution clusters so that in the event that required resources are 22 | no longer available on a given execution cluster, the job will be automatically forwarded to an 23 | execution cluster that does have the required resources.
24 |The time forwarded jobs spend in being forwarded between execution clusters before returning to the submission cluster 25 | for rescheduling can be configured for each queue.
26 |The wait time before the same job is returned to the same execution cluster can also be set.
27 | Both values are defined in
32 | timeout* The timeout value can be customized based on average job runtime and
39 | timeout = MAX(job_runtime, ( wait_time*
60 |
60 |
Faulty/not faulty physical drive notifications share these MIB references:
The 25 | faulted physical drive notification is sent when a physical device 26 | enters a state other than online or hot spare.
27 |