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

[Goh Sek Chye <sekchye@staff.singnet.com.sg>]

Hi there!  I was also given a new e-load febk.m40.7.0.5e7 two weeks ago.
I loaded it into two max4000 (lets call them MAX A and MAX B) which are
stacked together.

However, a few days later, MAX A started spitting index 179 warning
messeges.  These messages were generated very frequently. ( Around 10 for
every 3 minutes)

Yesterday, MAX A rebooted by itself :p

WARNING:  Index: 179  Load: febk.m40 Revision: 7.0.5e7
        Date: 04/19/1999.       Time: 23:16:02
        Location: b0112a4c b0114c4c b01423a0 b00234c4 b00663b4 00000000

FATAL ERROR:  Index: 8  Load: febk.m40 Revision: 7.0.5e7
        Date: 04/19/1999.       Time: 23:34:48
        Location: b007bf84 b00022c4 b00027d4 b029c804 b01c5aa8 b01c6864

SYSTEM IS UP:  Index: 100  Load: febk.m40 Revision: 7.0.5e7
        Date: 04/19/1999.       Time: 23:36:35

The strange thing is all the while, MAX B is performing fine.  But guess
what? 

After MAX A rebooted by itself, now MAX B is spitting out a lot of index
179 warning messages. I reckon MAX B will be next one to reboot by itself.

You need to run the MAX loaded with this eload for around one week to see
the MAX rebooting by itself. 

Now, I have set up the coredump to capture the coredump during the next
reboot.  I will then send the coredump to Ascend...

One comment:  

the new eload febk.m40.7.0.5e7 does solve the dead ethernet
problem. But now I have this problem of numerous index 179 warning
messages plus a final reboot.  This seems to indicate some stacking
problem with the code....  

Lets hope that after I have sent the coredump to Ascend, this problem can
be fixed and I can deployed the new code and be Y2K compliant :-) 


On Tue, 20 Apr 1999, james wrote:

#Hi ken,
#
#	they gave me a new e-load, 7.0.5e21_fek.m40,  If you want to have a
#test-drive, pls email to me.
#
#regards/james
#
#
#At 06:15 99-4-19 -0700, Ken Rea wrote:
#>
#>They were supposed to give us an e-load for the 6.1.24 software and we
#>never heard back from them.  They said there was one for the 7.0.4 load
#>but we had connection problems with that software and had to move back to
#>6.1.24.  I guess will have to play the "on the phone line for hours" with
#>then to find out what happened. 
#>
#>Ken Rea
#>
#>On Fri, 16 Apr 1999, james wrote:
#>
#>> Hi Ken,
#>> 
#>> 	do you stack the MAX together ? 
#>> 
#>> 	we have some MAX4000 for E1/PRI ISDN access with MAX Stack. we have
#>> problem with software 6.1.24 and 7.0.4 (fek.m40), ascend gave me a e-load
#>> which did not fix the problem.
#>> 
#>> regards/james
#>> 
#>> 
#>> 
#>> 
#>> 
#>> At 07:22 99-4-2 -0800, Ken Rea wrote:
#>> >
#>> >> 	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>
#>> >> #
#>> >
#>> 
#>
#>Ken Rea
#>wildcat@pcez.com
#>
#>
#>
#

________________________________
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>