<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic SOAP selectCmDevice - need to search on subnet in Management</title>
    <link>https://community.cisco.com/t5/management/soap-selectcmdevice-need-to-search-on-subnet/m-p/3527307#M1593</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As far as I can tell, the only wildcard option in the Item field (where I'm putting my IP address as search criteria), is to put a '*' at the end of my string. This doesn't allow me to search small subnets where maybe the last octet I only want to match on values 4-7 for instance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone know of a way to use either regular expression, or IPV4 subnet-based wildcarding in the selectCmDevice request?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 20 Nov 2015 15:15:16 GMT</pubDate>
    <dc:creator>alangfor</dc:creator>
    <dc:date>2015-11-20T15:15:16Z</dc:date>
    <item>
      <title>SOAP selectCmDevice - need to search on subnet</title>
      <link>https://community.cisco.com/t5/management/soap-selectcmdevice-need-to-search-on-subnet/m-p/3527307#M1593</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As far as I can tell, the only wildcard option in the Item field (where I'm putting my IP address as search criteria), is to put a '*' at the end of my string. This doesn't allow me to search small subnets where maybe the last octet I only want to match on values 4-7 for instance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone know of a way to use either regular expression, or IPV4 subnet-based wildcarding in the selectCmDevice request?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Nov 2015 15:15:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/soap-selectcmdevice-need-to-search-on-subnet/m-p/3527307#M1593</guid>
      <dc:creator>alangfor</dc:creator>
      <dc:date>2015-11-20T15:15:16Z</dc:date>
    </item>
    <item>
      <title>Re: SOAP selectCmDevice - need to search on subnet</title>
      <link>https://community.cisco.com/t5/management/soap-selectcmdevice-need-to-search-on-subnet/m-p/3527308#M1594</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not aware of any additional wildcards.&amp;nbsp; If your example covers just 4 IPs, could you build out the IPs and submit them, e.g.:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SelectCmDevice&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;Items[4]:&lt;/P&gt;&lt;P&gt;Item: 192.168.0.4&lt;/P&gt;&lt;P&gt;Item: 192.168.0.5&lt;/P&gt;&lt;P&gt;Item: 192.168.0.6&lt;/P&gt;&lt;P&gt;Item: 192.168.0.7&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Nov 2015 15:28:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/soap-selectcmdevice-need-to-search-on-subnet/m-p/3527308#M1594</guid>
      <dc:creator>dstaudt</dc:creator>
      <dc:date>2015-11-20T15:28:58Z</dc:date>
    </item>
    <item>
      <title>Re: SOAP selectCmDevice - need to search on subnet</title>
      <link>https://community.cisco.com/t5/management/soap-selectcmdevice-need-to-search-on-subnet/m-p/3527309#M1595</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was afraid of that. The only problem is that it doesn't scale well and in reality I have thousands of subnets to potentially divide up. I appreciate the feedback on this one. Hopefully they include the concept of subnet sizing into the IPV4 search field in the future.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Nov 2015 15:34:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/management/soap-selectcmdevice-need-to-search-on-subnet/m-p/3527309#M1595</guid>
      <dc:creator>alangfor</dc:creator>
      <dc:date>2015-11-20T15:34:06Z</dc:date>
    </item>
  </channel>
</rss>

