Dell PowerStore 3000X EMC PowerStore Service Scripts Guide - Page 16

Cluster management (svc_cluster_management), Format, Optional arguments, Example, Usage

Page 16 highlights

May cause data unavailability? May cause data loss? Scope Prerequisites Yes Yes Node, cluster None Format svc_cluster_diag [-h] [-w] [-i] [-e] [-d] Optional arguments Qualifier -h, --help -w, --warningLevel -i,--infoLevel -e,--errorLevel -d,--debugLevel Description Show the help message and exit. Display and filter the log warning level messages (includes messages with a higher severity). Display and filter the log informational level logs (includes messages with a higher severity). Display and filter the ERROR level logs (includes messages with a higher severity). Display and filter the DEBUG level logs (includes messages with a higher severity). Example The following output indicates that no logs are available and the system is running a support materials bundle after you have entered the svc_cluster_diag command: svc_cluster_diag -w The log statements that are needed to collect information for the command: 'journalctl --utc -t control-path | egrep "\[CC\]" | grep WARN' are no longer available Would you like to perform a data collection? Please enter 'yes' or 'no' yes Running data collection - This might take awhile data collection ID f10a1ebb-5727-4a84-aa29-58df29274bcc Status OK HTTP Code 201 Cluster management (svc_cluster_management) This service script enables service providers to attach, detach, and view status of each appliance in a cluster. If an appliance in a two appliance cluster fails, or can no longer communicate with the other appliance, the remaining appliance becomes unmanageable. You can request your service provider to detach the failed appliance from the cluster, and restore the ability to manage the remaining appliance. Once the issue with the appliance is resolved, you can then use the prep-attach and attach commands to reattach the appliance back into the cluster. Usage Function Mode Recovery Normal 16 Service Commands

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74

May cause data unavailability?
Yes
May cause data loss?
Yes
Scope
Node, cluster
Prerequisites
None
Format
svc_cluster_diag [-h] [-w] [-i] [-e] [-d]
Optional arguments
Qualifier
Description
-h
,
--help
Show the help message and exit.
-w
,
--warningLevel
Display and filter the log warning level messages (includes messages with a higher severity).
-i
,
--infoLevel
Display and filter the log informational level logs (includes messages with a higher severity).
-e
,
--errorLevel
Display and filter the ERROR level logs (includes messages with a higher severity).
-d
,
--debugLevel
Display and filter the DEBUG level logs (includes messages with a higher severity).
Example
The following output indicates that no logs are available and the system is running a support materials bundle after you have entered the
svc_cluster_diag
command:
svc_cluster_diag -w
The log statements that are needed to collect information for the command:
'journalctl --utc -t control-path | egrep "\[CC\]"
| grep WARN' are no longer available
Would you like to perform a data collection? Please enter 'yes' or 'no'
yes
Running data collection - This might take awhile
data collection ID f10a1ebb-5727-4a84-aa29-58df29274bcc
Status
OK
HTTP Code
201
Cluster management (svc_cluster_management)
This service script enables service providers to attach, detach, and view status of each appliance in a cluster. If an appliance in a two
appliance cluster fails, or can no longer communicate with the other appliance, the remaining appliance becomes unmanageable.
You can request your service provider to detach the failed appliance from the cluster, and restore the ability to manage the remaining
appliance. Once the issue with the appliance is resolved, you can then use the prep-attach and attach commands to reattach the
appliance back into the cluster.
Usage
Function
Recovery
Mode
Normal
16
Service Commands