Re: TSM network problem
Jim, What is your server platform? I have seen issues with the NIC card being on a slower bus in an AIX box cause problems.Once we moved the NIC card to a 40 MB/sec bus we were fine. - Original Message - From: Alex Paschal [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 17, 2002 2:28 PM Subject: Re: TSM network problem Jim, What have your network people said when they ran a packet analyzer on that switch? Also, have you tried running a crossover cable from your TSM server to one client to see if that works? It might be a way to prove that the problem doesn't lie with your systems. -Original Message- From: Jim Healy [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 5:15 AM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Sean, At one point we moved the cable from the TSM Server NIC on the switch to another port with no change in the error. Seay, Paul [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 11:28:35 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 Did you use the same ports on the switch? -Original Message- From: Jim Healy [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 2:25 PM To: [EMAIL PROTECTED] 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?
Re: TSM network problem
Sean, At one point we moved the cable from the TSM Server NIC on the switch to another port with no change in the error. Seay, Paul [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 11:28:35 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 Did you use the same ports on the switch? -Original Message- From: Jim Healy [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 2:25 PM To: [EMAIL PROTECTED] 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?
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?
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?
Re: TSM network problem
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?
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?
Re: TSM network problem
Check to see that the switch port is also set to 100/full. - Mr. Lindsay Morris CEO, Servergraph www.servergraph.com 859-253-8000 ofc 425-988-8478 fax -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Healy Sent: Monday, April 15, 2002 2:25 PM To: [EMAIL PROTECTED] 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?
Re: TSM network problem
Sorry about that, Lindsay. Replies go directly to you. Heh, heh. Additionally, you might check MTU sizes. I've seen situations where switches/routers were set to one, the clients were set to another, larger, if I remember correctly, and a do not split packet caused all sorts of havok. But really, if you're losing packets on ping, your networking guys should be able to analyze the packets and tell you what the problem is. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Mr. Lindsay Morris [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 12:04 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Check to see that the switch port is also set to 100/full. - Mr. Lindsay Morris CEO, Servergraph www.servergraph.com 859-253-8000 ofc 425-988-8478 fax -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Healy Sent: Monday, April 15, 2002 2:25 PM To: [EMAIL PROTECTED] 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?
Re: TSM network problem
Both ends are set to 100/full Alex Paschal [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 03:14:54 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 Sorry about that, Lindsay. Replies go directly to you. Heh, heh. Additionally, you might check MTU sizes. I've seen situations where switches/routers were set to one, the clients were set to another, larger, if I remember correctly, and a do not split packet caused all sorts of havok. But really, if you're losing packets on ping, your networking guys should be able to analyze the packets and tell you what the problem is. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Mr. Lindsay Morris [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 12:04 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Check to see that the switch port is also set to 100/full. - Mr. Lindsay Morris CEO, Servergraph www.servergraph.com 859-253-8000 ofc 425-988-8478 fax -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Healy Sent: Monday, April 15, 2002 2:25 PM To: [EMAIL PROTECTED] 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?
Re: TSM network problem
Hi Look for how many hops it takes to reach other end. Its tracerout and tracert to see the loss exactly where u are missing on the HOP. Balanand -Original Message- From: Jim Healy [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 2:36 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Both ends are set to 100/full Alex Paschal [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 03:14:54 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 Sorry about that, Lindsay. Replies go directly to you. Heh, heh. Additionally, you might check MTU sizes. I've seen situations where switches/routers were set to one, the clients were set to another, larger, if I remember correctly, and a do not split packet caused all sorts of havok. But really, if you're losing packets on ping, your networking guys should be able to analyze the packets and tell you what the problem is. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Mr. Lindsay Morris [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 12:04 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Check to see that the switch port is also set to 100/full. - Mr. Lindsay Morris CEO, Servergraph www.servergraph.com 859-253-8000 ofc 425-988-8478 fax -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Healy Sent: Monday, April 15, 2002 2:25 PM To: [EMAIL PROTECTED] 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?
Re: TSM network problem
traceroute to nis.nsf.net (35.1.1.48), 30 hops max, 56 byte packet 1 helios.ee.lbl.gov (128.3.112.1) 19 ms 19 ms 0 ms 2 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 39 ms 19 ms 3 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 39 ms 19 ms 4 ccngw-ner-cc.Berkeley.EDU (128.32.136.23) 39 ms 40 ms 39 ms 5 ccn-nerif22.Berkeley.EDU (128.32.168.22) 39 ms 39 ms 39 ms 6 128.32.197.4 (128.32.197.4) 40 ms 59 ms 59 ms 7 131.119.2.5 (131.119.2.5) 59 ms 59 ms 59 ms 8 129.140.70.13 (129.140.70.13) 99 ms 99 ms 80 ms 9 129.140.71.6 (129.140.71.6) 139 ms 239 ms 319 ms 10 129.140.81.7 (129.140.81.7) 220 ms 199 ms 199 ms 11 nic.merit.edu (35.1.1.48) 239 ms 239 ms 239 ms -Original Message- From: Jim Healy [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 2:36 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Both ends are set to 100/full Alex Paschal [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 03:14:54 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 Sorry about that, Lindsay. Replies go directly to you. Heh, heh. Additionally, you might check MTU sizes. I've seen situations where switches/routers were set to one, the clients were set to another, larger, if I remember correctly, and a do not split packet caused all sorts of havok. But really, if you're losing packets on ping, your networking guys should be able to analyze the packets and tell you what the problem is. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Mr. Lindsay Morris [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 12:04 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Check to see that the switch port is also set to 100/full. - Mr. Lindsay Morris CEO, Servergraph www.servergraph.com 859-253-8000 ofc 425-988-8478 fax -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Healy Sent: Monday, April 15, 2002 2:25 PM To: [EMAIL PROTECTED] 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?
Re: TSM network problem
There are no routers involved, just connections from the 3 tsm nics to the switch and the switch to the clients PINNI, BALANAND (SBCSI) [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 04:06:41 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 traceroute to nis.nsf.net (35.1.1.48), 30 hops max, 56 byte packet 1 helios.ee.lbl.gov (128.3.112.1) 19 ms 19 ms 0 ms 2 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 39 ms 19 ms 3 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 39 ms 19 ms 4 ccngw-ner-cc.Berkeley.EDU (128.32.136.23) 39 ms 40 ms 39 ms 5 ccn-nerif22.Berkeley.EDU (128.32.168.22) 39 ms 39 ms 39 ms 6 128.32.197.4 (128.32.197.4) 40 ms 59 ms 59 ms 7 131.119.2.5 (131.119.2.5) 59 ms 59 ms 59 ms 8 129.140.70.13 (129.140.70.13) 99 ms 99 ms 80 ms 9 129.140.71.6 (129.140.71.6) 139 ms 239 ms 319 ms 10 129.140.81.7 (129.140.81.7) 220 ms 199 ms 199 ms 11 nic.merit.edu (35.1.1.48) 239 ms 239 ms 239 ms -Original Message- From: Jim Healy [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 2:36 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Both ends are set to 100/full Alex Paschal [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 03:14:54 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 Sorry about that, Lindsay. Replies go directly to you. Heh, heh. Additionally, you might check MTU sizes. I've seen situations where switches/routers were set to one, the clients were set to another, larger, if I remember correctly, and a do not split packet caused all sorts of havok. But really, if you're losing packets on ping, your networking guys should be able to analyze the packets and tell you what the problem is. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Mr. Lindsay Morris [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 12:04 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Check to see that the switch port is also set to 100/full. - Mr. Lindsay Morris CEO, Servergraph www.servergraph.com 859-253-8000 ofc 425-988-8478 fax -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Healy Sent: Monday, April 15, 2002 2:25 PM To: [EMAIL PROTECTED] 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?
Re: TSM network problem
What I meant, earlier, was that while you may be using 100/full on the TSM server, and 100/full on the client, the cables plug into a switch in the middle, and each port on that switch may be configured differently. So you ave to telnet to the switch's IP address and log in some how and poke a round and see that the SWITCH ports are ALSO 100/full. - Mr. Lindsay Morris CEO, Servergraph www.servergraph.com 859-253-8000 ofc 425-988-8478 fax -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of PINNI, BALANAND (SBCSI) Sent: Monday, April 15, 2002 4:03 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Hi Look for how many hops it takes to reach other end. Its tracerout and tracert to see the loss exactly where u are missing on the HOP. Balanand -Original Message- From: Jim Healy [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 2:36 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Both ends are set to 100/full Alex Paschal [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 03:14:54 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 Sorry about that, Lindsay. Replies go directly to you. Heh, heh. Additionally, you might check MTU sizes. I've seen situations where switches/routers were set to one, the clients were set to another, larger, if I remember correctly, and a do not split packet caused all sorts of havok. But really, if you're losing packets on ping, your networking guys should be able to analyze the packets and tell you what the problem is. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Mr. Lindsay Morris [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 12:04 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Check to see that the switch port is also set to 100/full. - Mr. Lindsay Morris CEO, Servergraph www.servergraph.com 859-253-8000 ofc 425-988-8478 fax -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Healy Sent: Monday, April 15, 2002 2:25 PM To: [EMAIL PROTECTED] 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?
Re: TSM network problem
What are the clients involved... WinNT/2000? AIX,? etc. Have you looked at the event logs (NT term) of those clients to see if there are any errors reported there? We had a similar error message show up on a few slower processing NT servers. We ended up replacing the NICs on those nodes, as well as rescheduling them so there is less network traffic during their backups. That seemed to help. The servers that had issues are quad 200MHz machines running WinNT 4.0. Faster MHz nodes didn't seem to have issues. Just a thought. Good luck. Todd Jim Healy James.Healy@AXA To: [EMAIL PROTECTED] -TECH.COM cc: Sent by: ADSM:Subject: Re: TSM network problem Dist Stor Manager [EMAIL PROTECTED] T.EDU 04/15/02 03:16 PM Please respond to ADSM: Dist Stor Manager There are no routers involved, just connections from the 3 tsm nics to the switch and the switch to the clients PINNI, BALANAND (SBCSI) [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 04:06:41 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 traceroute to nis.nsf.net (35.1.1.48), 30 hops max, 56 byte packet 1 helios.ee.lbl.gov (128.3.112.1) 19 ms 19 ms 0 ms 2 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 39 ms 19 ms 3 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 39 ms 19 ms 4 ccngw-ner-cc.Berkeley.EDU (128.32.136.23) 39 ms 40 ms 39 ms 5 ccn-nerif22.Berkeley.EDU (128.32.168.22) 39 ms 39 ms 39 ms 6 128.32.197.4 (128.32.197.4) 40 ms 59 ms 59 ms 7 131.119.2.5 (131.119.2.5) 59 ms 59 ms 59 ms 8 129.140.70.13 (129.140.70.13) 99 ms 99 ms 80 ms 9 129.140.71.6 (129.140.71.6) 139 ms 239 ms 319 ms 10 129.140.81.7 (129.140.81.7) 220 ms 199 ms 199 ms 11 nic.merit.edu (35.1.1.48) 239 ms 239 ms 239 ms -Original Message- From: Jim Healy [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 2:36 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Both ends are set to 100/full Alex Paschal [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 03:14:54 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 Sorry about that, Lindsay. Replies go directly to you. Heh, heh. Additionally, you might check MTU sizes. I've seen situations where switches/routers were set to one, the clients were set to another, larger, if I remember correctly, and a do not split packet caused all sorts of havok. But really, if you're losing packets on ping, your networking guys should be able to analyze the packets and tell you what the problem is. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Mr. Lindsay Morris [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 12:04 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Check to see that the switch port is also set to 100/full. - Mr. Lindsay Morris CEO, Servergraph www.servergraph.com 859-253-8000 ofc 425-988-8478 fax -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Healy Sent: Monday, April 15, 2002 2:25 PM To: [EMAIL PROTECTED] 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?
Re: TSM network problem
These are strictly NT clients right now and there is no other traffic on the vlan when we run the test, so its not interference from other clients. Todd Lundstedt [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 04: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 What are the clients involved... WinNT/2000? AIX,? etc. Have you looked at the event logs (NT term) of those clients to see if there are any errors reported there? We had a similar error message show up on a few slower processing NT servers. We ended up replacing the NICs on those nodes, as well as rescheduling them so there is less network traffic during their backups. That seemed to help. The servers that had issues are quad 200MHz machines running WinNT 4.0. Faster MHz nodes didn't seem to have issues. Just a thought. Good luck. Todd Jim Healy James.Healy@AXA To: [EMAIL PROTECTED] -TECH.COM cc: Sent by: ADSM:Subject: Re: TSM network problem Dist Stor Manager [EMAIL PROTECTED] T.EDU 04/15/02 03:16 PM Please respond to ADSM: Dist Stor Manager There are no routers involved, just connections from the 3 tsm nics to the switch and the switch to the clients PINNI, BALANAND (SBCSI) [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 04:06:41 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 traceroute to nis.nsf.net (35.1.1.48), 30 hops max, 56 byte packet 1 helios.ee.lbl.gov (128.3.112.1) 19 ms 19 ms 0 ms 2 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 39 ms 19 ms 3 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 39 ms 19 ms 4 ccngw-ner-cc.Berkeley.EDU (128.32.136.23) 39 ms 40 ms 39 ms 5 ccn-nerif22.Berkeley.EDU (128.32.168.22) 39 ms 39 ms 39 ms 6 128.32.197.4 (128.32.197.4) 40 ms 59 ms 59 ms 7 131.119.2.5 (131.119.2.5) 59 ms 59 ms 59 ms 8 129.140.70.13 (129.140.70.13) 99 ms 99 ms 80 ms 9 129.140.71.6 (129.140.71.6) 139 ms 239 ms 319 ms 10 129.140.81.7 (129.140.81.7) 220 ms 199 ms 199 ms 11 nic.merit.edu (35.1.1.48) 239 ms 239 ms 239 ms -Original Message- From: Jim Healy [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 2:36 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Both ends are set to 100/full Alex Paschal [EMAIL PROTECTED]@VM.MARIST.EDU on 04/15/2002 03:14:54 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 Sorry about that, Lindsay. Replies go directly to you. Heh, heh. Additionally, you might check MTU sizes. I've seen situations where switches/routers were set to one, the clients were set to another, larger, if I remember correctly, and a do not split packet caused all sorts of havok. But really, if you're losing packets on ping, your networking guys should be able to analyze the packets and tell you what the problem is. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Mr. Lindsay Morris [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 12:04 PM To: [EMAIL PROTECTED] Subject: Re: TSM network problem Check to see that the switch port is also set to 100/full. - Mr. Lindsay Morris CEO, Servergraph www.servergraph.com 859-253-8000 ofc 425-988-8478 fax -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jim Healy Sent: Monday, April 15, 2002 2:25 PM To: [EMAIL PROTECTED] 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?
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?
Re: TSM network problem
Did you use the same ports on the switch? -Original Message- From: Jim Healy [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 2:25 PM To: [EMAIL PROTECTED] 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?
