Managed File Replication Over a Specific Interface
Summary: Only Backups and Restores use ifgroups until DDOS 5.7. This document is a workaround.
Symptoms
The management interface will get flooded with replication traffic limiting access using the interface.
Cause
Resolution
WORKAROUND
If the DNS is pointing to the management interface, follow the next steps in the document.
If the DNS points to the specific interface (i.e. a 10G interface), add a route (step 3)
To verify the DNS settings perform the following:
net show dns (verify that the DNS servers are correct)
net lookup <hostname>
1. Create a local host entry that points the hostname to the specified interface on both source and destination.
(Note: The gateway for the routing statement must be one that the server can communicate with).
- SOURCE -
net hosts add <Destination IP> <Destination FQDN> <Destination shortname>
Example:
net hosts add 192.168.1.150 dest.emc.com dest- DESTINATION -
net hosts add <Source IP> <Source FQDN> <Source shortname>
Example:
net hosts add 10.10.5.150 source.emc.com source
2. Run a "net host show" to verify the changes have been implemented correctly.
3. Create a static route that points the hostname to the desired interface on both source and destination.
See Data Domain: Adding a Static Route for specific information about adding routes to the DD. The example below is for a non-HA and DD OS 6.0 and newer.
- SOURCE -
route add -host <destination IP> gw <specified gateway> <desired source interface>
Example:
route add host 192.168.1.150 gw 10.10.5.1 dev eth0a- DESTINATION -
route add -host <source IP> gw <specified gateway> <desired destination interface>
Example:
route add host 10.10.5.150 gw 192.168.1.1 dev eth0b4. Run the "route show table" and verify that the entries are correct.
Example:
route show table
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.150 10.10.5.1 255.255.255.0 U 0 0 0 eth0a
route show table
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.10.5.150 192.168.1.1 255.255.255.0 U 0 0 0 eth0b
5. Run a test replication job from the backup application
6. Run an iostat 5 (or a specified number of seconds) and monitor for traffic going over the configured interface:
iostat 2
11/10 15:48:35
INTERVAL: 2 secs
"-" indicates that system is busy and unable to get recent data.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
CPU |State |NFS |CIFS |Net |Disk |NVRAM |Repl
aggr aggr| | | |eth4a eth4a eth4b eth4b eth4c eth4c eth4d eth4d eth5a eth5a eth5b eth5b eth5c eth5c eth5d eth5d ethMa ethMa ethMb ethMb ethMc ethMc ethMd ethMd| | aggr aggr|
busy max| | ops/s load data in data out|ops/s in out| in out in out in out in out in out in out in out in out in out in out in out in out| read write busy| read write| in out
% %|CDBVMSFIR| % MB/s MB/s| MB/s MB/s| MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s MB/s| KiB/s KiB/s %| KiB/s KiB/s| KB/s KB/s
---- ---- --------- ------- ----- ------- -------- ----- ------- ------- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ------- ------- ---- ------- ------- ------- -------
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
36 36 - 411 0 16.75 0.11 - - - 7.22 0 0 0 0 0 0 0 10.47 0.01 0 0 0 0 0 0 3.24 123 0 0 0 0 0 0 2993967 794450 - - - 1167 116670
36 39 C VM 401 0 16.14 0.11 2 0 0 6.97 0 0 0 0 0 0 0 10.37 0.01 0 0 0 0 0 0 3.20 123 0 0 0 0 0 0 2875004 762850 - - - 1149 117079
28 37 C VM 303 0 10.81 0.11 2 0 0 4.67 0 0 0 0 0 0 0 9.03 0 0 0 0 0 0 0 2.73 123 0 0 0 0 0 0 1490253 400502 - - - 904 121288
35 44 C VM 373 0 19.62 0.09 0 0 0 6.87 0 0 0 0 0 0 0 8.37 0 0 0 0 0 0 0 2.80 123 0 0 0 0 0 0 3099676 836494 - - - 945 115731
44 48 C VM 405 0 17.53 0.10 0 0 0 8.11 0 0 0 0 0 0 0 12.10 0 0 0 0 0 0 0 3.14 123 0 0 0 0 0 0 5252756 1235990 - - - 1219 124147
42 49 C VM 373 0 15.89 0.10 0 0 0 7.54 0 0 0 0 0 0 0 10.61 0 0 0 0 0 0 0 3.27 123 0 0 0 0 0 0 4624478 1036232 - - - 1194 115686
33 40 C VM 341 0 12.98 0.10 0 0 0 6.22 0 0 0 0 0 0 0 9.19 0 0 0 0 0 0 0 3.76 123 0 0 0 0 0 0 1257580 361429 - - - 1699 120311
28 41 C VM 385 0 21.53 0.11 0 0 0 6.47 0 0 0 0 0 0 0 10.39 0 0 0 0 0 0 0 3.50 123 0 0 0 0 0 0 2134021 640822 - - - 1508 116681
41 44 C VM 360 0 18.58 0.08 0 0 0 7.75 0 0 0 0 0 0 0 14.07 0 0 0 0 0 0 0 3.03 123 0 0 0 0 0 0 3884156 980316 - - - 1081 122749
43 49 C VM 345 0 15.06 0.08 0 0 0 7.88 0 0 0 0 0 0 0 11.23 0 0 0 0 0 0 0 2.99 123 0 0 0 0 0 0 3717975 903659 - - - 1157 120974
7. If the specified interface's traffic increases, a workaround has been implemented.
8. If the traffic is still going over the management interface, review the settings on the system or engage a Data Domain Networking Specialist.