Avatar of amanzoor
amanzoor
Flag for Canada asked on

Understanding the route between 2 local subnets

Hi there;
So I made a new subnet 10.10.2.0/23 to have more ip space.  My existing subnet 10.10.10.0/24 works fine but was getting short with ip's (it works fine but I needed to check the new subnet first).
I made the new subnet in AD sites.  Also assigned a secondary local IP of 10.10.3.254 to my router.  Just wanted to make myself sure if my new subnet is all set to go:
Here under you will find my brocade switch showrun and vlans.  Also a route print from a windows 8.1 client.  

The idea is I would like to understand if anymore things need to be done on my switch so that the 2 subnets i.e 10.10.10.0/24 and 10.10.2.0/23 talk to each other (meaning servers from one subnet be accessed by other?
Need help
brocade6450.txt
RoutersSwitches / Hubs

Avatar of undefined
Last Comment
amanzoor

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Akinsd

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
amanzoor

ASKER
Akinsd
***********If the 2 subnets were created on the switch and ip routing is enabled (which is, by default********
Thanks for the reply.  Could you please look at my show run above and see I have not created any subnets on the switch (brocade) show run is attached.
Thanks
Qlemo

Your switch should not be involved, as it does not build any VLANs (but on port 1/1/48).
The default gateway is your router. That is fine, as long as the router knows both subnets. Traffic between subnets will hence always flow thru the router (doubling its network load).

However, the question is why you didn't just expand your existing network 10.10.10.0/24 to 10.10.10.0/23  or 10.10.8.0/22? That way all you had to do is to change the subnet mask, and the router would not have to be involved.
amanzoor

ASKER
Qlemo,
I just wanted to try first with a new subnet leaving the 10.10.10.0/24 alone.  Now that I cannot the new subnet 10.10.2.0/23 is unable to check shared folders on 10.10.10.0/24.  I will go with the option you suggested to just change the mask.  i.e 10.10.10.0/23.
Question:  I will make a new subnet with 10.10.10.0/23 as the AD sites and services will not let me change unless the existing subnet is deleted.?
-I am also not sure if the subnet with mask 10.10.10.0/23 is allowed in my router?  How do I find this?
-Then I will simply make a new scope in DHCP with /23 and things should be fine?
Need help with these questions before change.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
SOLUTION
Qlemo

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
amanzoor

ASKER
My firewall sitting in between the router and the switch was infact blocking the interVlan traffic, the moment I unplugged it and plug it back in .  Things worked!!.  I really appreciate your time.