Hello,
according to the manual to view Cisco Catalyst 9500 switches in the Meraki Dashboard I used this manual:
https://documentation.meraki.com/Cloud_Monitoring_for_Catalyst/Onboarding/Cloud_Monitoring_for_Catalyst_Onboarding_Guide
But it fails altough all conditions met.
It´s the error message:
Device is not eligible for onboarding. Reason: Error: The switch is unable to connect to the TLS gateway eu.tlsgw.meraki.com to establish a tunnel connection. Verify routes and firewall rules are in place to allow communication on TCP 443." Review pre-onboarding requirements for more information:
https://documentation.meraki.com/Cloud_Monitoring_for_Catalyst/Onboarding/Cloud_Monitoring_for_Catalyst_Onboarding_Guide#Pre-Onboarding
I checked all to do´s and everything seems to be fine including the firewall config, the firmware version and so on.
Then I tried to make (for test purpose) an ssh connection to the described eu.tlsgw.meraki.com per CLI direct from the switch, but then I have this message:
Distri1#ssh eu.tlsgw.meraki.com
% Connection refused by remote host
also with the us site:
Distri1#ssh us.tlsgw.meraki.com
% Connection refused by remote host
Is there anybody who has some experience to do this monitoring an Cat 9xxx with Meraki Dashboard?
Any suggestions?
Thank you.
Solved! Go to solution.
I had to do this for importing Catalyst 9500 into the Meraki Dashboards:
adding the bold line on the switch config:
line vty 0 4
length 0
transport input ssh
transport output telnet ssh
I believe it is normal not to be able to SSH into a Cisco host, so this is not a valid test.
Do you have DNA Essentials or DNA Advantage?
Confirm that the switch(es) designated for onboarding are one of the following:
Catalyst 9200, 9300, or 9500 series hardware
Running IOS-XE 17.3.1 - 17.8.x
IOS-XE upgrade instructions and release notes: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9300/software/release/17-3/release_notes...
Current recommended IOS-XE release information can be found at: https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-series-switches/214814-recommended...
A full list of supported hardware can be found at: https://documentation.meraki.com/Clo...ud_Monitoring
Verify the ability to log in to https://dashboard.meraki.com/
Or create a free account. Instructions are available at: https://documentation.meraki.com/General_Administration/Organizations_and_Networks/Creating_a_Dashbo....
In Organization -> Settings verify that the checkbox for “Dashboard API Access” is selected and saved in the “Dashboard API access” section
From My Profile, choose "Generate new API key" or use an existing key. Note that a full admin account must be used. SAML log-in is not supported for API key creation
If an "invalid API key" error message appears, confirm the key and try again. API keys may take up to 15 minutes to become active in the onboarding application after creation.
The computer from which the onboarding application is run must be able to reach api.meraki.com on TCP port 443
The onboarding application is a stand-alone executable file; security settings on your local device must permit running this application and accessing the API server
HTTPS proxy servers that modify the certificate in transit are not currently supported
The Catalyst devices to onboard need access to the Cisco cloud
Ensure any firewall rules in place allow communication with the gateway corresponding with the dashboard region on TCP port 443:
Americas: us.tlsgw.meraki.com
EMEA: eu.tlsgw.meraki.com
Asia Pacific and Japan: ap.tlsgw.meraki.com
Test with telnet:
telnet us.tlsgw.meraki.com 443
I had to do this for importing Catalyst 9500 into the Meraki Dashboards:
adding the bold line on the switch config:
line vty 0 4
length 0
transport input ssh
transport output telnet ssh