Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: (ASCEND) 6.1.7 and randomness of the Max IP address....


This is what I get on traceroute from another system on the same LAN:

>From a cisco at 204.27.122.1:
SLC01#traceroute 204.27.122.8 

Type escape sequence to abort.
Tracing the route to 204.27.122.8
  1 204.27.122.8 4 msec 4 msec 4 msec

I'll add some extra info:

SLC01#traceroute 10.1.152.2 (one of the remote PTP addresses)
Type escape sequence to abort.
Tracing the route to 10.1.152.2
  1 204.27.122.8 4 msec 4 msec 4 msec
  2 10.1.152.2 28 msec 28 msec 24 msec
SLC01#ping 10.1.152.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echoes to 10.1.152.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/92/120 ms
SLC01#

from the Ascend in question:
SLA04% ping 10.1.152.2
PING 10.1.152.2 (10.1.152.2): 56 data bytes
^C
--- 10.1.152.2 ping statistics ---
150 packets transmitted, 0 packets received, 100% packet loss
round-trip min/avg/max = 0/0/0 ms

-------------------------------------------------------
Raul Zighelboim   -  504.636.3800  -  Verio Gulf South
rzig@verio.net    -                -  New Orleans,  LA


-|-----Original Message-----
-|From: Mike Hughes [mailto:mike@dircon.net]
-|Sent: Tuesday, August 25, 1998 4:37 AM
-|To: Raul Zighelboim; ascend-users@bungi.com
-|Subject: RE: (ASCEND) 6.1.7 and randomness of the Max IP address....
-|
-|
-|On 24 Aug 98 at 9:00, Raul Zighelboim wrote:
-|
-|> 
-|> Traceroute should respond with the IP of the interface the 
-|packets comes
-|> in; not the one it goes out.  AS least that is how Ascend 
-|routers used
-|> to work, and how all other routers/server/anything with multiple
-|> interfaces behaves.
-|> 
-|> This Max, running this particular software revision from Ascend,
-|> responds with the PTP IP of the _last_ caller.
-|
-|Paul,
-|
-|I have currently got the same problem on my Maxen (6000s running 
-|ebixk.m60 6.1.3/6.1.7), I have opened a ticket with EMEA support 
-|about this. (Ticket #267051)
-|
-|I've been asked to take a trace of the Ethernet traffic on this 
-|segment, because the Ascend Tech I'm working with at Sophia TAC 
-|thinks that the Max is malforming the return ICMP packets.
-|
-|I find that the WAN side address does eventually age out if there is 
-|no-one logged on the box, or if there are only dynamically assigned 
-|users (who don't need a static WAN address on the Max) connected, for 
-|a period of time.
-|
-|Here's something I'd like you to try... 
-|
-|Traceroute the Max ethernet address from a router or machine attached 
-|to the same ethernet. Do you get the correct ethernet address back? 
-|
-|I do, tracing from a Cisco 7200 router to a Max on one of it's 
-|attached Ethernets.
-|
-|Regards,
-|Mike
-|-- 
-|Mike Hughes - Network Services         mike@dircon.net
-|Tel: 0181 297 0300                     http://www.dircon.net/
-|Fax: 0181 463 9820
-|
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>