ccna 200 301 bookshare application

ccna 200 301 bookshare application.When multiple VLANs are configured on both switches, then cable-related issues become complicated in an environment where the two switches are mutually exclusive. Since one VLAN does not communicate with other VLANs, it means that you need to use a separate cable for each VLAN between the two switches. Figure 7.10 shows two VLANs configured on two switches, so you would need to deploy two cables.It's obviously too inefficient to interconnect one port for each VLAN between the connected switches, so in this case you need virtualization to help, enabling one cable to do the work of multiple physical cables. This technique is often called Trunking, where a switch marks data frames, sends them to the link, and then the other switch removes the marks. You may be wondering whether this is virtualization or not, but this technology is close enough to the technology this book is about, and Figure 7.11 shows how it works.Figure 7.8 2 Physical LANsFigure 7.9 2 VLANsChapter 7 Nexus Introduction Physical Layer 2 Switch Interconnect LinksFigure 7.102 Physical Switch Interconnect Link Virtual Layer 2 Switch Interconnect Link TrunkSales Market Sales MarketFigure 7.112 Virtualized switch interconnect links So far, we've talked about some concepts that may have once been familiar, but then we're moving into a new area: layer 3.7.3.3 Layer 3 Interface VirtualizationWe create multiple Layer 2 VLANs that cannot communicate with each other, and then connect the switches to each other over a Trunk link. Each Layer 2 VLAN has its own TCP/IP subnet, or broadcast domain, but if you want to communicate with other VLANs, you need to use routing, which requires a Layer 3 interface. To accomplish this, we can connect a physical Layer 3 device interface for each VLAN, as shown in Figure 7.12.