Hi Jim, All good responses so far.
We have a similar situation at one of my sites I look after. Are you running in an HACMP environment as well? Not that it should make a difference mind you (The problem I struck was with HACMP not ADSM/TSM. All our worries disappeared after changing the Cisco routers to NOT to auto-negotiate but 100BT. Hope this helps, if not I'm sure you'll get back to us all :) Cheers Stephen Pole Project Operations Manager - Geophysicist IBM RS6000/TSM/HACMP Specialist 61 Delonix Circle Woodvale WA 6026 Austalia Office Phone +61 8 9409 3014 Home Phone +61 8 9409 3012 Mobile Phone +61 4 2121 0157 Time Zone : WAST - GMT + 08:00 hours -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Seay, Paul Sent: Wednesday, 17 April 2002 1:38 AM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Jim, We have found that sometimes the switches have to be set to 100 not auto negotiate as well as the server. It has to do with incompatibility issues with auto negotiate and windows. -----Original Message----- From: Jim Healy [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 9:13 AM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Don Are you sure you're using CAT-5 cable? Definitely Cat-t You say the NIC's are forced at 100/full -- how about the switch ports? Switch ports are forced 100/full also Is there adjacent "noise" that might be emitting across the network? I don't know about adjacent noise, how do I look for that? Do you have old vs. current switch HW? Is it up to date, microcode? I'm having the network guys check the microcode VLAN's -- are you sure it's a point-to-point and not getting re-routed due to DNS "mistakes" (eg, any potential router involved, multiple DNS entries for the same hostname, local hosts file on the client, local routing table on the client)??? The clients only have one physical path to use to get to the TSM server thats the way we designed it, no routers involved either. Your msg got garbled when stating specifics of your client situation... is the problem only on one (of many) clients using the same switch? We are down to only 2 clients on the v-lan, they are both NT4 Finally, what OS platforms (and switch vendor & model) are involved? its a cisco 5000 switch Both clients behave the same on this segment. "Don France (TSMnews)" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 04/15/2002 07:34:50 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: TSM network problem Are you sure you're using CAT-5 cable? You say the NIC's are forced at 100/full -- how about the switch ports? Is there adjacent "noise" that might be emitting across the network? Do you have old vs. current switch HW? Is it up to date, microcode? VLAN's -- are you sure it's a point-to-point and not getting re-routed due to DNS "mistakes" (eg, any potential router involved, multiple DNS entries for the same hostname, local hosts file on the client, local routing table on the client)??? Your msg got garbled when stating specifics of your client situation... is the problem only on one (of many) clients using the same switch? Finally, what OS platforms (and switch vendor & model) are involved? These are buggers to solve, unless you can find some consistency -- eg, one client fails but others run fine (typical, and helps reduce the focus to identify the delta between good client and failing client -- for Win2K, we've seen flaky OEM-NIC's cause this kind of problem; also, one switch vendor didn't work well with forced 100/full, simply insisted on auto-negotiate.) ----- Original Message ----- From: "Jim Healy" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, April 15, 2002 11:25 AM Subject: TSM network problem > Can any of you network gurus help me out with a TSM problem? > > We currenty have an isolated 100mb ethernet network for TSM. We have > three NICS in the TSM server, each attached to a seperate V-lan We > spread the servers backing up across the three v-lans > > We are having on clients on one of the vlans that intermittently get > "session lost re-initializing messages" in the dsmsched.log > > When we ping the clients from the TSM server we get no seesion or > packet loss > > When we ping the TSM nic from the client we get intermittent packet losses > > We replaced the NIC in the TSM server > We replaced the cable from the TSM server to the switch > We replaced the cable from the client NIC to the switch > > We've ensured that both NICs are set to 100/full > > My network guys are out of ideas any body have any suggestions?
