<?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 ISE 2.3 - Session directory write failed in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-3-session-directory-write-failed/m-p/4005700#M454707</link>
    <description>&lt;P&gt;&lt;SPAN&gt;I'm getting these errors ever since swapping the M&amp;amp;T role to the secondary ISE server.&amp;nbsp; The secondary server was recently migrated to an all flash array because we were having I/O issues&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Alarm Name :&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Log Collection Error&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Details :&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Session directory write failed&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Description :&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The ISE M&amp;amp;T collector process is unable to persist the audit logs generated from the Policy Service nodes&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Severity :&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Warning&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Suggested Actions :&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;This will not impact the actual functionality of the Policy Service nodes, Please contact TAC&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;*** This message is generated by Cisco Identity Services Engine (ISE) ***&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Sent By Host : &amp;lt;name&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 02 Jan 2020 18:32:52 GMT</pubDate>
    <dc:creator>pnowikow</dc:creator>
    <dc:date>2020-01-02T18:32:52Z</dc:date>
    <item>
      <title>ISE 2.3 - Session directory write failed</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-session-directory-write-failed/m-p/4005700#M454707</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I'm getting these errors ever since swapping the M&amp;amp;T role to the secondary ISE server.&amp;nbsp; The secondary server was recently migrated to an all flash array because we were having I/O issues&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Alarm Name :&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Log Collection Error&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Details :&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Session directory write failed&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Description :&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The ISE M&amp;amp;T collector process is unable to persist the audit logs generated from the Policy Service nodes&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Severity :&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Warning&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Suggested Actions :&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;This will not impact the actual functionality of the Policy Service nodes, Please contact TAC&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;*** This message is generated by Cisco Identity Services Engine (ISE) ***&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Sent By Host : &amp;lt;name&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jan 2020 18:32:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-session-directory-write-failed/m-p/4005700#M454707</guid>
      <dc:creator>pnowikow</dc:creator>
      <dc:date>2020-01-02T18:32:52Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.3 - Session directory write failed</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-session-directory-write-failed/m-p/4005929#M454708</link>
      <description>&lt;P&gt;Have you Stopped and started the ISE &amp;nbsp;application since promoting the Secondary to active MnT? I don’t think it’s mandatory but in this case it might be a good first step. &amp;nbsp;I assume this node has same spec as the Primary? When you say “migrated”, did that involve a live migration like vMotion?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;sounds like a TAC case to me if you haven’t already got one.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jan 2020 09:03:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-session-directory-write-failed/m-p/4005929#M454708</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2020-01-03T09:03:19Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.3 - Session directory write failed</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-session-directory-write-failed/m-p/4006091#M454711</link>
      <description>I haven't yet stopped and started ISE application on the secondary PSN&lt;BR /&gt;where the M&amp;amp;T role now lives. Yes, when migrating from one storage array&lt;BR /&gt;to another, we used VMWare's storage vMotion to move it.&lt;BR /&gt;</description>
      <pubDate>Fri, 03 Jan 2020 15:33:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-session-directory-write-failed/m-p/4006091#M454711</guid>
      <dc:creator>pnowikow</dc:creator>
      <dc:date>2020-01-03T15:33:55Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.3 - Session directory write failed</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-session-directory-write-failed/m-p/4006254#M454714</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/978718"&gt;@pnowikow&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;I haven't yet stopped and started ISE application on the secondary PSN&lt;BR /&gt;where the M&amp;amp;T role now lives. Yes, when migrating from one storage array&lt;BR /&gt;to another, we used VMWare's storage vMotion to move it.&lt;BR /&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;keep in mind vMotion is not supported&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.google.com/search?q=ise+2.4+vmotion&amp;amp;oq=ise+2.4+vmotion&amp;amp;aqs=chrome..69i57j0l2j69i64.2734j0j7&amp;amp;sourceid=chrome&amp;amp;ie=UTF-8" target="_blank"&gt;https://www.google.com/search?q=ise+2.4+vmotion&amp;amp;oq=ise+2.4+vmotion&amp;amp;aqs=chrome..69i57j0l2j69i64.2734j0j7&amp;amp;sourceid=chrome&amp;amp;ie=UTF-8&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/identity-services-engine-ise/vmotion-support-for-ise/td-p/3445814" target="_blank"&gt;https://community.cisco.com/t5/identity-services-engine-ise/vmotion-support-for-ise/td-p/3445814&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jan 2020 21:05:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-session-directory-write-failed/m-p/4006254#M454714</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2020-01-03T21:05:12Z</dc:date>
    </item>
  </channel>
</rss>

