I have a general question on how to block map commands that support the 'no' option. My feeling is to treat these commands as states (no x y z | x y z).
Here is an example response:
interface t1 1/10/1:3 description "" no shutdown remote-loopback csu no remote-loopback fdl no remote-loopback feac timeout loopback 10 !
I would like to query the "remote-loopback" states so that the query returns the following information (example csu loopback):
RemoteLoopbackCsuState(1/10/1:3) = remote-loopback csu | no remote-loopback csu
This would work great for us but we are having a tough time response mapping this because it contains two words "remote-loopback" "csu" and block mapping doesn't work well for this.
If I response map "shutdown" using block maps I can return the shutdownState() = shutdown | no shutdown. I saw this example and I like the idea for all commands that support the "no" option.
Any ideas on this? I need a good way to handle the "no" option in block maps and return the state. An example block map would be great if you can attach one.