10-03-2011 09:33 AM - edited 03-16-2019 07:17 AM
I'm having a problem at one of our sites where they aren't able to receive incoming calls. When I do a sh log on the router, I keep seeing the ISM module going from STDY to WREG. What is WREG and could this be my problem?
Oct 3 11:18:16: %SRE_SM-6-STATE_CHANGE: ISM0/0 changing state from SERVICE_MODULE_STATE_STDY to SERVICE_MODULE_STATE_WREG
Oct 3 11:18:16: %SRE_SM-6-STATE_CHANGE: ISM0/0 changing state from SERVICE_MODULE_STATE_WREG to SERVICE_MODULE_STATE_STDY
Oct 3 11:19:02: %SRE_SM-6-STATE_CHANGE: ISM0/0 changing state from SERVICE_MODULE_STATE_STDY to SERVICE_MODULE_STATE_WREG
Oct 3 11:19:02: %SRE_SM-6-STATE_CHANGE: ISM0/0 changing state from SERVICE_MODULE_STATE_WREG to SERVICE_MODULE_STATE_STDY
Oct 3 11:19:47: %SRE_SM-6-STATE_CHANGE: ISM0/0 changing state from SERVICE_MODULE_STATE_STDY to SERVICE_MODULE_STATE_WREG
Oct 3 11:19:47: %SRE_SM-6-STATE_CHANGE: ISM0/0 changing state from SERVICE_MODULE_STATE_WREG to SERVICE_MODULE_STATE_STDY
Oct 3 11:20:32: %SRE_SM-6-STATE_CHANGE: ISM0/0 changing state from SERVICE_MODULE_STATE_STDY to SERVICE_MODULE_STATE_WREG
Oct 3 11:20:32: %SRE_SM-6-STATE_CHANGE: ISM0/0 changing state from SERVICE_MODULE_STATE_WREG to SERVICE_MODULE_STATE_STDY
Oct 3 11:21:17: %SRE_SM-6-STATE_CHANGE: ISM0/0 changing state from SERVICE_MODULE_STATE_STDY to SERVICE_MODULE_STATE_WREG
Oct 3 11:21:17: %SRE_SM-6-STATE_CHANGE: ISM0/0 changing state from SERVICE_MODULE_STATE_WREG to SERVICE_MODULE_STATE_STDY
10-04-2011 02:18 PM
Which version of IOS are you running on the router? I just came across the same log messages on 15.2(1)T1. I do not see the messages on 15.1(3)T2.
01-26-2012 08:31 PM
We have the same exact issue now at one of our RS 2921 router, no errors when it was on ios version 15.1 but for CME to support 6945 models we upgraded to version 15.2, now 6945 works but we get the same exact error. Did you open a case with tac ? What was the resolution ?
01-27-2012 03:35 AM
Console into CUE and observe what's happening.
01-27-2012 11:50 AM
Didn't see anything on the console but reloading the module fixed it. No more errors now.
01-27-2012 12:42 PM
I've noticed the same message. Looking at the CUE it looks perfectly normal.
Sent from Cisco Technical Support iPad App
01-27-2012 01:56 PM
I've seen it too. Reloading fixes the issue.
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