Eric,
you didn't tell us anything about the network layout. Let's play with some
assumptions:
-------------------- -----------------
| TSMClient | | TSM-Server |
| | | |
| 1-GB (1.1.1.1)/24 |---------(router)--------| x-GB (2.2.2.2) |
| | | | |
| 10-GB (1.1.1.2)/24 |----------| -----------------
--------------------
Depending on your default route, traffic not destined within your network
(1.1.1.x/24) will be routed via the adapter associated with the default route.
If you would like to send all traffic destined for the TSM-Server (2.2.2.2)
should go via the 10-GB Adapter, you will have to add a host-route defining
all traffic for 2.2.2.2 to go via 1.1.1.2 aka the 10-GB adapter and thus
ignoring the default route.
--
Michael Prix
On Thu, 2017-08-31 at 14:46 +0000, Loon, Eric van (ITOPT3) - KLM wrote:
> Hi guys!
> I have tested in the past with 10 Gb attached Linux clients and everything
> worked fine, but now we will add a 10 Gb card to a host which is already
> connected to 1 Gb. So this host has two possible paths to the server. How
> can I make sure the TSM client uses the 10 Gb adapter only? I read something
> about the TCPClientAddress parameter, but according to the manual that is
> only for the server to the client (restore), not for the client to the
> server (backup).
> Thanks for your help in advance!
> Kind regards,
> Eric van Loon
> Air France/KLM Storage Engineering
>
> ********************************************************
> For information, services and offers, please visit our web site: http://www.
> klm.com. This e-mail and any attachment may contain confidential and
> privileged material intended for the addressee only. If you are not the
> addressee, you are notified that no part of the e-mail or any attachment may
> be disclosed, copied or distributed, and that any other action related to
> this e-mail or attachment is strictly prohibited, and may be unlawful. If
> you have received this e-mail by error, please notify the sender immediately
> by return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
> ********************************************************
|