trace route problem

Dhotre, Shekhar Shekhar.Dhotre at t-t.com
Thu Oct 25 13:43:42 EDT 2001


Hi managers ,
  I am doing trace route from one of our production box to netbackup server
,because it is taking 30hours to backup 300GB of data .I have fiber optic
drives and EMC`s latest clarion4700 fiber attached disk .so I started
looking at network. 
My hostname idsmajor is on 36.x subnet and Netbackup master server is also
on 36.x subnet .
both servers got multiple interfaces .I am not able to find why host
idsmajor  is not reaching to netbackup master in one hop  ? 
also how does trace route and telnet handles routing ? one of our admin is
arguing on telnet and trace route : when you do telnet it reaches to
particular interface immediately and when you do trace route you get
multiple interfaces found message .


this routing table on source box .
                                                                         
Routing Table:                                                           
  Destination           Gateway           Flags  Ref   Use   Interface   
-------------------- -------------------- ----- ----- ------ ---------   
206.229.36.0         206.229.36.25         U        2 166460  hme0       
192.168.10.0         192.168.10.12         U        2  10674  qfe3       
192.168.1.0          192.168.1.11          U        2  10878  hme1       
default              206.229.36.1          UG       01463182             
127.0.0.1            127.0.0.1             UH       01253776  lo0        
                                                                         

when i do trace route from host idsmajor to neon i get following :

 

idsmajor:root:/>traceroute neon

traceroute: Warning: ckecksums disabled

traceroute: Warning: Multiple interfaces found; using 192.168.1.11 @ hme1

traceroute to neon.t-t.com (206.229.36.83), 30 hops max, 40 byte packets

 1  * * *

 2  * * *

 3  * * *

 4  * * *

 5  * *^Cidsmajor:root:/>


 4  * * *                                                               
 5  * *^C
idsmajor:root:/>ifconfig -a                                    
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232                  
        inet 127.0.0.1 netmask ff000000                                 
hme1: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500     
        inet 192.168.1.11 netmask ffffff00 broadcast 192.168.1.255      
        ether 8:0:20:82:ac:af                                           
qfe3: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500     
        inet 192.168.10.12 netmask ffffff00 broadcast 192.168.10.255    
        ether 8:0:20:82:ac:af                                           
hme0: flags=843<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500                
        inet 206.229.36.25 netmask ffffff80 broadcast 206.229.36.127
(source Ip address ) 
        ether 8:0:20:82:ac:af                                           
On host neon 
# ifconfig -a

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1

        inet 127.0.0.1 netmask ff000000

hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2

        inet 206.229.36.83 netmask ffffff80 broadcast 206.229.36.127
(Destination Ip address) 
        ether 8:0:20:9b:ab:56

hme1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3

        inet 206.229.32.17 netmask ffffff00 broadcast 206.229.32.255

        ether 8:0:20:9b:ab:56

lo0: flags=2000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6> mtu 8252 index 1

        inet6 ::1/128

hme0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2

        ether 8:0:20:9b:ab:56

        inet6 fe80::a00:20ff:fe9b:ab56/10




Thanks in advance 

SD 
Unix Admin
Boston ,USA .



posting Our internal conversation 




	Hmmm, ok -- I used "method" in a vague way.
What is the difference here?

idsmajor:root:/>idsmajor:root:/>traceroute neon
traceroute: Warning: ckecksums disabled
traceroute: Warning: Multiple interfaces found; using 192.168.1.11 @
hme1
traceroute to neon.t-t.com (206.229.36.83), 30 hops max, 40 byte packets
 1  *^Cidsmajor:root:/>
idsmajor:root:/>


idsmajor:root:/>telnet neon
Trying 206.229.36.83...
Connected to neon.t-t.com.
Escape character is '^]'.


SunOS 5.8

login: Connection closed by foreign host.
idsmajor:root:/>



	Why does telnet not say "Multiple interfaces 
found; using 192.168.1.11 @ hme1"?  That's what I 
meant by 'method' -- the network sockets code in
the telnet binary is probably written to check the
route table before making an open.  

	We should try to understand how netbackup
makes its connections.  If it's coming from netback,
then there might be problems with multiple interfaces
on that end as well.

	ufsdump also takes 40 - 50 hours, so maybe 
the problem is with packets coming to the box from
other networks, where file servers are mounted?




"Dhotre, Shekhar" wrote:
> 
> >I don't think backup traffic follows
> >traceroute's method though.
> 
>  Why do you think so ? backup traffic is nothing but tcp/ip packets .
> 
> -----Original Message-----
> From: Stiles, Richard
> Sent: Wednesday, October 24, 2001 7:00 PM
> To: Toal, Dave; Gummow, Skip
> Cc: Dhotre, Shekhar; Network Group
> Subject: RE: IDSMAJOR route table --compared to SPNODE1
> 
> Right-- but the warning says that "multiple interfaces" exist.... What I
> don't understand is 1) why it thinks there is more than 1 interface for
> that route and 2) how it ever decides on the 192.168 network (coin
> flip?).
> 
> I thought it was worth checking into, though the problem is apparently
> not tied directly to that 206.229.36.0 route.
> 
> Thanks for looking at it shekhar-- maybe we can discuss tomorrow
afternoon.
> 
> Thanks,
> Rich
> 
> -----Original Message-----




More information about the sunmanagers mailing list