- About GIdenJoe
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
GIdenJoe
Here to help
Member since Mar 5, 2019
15 hours ago
Community Record
15
Posts
7
Kudos
0
Solutions
Badges
19 hours ago
Then you'll need to buy the second MS350-24X. This one comes with a 0.5m stacking cable, so if you would still have that one that was delivered from the existing switch you can fully stack them. Else if you've lost it you'll need to order one MA-CBL-40G-50CM. Basically you need two in total to complete the 2switch stack. The switches need to be close to one another. If 0.5 meters is not enough you can order longer stacking cables of 1 or 3 meters. 2x MA-CBL-40G-1M or MA-CBL-40G-3M The stack config in dashboard is really straightforward but you will need to bring the new switch online without stacking it first and make sure the existing and the new switch have the same firmware. Then you'll need to power off both devices and connect the stacking cables in the back and startup the switches again. Then you'll have a potential stack which you'll just need to provision and voila. You can now start double uplinking every access switch for redundancy and extra bandwith through LACP port channels.
... View more
Monday
Yep, these switches are better stacked so from a logical standpoint you still have one switch but you do get the added availability and extra bandwidth. However this only works if you can co-locate both switches in the same area (closet). If you need redundancy and spatial separation (in case of fire) then with these switches you'll need to do the classic failover with blocked STP links. The MS4xx range of switches have flexible stacking which also makes stacking possible over larger distances.
... View more
Monday
I found out it only happens when the output is on the screen. When capturing to pcap file it usually remains on for the duration given. I also have another issue with the packet capture tool on switches. Since the packet capture is done from the dashboard, I suspect the capture is made after the frame has been processed by the ingress asic. Since even with tagged or untagged VLAN assignments all captures from the dashboard have an 802.1Q tag assigned which does not always correspond to the incoming frame in a port. So sometimes it's difficult to troubleshoot if a voice VLAN is getting the correct input from a phone or a server is tagging it's traffic as it should.
... View more
Thursday
@TylerjuzWe had a severe dashboard bug where a change in one unrelated configuration caused a wipe of all L3/L4 firewall rules. And those changes were not visible on the Organization->Changelog. So we decided to do a daily backup of all our customers who give us API access to their org up to the last three days. So we can always restore the firewall rules from the last 3 days. I believe my colleague used existing python code readily available on the internet and tweaked it a bit for our purposes so I can't answer any details on this. All I can say it's possible but make sure to get your customers approval and save those file in a secure location. The scripts you can find usually read the values and write the restore commands so the output is actually a .py file with the commands to restore that config, but for some things like firewall rules, you could output it textbased so it's more human readable and editable.
... View more
Thursday
A colleague of mine already uses an API to backup firewall rules, so I guess it's possible to backup configurations of other devices. Another colleague of mine painfully found out that switch cloning only takes the port configs but does not do anything with L3 interfaces and routes so beware.
... View more
Thursday
1 Kudo
Hey @NolanHerring, the option to disable meshing is not available by default. So in that environment it's still running. Btw I found your fun 2 year old article about this which I agree with fully: https://nolanwifi.com/2017/02/06/merakis-mesh-mess/
... View more
Thursday
I have turned off the 2.4 GHz on a MR53 using RF profile where only 5 GHz band is allowed. When I look at RF spectrum from neighboring AP's I can still see the MAC address of the disabled AP broadcasting quite strong but at 802.11g mode on channel 1 but at a high data rate (I don't trust that output because it sees 802.11ac on channel 1???) So I started a packet capture on the neighboring AP and found it that it still sends some LLC frames once every 30 seconds.
... View more
Wednesday
1 Kudo
- Interference is caused by other AP's or clients associated to other AP's on the same channel. They cause performance issues but that would need to be extremely severe before clients would start dropping their association. - Higher noise caused by non-wifi devices can cause the SNR to drop and clients to go below a certain PHY rate and if you've configured a minimum PHY rate they could be dropped because of that. - But it could be a driver issue on some clients since a certain update. Basically you'll need to find out if where it happens (if it's everywhere then test it anywhere) and if it's a certain device type, then test with multiple devices at that location to gather your info (PHY rates, retry rates, dropping) - If it's a driver issue then update/downgrade, if it's a noise/interference problem then you'll need to do a troubleshooting site survey at that location (spectrum analysis for noise, and passive survey for signals and interference)
... View more
a week ago
Nope MarcP, I was talking about the thread starter. But indeed your log messages seem to state a reason (auth expired), nothing embarrassing about that. Mistakes do happen the first time around ;) I meant the unknown reason disassocs from the threadstarter.
... View more
a week ago
Are you sure the disasociation frames are coming from the AP's and not some other network device sending disassociate frames on their behalf like air marshal going haywire? Maybe protected management frames can help in that case. 802.11w
... View more
a week ago
Hey, I've seen that message popping up with wired authentication policy but not with wireless SSID's. So if I read your answers correctly Meraki manages two separate users dB's per organization being one for admins (dashboard mgmt, clientVPN) and guests (guest portal, clientVPN) and another purely for dot1x purposes wired and wireless. Without looking towards the MDM solution, I guess the admins/guest will also be used for the ownership of devices? Is there a reason those dB's are separate? Because I see a big potential for overlapping users without the option to share users between those dB's.
... View more
a week ago
Hi everyone, Quick question/remark: I'm a full admin of several organizations so I should see all users in every network in those organizations. In the following Meraki document: https://documentation.meraki.com/MR/Encryption_and_Authentication/Meraki_Cloud_Hosted_Authentication It clearly states that: User accounts configured in the Meraki-hosted authentication server are global to the networks in the organization. So, a password change to a user account in one network applies to other networks in which the user account may be used. When I add an SSID in one network with Open/WPA2-PSK and then login through splash page and do the same for another network, I see the users and can authorize them for each network. However when I use WPA2-Enterprise on the SSID on the second network, the Users list is empty. Is there a logic reason why dot1x users are probably in a separate database? Wouldn't it be better if there was one list of Users for the entire organization and also could be authorized for all the SSID's of the same name in every network? I know you usually use AD for that, but this company doesn't work with AD at this time.
... View more
3 weeks ago
I just found out for myself. Rules containing TCP are honored but rules containing Any do not. Is there another protocol you tested outside of icmp that also gives this problem?
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 1 | 55 | |
| 1 | 144 |
