<?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 IM&amp;amp;P Publisher stay in fail over mode after downtime in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/im-amp-p-publisher-stay-in-fail-over-mode-after-downtime/m-p/4316713#M45408</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have IM&amp;amp;P 12 (2 node in the cluster)&lt;/P&gt;&lt;P&gt;I created presence redundancy group in the CUCM and activated high availability&lt;/P&gt;&lt;P&gt;Everitng was working fine&lt;/P&gt;&lt;P&gt;Then I have an issue on the IM&amp;amp;P publischer, so it was not available for 5h&lt;/P&gt;&lt;P&gt;During the downtime, any new created jabber user was not able to longin, when I check her status in the server, those user are unassigned&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then the publusher get back to UP&lt;/P&gt;&lt;P&gt;see below the status of the 2 node&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;publicher :&lt;BR /&gt;sever state : Failed over&lt;BR /&gt;reason : initialization&lt;BR /&gt;Suscriber :&lt;BR /&gt;server state Running in backup mode&lt;BR /&gt;reason : peer down&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now that the publische get back to up and stack in failover status, any new created jabber user cannot login, when I check those new user status in the server, those user are unassigned&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why user are not automaticaly assigned when the publischer is in failover status ?&lt;/P&gt;&lt;P&gt;How can I assigne those user to the suscriber when publischer has stacked in failover status ?&lt;/P&gt;&lt;P&gt;Why the publischer stack in fail over ?&lt;/P&gt;&lt;P&gt;How can I do to have automatic fallback in this case ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 31 Mar 2021 11:40:43 GMT</pubDate>
    <dc:creator>nicanor00</dc:creator>
    <dc:date>2021-03-31T11:40:43Z</dc:date>
    <item>
      <title>IM&amp;P Publisher stay in fail over mode after downtime</title>
      <link>https://community.cisco.com/t5/collaboration-applications/im-amp-p-publisher-stay-in-fail-over-mode-after-downtime/m-p/4316713#M45408</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have IM&amp;amp;P 12 (2 node in the cluster)&lt;/P&gt;&lt;P&gt;I created presence redundancy group in the CUCM and activated high availability&lt;/P&gt;&lt;P&gt;Everitng was working fine&lt;/P&gt;&lt;P&gt;Then I have an issue on the IM&amp;amp;P publischer, so it was not available for 5h&lt;/P&gt;&lt;P&gt;During the downtime, any new created jabber user was not able to longin, when I check her status in the server, those user are unassigned&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then the publusher get back to UP&lt;/P&gt;&lt;P&gt;see below the status of the 2 node&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;publicher :&lt;BR /&gt;sever state : Failed over&lt;BR /&gt;reason : initialization&lt;BR /&gt;Suscriber :&lt;BR /&gt;server state Running in backup mode&lt;BR /&gt;reason : peer down&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now that the publische get back to up and stack in failover status, any new created jabber user cannot login, when I check those new user status in the server, those user are unassigned&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why user are not automaticaly assigned when the publischer is in failover status ?&lt;/P&gt;&lt;P&gt;How can I assigne those user to the suscriber when publischer has stacked in failover status ?&lt;/P&gt;&lt;P&gt;Why the publischer stack in fail over ?&lt;/P&gt;&lt;P&gt;How can I do to have automatic fallback in this case ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Mar 2021 11:40:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/im-amp-p-publisher-stay-in-fail-over-mode-after-downtime/m-p/4316713#M45408</guid>
      <dc:creator>nicanor00</dc:creator>
      <dc:date>2021-03-31T11:40:43Z</dc:date>
    </item>
    <item>
      <title>Re: IM&amp;P Publisher stay in fail over mode after downtime</title>
      <link>https://community.cisco.com/t5/collaboration-applications/im-amp-p-publisher-stay-in-fail-over-mode-after-downtime/m-p/4386389#M45493</link>
      <description>&lt;P&gt;Hi Nicanor,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It is expected that when the HA of the IM&amp;amp;P Servers is in the wrong state, the users cannot be assigned automatically nor manually to one of the servers.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the IM&amp;amp;P Publisher server is in failed status and you want to assign the users to the subscriber, only two options can be performed:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Fix the problem with the IM&amp;amp;P Publisher and recover the HA so it can be normal/normal again.&lt;/LI&gt;
&lt;LI&gt;Disable the HA, save, and then assign manually the users.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;To know why the IM&amp;amp;P Server is stuck on a failed status, several situations should be taken into account:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Was there a reboot of a monitored service and HA was not disabled?
&lt;UL&gt;
&lt;LI&gt;Keep in mind that HA requires to be disabled if the server is to be rebooted or the following services will be restarted: A Cisco DB, Presence Engine or XCP Router.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;Maybe there was a network disconnection that overpasses the heartbeats keep alive, and that broke the HA&lt;/LI&gt;
&lt;LI&gt;Are all the services started on the IM&amp;amp;P Publisher?&lt;/LI&gt;
&lt;LI&gt;Some other options like a core dump or something that should be investigated via the Service Recovery Manager logs&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Automatic fallback is disabled by default to avoid saturation in the network traffic:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;But can be enabled by going to&amp;nbsp;&lt;FONT color="#800080"&gt;CUCM &amp;gt; Service Parameters Configuration &amp;gt; IMP &amp;gt; Cisco Recovery Manager &amp;gt; Enable automatic Fallback &amp;gt; set it to Ture.&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI&gt;Another solution is to disable the HA &amp;gt; save &amp;gt; Enable HA &amp;gt; save, which will resets the communication and fix the HA wrong state.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Apr 2021 18:52:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/im-amp-p-publisher-stay-in-fail-over-mode-after-downtime/m-p/4386389#M45493</guid>
      <dc:creator>Miguel E Castillo Torres</dc:creator>
      <dc:date>2021-04-13T18:52:33Z</dc:date>
    </item>
  </channel>
</rss>

