<?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 PassiveID User-IP Mapping timeout in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-passiveid-user-ip-mapping-timeout/m-p/4141135#M562508</link>
    <description>&lt;P&gt;Our problem is more towards ISE-PIC. PassiveID does not reflect new IP for new login with another IP address.&lt;/P&gt;
&lt;P&gt;If userA login from 192.168.1.1 for the first time, we receive the login message in ISE-PIC and share across to FMC via pxGrid. A second login from userA without logout from previous session at another IP address does not appear in ISE-PIC. Are there any specific tuning in ISE-PIC for concurrent/multi IP mapping?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Wing Churn&lt;/P&gt;</description>
    <pubDate>Tue, 25 Aug 2020 15:59:02 GMT</pubDate>
    <dc:creator>wileong</dc:creator>
    <dc:date>2020-08-25T15:59:02Z</dc:date>
    <item>
      <title>ISE PassiveID User-IP Mapping timeout</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-passiveid-user-ip-mapping-timeout/m-p/4141057#M562504</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Working on a use case as follows:&lt;/P&gt;
&lt;P&gt;UserA - 192.168.1.1 (First Login)&lt;/P&gt;
&lt;P&gt;UserA - 192.168.1.2 (Second Login)&lt;/P&gt;
&lt;P&gt;UserA login into 192.168.1.1 after login at 192.168.1.1. Based on ISE passiveID, only first IP is registered in User-IP mapping and shared via pxGrid to FMC. Any possibility for the same UserA map to multiple IPs for concurrent login?&lt;/P&gt;
&lt;P&gt;Currently even based on endpoint probes, the mapping will not get updated within 4 hours if user has no logout from earlier session.&lt;/P&gt;
&lt;P&gt;Without relying on limiting concurrent login at AD and PAM solution, do we have any workaround for ISE PassiveID to get latest endpoint information? Or are there any possibility for same username mapped to 2 or more IP?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Wing Churn&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Aug 2020 14:29:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-passiveid-user-ip-mapping-timeout/m-p/4141057#M562504</guid>
      <dc:creator>wileong</dc:creator>
      <dc:date>2020-08-25T14:29:11Z</dc:date>
    </item>
    <item>
      <title>Re: ISE PassiveID User-IP Mapping timeout</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-passiveid-user-ip-mapping-timeout/m-p/4141118#M562506</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I am using this with FMC configured with passive authentication identity&lt;BR /&gt;policy pointing to AD realm. Basically my users login to network either&lt;BR /&gt;with dot1x for LAN/WLAN or ISE authorization for VPN. Once logged in, ISE&lt;BR /&gt;updates FMC using PxGrid. Then FMC updates user-ip mapping DB and contact&lt;BR /&gt;AD to obtain AD groups as well.&lt;BR /&gt;&lt;BR /&gt;It can support multiple IPs for same user and I can see this update in FTD&lt;BR /&gt;DB by running the script user_identity.pl.&lt;BR /&gt;&lt;BR /&gt;Here is an example:&lt;BR /&gt;&lt;BR /&gt;root@lab-firepower:/home/admin# user_map_query.pl -u mohammed.baqari&lt;BR /&gt;&lt;BR /&gt;WARNING: This script was not tested on this major version (6.5.0)! The&lt;BR /&gt;results may be unexpected.&lt;BR /&gt;Current Time: 08/25/2020 15:33:27 UTC&lt;BR /&gt;&lt;BR /&gt;Getting information on username(s)...&lt;BR /&gt;___&lt;BR /&gt;User #1: mohammed.baqari&lt;BR /&gt;---&lt;BR /&gt;&lt;BR /&gt;  ID:         2981&lt;BR /&gt;  Last Seen:  Unknown&lt;BR /&gt;  for_policy: 0&lt;BR /&gt;  Realm ID:   5&lt;BR /&gt;&lt;BR /&gt;==============================&lt;BR /&gt;|          Database          |&lt;BR /&gt;==============================&lt;BR /&gt;&lt;BR /&gt;##) IP Address [Realm ID]&lt;BR /&gt; 1) ::ffff:10.11.15.10 [5]&lt;BR /&gt; 2) ::ffff:192.168.1.130 [5]&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;##) Group Name (ID)&lt;BR /&gt; 1) Domain Users (3)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;**** please remember to rate useful posts&lt;BR /&gt;</description>
      <pubDate>Tue, 25 Aug 2020 15:35:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-passiveid-user-ip-mapping-timeout/m-p/4141118#M562506</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2020-08-25T15:35:45Z</dc:date>
    </item>
    <item>
      <title>Re: ISE PassiveID User-IP Mapping timeout</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-passiveid-user-ip-mapping-timeout/m-p/4141135#M562508</link>
      <description>&lt;P&gt;Our problem is more towards ISE-PIC. PassiveID does not reflect new IP for new login with another IP address.&lt;/P&gt;
&lt;P&gt;If userA login from 192.168.1.1 for the first time, we receive the login message in ISE-PIC and share across to FMC via pxGrid. A second login from userA without logout from previous session at another IP address does not appear in ISE-PIC. Are there any specific tuning in ISE-PIC for concurrent/multi IP mapping?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Wing Churn&lt;/P&gt;</description>
      <pubDate>Tue, 25 Aug 2020 15:59:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-passiveid-user-ip-mapping-timeout/m-p/4141135#M562508</guid>
      <dc:creator>wileong</dc:creator>
      <dc:date>2020-08-25T15:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: ISE PassiveID User-IP Mapping timeout</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-passiveid-user-ip-mapping-timeout/m-p/4141806#M562533</link>
      <description>You can tune the global timeout value for the session directory but that is about all.  Sadly, it won't solve the issue you are experiencing.  If you moved to ISE instead of PIC, you would get the benefit of RADIUS accounting.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;-Tim</description>
      <pubDate>Wed, 26 Aug 2020 16:26:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-passiveid-user-ip-mapping-timeout/m-p/4141806#M562533</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2020-08-26T16:26:14Z</dc:date>
    </item>
    <item>
      <title>Re: ISE PassiveID User-IP Mapping timeout</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-passiveid-user-ip-mapping-timeout/m-p/4632407#M575495</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/26660"&gt;@Timothy Abbott&lt;/a&gt;I know this is old, but do you have some info on how to convert the FMC integration with ISE from ISE-PIC to ISE?&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jun 2022 13:53:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-passiveid-user-ip-mapping-timeout/m-p/4632407#M575495</guid>
      <dc:creator>DMel</dc:creator>
      <dc:date>2022-06-15T13:53:45Z</dc:date>
    </item>
  </channel>
</rss>

