Meraki

PeteStan · ‎May 15 2019

Thanks BrechtSchamp. That makes perfect sense and thanks for the link!

PeteStan · ‎May 15 2019

Hi, Is it possible to change the port type (access to trunk or vice versa) from the local device page or is a factory reset the only option? I had a look around on the local device page, but I couldn't see this as an option on the switch ports configuration tab. Example - if the uplink port type was changed from trunk to access and broke connection to the internet. It would be easier to just change port type back again from the local access page rather than factory resetting the switch. Thanks, Pete

PeteStan · ‎May 8 2019

Hi PhilipDAth, Thanks for the confirmation. I actually found an old TZ400 in our storeroom, so was able to lab this up with 2 Meraki switches (MS350 and 320) about 2 hours ago, and confirm what I suspected and you had confirmed. The SVI I created was already in the transit vlan, and I left the management IP unchanged (what I was referring as the local IP), and changed the default route to the new sub interface I created on the Sonicwall (10.0.0.2). As soon as I did this I lost internet connectivity. After changing the management IP to 10.0.0.3 and vlan tag to 100, it worked. Thanks for your assistance and confirmation 🙂

PeteStan · ‎May 8 2019

Currently our Sonicwall firewall is directly connected to our Meraki MS425 core switch. The Sonicwall is in the same vlan as the corp data vlan, with a default route on the Meraki to the IP of the LAN interface of the Sonicwall. In preparation for a firewall upgrade to a Palo Alto, I am going to be implementing a transit vlan to the firewall and am wanting to know if the local IP of the MS425 will need to change to an IP in the transit vlan. The local IP is currently in the corp data vlan. I would lab this up to test, but don't have spare equipment right now. Example: Corp data vlan 172.30.0.0 /24 vlan 1 Firewall IP: 172.30.0.254 SVI on Meraki core: 172.30.0.1 Local IP of core: 172.30.1.2 Transit vlan 10.0.0.0 /29 vlan 100 SVI of Transit vlan on Meraki: 10.0.0.1 New IP of Sonicwall LAN interface: 10.0.0.2 Thanks, Pete

PeteStan · ‎Apr 6 2019

Thanks for your thorough explanation MerakiDave. That makes sense. We were intending to use the device for an area in a building that only had 1 CAT5e run, to run an AP and power 2 IP phones and connect the laptops via the phone. We had a spare MR30H in inventory, but it doesn't look like it will carry all the vlans for the voice, data and wifi networks that we need. Ideally I'd prefer to have more wired cabling run into that area, but for reasons I won't go into, it's not an option (politics lol). I think I'll go with an MS120-8 switch and an MR42 AP instead. Thanks again for your responses PhilipDAth and MerakiDave!

PeteStan · ‎Apr 5 2019

Ok PhilipDAth if you agree, then I'm definitely not missing anything! Thanks.

PeteStan · ‎Apr 5 2019

Hi there, I've just had my first experience with configuring the wired ports on a MR30H, and I'm just trying to wrap my head around why Meraki is using SSIDs and port profiles, instead of the same method of configuring the wired ports as the MS switches. It just seems so convoluted and unintuitive, that Meraki must have a methodology and reasoning that I've missed. If anyone could shed some light, that would be great 🙂

PeteStan · ‎Mar 6 2019

I was using one for a sunglasses bag for a while, when I misplaced my original case. I've since found the original but it was a good substitute when I needed it 🙂

Meraki

Community

About PeteStan

PeteStan

Community Record

Badges

Re: Change port type in local device page

Change port type in local device page

Re: Local IP and implementing transit vlan

Local IP and implementing transit vlan

Re: Reasoning for MR30H port configuration

Re: Reasoning for MR30H port configuration

Reasoning for MR30H port configuration

Re: Recycling the power cord bags

Re: Change port type in local device page

Re: Reasoning for MR30H port configuration

Re: Recycling the power cord bags