<?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: VLAN PAIR in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/vlan-pair/m-p/1497971#M66758</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a. Vlan pair can be thought as&amp;nbsp; IPS on a stick (analogous to router on a stick)&lt;/P&gt;&lt;P&gt;One physical interface and multiple subinterfaces.&lt;/P&gt;&lt;P&gt;Each subinterface is associated with a pair of vlans.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b. On a given physical interface, you cannot associate the same vlan pair on more than one subinterface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;c. You can associate the same vlan pair assigned to a subinterface on a separate physical interface.&lt;/P&gt;&lt;P&gt;Correct, you will see an error message that warns you, that you are using same vlans for multiple interfaces.&lt;/P&gt;&lt;P&gt;But this should be fine. You will he having same Vlans say x &amp;amp; y being bridged on more that one physical interface on the IPS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;d. In terms of load-balancing, understand that IPS will inspect whatever traffic it recieves on&amp;nbsp; the physical interfaces.&lt;/P&gt;&lt;P&gt;Hence if you have 2 physical interfaces say 1 &amp;amp; 2 each having a subinterface 1 and same vlans x &amp;amp; y associated,&lt;/P&gt;&lt;P&gt;then its the job of the Nexus to make sure equal amount traffic actually goes into interface 1 &amp;amp; 2.&lt;/P&gt;&lt;P&gt;So traffic allocation on each ips interface depends on load-balacing done on nexus.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e. Like with every network design issue, always test it before putting it under production, to check for any unexpected issues (for e.g spanning-tree issues due to typical flow of traffic etc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sid Chandrachud&lt;/P&gt;&lt;P&gt;TAC Security Solutions&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 19 Aug 2010 17:51:34 GMT</pubDate>
    <dc:creator>Siddharth Chandrachud</dc:creator>
    <dc:date>2010-08-19T17:51:34Z</dc:date>
    <item>
      <title>VLAN PAIR</title>
      <link>https://community.cisco.com/t5/network-security/vlan-pair/m-p/1497970#M66757</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a question, I have a 4270 working with VLAN PAIRs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In an interface I have the VLAN pair 120-121&amp;nbsp; and in another interface the same pair 120-121 When I add that pair the IPS gives an error message saying that I already have that VLAN Pair however it allows the creation of the PAIR. I can even see traffic passing through the interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1 interface has so much traffic however the another one only a few traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know that I cannot have the same vlan twice in the same interface but I am using 2 different interfaces with the same vlan.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The IPS should be able to handle that right? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 2 Nexus doing load balancing, I connected them both to the IPS (1 interface per Nexus) so I can inspect all the traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know if I am doing the thing wrong.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 12:05:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vlan-pair/m-p/1497970#M66757</guid>
      <dc:creator>Diego Armando Cambronero Arias</dc:creator>
      <dc:date>2019-03-10T12:05:48Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN PAIR</title>
      <link>https://community.cisco.com/t5/network-security/vlan-pair/m-p/1497971#M66758</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a. Vlan pair can be thought as&amp;nbsp; IPS on a stick (analogous to router on a stick)&lt;/P&gt;&lt;P&gt;One physical interface and multiple subinterfaces.&lt;/P&gt;&lt;P&gt;Each subinterface is associated with a pair of vlans.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b. On a given physical interface, you cannot associate the same vlan pair on more than one subinterface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;c. You can associate the same vlan pair assigned to a subinterface on a separate physical interface.&lt;/P&gt;&lt;P&gt;Correct, you will see an error message that warns you, that you are using same vlans for multiple interfaces.&lt;/P&gt;&lt;P&gt;But this should be fine. You will he having same Vlans say x &amp;amp; y being bridged on more that one physical interface on the IPS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;d. In terms of load-balancing, understand that IPS will inspect whatever traffic it recieves on&amp;nbsp; the physical interfaces.&lt;/P&gt;&lt;P&gt;Hence if you have 2 physical interfaces say 1 &amp;amp; 2 each having a subinterface 1 and same vlans x &amp;amp; y associated,&lt;/P&gt;&lt;P&gt;then its the job of the Nexus to make sure equal amount traffic actually goes into interface 1 &amp;amp; 2.&lt;/P&gt;&lt;P&gt;So traffic allocation on each ips interface depends on load-balacing done on nexus.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e. Like with every network design issue, always test it before putting it under production, to check for any unexpected issues (for e.g spanning-tree issues due to typical flow of traffic etc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sid Chandrachud&lt;/P&gt;&lt;P&gt;TAC Security Solutions&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Aug 2010 17:51:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vlan-pair/m-p/1497971#M66758</guid>
      <dc:creator>Siddharth Chandrachud</dc:creator>
      <dc:date>2010-08-19T17:51:34Z</dc:date>
    </item>
  </channel>
</rss>

