What Neo can do with Cisco Meraki
- Find the customer and the device. Match the ticket’s company to a Meraki organization or network, and find a device by serial, MAC or name.
- Answer “is it really down”. Read device availability and when it changed, MX uplink status, WAN loss and latency, and VPN tunnel state.
- Investigate. Read network events, assurance alerts, the configuration change log, switch port status and LLDP/CDP neighbours, Wi-Fi connection and failure stats, and a user’s client.
- Run live diagnostics. Ping from a device, read its ARP or MAC table, check switch port status and PoE power.
- Check licences and firmware. Read licence expiry, co-term state and scheduled firmware upgrades.
- Act, with the approvals you choose. Reboot a device, cycle a switch port, run a cable test, block a client, or change an SSID, VLAN or firewall rule.
- Document the network. Write the customer’s organizations, networks and devices, with models, serials, firmware, uplinks, VLANs and SSIDs, into the ticket, IT Glue or Hudu.
Your Meraki organizations and networks are mapped to clients
Neo matches your Meraki organizations and networks to companies in your PSA and keeps the mapping on the Cisco Meraki card’s Organization Mapping tab. It refreshes the mapping when you save the API key, and again on each nightly PSA sync. Neo matches each organization first. For an organization that matches no client, such as a service-tier organization, Neo matches each of its networks instead. Networks named like “Acme - HQ” and “Acme - Branch” both map to Acme. An organization with only one network shows as that network. Once one of an organization’s networks is mapped, the organization itself no longer shows, because it holds several clients. Each name is matched exactly, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the rest. A name match, or one you confirm, is handed straight to your agents, so they start from the client’s organization and network ids without looking them up. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. Neo sees only the organizations the API key’s admin can access. An organization whose networks Meraki does not let Neo list (for example, with API access turned off) does not show. Anything else Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. One API key reaches every organization its admin can see. On a ticket that names a company, Neo sends a call only for the organizations and networks the ticket’s company is mapped to on the Organization Mapping tab, and checks that a device or network belongs to that client before it acts on it. For a client that is one network in a shared organization, Neo reads only what Meraki can filter to that network and makes no organization-wide change. Account-wide calls, such as the list of all organizations, are made only outside a ticket, such as from a chat with Neo. When a ticket’s company has no mapping, Neo asks a technician to map it.Next steps
Connect Cisco Meraki
Generate an API key in the Meraki dashboard and save it in Neo.
