Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Configuring an FTP server
- Using Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VII. Configuring cloud storage
- Section VIII. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Compressing files
- Section X. Reference
Configuring routing tables
To display the routing tables of the nodes in the cluster
- To display the routing tables of the nodes in the cluster, enter the following:
Network> ip route show [nodename]
where nodename is the node whose routing tables you want to display. To see the routing table for all of the nodes in the cluster, enter all.
For example:
Network> ip route show all
Destination |
Displays the destination network or destination host for which the route is defined. |
Gateway |
Displays a network node equipped for interfacing with another network. |
Genmask |
Displays the netmask. |
Flags |
The flags are as follows: U - Route is up H - Target is a host G - Use gateway |
MSS |
Displays maximum segment size. The default is 0. You cannot modify this attribute. |
Window |
Displays the maximum amount of data the system accepts in a single burst from the remote host. The default is 0. You cannot modify this attribute. |
irtt |
Displays the initial round trip time with which TCP connections start. The default is 0. You cannot modify this attribute. |
Iface |
Displays the interface. On UNIX systems, the device name lo refers to the loopback interface. |
To add to the route table
- To add a route entry to the routing table of nodes in the cluster, enter the following:
Network> ip route add nodename ipaddr netmask | prefix via gateway [dev device]
nodename
Specifies the node to whose routing table the route is to be added.
To add a route path to all the nodes, use
all
in the nodename field.If you enter a node that is not a part of the cluster, an error message is displayed.
ipaddr
Specifies the destination of the IP address.
You can specify either an IPv4 address or an IPv6 address.
If you enter an invalid IP address, then a message notifies you before you fill in other fields.
netmask
Specifies the netmask associated with the IP address that is entered for the ipaddr field.
Use a netmask value of 255.255.255.255 for the netmask to add a host route to ipaddr.
prefix
Specifies the prefix for the IPv6 address. Accepted ranges are 0-128 integers.
via
This is a required field. You must type in the word.
gateway
Specifies the gateway IP address used for the route.
If you enter an invalid gateway IP address, then an error message is displayed.
To add a route that does not use a gateway, enter a value of 0.0.0.0.
dev
Specifies the route device option. You must type in the word.
device
Specifies which Ethernet interface on the node the route path is added to. This variable is optional.
You can specify the following values:
any - Default
pubeth0 - Public Ethernet interface
pubeth1 - Public Ethernet interface
The Ethernet interface field is required only when you specify
dev
in the dev field.If you omit the dev and device fields, Veritas Access uses a default Ethernet interface.
To delete route entries from the routing tables of nodes in the cluster
- To delete route entries from the routing tables of nodes in the cluster, enter the following:
Network> ip route del nodename ipaddr netmask | prefix
nodename
Specify the node from which the route entry has to be deleted.
To delete the route entry from all nodes, use the
all
option in this field.ipaddr
Specifies the destination IP address of the route entry to be deleted.
You can specify either an IPv4 address or an IPv6 address.
If you enter an invalid IP address, a message notifies you before you enter other fields.
netmask
Specifies the IP address to be used. Netmask is used for IPv4 addresses.
prefix
Specifies the prefix for the IPv6 address. Accepted ranges are 0-128 integers.