multicast, at best
You mean like a device where there is a stream that I can join and listen with others? Would be kind of neat if I didn't have to send out any data to join the stream though.
And am I the only person that sees radio as a public forum?
They don't tell you WHERE those switches physically are, though.
True, true. I find that, in the absence of a proper floor plan, a digital camera and a fire escape plan will do the job.
1) A physical network diagram is always step one. Don't worry about which port connects where, but do worry about which server connects to which switch.
2) Never underestimate the value of a spreadsheet documenting your subnets. List each subnet and all of the corresponding information (VLAN ID, which router serves as the gateway, description if for instance it's the Accounting department). Then do a sheet for each subnet and breakout all of the static IP addresses for each subnet (printers, switches, routers, servers, etc).
3) Make a list of all of your vendors, support accounts and logins, etc.
4) Go back, make a copy of the physical layout, then add services to all of the servers and try to document the general flow of traffic in/out/around the network (easier said than done, but priceless once it's on paper).
5) Then start documenting the systems and services. Start first with simple documentation. It's more valuable to have a little bit about everything than everything about a single server. Concentrate on documenting in detail the systems that make the least sense, like the one-off FTP server that's NAT'ed different from everything else because of the company that Marketing uses to do their graphics. Think of the ones that would be the hardest to troubleshoot when they quit working. Then move to the obvious.
Call a local VAR or small IT services company and get some outside assistance. Check their references to see if they do good documentation. A lot of them spend a lot of time doing complex project work for small IT departments so documentation generally precedes a good reputation. Management should sign off on it because it's an obvious decision. Despite what others may say, only rarely will they see it as an opportunity to bring in someone cheaper once the job is done because it shows that you're a "company" man.
Fixed that for you. Now what were you saying?
Real Users are afraid they'll break the machine -- but they're never afraid to break your face.