<?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: ISE 2.1 Patch 4 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486287#M528170</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, I had logged a call with our cisco partner.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 29 Aug 2017 14:48:58 GMT</pubDate>
    <dc:creator>M. Wisely</dc:creator>
    <dc:date>2017-08-29T14:48:58Z</dc:date>
    <item>
      <title>ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486283#M528166</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is Patch 4 for ISE 2.1 going to be out soon? Customer running into a couple bugs that are fixed in future builds but wondering when that is going to happen. Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lou&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Jul 2017 16:16:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486283#M528166</guid>
      <dc:creator>lnorman</dc:creator>
      <dc:date>2017-07-27T16:16:05Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486284#M528167</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ISE 2.1, Patch-4 should be available sometime later next month or early September. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;-Hari&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Jul 2017 23:25:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486284#M528167</guid>
      <dc:creator>hariholla</dc:creator>
      <dc:date>2017-07-27T23:25:30Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486285#M528168</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Patch 4 is out now but I would be wary of it if you authenticate devices using eap-tls. We installed the patch this morning and I've now rolled it back as our iPhones and iPads hit the default rule rather than the ones that permitted them network access.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Aug 2017 13:31:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486285#M528168</guid>
      <dc:creator>M. Wisely</dc:creator>
      <dc:date>2017-08-29T13:31:04Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486286#M528169</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please make sure you work with the technical assistance center to check if it's a bug&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Aug 2017 13:41:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486286#M528169</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-08-29T13:41:06Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486287#M528170</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, I had logged a call with our cisco partner.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Aug 2017 14:48:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486287#M528170</guid>
      <dc:creator>M. Wisely</dc:creator>
      <dc:date>2017-08-29T14:48:58Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486288#M528171</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Agreed on the 'be wary about it' note from &lt;STRONG style="font-size: 10.8px; font-family: arial; color: #3d3d3d;"&gt;&lt;A href="https://community.cisco.com//people/martinwisely2"&gt;martinwisely2&lt;/A&gt;&lt;/STRONG&gt;. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We also had a customer load it to try to fix CSCvc69935 behavior (supposed to be fixed in patch 4, I have a hotfix for the bug to use temporarily which caused some other annoying problems with a 3595 appliance and had to remove it), but all indications were that patch 4 made the behavior worse, so the customer rolled back to patch 3 and reports things stabilized "back to normal". &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Only took Cisco 6 months to get this patch out the door (patch 3 was released February)... I've asked TAC to confirm with the BU that the fix for &lt;SPAN style="font-size: 13.3333px;"&gt;CSCvc69935 really did make it into Patch 4, because at this time I don't believe it did. &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Aug 2017 20:37:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486288#M528171</guid>
      <dc:creator>Richard Wakefield</dc:creator>
      <dc:date>2017-08-29T20:37:30Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486289#M528172</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is the Patch 4 now officially revoked? It disappeared in the download section as in the release notes without any anouncement.. looks like serious trouble. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Aug 2017 10:42:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486289#M528172</guid>
      <dc:creator>rafaelwunderwald</dc:creator>
      <dc:date>2017-08-31T10:42:54Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486290#M528173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I got an email yesterday listing it as an obsolete file.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Sep 2017 07:55:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486290#M528173</guid>
      <dc:creator>M. Wisely</dc:creator>
      <dc:date>2017-09-01T07:55:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486291#M528174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Splendid.. it's hard to take these ISE guys serious meanwhile. Not even the bug they promised to fix with patchlevel 4 was fixed as promised. I have opened a ticket at my cisco partner. No awnser yet.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Sep 2017 08:00:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486291#M528174</guid>
      <dc:creator>rafaelwunderwald</dc:creator>
      <dc:date>2017-09-01T08:00:32Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486292#M528175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There certainly seem to be QA issues with ISE and not just with this patch. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Sep 2017 08:10:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486292#M528175</guid>
      <dc:creator>M. Wisely</dc:creator>
      <dc:date>2017-09-01T08:10:21Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486293#M528176</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would confirm that. I've built a complete cluster in the last months and I have never seen such a buggy and dilettantish software for professionel use. Customer management doesn't seem any better. For example version 2.2 runs unstable about half a year after release, download is still available with no warnings. Version 2.1 is still recommended.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But hey, I got an awnser from Cisco TAC now:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"&lt;SPAN style="font-family: 'Courier New'; color: #1f497d;"&gt;In patch 4 we notice in big deployments that customers had issues with radius authentication latency, CSCvc69935 ISE 2.1 dropping radius traffic for stuck packet in duplicate manager. In case you notice problems with authentication latency you can rollback to patch 3 to resolve the issue.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Courier New'; color: #1f497d;"&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvc69935/?referring_site=bugquickviewredir"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvc69935/?referring_site=bugquickviewredir&lt;/A&gt;"&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Sep 2017 08:21:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486293#M528176</guid>
      <dc:creator>rafaelwunderwald</dc:creator>
      <dc:date>2017-09-01T08:21:26Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486294#M528177</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hopefully I'll get an answer this afternoon. We were advised by a TAC engineer against upgrading to 2.2, he referred to it as raw.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Sep 2017 08:36:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486294#M528177</guid>
      <dc:creator>M. Wisely</dc:creator>
      <dc:date>2017-09-01T08:36:04Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486295#M528178</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;..raw. It was released &lt;SPAN style="color: #333333; font-size: 11px;"&gt;31-JAN-2017&lt;/SPAN&gt;. I don't know what to say.&lt;/P&gt;&lt;P&gt;I've installed 2.3 for testing purposes on a seperate vm. Perhaps we can go online with that version in 2020.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Sep 2017 08:43:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486295#M528178</guid>
      <dc:creator>rafaelwunderwald</dc:creator>
      <dc:date>2017-09-01T08:43:45Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486296#M528179</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My company was on the waitlist for Patch 4 also, to resolve a bug for NIC binding. I got the alert email the patch was ready on 8/27, and applied it that day as it was on a weekend.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I and our networking team had to roll back the patch last night. We have 3 major campuses, and while we didn't see issues at 2 of them, at one campus with a cluster of 5508 WLCs we observed similar issues described above with WiFi clients. We saw very chatty sessions, EAP authentications being dropped, radius server connection issues from the WLC, and high latency on the PSNs. We tried upgrading the 5508 code to a later version, but the client WiFi issues continued. I should know later today if going back to patch 3 resolved our users' issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I echo the sentiments expressed though, that this patch 4 didn't seem to have been properly QA'd. I will be waiting a bit longer when the next one is released to vet users are having good success with it. I'm also glad we have skipped the ISE 2.2 train!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Sep 2017 13:52:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486296#M528179</guid>
      <dc:creator>joshobean</dc:creator>
      <dc:date>2017-09-07T13:52:49Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486297#M528180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just to add to my earlier comment, I can confirm that going back to ISE 2.1 Patch 3 fixed our WiFi issues. It appears Patch 4 with a 5508 WLC controller is not a good combo. Our other campuses that didn't experience the issue all had 5520s.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Sep 2017 16:32:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486297#M528180</guid>
      <dc:creator>joshobean</dc:creator>
      <dc:date>2017-09-07T16:32:38Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486298#M528181</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Patch 5 was just posted for 2.1, no release notes yet though. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Sep 2017 21:07:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486298#M528181</guid>
      <dc:creator>Richard Wakefield</dc:creator>
      <dc:date>2017-09-14T21:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486299#M528182</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Releasenotes are available now, including the Releasenotes for Patch 4.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Sep 2017 13:11:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486299#M528182</guid>
      <dc:creator>rafaelwunderwald</dc:creator>
      <dc:date>2017-09-15T13:11:25Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486300#M528183</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Release notes are now there, 3 bugs listed as resolved.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Sep 2017 13:12:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486300#M528183</guid>
      <dc:creator>M. Wisely</dc:creator>
      <dc:date>2017-09-15T13:12:25Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486301#M528184</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Patch 5 and Patch 6 seem to be working well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 12 Nov 2017 06:38:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486301#M528184</guid>
      <dc:creator>Richard Wakefield</dc:creator>
      <dc:date>2017-11-12T06:38:46Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.1 Patch 4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486302#M528185</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That's good to hear.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Nov 2017 09:52:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-patch-4/m-p/3486302#M528185</guid>
      <dc:creator>M. Wisely</dc:creator>
      <dc:date>2017-11-13T09:52:54Z</dc:date>
    </item>
  </channel>
</rss>

