About Marco_812

Marco_812

We have noticed a lot of this on our network and have determined it is because we refurb a lot of PC laptops/tablets and Macbooks. Anymore a lot of them don't have an RJ45 port, so we use USB to RJ45 adapters, and that's what's causing our flapping because these adapters don't stay in place, they get moved from station to station during the day

Marco_812 · ‎08-11-2020

Hey thanks everybody, didn't mean to drop out on ya but I had a little unexpected Covid break and I'm back on it and I believe I have it solved! Big extra thanks to @cmr and @PhilipDAth for the clues I needed. Hooking the MacBook up directly to the Meraki MS250 did result in getting an IP address almost instantly, no interim self-assigned address. I should have read Philip's response a little more closely as I went off in my own direction researching the SG220s which led me to the Port Fast setting you referenced, although in the SG220 this is referred to as Edge Port, at least in the GUI I changed the port setting to Edge Port for a couple of the ports, connected the MacBook and Boom! 4 seconds to an IP address, even with these clunky USB to Ethernet adapters Obvious in hindsight but it turns out this wasn't a problem with the Macs at all. I had noticed that the SG220s were slow to pick up an IP address as well, but I didn't connect the dots On Cloud 9, this has been a thorn for several months. Wondering if I can pull a Costanza and leave work early on a high note

Marco_812 · ‎06-18-2020

Hello: I'm serving DHCP from an MS250 layer 3 interface down through a Cisco SG220 switch and ultimately to some Macbooks. If I've got a Windows machine connected it picks up the DHCP info fairly quickly but the Macs are very slow to pick up the DHCP and usually self-assign an IP address before eventually obtaining an IP address from the Meraki Does anybody have any tips/ideas to speed DHCP up for the MacBooks, especially perhaps in the settings for the Cisco SG220? I'm sure some of it is on the Mac side, especially if I'm using a USB to RJ45 adapter. A thunderbolt to RJ45 adapter, or if I've got an older MacBook that actually has a network port will get better results but will still self-assign an IP address before getting one via DHCP On the layer 3 interface I have no boot options set, and multicast routing is disabled The port on the Meraki is set to Trunk, with RSTP enabled and Trusted Mode not enabled On the Cisco SG220 I can ping the layer 3 interface with no problem, not really sure what else I should be looking at Any tips appreciated, or if you can point me in the direction of what I should be researching that works too, thanks much!

Marco_812 · ‎04-09-2020

Thanks for all the help, it's really appreciated. I did switch back to trunk from access but it turns out I had the native VLAN on that port set to 40, but really needed to have it set to VLAN 1, and allow VLAN 40, as per the Meraki engineer who assisted. Doing that immediately opened up that port and all devices on VLAN 40 can now see each other I did not realize that the native VLAN setting is for management purposes. Lack of networking knowledge on my part but I'm really a database guy and had inherited this project as we no longer have a network guy Thanks again, feeling good . . . until the next crisis pops up 🙂

Marco_812 · ‎04-03-2020

Thank you. As far as I can tell the vSwitch is presenting as VLAN 40 although I'm pretty sure I never actually edited it as such

Marco_812 · ‎04-02-2020

Ahh, I was not aware of that, thank you, that could very well be it. This had been setup with a 172.20.x.x network previously, but that conflicted with an existing private network already set up here so I changed that, but I did not realize I had gone beyond the bounds of a private network. Thank you!

Marco_812 · ‎04-02-2020

I'm having an issue getting a Meraki MS-250 to 'see' a device plugged in via fiber to one of the SFP ports. A lot of factors in play here . . . we have configured a Layer 3 interface on the Meraki with a DHCP server that is basically going into a dead-end isolated network. The device is a virutalized (VMWare esxi) Ubuntu server (18.04) with a regular gigabit NIC, and the fiber connection. The Ubuntu Server (IP 172.60.4.189) shows on the Layer 3 ARP Table, but not in the MAC Forwarding table, and I cannot ping it from the Meraki, nor can I ping the Meraki interface IP (172.60.4.1) from Ubuntu If I ping the Meraki, or run a traceroute from Ubuntu, and run a Packet Capture from the Meraki, I see the attempted communication but neither is successful. Also, the Ubuntu server displays on the Client List for the Meraki. The Layer 3 interface runs downstream to a couple of Cisco SG switches, and there are devices on these switches getting their IPs from the Layer 3 DCHP, but these devices are not able to ping or connect to the Ubuntu server, nor can the Ubuntu server connect to them. It would seem the Meraki is aware of the existence of the Ubuntu server, but cannot contact it for whatever reason. Port 49 is set to Access, with an open policy currently. I have tried it as Trunk as well, but with no luck. This is a project I inherited, not 100% sure of my Linux networking skills so this could very well be on the Linux side (or even VMWare) but from the packet capture and other information it would seem it's set up properly. Any pointers, tips, or links to documentation on what settings I should be using for that port, or for the Meraki itself? Thanks very much

Marco_812

Community Record

Badges

Re: MAC Flaps - Always bad or sometimes normal?

Re: Slow DHCP between Meraki MS250 => Cisco SG220 => Macbook(s)

[SOLVED] Slow DHCP between Meraki MS250 => Cisco SG220 => Macbook(s)

Re: MS250 SFP port configuration

Re: MS250 SFP port configuration

Re: MS250 SFP port configuration

[SOLVED] MS250 SFP port configuration

Re: MS250 SFP port configuration

Re: Slow DHCP between Meraki MS250 => Cisco SG220 => Macbook(s)