- About Pete_RMOW
turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community Record
13
Posts
1
Kudos
0
Solutions
Badges
Tuesday
Thanks Zilla! I did not know this function existed, so thanks for the tip. It also looks like they can only be moved one at a time, but that's all. What's an extra few clicks haha
... View more
Tuesday
Thanks for the info Zilla. I'm not quite sure what you mean by "moved". I'm assuming, manually re-creating. I have a couple of new switches on order, so when they'll come in, I'll test this out.
... View more
a week ago
When cloning a switch, does the cloning process copy the layer 3 interfaces, ip helper address, static routes and default routes that I have also created on the reference/source switch? The info provided in the "What will this copy?" link in the dashboard doesn't mention the above items. I would normally test before making a post, but I don't have any spare switches available at the moment to test. Thanks.
... View more
3 weeks ago
Thanks MacuserJim. I'll definitely start playing around more with the templates. I took screenshots of all my L3 interfaces, vlan config, etc, so the reconfig of the core was only about 15mins. Thanks again! Pete
... View more
3 weeks ago
Thanks MacuserJim. That makes sense. I'm newish to Meraki and we haven't really started using templates for networks. These were already set up when I started here, and it looks like the dashboard networks were just set up mainly as logical containers for our different locations. So I created a test network, and placed the lab switches in there when I was testing, with the intention of moving them to their respective network after I had finished testing and they were ready to production. I'm guessing that I'm not using Networks for their intended purpose.
... View more
I'm wondering if it is possible to move a switch to a new network in the dashboard without losing all of the port config info, etc? If not, can anyone explain Meraki's reasoning for wiping the config info when moving switches between networks? I created a test network that contained all of the test switches. They've now been configured ready for production and are ready to be moved into the production networks in the dashboard. I don't want to lose all the work I've just done configuring the trunks and allowed vlans, etc just because I'm moving it to a different network.
... View more
a month ago
1 Kudo
I can confirm that Addon and FS.com SFPs work in the Meraki switches, but as PhilipDAth mentioned you may run into issues with Cisco Meraki support with non-genuine SFPs. For this reason, I keep a few genuine Cisco Meraki SFPs as spare.
... View more
10-15-2018
02:06 PM
I have inherited a network that currently has a HP Procurve switch as our core that we are replacing with a Meraki MS425-32. The remote sites connecting to the HP Procurve are all Meraki MS switches (220, 225, 320, 350's). I'm doing some cutover planning, and have found what I think is the data vlans are going across trunk links to remote sites untagged and I would like to confirm this is the case based on the info below. In addition it looks like the trunks all have a native vlan mismatch. Output from show vlan ports <interface number> detail (names and vlan tags changed for privacy) VLAN ID Name | Status Voice Jumbo Mode ------- -------------------- + ---------- ----- ----- -------- 3 Sales DATA | Port-based No No Untagged 30 Sales VOICE | Port-based Yes No Tagged The port on the Meraki at the other end of this link is set to Trunk, native vlan 1, allowed vlans 1,3, 30 All end device ports on the switch are set to access, vlan 1, voice vlan 30 Everything does work and clients can communicate to the internet and also to devices in other subnets with similar setup eg. vlan 2 HR DATA, HR VOICE 20, etc I just want to confirm that the untagged setting for vlan 3 data across the trunk is the same thing as configuring the native vlan in Cisco and Meraki world, and mismatching these numbers is considered a native vlan mismatch in Cisco Meraki terms. (The dashboard doesn't create a native vlan mismatch warning for the switches configured this way between the HP and Meraki switches, as it would for a native vlan mismatch between 2 Meraki switches). Based on answers, I will have some more follow on questions, so thanks in advance :)
... View more
10-09-2018
05:19 PM
Hi, I am trying to rename an administrator in our Meraki dashboard due to a spelling mistake, but the option to change the name is greyed out. Can I rename an administrator or do I need to delete and re-create the account? Thanks, Pete
... View more
Hi PhillipDAth, Thanks for your reply. I actually just resolved the issue by changing the port that the FW is connected to a trunk. What I'm not understanding is why switching the port on the MS425 to a trunk made things work, when the port type on the FW is still an access port in vlan 1. One thing I did fail to mention in my original post that this is currently all set up in a lab (completely separate from production network). I am using an MX64 for the lab firewall. The production FW is an older Sonicwall. I'm trying to lab up as much as possible to test and take any guess work out come cut over time. Static routes were in place on the FW so that was all good. The 350s don't have L3 routing enabled , so no L3 interfaces configured. They have a static IP in their respective vlans 2 and 3 and their gateways are the L3 vlan interfaces configured on the upstream MS425 core switch. Thanks again, appreciate the help.
... View more
Hi all, I'm hoping to get some advice on VLANs and routing to the internet. Background: We are replacing our core switch that is currently an older HP Procurve with an Meraki MS-425. There are a few bad practices with the current design, but the first phase of the project is to just swap out the HP with the Meraki and keep the config as similar as possible (default route that points to the firewall, IP subnets, vlan numbers, native vlans on trunks etc). We have an older firewall (also scheduled to be replaced after this project and a network redesign) that is connected to an access port on vlan 1 on the HP core switch. A default route on the HP points to the internal IP of this firewall. All VLAN interfaces for the other subnets are set up on the HP core switch and this switch does our inter vlan routing. I can ping to the internet eg 8.8.8.8 from any switch in the network (core and access switches) and end devices connected to these switches. I've essentially inputted this same config into the MS-425. All trunks have native vlan 1 and allowing all vlans for testing purposes right now. I have connected a couple of MS-350s to the MS-425 and configured their vlan, LAN IP corresponding to that vlan, and the gateway as the corresponding VLAN interface IP on the MS-425. The Ms-350 on vlan 1 can get to the Meraki cloud, but the 350s on vlans 2 and 3 cannot get to the Meraki cloud. I would have thought that setting their gateway to the vlan interface on the MS425 which is the upstream switch, and have the default route on the MS425 pointing to the FW would allow internet access, but I might be missing something here. Example of config: MS425 Core switch vlan 1 interface 172.16.1.1 /24 vlan 2 interface 10.0.2.1 /24 vlan 3 interface 10.0.3.1/24 Default route 0.0.0.0 0.0.0.0 172.16.1.254 (the firewall) LAN IP 172.16.1.2 Vlan1 Gateway 172.16.1.254 dns 8.8.8.8 All links to access switches are trunks with native vlan 1, allow all vlans (for testing) MS350 that can connect to Meraki cloud (access switch) LAN IP 172.16.1.10 vlan 1 gateway 172.16.1.1 dns 8.8.8.8 MS 350 #1 that cannot connect to Meraki cloud (access switch) LAN IP 10.0.2.10 vlan 2 gateway 10.0.2.1 dns 8.8.8.8 MS 350 #2 that cannot connect to the internet (access switch) LAN IP 10.0.3.10 vlan 3 gateway 10.0.3.1 dns 8.8.8.8 Any advice or help would be greatly appreciated.
... View more
09-18-2018
03:42 PM
I could not find any datasheets on this either when I wondered the same thing a few months ago, but I'm almost positive it is only 1Gb. I tried to connect an MS-425 using the MA-SFP-1GB-TX to an older 100mb HP Procurve switch (in a lab) and would not detect a link (no link lights on either switch). I tried 2 different MA-SFP-1GB-TX to make sure and same scenario on both. (Also tried the Cisco GLC-T with the same result) I then connected the MS-425 to both a new HP 1GB Procurve and also an MS250 and worked without any issues.
... View more
Latest Tags
No tags yet
