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
Mr. Lindsay Morris
CEO, Servergraph
www.servergraph.com
859-253-8000 ofc
425-988-8478 fax


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> PINNI, BALANAND (SBCSI)
> Sent: Monday, April 15, 2002 4:03 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> 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:James.Healy AT AXA-TECH DOT COM]
> Sent: Monday, April 15, 2002 2:36 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TSM network problem
>
>
> 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>
>
> Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> 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:lmorris AT SERVERGRAPH DOT COM]
> Sent: Monday, April 15, 2002 12:04 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> 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:ADSM-L AT VM.MARIST DOT EDU]On Behalf 
> > Of
> > Jim Healy
> > Sent: Monday, April 15, 2002 2:25 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > 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?
> >
>