02-27-2018 07:18 AM - edited 03-08-2019 02:02 PM
I'm new to the networking world and I'm trying to catch up quickly because we're short staffed here. Before our networking guy left he ordered 3 2960Xs and an ISR 4451 for a small branch site. Other branches have 3850s as the core at there sites. The other switches route fine using EIGRP and can communicate throughout the network. The 2960X can't I assume. Is there a way I can let the network know my 10.x.x.x/24 (data vlan) is down here at the switch? The 4451 is in a WAN EIGRP configuration so it's getting around the network fine and it's directly connected to one interface on the 2960 but that's where reachability stops. I've set up an SVI for my data vlan but I can't ping it. Any ideas?
Solved! Go to Solution.
02-27-2018 12:06 PM
02-27-2018 07:31 AM
02-27-2018 07:52 AM
Thanks Joseph I think I see what you're saying...I believe my version only supports the lan based routing so there in lies the problem. With the 2960XR you'll get the L3 routing capability. I did enable ip routing on the switch and will actually have my voice and data vlans set up there (/24 and a /25). Right now I'm directly connected to the 4451 through an interface that has a /30 ip address between the 2 which is on a separate vlan. I'm thinking if I trunk everything to that router I'd have to use that management interface thus removing the /30 address, and setting up my sub interfaces on the router. Is that what you are thinking?
02-27-2018 08:18 AM
02-27-2018 08:36 AM
You can do that or if your switch is doing basic routing you could use static routes eg -
on the switch -
"ip route 0.0.0.0 0.0.0.0 <router /30 IP>"
on the router for each of the vlans on your switch -
"ip route <subnet> <subnet mask> <switch /30 IP>"
and then redistribute those statics into EIGRP eg.
router eigrp <AS no>
Up to you really.
02-27-2018 08:42 AM - edited 02-27-2018 08:43 AM
What Jon shows, will of course work too. As to which to go use, if you were expecting "heavy" traffic between the branch VLANs, I would use Jon's approach, as it takes advantage of L3 switch performance. However, with only a data and VoIP VLANs, I would expect almost or all traffic to flow in/out the 4451, so I would let it do the routing and leave the switches just be L2 switches.
That said, Jon is also correct saying "Up to you really."
02-27-2018 11:28 AM
Also Joseph when I removed my /30 ips and trunked that interface connecting the router and the switch with my data and voice vlan making the sub interfaces on the router my gateway I lost my ability to ping from or to the switch.
02-27-2018 12:06 PM
02-27-2018 12:43 PM
Yes I put the default gateway for the switch as the address of the sub interface on my router. I added the next available address on the subnet as the vlan ip address for my data vlan. The switch interface is set to trunk my data and voice vlans as well.
02-27-2018 02:58 PM
OK putting the sub interfaces on the router did the trick Joseph. It didn't work originally because I fat fingered it. Thanks guys
02-28-2018 07:20 AM
02-28-2018 02:21 PM
Hey thank you!!
02-27-2018 11:00 AM
Hey guys had to step away for a minute. Jon I tried the static routes and redistributing into eigrp since I figured that was the quickest
but my data vlan is up/down so I can't even ping it. I do know I can't assign 2 vlans to one access port so how would I get my data vlan to a state of up/up?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: