Real Time Ascend Maling List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: (ASCEND) COMPLETE BULLSHIT



What is this dongle thing?

*********** REPLY SEPARATOR ***********

On 10/12/99, at 8:35 PM, Clint Sharp wrote: 

>Do you have the Ethernet dongle on that 6000? Some older 10 Mbit hubs have
>problems with the 10/100 autosensing stuff, and putting that dongle on it
>has fixed the problem on a couple of maxes for me (although the problem
>isn't usually intermittent, it usually just won't work without the
>dongle).
>
>Clint
>
>On Tue, 12 Oct 1999, Troy Settle wrote:
>
>> 
>> 
>> ** it's a software bug--happens to 4048's too.
>> 
>> I *seriously* doubt it.  Out of 11 boxes running 7.0.22, this is the only
>> box it's happened on.
>> 
>> What's different about this box than all the others?
>> 
>> For starters, it has a 10/100 ethernet port.  Ok, that's 3 of the 11.
>> 
>> Now, of those 3, 2 are connected to a 10/100 switch running in 100MB / Full
>> duplex.  These 2 6000's haven't had their ethernet go down, but the Rx and
>> Tx stats are way off.  (100 million packets recieved, only 50k packets
>> transmitted???).
>> 
>> The remaining max is on a 10mbit hub, and is having problems.
>> 
>> There is only 1 warning in the fatal history, and it's not in reference to
>> anything related to ethernet (so Ascend says).
>> 
>> All this leads me to believe that it's a severe problem with the packet
>> and/or hardware drivers for the ethernet interface on the 6000 chassis.
>> 
>> 
>> ** this happened to me too somewhere in 6.1.x--never happened in six months
>> ** running 6.0.10.
>> **
>> ** they told me it was fixed in 7.0.something so i upgraded--then it did it
>> ** again two weeks later.  this only happened to the first one in the
>> ** group--it gets the heaviest load.  then they emailed me 7.0.21e4--never
>> ** happened again.  you would think the patch would be in 7.0.22.
>> 
>> I gave Ascend your name, and they looked up the ticket in question, and said
>> it was an unrelated problem (you were actually seeing errors logged in your
>> fatal history).
>> 
>> **
>> ** i was just thinking about upping to 7.0.22 myself... maybe not now.  let
>> ** us know what support sez--tia
>> 
>> The engineer I spoke with said that the fix in 7.0.21e4 was indeed carried
>> over to 7.0.22.  But, remember the #1 rule of dealing with Ascend: If it
>> ain't broke, don't even *think* of upgrading.
>> 
>> **
>> ** i also asked if boxes running 7.x are compatible with ones on 6.x (like
>> ** for stacking) but the guy implied he is only allowed to answer one
>> ** question per call--lucent cracking the whip.  emailed the question but
>> ** never got an answer.  grrrr...
>> 
>> No help here, other than to say that for a short time, we ran a mixed
>> environment, and we didn't get any complaints.  That could be as simple as
>> nobody's session tried stacking between boxes with different software.
>> 
>> --
>>   Troy Settle
>>   iPlus Internet Services
>> 
>> 
>> ++ Ascend Users Mailing List ++
>> To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
>> To get FAQ'd:	<http://www.nealis.net/ascend/faq>
>> 
>
>++ Ascend Users Mailing List ++
>To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
>To get FAQ'd:	<http://www.nealis.net/ascend/faq>
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>