<?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 Steps for Administration in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-failover-test/m-p/2551454#M89698</link>
    <description>&lt;P&gt;Steps for Administration persona failover testing&lt;/P&gt;&lt;P&gt;1. Stop ISE services on Primary Admin&lt;/P&gt;&lt;P&gt;Primary Admin# application stop ise&lt;/P&gt;&lt;P&gt;2. Log in to the Secondary Admin GUI and manually promote to Primary&lt;/P&gt;&lt;P&gt;3. Wait 10-15 minutes before process is complete&lt;/P&gt;&lt;P&gt;4. Verify ISE services are up on promoted Secondary Admin&lt;/P&gt;&lt;P&gt;Secondary Admin# sh application status ise&lt;/P&gt;&lt;P&gt;5. Promoted Primary Admin checks&lt;/P&gt;&lt;P&gt;Deployment pages shows all nodes are green and in synch&lt;/P&gt;&lt;P&gt;6. User testing to verify successful authentications and logging&lt;/P&gt;&lt;P&gt;Note:&lt;/P&gt;&lt;P&gt;After you promote your secondary Administration node to become the primary Administration&lt;/P&gt;&lt;P&gt;node, you must reconfigure your scheduled Cisco ISE backups in the newly promoted primary&lt;/P&gt;&lt;P&gt;Administration node&lt;/P&gt;&lt;P&gt;because scheduled backups are not replicated from the primary to secondary Administration&lt;/P&gt;&lt;P&gt;node.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;7. After step 6 testing is complete restore original Primary Admin&lt;/P&gt;&lt;P&gt;8. Start ISE services on original Primary Admin&lt;/P&gt;&lt;P&gt;Primary Admin# application start ise&lt;/P&gt;&lt;P&gt;9. Verify ISE services are up on original Primary Admin&lt;/P&gt;&lt;P&gt;Primary Admin# sh application status ise&lt;/P&gt;&lt;P&gt;10. Promoted Primary Admin checks&lt;/P&gt;&lt;P&gt;Deployment pages shows original Primary Admin green and in synch&lt;/P&gt;&lt;P&gt;11. Stop ISE services on Promoted Primary Admin&lt;/P&gt;&lt;P&gt;Secondary Admin# application stop ise&lt;/P&gt;&lt;P&gt;12. Log in to the original Primary Admin GUI and manually promote to Primary&lt;/P&gt;&lt;P&gt;13. Wait 10-15 minutes before process is complete&lt;/P&gt;&lt;P&gt;14. Verify ISE services are up on original Primary Admin&lt;/P&gt;&lt;P&gt;Primary Admin# sh application status ise&lt;/P&gt;&lt;P&gt;15. Promoted Primary Admin checks&lt;/P&gt;&lt;P&gt;Deployment pages shows all nodes are green and in synch&lt;/P&gt;&lt;P&gt;16. User testing to verify successful authentications and logging&lt;/P&gt;&lt;P&gt;Note:&lt;/P&gt;&lt;P&gt;After you promote your secondary Administration node to become the primary Administration&lt;/P&gt;&lt;P&gt;node, you&lt;/P&gt;&lt;P&gt;must reconfigure your scheduled Cisco ISE backups in the newly promoted primary&lt;/P&gt;&lt;P&gt;Administration node&lt;/P&gt;&lt;P&gt;because scheduled backups are not replicated from the primary to secondary Administration&lt;/P&gt;&lt;P&gt;node.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;17. Start ISE services on original Secondary Admin&lt;/P&gt;&lt;P&gt;Secondary Admin# application start ise&lt;/P&gt;&lt;P&gt;18. Verify ISE services are up on original Secondary Admin&lt;/P&gt;&lt;P&gt;Secondary Admin# sh application status ise&lt;/P&gt;&lt;P&gt;19. Primary Admin checks&lt;/P&gt;&lt;P&gt;Deployment pages shows original Secondary Admin green and in synch&lt;/P&gt;&lt;P&gt;20. User testing to verify successful authentications and logging&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 03 Jul 2014 07:56:03 GMT</pubDate>
    <dc:creator>Saurav Lodh</dc:creator>
    <dc:date>2014-07-03T07:56:03Z</dc:date>
    <item>
      <title>Ise failover test</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-failover-test/m-p/2551451#M89691</link>
      <description>&lt;P&gt;As part of an ISE implementation, I want to test ISE failover for Admin, MnT, and PSN personas.&amp;nbsp; Does anyone have an ISE failover test plan or ISE failover test best practices documentation to share?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks much,&lt;/P&gt;&lt;P&gt;David Daverso&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 04:50:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-failover-test/m-p/2551451#M89691</guid>
      <dc:creator>david.daverso</dc:creator>
      <dc:date>2019-03-11T04:50:14Z</dc:date>
    </item>
    <item>
      <title>Refer the below</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-failover-test/m-p/2551452#M89693</link>
      <description>&lt;P&gt;Refer the below discussion&lt;/P&gt;&lt;P&gt;https://supportforums.cisco.com/discussion/11951356/ise-fail-over&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jul 2014 10:00:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-failover-test/m-p/2551452#M89693</guid>
      <dc:creator>Saurav Lodh</dc:creator>
      <dc:date>2014-07-01T10:00:56Z</dc:date>
    </item>
    <item>
      <title>Hello Saurav,Thanks for your</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-failover-test/m-p/2551453#M89695</link>
      <description>&lt;P&gt;Hello Saurav,&lt;/P&gt;&lt;P&gt;Thanks for your assistance (opened SAC case 191758). &amp;nbsp;I read the post to which you referred.&amp;nbsp; It was marginally helpful.&amp;nbsp; Have you ever completed a failover test in production?&amp;nbsp; My questions surrounding an ISE test plan&amp;nbsp;remain unanswered.&lt;/P&gt;&lt;P&gt;What is a good way to verify/test all three ISE persona for HA?&amp;nbsp; Reload the primary admin, MnT, PSN node?&amp;nbsp; Shut the switch interface to which the primary node is connected?&lt;/P&gt;&lt;P&gt;Will I see a performance spike when I promote the secondary Admin persona to primary?&amp;nbsp; If so, what's the expectation - 100% CPU utilization?&lt;/P&gt;&lt;P&gt;Will any alarms be generated when I halt the primary node to test HA?&amp;nbsp; If so, which ones?&lt;/P&gt;&lt;P&gt;Documentation is completely silent about the ISE pop-up&amp;nbsp;advisory you will get after you click the box&amp;nbsp;to promote&amp;nbsp;the secondary admin to primary, stating the admin function may be unavailable for 10 minutes.&amp;nbsp; How do I monitor anything when the admin persona is not available while switching from primary to admin?&lt;/P&gt;&lt;P&gt;What logs/support bundle&amp;nbsp;do I need to download and review to confirm monitoring is occurring normally after the secondary admin is promoted to primary and becomes active?&lt;/P&gt;&lt;P&gt;Will I see a performance hit when I revert back to the primary admin node?&amp;nbsp; What other post HA test actions should I take?&amp;nbsp; Documentation says after reverting back to primary admin node, backup operational data off the secondary admin node (now active) and restore to primary to fill in the monitoring gaps.&amp;nbsp; What logs should be backed up?&amp;nbsp; Details, please!&lt;/P&gt;&lt;P&gt;Thanks much,&lt;/P&gt;&lt;P&gt;David D.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jul 2014 23:00:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-failover-test/m-p/2551453#M89695</guid>
      <dc:creator>david.daverso</dc:creator>
      <dc:date>2014-07-02T23:00:33Z</dc:date>
    </item>
    <item>
      <title>Steps for Administration</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-failover-test/m-p/2551454#M89698</link>
      <description>&lt;P&gt;Steps for Administration persona failover testing&lt;/P&gt;&lt;P&gt;1. Stop ISE services on Primary Admin&lt;/P&gt;&lt;P&gt;Primary Admin# application stop ise&lt;/P&gt;&lt;P&gt;2. Log in to the Secondary Admin GUI and manually promote to Primary&lt;/P&gt;&lt;P&gt;3. Wait 10-15 minutes before process is complete&lt;/P&gt;&lt;P&gt;4. Verify ISE services are up on promoted Secondary Admin&lt;/P&gt;&lt;P&gt;Secondary Admin# sh application status ise&lt;/P&gt;&lt;P&gt;5. Promoted Primary Admin checks&lt;/P&gt;&lt;P&gt;Deployment pages shows all nodes are green and in synch&lt;/P&gt;&lt;P&gt;6. User testing to verify successful authentications and logging&lt;/P&gt;&lt;P&gt;Note:&lt;/P&gt;&lt;P&gt;After you promote your secondary Administration node to become the primary Administration&lt;/P&gt;&lt;P&gt;node, you must reconfigure your scheduled Cisco ISE backups in the newly promoted primary&lt;/P&gt;&lt;P&gt;Administration node&lt;/P&gt;&lt;P&gt;because scheduled backups are not replicated from the primary to secondary Administration&lt;/P&gt;&lt;P&gt;node.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;7. After step 6 testing is complete restore original Primary Admin&lt;/P&gt;&lt;P&gt;8. Start ISE services on original Primary Admin&lt;/P&gt;&lt;P&gt;Primary Admin# application start ise&lt;/P&gt;&lt;P&gt;9. Verify ISE services are up on original Primary Admin&lt;/P&gt;&lt;P&gt;Primary Admin# sh application status ise&lt;/P&gt;&lt;P&gt;10. Promoted Primary Admin checks&lt;/P&gt;&lt;P&gt;Deployment pages shows original Primary Admin green and in synch&lt;/P&gt;&lt;P&gt;11. Stop ISE services on Promoted Primary Admin&lt;/P&gt;&lt;P&gt;Secondary Admin# application stop ise&lt;/P&gt;&lt;P&gt;12. Log in to the original Primary Admin GUI and manually promote to Primary&lt;/P&gt;&lt;P&gt;13. Wait 10-15 minutes before process is complete&lt;/P&gt;&lt;P&gt;14. Verify ISE services are up on original Primary Admin&lt;/P&gt;&lt;P&gt;Primary Admin# sh application status ise&lt;/P&gt;&lt;P&gt;15. Promoted Primary Admin checks&lt;/P&gt;&lt;P&gt;Deployment pages shows all nodes are green and in synch&lt;/P&gt;&lt;P&gt;16. User testing to verify successful authentications and logging&lt;/P&gt;&lt;P&gt;Note:&lt;/P&gt;&lt;P&gt;After you promote your secondary Administration node to become the primary Administration&lt;/P&gt;&lt;P&gt;node, you&lt;/P&gt;&lt;P&gt;must reconfigure your scheduled Cisco ISE backups in the newly promoted primary&lt;/P&gt;&lt;P&gt;Administration node&lt;/P&gt;&lt;P&gt;because scheduled backups are not replicated from the primary to secondary Administration&lt;/P&gt;&lt;P&gt;node.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;17. Start ISE services on original Secondary Admin&lt;/P&gt;&lt;P&gt;Secondary Admin# application start ise&lt;/P&gt;&lt;P&gt;18. Verify ISE services are up on original Secondary Admin&lt;/P&gt;&lt;P&gt;Secondary Admin# sh application status ise&lt;/P&gt;&lt;P&gt;19. Primary Admin checks&lt;/P&gt;&lt;P&gt;Deployment pages shows original Secondary Admin green and in synch&lt;/P&gt;&lt;P&gt;20. User testing to verify successful authentications and logging&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jul 2014 07:56:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-failover-test/m-p/2551454#M89698</guid>
      <dc:creator>Saurav Lodh</dc:creator>
      <dc:date>2014-07-03T07:56:03Z</dc:date>
    </item>
  </channel>
</rss>

