Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About HeyCori
HeyCori
Comes here often
Member since Nov 3, 2021
Dec 1 2021
Community Record
11
Posts
0
Kudos
0
Solutions
Badges
Dec 1 2021
9:54 AM
After a few days off, I came back to this and got approval to bring in help from our vendor NSI. Maaaan did I open a can of worms. We made a few changes but primarily the biggest issue is that the switches/ports aren't trunked. And in order to get the new VLAN working system wide, they will need to be trunked. Now our vendor is going to assist in getting all the devices updated. Thanks to everyone for their assistance. You basically help me get like 75% of the way there! I didn't realize this was going to be a major overhaul beforehand!
... View more
Nov 18 2021
11:08 AM
As far as I can tell, the 10.0 points to what we have labeled as our MDF Core. Where do I look to see where all the static routes point to? Thanks! Note: I'm on a small vaca after today so I won't be able to do any tinkering until next week.
... View more
Nov 16 2021
10:01 AM
We have 4 static routes. Each one with a different subnet range. Two I recognize because it's our internal, 10.x and our public IP, 152.x. The two others (192.x and 172.x) we don't usually do anything with. And they all use the same gateway IP. I hope that was the information you were looking. Thanks!
... View more
Nov 15 2021
10:16 AM
We do have another device onsite for DHCP addresses. I set VLAN 3 to "Relay DHCP to another server" and then added the IP address for that server. However, the DHCP is on a 10.0 and not the 10.30 I was attempting to set up, so I'm guessing that's why they're not talking to each other. If I were to add a 192.168.x.x, would I still have to assign static IP addresses?
... View more
Nov 10 2021
9:43 AM
I haven't forgotten about this. Unfortunately, I'm knee deep in setting up our new library and I keep getting hit with one problem after another. 🤣😭 I did talk to our of our network guys and he said he's also going to check it out when he gets a chance. But to answer MCITDept. I switched the VLAN to "Do not respond to DHCP requests" because that is what VLAN 1 is set to. Sadly, that didn't resolve the issue. However, I have a device for testing which I gave a static IP to, and I can see it on the network, I just can't get access to the Internet.
... View more
Nov 3 2021
1:00 PM
I know one of the static routes is labeled as our public IP block, and the other is our internal network. There are two more which our vendor set up but I'm not sure what they are used for.
... View more
Nov 3 2021
12:58 PM
Yes, we have several sites that range from 10.0 - 10.11. If I'm understanding you correctly, because we fall under scenario 3, I should leave the static routes as they are. Right now I'm trying to figure out why I can't access the internet. As a test, I have one AP broadcasting the network I want to segregate. Within that SSID, I have the VLAN ID set to 3, same as the VLAN I just made. I can connect to that network but I can't access the internet so I must be missing a step somewhere. EDIT: Meant to add that when I connect to the SSID, I get a 169. IP address instead of something on the network.
... View more
Nov 3 2021
10:57 AM
Are you suggesting that I need to create another static route for the VLAN to work on?
... View more
Nov 3 2021
10:43 AM
Yes. I see the 10.0.0.0/8 along with a few other static routes.
... View more
Nov 3 2021
10:34 AM
Thanks for the info! The goal is to create a network that can access the internet but is also separate from our main VLAN. I'm hoping this will do the trick. I'm learning a lot of this from scratch since our organization is trying to save money by not calling our vendor. 😆 Now that I have the VLAN created, it's just a matter of figuring out how to attach it to certain APs and making sure internet access is still available.
... View more
Nov 3 2021
9:49 AM
Hello everyone! So I am very new at creating VLANs and using the Meraki dashboard. Originally, a separate vendor created our network. The VLAN they set up looks like this, MX: 10.0.255.254 Subnet: 10.0.0.0/16 I created a separate VLAN using, MX: 10.30.0.1 Subnet: 10.30.0.0/16 However, upon making the changes, I received this message, The VLAN subnets 10.0.0.0/16 and 10.30.0.0/16 and client VPN subnet 172.31.0.0/24 overlap with the static LAN route subnets 10.0.0.0/8 and 172.16.0.0/12. IP traffic will be routed to the smallest subnet that contains the IP address. I was hoping someone could explain exactly what that means. Like, will it affect the network, or VPN, in any noticeable way? Additionally, does anyone have a recommendation for a better way to set up the VLAN as to not receive this message? Thanks!
... View more
© 2024 Cisco Systems, Inc.
