Hi,
I am wondering what tools you consider most valuable when designing
big network from scratch or
perform a migration? For example I would like to know is there a tool
that will perform basic sanity checks
like network equipment without redundant link or without link at all...
I know that the one who design a network have to consider all this
issues but some automatic check will
save some time for sure...
Thank you.
Pavel Dimow <paveldimow@gmail.com> writes:
Hi,
I am wondering what tools you consider most valuable when designing big
network from scratch or perform a migration?
White board and a digital camera to document the drawings. Pen and paper
are also a very important tool.
For example I would like to know is there a tool that will perform
basic sanity checks like network equipment without redundant link or
without link at all...
Well there is my head and a couple of years experience. 
I know that the one who design a network have to consider all this
issues but some automatic check will save some time for sure...
Discuss your design with others. There is always more than one way to
design a network.
Jens
And how do you feel when client tell you that you don't have a
connection from SW-476 to SW-145?
"Well you see, there are plenty of boxes out there (couple hundreds)
you don't expect that everything must be perfect right? Anyhow I was
very tired that day...."
The point is, I am not looking for a program that will design the
network instead of me, just a little sanity check.
I agree that head, whiteboard, marker, sharp pencil 
are very
valuable but those were on my list anyway
Paul,
My biggest tool is a couple extra sets of eyes. A fresh look from the outside by someone else is going to be the biggest help. Pen and Paper (or Visio w/ Icons http://packetlife.net/media/library/33/Cisco_Marketing_Icons.zip)
I personally like using network simulators to try out different ideas. I'm a fan of packet tracer for those who have been through the Cisco Academy. The config options aren't *too* extensive, but the basics are there to help with a few sanity checks.
Garret
Everything should be documented and designed before its deployed. It should be reviewed by others.
Then it should be tested. Its hard to make it past the testing phase and still have these issues.
If your using a flawed deployment strategy, like many people do, where your skipping design, documentation or testing and just throwing things in, there will always be issues, even with fancy programs.
Brian
There was a lightning talk on Netdot at Nanog 48 I'd take a look at the presentation and the the website. It's quite useful from the documentation and discovery standpoint
After the initial whit board I generally sit down and document what we're going to build then we build a transition plan the covers the activities based on the docs and move on from there.
Joel's iPad
There was a lightning talk on Netdot at Nanog 48 I'd take a look at the presentation and the the website. It's quite useful from the documentation and discovery standpoint
meh, it was nanog 49, and the link is: