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

Re: (ASCEND) Weird 0.2.0.0 Route



I logged a Trouble Ticket with Ascend (TR# 186961) by telephone at 9:00 am
CST.  This problem has now been escalated to Level 3 support.....The support
engineer said (and I quote) "We don't know what is happening, I had to go
show them (the level 3 guys) to make them believe that it was reporting a
0.2.0.0 route."

They recommended that I downgrade from 5.1Ap6 to 5.0A in the meantime until
level 3 gets back to me....

My question is.....Has anyone done a downgrade from 5.1Ap6 (or something
close) to 5.0A....This box is at a remote site and I can't drive 5 hours to
reset it if it doesn't come back up after the TLOAD....????

______________________________________

Alex Simpson
Director of Technical Services
NetSolutions Corp

alex@nscorp.net
http://www.nscorp.net
http://www.connect-ed.net

615.367.4404  x101
615.367.3887  fax
615.303.7411  pager

Airport Executive Plaza
1321 Murfreesboro Rd
Suite 721
Nashville, TN  37217
__________________________________

-----Original Message-----
From: daniel@interaccess.com <daniel@interaccess.com>
To: Alex Simpson <alex@nscorp.net>
Cc: ascend-users@bungi.com <ascend-users@bungi.com>
Date: Thursday, February 12, 1998 6:46 PM
Subject: Re: (ASCEND) Weird 0.2.0.0 Route


>> Subject: (ASCEND) Weird 0.2.0.0 Route
>>
>> Weird problem showing up while doing a traceroute....
>
>> ascend% traceroute 38.153.248.1
>> traceroute to 38.153.248.1 (38.153.248.1), 30 hops max, 0 byte packets
>>  1   (0.2.0.0)  390 ms  90 ms  120 ms
>>
>> Any reason that this  0.2.0.0  route is showing up....It is not in any of
>> the routing tables, either in the max or in the pipeline.....Where is it
>> coming from.....?????
>>
>> The Maxen are on 5.0Ap27
>> The Pipe is on  5.1Ap6
>>
>> Anybody got any ideas.....????  We have 5 pipeline 130's connecting to 2
Max
>> 2000's, only 3 of the p130's are exibiting this problem....?????
>
>I would love to know why this is happening also.
>
>We have noticed it appearing on Pipeline 130's that are running the
>5.1 code that connect to Max 4000 series running any version of 5.0 code.
>
>No known solutions as of yet. I am planning on upgrading one of our Maxen
>to see if this will solve the problem.
>__________________________________________________________________________
>Dan Ozanich
>
>Network Engineer
>InterAccess Co.
>168 N. Clinton Street, 2nd Floor
>Chicago, IL. 60661
>
>daniel@interaccess.com
>__________________________________________________________________________
>
>


++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>


Follow-Ups: