×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Network Maps and methods

Answered Question
Feb 8th, 2014
User Badges:

Folks:

I am curious on how others handle making network maps? I remember reading somewhere that multiple maps should be drawn, which reflects different layers of the OSI model. Example: overall network map (high level view), Layer 3 and Layer 2 maps. In addition, when dealing with Layer 2 and STP – is it beneficial to map the physical network, and then map the ports that are in blocking status on a different map?


Since I am very new to the industry – how do most network veterans handle their network maps? What should I focus on? What should I pay attention too and not get slowed down?



Thank you

JJ

Correct Answer by Marvin Rhoads about 3 years 6 months ago

I've heard the same argument about multiple maps for the varying OSI layers. While it's a good idea, it often falls apart because the people advocating it in theory aren't usually the ones actually maintaining it. Or its created as part of a major refresh or Greenfield deployment and then staff aren't assigned to own the ongoing maintenance of it.


For those reason, I say start small - a map that at least has all of your devices and the relevant connectivity between them is a good start. Add in some VLAN and addressing as necessary to add value to the staff who use the map.


Most importantly no matter what scheme you decides best suits you is to have a process to keep the information current. Without that, any theoretical advantage of one representation vs. another quickly becomes a moot point.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Marvin Rhoads Sun, 02/09/2014 - 08:15
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,
  • Cisco Designated VIP,

    2017 Firewalling, Network Management, VPN

I've heard the same argument about multiple maps for the varying OSI layers. While it's a good idea, it often falls apart because the people advocating it in theory aren't usually the ones actually maintaining it. Or its created as part of a major refresh or Greenfield deployment and then staff aren't assigned to own the ongoing maintenance of it.


For those reason, I say start small - a map that at least has all of your devices and the relevant connectivity between them is a good start. Add in some VLAN and addressing as necessary to add value to the staff who use the map.


Most importantly no matter what scheme you decides best suits you is to have a process to keep the information current. Without that, any theoretical advantage of one representation vs. another quickly becomes a moot point.

Actions

This Discussion