<?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: 4215 problem with Inline Pair or 4FE in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/4215-problem-with-inline-pair-or-4fe/m-p/417050#M99001</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you see any error message ? Your config looks good, should be working. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Aug 2005 14:32:57 GMT</pubDate>
    <dc:creator>umedryk</dc:creator>
    <dc:date>2005-08-02T14:32:57Z</dc:date>
    <item>
      <title>4215 problem with Inline Pair or 4FE</title>
      <link>https://community.cisco.com/t5/network-security/4215-problem-with-inline-pair-or-4fe/m-p/417049#M98999</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I upgraded a 4215 from IDS to IPS 5.03 with Sig 181 and the BIOS update. Now I am unable to communicate through the sensor.  I can ping the sensor only from int FA1(which I presume is actually FA0/1 in the config)  &lt;/P&gt;&lt;P&gt;Here is my config:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;service analysis-engine&lt;/P&gt;&lt;P&gt;virtual-sensor vs0 &lt;/P&gt;&lt;P&gt;description default virtual sensor&lt;/P&gt;&lt;P&gt;logical-interface PAIR1&lt;/P&gt;&lt;P&gt;inline-interfaces PAIR1 &lt;/P&gt;&lt;P&gt;interface1 FastEthernet0/1&lt;/P&gt;&lt;P&gt;interface2 FastEthernet1/2&lt;/P&gt;&lt;P&gt;exit&lt;/P&gt;&lt;P&gt;bypass-mode auto&lt;/P&gt;&lt;P&gt;service interface&lt;/P&gt;&lt;P&gt;physical-interfaces FastEthernet0/1 &lt;/P&gt;&lt;P&gt;admin-state enabled&lt;/P&gt;&lt;P&gt;exit&lt;/P&gt;&lt;P&gt;physical-interfaces FastEthernet1/1 &lt;/P&gt;&lt;P&gt;admin-state enabled&lt;/P&gt;&lt;P&gt;exit&lt;/P&gt;&lt;P&gt;physical-interfaces FastEthernet1/2 &lt;/P&gt;&lt;P&gt;admin-state enabled&lt;/P&gt;&lt;P&gt;exit&lt;/P&gt;&lt;P&gt;Does anyone see anything obvious that I am overlooking?&lt;/P&gt;&lt;P&gt;The 4FE was working in IDS mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;JT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 09:33:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/4215-problem-with-inline-pair-or-4fe/m-p/417049#M98999</guid>
      <dc:creator>jterry</dc:creator>
      <dc:date>2019-03-10T09:33:30Z</dc:date>
    </item>
    <item>
      <title>Re: 4215 problem with Inline Pair or 4FE</title>
      <link>https://community.cisco.com/t5/network-security/4215-problem-with-inline-pair-or-4fe/m-p/417050#M99001</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you see any error message ? Your config looks good, should be working. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Aug 2005 14:32:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/4215-problem-with-inline-pair-or-4fe/m-p/417050#M99001</guid>
      <dc:creator>umedryk</dc:creator>
      <dc:date>2005-08-02T14:32:57Z</dc:date>
    </item>
    <item>
      <title>Re: 4215 problem with Inline Pair or 4FE</title>
      <link>https://community.cisco.com/t5/network-security/4215-problem-with-inline-pair-or-4fe/m-p/417051#M99005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A possible cause could be that you have network cables plugged into the wrong network interfaces on the back of the IDS-4215. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Beginning with IPS 5.0, on all existing sensor appliances, we name the network interfaces according to a Cisco standard. For a given slot (or main board) the interface physically closest to the power supply is lowest interface number (0), and the numbers increase as you move away from the power supply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This naming convention is opposite from the silk screen interface names marked on the outside of IDS-4215 sensors. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The interface pair you call "PAIR1" includes the interface on the main board furthest from the power supply (called "FastEthernet0/1" on the command line, but which is labeled "FastEthernet0" on the back of the unit) and the third interface from the power supply on the 4FE module.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hopefully my ASCII graphics make sense. This is what you would see looking at the rear of the IDS-4215:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;O-X-O-O......X-O......PS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Each "X" or "O" represents a network interface. The Xs mark the two that are in PAIR1. "PS" is the power supply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I recommend that you label your IDS-4215 interfaces, or blot out the silk screened names with a permanent marker, to avoid confusion in the future. We realize this causes some confusion, but moving to a naming standard will benefit you in the long run, especially if you have multiple Cisco products installed in your network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Aug 2005 15:24:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/4215-problem-with-inline-pair-or-4fe/m-p/417051#M99005</guid>
      <dc:creator>brhamon</dc:creator>
      <dc:date>2005-08-02T15:24:29Z</dc:date>
    </item>
  </channel>
</rss>

