Customer-signing of EEM policies is not yet feasible. Only the Cisco trustpoint is supported, and when that is enabled, unsigned policies cannot run. More flexible signing support for EEM Tcl policies is coming in a future version of EEM.
EEM 3.4 should support third party signing of Tcl policies. As to whether or not byte-code compiled policies will be supported is uncertain. However, you should be able to sign a byte-code compiled Tcl script (regular Tcl script, and not EEM policy) by putting the signature after the closing tbcload '}'. I assume the same thing will eventually be doable with EEM.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...