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
Configuring static routes on a NetBackup Flex Scale cluster
You can configure static routes on a NetBackup Flex Scale cluster to communicate with remote clients who are on a different subnet, if the default route is not suitable.
A static route is a normal Linux route which appears in the output of the ip route show command on the Linux server. You must specify the destination IP address, netmask, gateway IP and device to configure the new route. Once you configure static routes for the cluster nodes and NetBackup services, the NetBackup services can reach clients who are part of another data network.
You can view, add and delete static routes using both the GUI and RESTful APIs.
You can manage static routes using the NBFS GUI by navigating to
> > .To add a new static route
- In the Network > Static routes page, Click Add.
- In the Add static route window, specify the destination IP address, netmask, gateway IP and device. Click Save.
Note:
You can only add one static route at a time.
- The newly added static route will be visible in the list of static routes displayed.
You can either delete a specific static route or delete multiple static routes at the same time.
To remove a particular static route, in the static route row, click on the vertical ellipsis button from the right side of the UI and then select
.To remove multiple static routes, select all the routes that you want to delete and select
. A confirmation dialog box appears. Select .
Notification events are raised when new static routes are added to the cluster or when static routes are deleted from the cluster.
The following RESTful APIs are available to configure and manage the static routes:
POST /api/appliance/v1.0/network/static-routes: Add a static route to the network configuration.
GET /api/appliance/v1.0/network/static-routes: Get the available static route.
PATCH /api/appliance/v1.0/network/static-routes: Specify the static routes entries that needs to be deleted.
GET /api/appliance/v1.0/tasks/{taskId}: Get the progress of add/delete static routes operations
GET /api/appliance/v1.0/network/interfaces: Get the list of public device interfaces