Hi Carl, you can find a list of commands run for each commandType in the docs here https://fwd.app/docs/nqe/data-model/type_commandtype/. It doesn’t look like this is a command we associate with commandType, but you can add it as a custom command to reference it in NQE. 

Are you saying that there normal collection commands that we cannot use as a commandType?

I ask as the output is exactly like the syntax of ‘show ip nat statistics’ so the data is coming from somewhere in the normal collection.  I am actually not sure how you could infer some of the information without that specific command on a Cisco device.

I do not want to add custom command if at all possible for the 12k+ devices if we already have the information.  Also will have to wait for another cycle to get information - snapshots and processing takes too long and causes some organizational angst. 

​@CarlB Not all state files (think standard collection commands) are available as a CommandType. It is good to do a short query like this to check which CommandTypes are available for the device you are interested in.

foreach device in network.devices
where device.name == "{put device name here}"
foreach command in device.outputs.commands
select {
  Device: device.name,
  Commands: command.commandType
  }

it is confusing that the state files have names that do not match the show commands.  I believe that is to try and have a “normalized” state file name.  That what is represented would be the same no matter the vendor.

Some state files a explicitly not available to NQE for parsing, because the data is already parsed into the data model.

​@CarlB What data would you want out of that show command?  We can submit a plan to get that command added to CommandType.