<?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 In 802.1Q, what is the difference between IVL and SVL? in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/in-802-1q-what-is-the-difference-between-ivl-and-svl/m-p/49549#M599</link>
    <description>Article ID: 4918 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Standards&lt;/B&gt;&lt;BR /&gt;
802.1Q &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
Vlan learning settings &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Unicast flooding &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
For devices supporting 802.1Q VLAN functionality, there are two possible modes for the operation of the Source Address Table:&lt;UL&gt; 
&lt;LI&gt;&lt;B&gt;IVL&lt;/B&gt; (Independent Vlan Learning): VLANs each use their own logical Source Address Table. Transparent source address learning done as a result of ingressed vlan x traffic, is not made available on behalf of ingressed vlan ytraffic for forwarding purposes. This setting would be useful for handling devices (such as mainframes) with NICs which share a common MAC address.  
&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;SVL&lt;/B&gt; (Shared Vlan Learning): Two or more VLANs are grouped to share common source address information. This setting would be useful for configuration of more complex "asymmetrical cross-vlan" traffic patterns, without forcing the switch to flood the unicast traffic in each direction.&lt;/LI&gt;&lt;/UL&gt;
This brings us to the concept of a Filtering DataBase ID (aka FDB ID, aka FID). Though the reality is slightly more complex, a FID can be thought of as a plain, garden-variety Source Address Table. Different FIDs = different SATs = Independent VLAN Learning; and same FIDs = same SATs = Shared VLAN Learning. &lt;BR /&gt;
&lt;BR /&gt;
Depending upon the product, the VLAN Learning setting will be global for the entire switch (SVL or IVL, potentially selectable), or can be configured in a more granular manner in that some VLANs each have unique FIDs while other VLANs share a FID. &lt;BR /&gt;
&lt;BR /&gt;
A given device typically has a single Source Address Table, with each entry containing a FID parameter which can, if IVL is being used, make it appear that separate SATs are in use. &lt;BR /&gt;
&lt;BR /&gt;
See &lt;A href="http://bit.ly/1avSTRA" target="_blank" rel="nofollow noreferrer noopener"&gt;5397&lt;/A&gt; for configuring IVL/SVL on a Matrix DFE. &lt;BR /&gt;
See &lt;A href="http://bit.ly/1bfGhOw" target="_blank" rel="nofollow noreferrer noopener"&gt;5498&lt;/A&gt; for related Matrix C1/SecureStack C3/C2/B3/B2/A2 information.</description>
    <pubDate>Wed, 04 Dec 2013 03:51:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-12-04T03:51:00Z</dc:date>
    <item>
      <title>In 802.1Q, what is the difference between IVL and SVL?</title>
      <link>https://community.extremenetworks.com/t5/faqs/in-802-1q-what-is-the-difference-between-ivl-and-svl/m-p/49549#M599</link>
      <description>Article ID: 4918 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Standards&lt;/B&gt;&lt;BR /&gt;
802.1Q &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Goals&lt;/B&gt;&lt;BR /&gt;
Vlan learning settings &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Unicast flooding &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
For devices supporting 802.1Q VLAN functionality, there are two possible modes for the operation of the Source Address Table:&lt;UL&gt; 
&lt;LI&gt;&lt;B&gt;IVL&lt;/B&gt; (Independent Vlan Learning): VLANs each use their own logical Source Address Table. Transparent source address learning done as a result of ingressed vlan x traffic, is not made available on behalf of ingressed vlan ytraffic for forwarding purposes. This setting would be useful for handling devices (such as mainframes) with NICs which share a common MAC address.  
&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;SVL&lt;/B&gt; (Shared Vlan Learning): Two or more VLANs are grouped to share common source address information. This setting would be useful for configuration of more complex "asymmetrical cross-vlan" traffic patterns, without forcing the switch to flood the unicast traffic in each direction.&lt;/LI&gt;&lt;/UL&gt;
This brings us to the concept of a Filtering DataBase ID (aka FDB ID, aka FID). Though the reality is slightly more complex, a FID can be thought of as a plain, garden-variety Source Address Table. Different FIDs = different SATs = Independent VLAN Learning; and same FIDs = same SATs = Shared VLAN Learning. &lt;BR /&gt;
&lt;BR /&gt;
Depending upon the product, the VLAN Learning setting will be global for the entire switch (SVL or IVL, potentially selectable), or can be configured in a more granular manner in that some VLANs each have unique FIDs while other VLANs share a FID. &lt;BR /&gt;
&lt;BR /&gt;
A given device typically has a single Source Address Table, with each entry containing a FID parameter which can, if IVL is being used, make it appear that separate SATs are in use. &lt;BR /&gt;
&lt;BR /&gt;
See &lt;A href="http://bit.ly/1avSTRA" target="_blank" rel="nofollow noreferrer noopener"&gt;5397&lt;/A&gt; for configuring IVL/SVL on a Matrix DFE. &lt;BR /&gt;
See &lt;A href="http://bit.ly/1bfGhOw" target="_blank" rel="nofollow noreferrer noopener"&gt;5498&lt;/A&gt; for related Matrix C1/SecureStack C3/C2/B3/B2/A2 information.</description>
      <pubDate>Wed, 04 Dec 2013 03:51:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/in-802-1q-what-is-the-difference-between-ivl-and-svl/m-p/49549#M599</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-12-04T03:51:00Z</dc:date>
    </item>
  </channel>
</rss>

