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? >
