09-13-2017 06:39 PM - edited 03-08-2019 12:01 PM
Hi,
Has anyone experienced the problem where a default interface command causes the module to reset?
For instance
default int e1/10 - 11
The command above resets module 1.
We are using version 6.2(16).
TIA
PF
09-13-2017 07:27 PM
Hi,
I have never seen that. You may want to upgrade to a newer version (7.x) and test again. If not you may have to RMA the module back to Cisco.
HTH
09-13-2017 07:37 PM
Thanks Reza, this is the error messages on the log
2017 Sep 14 10:51:08.546 TP-H7-CSW-01 %SYSMGR-SLOT1-2-SERVICE_CRASHED: Service "aclqos" (PID 2376) hasn't caught signal 11 (core will be saved).
2017 Sep 14 10:51:12.681 TP-H7-CSW-01 %SYSMGR-SLOT1-2-SERVICE_CRASHED: Service "aclqos" (PID 29925) hasn't caught signal 11 (core will be saved).
2017 Sep 14 10:51:16.904 TP-H7-CSW-01 %SYSMGR-SLOT1-2-SERVICE_CRASHED: Service "aclqos" (PID 29982) hasn't caught signal 11 (core will be saved).
Thanks.
PF
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide