Geoff, AIX has some parameters, buffer sizes and so on that can be set. In 4.3.3 there was only one buffer pool and set of parameters that applied to all nics, but in 5.3 these can be adjusted on a per nic basis.
Maybe you lost some tuning when you moved machines? Even if you cloned the old machine to the new one, the nic numbering may be different to what it was, so per nic tuning might no longer apply correctly. Etherchannel and other virtual nic layers may also complicate the picture. Steve Steven Harris AIX and TSM Admin. Brisbane Australia [I haven't gotten right into the nic parameters because I'd have to study them intently for at least a week - I regard comms as a black art and have no desire to become a practitioner :) ] -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Gill, Geoffrey L. Sent: Saturday, 9 September 2006 2:50 AM To: [email protected] Subject: [ADSM-L] Gig utilization during backups I'd like to get some input on what others see on their port utilization during heavy network traffic. With 350+ systems backing up to a single TSM server I'm curious as to why we see only about 50% utilization on the GIG port with max scheduled sessions set to 95. Sessions run extremely long compared to when they were on the old system. What have others seen their systems and what do you have set for max scheduled sessions? I still feel like this system, which has 4 CPU's is not nearly as fast at moving data than my 2 CPU system was and the setup is very similar. AIX 5.3 - TSM 5.3.3.0 - 4 CPU's - 4GB memory - Gig interface Thanks, Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.12.2/442 - Release Date: 8/09/2006
