Ether-channel Redundancy, OSPF/EIGRP, VLANS, WLAN Controller - Looping Issue?

[DRG_]

Hello,

I've racked my brain so much I don't know what to do. I am testing this lab for personal study reasons. This is all being done on physical equipment not connected to the internet. The WLAN controller is a 2 in 1 so it has a 24 port 3750g connected to it.

Attached below is a rough topology of what it looks like. I have ether channel at the core for redundancy and have OSPF and EIGRP redistributed there. I have 2 VLAN, one for wireless (40) and one for general access (10). What's confusing me is that I am having no issues connecting to VLAN 40 via hardwire or wireless. The issue is VLAN 10. The laptop will pull a dhcp address and gateway but I cannot ping anything. I can't even ping the gateway. I just don't understand why one works and the other doesn't. I used Wireshark when I plugged into VLAN 10 and immediately started seeing "loop" error packets.

I don't know the best way to go about doing this so I also tried taking routing off of the port-channels and tried trunking them. 

I'm assuming that this is a looping issue but I must admit I am not that great at the switching side of things. Any help would be appreciated. Attached below and the configs with the routing tables. Please let me know if you need anymore information. 

Thank You,

Edit: Added Topology

[Peter Paluch · Accepted solution]

Hello,

I don't believe you are looking at a looping condition. If you see the LOOP frames in Wireshark coming in every 10 seconds, they are not an indication of a loop; they are just infrequent frames sent out from Catalyst switchports to detect self-looped ports.

One obvious typo I could see in your configuration is that in VLAN 10, the default gateway you are assigning to clients is 10.0.10.1 - but the VLAN 10 SVI on MLS-Core is 10.0.10.2. This could explain a lot.

I am not entirely certain what is the goal of your particular configuration you have there: Your EIGRP and OSPF switches have both a routed uplink and a switched trunk toward the core. Is this for any particular reason? You are not really terminating any VLANs on the EIGRP/OSPF MLS switches, and so the routing part there is unnecessary.

Best regards,
Peter

[DRG_]

Peter,

Thank you for you comment. After taking a break from it and coming back, I noticed this whole time the port I was connected to was not on VLAN 10. I am now able to ping everything. I thought I was plugged into the correct port the whole time. I was overlooking this issue and its frustrating that I wasted so much time on it and I'm embarrassed lol.

The goal of this project is to have redundancy between MLS-Core, Controller, and MLS-Backup as well as MLS-OSPF and MLS-EIGRP. The reason I have routed and trunked links is because I am unsure of how else I would be able to get VLANs 10,40 to MLS-OSPF and MLS-EIGRP switches while having EIGRP in the mix. Normally I would just use one IGP like you should but I know redistributing protocols is important when migrations happen etc. I am a student so I there are a lot of things that I may not understand. 

Is there a more efficient way to go about this?

Thank You,

DRG