Meraki

Ryan_Miles · ‎Oct 14 2021

my primary feedback would be that this page https://meraki.cisco.com/support/#policies:eol and this page https://documentation.meraki.com/General_Administration/Other_Topics/Product_End-of-Life_(EOL)_Policies are often not in sync with regards to the product list. for example right now the first link ends at the poe injector while the other page has more recent EoX announcements. more than once customers have pointed to one doc and i gave to steer them to whatever the most recent link is to get accurate EoX info.

MeVan · ‎Oct 13 2021

Thanks for the responses. I had no idea firmware could rollback when moved to a new network. I updated the firmware in the new network and it's now working fine!

PhilipDAth · ‎Oct 12 2021

I've never seen an AP run a network port at a sustained 1Gb/s of load. Never. I think it would be challenging to even do so. You'd probably have to set a special lab environment to make this happen. If you don't have MGig ports the solution is relatively simple - install more APs so the load gets split over more 1Gb/s switch ports.

Ryan_Miles · ‎Oct 12 2021

I've seen cases in which downgrading to older 25.x releases helps with stability on the older AP's. It's often case by case based on config and usage. The last case I see on this opened by you was Dec 2020. Perhaps open a new case online and request a downgrade to 25.14 to test stability. You could have Support downgrade just a single AP (or however many you want) to the older release so you can contain the testing to an area before downgrading all AP's.

Ryan_Miles · ‎Oct 11 2021

how often are you seeing this event? it typically occurs when a config change is made and for a brief moment the configs are out of sync. so it's typically a benign message in warm spare configs.

GIL_Jared · ‎Oct 8 2021

[UPDATE] -- FOUND THE SOLUTION! As someone mentioned previously, the issue was with the switch config, not the device config. Netgear has a really dated UI and obscured the issue a bit. I was able to find it after digging around the other night. As seen below, I went into Switching > VLAN > VLAN Membership > Click the 3 pixel down arrow and select the VLAN ID. VLAN ID #2 and #10 had port 27/28 (the two APs having issues) as blank. Was not tagged or untagged. Once I tagged them and applied the settings the issue resolved. The APs now are able to pull clients using any SSID/VLAN and allow internet without any issues. Thank you all for the replies. It helped narrow down the issue. Take care

Gdubya · ‎Oct 8 2021

Got it figured out. Default AP policy was 5Ghz only and overriding the settings of the SSIDs.

wizard · ‎Oct 6 2021

you can vlsm in cidr notation

Aaron_Wilson · ‎Oct 1 2021

I've seen it take longer than 10 minutes. Best to give it 20min wait.

Ryan_Miles · ‎Sep 29 2021

i would work from the guidance in the doc and that only allows a single model jump 80>84 or 84>85.

Ryan_Miles · ‎Sep 29 2021

agree the notes should clarify if OSPF is not enabled already on the network then the call requires ospfDisabled vs. disabled. i'll report this to the API folks for confirmation and fixing.

cmr · ‎Sep 15 2021

I've opened a case: 07014827 to see if something has simply got confused...

Ryan_Miles · ‎Sep 15 2021

the process to replace a stack switch member is here https://documentation.meraki.com/MS/Stacking/Switch_Stacks#Replacing_and_Cloning_Stack_Members and yes, the license warning will go away when you complete the process above as you won't be using more switches than you're licensed for.

AutomationDude · ‎Sep 13 2021

What is the reason for using templates here? Wouldn't you just be able to accomplish this if you didn't use templates..

Ryan_Miles · ‎Aug 14 2021

reviving this thread. spotted meraki ap's (via tv) at goodison park

JEIO · ‎Aug 9 2021

Thank you

Ryan_Miles · ‎Aug 7 2021

16.11 resolves this afaik. It’s in the release notes.

GiacomoS · ‎Aug 6 2021

@ACI_Admin I'd encourage you to get in touch with our Support team as the issue may be different/unrelated to yesterday's events. Many thanks! Giac

Ryan_Miles · ‎Aug 4 2021

The previous owner would need to unclaim it from their org

Ryan_Miles · ‎Aug 3 2021

video retention is based on the camera model storage (128, 256, or 512 GB) and the config under quality & rentention. as you configure the options on this page the dashboard will show you an estimate of the retention period. https://documentation.meraki.com/MV/Initial_Configuration/Video_Retention

BlakeRichardson · ‎Aug 3 2021

Firmware ok? they haven't tried to update and got stuck? Maybe try factory resetting one of them.

Ryan_Miles · ‎Aug 3 2021

Most Wi-Fi 5 AP's are now supported in 28.3 (as posted by cmr above). Exception is the 30H. MT documentation hasn't been updated to reflect this yet. But it's in the 28.3 release notes.

PhilipDAth · ‎Aug 3 2021

You'll have to configure matching back to back NAT's on the E300.

Aaron_Wilson · ‎Aug 2 2021

Then throw the new alt mgmt interface option to cause even more confusion....but I'm loving the alt mgmt IP option!

Ryan_Miles · ‎Aug 2 2021

i was going to suggest the same. almost all the switches were on ancient firmware from 2017 and that's likely the issue.

About Ryan_Miles

Ryan_Miles

Ryan Miles

Community Record

Badges