Network Diagrams: Drawing complex VLAN Networks with IP Addressing

In an earlier article I showed you how to create a simple VLAN image from a single line. I also talked about why using ONLY a line makes it more simple. If you need a recap go back to Network Diagrams: Labelling an VLAN/IP Segment (and the earlier article on the same topic Network Diagrams: VLANs and IP Subnets.

OK, got that in your head. I think we are ready to go on. Note: I assume that you have some experience in drawing diagrams and familiar with some of the hassles of representing a data network.

Drawing multiple VLANs and IP Subnets

For larger networks, you often have equipment that need to connect to multiple VLANs.

visio-mult-vlan-subnets-1.jpg

The problem is showing the all the connections in a meaningful way. Using straight lines ends up showing something like this:

visio-mult-vlan-subnets-2.jpg

If you use dynamic connectors, it will look completely useless as the right angles ends up invisible: Something like this:

visio-mult-vlan-subnets-3.jpg

.

Understand the problem, don’t look at the solution

I think the problem here is that I like using the pretty Cisco router icons. You can’t get them to clearly represent the physical device with interfaces (either logical or physical). Well, you can for small and simple diagrams like thss one, the Cisco router icon kind of just works:

visio-mult-vlan-subnets-4.jpg

My problem is that I am looking at the solution, not the problem. In other words, how can I make the Cisco router icon have meaning for a more complicated diagram. The answer is not to the use the Cisco router thingie and make your own shape.

What sort of shape ?

Any shape you like really. My preference tends towards something like this:

visio-mult-vlan-subnets-5.jpg

Building this shape

  1. Draw a simple box
  2. Go Format, Line & change the colour of the line to a dark blue, and set rounded corners
  3. Go Format, Fill & change the colour of the fill to pale colour
visio-mult-vlan-subnets-6.jpg

Labelling the Shape

There are a few ways of attacking this problem. When I think about the data that I need:

  • The box needs at least name
  • maybe to the loopback address if you are using loopbacks for management
  • IP address
  • interface name ie. for a Cisco Fa0/0

This data tends to two categories: details of the system, and details of the interface. I prefer click on the box to go into text mode and enter the name and, maybe the model. Most people use an object PLUS a text box which causes problems when you want to move objects around the page.

visio-mult-vlan-subnets-7.jpg

Quick Aside – textbox or object property

Most people would draw a line, then get the text tool to “add text” to the line.

visio-mult-vlan-subnets-9.jpg

But later on, if you need to move the VLAN around the page, the text gets left behind…..

visio-mult-vlan-subnets-10.jpg

The best way around this is to double click the VLAN graphic and get a text box. This text ‘belongs‘ to the ‘line’ so when you move the line, it always keeps the information.

visio-mult-vlan-subnets-11.jpg

I cover this topic in a lot more detail in THIS POST including some useful formatting tips for .

Labels – where do I the labels ?

A diagram is a picture with information on it. It’s not art. But when I put labels on the interfaces, the diagram start to look crowded.

visio-mult-vlan-subnets-8.jpg

The information could be split into two parts, the VLAN and the interface details. Lets try that again. This time with a bit of colour as well.

visio-mult-vlan-subnets-12.jpg

What is not very clear, is which lines connect to which. You can tell by where they end, but in much larger diagrams, its not so clear. Lets use the line ends to show the connection. Note: you should mark only one end. Since it is nearly always the ‘wrong’ end that gets the marker you can either rotate the line, choose the other end.

visio-mult-vlan-subnets-13.jpg

Now, this is a lot nicer looking.

visio-mult-vlan-subnets-14.jpg

Noting the different types of diagrams and their complexity

Some people don’t have the opportunity to draw big or complicated networks. I find this approach works well for large diagrams that have a lot of network elements and you want to capture the details of the device, which VLAN they connect to, and the interface addresses. ((In fact, I am not generally a believer in this kind of documentation. Trying to keep this documentation up to date, and accurate, requires will power that very few people have.
visio-mult-vlan-subnets-15

Design Diagrams are different

Its worth noting that I would not create this type of diagrams when I am designing. A design diagram for this network contains a lot less information and more accurately represent the ‘approach’ or the ‘intent’ of the design.

For example, the high level design for the diagram above would look something like this, where the design intent that all elements are redundant is not clear from looking at the diagram, but anyone reviewing the design would understand the functional intent.

visio-mult-vlan-subnets-16.jpg

Wrap Up

So the overview here is for implementation diagrams that are likely to be used by field or operations people. The great failing of this documentation is that operational people do not update these diagrams unless driven to it by management.

Still, these are some suggestions on how to do it.

PostScript

If you like this article, you might like to buy a book I wrote on using Visio for network diagrams.It’s just a few dollars, free of DRM and contains content just like this blog post. Click the widget below for more information or to buy the book.

Other Posts in A Series On The Same Topic

  1. Network Diagrams: Font Selection and Production Context. Choosing Slab or Thin fonts (9th June 2014)
  2. Book Release: Tips on Using Visio To Make Network Diagrams (27th March 2014)
  3. Network Diagrams: Drawing Overlay Network Layers (14th March 2014)
  4. Network Diagrams: Choosing Better and Free Fonts (10th January 2014)
  5. My New Diagram Colour Scheme "Old Disco Style" (24th September 2013)
  6. On Diagrams and Information (10th September 2013)
  7. Colour Blindness, Network Diagrams and Reliability (3rd March 2011)
  8. Designer or Engineer, Artist or Painter (19th January 2010)
  9. Network Diagrams: Rotating Text on a Line (1st October 2009)
  10. Network Diagrams: Tips for Printing from Visio (22nd September 2009)
  11. Network Diagrams:Zones on a diagram with Visio shape union (31st July 2009)
  12. Network Diagrams: Drawing complex VLAN Networks with IP Addressing (7th July 2009)
  13. Network Diagrams: Drawing Freehand Curves (and then fixing them) (23rd March 2009)
  14. Network Diagrams:Aligning Shapes (12th March 2009)
  15. Network Diagrams:Locking the Background Shape (10th March 2009)
  16. Network Diagrams: Labelling an VLAN/IP Segment (9th March 2009)
  17. Network Diagrams: VLANs and IP Subnets (8th March 2009)
  18. Network Diagrams: Drawing the Background Shape (6th March 2009)
  19. On the Art of Network Diagrams and Presentation (4th March 2009)
  • Fernando

    Hi Greg,

    I follow this series of article with great interest, as I often get to draw network perimeters for both design and operation purposes. Thank you for all the information!

    One thing I’ve used with some (moderate) success is the use of Visio layers – L2 connections and labels on one layer, L3 information on another and traffic flow diagrams on another one. I can’t get all on the same diagram, but at least I have one major diagram I update and generate several snapshots off of it.

    Thanks again!

    • http://etherealmind.com Greg Ferro

      Hi Fernando

      Thanks for the tip on layers, I do use them quite a bit myself. Possibly will do an article in future about them.

  • Andrew

    A great way of representing VLANs. Have you worked out a solution for trunk connections though in these type of diagrams?

    Thanks

    Andrew

  • Den V B

    speaking of Dynamic connectors, one can setup routing rules in Page properties dialog to suit one’s needs.
    I found dynamic connectors very helpful for L1-L2 diagrams, when i need to place, like, dozens of switches on a sheet, and make sure it’s human (not me) readable. I think what “playing with cubes” part of diagram design process would be a hell without this type of connectors…

    And your idea about VLANs is great. it results in a very clear view=)
    In my practice, i’m just drawing different-colored lines parallel to physical link representations, and name them at the ends. It’s good enough for 2-5 vlans, but more is such a mess…

  • http://www.jaxbeachtech.com Don

    Greg,
    I like this style for VLAN diags.  Thanks for all of the effort to do this.
    One question: How do you get the end of the line to sit right OVER the VLAN line ?
    When I have the connection (say from switch to VLAN, the END of the link butts up to the vlan and so the ball that represents the end of it sits off to the side of the line, rather than OVER it (Centered).
    Any clue on how to do this ?

    Thx.
    Don

  • SilentLennie

    “In fact, I am not generally a believer in this kind of documentation.
    Trying to keep this documentation up to date, and accurate, requires
    will power that very few people have.”

    Nope, you don’t want to create that documentation. But what you should do is generate diagrams like that from data collected about how the network is configured.

    If you collect information about the network during normal operations, when things fail you can see how things were or are connected at the time of the failure, this will hopefully allow you to fix things faster.

  • fizzixs

    Great blog, I’m amazed how much of my work comes down to graphic design.
    Thanks so much

    • http://etherealmind.com Etherealmind

      Pleased to hear. Hadn’t thought about engineer as graphic design. Interesting idea.

  • Marcy White

    Great article! Try building diagrams with Lucid Chart’s diagramming software, it’s awesome!