Member Avatar for sirlink99

I am wondering how to start drawing a network diagram. The way it was described to me I need to go into the configuration settings of the switches and check what type on connection there is and document where the connection is from, to where the connection is going. Then write it down. Once I have gone through all the switches I need to organize the data, and then produce the diagram from that.

Is that the correct way to go about doing it, or is there another procedure to accomplish this task?

Thanks for the help.

Edited by sirlink99
  • 4 Contributors
  • 4 Replies
  • 233 Views
  • 2 Months Discussion Span
  • Latest Post Latest Post by mrgreen

Dani AI

Generated

Good start — a practical diagram comes from a clear goal plus reliable data. Decide the audience and the level of detail first (executive: internet → firewall → datacenter; technician: rack, patch‑panel, switchport). Combine ’s edge‑to‑core approach with a disciplined inventory: physical connections, logical overlays (VLANs/subnets), and service mappings (DNS, NAT, ACLs). Not all links are visible in switch configs; plan to verify with multiple sources.

Practical workflow you can follow:

  1. Define scope and output format (Visio/draw.io editable source + PDF).
  2. Build a device inventory: hostname, model, mgmt IP, role, rack/U position.
  3. Gather connection evidence without changing production settings: CDP/LLDP, MAC tables, ARP, routing tables, traceroute and SNMP/topology data, plus physical patch‑panel labels.
  4. Map IP subnets/VLANs to devices and services.
  5. Produce diagrams in layers: high‑level, distribution/core, per‑rack/detail.
    Read‑only examples (Cisco) you might run from a management session:
    show lldp neighbors
show cdp neighbors detail
show mac address-table
show interface status
show vlan brief

What to record per link: local device and interface, remote device and interface, trunk/tagged VLANs and native VLAN, speed/duplex, port‑channel membership, patch‑panel ID/cable label, and any logical mapping (IP/subnet, purpose). For firewalls note NAT summaries and top ACLs — diagram the rule scope, not every line.

Drawing tips and cautions: start with a single clear backbone, then add detail. Use consistent naming and color codes, keep an editable master and maintain a simple change log (date, who, reason). Do not make config changes while collecting data; work read‑only and get backups. For different problems (like ’s lab request) open a new thread as advised so that recommendations and budgets can be addressed separately.

Recommended Answers

All 4 Replies

Member Avatar for CimmerianX

Start from the public internet and work your way into your network. IF this is just a hardware layout, then show the routers, firewalls, LBs, switches, etc... and the interconnects between each.

Look at some examples on google images for ideas

Member Avatar for sirlink99

Thanks for the reply. I have started, and I currenty have the firewall and the switches in place. I will then expand to the servers.

Member Avatar for uddhavn

i want to develope a lab of 60 nodes working for internet, online exams,ms-office, multimedia,etc. For secondary school level. Please give me configuration of equipments, structure of network. My budget is low.

Member Avatar for mrgreen

you should start your own thread for a new problem. This one is over 2 months old and has already been solved.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.