Bad Ethernet Connection (was: (ASCEND) Ticket # 828079), Our Ticket, 826776

[Ken Rea <wildcat@pcez.com>]

Looks like we had much the same problem here. This Max 4048 is only a
month old and we had problems with it out of the box. First, a modem card
was bad, then the Ethernet had a intermittent problem.  Ascend told use to
pull the mother board out and re-solder the area of the Ethernet
connector.  We did that, but about 3 weeks later it lost all Ethernet
connections one day and we had to re-boot to get it back on line.  

Ascend gave us a song and dance about how this is a sign of on over loaded
network and it was losing packets. This is not the case, it's on a 100 Mhz
switch and only see 0.3% packet loss to collisions.  Our ticket number is
826776. The serial # of this max is 8531326. 

How old is your max?  Is it fairly new?  I'm wondering if they had a bad
batch.  This is the only max we have this problem with and as I said it is
only about a month old.

Thanks,

Ken Rea



Goh Sek Chye <sekchye@staff.singnet.com.sg> & james <zhz@public1.sta.net.cn>
Wrote:

> From: Goh Sek Chye <sekchye@staff.singnet.com.sg>
> Date: Fri, 2 Apr 1999 09:21:20 +0800 (SST)
> Subject: Re: (ASCEND) Ticket # 828079  
> 
> 	I encountered similar situation with 7.0.4 once.  Need to reboot
> to solve it.  Don't know why it happened.
> 
> On Thu, 1 Apr 1999, Marc Newman wrote:
> 
> #Anyone else seeing the following under 7.0.3 for a Max4004?
> #
> #WARNING:  Index: 1001  Load: ftik.m40 Revision: 7.0.3
> #        Date: 03/31/1999.       Time: 19:44:11
> #        Location: b006fb2c b00711cc b0074c58 b00753d4 b0003e48 b000458c
> #
> #WARNING:  Index: 1001  Load: ftik.m40 Revision: 7.0.3
> #        Date: 03/31/1999.       Time: 19:44:11
> #        Location: b006fb2c b00711cc b0074c58 b00753d4 b0003e48 b000458c
> #
> #WARNING:  Index: 1006  Load: ftik.m40 Revision: 7.0.3
> #        Date: 03/31/1999.       Time: 19:44:11
> #        Location: b006fb48 b00711cc b0074c58 b00753d4 b0003e48 b000458c
> #                                                                           
> #
> #Once it happens, the Max will still answer calls but aparently the
> #ethernet is dead, and the box must be manually rebooted.
> #
> #It happened once a few weeks ago, then twice in two days this week.
> #
> #Marc
> #++ Ascend Users Mailing List ++
> #To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
> #To get FAQ'd:	<http://www.nealis.net/ascend/faq>
> #
> 
> ________________________________
> Goh Sek Chye
> SingNet Network Operations Centre
> - -------------------------------------------------------------------
> PGP Public Key:		finger sekchye@singnet.com.sg
> Key fingerprint =  55 9E FF EA 4D A7 33 25  03 00 3E BF A2 F3 AF 6A
> - -------------------------------------------------------------------
> 
> ++ Ascend Users Mailing List ++
> To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd:	<http://www.nealis.net/ascend/faq>
> 
> ------------------------------
> 
> From: james <zhz@public1.sta.net.cn>
> Date: Fri, 02 Apr 1999 09:37:08 +0800
> Subject: Re: (ASCEND) Ticket # 828079  
> 
> Marc,
> 
> 	we had the same problem too, we are running 6.1.24, Ascend is 
> working hard to fix the problem, the gave me a e-load now.
> 
> regards/james
 

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