switch-port-lookup

Resolve Meraki switch ports and generate structured reports of configuration and live status.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill switch-port-lookup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: switch-port-lookup
Source: https://github.com/afoxnyc3/chelsea-piers-itops/tree/main/chelsea-piers-itops/skills/switch-port-lookup
Command: npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill switch-port-lookup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify which Meraki switch port a device is using when connectivity is failing, a port appears down, or you need to trace a client to its physical wiring.

Core Features & Use Cases

  • Device-to-Port Resolution: Find the switch port by switch+port, client MAC, client IP, or hostname, then return the associated port details.
  • Port Health & Network Context: Provide VLAN configuration, PoE status, STP state, live link status, error counters, and neighbor (LLDP/CDP) information when available.
  • Operational Triage: Flag issues such as a down port, unauthorized VLANs, unexpected VLANs, or PoE budget risks, and suggest recommended next actions for faster incident response.

Quick Start

Run /switch-port-lookup with a switch name and port number, a client MAC/IP, or a device hostname to get a structured port report.

Frequently Asked Questions about switch-port-lookup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find which Meraki switch port a device is connected to?

To trace a Meraki switch port, query by switch name and port number, client MAC, client IP, or device hostname to resolve the physical connection and return structured port details for connectivity troubleshooting.

What information is included in a Meraki switch port health report?

A Meraki switch port health report provides VLAN configuration, PoE status, STP state, live link status, error counters, and LLDP/CDP neighbor data to validate access and trunk port correctness.

How do I troubleshoot a down Meraki switch port during an incident?

Troubleshoot a down Meraki switch port by resolving the port identifier to retrieve live status, error counters, and STP state, which flags issues like unauthorized VLANs or PoE budget risks and suggests next actions.

Can I trace an unknown endpoint to its physical patch panel using LLDP and CDP neighbor data?

Yes, trace unknown endpoints by resolving client-to-port correlation and optionally retrieving LLDP/CDP neighbor data to identify the physical wiring path and connected infrastructure.

Do I need the Meraki API to validate VLAN and PoE configuration on access ports?

Yes, Meraki API lookups are required to retrieve port configuration and live status for validating VLAN assignment, PoE budget, and STP correctness on Meraki access and trunk ports.

Why does my Meraki switch port show unexpected VLAN or PoE budget issues?

Unexpected VLAN or PoE budget issues are flagged during port resolution by comparing live status and configuration against expected values, helping identify unauthorized VLANs or power allocation risks for faster triage.