When it comes to maintaining and managing an IT infrastructure, network diagrams are critical to compliance, security, troubleshooting, and minimizing downtime. Network diagrams, or maps, are […]

Physical Network Diagrams Explained

When it comes to maintaining and managing an IT infrastructure, network diagrams are critical to compliance, security, troubleshooting, and minimizing downtime. Network diagrams, or maps, are […]

physical-network-diagrams-intro-imageWhen it comes to maintaining and managing an IT infrastructure, network diagrams are critical to compliance, security, troubleshooting, and minimizing downtime. Network diagrams, or maps, are visuals that use symbols/icons/shapes to depict the different objects and connections in a network. Depending upon what you need to document, you may will probably have different types of network diagrams. The two most common network diagrams you’ll come across are physical and logical.

Logical network diagrams focus in on how traffic flows across the network, IP addresses, admin domains, how domains are routed, control points, and so on. Within the OSI model of networking, logical diagrams are referred to as ‘L2’.

example-of-logical-network-diagram-created-with-software

A physical network diagram will, ideally, show the network topology exactly as it is: with all of the devices and the connections between them. Because physical diagrams depict all of the physical aspects of the network, they will likely include: ports, cables, racks, servers, specific models, and so on. Within the OSI model of networking, physical diagrams are referred to as ‘L1’. So, a physical network diagram could be a network’s server diagram, a network’s cabling diagram, racks diagram, or a mix of different types of diagram that is interactive and allows you to view what you need to see (if you’re using automated mapping software).

Physical Network Diagrams: What’s In Them?
Because physical network diagrams depict the entire topology of the physical network, they can include a number of different components:

  • Connections:connections are critical to a physical network diagram. Connectors (aka connections) depict the physical cabling that connects physical devices in a network. The ends of each connection should be labeled both with whichever port it connects to and where it ends.Depending upon the level of detail required, you may use different colors, thickness, and types of lines to represent differences in connections: such as fiber, copper, and so on.
  • Labels:Labels tell the viewer what they are looking at, especially when a physical diagram uses generic icons. Everything that is active and managed in the network should be labeled with the hostname and IP address, including: switches, routers, firewalls, and so on. When a device is active and being managed elsewhere, it should still be labeled in some way (perhaps with a different font to differentiate it from the other network devices).
  • Diagram Legend: a diagram’s legends tells the viewer what the different objects and connections mean. The legend translates the different graphics, icons, colors, and gives it real-world meaning. If, for example, you use double black lines to represent a type of fiber cabling — you would include this in your legend.
  • Switch Stacks: switch stacks, that function similar to a chassis switch, are generally depicted as a single object/device.

Physical Network Diagrams: Shapes, Symbols, or Models?
How you depict the physical network and connections is up to you and the needs of your organization: you can be as general (for example, using generic topology icons) or specific (use exact device models as icons) as needed. Using generic topology icons can be more easily read by anyone; specific models of devices (exact models that include fans, rack ears, and ports, for example) may require more familiarity with exactly what is in a given network. If you are using DCIM or network documentation software, you may choose to use the generic icons for higher-level layers and more specific icons/models as you drill down.

example-of-using-specific-models-in-physical-network-diagrams

example-of-using-general-icons-in-physical-network-diagrams

Physical Network Diagrams: How are they Created?
You can create physical network diagrams in a variety of ways: by hand, using software such as Visio, or with a dedicated network diagramming or DCIM software. While Visio or hand-drawn network diagrams may work for small networks, one of the keys to successful network documentation is ongoing documentation. If you are managing a larger network with any complexity, you may want the ability to automatically generate network diagrams with a few clicks, based on real-time data.

Bottomline? Without physical diagrams of the network, it’s hard to quickly plan for capacity, fix problems, avoid zombie servers, and IT clutter. If you are trying to use spreadsheets or static Visio diagrams, it may be time to look at upgrading to an enterprise-grade diagramming software specifically for network documentation.

Hannah Ash
Hannah Ash
Hannah Ash is a marketing specialist who loves thinking, writing and speculating about the future of the data center.

2 Comments

  1. Shayne says:

    wait… are you saying that Visio is not an enterprise-grade diagramming tool?

  2. Not by any stretch of the imagination :- )
    At least not the way the industry usually utilizes the term “enterprise-grade”

    I know… it is very self serving because I am responding on behalf of the vendor here, but (and please don’t take it the wrong way) this one is too easy, if I may:
    – Visio is not multi-user
    – Visio is not concurrent
    – Visio is not web-based (no, SharePoint or other convoluted alternatives do not qualify, the actual tool is desktop-based)
    – Visio has no inherent built-in security. Pass the file and anybody can open it. No privileges as to who can open what, which part, etc

    I hope we can agree that those four are sort of the “Enterprise-grade 101” litmus tests?

    But it keeps going, because nowadays companies also require basic traits considered essential in a large multi-user environment, and Visio also lacks:

    – Audit trails
    – Any sort of discovery
    – Basic reporting (let alone a dashboard or BI tool)
    – Some sort of workflow management

    Notice that I haven’t really gone into actual network documentation specific features yet.
    And you can make the case that Enterprise grade software kinda needs to have ready-made solutions. Visio is still in essence just a drawing tool.
    What I mean by that is that it has no:

    – automation capabilities
    – device modeling (no, stencils don’t quality, real modeling means that you add a device and it already creates the ports, slots, knows about the power specs, etc)
    – auto rack mounting
    – mapping capabilities
    – and on and on

    Don’t get me wrong, Visio is good at many things and it certainly has features that tools like netTerrain don’t have, but they are usually drawing generic features and not things that make a software Enterprise-grade.

    Hope this helps!
    Jan

Leave a Reply

Your email address will not be published. Required fields are marked *