<?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 Re: Lookup with CIDR in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82245#M20878</link>
    <description>&lt;P&gt;Hmm, I get:&lt;/P&gt;

&lt;P&gt;[DT-SPLK-Idx] Error 'Could not find all of the specified destination fields in the lookup table.' for conf 'ipam' and lookup table 'ipam'.&lt;/P&gt;

&lt;P&gt;After cutting and pasting your suggestion above.  &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;  Thanks though!&lt;/P&gt;</description>
    <pubDate>Tue, 02 Jul 2013 16:43:31 GMT</pubDate>
    <dc:creator>ccsfdave</dc:creator>
    <dc:date>2013-07-02T16:43:31Z</dc:date>
    <item>
      <title>Lookup with CIDR</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82243#M20876</link>
      <description>&lt;P&gt;Greetings, &lt;/P&gt;

&lt;P&gt;I feel like this shouldn't be rocket science,but I just can't make it work.&lt;/P&gt;

&lt;P&gt;Our internal network is pretty complicated with IPs assigned to departments in pretty granular form.  I would like to do the hard work ahead of time and put our IPAM (IP Address Management) into a lookup table.  I am trying on a very small sample first to get it working then will add the rest.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;transforms.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[ipam]&lt;BR /&gt;
filename = ipam.csv&lt;BR /&gt;
match_type = CIDR(src_ip)&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[ipam]&lt;BR /&gt;
LOOKUP-ipam = ipam Dept OUTPUTNEW Department&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;ipam.csv&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;src_ip,Dept&lt;BR /&gt;
10.17.101.0/16,Some_Dept_Name&lt;BR /&gt;
10.17.102.0/15,Some_Dept_Name&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;So if I do a search of 10.17.10*.* I would like to get a new Department field created with the value of Rec and Park assigned to it.&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;

&lt;P&gt;Dave&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2013 16:23:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82243#M20876</guid>
      <dc:creator>ccsfdave</dc:creator>
      <dc:date>2013-07-02T16:23:41Z</dc:date>
    </item>
    <item>
      <title>Re: Lookup with CIDR</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82244#M20877</link>
      <description>&lt;P&gt;Your lookup should probably be something like:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[ipam]
LOOKUP-ipam = ipam src_ip OUTPUTNEW Dept AS Department
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I've note tested/tried this as I normally don't use the automatic lookups (for some reason).    &lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2013 16:38:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82244#M20877</guid>
      <dc:creator>MHibbin</dc:creator>
      <dc:date>2013-07-02T16:38:12Z</dc:date>
    </item>
    <item>
      <title>Re: Lookup with CIDR</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82245#M20878</link>
      <description>&lt;P&gt;Hmm, I get:&lt;/P&gt;

&lt;P&gt;[DT-SPLK-Idx] Error 'Could not find all of the specified destination fields in the lookup table.' for conf 'ipam' and lookup table 'ipam'.&lt;/P&gt;

&lt;P&gt;After cutting and pasting your suggestion above.  &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;  Thanks though!&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2013 16:43:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82245#M20878</guid>
      <dc:creator>ccsfdave</dc:creator>
      <dc:date>2013-07-02T16:43:31Z</dc:date>
    </item>
    <item>
      <title>Re: Lookup with CIDR</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82246#M20879</link>
      <description>&lt;P&gt;@ccsfdave, Hmmm... try changing the &lt;CODE&gt;src_ip&lt;/CODE&gt; field in your lookup to &lt;CODE&gt;srcip&lt;/CODE&gt;, and then change it in you transforms.conf. Then change the props.conf to the following:&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;LOOKUP-ipam = ipam srcip AS src_ip OUTPUTNEW Dept AS Department&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jul 2013 09:46:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82246#M20879</guid>
      <dc:creator>MHibbin</dc:creator>
      <dc:date>2013-07-03T09:46:42Z</dc:date>
    </item>
    <item>
      <title>Re: Lookup with CIDR</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82247#M20880</link>
      <description>&lt;P&gt;So I am half way there, I will actually open a separate answer for the next issue because it is not directly related to making the lookup work.  &lt;/P&gt;

&lt;P&gt;The issue here was that in the props, the bracketed words are a sourcetype.  The documentation was either missing this detail or I skimmed over it.  Hopefully this post will help someone else.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;transforms.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[ipam]&lt;BR /&gt;
filename = ipam.csv&lt;BR /&gt;
match_type = CIDR(src_ip)&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[cisco_asa]&lt;BR /&gt;
LOOKUP-ipam = ipam src_ip OUTPUTNEW Dept AS Department&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;ipam.csv&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;src_ip,Dept&lt;BR /&gt;
10.17.101.0/16,Some_Dept_Name&lt;BR /&gt;
10.17.102.0/15,Some_Dept_Name&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jul 2013 14:31:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82247#M20880</guid>
      <dc:creator>ccsfdave</dc:creator>
      <dc:date>2013-07-03T14:31:13Z</dc:date>
    </item>
    <item>
      <title>Re: Lookup with CIDR</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82248#M20881</link>
      <description>&lt;P&gt;I completely overlooked that!&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jul 2013 15:57:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82248#M20881</guid>
      <dc:creator>MHibbin</dc:creator>
      <dc:date>2013-07-03T15:57:19Z</dc:date>
    </item>
    <item>
      <title>Re: Lookup with CIDR</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82249#M20882</link>
      <description>&lt;P&gt;MHibbin,&lt;/P&gt;

&lt;P&gt;So do I need the same stanza for each source type in props.conf?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jul 2013 18:34:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Lookup-with-CIDR/m-p/82249#M20882</guid>
      <dc:creator>ccsfdave</dc:creator>
      <dc:date>2013-07-03T18:34:26Z</dc:date>
    </item>
  </channel>
</rss>

