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 On Jun 21, 2010, at 5:20 PM, Pavel Dimow wrote:
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 :)
On Mon, Jun 21, 2010 at 10:18 PM, Jens Link <lists@quux.de> wrote:
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 -- ------------------------------------------------------------------------- | Foelderichstr. 40 | 13595 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@guug.de | ------------------- | -------------------------------------------------------------------------