Writing a network report

Excellent Reource on the subject,

Top Down Network Design by Priscilla Oppenheimer
http://www.topdownbook.com/


John Lockie
Here9s my advice
1. Monitor: use SNMP to gather A) interface bandwidth, B) CPU, and C)
interface errors. Check the manufacturer for MIB9s to do this. If setting
up SNMP is intimidating to you, contact Logic Monitor
http://www.logicmonitor.com who I happen to know, but I am sure there are
others that do this. Use 14 day trial if you don9t have funds or authority
to authorize.
2. Document: document your findings...how hard is this? When you see an
interface is at 90% utilization state it plainly, and then provide a
solution such as LACP. Include a task cost dollar value (and include buffer
room on the cost, don9t forget to consider labor, cabling, equipment,
warranty, SmartNET, etc.). It may be that management is not even asking you
for costs, in which case your job is 10x easier.
3. Summarize: reports that will go in front of executive eyeballs needs to
have 3executive summary2 (hence the term). Their time is valuable, so cut
to the chase on page 1 and leave the rest of the reading for the nerdy or
even 3doubting2 executives :)

That9s all you probably need to include. If you want to go crazy (like if
your switch network is going to cost you a million to upgrade) then it might
be wise to really dive in to vendor technologies, the differences between HP
and Cisco at L2 level, etc. Go nuts if you decide to do this, the more the
better - just don9t forget your executive summary, because some guys could
care less.

Some other advice I can give you, as a manager who reports to executives....
1. Keep yourself out of the equation, think for the business. By thinking
for the business interest you are in the long run thinking for your own.
2. Ask management the same question you asked us. 3What do you expect to
see included in this report2. You may be surprised. Every time I am given
a directive from executives I ask them, 3what you do expect to see2. There
is no shame in asking, and it9s actually dangerous not to ask. Sometimes
they want only a price, and other times they want the entire enchilada. My
points above assumed somewhere between those two....

One other thing....since you said 4500 series. Why not stackable 3700
series? :). Be careful here....while you are comparing old to new, you need
to know why you would do 1 new over another new. For example, it might be
obvious you need to upgrade switched network. But is it obvious why you
pick Catalyst over Procurve? A discriminating executive who knows even a
little (or lives next door to a VP for Procurve division!) could really
challenge you on this one. Here is a tip, simply look closely at things
like ISL over 802.1Q, and you may find that arguing for Cisco protocols is a
little more justified.

Good luck,
John