Login or Register to Ask a Question and Join Our Community


Solaris

Network issue on multinic. Unable to ping a host from One NIC but other works

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris Network issue on multinic. Unable to ping a host from One NIC but other works
# 1  
Old 05-15-2013
Oracle Network issue on multinic. Unable to ping a host from One NIC but other works
Dear,
I hope you all will be ok.
I have an issue with Solaris box running on x86 Blade.
I am unable to ping a node neither traceroute. I am able to do traceroute from oce0:6 port which have IP and subnet of same type which oce0:1 has.
details are as follows:


Problem:
Code:
root@rinams02:/# traceroute 10.128.1.35
traceroute: Warning: Multiple interfaces found; using 10.128.5.6 @ oce0:1
traceroute to 10.128.1.35 (10.128.1.35), 30 hops max, 40 byte packets
 1  10.128.5.29 (10.128.5.29)  1.056 ms  0.927 ms  0.784 ms
 2  10.128.5.194 (10.128.5.194)  0.405 ms  0.419 ms  0.272 ms
 3  * * *
 4 ^C
 root@rinams02:/# traceroute -i oce0:6 10.128.1.35
traceroute to 10.128.1.35 (10.128.1.35), 30 hops max, 40 byte packets
1 10.128.5.29 (10.128.5.29) 1.288 ms 1.206 ms 1.568 ms
2 10.128.5.194 (10.128.5.194) 0.382 ms 0.373 ms 0.385 ms
3 10.128.1.28 (10.128.1.28) 0.679 ms 0.486 ms 0.427 ms
4 10.128.1.35 (10.128.1.35) 0.385 ms 0.279 ms 0.323 ms
 root@rinams02:/# traceroute 10.128.1.36
traceroute: Warning: Multiple interfaces found; using 10.128.5.6 @ oce0:1
traceroute to 10.128.1.36 (10.128.1.36), 30 hops max, 40 byte packets
 1  10.128.5.29 (10.128.5.29)  1.067 ms  0.784 ms  0.751 ms
 2  10.128.5.194 (10.128.5.194)  0.363 ms  0.354 ms  0.282 ms
 3  * * *
 4 ^C
 root@rinams02:/# traceroute -i oce0:6 10.128.1.36
traceroute to 10.128.1.36 (10.128.1.36), 30 hops max, 40 byte packets
 1  10.128.5.29 (10.128.5.29)  1.236 ms  0.833 ms  0.691 ms
 2  10.128.5.194 (10.128.5.194)  0.337 ms  0.273 ms  0.303 ms
 3  10.128.1.28 (10.128.1.28)  0.645 ms  0.503 ms  0.486 ms
 4  10.128.1.36 (10.128.1.36)  0.219 ms  0.184 ms  0.194 ms

Similar behaviour is seen when doing ssh adding -b 10.128.5.7 (which is OSS VIP) to the node instead of just ssh user@node
Thanks in advance for any hint on this.
Code:
netstat -rn
 Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use     Interface
——————– ——————– —– —– ———- ———
default              10.128.5.1           UG        1      17169
10.128.5.0           10.128.5.6           U         1      19141 oce0:1
10.128.5.0           10.128.5.10          U         1          0 oce0:2
10.128.5.0           10.128.5.9           U         1          0 oce0:3
10.128.5.0           10.128.5.8           U         1          0 oce0:4
10.128.5.0           10.128.5.11          U         1          0 oce0:5
10.128.5.0           10.128.5.7           U         1          0 oce0:6
10.128.5.0           10.128.5.6           U         1          0 oce0
10.128.5.0           10.128.5.6           U         1          1 oce9
10.128.5.5           200.200.200.15       UGH       1          1
192.168.100.0        192.168.100.35       U         1    1350595 oce2:1
192.168.100.0        192.168.100.35       U         1          0 oce2
192.168.100.0        192.168.100.35       U         1    1350390 oce11
192.168.128.0        192.168.128.6        U         1         24 oce3
192.168.128.0        192.168.128.5        U         1          0 oce3:1
192.168.128.0        192.168.128.4        U         1          0 oce3:2
200.200.200.0        200.200.200.35       U         1          1 oce10
224.0.0.0            10.128.5.6           U         1          0 oce0:1
127.0.0.1            127.0.0.1            UH      122    2553507 lo0   
 ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
