3par check health command

[haku1]

Hello,

I would like to ask about the checkhealth command.

The following options are available for 3PAR OS 3.3.1 MU5 and later versions.
checkhealth -pelcheck -d cabling

My question is below.
(1) Focusing only on cabling, what is the difference in the results of the commands below?
checkhealth -pelcheck -d cabling
checkhealth -svc -d cabling
checkhealth -full -d cabling
I would like to know if they all have the same effect.

(2)The following commands cannot be used with earlier than 3PAR OS 3.3.1 MU5.
checkhealth -pelcheck -d cabling

Is there an alternative command for the above?

(3)The following commands cannot be done.
checkhealth -pelmon -d cabling 0:0:1

I tried with 3PAR OS less than 3.3.1 MU5 and got an error.
Invalid argument: "-pelmon"

What is the alternative command for the above in 3PAR OS 3.3.1 MU1?

(4) Focusing only on cabling, what is the difference in the results of the commands below?
checkhealth -pelmon -d cabling
checkhealth -svc -d cabling
checkhealth -full -d cabling

Best Regards,

[Mahesh202]

Hi haku1

1.The difference of the commands is as follows:

• checkhealth -pelcheck -d cabling: This command checks the cabling health by verifying the cable connections between nodes and between controllers within a node. It checks the cable lengths, types, and connectivity to ensure that they are within specifications.
• checkhealth -svc -d cabling: This command checks the cabling health by verifying the cabling between the Service Processor (SP) and the nodes. It checks the cable lengths, types, and connectivity to ensure that they are within specifications.
• checkhealth -full -d cabling: This command checks the cabling health by performing a comprehensive check of all the cabling in the system, including node-to-node cabling, controller-to-disk enclosure cabling, and SP-to-node cabling. It checks the cable lengths, types, and connectivity to ensure that they are within specifications.
Therefore, while all three commands check the cabling health, they focus on different types of cabling and have different levels of coverage.

2. The checkhealth -pelcheck -d cabling command was introduced in 3PAR OS 3.3.1 MU5 and is not available in earlier versions. There is no alternative command for this specific check in earlier versions.

3. The -pelmon option for the checkhealth command was introduced in 3PAR OS 3.3.1 MU5. In 3PAR OS 3.3.1 MU1, you can use the following command to monitor the cabling on disk enclosure 0, port 1:
checkhealth -svc -d cabling -c 0:0:1

4. The difference in the results of the commands is as follows:

• checkhealth -pelmon -d cabling: This command monitors the cabling health by continuously checking the cable connections between nodes and between controllers within a node. It checks for any changes in cable lengths, types, and connectivity to ensure that they are within specifications.
• checkhealth -svc -d cabling: This command checks the cabling health by verifying the cabling between the Service Processor (SP) and the nodes. It checks the cable lengths, types, and connectivity to ensure that they are within specifications.
• checkhealth -full -d cabling: This command checks the cabling health by performing a comprehensive check of all the cabling in the system, including node-to-node cabling, controller-to-disk enclosure cabling, and SP-to-node cabling. It checks the cable lengths, types, and connectivity to ensure that they are within specifications.
Therefore, the checkhealth -pelmon -d cabling command is focused on continuous monitoring of cabling health, while the other commands are one-time checks that focus on different types of cabling and have different levels of coverage.

Regards
Mahesh.

[haku1]

@Mahesh202 

Hi Mahesh202,

>3. The -pelmon option for the checkhealth command was introduced in 3PAR OS 3.3.1 MU5. In 3PAR OS 3.3.1 MU1, you can use the following command to monitor the cabling on disk enclosure 0, port 1:
>checkhealth -svc -d cabling -c 0:0:1

An error occurs even if it is executed in 3.3.2 (MU1).
What version is "checkhealth -pelmon -d cabling" command available?

