<?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 Cisco ISE Bridge Mode in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765718#M218814</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In bridged mode, the Inline Posture node operates as a standard Ethernet bridge. This configuration is typically used when the untrusted network already has a gateway, and you do not want to change the existing configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The figure below shows the Inline Posture node acting as a bridge for the Layer 2 client traffic from the WLC into the Cisco ISE network, managed by the Policy Service ISE node. In this configuration, Inline Posture requires subnet entries for the 10.20.80.0/24 and 10.20.90.0/24 subnets to be able to respond to and send Address Resolution protocol (ARP) broadcasts to the correct VLANs.&lt;/P&gt;&lt;P&gt;&lt;IMG height="384" src="http://sac3.cisco.com:9128/userfiles//Capture(9).jpg" width="597" /&gt;&lt;/P&gt;&lt;P&gt;When the Inline Posture node is in bridged mode, the following conditions apply:&lt;/P&gt;&lt;P&gt;•Inline Posture eth0 and eth1 can have the same IP address.&lt;/P&gt;&lt;P&gt;•All end devices in the bridged subnet must be on the untrusted network.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 Mar 2013 21:14:25 GMT</pubDate>
    <dc:creator>mmangat</dc:creator>
    <dc:date>2013-03-06T21:14:25Z</dc:date>
    <item>
      <title>Cisco ISE Bridge Mode</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765714#M218794</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was trying to configure Cisco ISE bridge mode for ISE Policy Node configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It was working fine for few mins and then the ISE Stop responding. &lt;/P&gt;&lt;P&gt;through console access i could only ping the default gateway but no other servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have configured the VLAN Mapping rule for it also before restarting the node.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can some1 help me out.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 01:28:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765714#M218794</guid>
      <dc:creator>saxenanitesh8522</dc:creator>
      <dc:date>2019-03-11T01:28:24Z</dc:date>
    </item>
    <item>
      <title>Cisco ISE Bridge Mode</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765715#M218798</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Could you please issue the command "show application status ise" to see if the processes are OK ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Oct 2011 17:45:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765715#M218798</guid>
      <dc:creator>Eduardo Aliaga</dc:creator>
      <dc:date>2011-10-12T17:45:23Z</dc:date>
    </item>
    <item>
      <title>Cisco ISE Bridge Mode</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765716#M218802</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;its running ISE inline POLICY NODE so it only shows the kernel and thats it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;secondly, i am losing the management connection and ping request.&lt;/P&gt;&lt;P&gt;does any1 has an idea why this happening.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please if you can me out...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Oct 2011 18:40:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765716#M218802</guid>
      <dc:creator>saxenanitesh8522</dc:creator>
      <dc:date>2011-10-12T18:40:23Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Bridge Mode</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765717#M218808</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;This is common mapping problem I think.&lt;/P&gt;&lt;P&gt;Remove the mapping and use different vlans and take a look at the debug log.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Nov 2011 13:41:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765717#M218808</guid>
      <dc:creator>deger guneyi</dc:creator>
      <dc:date>2011-11-08T13:41:38Z</dc:date>
    </item>
    <item>
      <title>Cisco ISE Bridge Mode</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765718#M218814</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In bridged mode, the Inline Posture node operates as a standard Ethernet bridge. This configuration is typically used when the untrusted network already has a gateway, and you do not want to change the existing configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The figure below shows the Inline Posture node acting as a bridge for the Layer 2 client traffic from the WLC into the Cisco ISE network, managed by the Policy Service ISE node. In this configuration, Inline Posture requires subnet entries for the 10.20.80.0/24 and 10.20.90.0/24 subnets to be able to respond to and send Address Resolution protocol (ARP) broadcasts to the correct VLANs.&lt;/P&gt;&lt;P&gt;&lt;IMG height="384" src="http://sac3.cisco.com:9128/userfiles//Capture(9).jpg" width="597" /&gt;&lt;/P&gt;&lt;P&gt;When the Inline Posture node is in bridged mode, the following conditions apply:&lt;/P&gt;&lt;P&gt;•Inline Posture eth0 and eth1 can have the same IP address.&lt;/P&gt;&lt;P&gt;•All end devices in the bridged subnet must be on the untrusted network.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Mar 2013 21:14:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765718#M218814</guid>
      <dc:creator>mmangat</dc:creator>
      <dc:date>2013-03-06T21:14:25Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Bridge Mode</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765719#M218819</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Kindly review the attached doc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 May 2013 10:39:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765719#M218819</guid>
      <dc:creator>manjeets</dc:creator>
      <dc:date>2013-05-22T10:39:02Z</dc:date>
    </item>
    <item>
      <title>avoid to put the posture</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765720#M218822</link>
      <description>&lt;P&gt;&lt;SPAN id="result_box" lang="en"&gt;&lt;SPAN class="hps"&gt;avoid to put&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;the &lt;/SPAN&gt;&lt;SPAN class="hps"&gt;posture&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;inline&lt;/SPAN&gt; &lt;/SPAN&gt;&lt;SPAN id="result_box" lang="en"&gt;&lt;SPAN class="hps"&gt;Node&lt;/SPAN&gt; &lt;/SPAN&gt;&lt;SPAN id="result_box" lang="en"&gt;&lt;SPAN class="hps"&gt;in the same&lt;/SPAN&gt; subnet &lt;SPAN class="hps"&gt;as the&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;Administration &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN id="result_box" lang="en"&gt;&lt;SPAN class="hps"&gt;Node&lt;/SPAN&gt; &lt;/SPAN&gt;&lt;SPAN id="result_box" lang="en"&gt;&lt;SPAN class="hps"&gt;.&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;At&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;least put&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;an explicit&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;static route on&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;inline&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;post&lt;/SPAN&gt;&lt;/SPAN&gt;ure Node.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN id="result_box" lang="en"&gt;&lt;SPAN class="hps"&gt;The problem&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;is because&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;the&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;posture&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;inline &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN id="result_box" lang="en"&gt;&lt;SPAN class="hps"&gt;Node&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN id="result_box" lang="en"&gt; &lt;SPAN class="hps"&gt;expects&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;the fact that the&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;Admin&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;Node&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;is on the&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;trust&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;side.&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;and in the case&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;of the&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;bridged&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;mode, the&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;two&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;subnets&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;are merged&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 04 Jul 2015 16:25:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-bridge-mode/m-p/1765720#M218822</guid>
      <dc:creator>M'Bouke Serge Cedric BESSE</dc:creator>
      <dc:date>2015-07-04T16:25:33Z</dc:date>
    </item>
  </channel>
</rss>

