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. Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide
  3. Appendix A. NetBackup BMR related appendices
  4. Network services configurations on BMR boot Server
  5. SUSE Linux Network configuration
Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide

SUSE Linux Network configuration

The following system prerequisites apply only to SUSE Linux systems:

  • Install the following RPM packages (unless they are installed already):

    • nfs-utils

    • dhcp-base

    • dhcp-server

    • inetd

    • tftp

  • Enable the tftp service by doing the following:

    • Edit the /etc/inetd.conf file and uncomment the tftp line.

    • Start the service by running the following command:

      /etc/init.d/inetd restart

  • Modify the /etc/dhcpd.conf file to define the networks it serves. You do not have to define host information; hosts are added and removed as needed by the Bare Metal Restore software. The following is an example configuration:

    log-facility local7;
    ddns-update-style none;
    ignore unknown-clients;
    subnet 10.10.5.0 netmask 255.255.255.0 {  
    default-lease-time            600;  
    max-lease-time                7200;  
    option domain-name            "example.com";  
    option broadcast-address      10.10.5.255;  
    option domain-name-servers    10.10.1.4,10.88.24.5;  
    option routers                10.10.5.1;
    }

    To verify the /etc/dhcpd.conffile syntax, restart the daemon and ensure that it starts successfully by running:

    /etc/init.d/dhcpd restart

Note:

DHCP server needs to be configured on Linux BMR boot server. Any existing DHCP server in the network cannot be used for Linux BMR network-based boot recovery. It is recommended to shut down any other DHCP server while Linux client is network booting over BMR boot server. If the client DHCP boot request goes to the other DHCP server, then network boot recovery fails. This is not a BMR limitation and instead the way this boot protocol works.

Feedback

Was this page helpful?
Previous

Red Hat Enterprise Linux network configuration

Next

Solaris Network configuration

Feedback

Was this page helpful?