Below are the results I verified.
cli% showversion
Release version 3.3.2 (MU1)
Patches: P04
cli% checkhealth -pelmon -d cabling
Invalid argument: "-pelmon"

cli% showversion
Release version 3.3.1 (MU3)
Patches: P50,P58,P77,P91,P92,P97,P109,P114,P120,P128
cli% checkhealth -pelmon -d cabling
Checking cabling
The following components are healthy: cabling

cli% showversion
Release version 3.3.1 (MU1)
Patches: P09,P11,P18
cli% checkhealth -pelmon -d cabling
Invalid argument: "-pelmon"

My question is based on PEAK0083's information.
1. Run "checkhealth -pelmon -d cabling <2:1:2>" for more information about the alert For MU5 and later, use "checkhealth -pelcheck -d cabling".

I have verified the above description, but I am asking because the command resulted in an error.
As verified above, the "checkhealth -pelmon -d cabling" command may not work even if it is less than MU5.
I'm looking for an alternative command.

Is "checkhealth -pelmon -d cabling <2:1:2>" command be included in the checkhealth -full -d cabling?

>2. The checkhealth -pelcheck -d cabling command was introduced in 3PAR OS 3.3.1 MU5 and is not available in earlier versions. There is no alternative command for this specific check in earlier versions.

PEAK0083 states that the "checkhealth -pelmon -d cabling" and "checkhealth -pelcheck -d cabling" commands have the same result.

Best Regards,

[Vinky_99 · Accepted solution]

@haku1 

Good day! 

The 'checkhealth' command in HPE 3PAR storage systems is used to check the health and status of various components and subsystems within the storage system. Let me address your questions one by one:

(1) Difference between the commands with the "-d cabling" option:

>> checkhealth -pelcheck -d cabling

This command specifically checks the cabling between Persistent Ports (P-Ports) and the associated drive enclosures. It focuses on the cabling health for the Persistent Ports.

>> checkhealth -svc -d cabling

The -svc option is not typically used to check cabling health directly. This command performs a system-wide health check but doesn't specifically target cabling. It provides a more general health assessment.

>> checkhealth -full -d cabling

* The -full option is a comprehensive health check that includes checking various subsystems, including cabling, among others. It provides a more detailed health assessment compared to the others.

* So, the key difference is in the level of detail and scope of the health check. The first command (-pelcheck) specifically focuses on Persistent Port cabling, while the other two commands provide broader health assessments.

(2) Alternative command for checkhealth -pelcheck -d cabling in versions earlier than 3PAR OS 3.3.1 MU5:

>> Unfortunately, there may not be a direct alternative command for checking Persistent Port cabling health in versions earlier than 3.3.1 MU5. This specific functionality may not be available in older firmware versions, and you may need to rely on other methods or tools to check cabling health.

(3) Alternative command for checkhealth -pelmon -d cabling 0:0:1 in 3PAR OS 3.3.1 MU1:

>> It appears that the -pelmon option is not recognized in 3PAR OS 3.3.1 MU1. This might be a feature introduced in a later firmware version. In older versions like 3.3.1 MU1, you might not have a direct alternative for monitoring Persistent Ports in the same way. You may need to rely on other diagnostic tools or methods available in that version.

(4) Difference between the commands with the "-d cabling" option in terms of cabling health:

>> checkhealth -pelmon -d cabling

This command is intended to monitor the health of Persistent Ports and their cabling specifically. It focuses on monitoring these ports for issues.

>> checkhealth -svc -d cabling

As mentioned earlier, the -svc option is a more general system health check and may not specifically focus on cabling health. It provides a broader health assessment.

>> checkhealth -full -d cabling

Similar to the -svc option, the -full option is a comprehensive health check that includes cabling as part of its assessment but is not solely focused on it.

In summary, the key difference is the focus of the command. The -pelmon option is intended for monitoring Persistent Ports, while the other two provide broader health assessments with varying levels of detail.

I hope this helps! Let me know