oce0: flags=9040843 mtu 1500 index 2
        inet 10.128.5.14 netmask ffffffe0 broadcast 10.128.5.31
        groupname pub_mnic
        ether 78:ac:c0:f7:47:4
oce0:1: flags=1000843 mtu 1500 index 2
        inet 10.128.5.6 netmask ffffffe0 broadcast 10.128.5.31
oce0:2: flags=1000843 mtu 1500 index 2
        inet 10.128.5.10 netmask ffffffe0 broadcast 10.128.5.31
oce0:3: flags=1000843 mtu 1500 index 2
        inet 10.128.5.9 netmask ffffffe0 broadcast 10.128.5.31
oce0:4: flags=1000843 mtu 1500 index 2
        inet 10.128.5.8 netmask ffffffe0 broadcast 10.128.5.31
oce0:5: flags=1000843 mtu 1500 index 2
        inet 10.128.5.11 netmask ffffffe0 broadcast 10.128.5.31
oce0:6: flags=1000843 mtu 1500 index 2
        inet 10.128.5.7 netmask ffffffe0 broadcast 10.128.5.31
oce2: flags=9040843 mtu 1500 index 5
        inet 192.168.100.36 netmask ffffff80 broadcast 192.168.100.127
        groupname stor_mnic
        ether 78:ac:c0:f7:47:5
oce2:1: flags=1000843 mtu 1500 index 5
        inet 192.168.100.35 netmask ffffff80 broadcast 192.168.100.127
oce3: flags=1000843 mtu 1500 index 6
        inet 192.168.128.6 netmask ffffffc0 broadcast 192.168.128.63
        ether 78:ac:c0:f7:47:9
oce3:1: flags=1000843 mtu 1500 index 6
        inet 192.168.128.5 netmask ffffffc0 broadcast 192.168.128.63
oce3:2: flags=1000843 mtu 1500 index 6
        inet 192.168.128.4 netmask ffffffc0 broadcast 192.168.128.63
oce9: flags=9040843 mtu 1500 index 7
        inet 10.128.5.15 netmask ffffffe0 broadcast 10.128.5.31
        groupname pub_mnic
        ether 78:ac:c0:f7:47:10
oce10: flags=1000843 mtu 1500 index 3
        inet 200.200.200.35 netmask ffffff00 broadcast 200.200.200.255
        ether 78:ac:c0:f7:47:d
oce11: flags=9040843 mtu 1500 index 4
        inet 192.168.100.37 netmask ffffff80 broadcast 192.168.100.127
        groupname stor_mnic
 root@rinams02:/# cat /etc/netmasks
#
# The netmasks file associates Internet Protocol (IP) address
# masks with IP network numbers.
#
#       network-number  netmask
#
#               128.32.0.0 255.255.255.0
#
10.128.5.0 255.255.255.224
192.168.100.0   255.255.255.128
200.200.200.0   255.255.255.0
192.168.128.0   255.255.255.192
 root@rinams02:/# cat /etc/hostname*
10.128.5.14 netmask + broadcast + deprecated -failover up \
    addif 10.128.5.6 netmask + broadcast + up
200.200.200.35
192.168.100.37 netmask + broadcast + deprecated -failover up
192.168.100.36 netmask + broadcast + deprecated -failover up \
    addif 192.168.100.35 netmask + broadcast + up
rinams02-bkp
10.128.5.15 netmask + broadcast + deprecated -failover up
root@rinams02:/# cat /etc/hostname*
hostname.oce0   hostname.oce11  hostname.oce3
hostname.oce10  hostname.oce2   hostname.oce9
root@rinams02:/# cat /etc/hostname.oce0
10.128.5.14 netmask + broadcast + deprecated -failover up \
    addif 10.128.5.6 netmask + broadcast + up
 eshlkhn@rinams02> ping 10.128.20.2
