(ASCEND) MAX 4000 rebooting with fatalhistory reporting Index 185

["Davar, Vikram" <vikram.davar@gs.com>]

Hi,

We have been seeing some strange occurrences with our MAX 4000 running
4.6Bp26 in that it is seen to periodically reboot. A fatalhistory
display in debug mode shows 4 to 6 occurrences of a WARNING: Index: 185
error with a memory location and then a SYSTEM IS UP Index:100 message.

Has anyone seen a similar occurrence? What exactly does an Index: 185
warning point to?

Thanks.

Vik Davar
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.shore.net/~dreaming/ascend-faq>
or		<ftp://ftp.shore.net/members/dreaming/ascend-faq.txt>

---

Follow-Ups:

• Re: (ASCEND) MAX 4000 rebooting with fatalhistory reporting Index 185
• From: Kevin Smith <kevin@ascend.com>
• Re: (ASCEND) MAX 4000 rebooting with fatalhistory reporting Index 185
• From: Jason Nealis <nealis@babylon.erols.com>

---

• Prev by Date: (ASCEND) 5.0Ai10 breaks route table
• Next by Date: (ASCEND) Duplicate User Information in (SNMP) callStatusGroup
• Prev by thread: (ASCEND) MAX, Win95 PPP and callback: might not SLIP work?
• Next by thread: Re: (ASCEND) MAX 4000 rebooting with fatalhistory reporting Index 185
• Index(es):
  • Main
  • Thread