Using REST you can see the configs using
http : //<IP>/spectrum/restful/model/0x111d00?attr=0x82002b
This gives you some text which is basically interger numbers with '.' inbetween. if you loop through each number and convert it to an ascii character you get the config (letter by letter). Granted there are some non-printable characters like newline as well.
Now when I look at the vnmshell it displays hex values between full-stops. (why is this different than the REST output? The hex characters are not the equivalent to the REST info - perhaps encoded? if so - how to decode them?)
I've seen this type of thing before where values are sometimes displayed as hex for example and then in other places as integers - e.g. model Handles.
Firstly: please standardise
Secondly: I'm not sure why when I do something like:
<?xml version="1.0" encoding="UTF-8"?>
<rs:model-request throttlesize="1000"
xmlns:rs="http://www.ca.com/spectrum/restful/schema/request"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.ca.com/spectrum/restful/schema/request ../../../xsd/Request.xsd">
<rs:target-models>
<rs:models-search>
<rs:search-criteria
xmlns="http://www.ca.com/spectrum/restful/schema/filter">
<filtered-models>
<and>
<has-substring>
<attribute id="0x82002b">
<value>110.111.32.105.112.32.100.104.99.112</value>
</attribute>
</has-substring>
<equals>
<attribute id="0x10000">
<value>HostConfiguration</value>
</attribute>
</equals>
</and>
</filtered-models>
</rs:search-criteria>
</rs:models-search>
</rs:target-models>
<rs:requested-attribute id="0x1006e"/>
<rs:requested-attribute id="0x10000"/>
<rs:requested-attribute id="0x129fa"/>
</rs:model-request>
it seems to return all HostConfiguration models matching (note text equates to 'no ip dhcp' which I know is definitely only in the latest config.)
Once we know what to look for we would just need to convert the string you are looking for in the config - into some hex/ascii/etc and in theory it should work - but in my case even though it shows in a certain format using REST, it seems the XML search-criteria needs to be different.