[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | SunNet - the defacto distributed system standard |
|
| Moderator: | CVG::PETTENGILL |
|
| Created: | Mon Jun 02 1986 |
| Last Modified: | Fri May 16 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 479 |
| Total number of notes: | 1270 |
478.0. "Can it support NFS service if ping fail?" by TPSPS5::TSCMGR () Thu May 08 1997 09:28
Hi,
The following is my network architecture for ping fail problem, because
I must setting the NFS service under the WAN env through Welfleet route.
(But the telnet/ftp are always works fine.)
tu1: 150.101.1.2 150.101.5.2
-----------------------------------------
| |
| |
(yuta02) |
WINDOW95-------------- AXP2100 --------------------- WelFleet Route1
150.100.1.10 tu0: 150.100.1.2 150.100.5.2
200.100.4.1
|
|
|
|
(yuta07) 200.100.4.2
------ AXP2100 --------------------- WelFleet Route2
tu0: 153.100.1.1 153.100.5.1
| |
| |
-----------------------------------------
tu1: 153.101.1.1 150.101.5.1
Both of AXP2100 (yuta02 and yuta07) are DIGITAL_UNIX V3.2C, there are
two interface to connect to WelFleet Route. And setting dynamic route
(routed -q) for network failover.
On yuta02:
It's ping fail to 200.100.4.1, 200.100.4.2, 153.100.1.1 and 153.101.1.1,
only success to ping 150.100.5.2 through tu0 interface, but it will work
fine using the telnet/ftp. But the WINDOW95 (150.100.1.10) that are work
well to ping 200.100.4.1, 200.100.4.2, 153.100.1.1 and 153.101.1.1.
It's ping successfully to 200.100.4.1, 200.100.4.2, 153.100.1.1 and
153.101.1.1 if modify the route table from tu0 to tu1 interface on yuta02.
Why? (As same the case, it should be take place on yuta07)
PS: The image of WelFleet Route is "rev/10.01/5" from BayNetwork Router ASN.
Have any bug on DIGITAL_UNIX or WelFleet network broadcast problem for ping?
Thanks in advance,
Richard.
============================================================================
The following is network configuration on yuta02 and yuta07(AXP2100).
yuta02# ifconfig tu0
tu0: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
inet 150.100.1.2 netmask ffff0000 broadcast 150.100.255.255 ipmtu 1500
yuta02# ifconfig tu1
tu1: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
inet 150.101.1.2 netmask ffff0000 broadcast 150.101.255.255 ipmtu 1500
yuta02# ps ax|grep rout
180 ?? S 3:06.53 /usr/sbin/routed -q
4220 ttyp5 S + 0:00.02 grep rout
yuta02# netstat -rn|grep 153.100
153.100 150.100.5.2 UG 0 125127 tu0
yuta02# netstat -rn|grep 153.101
153.101 150.100.5.2 UG 0 457828 tu0
yuta02# ping 153.100.1.1
PING 153.100.1.1 (153.100.1.1): 56 data bytes
----153.100.1.1 PING Statistics----
10 packets transmitted, 0 packets received, 100% packet loss
yuta02# ping 153.101.1.1
PING 153.101.1.1 (153.101.1.1): 56 data bytes
----153.101.1.1 PING Statistics----
6 packets transmitted, 0 packets received, 100% packet loss
yuta02# ping 150.100.5.2
PING 150.100.5.2 (150.100.5.2): 56 data bytes
64 bytes from 150.100.5.2: icmp_seq=0 ttl=30 time=1 ms
64 bytes from 150.100.5.2: icmp_seq=1 ttl=30 time=0 ms
64 bytes from 150.100.5.2: icmp_seq=2 ttl=30 time=0 ms
----150.100.5.2 PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/1 ms
yuta02# ping 150.101.5.2
PING 150.101.5.2 (150.101.5.2): 56 data bytes
64 bytes from 150.101.5.2: icmp_seq=0 ttl=30 time=19 ms
64 bytes from 150.101.5.2: icmp_seq=1 ttl=30 time=4 ms
64 bytes from 150.101.5.2: icmp_seq=2 ttl=30 time=0 ms
64 bytes from 150.101.5.2: icmp_seq=3 ttl=30 time=0 ms
----150.101.5.2 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/5/19 ms
yuta02#
yuta02# telnet 153.100.1.1
Trying 153.100.1.1...
Connected to 153.100.1.1.
Escape character is '^]'.
Digital UNIX (yuta07) (ttyp1)
login: root
Password:
Login incorrect
yuta02#
yuta02# telnet 153.101.1.1
Trying 153.101.1.1...
Connected to 153.101.1.1.
Escape character is '^]'.
Digital UNIX (yuta07) (ttyp1)
login: root
Password:
yuta07# ifconfig tu0
tu0: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
inet 153.100.1.1 netmask ffff0000 broadcast 153.100.255.255 ipmtu 1500
yuta07# ifconfig tu1
tu1: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
inet 153.101.1.1 netmask ffff0000 broadcast 153.101.255.255 ipmtu 1500
yuta07# ps ax|grep route
182 ?? S 0:55.95 /usr/sbin/routed -q
22241 ttyp1 S + 0:00.01 grep route
yuta07# netstat -rn|grep 150.100
150.100 153.101.5.1 UG 5 4653 tu1
yuta07# netstat -rn|grep 150.101
150.101 153.101.5.1 UG 1 136006 tu1
yuta07#
yuta07# ping 150.100.1.2
PING 150.100.1.2 (150.100.1.2): 56 data bytes
64 bytes from 150.100.1.2: icmp_seq=0 ttl=253 time=38 ms
64 bytes from 150.100.1.2: icmp_seq=1 ttl=253 time=38 ms
64 bytes from 150.100.1.2: icmp_seq=2 ttl=253 time=38 ms
----150.100.1.2 PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 38/38/38 ms
yuta07# ping 150.101.1.2
PING 150.101.1.2 (150.101.1.2): 56 data bytes
64 bytes from 150.101.1.2: icmp_seq=0 ttl=253 time=38 ms
64 bytes from 150.101.1.2: icmp_seq=1 ttl=253 time=38 ms
64 bytes from 150.101.1.2: icmp_seq=2 ttl=253 time=40 ms
64 bytes from 150.101.1.2: icmp_seq=3 ttl=253 time=38 ms
----150.101.1.2 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 38/38/40 ms
yuta07# traceroute 150.100.1.2
traceroute to 150.100.1.2 (150.100.1.2), 30 hops max, 40 byte packets
1 KSH-ASN12 (153.101.5.1) 2 ms 1 ms 1 ms
2 200.100.4.1 (200.100.4.1) 28 ms 28 ms 28 ms
3 yuta02 (150.100.1.2) 28 ms 34 ms 29 ms
yuta07# traceroute 150.101.1.2
traceroute to 150.101.1.2 (150.101.1.2), 30 hops max, 40 byte packets
1 KSH-ASN12 (153.101.5.1) 1 ms 2 ms 1 ms
2 200.100.4.1 (200.100.4.1) 27 ms 32 ms 44 ms
3 yuta021 (150.101.1.2) 48 ms 60 ms 59 ms
The following information is from WelFleet Route1:
==============================================================================
yuta02# telnet 150.100.5.2
Trying 150.100.5.2...
Connected to 150.100.5.2.
Escape character is '^]'.
Bay Networks, Inc. and its Licensors.
Copyright 1992, 1993, 1994, 1995, 1996. All rights reserved.
Login: Manager
Password: Mounting new volume...
Device label:
Directory: 1:
New Present Working Directory: 1:
Welcome to the Backbone Technician Interface
[TPE-ASN2]$show ip arp
IP Address Type Physical Address
---------------- -------- --------------------
150.100.1.1 Dynamic 08-00-2B-E5-96-38-
150.100.1.2 Dynamic 08-00-2B-E5-97-26-
150.100.5.1 Dynamic 00-00-A2-D3-A7-40-
150.100.5.3 Dynamic 00-00-A2-D3-82-F6-
150.100.10.2 Dynamic 00-80-C8-2E-31-B3-
150.100.10.3 Dynamic 00-80-C8-19-2B-A7-
150.100.10.7 Dynamic 00-80-C8-38-EF-BE-
150.100.10.25 Dynamic 00-80-C8-2B-5E-82-
150.100.12.200 Dynamic 00-80-C8-82-5A-B7-
150.101.1.1 Dynamic 08-00-2B-E5-A6-61-
150.101.1.2 Dynamic 08-00-2B-E5-C1-88-
150.101.5.1 Dynamic 00-00-A2-D3-A7-41-
150.101.5.3 Dynamic 00-00-A2-D3-82-F7-
150.101.6.1 Dynamic 00-A0-D6-00-14-D3-
150.101.11.8 Dynamic 00-80-C8-51-50-F4-
150.101.11.13 Dynamic 00-80-C8-34-69-5D-
150.101.12.1 Dynamic 00-80-C8-57-4C-96-
150.101.12.4 Dynamic 00-80-C8-59-35-45-
150.101.12.6 Dynamic 00-80-C8-34-5F-E1-
150.101.12.7 Dynamic 00-80-C8-57-1B-16-
Type: <space> to page; <return> advance 1 line; Q to quit
Command aborted.
[TPE-ASN2]$show ip rout
Destination Mask Proto Age Cost NextHop Addr / AS
--------------- --------------- ----- -------- -------- ---------------------
150.1.0.0 255.255.0.0 RIP 20 2 150.100.5.1
150.2.0.0 255.255.0.0 RIP 20 2 150.100.5.1
150.3.0.0 255.255.0.0 RIP 20 2 150.100.5.1
150.4.0.0 255.255.0.0 LOCAL 3028245 1 200.150.4.2
150.5.0.0 255.255.0.0 LOCAL 691230 1 200.150.5.2
150.6.0.0 255.255.0.0 RIP 15 2 200.150.6.2
150.7.0.0 255.255.0.0 RIP 5 2 200.150.7.2
150.50.0.0 255.255.0.0 RIP 20 3 150.101.5.1
150.100.0.0 255.255.0.0 LOCAL 3628575 0 150.100.5.2
150.101.0.0 255.255.0.0 LOCAL 4314800 0 150.101.5.2
151.1.0.0 255.255.0.0 RIP 25 3 200.100.2.2
151.2.0.0 255.255.0.0 RIP 25 3 200.100.2.2
151.3.0.0 255.255.0.0 RIP 25 3 200.100.2.2
151.4.0.0 255.255.0.0 RIP 25 2 200.100.2.2
151.5.0.0 255.255.0.0 RIP 25 2 200.100.2.2
151.6.0.0 255.255.0.0 RIP 25 2 200.100.2.2
151.7.0.0 255.255.0.0 RIP 25 3 200.100.2.2
151.8.0.0 255.255.0.0 RIP 25 4 150.101.5.1
151.100.0.0 255.255.0.0 RIP 25 2 200.100.2.2
151.101.0.0 255.255.0.0 RIP 25 2 200.100.2.2
152.2.0.0 255.255.0.0 RIP 5 3 150.101.5.1
152.3.0.0 255.255.0.0 RIP 5 4 150.101.5.1
152.4.0.0 255.255.0.0 RIP 5 5 150.100.5.1
152.5.0.0 255.255.0.0 RIP 5 5 150.101.5.1
152.6.0.0 255.255.0.0 RIP 5 5 150.101.5.1
152.100.0.0 255.255.0.0 RIP 5 3 150.100.5.1
152.101.0.0 255.255.0.0 RIP 5 3 150.100.5.1
153.1.0.0 255.255.0.0 RIP 25 2 200.100.4.2
153.2.0.0 255.255.0.0 RIP 25 2 200.100.4.2
153.3.0.0 255.255.0.0 RIP 25 3 200.100.4.2
153.4.0.0 255.255.0.0 RIP 25 3 200.100.4.2
153.100.0.0 255.255.0.0 RIP 25 2 200.100.4.2
153.101.0.0 255.255.0.0 RIP 25 2 200.100.4.2
200.100.1.0 255.255.255.0 RIP 5 2 150.100.5.1
200.100.2.0 255.255.255.0 LOCAL 4314880 0 200.100.2.1
200.100.3.0 255.255.255.0 RIP 5 2 150.100.5.1
200.100.4.0 255.255.255.0 LOCAL 624135 0 200.100.4.1
200.100.5.0 255.255.255.0 RIP 25 3 200.100.4.2
200.150.1.0 255.255.255.0 RIP 5 2 150.100.5.1
Type: <space> to page; <return> advance 1 line; Q to quit
Command aborted.
[TPE-ASN2]$logout
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 478.1 | use SNIFFER to capture data for ping | TPSPS5::TSCMGR | | Mon May 12 1997 01:16 | 23 |
| use SNIFFER to catch to find out the broadcast packet of SRC is 0.0.0.0
for ping and traceroute as below, but through telnet it's OK.
If ping successful from tu1 interface through WelFleet route to yuta07,
that will be display:
SUMMARY DELTA T_DST SRC
16 0.0002 [153.101.1.1] <<[150.101.1.2] ICMP
ECHO
.
18 0.0240 [150.101.1.2] <<[153.101.1.1] ICMP ECHO
REPLY
If ping fail from tu0 interface through WelFleet route to yuta07, that
will be display:
SUMMARY DELTA T_DST SRC
6 0.0004 [153.101.1.1] <<[0.0.0.0] ICMP
ECHO
Not any protocol for "ICMP ECHO REPLY", Why?
Richard.
|
| 478.2 | Re: Can it support NFS service if ping fail? | QUABBI::"werme@zk3.dec.com" | | Thu May 15 1997 00:36 | 16 |
| tscmgr@tpsps5.enet.dec.com writes:
> If ping fail from tu0 interface through WelFleet route to yuta07, that
> will be display:
> SUMMARY DELTA T_DST SRC
> 6 0.0004 [153.101.1.1] <<[0.0.0.0] ICMP
> ECHO
I think 0.0.0.0 is illegal. At the very least, the server probably can't
figure out how to reply to it. Make sure your tu0 interface is
configured properly. I've seen 0.0.0.0 a couple time on nightly builds,
but I don't think I've seen it on a released kernel. If you can
figure out how to cause it reliably, a QAR may be worthwhile.
--
<> Eric (Ric) Werme <> This space under reconstruction <>
<> <werme@zk3.dec.com> <> <>
[posted by Notes-News gateway]
|
| 478.3 | The tu0 interface is configured correctly. | TPSPS5::TSCMGR | | Thu May 15 1997 01:07 | 13 |
| > Make sure your tu0 interface is
> configured properly. I've seen 0.0.0.0 a couple time on nightly
builds,
They are works fine for ping from tu0 or tu1 interface if it had run
"route flush; kill -9 <PID of routed>; /usr/sbin/routed -q" when the
ping fail from tu0 interface. but I don't know how long is it to keep
good?
We are already post to IPMT because it's a critical case.
Thanks,
Richard.
|