Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello,we've monitored our devices via CheckMK and the Meraki special agent and recently updated our Meraki MS390 and C9300L switches to IOS-XE 17.15.5.Since the update we are not able to monitor/get the interfaces, status, utilization, or anything be...
Hello community,we've noticed strange entrys in the DHCP Servers & ARP overview of one of our major sites, there're entrys for 0.0.0.0/x network in our client-vlan and the shown packet details in Dashboard don't make sense.Originated Server and assig...
At first: Thank you Torbjorn for your Input. For me it hadn't felt "validated" enough to open a TAC case, and based on the available informations/outputs, TAC probably wouldn't have been able to help. Everything looked fine over the CLI and on packet...
At first: Thank you Torbjorn for your Input. For me it hadn't felt "validated" enough to open a TAC case, and based on the available informations/outputs, TAC probably wouldn't have been able to help. Everything looked fine over the CLI and on packet...
Hi Torbjorn,that's the Issue, I don't get any errors, whether from the device nor the monitoring system (CheckMK).We use SNMPv3 AuthPriv, SHA(1-96) with AES-128, required since this update, but I also tried more complex cyphers.Cloud-Terminal shows t...
final Note:I can recreate the issue, the root cause are indeed DHCPINFORM packets.The Dashboard shows wrong and bogus informations for them.But for anyone who maybe experience this too, it's only a visual issue. The real data/packet which traversed t...
