<?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: 4250-XL in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/4250-xl/m-p/412098#M97989</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Seems to be the case.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 01 Jun 2005 14:50:15 GMT</pubDate>
    <dc:creator>mlipsey</dc:creator>
    <dc:date>2005-06-01T14:50:15Z</dc:date>
    <item>
      <title>4250-XL</title>
      <link>https://community.cisco.com/t5/network-security/4250-xl/m-p/412097#M97988</link>
      <description>&lt;P&gt;I'm a bit new to the IDS/IPS world but we have just received two 4250-XLs and I was going to use the ethernet monitor port but it simply won't let me. Reading the literature online it looks like this port is not useable as a monitoring port in the XL model and that I have to use the fiber ports.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this true?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 09:28:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/4250-xl/m-p/412097#M97988</guid>
      <dc:creator>mlipsey</dc:creator>
      <dc:date>2019-03-10T09:28:34Z</dc:date>
    </item>
    <item>
      <title>Re: 4250-XL</title>
      <link>https://community.cisco.com/t5/network-security/4250-xl/m-p/412098#M97989</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Seems to be the case.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Jun 2005 14:50:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/4250-xl/m-p/412098#M97989</guid>
      <dc:creator>mlipsey</dc:creator>
      <dc:date>2005-06-01T14:50:15Z</dc:date>
    </item>
    <item>
      <title>Re: 4250-XL</title>
      <link>https://community.cisco.com/t5/network-security/4250-xl/m-p/412099#M97990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It depends on the software version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the original 4.x software the onboard copper TX monitoring interface could notbe used for monitoring while an XL card was installed.&lt;/P&gt;&lt;P&gt;This is because the XL card had ot have a special driver and that driver could only control the fiber ports of the XL card.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In version 4.x if you wanted to monitor using the copper interface and not the 2 fiber ports of the XL card, then you need to physically remove the XL card.  A different driver would then be loaded and you could monitor the copper interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In version 5.0 this was changed.  The 2 drivers were combined so that both the XL fiber ports and the onboard copper port could be monitored at the same time.&lt;/P&gt;&lt;P&gt;So in 5.0 the onboard copper port is selectable as a promiscuous monitoring interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOTE1: The onboard copper interface does not have the hardware acceleration of the 2 XL fiber ports.  So performance when using the copper interface will be much less than the performance when using the fiber ports.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOTE2: The copper interface should not be combined with a fiber interface as part of an InLine interface pair for doing InLine IPS monitoring with version 5.0.&lt;/P&gt;&lt;P&gt;Only the pairing of the 2 fiber ports for InLine monitoring was tested and is supported by Cisco.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Jun 2005 17:08:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/4250-xl/m-p/412099#M97990</guid>
      <dc:creator>marcabal</dc:creator>
      <dc:date>2005-06-01T17:08:33Z</dc:date>
    </item>
  </channel>
</rss>

