We finally figured out that ehterchannel was not doing what we wanted last week, so we re-configured our gigabit ethernet adapters as individual adapters on six separate internal networks. Now I've run into another interesting observation.
I can fire up one interface from a client system to my TSM server with the ftp process coverd in the tuning doc (from /dev/zero to /dev/null) and get 110 MB per second over the interface. If I then fire up the second interface on the same client to the TSM server -- I get 110 MB/sec as an aggregate; both interfaces run at 55 to 58 MB/sec. This is not a TSM server constraint; I can get all six interfaces running at 110 MB/sec if I run one process on each of six clients. So it's a client tuning issue -- and not a problem with input from /dev/zero, as these results mirror my TDP/R3 backups this weekend. Any suggestions on what knobs to tweak? Better yet, any suggestions on how to determine what resource constraint I'm hitting? I'm beating my way through the various redbooks that cover network tuning, but this can be time-consuming. TIA Tom Kauffman NIBCO, Inc CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