10.128.20.2 is alive
eshlkhn@rinams02> ping 10.128.3.1
10.128.3.1 is alive
eshlkhn@rinams02> ping 10.128.3.133
10.128.3.133 is alive
eshlkhn@rinams02> ping 10.128.3.132
10.128.3.132 is alive
eshlkhn@rinams02> ping 10.128.3.11
10.128.3.11 is alive
eshlkhn@rinams02> traceroute 10.128.3.11
traceroute: Warning: Multiple interfaces found; using 10.128.5.6 @ oce0:1
traceroute to 10.128.3.11 (10.128.3.11), 30 hops max, 40 byte packets
1  10.128.5.29 (10.128.5.29)  1.085 ms  0.944 ms  0.617 ms
2  10.128.5.194 (10.128.5.194)  0.264 ms  0.336 ms  0.245 ms
3  10.128.3.11 (10.128.3.11)  1.278 ms  2.171 ms  2.125 ms

root@rinams02:/# ping -I oce0:6 10.128.1.36 
ping: bad interval: oce0:6
root@rinams02:/# 
root@rinams02:/# ping -i oce0:6 10.128.1.36 
^C
root@rinams02:/# traceroute -l -s  10.128.5.6 10.128.1.36
traceroute to 10.128.1.36 (10.128.1.36) from 10.128.5.6, 30 hops max, 40 byte packets
 1  10.128.5.29 (10.128.5.29)  0.990 ms (ttl=64)  1.018 ms (ttl=64)  0.722 ms (ttl=64)
 2  10.128.5.194 (10.128.5.194)  0.406 ms (ttl=254)  0.373 ms (ttl=254)  0.354 ms (ttl=254)
 3 ^C
root@rinams02:/# traceroute -l -s  10.128.5.7 10.128.1.36
traceroute to 10.128.1.36 (10.128.1.36) from 10.128.5.7, 30 hops max, 40 byte packets
 1  10.128.5.29 (10.128.5.29)  1.293 ms (ttl=64)  0.861 ms (ttl=64)  0.534 ms (ttl=64)
 2  10.128.5.194 (10.128.5.194)  0.301 ms (ttl=254)  0.300 ms (ttl=254)  0.294 ms (ttl=254)
 3  10.128.1.28 (10.128.1.28)  0.621 ms (ttl=62)  0.456 ms (ttl=62)  0.346 ms (ttl=62)
 4  10.128.1.36 (10.128.1.36)  0.328 ms (ttl=61)  0.224 ms (ttl=61)  0.207 ms (ttl=61)
root@rinams02:/# 
root@rinams02:/# 
root@rinams02:/# ping -l oce0:6 10.128.1.36
ping: bad timeout: 10.128.1.36
root@rinams02:/# ping -i oce0:6 10.128.1.36
^C
root@rinams02:/# ping -i 10.128.5.7 10.128.1.36
^C
root@rinams02:/# ping -I oce0:6 10.128.1.36
ping: bad interval: oce0:6
root@rinams02:/# ping -I oce0:1 10.128.1.36i
ping: bad interval: oce0:1
root@rinams02:/# 
root@rinams02:/#

Please advise what I can do on this or way forward.
Last edited by DukeNuke2; 05-15-2013 at 01:53 PM..
# 2  
Old 05-15-2013
Because you can reach 10.128.5.194 I suspect this or the the next hub to be a firewall,
and blocking your 10.128.5.6 but not your 10.128.5.7.
I hope you are aware that query packets sent out from 10.128.5.7, and the answer packets are routed to another interface.
Use snoop host 10.128.1.35 to see the actual packets.
# 3  
Old 05-15-2013
Hi Thanks for your prompt reply, Can you elaborate in details

As I can seem I am able to ssh the remote node 10.128.1.35

Code:
root@rinams01:/# ssh -b 10.128.5.7 nsuser@10.128.1.35
Warning: Permanently added '10.128.1.35' (RSA) to the list of known hosts.
Password: 
Last login: Tue May 14 15:45:48 2013 from 10.128.5.7
  SN Shell version 3.5
Copyright (c) 2002-2007
nsuser@rsvtutlteSASNsvrRD$ ping 10.128.5.7
PING 10.128.5.7 (10.128.5.7) 56(84) bytes of data.
64 bytes from 10.128.5.7: icmp_seq=1 ttl=252 time=0.216 ms
64 bytes from 10.128.5.7: icmp_seq=2 ttl=252 time=0.173 ms
64 bytes from 10.128.5.7: icmp_seq=3 ttl=252 time=0.189 ms
64 bytes from 10.128.5.7: icmp_seq=4 ttl=252 time=0.207 ms

