EEM Scripting not start

[frankieng]

The EEM script to monitor the te0/0/0/0, Output Data Rate has amount of bps, then open the cli for some interface configuration.

After commit the EEM.tcl file

RP/0/RSP0/CPU0:ASR9K#show event manager policy registered

Tue Mar 12 02:15:58.462 HKT

No.  Class     Type    Event Type          Trap  Time Registered           Name

1    script    user    statistics          Off   Tue Mar 12 01:42:48 2013  EEM.tcl

name {ifstats-datarate} modifier_1 {Te0/0/0/0} modifier_2 {OutputDataRate}

entry_op gt entry_val {3600} exit_comb and exit_op ne exit_val {36000}

exit_time_sec 900 exit_time_nsec 0 poll_interval_sec 5 poll_interval_nsec 0

nice 0 queue-priority normal maxrun 20.000 scheduler rp_primary Secu none

persist_time: 3600 seconds,  username: cisco

RP/0/RSP0/CPU0:ASR9K#show interfaces tenGigE 0/0/0/0 | inc rate

Tue Mar 12 02:17:08.651 HKT

  30 second input rate 0 bits/sec, 0 packets/sec

  30 second output rate 7599301000 bits/sec, 6205537 packets/sec

The ten 0/0/0/0 is overed value 3600, but the script still not run.

What is problem? attached the TCL file

[Joe Clarke]

The script looks okay to me (at least the ED line).  How do you know it's not running?  Is it not showing up in the event history?

[frankieng]

Because the scripting should apply for service policy to te0/0/0/1.106 but the policy not applied to the interface.

RP/0/RSP0/CPU0:ASR9K#show policy-map interface tenGigE 0/0/0/1.106

Tue Mar 12 02:48:50.846 HKT

TenGigE0/0/0/1.106 direction input: Service Policy not installed

TenGigE0/0/0/1.106 direction output: Service Policy not installed

Therefore, it seen not start

[Joe Clarke]

That's what I thought.  The policy may be running, though.  Can you check the output of "show event manager history events" to see if it's getting triggered.

[frankieng]

The platform is ASR9000 with 4.1.2, no "show event manager histroy events"

RP/0/RSP0/CPU0:ASR9K#show event manager ?

  directory         Embedded Event Manager directory information

  environment       Global variables for policies

  metric            Metric data

  policy            Policy information

  refresh-time      Refresh time for policy username's AAA taskId

  statistics-table  Supported statistics counters

  trace             Show trace data for EEM component

[Joe Clarke]

Enable debugging for EEM then reregister the policy (no it, commit, re-configure it, commit).  Then post the output while the output rate is sufficiently high.

[Joe Clarke]

See this thread.  Looks like the interface name needs to be specified in a specific way:

https://supportforums.cisco.com/message/3891999#3891999