
Diagnostic Parameters and Commands
Using diagnostics-related DO commands
MAX Administration Guide
B-33
Other resets include:
FATAL_PROFILE_BAD = 3
FATAL_SWITCH_TYPE_BAD = 4
FATAL_LIF_FATAL = 5
FATAL_LCD_ERROR = 6
FATAL_ISAC_TIMEOUT = 7
FATAL_SCC_SPURIOUS_INT = 8
The preceding reset is caused by a processor exception error.
FATAL_EXEC_INVALID_SWITCH = 9
FATAL_EXEC_NO_MAIL_DESC = 10
The preceding reset occurs if the MAX unit tries to allocate a mail message and there are none
left. A reset of this type is usually due to a memory leak.
FATAL_EXEC_NO_MAIL_POOL = 11
FATAL_EXEC_NO_TASK = 12
FATAL_EXEC_NO_TIMER = 13
FATAL_EXEC_NO_TIMER_POOL = 14
FATAL_EXEC_WAIT_IN_CS = 15
FATAL_DSP_DEAD = 16
FATAL_DSP_PROTOCOL_ERROR = 17
FATAL_DSP_INTERNAL_ERROR = 18
FATAL_DSP_LOSS_OF_SYNC = 19
FATAL_DSP_UNUSED = 20
FATAL_DDD_DEAD = 21
FATAL_DDD_PROTOCOL_ERROR = 22
FATAL_X25_BUFFERS = 23
FATAL_X25_INIT = 24
FATAL_X25_STACK = 25
FATAL_ZERO_MEMALLOC = 27
FATAL_NEG_MEMALLOC = 28
FATAL_TASK_LOOP = 29
The preceding reset is caused by a software loop.
FATAL_MEMCPY_TOO_LARGE = 30
FATAL_MEMCPY_NO_MAGIC = 31
FATAL_MEMCPY_WRONG_MAGIC = 32
FATAL_MEMCPY_BAD_START = 33
FATAL_IDEC_TIMEOUT = 34
FATAL_EXEC_RESTRICTED = 35
FATAL_STACK_OVERFLOW = 36
FATAL_OPERATOR_RESET = 99
The preceding entry is logged to the fatal-error table when the MAX has been manually reset,
either in diagnostic mode (with the Reset or NVRAMclear commands), through the user
interface, or through MIF.
Instead of a standard stack backtrace, the message includes the active Security profile index.
On a MAX unit the Default profile is number 1, and the Full Access profile is number 9. 0
indicates an unknown security profile.
The reset is logged immediately before the MAX unit goes down.