Free Switch Port Map Generator

A switch port map records what is connected to each physical Ethernet or fiber port. It connects a port number to the endpoint, patch panel position, VLAN, PoE state, connection type, location and operational notes a technician needs.

Use the map to trace a cable, identify unused capacity, check an uplink or confirm a port before making a change. This generator is a manual documentation tool: it does not connect to a switch, discover devices or scan a network.

Start with the switch name, model and site location. For each port, record the connected device or endpoint, patch panel port, VLAN or trunk designation, PoE status, connection type, current status and the room or wall jack when known.

Enter verified details rather than inferring a connection from a port description. If a field is unknown, leave it blank or mark the connection as not specified; update the map after a change is tested.

At minimum, record the physical port number, endpoint, VLAN, link or port status and the patch panel reference when one is used. PoE, media type, room, wall jack, MAC address and notes add context for troubleshooting and remote hands.

Distinguish a port's configured role from the device currently connected. A port can be an uplink or trunk even when the far-end device changes; add the current endpoint and a review date in the permanent site record.

Use one naming scheme across switch maps, rack diagrams, cable labels and patch panel schedules. Keep device names and locations specific, use consistent VLAN names or IDs, and distinguish unused, disabled, uplink and trunk ports rather than treating them as interchangeable.

Review the map after moves, adds and changes. Verify the first and last port numbers against the physical switch, check uplink and trunk details with the network configuration, and date the permanent copy so technicians can tell whether it is current.

Record both ends of a permanent cable path: the switch and port, patch panel and port, and the wall jack or room where the run terminates. A clear mapping might show switch port 1 connected to PP1-01 and the Lobby access point.

Use the same panel and jack identifiers that appear on installed labels. Open the Patch Panel Documentation Template and Port Map to record destinations, and use the Patch Panel Label Generator to create consistent physical labels.

Record the access VLAN for an endpoint port and identify trunk ports explicitly. For trunks, note the native VLAN and allowed VLANs in the permanent network record when those details matter; a single short field on a printed map may not capture the full configuration.

Use the same VLAN ID and name as the switch configuration and the site's VLAN plan. The VLAN and Subnet Planner can help document subnet, gateway and DHCP details alongside this physical port map.

Mark whether a port provides power over Ethernet and name the connected device. Access points, cameras and phones may depend on PoE, so recording the switch port and destination can speed up power and connectivity checks.

A Yes or No entry is a field note, not a live reading of negotiated power or switch configuration. Verify the actual PoE setting and budget on the managed switch before changing power delivery.

Identify uplinks and trunks in the status field so they stand out from ordinary endpoint connections. Record the far-end switch, firewall or router, the patch path, media type and VLAN context that technicians need to trace the link.

Do not rely on a label alone to establish trunk membership, link speed or redundancy. Confirm those details from the switch configuration and keep the map in step with the change record.

A 24-port office switch map might show ports 1–12 serving workstations and phones, ports 13–20 serving access points and printers, ports 21–22 unused, and ports 23–24 reserved for uplinks or trunks. Record the VLAN, PoE state and patch panel port for each connection.

These assignments are only an example. Match the map to the installed switch and verified configuration rather than copying a sample layout into production documentation.

A 48-port access switch may use ports 1–36 for desks and printers, ports 37–44 for wireless access points, and the remaining ports for spare capacity or uplinks. Document each cable path and identify any port-channel members together in the notes.

For modular or mixed-media switches, record the port numbering and connection type as marked on the device. Do not assume every numbered port uses the same speed, connector or PoE capability.

Use a stable switch identifier such as SW-MDF-01 and a consistent port notation such as SW-MDF-01 / Gi1/0/24 when the manufacturer or site uses interface names. Include a building, closet or rack code when a switch name would otherwise be ambiguous.

Keep the physical number visible even if you also document a vendor-specific interface name. Pair port names with patch panel and destination IDs so a technician can move between the switch face, rack drawing and cable schedule.

A current port map reduces time spent tracing cables during outages, moves and troubleshooting. It also gives another technician a usable handoff when the person who installed the switch is unavailable.

Store the finished map with the client's network diagram, rack layout, VLAN plan and patch panel schedule. Reconcile the documents after changes so the map describes the network that is actually installed.