<?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 CX Module Console Error in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cx-module-console-error/m-p/2617633#M196221</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Getting below error while trying to console CX module from ASA.&lt;/P&gt;&lt;P&gt;HQ-JNM-ASA/act# session cxsc console&lt;BR /&gt;&lt;STRONG&gt;ERROR: An existing console session is in progress with module cxsc. Only one is allowed at any point in time.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have tried resolving the issue through solution available (clear connection all port &amp;lt; &amp;gt; etc , etc) &amp;nbsp;on internet but with no luck.&lt;/P&gt;&lt;P&gt;ASA / CX module is in production , hence we can't go for reload the unit.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Help requested for alternate and key solution.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rgds&lt;/P&gt;&lt;P&gt;***&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 05:37:34 GMT</pubDate>
    <dc:creator>netbeginner</dc:creator>
    <dc:date>2019-03-12T05:37:34Z</dc:date>
    <item>
      <title>CX Module Console Error</title>
      <link>https://community.cisco.com/t5/network-security/cx-module-console-error/m-p/2617633#M196221</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Getting below error while trying to console CX module from ASA.&lt;/P&gt;&lt;P&gt;HQ-JNM-ASA/act# session cxsc console&lt;BR /&gt;&lt;STRONG&gt;ERROR: An existing console session is in progress with module cxsc. Only one is allowed at any point in time.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have tried resolving the issue through solution available (clear connection all port &amp;lt; &amp;gt; etc , etc) &amp;nbsp;on internet but with no luck.&lt;/P&gt;&lt;P&gt;ASA / CX module is in production , hence we can't go for reload the unit.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Help requested for alternate and key solution.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Rgds&lt;/P&gt;&lt;P&gt;***&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:37:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cx-module-console-error/m-p/2617633#M196221</guid>
      <dc:creator>netbeginner</dc:creator>
      <dc:date>2019-03-12T05:37:34Z</dc:date>
    </item>
    <item>
      <title>Have you tried the published</title>
      <link>https://community.cisco.com/t5/network-security/cx-module-console-error/m-p/2617634#M196222</link>
      <description>&lt;P&gt;Have you tried the published method as described in &lt;A href="http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/116404-problemsolution-product-00.html"&gt;this TAC note&lt;/A&gt;?&lt;/P&gt;&lt;P&gt;If that doesn't work, you can reset the module and it would only affect the inspection of traffic by the CX&amp;nbsp;(assuming your service-policy is fail-open). That would be minimal connectivity impact.&lt;/P&gt;&lt;P&gt;If that's not acceptable then you will have to schedule a maintenance period to do the reset. &amp;nbsp;A working CX normally comes back online within 5 minutes or less.&lt;/P&gt;&lt;P&gt;Why do you need to access the CX console in the first place? Beyond initial setup and TAC troubleshooting there's seldom any call to access the cli as 98% of the settings are configured and verified via PRSM.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Mar 2015 18:13:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cx-module-console-error/m-p/2617634#M196222</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2015-03-11T18:13:28Z</dc:date>
    </item>
  </channel>
</rss>

