12-21-2015 03:22 PM
Hi, we have TCL Script configured in the Cisco 2921 Router to bounce the voice ports by forcing other Voice Port to DORMANT State.
TCS Script:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
event manager applet forcedshut
event snmp oid 1.3.6.1.2.1.2.2.1.8.16 get-type exact entry-op eq entry-vatry-type value exit-op eq exit-val "5" exit-type value poll-interval 3
action 1.0 syslog msg "Disconnecting Paging"
action 2.0 cli command "en"
action 3.0 cli command "conf t"
action 4.0 cli command "voice-port 0/1/1"
action 5.0 cli command "shut"
action 6.0 wait 2
action 7.0 cli command "no shut"
action 8.0 cli command "exit"
!
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
This Script is working fine for routers which have 2 Voice E&M ports and the non-working stores have 4:
WORKING:
3 Gigabit Ethernet interfaces
1 Serial interface
1 terminal line
12 Voice FXO interfaces
8 Voice FXS interfaces
2 Voice E & M interfaces
NON-WORKING:
3 Gigabit Ethernet interfaces
1 Serial interface
1 terminal line
12 Voice FXO interfaces
8 Voice FXS interfaces
4 Voice E & M interfaces
Both of them are running in same router model/ version of IOS.
Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.2(2)T2, RELEASE SOFTWARE (fc1)
ROM: System Bootstrap, Version 15.0(1r)M9, RELEASE SOFTWARE (fc1)
System image file is "flash0:c2900-universalk9-mz.SPA.152-2.T2.bin"
Cisco CISCO2921/K9 (revision 1.0)
Can Dev Team take a look and let us know how to troubleshoot this one further?
Thanks, Janaki
12-21-2015 04:08 PM
That's a real shot from the past. I didn't think anyone used E&M anymore.
I have this vague memory that on four port cards that the first two ports were linked, and the second two ports were linked. So if you shut down either of the first two ports both got shutdown. It may have been that you had to shutdown the first of the two ports as well, rather than the second of the two. Ditto with the second two. But this was a long time ago, and may not apply any more.
Does using the "clear" command instead resolve the issue?
If you really think this is a bug you need to open a case with Cisco TAC.
12-22-2015 02:10 PM
Thanks for your response, nope still it is not working. Already I have opened a TAC but been told to post my questions here to get response from Developer Team.
12-22-2015 02:28 PM
If you manually go to that interface, do a "shut" and then a "no shut" does it also fail to work?
12-23-2015 02:18 PM
Yes I have tested this today but still not working.
12-23-2015 03:44 PM
Then this has nothing to do with EEM. Open your TAC case and don't mention EEM at all. Tell them you have an issue with the desired shut/no shut behavior.
12-24-2015 07:40 AM
Thanks Joe for your comments, will check with the TAC and keep us posted on updates.
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