<?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 S/N/K-Series Policy Based Mirroring overview in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/s-n-k-series-policy-based-mirroring-overview/m-p/43233#M162</link>
    <description>Article ID: 12373 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
S-Series, all firmware&lt;BR /&gt;
Matrix N-Series DFE, firmware 7.11.01.0025 and higher&lt;BR /&gt;
K-Series, all firmware &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Discussion&lt;/B&gt;&lt;BR /&gt;
Policy based mirroring allows certain data types to be matched by normal policy-based packet pattern classification, sending only that data as a source for a port mirror. This may be useful for analyzing only certain aspects of a conversation on the network; be it a protocol type, a user IP address, etc. &lt;BR /&gt;
&lt;BR /&gt;
Here are the affected commands. The  value in the 'set mirror' commands corresponds with the  value in the 'set policy' commands:&lt;BR /&gt;
set mirror&lt;BR /&gt;
  [create ]&lt;BR /&gt;
  [ {[storage-type {non-volatile | volatile}] | [owner ]}&lt;BR /&gt;
  [ {[mirrorN &amp;lt;#frames&amp;gt;] | [storage-type {non-volatile | volatile}] | [owner ]} (requires f/w 8.x)&lt;BR /&gt;
  [enable {}]&lt;BR /&gt;
  [disable {}]&lt;BR /&gt;
  [ports   [append]]&lt;BR /&gt;
 &lt;BR /&gt;
set policy profile  [name ]&lt;BR /&gt;
  [pvid-status {enable | disable} {pvid }]&lt;BR /&gt;
  [cos-status {enable | disable} {cos }]&lt;BR /&gt;
  [mirror-destination ] | [clear-mirror] | [prohibit-mirror]&lt;BR /&gt;
  [egress-vlans ]&lt;BR /&gt;
  [forbidden-vlans ]&lt;BR /&gt;
  [untagged-vlans ]&lt;BR /&gt;
  [append] | [clear]&lt;BR /&gt;
  [tci-overwrite {enable | disable}]&lt;BR /&gt;
  [precedence ]&lt;BR /&gt;
  [syslog {enable | disable}]&lt;BR /&gt;
  [trap {enable | disable}] &lt;BR /&gt;
  [disable-port {enable | disable}]&lt;BR /&gt;
 &lt;BR /&gt;
set policy rule {admin-profile | }&lt;BR /&gt;
  { [] [mask ]}&lt;BR /&gt;
  [port-string ] &lt;BR /&gt;
  [storage-type {non-volatile | volatile}]&lt;BR /&gt;
  [vlan ] | [drop | forward]&lt;BR /&gt;
  [cos ]&lt;BR /&gt;
  [mirror-destination ] | [clear-mirror] | [prohibit-mirror]&lt;BR /&gt;
  [admin-pid ]&lt;BR /&gt;
  [syslog {enable | disable | prohibit}]&lt;BR /&gt;
  [trap {enable |disable | prohibit}] &lt;BR /&gt;
  [disable-port {enable | disable | prohibit}]Note: With S/K-Series firmware 8.01.01.0016 and higher, the mirror command supports the 'mirrorN' feature to specify mirroring a maximum of &lt;I&gt;N&lt;/I&gt; frames. The maximum value for &amp;lt;&lt;I&gt;#frames&lt;/I&gt;&amp;gt; is 4294967295, equivalent to 0xffffffff. &lt;BR /&gt;
&lt;BR /&gt;
Here is a sample configuration that uses policy profile 10 to check for ARP frames ingressing policy-applied port ge.5.2, sending them to mirror instance 2 which applies to destination port ge.5.1. Remember that policy rules examine ingress traffic only.&lt;BR /&gt;
set mirror create 2&lt;BR /&gt;
set mirror ports ge.5.1 2&lt;BR /&gt;
set policy profile 10&lt;BR /&gt;
set policy rule 10 ether 0x806 mirror-destination 2 forward&lt;BR /&gt;
set policy port ge.5.2 10Again, the source of the ingressing ARP frames is port ge.5.2 and the sniffer, IDS or other traffic analysis device would plug into port ge.5.1. &lt;BR /&gt;
&lt;BR /&gt;
In these commands, the 'mirror-destination' parameter may be considered to act similarly to what is already understood for the 'pvid/vlan' and 'cos' parameters. That is, if an underlying rule containing such a parameter (e.g. mirror-destination) is "hit" by a policy-traversing packet, then that rule-specified action is executed for the packet - otherwise the same parameter if present in the profile command is executed for the packet as a default action. Thus, the example presented above mirrors ARP-matching traffic. If instead we wanted to mirror non-ARP-matching traffic, then the 'mirror-destination 2' parameter would be moved from the rule to the profile. &lt;BR /&gt;
&lt;BR /&gt;
Also see this &lt;A href="https://www.youtube.com/watch?v=CXrRp8h2KJw&amp;amp;#38;index=30&amp;amp;#38;list=PLvQMiI4QwvHTFYkDRLl_8NUE8Ijp5Zm8n" target="_blank" rel="nofollow noreferrer noopener"&gt;HowTo Video&lt;/A&gt; which provides further background regarding the policy-based mirroring feature.</description>
    <pubDate>Sat, 09 Nov 2013 04:56:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-11-09T04:56:00Z</dc:date>
    <item>
      <title>S/N/K-Series Policy Based Mirroring overview</title>
      <link>https://community.extremenetworks.com/t5/faqs/s-n-k-series-policy-based-mirroring-overview/m-p/43233#M162</link>
      <description>Article ID: 12373 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
S-Series, all firmware&lt;BR /&gt;
Matrix N-Series DFE, firmware 7.11.01.0025 and higher&lt;BR /&gt;
K-Series, all firmware &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Discussion&lt;/B&gt;&lt;BR /&gt;
Policy based mirroring allows certain data types to be matched by normal policy-based packet pattern classification, sending only that data as a source for a port mirror. This may be useful for analyzing only certain aspects of a conversation on the network; be it a protocol type, a user IP address, etc. &lt;BR /&gt;
&lt;BR /&gt;
Here are the affected commands. The  value in the 'set mirror' commands corresponds with the  value in the 'set policy' commands:&lt;BR /&gt;
set mirror&lt;BR /&gt;
  [create ]&lt;BR /&gt;
  [ {[storage-type {non-volatile | volatile}] | [owner ]}&lt;BR /&gt;
  [ {[mirrorN &amp;lt;#frames&amp;gt;] | [storage-type {non-volatile | volatile}] | [owner ]} (requires f/w 8.x)&lt;BR /&gt;
  [enable {}]&lt;BR /&gt;
  [disable {}]&lt;BR /&gt;
  [ports   [append]]&lt;BR /&gt;
 &lt;BR /&gt;
set policy profile  [name ]&lt;BR /&gt;
  [pvid-status {enable | disable} {pvid }]&lt;BR /&gt;
  [cos-status {enable | disable} {cos }]&lt;BR /&gt;
  [mirror-destination ] | [clear-mirror] | [prohibit-mirror]&lt;BR /&gt;
  [egress-vlans ]&lt;BR /&gt;
  [forbidden-vlans ]&lt;BR /&gt;
  [untagged-vlans ]&lt;BR /&gt;
  [append] | [clear]&lt;BR /&gt;
  [tci-overwrite {enable | disable}]&lt;BR /&gt;
  [precedence ]&lt;BR /&gt;
  [syslog {enable | disable}]&lt;BR /&gt;
  [trap {enable | disable}] &lt;BR /&gt;
  [disable-port {enable | disable}]&lt;BR /&gt;
 &lt;BR /&gt;
set policy rule {admin-profile | }&lt;BR /&gt;
  { [] [mask ]}&lt;BR /&gt;
  [port-string ] &lt;BR /&gt;
  [storage-type {non-volatile | volatile}]&lt;BR /&gt;
  [vlan ] | [drop | forward]&lt;BR /&gt;
  [cos ]&lt;BR /&gt;
  [mirror-destination ] | [clear-mirror] | [prohibit-mirror]&lt;BR /&gt;
  [admin-pid ]&lt;BR /&gt;
  [syslog {enable | disable | prohibit}]&lt;BR /&gt;
  [trap {enable |disable | prohibit}] &lt;BR /&gt;
  [disable-port {enable | disable | prohibit}]Note: With S/K-Series firmware 8.01.01.0016 and higher, the mirror command supports the 'mirrorN' feature to specify mirroring a maximum of &lt;I&gt;N&lt;/I&gt; frames. The maximum value for &amp;lt;&lt;I&gt;#frames&lt;/I&gt;&amp;gt; is 4294967295, equivalent to 0xffffffff. &lt;BR /&gt;
&lt;BR /&gt;
Here is a sample configuration that uses policy profile 10 to check for ARP frames ingressing policy-applied port ge.5.2, sending them to mirror instance 2 which applies to destination port ge.5.1. Remember that policy rules examine ingress traffic only.&lt;BR /&gt;
set mirror create 2&lt;BR /&gt;
set mirror ports ge.5.1 2&lt;BR /&gt;
set policy profile 10&lt;BR /&gt;
set policy rule 10 ether 0x806 mirror-destination 2 forward&lt;BR /&gt;
set policy port ge.5.2 10Again, the source of the ingressing ARP frames is port ge.5.2 and the sniffer, IDS or other traffic analysis device would plug into port ge.5.1. &lt;BR /&gt;
&lt;BR /&gt;
In these commands, the 'mirror-destination' parameter may be considered to act similarly to what is already understood for the 'pvid/vlan' and 'cos' parameters. That is, if an underlying rule containing such a parameter (e.g. mirror-destination) is "hit" by a policy-traversing packet, then that rule-specified action is executed for the packet - otherwise the same parameter if present in the profile command is executed for the packet as a default action. Thus, the example presented above mirrors ARP-matching traffic. If instead we wanted to mirror non-ARP-matching traffic, then the 'mirror-destination 2' parameter would be moved from the rule to the profile. &lt;BR /&gt;
&lt;BR /&gt;
Also see this &lt;A href="https://www.youtube.com/watch?v=CXrRp8h2KJw&amp;amp;#38;index=30&amp;amp;#38;list=PLvQMiI4QwvHTFYkDRLl_8NUE8Ijp5Zm8n" target="_blank" rel="nofollow noreferrer noopener"&gt;HowTo Video&lt;/A&gt; which provides further background regarding the policy-based mirroring feature.</description>
      <pubDate>Sat, 09 Nov 2013 04:56:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/s-n-k-series-policy-based-mirroring-overview/m-p/43233#M162</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-11-09T04:56:00Z</dc:date>
    </item>
  </channel>
</rss>

