Veritas NetBackup™ Flex Scale Administrator's Guide
- Product overview
- Viewing information about the NetBackup Flex Scale cluster environment
- NetBackup Flex Scale infrastructure management
- User management
- Considerations for managing NetBackup Flex Scale users
- Adding users
- Changing user password
- Removing users
- Modifying user roles
- Considerations for configuring AD/LDAP
- Configuring AD server for Universal shares and Instant Access
- Configuring AD/LDAP servers for NetBackup services
- Configuring additional AD/LDAP servers for managing NetBackup services/Universal Shares/Instant Access
- Configuring AD/LDAP servers on clusters deployed with only media servers
- Directory services and certificate management
- Region settings management
- About NetBackup Flex Scale storage
- About Universal Shares
- Cloud bucket support for NetBackup Flex Scale
- Node and disk management
- NetBackup Flex Scale network cabling
- Adding a node to the cluster using the NetBackup Flex Scale web interface
- Adding a node using the REST APIs
- Replacing a node in a cluster
- Starting and stopping nodes
- Rebooting a node
- Adding an excluded node to the cluster
- Replacing a disk
- Adding an excluded disk to the cluster
- Viewing the disk sync status
- Viewing disk details
- Viewing node details
- Switching management console to another cluster node
- License management
- Stopping NetBackup service containers
- Starting NetBackup service containers
- Managing hardware vendor packages
- User management
- NetBackup Flex Scale network management
- About network management
- Modifying DNS settings
- About bonding Ethernet interfaces
- Bonding operations
- Configuring NetBackup Flex Scale in a non-DNS environment
- Data network configurations
- Choosing the correct input method for data network configuration
- Network configuration on plain device (eth5)
- Network configuration on VLAN (eth5)
- Network configuration on bonded interfaces (bond0 on eth5 and eth7)
- VLAN on bond of eth5 and eth7 (bond0)
- Network configuration on management interface (eth1)
- Network configurations for adding a partial data network
- Support for multiple VLAN when disaster recovery is configured
- Configuring static routes on a NetBackup Flex Scale cluster
- NetBackup Flex Scale infrastructure monitoring
- Resiliency in NetBackup Flex Scale
- EMS server configuration
- Site-based disaster recovery in NetBackup Flex Scale
- About site-based disaster recovery in NetBackup Flex Scale
- Configuring disaster recovery using GUI
- Clearing the host cache
- Automated NetBackup SLP management
- DNS key management
- Managing disaster recovery using GUI
- Performing disaster recovery using RESTful APIs
- Active-Active disaster recovery configuration
- NetBackup optimized duplication using Storage Lifecycle Policies
- NetBackup Flex Scale security
- STIG overview for NetBackup Flex Scale
- FIPS overview for NetBackup Flex Scale
- Managing the login banner
- Changing the password policy
- Support for immutability in NetBackup Flex Scale
- Authenticating users using digital certificates or smart cards
- About system certificates on NetBackup Flex Scale
- Deploying external certificates on NetBackup Flex Scale
- Troubleshooting
- Services management
- Audit logs
- Collecting logs for cluster nodes
- Troubleshooting NetBackup Flex Scale issues
- If cluster configuration fails (for example because an IP address that was already in use is specified) and you try to reconfigure the cluster, the UI displays an error but the configuration process continues to run
- Validation error while adding VMware credentials to NetBackup
- NetBackup Web UI incorrectly displays some NetBackup Flex Scale processes as failed
- Unable to create BMR Shared Resource Tree (SRT) on NetBackup Flex Scale Appliance
- NetBackup configuration files are not persistent across operations that require restarting the system
- Appendix A. Maintenance procedures for HPE servers
- Replacement procedure for a chassis fan
- Replacement procedure for power supply
- Replacement procedure for a single OS disk
- Replacement procedure for both OS disks on the management console node
- Replacement procedure for both OS disks on a non- management console node
- Replacement procedure for NVMe disks (SSDs)
- Replacement procedure for RAID controller
- Replacement procedure for an Integrated Lights-Out (iLO) port
- Replacement procedure for quad-port NIC
- Procedure for memory expansion (DIMMs)
- Replacement procedure for memory (DIMMs)
- Replacement procedure for Mellanox port
- Appendix B. Configuring NetBackup optimized duplication
- Appendix C. Disaster recovery terminologies
- Appendix D. Configuring Auto Image Replication
Replacement procedure for an Integrated Lights-Out (iLO) port
This topic describes the process of replacing the iLO port on an HPE server node. Each node has one iLO port.
The iLO port is configured with a default user name, password, and DNS name. The default information is on the serial label pull tab attached to the server. Use these values to access iLO remotely by using a web browser.
Verify if the iLO UI is accessible using the iLO host name. The following error is shown if the UI is not accessible.
Verify if the IP allocated to the iLO interface is reachable. The following error is shown if the IP is unreachable.
If you encounter these issues, there might be a problem with the cables connection or the iLO port. To isolate the issue, first tighten the cable connections and try accessing the iLO UI and the IP. If you face the same issue, replace the cables and try again. If the issue persists it implies that the iLO port is faulty. Contact Veritas TSE to replace the node with the faulty iLO port.
To replace the node:
- Check the node status in the NetBackup Flex Scale infrastructure management UI. The node is shown unhealthy and the node status is offline.
- Prepare the node for replacement:
Deploy ISO on the failed node where the OS disks were replaced.
Perform factory reset on that node from the node CLI by using the system factory-reset command.
Install vendor packages on the node:
Assign the node's old management IP address from node-level CLI:
set network interface ip=x.x.x.x netmask=x.x.x.x.x gateway=x.x.x.x.x
Create NFS share from node-level CLI to create the
/system/inst/patch/incomingdirectory:system software share open
From a remote Linux host, complete the following steps:
Mount NFS share on driver node # mount -t nfs [management IP]:/system/inst/patch/incoming/ /mnt
Run the cd /mnt command.
Download vendor packages that are complaint with your hardware platform from the Download Center on the Veritas Support website.
Install the vendor package by running the following command from the node-level CLI:
system install hw-vendor-packages
- From the NetBackup Flex Scale infrastructure management UI perform the replace node operation.
Scan for nodes. Click Scan for nodes to discover the nodes.
Select a node from the displayed list and replace the node. For the unhealthy node, click the Actions menu (vertical ellipsis) from the right side of the row in the UI, and click Replace node.
In the Replace node dialog box, select the node that you want to use to replace the unhealthy node and click Replace node.
- After the replace node operation completes successfully check the node status in the NetBackup Flex Scale infrastructure management UI. Navigate to Monitor > Infrastructure > Nodes. The node is online and shown healthy.
Click Dashboard and verify that all the NetBackup services are running.
After you replace the node, verify that the issue is resolved.
Plug in the cable in the iLO port and verify if the iLO UI is accessible using the iLO host name.
Verify that the IP address allocated to the iLO interface is reachable.