I had an issue recently with an AIM-CUE giving me memory exceptions when I attempted to connect to it using the service-module service-engine 0/0 session commnad. Try a full power off reboot of the router to fully reset the CUE module, then when you try to session into the AIM-CUE try using telnet to connect to the router. Getting a session to the AIM-CUE from a console connection before it was configured would lock up my console port on my router, but if I connected to the router via telnet first it seemed to work fine.
A 'show version' and 'show stack' from the router would also be good. Then we can take a look at the crash. Most likely this would be better handled in a TAC case since there's probably some defect that should be linked to. Right now I'm not aware of any such issue where the system would just reboot (does it do this constantly?) with the AIM-CUE installed with that version of IOS.
sh ver and sh stack are here:
Cisco IOS Software, 2800 Software (C2800NM-SPSERVICESK9-M), Version 12.4(2)T, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Thu 23-Jun-05 22:32 by kellmill
ROM: System Bootstrap, Version 12.3(8r)T7, RELEASE SOFTWARE (fc1)
CCME uptime is 4 hours, 30 minutes
System returned to ROM by power-on
System restarted at 15:16:12 CETDST Thu Oct 6 2005
System image file is "flash:c2800nm-spservicesk9-mz.124-2.T.bin"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
If you require further assistance please contact us by sending email to
Cisco 2821 (revision 53.51) with 249856K/12288K bytes of memory.
Processor board ID FCZ0928701W
2 Gigabit Ethernet interfaces
31 Serial interfaces
4 ISDN Basic Rate interfaces
1 terminal line
1 Channelized E1/PRI port
1 cisco service engine(s)
DRAM configuration is 64 bits wide with parity enabled.
239K bytes of non-volatile configuration memory.
62720K bytes of ATA CompactFlash (Read/Write)
Configuration register is 0x2102
Minimum process stacks:
4752/6000 USB Startup
5204/6000 VIC_BRI_I3086 BACKGROUND
5332/6000 SPAN Subsystem
5156/6000 DIB error message
2308/3000 allegro libretto init
59136/60000 script background loader
5340/6000 vidb clone Process
5148/6000 RADIUS INITCONFIG
2104/3000 Rom Random Update Process
1292/6000 TFTP Server
8980/12000 HTTP CP
Interrupt level stacks:
Level Called Unused/Size Name
1 360363 5848/9000 Network interfaces
2 176703 8560/9000 DMA/Timer Interrupt
3 1 8288/9000 PA Management Int Handler
4 4 8616/9000 Console Uart
5 0 9000/9000 External Interrupt
7 4088802 8568/9000 NMI Interrupt Handler
Sorry for all the questions...do you have the configuration, as well? This looks like it may be something new, so I'm wondering what's so special about this particular deployment.
This stack trace doesn't help because the last startup cause was power-on (i.e. it was powered off an on so the stack trace of the crash was lost). We either need to get the actual stack trace of a crash, or a log of the thing as it's rebooting since it should be spitting out error messages or something as it's going down.