<?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: Keeping the MC in sync in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336627#M97469</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Still did not work. How can I verify if the url is correct for our installation?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 07 Jan 2005 19:17:31 GMT</pubDate>
    <dc:creator>gbudgbud7</dc:creator>
    <dc:date>2005-01-07T19:17:31Z</dc:date>
    <item>
      <title>Keeping the MC in sync</title>
      <link>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336621#M97461</link>
      <description>&lt;P&gt;What is the best way to ensure the MC database is in sync with the actual running config for a sensor? Currently I remove and re-add the sensor if the MC does not reflect the actual sensor config?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 09:12:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336621#M97461</guid>
      <dc:creator>gbudgbud7</dc:creator>
      <dc:date>2019-03-10T09:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: Keeping the MC in sync</title>
      <link>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336622#M97462</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;there is a script as well that you can run to sync up the mc with sensor &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Usage Ex.&lt;/P&gt;&lt;P&gt;In a browser window type: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="https://" target="_blank"&gt;https://&lt;/A&gt;&lt;SERVER&gt;/ids-config/GPS?class=com.cisco.nm.mdc.ids.common.ReImport.ImportServlet&amp;amp;import-all=true&lt;/SERVER&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;server = name or ip address. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="https://" target="_blank"&gt;https://&lt;/A&gt;&lt;SERVER&gt;/ids-config/GPS?class=com.cisco.nm.mdc.ids.common.ReImport.ImportServlet&amp;amp;import-name=machine1,machine2 &lt;/SERVER&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="https://" target="_blank"&gt;https://&lt;/A&gt;&lt;SERVER&gt;/ids-config/GPS?class=com.cisco.nm.mdc.ids.common.ReImport.ImportServlet&amp;amp;import-ip=10.10.10.1,10.10.10.2&lt;/SERVER&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;btw why it goes off sync?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Dec 2004 21:56:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336622#M97462</guid>
      <dc:creator>nkhawaja</dc:creator>
      <dc:date>2004-12-30T21:56:43Z</dc:date>
    </item>
    <item>
      <title>Re: Keeping the MC in sync</title>
      <link>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336623#M97463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your reply. I will try your sugestions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To answer your question: sometimes our admins may modify a sensor by logging into its own web interface or on the CL&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Dec 2004 22:52:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336623#M97463</guid>
      <dc:creator>gbudgbud7</dc:creator>
      <dc:date>2004-12-30T22:52:16Z</dc:date>
    </item>
    <item>
      <title>Re: Keeping the MC in sync</title>
      <link>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336624#M97464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have some type of permission error to get through. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will keep trying&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Dec 2004 23:13:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336624#M97464</guid>
      <dc:creator>gbudgbud7</dc:creator>
      <dc:date>2004-12-30T23:13:29Z</dc:date>
    </item>
    <item>
      <title>Re: Keeping the MC in sync</title>
      <link>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336625#M97466</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have had time to try running the script from my workstation and I get the following error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"You are not authenticated, and are not allowed to perform this function. You must either be logged into the desktop and then launch this URL, or youmust pass a 'user' and 'password' parameter to use for authentication purposes".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried running it from a terminal window using the rdep client and I got the same error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jan 2005 17:37:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336625#M97466</guid>
      <dc:creator>gbudgbud7</dc:creator>
      <dc:date>2005-01-07T17:37:49Z</dc:date>
    </item>
    <item>
      <title>Re: Keeping the MC in sync</title>
      <link>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336626#M97468</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;try to first login to VMS and keep those windows open. then launch this from a new browser window&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jan 2005 18:09:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336626#M97468</guid>
      <dc:creator>nkhawaja</dc:creator>
      <dc:date>2005-01-07T18:09:46Z</dc:date>
    </item>
    <item>
      <title>Re: Keeping the MC in sync</title>
      <link>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336627#M97469</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Still did not work. How can I verify if the url is correct for our installation?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jan 2005 19:17:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336627#M97469</guid>
      <dc:creator>gbudgbud7</dc:creator>
      <dc:date>2005-01-07T19:17:31Z</dc:date>
    </item>
    <item>
      <title>Re: Keeping the MC in sync</title>
      <link>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336628#M97471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jan 2005 19:40:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336628#M97471</guid>
      <dc:creator />
      <dc:date>2005-01-07T19:40:43Z</dc:date>
    </item>
    <item>
      <title>Re: Keeping the MC in sync</title>
      <link>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336629#M97472</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;nkhawaja&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;looks like user head space issue. I was running the script from the main cisco works window not the MC for IDS Sensors window.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The script is running now. Ill have to wait for the results&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jan 2005 19:52:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/keeping-the-mc-in-sync/m-p/336629#M97472</guid>
      <dc:creator>gbudgbud7</dc:creator>
      <dc:date>2005-01-07T19:52:15Z</dc:date>
    </item>
  </channel>
</rss>

