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 Release Notes
  3. Known issues
  4. Upgrade issues
  5. Gateway IP not visible in the GUI if a cluster is upgraded from version 3.2 or 3.2.100 to version 3.5.100 after an add gateway operation
NetBackup™ Flex Scale Release Notes

Gateway IP not visible in the GUI if a cluster is upgraded from version 3.2 or 3.2.100 to version 3.5.100 after an add gateway operation

If an add gateway operation is performed on a secondary data network on a NetBackup Flex Scale cluster version 3.2 or 3.2.100 and then an upgrade is performed from version 3.2 or 3.2.100 to version 3.5.100, the gateway IP address is not visible in the GUI after the upgrade. This happens because as part of the add gateway operation done on the 3.2 and 3.2.100 cluster, the gateway is not added to net_info_list.conf file.

Workaround:

There is no workaround for this issue.

Feedback

Was this page helpful?
Previous

Upgrade operations may fail on a NetBackup Flex Scale cluster on which only media servers are deployed when an upgrade is performed from version 3.2 or 3.2.100 to version 3.5.100

Next

UI issues

Feedback

Was this page helpful?