AND Snoop enabled at rinams01 gives me following thing... does it make any sense.
note: masterservice is 10.128.5.7 configure on oce0:5 a virtual IP on VCS cluster server.
Code:
root@rinams01:/# 
root@rinams01:/# snoop host 10.128.1.35
Using device oce0 (promiscuous mode)
    rinams01 -> 10.128.1.35  UDP D=161 S=53403 LEN=49
masterservice -> 10.128.1.35  TCP D=22 S=48819 Syn Seq=3738098444 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK>
 10.128.1.35 -> masterservice TCP D=48819 S=22 Syn Ack=3738098445 Seq=1919781612 Len=0 Win=5840 Options=<mss 1460,nop,nop,sackOK,nop,wscale 8>
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919781613 Seq=3738098445 Len=0 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738098445 Seq=1919781613 Len=21 Win=23
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919781634 Seq=3738098445 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919781634 Seq=3738098445 Len=22 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Ack=3738098467 Seq=1919781634 Len=0 Win=23
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738098467 Seq=1919781634 Len=784 Win=23
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919782418 Seq=3738098467 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919782418 Seq=3738098467 Len=488 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Ack=3738098955 Seq=1919782418 Len=0 Win=27
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919782418 Seq=3738098955 Len=24 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Ack=3738098979 Seq=1919782418 Len=0 Win=27
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738098979 Seq=1919782418 Len=280 Win=27
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919782698 Seq=3738098979 Len=272 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738099251 Seq=1919782698 Len=592 Win=32
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919783290 Seq=3738099251 Len=16 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Ack=3738099267 Seq=1919783290 Len=0 Win=32
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919783290 Seq=3738099267 Len=48 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Ack=3738099315 Seq=1919783290 Len=0 Win=32
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738099315 Seq=1919783290 Len=48 Win=32
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919783338 Seq=3738099315 Len=64 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738099379 Seq=1919783338 Len=80 Win=32
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919783418 Seq=3738099379 Len=240 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738099619 Seq=1919783418 Len=80 Win=36
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919783498 Seq=3738099619 Len=528 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738100147 Seq=1919783498 Len=80 Win=40
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919783578 Seq=3738100147 Len=96 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738100243 Seq=1919783578 Len=64 Win=40
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919783642 Seq=3738100243 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919783642 Seq=3738100243 Len=80 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738100323 Seq=1919783642 Len=48 Win=40
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919783690 Seq=3738100323 Len=80 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738100403 Seq=1919783690 Len=32 Win=40
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919783722 Seq=3738100403 Len=64 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738100467 Seq=1919783722 Len=48 Win=40
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919783770 Seq=3738100467 Len=464 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738100931 Seq=1919783770 Len=48 Win=44
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738100931 Seq=1919783818 Len=176 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919783994 Seq=3738100931 Len=0 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738100931 Seq=1919783994 Len=80 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784074 Seq=3738100931 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919784074 Seq=3738100931 Len=48 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738100979 Seq=1919784074 Len=48 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784122 Seq=3738100979 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919784122 Seq=3738100979 Len=48 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101027 Seq=1919784122 Len=48 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784170 Seq=3738101027 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919784170 Seq=3738101027 Len=48 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101075 Seq=1919784170 Len=48 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784218 Seq=3738101075 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919784218 Seq=3738101075 Len=48 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101123 Seq=1919784218 Len=48 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784266 Seq=3738101123 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919784266 Seq=3738101123 Len=48 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101171 Seq=1919784266 Len=48 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784314 Seq=3738101171 Len=0 Win=49640
    rinams01 -> 10.128.1.35  UDP D=161 S=53403 LEN=49
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919784314 Seq=3738101171 Len=48 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101219 Seq=1919784314 Len=48 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784362 Seq=3738101219 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919784362 Seq=3738101219 Len=48 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101267 Seq=1919784362 Len=48 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784410 Seq=3738101267 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919784410 Seq=3738101267 Len=48 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101315 Seq=1919784410 Len=48 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784458 Seq=3738101315 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919784458 Seq=3738101315 Len=48 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101363 Seq=1919784458 Len=48 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784506 Seq=3738101363 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919784506 Seq=3738101363 Len=48 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101411 Seq=1919784506 Len=48 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784554 Seq=3738101411 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919784554 Seq=3738101411 Len=48 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101459 Seq=1919784554 Len=48 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784602 Seq=3738101459 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919784602 Seq=3738101459 Len=48 Win=49640
 10.128.1.35 -> masterservice ICMP Echo request (ID: 49518 Sequence number: 1)
