About Dunky

Dunky

I must say that was a very very pleasant surprise when I logged on this morning, its really good to know that this forum is taken notice of. I have reached out to Han as David recommended on the other issues around being able to specify which sensors (defaults to ALL), and the visibility of the 'Download' button. Thanks again!

Dunky

I can see the ability to grant access to sensors in networks that do not have MV's is now available 🙂

Dunky

Well, my excitement at finally having this feature didn't last long 😞 When creating the role, it appears the only networks you can select are those that have MV's. I am unable to see networks that have sensors but no MV's I assume this is a bug and will be addressed, as the feature cannot be used if you don't have MV's in the same network as sensors. We have sites with sensors that we need to give users access to, but there are no cameras in those networks. On the site where we have both MT and MV's, I created a role to access sensors only, but was unable to select which sensors as the screen below did not list the sensors to select (i.e. I cannot give the role access to specific sensors only - EG MT11's, not MT10's) When hovvering the mouse over the "All Sensors" box, it cannot be changed, so how do you select specific sensors/models? Furthermore, the "Read-only sensor access" does not give the users the "Download" button which is necessary to save IT having to do this for every sensor every month and email to the users.

Dunky

Thanks David, this is fantastic news for us!

Dunky

Wow, it looks like Meraki have implemented access to sensors for non-IT staff - MT Sensor-Only Admin - The Meraki Community I will be testing this as soon as its made available, will be an absolute god-send if it all works 🙂 @DavidWorley Do you know when this will be available in the dashboard, I just checked and its not available in mine yet.

Dunky · ‎08-17-2023

Thanks Larry. What we really need is a 'read-only' mode but with the ability to download the readings - at present that button does not appear when logged in as a user with read-only rights. The way to look at it is that these MT11 sensors are there to to alert when temperature thresholds in freezers in a Laboratory containing bio samples go out of the thresholds defined and the users in the Lab need to be able to see the current and historic reading and be able to download the readings for auditing purposes as part of their accreditation. Once installed and configured, its not really of interest to Meraki admins, its the users that need the access to view and download.

Dunky · ‎08-16-2023

Have you tried rolling back the upgrade to confirm it was definitely the upgrade that broke it?

Dunky · ‎08-16-2023

@Larry_Woods Is there any timeframe for giving users access to MT's (with the download ability) without having to put the MV/MR they are connected to into a different network? We have requirements for MT's but if we cannot give users access to view and download the readings and there is no timescale to provide user access to these, then I will have no option but to go elsewhere.

Dunky · ‎08-11-2023

After raising a support case I got a really helpful response and explanation as to why they publish the dst as ANY as per below: Thanks for getting in touch with us here at Cisco Meraki! I'll be happy to provide support on this case. So for the MV Cloud Archive specifically, it's port 443 you'll want open outbound on any upstream device. The destination catch-all of any I believe, is shown because it will change based on where you choose your organisation's location to be and thus the corresponding data centre, details found here: https://documentation.meraki.com/General_Administration/Organizations_and_Networks/Creating_a_Dashboard_Account_and_Organization#Organization_Region_and_Data_Storage Depending if you fall into APAC, EU, or NA data centres the destination IP for archival you require may differ but here is a list of potentials depending on your config: APAC - https://cloud-archive-upload.apa.vision.meraki.com 13.112.106.253 EU - https://cloud-archive-upload.euc.vision.meraki.com 3.65.231.194 NA - https://cloud-archive-upload.use.vision.meraki.com 3.225.48.233 Please note, our recommended, supported configuration is for the destination to be set to any so please bear this set configuration in mind for any future troubleshoot. Wishing you a good weekend, let me know if I can assist further! I have used the relevant FQDN as the dst as I did an NSLOOKUP and got a different IP so I guess there is more than one dst IP for the FQDN.

Dunky · ‎08-11-2023

Did you ever resolve this, I have the exact same issue. Non-meraki VPN to Azure is down but absolutly nothing in the event logs

Dunky · ‎08-09-2023

Same here no option to upgrade, currently on 18.107.2

Dunky · ‎08-09-2023

Will MA-PWR-ETH not do the trick, is says its for MV2 and MT.

Dunky · ‎08-08-2023

Should have read more before I posted - just seen another thread saying the MT and MR have to be in same network. That isnt going to work as the user needs to be full admin in order to download the logs for auditing accreditation purposes. I do hope Meraki sort this soon as I can see them moving away from Meraki if we cannot give them access/

Dunky · ‎08-08-2023

Hopefully this is a really quick question.... We have a number of MT11 sensors installed but the users need to be able to access these in the dashboard and download the readings for audit purposes. To do this I need to split them off into a separate network and make the users Full Admins as otherwise they dont see the Download option. The question is - will the MT's still BLE connect ok to the MR's that are in the existing network (i.e. they will be in 2 diff networks so far as the dashboard is concerned. imho, the whole issue of user access to Sensors to VIEW and DOWNLOAD needs to be rethought as I cant be the only person that is getting such requests from users?

Dunky · ‎08-04-2023

Thats great, many thanks. It sends every flow to the syslog server rather than just the ones Ive ticked the syslog box for though, but not an issue (other than generating unnecessary traffic), I've just filtered on the syslog server to show those where message contains "deny"

Dunky · ‎08-03-2023

visual syslog

Dunky · ‎08-03-2023

I get the flows but I dont see any hits arriving on the syslog server for the rules I have ticked. Unless there are just so many i cant see them, Is there anything specific you are aware of in the text that I can filter by?

Dunky · ‎08-03-2023

That then sends absolutely everything, not just the rules where I tick the syslog box - I only want to see what is hitting the rules I have ticked the syslog box on.

Dunky · ‎08-03-2023

Nope, its not filtering anything, displays all the other events, just nothing from the L3 rules where I ticked the syslog box

Dunky · ‎08-03-2023

Is someone able to tell me exactly how to identify traffic that is hitting specific L3 rules? Ive defined the local syslog server and added "Security Events" and "Appliance Event Log" to it in Network-wide>General-Reporting I have ticked the syslog box against the rules I want to see what traffic is matching, yet nothing is getting logged to my syslog server even though the hit counts on those rules is going up. I am getting other msgs on the syslog server from the MX ok though. TIA

Dunky · ‎08-03-2023

OK, thanks Ryan. Seems it was released a little prematurely 🙂

Dunky · ‎08-03-2023

Done

Dunky · ‎08-03-2023

I started to implement these today but have given up as they appear too 'buggy' to me. I set the port profile as below, note the STP Guard setting However when comparing once its been applied to a port, the STP Guard shows as "n/a" as shown below: Also, if you edit a port and disable the port profile, it still shows up when viewing switch ports: Also, the profile will not let you have a blank Native VLAN which the port itself does Furthermore, even if you disable the port profile on the ports, when you then edit the port profile, it says it will be applied to 'n' ports. So I will park it until these anomalies are fixed

Dunky · ‎07-23-2023

Yeah thats what I am gonna have to do, just thought it stramge why Meraki dont publish dst IP/subnets or FQDNs for one particular rule

Dunky · ‎07-21-2023

Thanks, I guess that will be uk.pool.ntp.org then for deployments in the UK.

Dunky

Community Record

Badges