Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Flex Scale Administrator's Guide
  3. NetBackup Flex Scale infrastructure monitoring
  4. Monitoring hardware components
  5. Monitoring deviations in firmware, driver, and utilities
NetBackup™ Flex Scale Administrator's Guide

Monitoring deviations in firmware, driver, and utilities

If you plan to leverage your own hardware instead of the out of the box appliance, you can monitor the firmware, driver, and utility versions that are installed on your hardware and report deviations, if any, with Veritas-supported versions.

You can use the following commands to monitor the deviation:

  • show hardware-health node component=Firmware

  • show hardware-health node component=Driver

  • show hardware-health node component=Utility

The following example shows the output that is displayed when you run the show hardware-health node component=Driver command on an HPE 5551 model:

The Status column of the firmware, driver or utility output shows one of the following values:

  • Latest Version: The latest supported version is installed. No action is required.

  • Update Available: You must contact Veritas Support to get the required update package.

  • Unsupported Version: The detected version is not supported by Veritas and you must contact Veritas Support. An alert is generated if an unsupported version is detected.

  • Fail: The service that detects the versions did not run. Wait for a maximum of 24 hours for the next service cycle to run.

Feedback

Was this page helpful?
Previous

Monitoring hardware components

Next

Performing health check for the cluster

Feedback

Was this page helpful?