masterservice -> 10.128.1.35  ICMP Echo reply (ID: 49518 Sequence number: 1)
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101507 Seq=1919784602 Len=160 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784762 Seq=3738101507 Len=0 Win=49640
 10.128.1.35 -> masterservice ICMP Echo request (ID: 49518 Sequence number: 2)
masterservice -> 10.128.1.35  ICMP Echo reply (ID: 49518 Sequence number: 2)
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101507 Seq=1919784762 Len=96 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784858 Seq=3738101507 Len=0 Win=49640
 10.128.1.35 -> masterservice ICMP Echo request (ID: 49518 Sequence number: 3)
masterservice -> 10.128.1.35  ICMP Echo reply (ID: 49518 Sequence number: 3)
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101507 Seq=1919784858 Len=96 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919784954 Seq=3738101507 Len=0 Win=49640
 10.128.1.35 -> masterservice ICMP Echo request (ID: 49518 Sequence number: 4)
masterservice -> 10.128.1.35  ICMP Echo reply (ID: 49518 Sequence number: 4)
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101507 Seq=1919784954 Len=96 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919785050 Seq=3738101507 Len=0 Win=49640
 10.128.1.35 -> masterservice ICMP Echo request (ID: 49518 Sequence number: 5)
masterservice -> 10.128.1.35  ICMP Echo reply (ID: 49518 Sequence number: 5)
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101507 Seq=1919785050 Len=96 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919785146 Seq=3738101507 Len=0 Win=49640
 10.128.1.35 -> masterservice ICMP Echo request (ID: 49518 Sequence number: 6)
masterservice -> 10.128.1.35  ICMP Echo reply (ID: 49518 Sequence number: 6)
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101507 Seq=1919785146 Len=96 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919785242 Seq=3738101507 Len=0 Win=49640
 10.128.1.35 -> masterservice ICMP Echo request (ID: 49518 Sequence number: 7)
masterservice -> 10.128.1.35  ICMP Echo reply (ID: 49518 Sequence number: 7)
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101507 Seq=1919785242 Len=96 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919785338 Seq=3738101507 Len=0 Win=49640
 10.128.1.35 -> masterservice ICMP Echo request (ID: 49518 Sequence number: 8)
masterservice -> 10.128.1.35  ICMP Echo reply (ID: 49518 Sequence number: 8)
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101507 Seq=1919785338 Len=96 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919785434 Seq=3738101507 Len=0 Win=49640
 10.128.1.35 -> masterservice ICMP Echo request (ID: 49518 Sequence number: 9)
masterservice -> 10.128.1.35  ICMP Echo reply (ID: 49518 Sequence number: 9)
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101507 Seq=1919785434 Len=96 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919785530 Seq=3738101507 Len=0 Win=49640
 10.128.1.35 -> masterservice ICMP Echo request (ID: 49518 Sequence number: 10)
masterservice -> 10.128.1.35  ICMP Echo reply (ID: 49518 Sequence number: 10)
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101507 Seq=1919785530 Len=96 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919785626 Seq=3738101507 Len=0 Win=49640
 10.128.1.35 -> masterservice ICMP Echo request (ID: 49518 Sequence number: 11)
masterservice -> 10.128.1.35  ICMP Echo reply (ID: 49518 Sequence number: 11)
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101507 Seq=1919785626 Len=96 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919785722 Seq=3738101507 Len=0 Win=49640
masterservice -> 10.128.1.35  TCP D=22 S=48819 Push Ack=1919785722 Seq=3738101507 Len=48 Win=49640
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101555 Seq=1919785722 Len=224 Win=44
masterservice -> 10.128.1.35  TCP D=22 S=48819 Ack=1919785946 Seq=3738101555 Len=0 Win=49640
    rinams01 -> 10.128.1.35  UDP D=161 S=53403 LEN=49
    rinams01 -> 10.128.1.35  TCP D=22 S=49147 Syn Seq=3556946310 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK>
    rinams01 -> 10.128.1.35  TCP D=22 S=49147 Syn Seq=3556946310 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK>
    rinams01 -> 10.128.1.35  TCP D=22 S=49147 Syn Seq=3556946310 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK>
    rinams01 -> 10.128.1.35  TCP D=22 S=49147 Syn Seq=3556946310 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK>
 10.128.1.35 -> masterservice TCP D=48819 S=22 Push Ack=3738101619 Seq=1919785946 Len=80 Win=44

