Join Telegram Study Group ▷
Basically, this is considered to be a needle in a haystack, but if you wish to have more details regarding the LAN Distribution which would be used in CCIE Routing and Switching Lab, you might check out the courses, offered by the SPOTO.
A LAN would be considered as a high-speed, fault-tolerant data network which would be supplying connectivity to a group of computers, printers, as well as other devices which are in close proximity to each other, like an office building, a school or a home. LANs offer the users of computers, lots of benefits, which would include shared access to devices as well as applications, file exchange between connected users, and communication between users via electronic mail as well as other applications.
Section 1.1: LAN Access:
The following requirements would be needed to pre-configure.
VTP would be turned off in all switches. All required VLAN, including access-ports configuration in all relevant switches, are going to be provisioned. All required SVI interfaces in all relevant switches which would be including IP address and subnet mask are going to be provisioned.
Next, configure the network in all sites as per the requirements mentioned below:
• Access-ports should be immediately transitioning to the forwarding state upon link up, as long as they don’t receive a BPDU. Use the minimal number of commands per switch for enabling this feature.
• If an access-port would be receiving a BPDU, it should automatically shut down. Use the minimal number of commands per switch for enabling this feature.
• Ports that were shutdown should be attempted to automatically recover after 10 minutes.
• None of the switches might be able to generate a TC when any of the access ports go down.
Section 1.2: LAN Distribution:
Configure the headquarters’ network, and the large as well as medium office networks as per the following requirements:
• All trunks should always use dot1Q encapsulation.
• Negotiation of trunking protocol should have to be disabled in all switches.
• Distribution switches should initiate EtherChannel negotiation utilizing LACP.
• Access switches should never initiate EtherChannel negotiation.
• Configure layer 2 ether channels' number which would be seen in the “Diagram 1: Main topology” and “Diagram 5: Layer 2 Connections”, like that would be used only Po1 and/or Po2.
• Ensure that all ports which would be included in other channels which are effectively in use as well as bundled in the expected channel.
• Access switches should be seeing similar output:
Section 1.3: LAN Resiliency: Spanning-Tree
Configure the headquarters’ network as per the requirements mentioned below:
• SW300 must be the spanning-tree root bridge as well as would have to maintain a single SpanningTree instance for the following VLANs: 2000, 2002, 2004, 2006, 2008 (use instance number 2).
• SW301 must be the spanning-tree root bridge as well as would have to maintain a single SpanningTree instance for the following VLANs: 2001, 2003, 2005, 2007, 2009 (use instance number 1).
• All other VLANs, except 3001, would have to share the default Spanning-Tree instance.
• Ensure that interface E0/2 of SW300, as well as SW301, is a dot1q trunk and that it would be switching frames for VLAN 3001 only.
• SW300, SW301, and SW310 shouldn’t have any blocked ports for any access VLAN (i.e. 2000-2009).
• SW310 should have the least chance of being elected for the root bridge for any VLAN.
• None of the three switches might have to run more than four instances of Spanning-Tree at any point in time.
As we have already discussed that this is just a needle in a haystack, and if you wish to have more details, you might have it through the courses which are offered by the SPOTO.
