Tcl Script Not Executing

[Carlton Patterson]

Hello Community,

I have been working very hard to get the attached script to work. It was working and for some reason it has stopped working.

It has registered successfully, however I keep on getting the following error message when it's due to activate.

Process Forced Exit- MAXRUN timer expired.

    while executing

"if [catch {cli_exec $cli(fd) "show interface [ lindex $interface $i ]"} result] {

    error $result $errorInfo

}"

    invoked from within

"$slave eval $Contents"

    (procedure "eval_script" line 7)

    invoked from within

"eval_script slave $scriptname"

    invoked from within

"if {$security_level == 1} {       #untrusted script

     interp create -safe slave

     interp share {} stdin slave

     interp share {} stdout slave

..."

    (file "tmpsys:/lib/tcl/base.tcl" line 50)

Tcl policy execute failed:

Process Forced Exit- MAXRUN timer expired.

1Process Forced Exit- MAXRUN timer expired.

    while executing

"if [catch {cli_read_drain $cli(fd)} result] {

    error $result $errorInfo

}"

I wonder if someone could take a look and provide some assistance? Really appreciate it.

Cheers

Carlton

[Carlton Patterson]

Hi Joseph,

Now this very interesting (and a little annoying :-)

The following outputs would suggest that script is working fine, but an email isn't sent.

If you could please shed some light on the issue I would really appreciate it.

MX-C3750-FL2-S#show even man p r                         

No.  Class     Type    Event Type          Trap  Time Registered           Secu  Name

1    script    user    timer watchdog      Off   Mon Jul 29 14:03:15 2013  2048  composite_device_health.tcl

name {composite_device_health_interfac} time 120.000

nice 1 queue-priority low maxrun 120.000 scheduler rp_primary

MX-C3750-FL2-S#show even man p ac

Key: p - Priority        :L - Low, H - High, N - Normal, Z - Last

     s - Scheduling node :A - Active, S - Standby

default class - 1 script event

no.  job id      p s status  time of event             event type          name

1    267962      L A running Mon Jul29 19:27:16 2013   timer watchdog      composite_device_health.tcl

MX-C3750-FL2-S#show event  manager history events        

No.  Job Id Proc Status   Time of Event            Event Type         Name

1    267952 Actv success  Mon Jul29 19:07:16 2013  timer watchdog     script: composite_device_health.tcl

2    267953 Actv success  Mon Jul29 19:09:16 2013  timer watchdog     script: composite_device_health.tcl

3    267954 Actv success  Mon Jul29 19:11:16 2013  timer watchdog     script: composite_device_health.tcl

4    267955 Actv success  Mon Jul29 19:13:16 2013  timer watchdog     script: composite_device_health.tcl

5    267956 Actv success  Mon Jul29 19:15:16 2013  timer watchdog     script: composite_device_health.tcl

6    267957 Actv success  Mon Jul29 19:17:16 2013  timer watchdog     script: composite_device_health.tcl

7    267958 Actv success  Mon Jul29 19:19:16 2013  timer watchdog     script: composite_device_health.tcl

8    267959 Actv success  Mon Jul29 19:21:16 2013  timer watchdog     script: composite_device_health.tcl

9    267960 Actv success  Mon Jul29 19:23:16 2013  timer watchdog     script: composite_device_health.tcl

10   267961 Actv success  Mon Jul29 19:25:16 2013  timer watchdog     script: composite_device_health.tcl

MX-C3750-FL2-S#

As you can see, all of the above outputs suggest that the script is running but it won't actually activate.

Any help you can provide would be greatly appreciated.

Cheers

Carlton

[Joe Clarke]

The script only sends email when a threshold is violated.  If there are no violations, the script will not produce any output.  So you'll need to debug the Tcl CLI calls and check the output to make sure the math lines up (the debug will also show if there is a problem running the CLI commands).  Note: you may have to add some debugging "puts" statements to the script if you want to see what the values are for intermediate variables.

[Carlton Patterson]

Joseph,

I hope the previous outputs helps you to shed some light on what might be the problem. However, I was wondering how the line would help with non ip ports:

sh ip int brief | exc Interface|down|\[0-9\]*/\[0-9\]*\\.\[0-9\]*

[Carlton Patterson]

Hi Joseph,

Thanks for sticking with me on this.

A violation is the number of resets exceeding 5.

The following shows resets of 6 from the device with the outputs shown above:

MX-C3750-FL2-S#show int gig 1/0/10

GigabitEthernet1/0/10 is down, line protocol is down (notconnect)

  Hardware is Gigabit Ethernet, address is b0fa.ebc3.128a (bia b0fa.ebc3.128a)

  Description: Desktop PC Floor Second South

  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Auto-duplex, Auto-speed, media type is 10/100/1000BaseTX

  input flow-control is off, output flow-control is unsupported

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input never, output 5d03h, output hang never

  Last clearing of "show interface" counters 2d10h

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     0 packets input, 0 bytes, 0 no buffer

     Received 0 broadcasts (0 multicasts)

     0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 watchdog, 0 multicast, 0 pause input

     0 input packets with dribble condition detected

     0 packets output, 0 bytes, 0 underruns

     0 output errors, 0 collisions, 6 interface resets

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier, 0 PAUSE output

     0 output buffer failures, 0 output buffers swapped out

[Carlton Patterson]

OK Joseph,

I think I've found the problem.

The little thing I forgot to mention is that the 3750 switch is part of a stack of 4 switches, please see log. So, basically, there are 192 interfaces.

As a result, I tried increasing the maxrun and watchdog timer to 3600 but it still didn't activate.

I ran the script on an GNS3 device and it worked fine.

So I'm wondering if I need to tweak the script further to account for the stack?

Cheers

[Carlton Patterson]

Wow!

I meant 208 interfaces, not 192 interfaces

[Carlton Patterson]

Hello Joseph,

Can you let me know what is the maximum time that can be set to maxrun?

I think I figured out why the script won't activate - stated below and I think I need increase the maxrun. However, when I can't get the maxrun to increase above 120, even though I typed 600.

[Carlton Patterson]

Joseph,

I think I have figured out why it didn't work - the script only appears to work on interfaces that are ('connected'). I've been testing the script on unconnected interfaces...

[Joe Clarke · Accepted solution]

Yes, that's the point of adding the "down" bit to the regular expression.  Interfaces that are not up are excluded since you wouldn't typically care about those.

[Carlton Patterson]

Thanks again mate.

Really appreciate it.

Cheers

Carlton

[Joe Clarke]

The maxrun can vary based on platform.  You can try up to 2147483647.