Community Record
259
Posts
249
Kudos
3
Solutions
Badges
yesterday
I know this sucks, but this issue isn't just a Meraki issue but any company that locks equipment once it's claimed.
... View more
Monday
Yeah, I did that for most of my VLANs as well. For my infrastructure VLAN that is still on the MX,but this is mostly network hardware.
... View more
Sunday
8 Kudos
I ran into this issue a lot with Ubuntu when I was turning up VMs on my ESXI hosts. Solution 1: Configure DHCP to use MAC instead of Client ID (Netplan) If you’re using Netplan (common in Ubuntu 18.04 and later), you can modify the Netplan configuration file. Edit Netplan Configuration File: bash Copy code sudo nano /etc/netplan/01-netcfg.yaml Look for the network interface section (it will look something like this): yaml Copy code network: version: 2 renderer: networkd ethernets: enp3s0: dhcp4: true Force Netplan to use the MAC address as the Client ID. Add the following option under the interface: yaml Copy code network: version: 2 renderer: networkd ethernets: enp3s0: dhcp4: true dhcp-identifier: mac Apply the changes: bash Copy code sudo netplan apply This tells Netplan to use the MAC address as the DHCP identifier instead of the Client ID. Solution 2: Configure DHCP Client to Use MAC (dhclient.conf) If you're using dhclient directly (common in older versions of Ubuntu), you can modify its behavior. Edit the DHCP client configuration file: bash Copy code sudo nano /etc/dhcp/dhclient.conf Force it to use the MAC address. Add this line at the top or bottom of the file: conf Copy code send dhcp-client-identifier = hardware; Restart network services: bash Copy code sudo systemctl restart networking Alternatively, you can stop and restart dhclient manually for a specific interface: bash Copy code sudo dhclient -r enp3s0 # Release the DHCP lease sudo dhclient enp3s0 # Request a new lease using the MAC address
... View more
a week ago
Silly question but what information could be leaked by knowing your public IP?
... View more
a week ago
1 Kudo
Thanks for your time in responding to this post. Sorry for the typos I was working on a small fire when I saw you replied and I wanted to respond quickly :). I don't want to turn this into the me show, so if any of the other forum members would want to share their thoughts please do :).
... View more
a week ago
@RaulR Much respect on the Team's thoughts and feelings on having the ability to enable or disable IPV6 on the WAN, but I can share the fact my personal issues with this choice was met with a lot of pushback from the sales team to get this data to the right people. Also the fact that we the admins like to have the ability to even see any aspect of IPv6 on our network should be due our choice. I have multiple vendors from free open source to top 3 vendors including Cisco popper that gives me this choice. I will say my initial problem I ran into when you guys first released the firmware that enabled IPv6 on the WAN has been resolved, but like my self and others have stated "We just want the option".
... View more
a week ago
I agree and this is the only solution that I don't have control over this function.
... View more
2 weeks ago
1 Kudo
Quick question did Meraki devs ever give a reason why we don't have the ability to disable IPv6 on the WAN interface? I know it's a minor gripe, but in the early release days this rollout caused an issue with our branches.
... View more
2 weeks ago
3 Kudos
General important notes MS17 introduces a change to the default login credentials for the device local status page, using "admin" as the username, and the device serial number (upper case with dashes) as the password Ms12x important notes If DAI is enabled prior to upgrading the network to MS 16, ensure that trusted ports and/or DAI-allow lists are configured prior to upgrading to avoid potential network outages. Ms420 important notes Devices configured for this version will run MS 15.22 New feature highlights DOM (Digital Optical Monitoring) Intelligent Capture RSPAN and VLAN Based SPAN SmartPorts New ms130x feature highlights Adaptive Policy on MS130X/R models General fixed issues Fixed a bug that caused some 802.3af devices to display as 802.3at in Switch Port Details Fixed a bug that caused switches to forward some RADIUS requests that included an invalid source MAC address Fixed a cross-stack port mirroring bug that incorrectly showed CDP/LLDP traffic from the source port as being connected to other members of the stack Fixed an issue that caused boot loops when attempting to upgrade to MS17 while using an externally calibrated third party SFP Fixed an issue that caused clients to get stuck in an auth_pending status until the switch port the client was connected to was bounced Fixed an issue that caused switch stacks to learn MAC addresses from ports in the STP blocking state, triggering MAC flap messages in the event log Resolved an issue that prevented an active stack member from managing STP state on other stack members after the active member rebooted Resolved an issue that sometimes prevented stack ports from being correctly reconfigured after stack link flaps Ms130 fixed issues Resolved a bug that caused some MS130s to stop reporting to Dashboard while upstream switches reported UDLD issues Ms210 fixed issues Fixed a bug that caused MS210 stack port LEDs to incorrectly indicate an orange light rather than the expected green Ms220 fixed issues Fixed an issue that caused the packet capture files generated by the Local Status Page to be empty Ms355 fixed issues Fixed a bug that occasionally caused some MS355 switches to reboot Ms425 fixed issues Fixed a bug that caused high device utilization on MS425 stacks when multicast routing was enabled Resolved an issue that caused pNIC errors when forwarding some LLC packets General known issues If voice and data are configured to use the same VLAN DHCP discovery messages may not be correctly forwarded from client devices after being authenticated via 802.1x on the voice VLAN LACP links may take an extended time to come back up when the Active Member of a stack reboots RADIUS communications may not recover after an initial failure when Critical Auth is enabled Some clients may be incorrectly added to a configured Guest VLAN when authenticated via RADIUS immediately after a switch reboot Some switches may encounter an error, "incompatible configuration for attributes: allowed_vlans" when attempting to aggregate ports regardless of allowed VLANs configured in Dashboard Switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 or other Catalyst switches unless the bundles are configured on the MS390/Catalyst switches first. All non-catalyst ports are configured in passive LACP mode so that loops do not occur between Meraki switches (always present) Ms120 known issues Some client devices may fail to authenticate via MAB in an access policy with hybrid authentication enabled, resulting in 802.1X authentication failures Switches may fail to provide PoE power to legacy access points (always present) Ms12x known issues] ms120/125s may fail to forward link-local multicast [224.0.0.x traffic when 'Flood unknown multicast traffic' is disabled Ms130 known issues MS130-X switches may experience slow upstream throughput when connected directly to an MX device via an mGig port Ms250 known issues Switchport with Multi-Domain Hybrid auth access policy randomly goes into a port not forwarding state Ms350 known issues Cable tests may fail to execute on mGig ports Enabling Auto-stacking on MS350s may remove existing L3 SVIs Ms35x known issues In rare instances, stack ports fail to initialize after an upgrade (always present) Incorrect SFP port mappings may disrupt SFP functionality Switches may experience an unexpected reboot (present since MS 15) Ms425 known issues In rare circumstances MS425 switches may encounter a software crash that results in a reboot In some circumstances ARP requests may not be correctly forwarded after connectivity is restored following an inter-DC VPLS DCI outage MS425s in stack configurations may periodically trigger New DHCP Server alerts that include mismatched VLANs/subnets Ms4xx known issues When an SFP module is inserted/removed, BPDUs can be delayed leading to STP transitions in the network (predates MS 12)
... View more
2 weeks ago
2 Kudos
Let's start off the with obvious this is a great add and I am thankful to see the additional information. That being said I feel like with the additional information we are able to see this could be combined with the current summary page and this would save admins the time of clicking back and forth. New Tile Device Summary Combine the following categories into one Block CPU Memory Power - Make smaller Power Mode - Make smaller AP Reboot - Merge with Historical Connectivity Historical Connectivity - Tweak this bar to combine the alerts with AP Reboots, but use the same colors Radius and VLAN Status - Make smaller Uplink Traffic Radio Summary Utilization on current channel Add Client count on each radio Current Client Keep the same Historical Device Data Keep the same These are just my thoughts. @RaphaelL - Thanks for posting about this release I missed it.
... View more
2 weeks ago
What switch do you have running these APs? Also, how are they being powered?
... View more
3 weeks ago
1 Kudo
I like the call me now feature, but here are my thoughts: Love: The system does call you at the assigned number. When a rep is connected they have all the info from the ticket. Like: The overall process isn't bad. Dislike: The system calls you just to place you on hold until an agent is free. Change Request: Change to wording to "Call Back" Once the ticket is placed inform the admin of an ETA on when to expect a call back, then have the system call when the admin is next in the queue.
... View more
3 weeks ago
removing any special characters in the name of the vMX <-- I do have dashes in my naming convention so this might be the smoking gun. <--- When I ran into this issue the device wouldn't even complete the install process. Meraki support has passed this off as an Azure problem <-- To a point, they are kind of right. If the DNS servers you could be using don't have access to the internet to complete the DNS requests then it should and would fail. That being said if they do have a path to the internet then I don't see why it would fail. The good news for anyone else running into this issue is the secondary server method of 8.8.8.8 is only required while spinning up the device. Once it has been installed you can change your DNS servers in the dashboard to the DNS servers of choice then revert your Azure secondary DNS server to what you had it set to previously.
... View more
CS is 17.1.4 MS is 17.1.3.
... View more
Oct 28 2024
4:32 PM
2 Kudos
It's a small update, but big enough to be clear that an issue has been resolved. I like it.
... View more
Oct 21 2024
6:31 PM
I had this issue with Cox as well. I didn't have a Meraki switch in place, but I did with Cisco Cat switch and UI switch. I was able to Simi get this working with a ton of modem reboots and port disable and enables.
... View more
Oct 14 2024
12:55 PM
Complete!! Good luck everyone..
... View more
Oct 12 2024
5:01 AM
That's most companies :).
... View more
Oct 11 2024
3:51 AM
Just a question, but is not rolling back to 18.1 not an option?
... View more
Oct 9 2024
4:59 PM
That mostly falls on the 3rd party firmware maker vs the original vendor.
... View more
Oct 5 2024
3:31 PM
1 Kudo
Signed up as well.
... View more
Switch: MS130-8X If nothing changes I wouldn't be upset, but given a choice, I would like to see one of the following changes. 1. Keep the "current" readings as they are but make the graph a single graph with overlapping variables. Then allow the admin the option to toggle on and off the categories they would like to see on the graph. Doing this would save from "me" from a lot of scrolling if I want to see 3 or more categories. 2. The popup box that is shown when you hover over a plot point would be nice to have if you hover or click the "current" status category, at least the min and and max readings.
... View more
Aug 30 2024
4:43 PM
In this case they are correct. The device is tied to the key the Meraki portal vs the account that the VM I assigned to.
... View more
My Accepted Solutions
Subject | Views | Posted |
---|---|---|
174 | Sunday | |
910 | Apr 12 2024 6:57 PM | |
1127 | Aug 22 2022 6:17 PM |
My Top Kudoed Posts
Subject | Kudos | Views |
---|---|---|
8 | 174 | |
6 | 2110 | |
6 | 12058 | |
5 | 18724 | |
4 | 4715 |