Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TSM\s+network\s+problem\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TSM\s+network\s+problem\s*$/: 18 ]

Total 18 documents matching your query.

1. TSM network problem (score: 1): Author: Jim Healy <James.Healy AT AXA-TECH DOT COM>; Date: Mon, 15 Apr 2002 14:25:22 -0400; 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 sp; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00858.html (11,717 bytes)
2. Re: TSM network problem (score: 1): Author: "Mr. Lindsay Morris" <lmorris AT SERVERGRAPH DOT COM>; Date: Mon, 15 Apr 2002 15:04:29 -0400; Check to see that the switch port is also set to 100/full. -- Mr. Lindsay Morris Mr. Lindsay Morris CEO, Servergraph www.servergraph.com 859-253-8000 ofc 425-988-8478 fax; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00862.html (12,703 bytes)
3. Re: TSM network problem (score: 1): Author: Alex Paschal <AlexPaschal AT FREIGHTLINER DOT COM>; Date: Mon, 15 Apr 2002 12:14:54 -0700; 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,; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00863.html (11,760 bytes)
4. Re: TSM network problem (score: 1): Author: Jim Healy <James.Healy AT AXA-TECH DOT COM>; Date: Mon, 15 Apr 2002 15:36:23 -0400; Both ends are set to 100/full "Alex Paschal" <AlexPaschal AT FREIGHTLINER DOT COM>@VM.MARIST.EDU> on 04/15/2002 03:14:54 PM Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> S; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00867.html (12,266 bytes)
5. Re: TSM network problem (score: 1): Author: "PINNI, BALANAND (SBCSI)" <bp3965 AT SBC DOT COM>; Date: Mon, 15 Apr 2002 15:02:36 -0500; 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; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00871.html (11,588 bytes)
6. Re: TSM network problem (score: 1): Author: "PINNI, BALANAND (SBCSI)" <bp3965 AT SBC DOT COM>; Date: Mon, 15 Apr 2002 15:06:41 -0500; 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.ED; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00872.html (12,286 bytes)
7. Re: TSM network problem (score: 1): Author: Jim Healy <James.Healy AT AXA-TECH DOT COM>; Date: Mon, 15 Apr 2002 16:16:33 -0400; There are no routers involved, just connections from the 3 tsm nics to the switch and the switch to the clients "PINNI, BALANAND (SBCSI)" <bp3965 AT SBC DOT COM>@VM.MARIST.EDU> on 04/15/2002 04:06:41; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00873.html (12,780 bytes)
8. Re: TSM network problem (score: 1): Author: "Mr. Lindsay Morris" <lmorris AT SERVERGRAPH DOT COM>; Date: Mon, 15 Apr 2002 16:46:57 -0400; 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 configu; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00874.html (16,589 bytes)
9. Re: TSM network problem (score: 1): Author: Todd Lundstedt <Todd_Lundstedt AT VIA-CHRISTI DOT ORG>; Date: Mon, 15 Apr 2002 15:34:50 -0500; 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; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00875.html (13,899 bytes)
10. Re: TSM network problem (score: 1): Author: Jim Healy <James.Healy AT AXA-TECH DOT COM>; Date: Mon, 15 Apr 2002 17:26:01 -0400; 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" <Todd_Lundstedt AT VIA-CHRISTI DOT; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00876.html (14,407 bytes)
11. Re: TSM network problem (score: 1): Author: "Don France (TSMnews)" <DFrance-TSM AT ATT DOT NET>; Date: Mon, 15 Apr 2002 16:34:50 -0700; 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.; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00883.html (12,307 bytes)
12. Re: TSM network problem (score: 1): Author: "Seay, Paul" <seay_pd AT NAPTHEON DOT COM>; Date: Mon, 15 Apr 2002 23:28:35 -0400; Did you use the same ports on the switch?; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00887.html (11,636 bytes)
13. Re: TSM network problem (score: 1): Author: Jim Healy <James.Healy AT AXA-TECH DOT COM>; Date: Tue, 16 Apr 2002 08:15:23 -0400; 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" <seay_pd AT NAPTHEON DOT COM>@VM.MARIST.EDU> on 04/15/2002 11:28:; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00910.html (12,040 bytes)
14. Re: TSM network problem (score: 1): Author: Jim Healy <James.Healy AT AXA-TECH DOT COM>; Date: Tue, 16 Apr 2002 09:13:24 -0400; 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" tha; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00921.html (14,054 bytes)
15. Re: TSM network problem (score: 1): Author: "Seay, Paul" <seay_pd AT NAPTHEON DOT COM>; Date: Tue, 16 Apr 2002 13:37:51 -0400; 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.; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00949.html (11,425 bytes)
16. Re: TSM network problem (score: 1): Author: Stephen Pole <spole AT BIGPOND.NET DOT AU>; Date: Wed, 17 Apr 2002 09:25:31 +0800; 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 pro; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg00979.html (11,884 bytes)
17. Re: TSM network problem (score: 1): Author: Alex Paschal <AlexPaschal AT FREIGHTLINER DOT COM>; Date: Wed, 17 Apr 2002 11:28:54 -0700; 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 migh; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg01019.html (11,332 bytes)
18. Re: TSM network problem (score: 1): Author: Bill Maloney <bmaloney AT DNDCONSULT DOT COM>; Date: Wed, 17 Apr 2002 14:55:56 -0400; 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.; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2002-04/msg01021.html (11,149 bytes)

Current List: 1 - 18
Page: [1]