<?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: IDSM  in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/idsm/m-p/1114013#M79106</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The intrusion detection module is connected to the switch back plane via a 'hidden' link. Which can be seen by show ether channel tough. The IDSM in total has 8 ports. In your configuration  the management/command&amp;amp;control port belongs to VLAN 333 (this is port gig 0/1 on the IDSM I think). This port is represented by 'management-port' in the IDSM config.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ports gig x/7 and gig x/8 are the two 'sensing' ports. These are represented by 'data-port' 1 and 2 in the IDSM config. In you case all data from some interface(s)/vlan(s) is being sent to the 'first' sensing port of the IDSM. So in short you are using promiscuous mode. For more details on what traffic is being sent, have a look at the 'show monitor session' command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate if helpful.&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;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 22 Aug 2008 02:14:19 GMT</pubDate>
    <dc:creator>Farrukh Haroon</dc:creator>
    <dc:date>2008-08-22T02:14:19Z</dc:date>
    <item>
      <title>IDSM</title>
      <link>https://community.cisco.com/t5/network-security/idsm/m-p/1114008#M79101</link>
      <description>&lt;P&gt;Which command on IDSM is used to check if the device is running on inline or promiscous mode?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 11:15:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm/m-p/1114008#M79101</guid>
      <dc:creator>aksher</dc:creator>
      <dc:date>2019-03-10T11:15:24Z</dc:date>
    </item>
    <item>
      <title>Re: IDSM</title>
      <link>https://community.cisco.com/t5/network-security/idsm/m-p/1114009#M79102</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can see this both from the Cataylyst Switch configuration and the IDS itself. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the 6500 switch if its inline VLAN pair you will form a trunk to the IDSM like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;intrusion-detection port-channel 5 trunk allowed-vlan 130,140&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it is Inline Phyiscal interfae you will see something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;intrusion-detection module 4 data-port 1 access-vlan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In case of promiscious you will have SPAN/capture configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the IDS cli you can see it via CLI:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;physical-interfaces GigabitEthernet0/8 &lt;/P&gt;&lt;P&gt;subinterface-type inline-vlan-pair&lt;/P&gt;&lt;P&gt;subinterface 7 &lt;/P&gt;&lt;P&gt;vlan1 160&lt;/P&gt;&lt;P&gt;vlan2 760&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is an example of Inline VLAN Pair.&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;Farrukh&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Aug 2008 06:38:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm/m-p/1114009#M79102</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-08-20T06:38:40Z</dc:date>
    </item>
    <item>
      <title>Re: IDSM</title>
      <link>https://community.cisco.com/t5/network-security/idsm/m-p/1114010#M79103</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I can see &lt;/P&gt;&lt;P&gt;inline-interfaces test &lt;/P&gt;&lt;P&gt;no description&lt;/P&gt;&lt;P&gt;interface1 GigabitEthernet0/7&lt;/P&gt;&lt;P&gt;interface2 GigabitEthernet0/8&lt;/P&gt;&lt;P&gt;on CLI of IDSM which means it's in inline VLAN pair but however i can also see SPAN through monitor commands which means it's in promiscous mode. Which is correct?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Aug 2008 20:10:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm/m-p/1114010#M79103</guid>
      <dc:creator>aksher</dc:creator>
      <dc:date>2008-08-20T20:10:11Z</dc:date>
    </item>
    <item>
      <title>Re: IDSM</title>
      <link>https://community.cisco.com/t5/network-security/idsm/m-p/1114011#M79104</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No you IDS seems to be in 'Inline Interface Pair' mode and not Inline VLAN pair mode and definitely not in promiscuous mode. Those span settings must be for something else on the switch. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In IDM &amp;gt;&amp;gt; Virtual Sensor Configurationyou sill see it spelled out pretty clearly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If possible post 'show run | inc intrusion' from your core switch.&lt;/P&gt;&lt;P&gt;&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;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Aug 2008 01:36:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm/m-p/1114011#M79104</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-08-21T01:36:24Z</dc:date>
    </item>
    <item>
      <title>Re: IDSM</title>
      <link>https://community.cisco.com/t5/network-security/idsm/m-p/1114012#M79105</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Farrukh! I am sending the output here,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sh run | i intrusion&lt;/P&gt;&lt;P&gt;intrusion-detection module 2 management-port access-vlan 333&lt;/P&gt;&lt;P&gt;intrusion-detection module 2 data-port 1 autostate include&lt;/P&gt;&lt;P&gt;intrusion-detection module 2 data-port 1 portfast enable&lt;/P&gt;&lt;P&gt;monitor session 2 destination intrusion-detection-module 2 data-port 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also it would be great if you explain the over all stuff in quick reference style:)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Aug 2008 22:23:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm/m-p/1114012#M79105</guid>
      <dc:creator>aksher</dc:creator>
      <dc:date>2008-08-21T22:23:31Z</dc:date>
    </item>
    <item>
      <title>Re: IDSM</title>
      <link>https://community.cisco.com/t5/network-security/idsm/m-p/1114013#M79106</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The intrusion detection module is connected to the switch back plane via a 'hidden' link. Which can be seen by show ether channel tough. The IDSM in total has 8 ports. In your configuration  the management/command&amp;amp;control port belongs to VLAN 333 (this is port gig 0/1 on the IDSM I think). This port is represented by 'management-port' in the IDSM config.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ports gig x/7 and gig x/8 are the two 'sensing' ports. These are represented by 'data-port' 1 and 2 in the IDSM config. In you case all data from some interface(s)/vlan(s) is being sent to the 'first' sensing port of the IDSM. So in short you are using promiscuous mode. For more details on what traffic is being sent, have a look at the 'show monitor session' command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate if helpful.&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;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Aug 2008 02:14:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/idsm/m-p/1114013#M79106</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-08-22T02:14:19Z</dc:date>
    </item>
  </channel>
</rss>

