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 quad-port NIC
This topic describes the process of replacing the NIC quad port on an HPE server node.
Verify if the cables are unplugged or faulty. After removing cable from quad-port NIC node state in the UI shows Unhealthy.
The eth1 network interface state is shown unplugged in the UI. To view the link status, navigate to in the NetBackup Flex Scale infrastructure UI.
The network status for the public network is shown unhealthy. Navigate to the dashboard page of the UI:
In the iLO remote console, adapter1 slot 3 status is shown as link down.
An event notifying that the eth1 network interface is in faulted state is shown on the page of the UI:
If you encounter these issues, there might be a problem with the cables connection or the quad-port. To isolate the issue, first tighten the cable connections. If you face the same issue, replace the cables and try again. If the issue persists it implies that the port is faulty. Contact Veritas TSE to replace the faulty quad-port NIC.
Note the MAC address of the network interface. After the quad-port NIC is replaced, the MAC address will change:
Before an HPE representative can replace the quad-port NIC, you must shut down the node.
To shut down the node:
- Sign in to the NetBackup Flex Scale infrastructure management UI and navigate to Monitor > Infrastructure > Nodes.
- On the node where the failure occurred, click the Actions menu (vertical ellipsis) from the right side of the row in the UI and click Shutdown node.
- Confirm that the node is shut down successfully. In the UI, you can view the notification at the top of the page. In the iLO remote console, wait until the system shows the System halted message.
- Shut down the node. Press the Power button on the front panel of the server or from the iLO remote console use the Server Power > Press and Hold option.
The HPE representative replaces the quad-port NIC.
After the hardware vendor notifies you that the hardware component is replaced, verify that the issue is resolved.
To verify that the issue is resolved, complete the following steps:
- Restart the node from the iLO remote console using the Power > Momentary Press option.
The green color power symbol indicates that the node has started.
- As the port is changed physically, the MAC address is also changed, which results in the following cases:
The node status is shown unhealthy in the UI:
The eth1 network interface state is shown unplugged in the UI. To view the link status, navigate to Infrastructure > Hardware > Network Card in the NetBackup Flex Scale infrastructure UI.
In the iLO remote console, adapter1 slot 3 status is shown as link down:
An event notifying that the eth1 network interface is in faulted state is shown on the Settings > Events page of the UI:
- If you are on version 3.0 or earlier, complete the following steps to bring up eth1. You need to elevate to root access to perform these steps.
SSH to another cluster node:
ssh primary@node_name
su
Enter the maintenance password.
Open the
/etc/sysconfig/network-scripts/ifcfg-eth1file and you will see old MAC ID in the HWADDR field. Change the MAC ID in the HWADDR field to the new MAC ID.Run following commands:
ifdown eth1
ifup eth1
At this point, eth1 is up.
- Verify that the node status is shown healthy in the UI:
- Verify that the eth1 link state has changed to Plugged:
- The public network status is shown healthy:
- Verify that Adapter 1 slot 3 link status is shown OK:
- Verify that the changed MAC ID can be seen in the system hardware-health and in ifconfig eth1 output: