I've written in the past about the need to use network design templates. However, part of developing the templates is picking standard icons to use in the diagrams. The problem is there are just so many different formats to choose from; and everyone has their own favorite.
Cisco adds to this problem. Just for a "router" they have a black icon:
and a blue icon:
and a grey icon:
and the high quality Packet Magazine icon (even though the magazine doesn't exist anymore):
and then, what seems to be the Cisco favorite, the PowerPoint blue icon:
And that's just for routers. Then you get to choose which icons to use for everything else. Like switches and WAPs and clouds and IP Phones and users and MUXs and firewalls and........AHHHH....
Plus, have you ever copied and pasted the Packet Magazine or PowerPoint icons into Visio? The Visio file sizes are HUGE. Our normal Visio site diagram with four tabs is 7.3 MB. Our DC template had to be broken into several files because it ballooned to over 40 MB. It was fun to watch Windows and Visio choke on that monster. You'd need a reboot soon if you were not provided one.
If you're a real geek you can take a shot at the Visio stencils Cisco provides. These can be very nice because they show the actual view of the device and you can add appropriate line cards or modules. For example, here's an empty Cisco 2821 router:
Then you can use the stencils for modules and HWICs to complete the router. Now you have a complete device view and can connect lines to the actual physical interfaces making it a very useful visual tool for network builds. However, this is extremely time consuming and I've often been frustrated to find the Visio stencil for certain network modules missing. Then you end up with a big black hole in your diagram or you have to create your own stencil for that new line card. Just keeping track of all the stencils and icons is hard enough. There are 90 stencil files on that web page each with many individual stencils. The complete stencil collection is 85 MB.
Our team struggled with choosing standard icons for nearly 6 months a few years back. Everyone had their favorite icons and didn't want to change. I actually came up with a different approach. I created my own icons - just a bunch of squares and circles.
That went over like a ton of bricks. Everyone hated them and just kept on using their own favorite icons. We finally all sat down together and agreed on which icons to use. We now use the Cisco Packet Magazine Icons and have selected specific icons in that collection to represent an ISR or a 7600 or a WAP. That provided uniformity in our diagrams.
But wow, it was amazing people's affinity for their favorite icons. Just let go. It's just an icon.
Michael Morris is a communications engineering manager at a $3-billion high-tech company. His background is in enterprise WANs working with telcos and developing large-scale routing designs. He has worked on networks at government and corporate organizations, including networks at two Fortune 10 companies. In his current role, he leads a team of 10 engineers responsible for large-scale IT networking projects and architectural standards for data networks, storage area networks, IP telephony, contact centers, and security. Michael is CCIE #11733 and recently became one of the first three Cisco Certified Design Experts (CCDE) ever (#20080002). He has 11 years experience in networking and communications, including four years as a paratrooper in the U.S. Army. He has a bachelor's degree in MIS from the University at Buffalo and is working on his MBA from NC State University. In 2008, he was awarded the Network Professional Association (NPA) Professional Excellence and Innovation Award for his work on network architecture, templates and enterprise MPLS design.
Michael Morris's From the Field blog is also featured on the Cisco Learning Network. See it there, along with the blogs of other Cisco Experts.