hmmm. Well the device deosnt technically have a mac address, the interface does. I am not sure if you can traverse relationships or not with TALES. If you could (again not sure you can), it might look something like ${device/interfaces/eth0/macaddress}

So that report leverages some python stanzas and the layer 2 catalog, not tales expressions. I am sure ther e is a way to do what your asking, but I'm struggling to come up with a way to do it with a native user command, as opposed to using a script to wrap etherwake. If you had a custom DMD script, the user command could call the DMD script which could then leverage python code and traverse the relationships, or use the layer two catalog like the report pack. Once the MAC is know you fire off etherwake. I know thats alot more complicated than you wanted to hear, but maybe someone knows of an easier.

UbuntiLocoL

You can write a python script that returns the macaddress of the device context then access it in a tales expression.

For example, ${device/getMacAddress} where the script is called getMacAddress and is a method extending ZenModel.DeviceClass.

Best,

--Shane

UbuntuLoco:

Alrighty. Good luck!

Best,

--Shane