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
- About Universal Shares
- Node and disk management
- Adding a node to the cluster using the NetBackup Flex Scale web interface
- License management
- Managing the Fibre Channel ports
- Requirements
- Managing hardware vendor packages
- User management
- NetBackup Flex Scale network management
- Bonding operations
- Data network configurations
- Network configuration on plain device (eth5)
- Network configuration on bonded interfaces (bond0 on eth5 and eth7)
- NetBackup Flex Scale infrastructure monitoring
- Resiliency in NetBackup Flex Scale
- EMS server configuration
- Site-based disaster recovery in NetBackup Flex Scale
- Performing disaster recovery using RESTful APIs
- NetBackup Flex Scale security
- STIG overview for NetBackup Flex Scale
- FIPS overview for NetBackup Flex Scale
- Support for immutability in NetBackup Flex Scale
- Deploying external certificates on NetBackup Flex Scale
- Configuring multifactor authentication
- Single Sign-On (SSO)
- Appendix A. Maintenance procedures for HPE servers
- Appendix B. Configuring NetBackup optimized duplication
- Appendix C. Disaster recovery terminologies
- Appendix D. Configuring Auto Image Replication
Replacement procedure for a Fibre Channel card for a node that is not in a cluster
Use the following procedure to replace a Fibre Channel card when the NetBackup Flex Scale ISO is installed on the node but it is not a part of the cluster.
Shut down the node from the iLO remote console of the node by using the
option.The HPE representative replaces the Fibre Channel card for 5561 model.
The HPE representative replaces the Fibre Channel card for 5551 model.
After the hardware vendor notifies you that the hardware component is replaced, verify that the issue is resolved.
Power on the node from the iLO remote console by using the
option. The green color power symbol indicates that the node has started.After restarting the node, enable the Fibre Channel BOM configuration from the Appliance Node-level CLI.
To enable Fibre Channel BOM:
- Use SSH Login to Node level CLI using the eth1 IP address of the node
- Run the following command:
support bom-conf get
- To update this
bom-config.json
file open an NFS share by running the following command:system software share open
- Mount the above open NFS share on any available Linux Client by using the Linux command:
mount -t nfs ipaddressorfqdn:/system/inst/patch/incoming /mnt
where ipaddressorfqdn is the IP address or the FQDN that was displayed when you ran the system software share open command.
The
/mnt
location can be changed to the required location for mounting the NFS share.The
bom-config.json
file is copied to the/mnt
location. - Set the FC-ENABLE key value to 1. Open the
bom-config.json
using the vim command:vim bom-config.json
Change the FC-ENABLE key to 1 and save the file. the updated file should look similar to shown below:
- Log in to the Appliance Node-level CLI again using the eth1 IP address of the node.
- Run the following command to update configuration:
support bom-conf update
- After the file is updated, close the open NFS share:
system software share close
After you enable the Fibre Channel BOM, create the zoning again with new Fibre Channel card WWPN (World Wide Port Name).