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 PacketHauler
Community Record
19
Posts
33
Kudos
0
Solutions
Badges
06-06-2018
08:04 AM
I was on the phone recently with Meraki support with an unrelated issue, and I just deployed my first set of MS120s. The tech on the phone mentioned to run 10.25 (beta) on the MS120s. They ship with an earlier 10 code deployed on them. So far they have been running okay.
... View more
05-18-2018
01:12 PM
1 Kudo
I'll be there! 2XL
... View more
03-14-2018
05:59 PM
5 Kudos
I just received my trial cameras via FedEx today. I can't believe how small they are! This makes me extremely excited to try them out. We will be deploying a couple of hundred across our company. Being an infusion pharmacy company, this will help keep our pharmacies and drug storage in compliance. (Pen in picture is for scale)
... View more
02-28-2018
06:59 AM
We're looking to possibly roll out Meraki cameras to all of our pharmacies in the near future. We have ordered a couple of these for trial to make sure they will provide the views we need. We already have a few MV21s deployed. These new cameras appear to have a much lower profile and better capture resolution. We're excited to see how they perform!
... View more
02-20-2018
11:54 AM
18 Kudos
I had a remote site that was complaining of slowness in certain parts of the branch office during the latter part of the day. I started to dig into client statistics on the dashboard, and noticed that there was a group of about 10 systems that were transferring gigabytes of data within a very short period of time. It then would flood some of the uplinks of the switches they were attached to. The kicker that this traffic started once the site went to idle hours (after 6pm local time) and all were sending/receiving identical amounts of data. I ended up doing a packet capture on the switch ports of the hosts that were producing this traffic, and found that they were sending and receiving large amounts of IPv6 multicast traffic. After seeing they were HP desktops that were only generating this traffic, I went digging through the search engines for a possible answer. It turns out there was a known bug in certain driver versions of the onboard NIC of these machines. When the machines go idle, they end up being chatty with each other with IPv6 multicast traffic. The fix is to disable IPv6 or install a driver update. I sent out one of our help desk techs to assist on site with updating drivers on those specific desktop machines. Once that was completed, problem solved, have not seen that occurrence again. Moral of the story: Remote packet captures are your friend with Meraki.
... View more
01-31-2018
10:24 AM
Of course! I'm hoping it just becomes the next stable RC version and isn't only in the beta tree.
... View more
01-31-2018
10:07 AM
Bug has not been fixed yet, support advised me they would send a notification when it has been squashed and what version to upgrade to. Only work around is to unplug the cell modem, or roll back to a previously known working version.
... View more
01-30-2018
12:11 PM
1 Kudo
FYI, I just ran into this issue on a few of our sites that were upgraded to 13.28, with the MX84 platform. There is a bug in this version that can cause very high CPU utilization, impacting latency sensitive traffic such as VoIP. The symptoms are very bad call quality, and increased RTT for IP traffic. From what I can tell, it seems to impact sites that have Cellular modems that may not have fully initialized, and are unable to connect to their respective telcos. Rebooting the device solves the issue immediately, but then eventually it does come back. Meraki's suggested fix is to either unplug the modem entirely, or revert back to a previous software version. I've reverted one of our sites back to 12.26. I should know by tomorrow how it will look. However, there is one site where I had the user unplug, and plug the cell modem back into the MX84, and the issue hasn't appeared since, and it is still running 13.28.
... View more
10-27-2017
05:45 AM
Use the 'Make a Wish' button on the status page. That's what I've been doing. If I needed to know the CPU utilization or uptime stats on a device, I just call support and ask them, they've been happy to tell me without needing to put a ticket in.
... View more
10-27-2017
05:41 AM
@redsector wrote: Meraki said to me that after the updates the problem would be solved, but it wasn't. I had to take a video (with sound) of the problem, uploading in the "Cases". After this Meraki made an RMA. I've never had to go that far to prove that something was wrong with the fans. I had 2 switches that stayed in a failed state after the firmware update even, the fans never ended up spinning ever again after they failed. I think this is why they want everyone to install the update ASAP. Conversely, I had 2 switches that ended up fixing themselves after the update. They were throwing critical temperature alerts before hand, but after the firmware update the alerts cleared. I've been watching the event logs for those 2 sites ever since and haven't seen the alerts re-appear.
... View more
10-23-2017
06:53 AM
3 Kudos
What version of firmware are you running? There was a recent beta release that I thought addressed random reboots of that particular model. Release notes for 25.8: Bug fixes Provisioning service in some cases would not be able to bring up BLE radio (MR33/MR30H/MR74) Some clients and APs were reported with high RSSIs (255dB) which were inaccurate (MR42/MR52/MR53/MR84) Port 0 was being assigned to an Aggregation Port which violated 802.1ax-2014 section 6.3.4 (MR52/MR53/MR84) Tuned MCS EVM to improve rate vs range (MR42) Provisioning service would cause scanning radio to get stuck (MR30H/MR33/MR42/MR52/MR53/MR84/MR74) Stale information fix ups for Client Balancing Ethernet phy configuration issue caused CRCs on upstream switch ports (MR33/MR30H/MR74) Stability issue caused MR to reboot under load' Low level stability issue caused AP to reboot
... View more
10-17-2017
08:05 AM
If you cannot feel any air moving at all, and your on MS 9.30, you need to get them RMAed pretty quick. The fan will never spin up again at that point, and the hardware needs to be replaced. I've never had an issue forcing them to do an RMA when that happens. I've had about 5 fail on me that way before.
... View more
10-12-2017
02:10 PM
1 Kudo
I'm a little late to the party! I'm Nils, and I'm the lead network and voice engineer for BioScrip. We have about 70 pharmacies and infusion suites across the country and 95% of them are using the full Meraki stack now. In about a month we'll be at 100%!
... View more
10-12-2017
11:49 AM
Yikes. I've deployed about 55 of these in the last 6 months. So far I think I've replaced maybe 20 of them. All of them are running 9.30 code now, and just waiting for more failures now. I've had a few tickets come in from sites asking if the higher speed is normal. All I can tell them is that's the new normal.
... View more
10-12-2017
11:46 AM
If your switches are throwing critical temperature alerts, Meraki sends out a custom email alert, as well as put a banner at the top of the dashboard screens stating which networks have a device with potential fan failures and that you need to RMA them right away. That's how I found out I had 3 more failures this week. I'm not sure why there isn't an email alert from the devices themselves stating there is a temperature alarm. Something they need to add in the future for sure.
... View more
10-12-2017
11:40 AM
@BrianH wrote: We are having similar issues. Some of our 225-48LP's sound like a jet engine with or without POE load on them. Some sound like a normal switch. All are on the 9.30 code. Support has no idea at this point. I have a case open and right now they are at a loss. I really think there is a sub issue with these switches besides the thermal problem. I can't imagine their engineering team allowing the fans to be rev'ed on high constantly as a solution to this. Unfortunately I can't speak to the inconsistent fan speeds on the 48LP model. All my deployments have been the 225-48FP. Those for sure have thermal issues. I had 3 more throw temperature alarms this week, and have them slated to be replaced. When I've seen these fail, the fan shuts down completely. Even after putting on 9.30 code, the fan refuses to spin causing the hardware failure. To me it looks like they put in bad fan controllers to adjust the speed, and the way to 'fix' that issue without replacing the whole switch was to increase the minimum speed of the fan regardless of the load on the switch.
... View more
10-10-2017
05:42 AM
If you go under 'Organization->Firmware Updates' and then click on the software release for your particular device, you should see the appropriate release notes.
... View more
10-10-2017
05:40 AM
2 Kudos
There is a known issue with a large batch of the MS225-48LP/FP switches, that end up having a failure of the fan. I've deployed 60 of these models in the last 6 months, and I've had a good number of them fail. Meraki has been good about replacing them. In the 9.30 verison of firmware that was released, they increased the minimum fan speed on the switch, so you will notice it run at a higher RPM all the time, however it shouldn't change speeds that much, so you might have a fan that is indeed going bad. I would go for a replacement as soon as you can before the fan completely fails. Take it from someone who has done about 15 RMAs so far on this particular issue.
... View more
10-10-2017
05:36 AM
2 Kudos
Yes. We've deployed about 60 of these in the last 6 months. This is a known issue with this particular model. They pushed a firmware update (version 9.30) to increase the minimum fan speed. Let the software update complete, and see if that fixes your issue? If not, have been good about issuing replacements.
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 18 | 19577 | |
| 5 | 22755 | |
| 3 | 14966 | |
| 2 | 28929 | |
| 2 | 27280 |
