Hello everyone, this is an update/follow-up to the following thread seen below
https://community.cisco.com/t5/routing/networking-switching-configuration-lab/m-p/5336328#M412991
Before I keep maintaining this format, please let me know if I should continue making new threads to add on to this chain of labs. Or if I should keep them associated to one thread to avoid spam. Since I plan on making these until I understand all the concepts within the CCNA and can design a network fully with all ranges of topics included into one big mega lab. I don't want to spam the Cisco community either with my labs.
The goal in the short-term is to work on each topic within the CCNA exam with comfort, without needing google to refer to any commands. At this time I am comfortable with static routing, STP, VTP, VLANs(trunking/access ports), Switch customization (Editing interfaces with descriptions, adding hostnames to a switch/router etc.) and I am beginning to delve into dynamic routing.
Be aware these labs in many cases may not be THE best design for networks, or follow the common practices in the field. This is merely for practice for myself in dealing with CiscoIOS as a whole, and to improve my understanding of the networking field.
I can say in my first post I had a few gentlemen provide very helpful advice and feedback. I was able to follow and make some of the changes they suggested. Also following Joseph's advice I did attempt to add the pkt file here but received the error message below
I know I must be doing something wrong, but wanted to share. Anyway read below for the lab:
Warning this is a long thread about a lab so to not waste your time understand this is coming from a "noob" in the networking field. if you're new as well maybe this can benefit you.
Above is after the changes were made, below is before:
As you can see, I removed the extra links from DSW's 1 & 2 leading to ASW1(Switch2) ASW2(Switch 3) ASW3(Switch4). Now each link from DSW's is only feeding to ASW1 and 3. I realize now, the point of the DSW's are to feed directly into the ASW's, but I instead left the two links instead.
I took the advice of adding Etherchannel links feeding from CoreSW to both DSW's. Configuring both PO2 (CoreSW -> DSW1) and PO3 (CoreSW -> DSW2). And maintained the PO1 as the link between DSW 1 & 2. I also took the advice of load-balancing the root bridges for STP as DSW2 being the root primary of VLAN 1 and 8 (which I may need to adjust due to the removal of VLAN 1 entirely) and the secondary as DSW2 for VLANs 12, 24, and 34
Below are a few mistakes/things I learned in the process of fixing them:
1. Upon editing the PO3 Etherchannel link from DSW2 -> CoreSW. and adjusting the root primary/secondary switches I made the mistake of selecting a wrong interface. An interface that was already being used for PO1 to DSW1. Here are some of my notes for this
Issue: Prior to load-balancing the VLAN roots from DSW2 -
I had all VLANs set to the spanning-tree vlan 1,8,12,24,34 root primary command. Meaning all those listed VLAN's are the root VLAN for that switch.
I made load-balancing adjustments below
After change the following is the layout:
DSW1 VLAN(s) root- 12, 24, and 34
DSW2 VLAN(s) root- 1 and 8
PC5-
ASW1 above
While connected to VLAN 8, along with the access port set for the proper VLAN
I knew it couldn't be due to the interface not associated with that VLAN.
I found no ping was being accepted
I also found there wasn't ANY ping being accepted for any VLAN (12, 24, or 34)
HOWEVER, if we plug that same PC5 into our ASW3 which is directly connected to DSW2 (who is the root for the VLAN
The answer seems to be DSW1 cannot receive traffic from VLAN 8 off ASW1, therefore it cannot FWD that traffic to DSW2 or the L3 Core. I also found the following
DSW1 is BLK all VLAN 8 ports by default.
After removing the Port Channel (PO1) on both DSW1 and 2
Then entering those same interfaces and no shutdown which turned them back on, a successful ping was made.
Another big mistake I made:
I was no longer able to ping other hosts from any of the PCs. All of them were on access switches, but it did not make any intervlan comms. After over two hours of thinking on this, I decided to run the show running-config on my L3 Core switch. Sure enough, there was no ip routing enabled. I enabled it and now
PC5 on VLAN 8 can reach PC3 (192.168.8.3 - VLAN
Moving forward, I have begun dynamic routing with RIP and EIGRP. In this topology I have used EIGRP (AS 1)
I started with three routers
Connected to the original topology is the CompA_WAN router. Next is the ISP_WAN last is the Router2. Below is there connections
(10.0.0.0/30) CompA_WAN(G0/0/2) .1-> ISP_WAN(G0/0/2) .2 | ISP_WAN(G0/0/0) .2
Using EIGRP I created dynamic routing across all three devices, entering the following:
en
conf t
router eigrp 1 - The 1 signals the AS (Autonomous System) which is essentially specific per organization (I believe this is the correct explanation)
no auto-summary
network
