ERROR: read error on status slice object.volume, class=class:
volume info:devno(maj,min)=v_devno(v_maj,v_min)
device info:devno(maj,min)=p_devno(p_maj,p_min)
devname=device
error info: blk in disk=blknodk, blk in slice=blknosl,
length=length, resid=resid, errno=errno
Explanation
Read request sent to slice object.volume in status status terminated abnormally. Read request sent to volume configured by this slice, or to slice accessible in isolation was returned as error.
You must attempt recovery as soon as possible since the application may cease normal operation.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk.
ERROR: write error on status slice object.volume, class=class:
volume info:devno(maj,min)=v_devno(v_maj,v_min)
device info:devno(maj,min)=p_devno(p_maj,p_min)
devname=device
error info: blk in disk=blknodk, blk in slice=blknosl,
length=length, resid=resid, errno=errno
Explanation
Write request sent to slice object.volume in status status terminated abnormally. Write request sent to volume configured by this slice, or to slice accessible in isolation was returned as error.
You must attempt recovery as soon as possible since the application may cease normal operation.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk.
ERROR: open error on status slice object.volume, class=class:
volume info:devno(maj,min)=v_devno(v_maj,v_min)
device info:devno(maj,min)=p_devno(p_maj,p_min)
devname=device
error info: oflag=oflag, errno=errno
Explanation
Open request sent to slice object.volume in status status terminated abnormally. Open request sent to volume configured by this slice, or to slice accessible in isolation was returned as error.
You must attempt recovery as soon as possible since the application may cease to operate normally.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk.
ERROR: read error and writeback error on status slice object.volume, class=class:
volume info:devno(maj,min)=v_devno(v_maj,v_min)
device info:devno(maj,min)=p_devno(p_maj,p_min)
devname=device
error info: blk in disk=blknodk, blk in slice=blknosl,
length=length, resid=resid, errno=errno
Explanation
Read request and writeback request sent to slice object.volume in status status terminated abnormally. Read request sent to volume configured by this slice, or to slice accessible in isolation was returned as error.
You must attempt recovery as soon as possible since the application may not operate normally.
Writeback is a process to read data from other slices in the event of a read error.
Resolution
Disk failure may have occurred. Identify the cause by referring to disk driver log message, and promptly recover the disk.
ERROR: disk: device: ready for swapping due to I/O error, class=class
Explanation
Because an I/O error occurred on the disk disk in the class class, the physical disk device was excluded from GDS management and made exchangeable.
Resolution
Exchange the physical disk device, and then include it into GDS management executing diskpowon(1M), the hot-swap disk attachment command that is a machine administrative function provided by Enhanced Support Facility (ESF).
For details, see "Machine Administration Guide."
However, if the error message "ERROR: device: setup for hot-swap failed" is output following this message on the console, recovery based on the resolution method related in that message is necessary.
ERROR: device: setup for hot-swap failed
Explanation
The physical disk device was excluded from GDS management and made exchangeable, but preparations for hot swap with a machine administrative function of Enhanced Support Facility (ESF) failed.
Resolution
Exchange the physical disk device, and then include it into GDS management executing the sdxswap -I command or performing physical disk restoration in GDS Management View.
ERROR: volume: closed down volume, class=class
Explanation
volume has closed down.
Resolution
Promptly attempt recovery by identifying the cause of failure by referring to GDS log message that was output immediately before the error.
For information on recovery, see "F.1.3 Volume Status Abnormality."
ERROR: class: cannot startup class, no valid configuration database, sdxerrno=errno
Explanation
Could not startup class, since valid class configuration database could not be found.
This message is output when all disks (or the majority of disks) registered with class are unavailable.
Resolution
ERROR: class: cannot startup class, too few valid configuration database replicas, sdxerrno=errno
Explanation
Could not startup class, due to insufficient number of valid databases.
This message is output when many disks registered with class are unavailable.
Resolution
ERROR: class: closing down class, no valid configuration database
Explanation
class was closed since no valid class configuration database was found.
This message is output when all disks (or the majority of disks) registered with class are unavailable.
Resolution
ERROR: class: closing down class, too few valid configuration database replicas
Explanation
class was closed due to insufficient number of valid database.
This message is output when many disks registered with class are unavailable.
Resolution
ERROR: failed to send request message on node node, details
Explanation
Sending request message from node was unsuccessful.
Resolution
Collect investigation material and contact field engineers.
ERROR: timeout on receiving reply message from node node, details
Explanation
Timeout occurred while receiving a reply message from a remote node node.
Resolution
Collect investigation material and contact field engineers.
ERROR: rejected request message on remote node node, details
Explanation
Processing a request message on a remote node node was unsuccessful.
Resolution
Investigate the node message log and take necessary actions. If recovery is impossible, collect investigation material and contact field engineers.
ERROR: class: failed to start type volumes, status volume volume exists, node=node
Explanation
Starting volumes within the class class failed on the node node since the status volume volume exists.
type is the class type attribute.
Resolution
volume is in abnormal status. First, you must recover normal status.
For information on recovery, see "F.1.3 Volume Status Abnormality."
ERROR: class: failed to start and standby type volumes, status volume volume exists, node=node
Explanation
Starting and putting on standby volumes within the class class failed on the node node since the status volume volume exists.
type is the class type attribute.
Resolution
volume is in abnormal status. First, you must recover normal status.
For information on recovery, see "F.1.3 Volume Status Abnormality."
ERROR: class: failed to stop and standby type volumes, status volume volume exists, node=node
Explanation
Stopping and putting on standby volumes within the class class failed on the node node since the status volume volume exists.
type is the class type attribute.
Resolution
volume is in abnormal status. First, you must recover normal status.
For information on recovery, see "F.1.3 Volume Status Abnormality."
ERROR: class: failed to stop type volumes, status volume volume exists, node=node
Explanation
Stopping volumes within the class class failed on the node node since the status volume volume exists.
type is the class type attribute.
Resolution
volume is in abnormal status. First, you must recover normal status.
For information on recovery, see "F.1.3 Volume Status Abnormality."
ERROR: class: failed to start type volumes, class closed down, node=node
Explanation
Starting volumes failed since the class class has been closed down.
type is the class type attribute.
Resolution
Recover closed class. There may be multiple disk failures. Identify the cause based on object status, GDS log message, and syslog message.
For information on recovery, see "F.1.4 Class Status Abnormality."
ERROR: class: failed to start and standby type volumes, class closed down, node=node
Explanation
Starting and putting on standby volumes failed, since the class class has been closed down.
type is the class type attribute.
Resolution
Recover closed class. There may be multiple disk failures. Identify the cause based on object status, GDS log message, and syslog message.
For information on recovery, see "F.1.4 Class Status Abnormality."
ERROR: class: failed to stop and standby type volumes, class closed down, node=node
Explanation
Stopping and putting on standby volumes failed. Since the class class has been closed down.
type is the class type attribute.
Resolution
Recover closed class. There may be multiple disk failures. Identify the cause based on object status, GDS log message, and syslog message.
For information on recovery, see "F.1.4 Class Status Abnormality."
ERROR: class: failed to stop type volumes, class closed down, node=node
Explanation
Stopping volumes failed since the class class has been closed down.
type is the class type attribute.
Resolution
Recover closed class. There may be multiple disk failures. Identify the cause based on object status, GDS log message, and syslog message.
For information on recovery, see "F.1.4 Class Status Abnormality."
ERROR: class: closing down class, cluster-wide lock failure, sdxerrno=sdxerrno
Explanation
Abnormal exclusive control between cluster system nodes occurred. Since the process cannot be continued, class will be closed.
Resolution
Collect investigation material and contact field engineers.
ERROR: class: cannot startup class, cluster-wide lock failure, sdxerrno=errno
Explanation
Abnormal exclusive control between cluster system nodes occurred. Since the process cannot be continued, class could not be started.
Resolution
Collect investigation material and contact field engineers.
ERROR: class: closing down class, cluster communication failure, sdxerrno=sdxerrno
Explanation
Transmission failure between cluster system nodes occurred. Since the process cannot be continued, class will be closed.
Resolution
Collect investigation material and contact field engineers.
ERROR: class: cannot operate in cluster environment, created when cluster control facility not ready
Explanation
The class class cannot be used in a cluster environment since it was created when the cluster control facility was inactive. This message is output when one of the following operations is performed.
After class was created automatic resource registration was performed on a node where automatic resource registration was not complete.
In a cluster environment where automatic resource registration is complete, class was created in single user mode.
A single node with class was changed over to a cluster system.
Resolution
See "(1) The error message "ERROR: class: cannot operate in cluster environment, ..." is output, and the operation cannot be conducted on the class class." in "F.1.9 Cluster System Related Error."
ERROR: proxy: failed to copy with OPC, source=disk.volume, target=disk.volume, class=class
Explanation
While performing copying between proxy volume proxy and master volume with the OPC function, an I/O error occurred, and the copying process failed.
"source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.
Resolution
Identify the cause by referring to the log messages for GDS, disk driver, and ETERNUS Disk storage system that were output right before the occurrence of the error, and restore.
ERROR: proxy: failed to copy with EC, source=disk.volume, target=disk.volume, class=class
Explanation
While performing copying between proxy volume proxy and master volume with the EC function, an I/O error occurred, and the copying process failed.
"source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.
Resolution
Identify the cause by referring to the log messages for GDS, disk driver, and ETERNUS Disk storage system that were output right before the occurrence of the error, and restore.
ERROR: proxy: failed to copy with TimeFinder, source=disk, target=disk, class=class
Explanation
Copying failed due to an I/O error caused while conducting copying between the proxy group proxy and the master group with TimeFinder.
"source" is the name of the copy source disk, "target" is the name of the copy destination disk, and "class" is the name of the class to which the copy source and destination disks belong.
Resolution
Identify the cause by referring to the log messages for GDS, disk driver and Dell EMC storage units that were output right before the occurrence of the error, and restore.
ERROR: proxy: failed to copy with SRDF, source=disk, target=disk, class=class
Explanation
Copying failed due to an I/O error caused while conducting copying between the proxy group proxy and the master group with SRDF.
"source" is the name of the copy source disk, "target" is the name of the copy destination disk, and "class" is the name of the class to which the copy source and destination disks belong.
Resolution
Identify the cause by referring to the log messages for GDS, disk driver and Dell EMC storage units that were output right before the occurrence of the error, and restore.
ERROR: proxy: failed to start OPC, source=disk.volume, target=disk.volume, class=class
Explanation
An error occurred between proxy volume proxy and the master volume when OPC was initiated.
"source" indicates the copy source slice name, "target" indicates the copy destination slice name, and "class" indicates a class to which the copy source and destination slices belong.
Resolution
Identify the cause based on log messages of GDS, disk drivers, ETERNUS Disk storage system and such, and promptly recover the disk.
ERROR: proxy: failed to stop OPC, source=disk.volume, target=disk.volume, class=class
Explanation
When stopping OPC between proxy volume proxy and master volume, an error occurred.
"source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.
Resolution
Identify the cause by referring to the log messages for GDS, disk driver, ETERNUS Disk storage system that were output right before the occurrence of the error, and restore.
ERROR: proxy: failed to start EC session, source=disk.volume, target=disk.volume, class=class
Explanation
An error occurred between proxy volume proxy and the master volume when EC was initiated.
"source" indicates the copy source slice name, "target" indicates the copy destination slice name, and "class" indicates a class to which the copy source and destination slices belong.
Resolution
Identify the cause based on log messages of GDS, disk drivers, ETERNUS Disk storage system and such, and promptly recover the disk.
ERROR: proxy: failed to stop EC session, source=disk.volume, target=disk.volume, class=class
Explanation
When stopping EC session between proxy volume proxy and master volume, an error occurred.
"source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.
Resolution
Identify the cause by referring to the log messages for GDS, disk driver, and ETERNUS Disk storage system that was output right before the occurrence of the error, and restore.
ERROR: proxy: failed to suspend EC session, source=disk.volume, target=disk.volume, class=class
Explanation
When temporarily suspending EC session between proxy volume proxy and master volume, an error occurred.
"source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.
Resolution
Identify the cause by referring to the log messages for GDS, disk driver, and ETERNUS Disk storage system that were output right before the occurrence of the error, and restore.
ERROR: proxy: failed to resume EC session, source=disk.volume, target=disk.volume, class=class
Explanation
When resuming EC session between proxy volume proxy and master volume, an error occurred.
"source" specifies the original slice name, "target" the mirror slice name, and "class" to which the original slice and mirror slice belong.
Resolution
Identify the cause by referring to the log messages for GDS, disk driver, and ETERNUS Disk storage system that were output right before the occurrence of the error, and restore.
ERROR: proxy: failed to establish BCV pair, STD=disk, BCV=disk, class=class
Explanation
Error occurred while establishing a BCV pair between the proxy group proxy and the master group.
"STD" is the disk name of the standard device, "BCV" is the disk name of the BCV device, and "class" is the name of the class to which the standard and BCV devices belong.
Resolution
Identify the cause by referring to log messages previously output on the GDS, disk driver or Dell EMC storage units, and promptly recover the disk.
ERROR: proxy: failed to cancel BCV pair, STD=disk, BCV=disk, class=class
Explanation
Error occurred while canceling a BCV pair between the proxy group proxy and the master group.
"STD" is the disk name of the standard device, "BCV" is the disk name of the BCV device, and "class" is the name of the class to which the standard and BCV devices belong.
Resolution
Identify the cause by referring to log messages previously output on the GDS, disk driver or Dell EMC storage units, and promptly recover the disk.
ERROR: proxy: failed to split BCV pair, STD=disk, BCV=disk, class=class
Explanation
Error occurred while splitting a BCV pair between the proxy group proxy and the master group.
"STD" is the disk name of the standard device, "BCV" is the disk name of the BCV device, and "class" is the name of the class to which the standard and BCV devices belong.
Resolution
Identify the cause by referring to log messages previously output on the GDS, disk driver or Dell EMC storage units, and promptly recover the disk.
ERROR: proxy: failed to re-establish BCV pair, STD=disk, BCV=disk, class=class
Explanation
Error occurred while re-establishing a BCV pair between the proxy group proxy and the master group.
"STD" is the disk name of the standard device, "BCV" is the disk name of the BCV device, and "class" is the name of the class to which the standard and BCV devices belong.
Resolution
Identify the cause by referring to log messages previously output on the GDS, disk driver or Dell EMC storage units, and promptly recover the disk.
ERROR: proxy: failed to establish SRDF pair, source=disk, target=disk, class=class
Explanation
Error occurred while establishing an SRDF pair between the proxy group proxy and the master group.
"source" is the name of the source disk, "target" is the name of the target disk, and "class" is the name of the class to which the source and target disks belong.
Resolution
Identify the cause by referring to log messages previously output on the GDS, disk driver or Dell EMC storage units, and promptly recover the disk.
ERROR: proxy: failed to cancel SRDF pair, source=disk, target=disk, class=class
Explanation
Error occurred while canceling an SRDF pair between the proxy group proxy and the master group.
"source" is the name of the source disk, "target" is the name of the target disk, and "class" is the name of the class to which the source and target disks belong.
Resolution
Identify the cause by referring to log messages previously output on the GDS, disk driver or Dell EMC storage units, and promptly recover the disk.
ERROR: proxy: failed to split SRDF pair, source=disk, target=disk, class=class
Explanation
Error occurred while splitting an SRDF pair between the proxy group proxy and the master group.
"source" is the name of the source disk, "target" is the name of the target disk, and "class" is the name of the class to which the source and target disks belong.
Resolution
Identify the cause by referring to log messages previously output on the GDS, disk driver or Dell EMC storage units, and promptly recover the disk.
ERROR: proxy: failed to re-establish SRDF pair, source=disk, target=disk, class=class
Explanation
Error occurred while re-establishing an SRDF pair between the proxy group proxy and the master group.
"source" is the name of the source disk, "target" is the name of the target disk, and "class" is the name of the class to which the source and target disks belong.
Resolution
Identify the cause by referring to log messages previously output on the GDS, disk driver or Dell EMC storage units, and promptly recover the disk.
ERROR: volume: failed to change slice status, class=class
Explanation
Changing the status of slices composing the volume volume of the class class failed. If ACM's inter-server replication function has normally started the EC or REC copying to volume, the equivalency of volume is not ensured.
Resolution
Collect investigation material and contact field engineers.
ERROR: volume: failed to change read policy, class=class
Explanation
The volume volume of the class class is registered as the replication destination volume of ACM's inter-server replication function. The read policy of volume is set as follows according to the inter-server replication processing state.
When volume is up and it is the EC/REC copy destination in equivalent status:
A slice that is read when a read request is issued from a higher level to volume is always a certain slice among ACTIVE slices composing volume.
When volume is in a status other than a.:
A slice that is read when a read request is issued from a higher level to volume is selected from ACTIVE slices composing volume one after the other.
If this message is output when changing the read policy to the status of a., reading volume may read improper data.
If this message is output when changing the read policy to the status of b., the load of reading certain slices composing volume may be higher.
Resolution
Collect investigation material and contact field engineers.
ERROR: no enough address space, details
Explanation
The OS malloc function returned an error.
Resolution
Check whether memory and a swap area are sufficient.
ERROR: volume: invalid volume type, class=class
Explanation
The volume volume of the class class is not of a volume type supported by ACM's inter-server replication function.
Resolution
Specify a volume of a supported type.
If volume is already registered in ACM replication volume information, the volume configuration may have been changed after the registration. In that event, with the relevant ACM commands, cancel the EC or REC copying to volume and remove volume from the ACM replication volume information.
To re-register volume in the ACM replication volume information, back up volume data as needed and then change the volume configuration.
ERROR: hangup detectedExplanation
Either a hang-up in the GDS daemon or the driver was detected.
The system panics after this message is output.
ERROR: val: interval must be integer
Explanation
The hang-up monitoring function can not be started because the value of monitoring interval (SDX_HCHK_INTERVAL) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is not a numerical value.
This message is output to the log file of SMF /var/svc/log/milestone-fjsvsdxhealth:default.log. However, it is not output to the log file (sdxservd.log) of daemon, log file of syslogd and the console indicated in "E.3 Daemon Messages."
Resolution
Refer to "How to change parameters" in "8.5 Hang-up Monitoring Function" in order to edit the value configured in SDX_HCHK_INTERVAL of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Cancel maintenance state of the service with the following command.
# svcadm clear svc:/milestone/fjsvsdxhealth:default |
Check that the service is in online state with the following command.
# svcs svc:/milestone/fjsvsdxhealth:default |
ERROR: val: too small interval
Explanation
The hang-up monitoring function can not be started because the value of monitoring interval (SDX_HCHK_INTERVAL) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is smaller than the allowed value.
This message is output to the log file of SMF /var/svc/log/milestone-fjsvsdxhealth:default.log. However, it is not output to the log file (sdxservd.log) of daemon, log file of syslogd and the console indicated in "E.3 Daemon Messages."
Resolution
Refer to "How to change parameters" in "8.5 Hang-up Monitoring Function" in order to edit the value configured in SDX_HCHK_INTERVAL of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Cancel maintenance state of the service with the following command.
# svcadm clear svc:/milestone/fjsvsdxhealth:default |
Check that the service is in online state with the following command.
# svcs svc:/milestone/fjsvsdxhealth:default |
ERROR: val: too large interval
Explanation
The hang-up monitoring function can not be started because the value of monitoring interval (SDX_HCHK_INTERVAL) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is larger than the allowed value.
This message is output to the log file of SMF /var/svc/log/milestone-fjsvsdxhealth:default.log. However, it is not output to the log file (sdxservd.log) of daemon, log file of syslogd and the console indicated in "E.3 Daemon Messages."
Resolution
Refer to "How to change parameters" in "8.5 Hang-up Monitoring Function" in order to edit the value configured in SDX_HCHK_INTERVAL of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Cancel maintenance state of the service with the following command.
# svcadm clear svc:/milestone/fjsvsdxhealth:default |
Check that the service is in online state with the following command.
# svcs svc:/milestone/fjsvsdxhealth:default |
ERROR: val: criterion must be integer
Explanation
The hang-up monitoring function can not be started because the value of conclusion time (SDX_HCHK_CRITERION) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is not a numerical value.
This message is output to the log file of SMF /var/svc/log/milestone-fjsvsdxhealth:default.log. However, it is not output to the log file (sdxservd.log) of daemon, log file of syslogd and the console indicated in "E.3 Daemon Messages."
Resolution
Refer to "How to change parameters" in "8.5 Hang-up Monitoring Function" in order to edit the value configured in SDX_HCHK_CRITERION of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Cancel maintenance state of the service with the following command.
# svcadm clear svc:/milestone/fjsvsdxhealth:default |
Check that the service is in online state with the following command.
# svcs svc:/milestone/fjsvsdxhealth:default |
ERROR: val: too small criterion
Explanation
The hang-up monitoring function can not be started because the value of conclusion time (SDX_HCHK_CRITERION) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is smaller than the allowed value.
This message is output to the log file of SMF /var/svc/log/milestone-fjsvsdxhealth:default.log. However, it is not output to the log file (sdxservd.log) of daemon, log file of syslogd and the console indicated in "E.3 Daemon Messages."
Resolution
Refer to "How to change parameters" in "8.5 Hang-up Monitoring Function" in order to edit the value configured in SDX_HCHK_CRITERION of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Cancel maintenance state of the service with the following command.
# svcadm clear svc:/milestone/fjsvsdxhealth:default |
Check that the service is in online state with the following command.
# svcs svc:/milestone/fjsvsdxhealth:default |
ERROR: val: too large criterion
Explanation
The hang-up monitoring function can not be started because the value of conclusion time (SDX_HCHK_CRITERION) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is larger than the allowed value.
This message is output to the log file of SMF /var/svc/log/milestone-fjsvsdxhealth:default.log. However, it is not output to the log file (sdxservd.log) of daemon, log file of syslogd and the console indicated in "E.3 Daemon Messages."
Resolution
Refer to "How to change parameters" in "8.5 Hang-up Monitoring Function" in order to edit the value configured in SDX_HCHK_CRITERION of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Cancel maintenance state of the service with the following command.
# svcadm clear svc:/milestone/fjsvsdxhealth:default |
Check that the service is in online state with the following command.
# svcs svc:/milestone/fjsvsdxhealth:default |
ERROR: interval val isn't larger than criterion val
Explanation
The hang-up monitoring function can not be started because the value of conclusion time (SDX_HCHK_CRITERION) of hang-up monitoring function configured in the GDS settings file /etc/opt/FJSVsdx/sdx.cf is greater than or equal to the value of monitoring interval (SDX_HCHK_INTERVAL).
This message is output to the log file of SMF /var/svc/log/milestone-fjsvsdxhealth:default.log. However, it is not output to the log file (sdxservd.log) of daemon, log file of syslogd and the console indicated in "E.3 Daemon Messages."
Resolution
Refer to "How to change parameters" in "8.5 Hang-up Monitoring Function" in order to edit the value configured in either of SDX_HCHK_CRITERION or SDX_HCHK_INTERVAL of GDS settings file /etc/opt/FJSVsdx/sdx.cf.
Cancel maintenance state of the service with the following command.
# svcadm clear svc:/milestone/fjsvsdxhealth:default |
Check that the service is in online state with the following command.
# svcs svc:/milestone/fjsvsdxhealth:default |