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 Best Practices and Troubleshooting Guide
  3. Best practices
  4. Private network connectivity
NetBackup™ Flex Scale Best Practices and Troubleshooting Guide

Private network connectivity

NetBackup Flex Scale uses Avahi to discover the nodes in the private network. When you scan for the nodes that can be added to cluster, Avahi scans the private network and displays all the detected nodes in this network.

NetBackup Flex Scale uses IP address 172.16.0.0/19 for private network NICs by default. If IP from 172.16.0.0/19 are reserved by the company, change private IP addresses to other local network addresses, such as 192.168.x.x or other subnets such as 172.20.x.x.

To check private network connectivity:

  1. Use SSH and log in to the node using the default administrator credentials:

    username: admin

    password: P@ssw0rd

  2. Run the support elevate command to elevate to the bash prompt.

    To check if the private network is accessible, run the following command:

    /opt/IMAppliance/ansible/roles/avahi/bin/mdns-config | jq

    The following example shows the sample output for four nodes:

    [
      {
        "domain": "local",
        "hostname": "VTAS9031105",
        "ip": "172.1.2.3",
        "ipv6": "fd00::2"
      },
      {
        "domain": "local",
        "hostname": "VTAS9031104",
        "ip": "172.1.2.4",
        "ipv6": "fd00::3"
      },
      {
        "domain": "local",
        "hostname": "VTAS9031103",
        "ip": "172.1.2.5",
        "ipv6": "fd00::4"
      },
      {
        "domain": "local",
        "hostname": "VTAS9031102",
        "ip": "172.1.2.6",
        "ipv6": "fd00::1"
      }
     ]
  3. To verify all the nodes in the private network can be discovered, run the following command:

    avahi-browse -d local _discovery._sub._http._tcp -rt

    The following example shows the sample output. Ensure all the nodes in the private network are displayed.

site1-01:~ # avahi-browse -d local _discovery._sub._http._tcp -rt
+   eth4 IPv6 VTAS9031103                                   Web Site             local
+   eth4 IPv6 VTAS9031104                                   Web Site             local
+   eth4 IPv6 VTAS9031102                                   Web Site             local
+   eth4 IPv6 VTAS9031105                                   Web Site             local
+   eth4 IPv4 VTAS9031103                                   Web Site             local
+   eth4 IPv4 VTAS9031104                                   Web Site             local
+   eth4 IPv4 VTAS9031102                                   Web Site             local
+   eth4 IPv4 VTAS9031105                                   Web Site             local
=   eth4 IPv6 VTAS9031102                                   Web Site             local
   hostname = [VTAS9031102.local]
   address = [fd00::1]
   port = [12345]
   txt = []
=   eth4 IPv4 VTAS9031102                                   Web Site             local
   hostname = [VTAS9031102.local]
   address = [172.1.2.3]
   port = [12345]
   txt = []
=   eth4 IPv6 VTAS9031104                                   Web Site             local
   hostname = [VTAS9031104.local]
   address = [fd00::3]
   port = [12345]
   txt = []
=   eth4 IPv4 VTAS9031104                                   Web Site             local
   hostname = [VTAS9031104.local]
   address = [172.1.2.4]
   port = [12345]
   txt = []
=   eth4 IPv6 VTAS9031103                                   Web Site             local
   hostname = [VTAS9031103.local]
   address = [fd00::4]
   port = [12345]
   txt = []
=   eth4 IPv4 VTAS9031103                                   Web Site             local
   hostname = [VTAS9031103.local]
   address = [172.1.2.5]
   port = [12345]
   txt = []
=   eth4 IPv6 VTAS9031105                                   Web Site             local
   hostname = [VTAS9031105.local]
   address = [fd00::2]
   port = [12345]
   txt = []
=   eth4 IPv4 VTAS9031105                                   Web Site             local
   hostname = [VTAS9031105.local]
   address = [172.1.2.6]
   port = [12345]
   txt = []
site1-01:~ #

If the 172.16.x.x IP range is restricted in the customer's environment, you must change the IP addresses assigned to the private NICs.

Feedback

Was this page helpful?
Previous

Management network connectivity

Next

Configuring AutoSupport for the appliance

Feedback

Was this page helpful?