Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Complex Network Design Tools?

Cliff posted more than 11 years ago | from the thinking-things-through dept.

Software 33

I'm-Not-A-BOFH asks: "How do you do your large scale network design? I am currently designing a large enterprise network - and there is a ton of information to track and think about. I use AutoCAD, Visio and Cisco Configmaker (which sucks) and many other applications. I am looking for software specifically designed to help you design a network. What tools do you use - and what tools are out there that maybe are little known? How do you begin to manage network documentation when your hosts get into the thousands and your routers and routes into the hundreds? I am really just interested in the tools used to accomplish this - as all the tools I have been finding are just not adequate or well thought out. Please let me know what you think is invaluable to you when you design your systems."

cancel ×

33 comments

Sorry! There are no comments related to the filter you selected.

oh this is so easy (-1, Troll)

Anonymous Coward | more than 11 years ago | (#6354840)

paper and pencil

Try Us (-1)

peripatetic_bum (211859) | more than 11 years ago | (#6354896)

We will be glad to help you out. Contact mailto:dude@networkninjas.com
or ian and we can help you set this up

G

Some useful tools. (3, Informative)

Mordant (138460) | more than 11 years ago | (#6354954)

http://www.research.att.com/sw/tools/graphviz/

http://www.lumeta.com/ipsonar.html

The whiteboard.

A good knowledge of networking protocols, etc.

The hardcore network engineer doesn't need diagrams - sh ip route, sh ip bgp, sh ip ospf, sh cdp neigh, sh arp, sh cam dyn, etc. (in Cisco-speak; there are equivalents for other vendors) are enough to visualize/plan/troubleshoot, quite frankly.

Re:Some useful tools. (3, Insightful)

RabidMonkey (30447) | more than 11 years ago | (#6355440)

Yes... because a hardcore network engineer can visualize hundreds of routers/switches, all their varioius routing protocols and associated foibles, all the redundancies etc ...

Thats assinine. Have you ever worked on a network with THOUSANDS of devices before? He didn't say 'Small Business' he said 'enterprise'.

stupid arrogant people assuming the people who need diagrams aren't good enough. Glad you can sit and boost your ego that way, but when that stops working for you, join the real world.

To keep this slighly on topic, try using Ciscoworks [cisco.com] ... its good for planning, config backup, management, etc.

Re:Some useful tools. (3, Interesting)

Mordant (138460) | more than 11 years ago | (#6356196)

I do just that, every day - on a VERY large enterprise network. Before that, for an ISP hosting one of the busiest Web sites in the world.

Our network changes so much (because it's so large, and there are many people doing things to it 24/7 worldwide) that any sort of diagrams are pretty much obsolete the moment they're drawn. The pretty pictures are useful props for talking to management, etc., but they are of zero value in troubleshooting the network.

I don't need to visualize thousands (we went into five figures years ago) of devices simultaneously - nobody does. But since we adhere to sound architectural principles, and know what we're doing, I can troubleshoot any portion of said network without any diagrams other than the ones in my head as I poke around and a few quick sketches I might draw 'live' on a pad as I make inferences from my observations.

Re:Some useful tools. ---- what's that we hear? (-1, Redundant)

Anonymous Coward | more than 11 years ago | (#6356555)

so is this what's called a pissing contest?

Re:Some useful tools. (1)

Glamdrlng (654792) | more than 11 years ago | (#6378287)

OK so for the moment I'll ignore the inadequacies of maintaining a large network without diagrams. Myself, I'm a visual person, so a diagram helps me visualize traffic flows etc. It's also useful for having a conversation with someone else about the network. But what do you do when (if) you bring in a consultant or a sales engineer, or if you hire someone new in your department? Do you just tell them to go nuts on your routers looking at routing tables, link state databases, and bgp tables? Myself, there's nothing I love more when I'm consulting than being brought into a network that has jack for documentation. It means that I'm getting at least two billable hours out of the deal just for documenting the network, or the segment that I'm working on. There's only one reason to keep inadequate documentation and do seat-of-your-pants networking like that, and that's to maintain your job security.

Re:Some useful tools. (1)

Mordant (138460) | more than 11 years ago | (#6381341)

That's untrue.

The reason is because we're understaffed, and we're just too damned swamped to have a dedicated doc-monkey or two to do the work.

I'm not worried about my job security - I'm one of the best in the world at what I do. When someone new joins our group, we spend 4-8 hours initially on the whiteboard, and then subsequent time as events warrant. Since we haven't acquired any new members in the last year or so, it hasn't been necessary.

Re:Some useful tools. (1)

Glamdrlng (654792) | more than 11 years ago | (#6384359)

Hey man if it works for you than knock yourself out. Myself, it seems to me that the fact that multiple people are making changes to the network 24/7 should make documentation that much more necessary, be it a visual diagram or some other form.

I'm going to hazard a guess that even in your environment there's still a spreadsheet or a databse or something you use to look up IP's by location and make sure you don't assign overlapping IP's right? If that's the case, and you haven't played with it yourself yet, you may want to take a look at Visio 2002 Enterprise. It uses SNMP queries to build an SQL database while automatically diagramming your network. I know you're a command line kinda guy, and that's my preferred way to work on routers too. But if you want something to help out any junior techs or to automate your diagrams for when you appease your management, you may want to check it out.

Salud.

Re:Some useful tools. (1)

Mordant (138460) | more than 11 years ago | (#6384629)

For that sort of thing, we have a very sophisticated system . . . we trend SNMP stuff, use NetFlow, have RMON probes, manage both IPv4 and IPv6 address space, etc.

We just don't have lots of pretty diagrams lying around. ;>

CiscoWorks (1)

argel (83930) | more than 11 years ago | (#6363530)

From what I have seen of CiscoWorks, it is more of a management tool and less of a design tool.

Re:Some useful tools. (1)

arkepp (604390) | more than 11 years ago | (#6387106)

Maybe the hardcore engineer doesn't need it, but the company does!

If you have a serious network then that information is too vital (to the company) to be stored in the head of one person.

What if he/she retires? What if something bad happens? Do you get a whiteboard and start from scratch to figure out how these wires are supposed to be connected and why?

Netviz (2, Interesting)

ryanmoffett (265601) | more than 11 years ago | (#6354991)

We use Netviz. It is data-driven and all the data for the diagrams can be stored in a database. Create one instance of a router, and that instance can appear in any of your diagrams with all of the properties, links and any number of user-defined attributes. Diagrams can be constructed in a hierarchy with drill-down-to-detail capability. Obviously, this is only one component of many you will need in the design process. It doesn't contain all the device specific config-checking tools that some other vendor-specifc tools have, but who needs those anyway?

Also, another set of tools that you might find useful is Opnet IT guru. If you need to model a proof of concept involving a complex network and application interaction, this can do it.

If you run a very Cisco-centric network (or totally Cisco) you can use IPAT Plus from WANDL. It takes Cisco router configs and builds a network model that can be used for reachability proof and various what-if scenarios.

Re:Netviz (1)

metacosm (45796) | more than 11 years ago | (#6360676)

I agree with the above post -- the most important thing about netvis is the layers of views. On a large scale network -- at the top level -- you would probably just see your 20 or 30 buildings. You can then click on that building to see the rooms inside it, you can than click on a room to find the hardware inside it which can be abstracted into groups like "routers", "servers" or anything else you can think of. NetVis lets you logically organize your large structure and is searchable.

You need to be abstract the complexity of what you are doing. The drill down to detail ability is SO important for large network design.

Yet another Ask Google... (0)

Anonymous Coward | more than 11 years ago | (#6355115)

Google Google Google [google.com]

Do I have to do all the work for you?

Google wasn't very helpful, ... (1)

Futurepower(R) (558542) | more than 11 years ago | (#6358267)

Google wasn't very helpful, I found. Mostly I saw a lot of marketing language written by people who don't really understand what they are writing and are bored by it, anyway.

opnet (3, Informative)

austad (22163) | more than 11 years ago | (#6355444)

Opnet [opnet.com]

I've been looking at this recently to see how different things will affect my network, since I can't really test them on the live network without making a lot of people and clients really mad. I have not used it yet though.

I prefer to design the network simply using Visio to get a good logical design, and then once that is down, I create another map with the physical layout. Worry about your routing protocols after you have figured out the best logical design (redundancy, required link speeds, etc.). Most network admins have a favorite routing protocol, which for most seems to be EIGRP with cisco equipment. I personally like OSPF because it offers enormous flexibility, and it works with equipment from vendors other than Cisco.

There's a fine line between an ingeniously designed network and something that is overly complex. It takes experience to figure out where that line is. If it seems like you are doing something screwed up, you probably are.

No Single Tool and Layers (4, Insightful)

xanthan (83225) | more than 11 years ago | (#6355681)

For something that complex, no single tool will do it for you. That said, consider doing your documents in layers. Having a single document that includes all of the gory details of such a large network will be useless. Instead, do a document that describes the high level architecture, then open up each cloud into another document and describe the network topology there, then open up those clouds into documents that get into individual host level information. It is the only reliable way to grow the diagram as necessary and make it possible for others to understand what is going on at a glance.

Other Considerations (3, Insightful)

innosent (618233) | more than 11 years ago | (#6355805)

I generally use Visio for this sort of thing, but planning out a large network using an automated software tool is impossible, at least in my experience. If you can logically group your network at some level, you will find that it will make planning, and/or diagramming your network much easier. Even the largest networks are broken down into several groups at some level, and you have to keep those groups in mind. You should know the usage patterns of these groups, how much bandwidth each group needs, and where they connect to, etc. Logically map out the best performance scenario for these groups. Then start with your smallest groups, and find similarities to form larger groups, until you have encompassed the entire network. I'm assuming that there are probably departmental connections needed, as well as outside connections, but the key is how much each group of people use each resource available.
Many "well-planned" networks fail because they aimed to provide all resources evenly, but in the real-world, this is not the case. Most of the time, a certain group of people use specific resources, and use very little of other resources. Also keep in mind that you must be able to adapt if the resource requirements for a group change, because it will happen. It's the same thing as trying to use a database wizard to optimize your database. A computer just can't do that for you. The software doesn't have all the necessary input parameters to the problem, and even if it did, the problem is NP Hard. So, in reality, it doesn't matter what tool you use to diagram the network, but actual design still has to be done by human insight, or at least a well-trained monkey...

seriously (1)

yo5oy (549821) | more than 11 years ago | (#6355954)

how do you get to the level of designing an enterprise network without already having the experience and the toolkit to accomplish your tasks? it seems you already have the tools that most people use to design networks. i have only used visio myself for no more than a network that supports 300 users (law firm) and for a community college computer lab with a mixed platform, with vlans for experimental router subnets for cisco classes and for teaching advanced system adminstration and programming on linux. i learned to use visio and it was adequate. how do these tools fail to scale? maybe provide some examples of where you are having trouble instead of just asking for some other tool. thanks for reading.

Re:seriously (0)

Anonymous Coward | more than 11 years ago | (#6359676)

The point was to really just see if there is anything new out there that has come about that my be obscure - or maybe find something that is used that may not really be intended for network design but someone found a novel way to apply it.

thats why it was specifically stated that the tools were of the interest and not design methodoiolgies.

Cisco Network Designer (2, Informative)

dago (25724) | more than 11 years ago | (#6356292)

If you want to make design, why head to cisco configmaker instead of cisco network designer [cisco.com] ?

Internally, 3com used... (1)

PunkeyFunky (522484) | more than 11 years ago | (#6356524)

..nothing too complex.

As an ex-3Com employee, the network guys made extensive use of a whiteboard, followed by documenting what they'd done in Visio.

I doubt you'll get all information into one form of documentation; you'll most likely need various 'parts' of documentation.
This implies different tools for the job.

Surely a "real" engineer can pull all this together without the need for specific tools?

Use your HEAD (2, Informative)

noah_fense (593142) | more than 11 years ago | (#6357646)

First, use visio to design your CORE network. This would include all your high bandwidth, long haul fibre links. Choose a routing protocol (ISIS and OSPF are what most carriers use). If you want to implement newer protocols like MPLS, you still need OSPF or ISIS to run underneath it. Your core network should be layer three only. Avoid using ATM links becuase they add an extra "layer 2.5".

Then, off of each core router, drop gig-e links off to your layer 2/3 routers. If redundancy is a huge issue (which is probabally is), you will probabally have two core layer 3 routers (probably cicso, juniper) with a small number of ports, and two layer 2/3 routers (riverstone, foundry, extreme) with a large number of layer two ports at each major location with gig-e multimode links btween them to provide extra redundancy. Before you go and buy everything, spend time testing this four router configuration (see how long it takes to reroute traffic when links go down). This is especially important if you ever intend on implementing VoIP on your new network.

All critical systems (DNS servers, domain controllers, application servers, VoIP gateways, database servers) should be on the layer 2/3 routers, not on the smaller routers underneath that most "end users" will be connected to throughout each location. Essentially the layer 3 routers are just for core routing, and the layer 2/3 routers will provide most of your functionality.

Once you have everything up and running, use SNMP to monitor your links (most SNMP management software draws your network for you, and it will draw nice broken links when links go down). Good SNMP software will map every network device on you network, as long as you configure SNMP on all your new nodes. Also, make sure you have a really cool NOC (Network Operations Center) with lots of LCD projectors and linux/unix workstations. Make sure you have a good naming convention for all your network links and routers.

Don't deploy at 100% capactiy immediately, run at 10% capacity then work your way up.Many unforseen problems WILL come up (Routers have more bugs than you can imagine). In the end, you will probably have a nice buildingwide, statewide, nationwide, or worldwide modern next-generation (VoIP etc) capapable network.

-n

Re:Use your HEAD (0)

Anonymous Coward | more than 11 years ago | (#6360890)

Why bother?

Just give every user in your enterprise an 802.11 card, place a wireless nic in each server and run the whole network in add-hoc mode.

ATM and gigabit ethernet are for old-school l00sers, the return on investment for cabling cannot keep up with the speed and flexability of wireless, especiall when the wireless cards are well under $100... think about what one pull of ethernet costs, and the cable isn't upgradeable.

Re:You need to use YOUR head (0)

Anonymous Coward | more than 11 years ago | (#6389535)

How in the hell can you have a layer 3 only network? That comment makes no sense if you think about it, because if there is no physical or data link layer, what is the point of having a network layer?


The process is called encapsulation, and it must all work from layers 1-7 for any of it to work at all. Incidentally, ATM operates at L2. It is purely a switched protocol, defining L2.

complex network simulation? (1)

dousette (562546) | more than 11 years ago | (#6363087)

Along this line of thought, is there a product out there that is a full network simulator? Meaning, can I put routers A, B, and C in my diagram, with A linked to B, and A linked to C. Router A runs BGP between these two connections. Is there software out there to where I could put a simulated load on the router, then virtually "cut" one of the links to see what would happen and how it would affect the other link? What if one of the links' latency spiked? Using BGP with two links is a pretty easy example, but you get the idea. It would be a great teaching tool, as well.

Ideally, Cisco would make a tool like this, so you could tweak the virtual BGP (or MLPPP, OSPF, RIP, STP, etc) configs on the routers, but I haven't seen one on their site.

Design or Document? (1)

An anonymous Frank (559486) | more than 11 years ago | (#6363183)

Visio Enterprise has many a tool set that will both allow theoretical design and actual representation of a network and it's content. The whole thing is based on a database you can build from scratch or modify following an SNMP sweep of your devices. It does a fair job at keeping things contextual and allows you to consult your devices as objects with properties, rather than simply as icons on a piece of paper. No matter what, as complexity grows you will have to give up the convenience of paper as the main media of communication. I'm assuming that some sort of visual representaion is the goal here. Instead, if you are merely looking for a way to document your network for efficient access, and wish to minimize your upkeep, look into products such as Network Node Manager, which will regularly poll inventory information from supported SNMP nodes, or (for servers) IT Operations which will run local agents and gather similar info. There are plenty of rival products and I'm not pushing for HP here, but the most important thing to ask yourself is: how do you intend to use the information? (Rather than how will I gather it.)

Network design tools (0)

Anonymous Coward | more than 11 years ago | (#6379392)

Opnet is quite good for doing theoretical network designs, and showing what sort of loading is expected at any node.

It can also be linked up with other software to import the network layout from other tools. (I have done it from HP openview).

You people must be kidding (0)

Anonymous Coward | more than 11 years ago | (#6380538)

There are some absolutely crazy people in here trying to talk about things they know nothing about.

First off, you're on the right path with AutoCAD. People who run really large networks do a lot of work with CAD-based tools as opposed to "lower-end" solutions like Visio. I don't agree with one network engineer's statement who claims that you can do all your work with the routing tables and with show commands. That just isn't convenient in any of today's modern enterprises, particularly when "a picture conveys a thousand routes" - it takes a while to troubleshoot interactions involving multiple routers and to suggest even for a moment that you do it in your head is ludicrous. Furthermore, you are costing your organization an incredible amount of money in terms of the cost of bearing your knowledge as opposed to the ability to bring a new engineer's knowledge up to speed quickly.

For dynamic work, i'm doing a lot of generation with aiSee, SNMP, and to some degree, GraphViz. They are all excellent tools and allow me to quickly develop layouts using a number of methods. I do use AutoCAD for some of our larger diagrams, and Visio for some of the smaller networks we run, or when I need to one-off something for a business type to look at. AutoCAD has a number of features that make working with large diagrams easy.

ConfigMaker is indeed a terrible tool. The comment about NetViz was a valuable one; if you're trying to do highly data-driven design (you know what you have and you want it to be drawn), then NetViz is definitely your tool. For conceptual design, stick with AutoCAD.

A colleague and I have a book in progress about network operations and large-scale network design, including some significant talk about best practices.

seriours (1)

arkepp (604390) | more than 11 years ago | (#6387007)

disclaimer: I work for a national distributor of these products, but probably not in your area If you have a budget you can go for Physical Network Inventory or Logical Network Inventory by GE Network Solutions (formerly known as Smallworld), http://www.gepower.com/dhtml/network_solutions/en_ us/communication/physical_logicalnetwork.jsp/ These applications are used by some big telecom companies and model the network (physically and logically) down to single ports on switches. You can also have multiple people work on the same design, trace errors, check redundancy etc. It will probably read your autocad files too. A good chunk of the source code is included, but I believe these applications only run on Win32 at the moment (the underlying system also runs on Linux, Solaris and HPUX).

Re:serious software for modelling complex networks (1)

arkepp (604390) | more than 11 years ago | (#6387039)

eh.. accidently hit the return key while writing the heading ; )

LP (0)

Anonymous Coward | more than 11 years ago | (#6467925)

Important Stuff: Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)
Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>