Community Record
25
Posts
12
Kudos
2
Solutions
Badges
Alemabrahao is correct, you can use any router with Meraki Switches, we did for a few years before moving over to the MX devices. I hope you can get them talked into using the MX, as you probably know already, they are nice to use if you already have the switches in the dashboard.
... View more
Apr 11 2022
1:24 PM
2 Kudos
It is the model that is listed on the Meraki datasheet you link to. They are sold as Cisco SFPs now that is what it says on the box they came in. It is the MA-SFP-1GB-SX, and they are not cheap, but now I have some, as well as others we use, so if I have an issue, I can put a supported model on each end of the connection. The firmware upgrade fixed the issue. Thank you to all for your help.
... View more
Apr 11 2022
1:17 PM
2 Kudos
After upgrading the switches to 15.10 the SFP ports now work. Thank you rymiles.
... View more
Apr 11 2022
9:06 AM
OK, will try the upgrade to latest firmware and report back in a little while. Thank you.
... View more
Apr 11 2022
8:32 AM
We have two MS210-24P switches set up in a stack. I currently have an MS320-24 with SFP to a MS120-24P SFP working for a long time. I need to move the SFP connection from the MS320 to the newly added MS210 stack. I have purchased Cisco SFP modules for both ends, and the switches do see the SFP modules, but no connection. The same fiber and modules will work in the MS320, but will not work in either of the stacked MS210 switches. I have checked and flipped the fiber connections, still no go. I have tried different SFP ports on both MS210's, still no go. I can put the module and fiber back to the MS320 and it will connect. I have looked over all my settings and cannot find anything so far that should prevent this from working. After looking online in the forum I did find there is an issue with certain firmware not initializing the SFP module, but it seems to be on my switches, at least it names them and shows the serial number for each. I am on firmware 15.2 for all of the switches, could the firmware be the issue here? Any other suggestions to try? Thank you. MCITdept
... View more
Dec 1 2021
11:02 AM
I can't tell you how many times I didn't realize how big a change was going to be beforehand. It always seems to find a way to affect more than what you first realize. Good you got things figured out, and are getting some help with getting it right. You must have a pretty huge network, and a complicated one at that. Good luck!
... View more
Nov 18 2021
5:12 PM
Well, start in your dashboard. Is there any other devices, or networks that you can see that have the IPs in your static routes? Are the other network devices a different brand than Meraki? Can you log into those devices, like the DHCP server, or any other device that is part of the network. If that does not work, try tracing out cables that are connected to your MX, and see where they go, you might find the static route devices if they are onsite, or a part of your local network. Bottom line is, you have to configure the VLAN on another device it sounds like, not sure what that device is though. Look for the IP of the DHCP server on your network, is it another router? There are many tools you can use to find IPs on your network, try some of those. Go from there! Good luck!
... View more
Nov 17 2021
10:07 AM
Do you know what the static routes point to? A layer 3 switch? Another router? Need more.
... View more
Nov 15 2021
10:45 AM
OK, is the second router the main gateway to the internet, is it even the main router? We know you have at least two routers at this location, are those all the routers at this location? Or are there others that those static routes point to? Please give us more information, as it is too hard to imagine what you have, and help you. You can change the information or IPs, so you don't give out anything you need to keep private.
... View more
Nov 10 2021
1:08 PM
If you also have VLAN-1 set to NOT hand out DHCP, then either you must assign static IPs to everything, or you have another device on-site that is handing out DHCP addresses. Since you are getting a 169 address in VLAN-3, something else has to hand out IPs, or you have to turn DHCP on, on the MX. Do you have another router that is acting as the DHCP server? It looks like you have a tremendous amount of IPs in your network, with the /16 setup. If you just need to add a new VLAN, and just get internet access on it, then as long as the MX you are configuring this on, is the main router, then I would set it up in a different subnet than 10.x.x.x. Something like 192.168.x.x, a subnet you are not using or will not overlap anywhere. Then just set up firewall rules to block the communication between all your other subnets, and the new one. Unless we are not seeing the whole picture, which seems pretty likely, it should not be too hard. Sadly, it is hard to say what is right without knowing more about your configuration, and what you are doing.
... View more
Nov 4 2021
8:15 AM
Sounds like your new VLAN-3 does not have DHCP configured, if you are getting a 169. self assigned IP. Go to Security & SD-WAN then DHCP, on your Meraki dashboard, then check and see if your VLAN-3 is configured to hand out IPs in the correct subnet.
... View more
My Accepted Solutions
Subject | Views | Posted |
---|---|---|
1064 | Apr 12 2022 5:26 AM | |
7391 | Nov 18 2021 5:12 PM |
My Top Kudoed Posts
Subject | Kudos | Views |
---|---|---|
2 | 1064 | |
2 | 3570 | |
2 | 3583 |