As a consultant for telcos and ISPs who do VoIP, nearly all of my customers have network diagrams. We use these diagrams when we make network design changes or troubleshoot an existing network.
However, nearly any time we study a customer's network diagram in detail, they'll say, "Wait, that's not right. This doesn't even show the FL-2100 we installed two years ago!" Or, "No, there must be more cables than this. There's no way this is right."
While I still learn important things from every customer's diagram, having an accurate network diagram can help streamline project management and issue resolution. That's why learning to create network diagrams effectively can be very useful for anyone who builds and manages VoIP networks.
In this blog, I'll break down the different types of network designs and what you need to know to draw an effective network diagram.
What Are Network Diagrams?
A network diagram is a graphical representation that depicts the architecture of a network. It's used to visualize the structure and design of a network, including the various nodes and connection points within it.
Network diagrams are important tools for engineering teams since they provide us with a way to understand and manage the network more efficiently. The two main network diagram types are physical, which shows the physical relationship between the components of a network, and logical, which shows how connecting devices in a network communicate with each other.
- Physical: Shows the physical relationship between networking devices and components.
- Logical: Shows how devices in a network communicate with each other.]
Universal Network Diagram Terminology
There are several commonly used symbols in a basic network diagram that you should be aware of, including:
Activity
Activity is an operation with a starting and end point. It's typically represented by an arrow and can reflect:
- Predecessor activities, which must be completed before another activity can begin.
- Successor activities, which can't be initiated until predecessor activities are completed.
- Concurrent activities, which should be started at the same time.
- Dummy activities, which don't use any resources but are important for depicting dependence.
Event
An event is depicted by a circle and shows a visual representation of the completion of activities and the beginning of new ones. Events can be one of three different types:
- Merge events, which are where one or more activities connect with the event.
- Burst events, which are where one or more activities leave an event.
- Merge and Burst events, which are where activities merge and burst simultaneously.
Sequencing
Sequencing reflects the precedence of relationships between multiple devices or activities in the network.
Types of Physical Layer Diagrams
Nearly everyone who builds and manages VoIP networks maintains physical layer diagrams, where each box symbol on the network diagram represents a physical device component, and each line represents a cable.
Physical diagrams can help with troubleshooting wholesale outages, counting available ports, or designing fault tolerance. And they're fine for 1994-era IP networking – all hubs, no VLANs, and only one IP address per device.
However, physical diagrams strain to convey:
- VLANs: Which VLAN is this port assigned to? Is it a VLAN trunk?
- Subnets:What subnet is this device a member of?
- Roles: Which network components are doing routing? Switching? Basic servers?
- IP routing tables per device: Such as Cisco VRFs / MPLS VPNs.
- Devices with multiple IP addresses within each stack: Visio users tend to insert pictures of the equipment, but it's often distracting and doesn't print well.
Here's an example of a physical layer network diagram:
VLAN/Subnet Diagrams
A VLAN/Subnet diagram is when each box represents a VRF or IP routing table – typically one per physical device. Every line represents an IP address assignment to a subnet. At the center, another shape, like an oval, represents the actual subnets or collision domains. In clean designs, one subnet is exactly one VLAN, and layer-2 switching equipment typically isn't drawn in.
VLAN/Subnet diagrams are ideal for following the paths of packets through the network. However, they have their limitations, too:
- They can't represent layer-2 redundancy.
- They aren't good at identifying available ports.
- Not every physical device is shown, so they aren't good for inventory.
- They don't show what data flow is normal or expected.
When VRFs are involved, an alternate approach is to create a network diagram that represents VLANs with color-coded cables. A blue cable is VLAN 101, a red cable is VLAN 102, and a green cable is VLAN 103. This method can be effective as long as you only have a small number of VLANs; otherwise, you might end up asking, "Which VLAN is magenta...and which is purple?"
Application-Layer Communication Diagrams
Another valuable abstraction for diagramming networks is called an application-layer communication diagram. This type of network diagram doesn't show any underlying transport but only the normal communication paths at the application layer. For any given device, there are connecting lines to every other device it communicates with at the application layer.
Application-layer communication diagrams are essential for developing effective firewall and IDS rules. They're also valuable for SIP VoIP platforms, where routing of SIP messages is complex and where it's reasonable to ask, "Where should this device be sending its INVITE? To what other devices will it be sending RTP?"
An example of an application-layer communication network diagram is below:
Basic Network Topologies
Choosing the right network diagram topology is essential when designing and documenting network structures. Some popular options include:
Bus
Bus topology, often called line topology, is where every network device is linked to a single cable called the backbone. This configuration allows data transmission across the network from one computer to another. But while it's easy to set up and takes less cable than most other topologies, bus topology networks have risks.
Any failure along the backbone can disrupt the entire network. Troubleshooting can also be difficult since identifying the exact point of failure in the bus is complex. Because of these issues, bus topology is typically more suitable for small networks with minimal network traffic.
Star
Star topology is a type of network where each device is connected to a central hub, switch, or computer, which acts as a conduit to transmit data. This setup is like the spokes on a bicycle wheel, with the central node functioning as the hub.
It's a generally reliable network structure since if one device fails, it doesn't affect the rest of the network. However, the central hub is a potential point of failure – if it goes down, the entire network collapses.
Tree
Tree topology, sometimes referred to as hierarchical topology, integrates the characteristics of bus and star topologies. In this setup, multiple star networks are connected to a single bus, with each star acting as a node in the bus network. The central node of each star network is connected to a central backbone, similar to branches connecting to a tree trunk – hence the name.
A main advantage of tree topology is its scalability, allowing easy addition or removal of nodes. But, since interconnection depends on the central backbone, the whole network is susceptible to failure if the backbone breaks down.
Ring
Ring topology is a type of network setup where each device is connected to two others, forming a ring. Data is transferred from one device to another in a circle until it reaches the intended location.
While this configuration allows for more efficient bandwidth use, the failure of just one device can disrupt the entire network. Adding or removing devices can also be complex as it might disrupt network communication. Despite these challenges, ring topology is favored in some systems for its simplicity and predictable data path.
Mesh
Mesh topology is where each device, or node, is connected to other nodes within the network. It creates multiple pathways for transmitting data and provides redundancy, so if one path fails, data can reroute through another, making mesh networks highly reliable.
However, this robustness and complexity can make them more expensive and difficult to manage than other topologies. They're often used in high-demand situations where network failure is unacceptable, such as in data centers or telecom networks.
Step-by-Step Guide to Drawing a Network Diagram
Drawing a network diagram requires detailed knowledge of the network's architecture and every device involved. Here's a step-by-step guide to help you draw a basic network diagram:
- Identify and list each device in your network: This can include servers, routers, switches, hubs, and endpoints like workstations and laptops.
- Decide on which topology to use for your network: The topology could be bus, star, tree, ring, or mesh, as discussed above. The topology you choose will shape how your devices are interconnected.
- Draw the main components first: Start by plotting the central devices like switches, servers, or routers that act as your network's principal hubs or backbones.
- Connect the devices: Once the main components are in place, draw lines representing the connections between each device.
- Add endpoints: Now, you can add endpoints like workstations and laptops and connect them to the main device.
- Label all devices and connection points: Clearly label each device, connection, and relevant symbols. This can include information like device names, IP addresses, and the type of connection.
- Review and update: Ensure that all network devices are included and accurately interconnected. Regular updates of the diagram are necessary to reflect changes within the network.
Remember that the goal of creating a network diagram is to visually represent your network's structure. Diagramming software can also assist in simplifying the design and updating processes of complex diagrams.
Learn How To Draw a Network Diagram With Expert Guidance From ECG
If you're struggling to draw network diagrams, we're here to help. Drawing an effective network diagram takes a lot of in-depth experience in designing and managing different network architectures.
Working with a voice engineering consultant like ECG can help you get the expertise needed to create a network diagram that represents your complex systems. We have years of proven experience building and supporting voice networks for dozens of VoIP service providers in the U.S. and worldwide, so you can trust our engineering team to deliver elegant network designs or provide the training your staff needs to draw a network diagram better.
Ready to create more accurate diagrams for your network upgrade and expansion projects? Get in touch with ECG today.