SevOne

SevOne

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

Meraki Wireless - Monitoring Networks 

Tue October 24, 2023 10:35 AM

Purpose of the Workflow: Monitor Meraki Wireless Networks

Description: This IBM Rapid Network Automation workflow allows us to use certified vendor APIs to collect performance data, in this from Cisco Meraki Wireless, and ingest it in SevOne, allowing us to:

  • Keep performance data for longer
  • Keep raw data for the whole retention period
  • Analyse the data, including enabling anomaly detection
  • Have a single report with data from different domains (legacy network, cloud, wireless, SDWAN...)

This workflow only collects data from 'networks', it will not collect data from APs (i.e. devices), SSIDs or wireless clients. Please use this workflow as a reference if you want to collect more data available in Cisco Meraki, even if it's from other domains (switches, cameras, firewalls...)

List of requirements:

Rapid Network Automation Version: 2022.8 or newer

SevOne Version: 6.6.0 or newer

Environment Required:

NMS Credentials

Meraki Credentials

SevOne Self-Service Data Ingestion workflow (available here https://community.ibm.com/community/user/aiops/viewdocument/sevone-data-ingestion-api-v3?CommunityKey=fe9d91df-352c-4846-9060-189fd98d00ca&tab=librarydocuments)

Setup:

  • Import workflow
  • Create Job to execute this workflow every 10 minutes

Expected Results:

There should be new devices created in SevOne with the names of the Wireless network available.

Statistics
0 Favorited
48 Views
1 Files
0 Shares
7 Downloads
Attachment(s)
zip file
Meraki Monitoring - Wireless Networks_2023-10-24_14_24_17.zip   1 KB   1 version
Uploaded - Tue October 24, 2023

Comments

Thu April 18, 2024 05:32 AM

Wed April 17, 2024 04:35 PM

Missing flow URL: admin/User/Production/SevOne Ingest Data - APIv3 (new v3 version)

Please export using absolute path and upload workflow again.