- About Slobs2
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Slobs2
Here to help
Member since May 10, 2018
Monday
Community Record
10
Posts
0
Kudos
0
Solutions
Badges
09-10-2019
02:46 PM
Hi all, I’ve got an issue where the policy keeps changing to blocked on clients but the dashboard says normal. I called support and they say it’s a known issue with the dashboard and the workaround is to apply a different policy to the device. What’s “fun” about this issue is there is no way to determine what devices have the issue until I get a call about it and everyday many of the same devices have this issue. Anyone seeing this? The last update I received was that the root cause of the problem has been identified and should be resolved in about a week. This is totally crazy, not to mention unacceptable. Since this issue is at the developer level, no one will share any details of what is going on.
... View more
@PhilipDAth One last question. If I complete all the edge switch stack upgrades using the staged upgrade tool then only have my two MS425 aggregation switches left to update (which is where I really would like redundancy to occur), does using the regular firmware upgrade page under Org->Monitor behave any differently?
... View more
@PhilipDAth Haha yes that would be much more accurate!
... View more
Thanks @PhilipDAth for your response. I did see that documentation as well, I guess where it says "rebooting close to the same time" was just ambiguous to me. Thanks!
... View more
04-15-2019
02:59 PM
As the title would suggest, I'm looking for everyone's experience and info on the behavior of the staged upgrade tool with stacks. I was told a few times by support that the best practice for using the staged upgrade tool is to add all members of the stack to be upgraded to the same window of time. I was also told that after they download the update, there is a "back-off" timer that should prevent them from all rebooting at the same time. I am not finding this to be the case after two stacks I have updated, and in both cases all member rebooted at the same time. I was also told to not try to stagger the updates of switch stack members as this might cause issues with the stack. What is everyone's experience with this scenario? I am updating from 10.26 to 10.45. Any insight is much appreciated!
... View more
12-11-2018
06:18 AM
Hello all, I currently have an MS425 doing all layer 3 on my network. I purchased an MX250 and am going to move all layer three to the MX. Since the move networks option only moves interfaces to other switches, is there an easier way to move all the interfaces? Setup the MX with the static routes as the current firewall is setup now and then move them one at a time or create all the interfaces on the MX and attempt to remove all the interfaces from the MS? For added complexity I am also using the MS as DHCP too.
... View more
05-31-2018
06:43 AM
The cable plant is OM1 (62.5/125) and so are the patch cords. Oddly enough, one of the two aggregates is up and working. Using the same cables as the one that is not working.
... View more
05-30-2018
04:48 PM
Hello all. I am in the process of moving layer 3 interfaces from my old core switch to 2 stacked 425s. I am also moving all the fiber connections to the 425 stack, with aggregates to each edge switch at 10G. So I have one edge switch (an HP Procurve) connected to the stack. I have an aggregate created connected to port 12 on each stack member back to the edge switch. I have double checked that the edge switch’s port config matches the stack but I can only get one of the two members of the aggregate to come up. Previously, this edge switch was connected via 1G SFPs and multi mode to the old core via an aggregate. Any thoughts are greatly appreciate.
... View more
05-10-2018
03:48 PM
New admin to meraki so just trying to figure something out. I will be getting two 425s for my core, stacked together. What I am trying to grasp is the management network. I know each switch in the stack will need an IP for manament but how will this work at the core? If my management subnet is 10.95.0.0/24 and VLAN is 95 does that mean that setting the management VLAN to 95 and setting one of the switches as the 10.95.0.1 gateway mean it will route? Would the stack layer 3 interface need to be the .1 address and the other switches be .2 and .3? Or does the management network need to be part of the inside firewall network?
... View more
Labels:
