I've recently encountered an issue that has me stumped and I'm curious as to what people have run into....looking at you !
The Indeni platform runs the following command on all the PAN devices to check if its drives or partitions have any issues.
ipaddress/api?type=op&cmd=<show><system><raid><detail></detail></raid></system></show>&key=${api-key}
Here is an example of the output of a PAN device that only has 1 disk in the RAID:
<response status="success"><result>
<drive_status>
<disk_id_1>Present</disk_id_1>
<disk_id_2>Missing</disk_id_2>
</drive_status>
<overall_raid_status>Good</overall_raid_status>
<partition_status>
<panrepo>
<drive_state>clean, degraded</drive_state>
<drive_id_1>active sync</drive_id_1>
</panrepo>
<panlogs>
<drive_state>clean, degraded</drive_state>
<drive_id_1>active sync</drive_id_1>
</panlogs>
<sysroot1>
<drive_state>clean, degraded</drive_state>
<drive_id_1>active sync</drive_id_1>
</sysroot1>
<sysroot0>
<drive_state>clean, degraded</drive_state>
<drive_id_1>active sync</drive_id_1>
</sysroot0>
<maint>
<drive_state>clean, degraded</drive_state>
<drive_id_1>active sync</drive_id_1>
</maint>
<pancfg>
<drive_state>clean, degraded</drive_state>
<drive_id_1>active sync</drive_id_1>
</pancfg>
<swap>
<drive_state>clean, degraded</drive_state>
<drive_id_1>active sync</drive_id_1>
</swap>
</partition_status>
</result></response>
After we run the command, we parse for the value of drive_state to determine if the partition has issues. If the state is "clean", then the partition is considered as being "status up". However, it seems that the values flap a lot. What could be the reason why?
Attached is our IND script:
https://bitbucket.org/indeni/indeni-knowledge/raw/08fbf45b1e4fe700ded2a1c228733e4dcc3a0b9e/parsers/panw/panos/show-system-raid-detail.ind