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 jefanell
jefanell
Here to help
Member since Nov 17, 2020
a week ago
Community Record
16
Posts
13
Kudos
0
Solutions
Badges
a week ago
I'm seeing erroneous VLAN mismatch alerts on both 9k switch ports in my LACP link to another (monitored) 9k. Neither switch is showing any errors etc, and the LACP port channel is happy. relevant config on switch 1: interface Port-channel12 switchport mode trunk device-tracking attach-policy MERAKI_POLICY no logging event link-status snmp trap mac-notification change added snmp trap mac-notification change removed ! interface TenGigabitEthernet1/0/43 description 9300-macavia-lacp switchport mode trunk logging event trunk-status logging event spanning-tree logging event status snmp trap mac-notification change added snmp trap mac-notification change removed channel-protocol lacp channel-group 12 mode active spanning-tree portfast ip nbar protocol-discovery ! interface TenGigabitEthernet1/0/44 description 9300-macavia-lacp switchport mode trunk logging event trunk-status logging event spanning-tree logging event status snmp trap mac-notification change added snmp trap mac-notification change removed auto qos trust channel-protocol lacp channel-group 12 mode active spanning-tree portfast service-policy input AutoQos-4.0-Trust-Cos-Input-Policy service-policy output AutoQos-4.0-Output-Policy ip nbar protocol-discovery relevant config on switch 2: interface Port-channel1 no logging event link-status ip dhcp snooping trust ! interface TenGigabitEthernet1/1/1 description 9300-core-uplink logging event trunk-status logging event spanning-tree logging event status snmp trap mac-notification change added snmp trap mac-notification change removed channel-protocol lacp channel-group 1 mode active ip dhcp snooping trust ! interface TenGigabitEthernet1/1/2 description 9300-core-uplink logging event trunk-status logging event spanning-tree logging event status snmp trap mac-notification change added snmp trap mac-notification change removed channel-protocol lacp channel-group 1 mode active ip dhcp snooping trust
... View more
09-20-2022
04:07 PM
appears to connect just fine, shows an identical response to two other 9k's I have onboarded into Meraki. 9300-sfld-1#telnet us.tlsgw.meraki.com 443 Trying us.tlsgw.meraki.com (35.165.42.192, 443)... Open
... View more
09-20-2022
08:36 AM
I have, and that command works (I get an open connection). I'll send a CLI log shortly.
... View more
09-19-2022
08:58 AM
has anyone been able to onboard a device today / this past weekend? getting this error in pre-check. I tried from multiple Macs. switch and the Macs in question can successfully reach the us.tlsgw.meraki.com on tcp/443. [2022-09-19 11:54:27.322] [info] Pre-check error occurred. Sending error to the UI [dv-9e1d5391-775e-41e1-8e27-1fd9950c80d2] telnet us.tlsgw.meraki.com 443 Trying us.tlsgw.meraki.com (35.165.42.192, 443)... Open Quit [2022-09-19 11:54:27.327] [info] CLIENT_EVENT :: Client received device pre-check error [dv-9e1d5391-775e-41e1-8e27-1fd9950c80d2] { id: 'dv-9e1d5391-775e-41e1-8e27-1fd9950c80d2', error: 'Error: telnet us.tlsgw.meraki.com 443\n' + 'Trying us.tlsgw.meraki.com (35.165.42.192, 443)... Open\n' + 'Quit\n'
... View more
06-26-2022
09:05 AM
2nd update: one of my 9k's is working / shows up in dashboard, the other doesn't. same AAA config, no errors in AAA authentication / authorization. Unfortunately no way to troubleshoot. I see a non stop set of commands getting (successfully) authorized on my switch debugs but this switch never shows up in Meraki dashboard. 1st update: I added "meraki-user" into ISE and ensure that user is getting priv-15 / full command authorization and it looks like the onboarding into Meraki cloud is now working. It looks like root issue is the added Meraki Cloud AAA config enables local authentication for the meraki-user connection to the switch but doesn't enable local authorization for the same; so the meraki-user user locally authenticates but then the switch attempts to use the (existing, in my case) AAA TACACS authorization config for meraki-user, which fails unless you have this user in your AAA server etc (in my case, Cisco ISE). --- hmm ok I'm probably having the same problem. Both my 9300's (2 standalone 9k's running 17.6.3) show successfully onboarded in the app but never show up in the cloud. I did have a TACACS config running, and I see the new Meraki AAA config, but how to resolve now?
... View more
