Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About ccraddock
ccraddock
Here to help
Member since Mar 19, 2019
Mar 28 2019
Community Record
15
Posts
3
Kudos
0
Solutions
Badges
Mar 28 2019
12:23 PM
1 Kudo
I see. So in essence no vlans (except 1) exist on a meraki switch until you either 1) create an SVI for that vlan or 2) assign a switchport to a specific vlan? In both cases, those vlans will be allowed on any trunk set to allow "all" vlans? Am I understanding that? If so I guess its not much different than in IOS where when you try to assign a port to a vlan that doesn't yet exists, the switch will just create it for you.
... View more
Mar 28 2019
10:27 AM
@kYutobi , Thanks for the reply! This begs the question: If there is no way to "create" vlans directly on the Meraki switch, is it safe to assume that all possible vlans are already "created" and that all you have to do is assign vlans to ports and trunks? Ive spent my entire career having to "create" vlans before they can be used, but the Meraki switches seem to already know about them ahead of time. I'm a little confused as to how that works. Thanks.
... View more
Mar 28 2019
9:48 AM
Dear community, I had a quick question regarding the trunking mechanism on the Meraki switches. When you set a port to trunk mode and allow all vlans on that trunk, will it automatically allow vlans on the trunk as you assign ports to their respective vlan? For instance, if I assigned port 1 to vlan 300 and port 2 to vlan 400, will the trunks automatically start trunking for and forwarding for those vlans on the trunk? Or is it better to manually specify exactly which vlans are allowed on the trunk to make sure they are forwarding on that trunk? On IOS I would just run a "show interfaces trunk" and a "show spanning-tree interface" to see what the forwarding action was on a specific interface. Unfortunately I cannot find a way to verify which vlans the trunks are forwarding for, its kind of annoying actually. Thanks.
... View more
Mar 28 2019
7:47 AM
@PhilipDAth , Thanks for the reply! After mulling over the options and considering your advice I think you're right. What I'm going to do is create a separate interface on the next hop firewall that will have the same IP address as the current default gateway SVI (10.30.30.1). This way, once the connection is moved to the Meraki switch stack, all it will have to do is update its ARP and MAC table and be off and running. This also alleviates me from having to reconfigure all my devices as they are all already statically configured. Ill have to trunk VLAN 300 across which usually cross campus VLANs bug me but in this case its necessary so an exception is warranted. Thanks again for your help!
... View more
Mar 27 2019
11:21 AM
Dear Community, I am in a bit of a conundrum. We are going to replace our existing network infrastructure (Catalyst 4510 switches and Aruba Wireless) with four MS-350 Switches and 16 MR33 AP's. The switches are combined into 2 separate stacks (17th floor and 2nd floor) with the 2nd floor stack being the distribution stack the 17th floor feeds into. All the routing will be done via the 2nd floor stack with the 17th floor stack pretty much being a Layer 2 stack. This equipment is currently getting access to the internet via the existing network infrastructure by uplinking the 2nd floor stack to the existing 4510 (on VLAN 300) that acts as the default gateway. All the Meraki gear is on VLAN 300 (10.30.30.0/24) with the VLAN 300 SVI (10.30.30.1) existing on the Catalyst 4510 switch acting as the DG for the Meraki VLAN 300. When I remove the old 4510 from production, how can I go about getting the Meraki gear back online? The 2nd floor Meraki stack already has all the necessary routing information configured in it that mirrors that of the 4510 (SVI's and default route). Should I just create a VLAN 300 SVI (10.30.30.2) on the 2nd floor Meraki switch stack and tell all equipment to use that as the default gateway before moving the uplink for the default route next hop onto the 2nd floor stack and removing the old 4510? Will that even work? Im assuming it might as it will look to itself for a route and use the default route I already have configured. or, can I just change the default gateway in the switch and AP configs to use the default route next hop IP to the datacenter (10.125.0.1)? Im not quite sure how to approach getting this gear back online with the portal after I move the Datacenter uplink from the 4510 to the 2nd floor stack, the 4510 will no longer have any uplink to the Datacenter, it'll essentially be an airgapped device at that point. Please let me know your thoughts on the best way to do if this is even making sense. Thanks.
... View more
Mar 26 2019
6:46 AM
1 Kudo
@jdsilva , Thanks for the reply and the answer. I really appreciate it!
... View more
Mar 25 2019
2:00 PM
Dear Community, I am still kind of new to Meraki to please forgive my ignorance. I am trying to figure out how I can make a single switchport into a Layer 3 routed port, similar to using the "no switchport" command on a catalyst device. I have successfully created several Layer 3 routed SVI's in the Routing&DHCP section with assigned VLAN's but am not able to see how I can assign an IP address to a single switchport. Is this possible? Or do I have to create a VLAN SVI and then assign only that one switchport to that VLAN? I checked under the L3 tab of the actual switchport in question but didnt see anywhere to actually assign an IP address to that individual switchport. Thanks.
... View more
Mar 25 2019
8:47 AM
It appears PMK caching and OKC was the answer I was looking for. I am glad to know the Meraki AP's do this by default. As far as 802.11r is concerned, ill probably attempt it in adaptive mode to start as we will have a separte SSID using WPA2-PSK that allows folks to connect their mobile devices to. Thanks again everyone for your efforts to assist me.
... View more
Mar 25 2019
6:39 AM
@NolanHerring, @PhilipDAth , Thank you both so much for your responses. these are extremely helpful. I will fire up a test SSID in the next couple of days to test and see if I can connect with the Windows 8 and Windows 10 devices using 802.11r. All of the AP's will be on the same exact VLAN/Subnet, there will be no Layer 3 roaming in our environment. Can I assume that when 802.1x is being used that the AP that is initially connected to will then broadcast or otherwise communicate with all other AP's in the VLAN about that connection? Making roaming faster? If so is this some built in "behind the scenes" feature? if this is the case then it makes sense as to why all the AP's need to be on the same subnet. Thanks.
... View more
Mar 22 2019
7:11 AM
@NolanHerring , Thanks for the reply! We run a mix of Windows 8 and Windows 10 devices, we also have roughly 10 or 12 Mac users all running anywhere from Sierra, to High Sierra and possibly Mojave. My concern is that we are moving away from a controller based wireless model where the controller handles all the fast roaming features to Meraki, and Im not sure how the Meraki AP's coordinate with eachother regarding the authentication keys and such. I would think that Meraki would have thought of this already though. Like I said, I have not deployed the Meraki equipment yet but plan to do so in the next couple weeks.
... View more
Mar 21 2019
2:29 PM
Dear Community, I am new to Meraki wireless and so I had a few concerns regarding the roaming action with Meraki Wireless when an SSID uses 802.1x. We have not currently deployed our Meraki wireless network and are still running our legacy Aruba Wireless network. We are currently using EAP-TLS with a Microsoft NPS Radius server for one of our corporate SSID's. All of the wireless clients have user certificates that are presented to the server during authentication (Windows devices and Macbooks are present in the environment). Currently, machines are able to roam pretty seamlessly between AP's. The SSIDs will be operating in bridge mode with all AP's on the same subnet. We are using MR33 AP's on MR25.13 Firmware. My questions are these: 1) Are there any issues I should be aware of as it pertains to roaming between Meraki AP's when connected to an SSID that requires 802.1x authentication? I was reading that 802.11r is supposed to help this but also saw that it could cause issues? I was also reading that PEAP "fast reconnect" is an option but we are not running PEAP. 2) If 802.11r is enabled, should I be using "Enabled" or "Adaptive" mode? Please let me know what you think? I have not yet deployed the wireless but plan to do so in the next couple of weeks. Thanks.
... View more
Mar 19 2019
2:08 PM
@BrechtSchamp , Wow! I feel dumb! I didn't press enter! That worked, thanks!
... View more
Mar 19 2019
1:44 PM
@BlakeRichardson , Even with it online and registered I still cannot create a tag. I may have to open a TAC case with Meraki.
... View more
Mar 19 2019
1:25 PM
1 Kudo
@BlakeRichardson , This is a new meraki rollout so nothing is in production yet. I have other AP's that have been registered to the portal but are also offline, same issue. Ill bring the AP in question online and try it again and report back. Thanks.
... View more
Mar 19 2019
12:47 PM
Dear Community, I am trying to apply an AP Tag to an AP but the dashboard will not let me save it. I am going to Wireless-->Access Points and then clicking on the AP. IN the AP settings I am going to Tags and clicking on the edit icon. When I type the name of the tag the Save button is grayed out and will not let me save it. I have also tried clicking the check box next to the AP and selecting Edit in the Access Points page, the Add button is also grayed out. The AP is offline and has never been registered with the portal. Any ideas? Thanks.
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 1 | 3005 | |
| 1 | 3661 | |
| 1 | 4673 |
© 2024 Cisco Systems, Inc.
