4-14 Dell PowerVault 720N, 740N, and 760N System Administrator and Command Reference Guide
The file consists of lines with the following format:
JDWHZD\PHWULF
where gateway is the name or the IP address of a default router and metric is a pref-
erence indicator, which ranges from 1 (highest) to 15 (lowest) as shown below.
NOTE: Each entry for such a default router must have an IP address that belongs to
the IP subnet of one of the interfaces configured for the filer.
+RZWKH)LOHU5HSOLHVWR5HTXHVWV
The following list describes how the filer uses its interfaces to respond to different
types of packets.
NFS-over-UDP requests: The filer does not use the conventional IP routing mecha-
nisms to reply to NFS-over-UDP requests. The filer sends the response on the
network interface on which the request was received to the same address that gener-
ated the request. For example, the filer named filer uses the filer-e1 interface to
send packets in response to NFS requests received on the filer-e1 interface.
This way of handling NFS-over-UDP requests enables you to attach multiple interfaces
of the filer to networks with the same IP subnetwork number while keeping NFS-
over-UDP traffic isolated to the appropriate physical networks.
Because of this scheme, it is possible that NFS-over-UDP responses might be
returned through a different path than you might expect from an examination of the IP
routing table using netstat -r. This scheme generally works well, although it can
result in different routes than expected if your environment contains one-way routes.
For example, the IP packets might not be routed as you intended if you configured the
network so that the IP traffic from host1 to host2 is routed through router1 and the IP
traffic from host2 to host1 is routed through router2.
NFS-over-TCP, -CIFS, and -HTTP requests: The filer tries to return NFS-over-TCP and
-HTTP traffic over the interface on which the traffic was received. However, there are
exceptions. For example, if the filer experiences excessive queuing to a response or
experiences a time-out followed by a retransmit, the filer routes the traffic by using
conventional IP routing table lookups. If the filer has multiple interfaces attached to
networks with the same IP network number, the filer uses the first interface it finds
with that number to send the responses.
IP-based traffic other than NFS and HTTP requests: For other types of traffic, for
example, traffic generated by telnet, rsh, and ping, the filer uses IP routing table
lookups and routing. If the filer has multiple interfaces attached to networks with the
same IP network number, the filer uses the first interface it finds with that number to
send the responses.
*DWHZD\ 0HWULF
192.9.200.10 1
eng_gateway 2