@RedNectar Thanks for your reply. I didn't know you could set variables in bash but that makes sense, so that is cool!
In looking at it, your query is basically like what I was doing using grep without variables, and I'm guessing filtering using grep will be the only way to get the information I need in this particular case. Basically I will have to get all interfaces in a certain state (i.e. all "down" interfaces), and then filter the output and see if my particular interface is in the list.
So, let's say I wanted to see if eth1/6 was down on node 216, I would use this command and see if I got any output:
moquery -c ethpmPhysIf -f 'ethpm.PhysIf.operSt=="down"' | grep node-216 | grep eth1/6
If I did get a line of output, it means the interface is down. If I didn't get any output, I could change the .operSt filter to "up" and run the command again to confirm the interface is up. So that is probably the best solution in this case. Thanks for the confirmation of my syntax, and also that there might be a bug in filtering the dn on the ethpmPhysIf class!
SIDE NOTE:
Interestingly, in my searching Google for moquery stuff I ended up reading a little bit of a blog post yesterday without knowing it was yours, and you mentioned using awk filtering (which I then became very curious about, and discovered awk stands for the inventors of it, Aho, Weinberger, and Kernighan). Compared to grep (created of course by Ken Thompson, "get [regular expression] print" ) , awk definitely gives better performance when parsing large files/output since awk is stream-based, so it doesn't need to read the whole file/output into memory before it begins parsing for matches. The only caveat with awk is it is a bit more difficult/awkward (pun intended) to format a command with awk than with grep
So we can achieve the same result as above using awk :
moquery -c ethpmPhysIf -f 'ethpm.PhysIf.operSt=="down"' | awk '{if (($3 ~ "node-216") && ($3 ~ "eth1/6")) print $3}'
But of course that is much more difficult to type on the fly, and for this small of a result set awk only gives about 1 second of improved performance over grep, so in this case using grep would be more desirable. However, I could definitely see a good use for awk in ACI for parsing through large result sets, such as ACI log messages. So, I appreciate you mentioning awk in your blog post, as it gave me another option to have in my toolkit for filtering ACI output!
0xD2A6762E
