About Ryan_Miles

Ryan_Miles · ‎12-07-2022

https://documentation.meraki.com/MX/Other_Topics/vMX_NAT_Mode_Use_Cases_and_FAQ

Ryan_Miles · ‎12-07-2022

Ok, so your switchport is native VLAN 119. Is there a DHCP server on for that VLAN/subnet? Does a regular wired client receive DHCP if connected to that port or a port configured the same?

Ryan_Miles · ‎12-07-2022

What is the switchport config? And make sure in dashboard you're not tagging whatever the native VLAN is. Example, if the switchport native VLAN is say 100. Don't also go into dashboard and set the AP mgmt VLAN as 100. I see that issue a lot. Repeater APs don't get IPs. So, if your AP is acting as a repeater it would be expected to not show an IP. So, it sounds like a switchport config issue.

Ryan_Miles · ‎12-06-2022

That's not how it works. The assumption is when you buy new Meraki hardware it's available and not claimed. You're talking about used gear here so there are no guarantees of anything.

Ryan_Miles · ‎12-06-2022

You can claim the serial numbers using the inventory page. If they're already claimed elsewhere because these sound to be used then you're not going to be able to claim them. Also, if you plan to resell these you shouldn't be claiming them into a dashboard as the next person won't be able to claim them.

Ryan_Miles · ‎12-06-2022

If you're planning to sell them why are you doing anything in dashboard?

Ryan_Miles · ‎12-06-2022

You can move serials numbers between orgs no problem. Just remove it from the network(s) (if assigned to networks) and then unclaim via the inventory page. If you need to move/split licensing from the source org to a new destination org enable the co-term license move beta under Organization > Configure > Early Access on both orgs and make sure you're an admin in both orgs. Details HERE.

Ryan_Miles · ‎12-06-2022

https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Using_Packet_Prioritization_on_a_Traffic_Shaping_Rule

Ryan_Miles · ‎12-06-2022

I suggest you open a Support case. I see your email listed in 5 different orgs and at a glance they appear to all be fine. Status says ok and not locked or unverified. Support should be able to get it sorted out.

Ryan_Miles · ‎12-06-2022

👆 Agree with Tony. Please open a case or hit the "give your feedback" button on the lower right of any dashboard page.

Ryan_Miles · ‎12-04-2022

We have Visio stencils HERE. Not sure how current or complete they are. I've switched over to using google slides for all my diagrams nowadays. Not as technical as Visio or Lucidchart for sure. But, it has a simpler and more modern look for how I prefer diagrams to look. Not aware of any templates though. I tend to borrow product icons from here to make my diagrams.

Ryan_Miles · ‎12-04-2022

The automatically created topology is network specific and requires Meraki switches be in the network. You'll need to create your diagram of hubs & spokes manually.

Ryan_Miles · ‎12-02-2022

You're running 4.20 which is now deprecated. You may want to test the current beta 5.0 which has a number of fixes. Support is going to advise you either run the latest stable, RC, or beta. In general, software engineering will usually never focus on troubleshooting deprecated firmware and rather will ask to start from a current firmware build/train.

Ryan_Miles · ‎12-02-2022

Newly created networks will need up to 4 hours of the device being online before it will allow a firmware upgrade to be scheduled. If you need it done sooner Support can force it through if you open a case.

Ryan_Miles · ‎12-01-2022

I would recommend you open a Support case for this issue.

Ryan_Miles · ‎11-29-2022

I would recommend you open a Support case for this issue.

Ryan_Miles · ‎11-29-2022

This is MT14 specific. It's explained here https://documentation.meraki.com/MT/MT_General_Articles/MT14_Metrics_Explained

Ryan_Miles · ‎11-29-2022

Are these wireless only networks or combined networks? The endpoint you mentioned should list wireless only networks. It works in my org.

Ryan_Miles · ‎11-28-2022

It's mentioned in the thread. You need to open a Support case for the backend config option to be set.

Ryan_Miles · ‎11-28-2022

It's this issue https://community.meraki.com/t5/Security-SD-WAN/AnyConnect-w-SAML-amp-Azure-AD-Authentication-not-prompted-for/m-p/155972/highlight/true#M39190

Ryan_Miles · ‎11-26-2022

Ok found it. It's already mentioned HERE. There’s a bug on the MX84 in that any LAN port shows as 0 in LLDP. No other models should be affected.

Ryan_Miles · ‎11-26-2022

Not sure. Added to my to do list for next week to see if it is documented. And if not, I will create it. But it's probably the case that all MX models are 0,1 for WAN ports and 0-x for the LAN ports.

Ryan_Miles · ‎11-26-2022

For example this is how my MX95 is cabled and how the LLDP info looks from downstream switches

Ryan_Miles · ‎11-26-2022

AFAIK the WAN port numbering internally is 0 & 1. And the LAN port numbering also starts at 0. So, for a MX85 the LAN ports from an ifconfig or LLDP perspective would appear as LAN 0-9. Using that numbering your info of physical ports 11 & 12 would equate to the internal numbering scheme mapping to 6 & 7.

Ryan_Miles · ‎11-24-2022

Are you using Face ID in the mobile app (in settings > account) ? I’ve noticed if I disable it the stream still works when opening the app. With Face ID enabled I get the loading logo and need to exit from the feed and go back to get it working.

Ryan_Miles

Ryan Miles

Community Record

Badges