Last edited by khaniqshahid; 05-17-2013 at 02:30 AM..
# 4  
Old 05-17-2013
Any help will be appreciated
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Cant ssh, but ping works

I cant ping to some of my machines, but ping works. I attach screenshots. Port is open and it is 22. I can't figure out why i cant access. https://www.unix.com/attachments/unix-for-advanced-and-expert-users/7492d1541541072-cant-ssh-but-ping-works-sshlisten-jpg... (17 Replies)
Discussion started by: tomislav91
17 Replies

2. Solaris

Solaris 10 - ping network issue

Hi, I'am begineer in this OS. I've installed it few days ago only to perform project "Managing users in Solaris". I have to create two virtual systems in eg. vmware , connect them and eg. rlogin from user1/machine1 to user2/machine2, give them some permissions to write read etc (this is... (1 Reply)
Discussion started by: michael.pelc
1 Replies

3. Linux

Unable to ping Linux guest from win7 host

Hi, I am using win7 on my PC and installed VMware on it on which i am running linux I am unable to ping my linux guest from my win machine, but i can ping my windows host from linux guest : Below is my system configuration Linux root@localhost ~]# ifconfig eth0 Link... (9 Replies)
Discussion started by: chander_1987
9 Replies

4. IP Networking

ping can not recognize host but host command can

Hi, I have a weird problem. when ever I do ping command like for example ping unix.comI get the following message: # ping unix.com ping: unknown host unix.com but when I use host the computer is able to know the host. # host unix.com unix.com has address 81.17.242.186 unix.com mail is... (2 Replies)
Discussion started by: programAngel
2 Replies

5. Solaris

Unable to ping Solaris VM from Xp host

Hi All, I am using Vmware Workstation 6.0.3 build-80004. Guest OS: Solaris 10 Host OS : Win XP I am getting request time out when i am trying to ping from XP ( cmd line) to Solaris VM - I have assigned IP 192.168.50.5 in Solaris VM ( Hostname: Tower1) and it is in UP status. ... (4 Replies)
Discussion started by: saurabh84g
4 Replies

6. Solaris

unable to ping a host in another domain

Hello I have a server in it.siroe.com I added it.siroe.com in /etc/resolv.conf. I still can't ping the server. any service to restart here? any other file to edit? thx (4 Replies)
Discussion started by: melanie_pfefer
4 Replies

7. Solaris

PING - Unknown host 127.0.0.1, Unknown host localhost - Solaris 10

Hello, I have a problem - I created a chrooted jail for one user. When I'm logged in as root, everything work fine, but when I'm logged in as a chrooted user - I have many problems: 1. When I execute the command ping, I get weird results: bash-3.00$ usr/sbin/ping localhost ... (4 Replies)
Discussion started by: Przemek
4 Replies

8. UNIX for Dummies Questions & Answers

NIC The Status Down but I can ping the localhost??!!

Hello, hi guys I don't know what is the problem with my NIC I can ping the Localhost (LOOPBACK) but when I run a scripts to check the NIC statuse it's shown the NIC DOWN sooo what could be the problem and what is the best way to start trouplshooting the NIC in SUN-SOLARIS. Regards, Karim ... (3 Replies)
Discussion started by: geoquest
3 Replies

9. IP Networking

QNX host cannot ping SCO host, vice versa

The problem I am facing now is that the QNX host could not ping the SCO host and vice versa. They are in the same domain, ie, 172.20.3.xx. As I am very new to Unix, I guess I must have missed out some important steps. Pls help... Thanx alot (2 Replies)
Discussion started by: gavon
2 Replies

10. UNIX for Dummies Questions & Answers

Unable to ping host

Hi, dear all, I am rather new to Unix and have this problem where I cant seem to ping from 1 host to another. The scenerio is as follows: - 1 QNX host->Eth->1 SCO host the SCO host is configured with it's IP the QNX host is configured with another IP both in the same domain, ie, 172.20.3.XX... (3 Replies)
Discussion started by: gavon
3 Replies
Login or Register to Ask a Question