A Simple Tool for Tracking Switch Ports? 84
jeremy cobert asks: "I work for a large school district in the Computer Networking department. We have several network closets at each school and each switch is set for different equipment on different VLAN's. Sometimes a Tech at a school will call in and need a printer plugged into a switch, and we are currently using maps drawn with PhotoShop to keep track of which ports are set for different equipment. I can look at a map and tell them to use a port that is already setup for printers. I am the only person who knows how to use Photoshop in our department and it is becoming way too time consuming every time someone switches a port. Here is an example of how we currently track our ports. Is there any program that we can use to make changes and diagrams in some similar fashion?"
We're doing this right now (Score:5, Insightful)
We're doing something similar at work so it's still fresh in my mind. First off: lose the Photoshop crud. Assuming your switches are managed or have at least some smarts in them I'd suggest using SNMP, $LANGUAGE and PHP to track your port information. Then any of your admins can access it via a webpage on your intranet. ($LANGUAGE can be anything but we like python and perl)
Consider replacing the hubs in your diagram with switches that have some smarts and SNMP. Not a crap LinkSys thing for $19 at BestBuy or whatever. A real, managed switch with a serial console port would be best IMHO.
Consider an "out of band" private network too. Something you can use to connect to another machine in the closets with a serial link to the switch console ports. That way if a switch/firewall/router stops talking you can remotely get to it via the console. We just received a bunch of old fibercopper media converters for this purpose (some of the runs are long)
You're there to manage the network, not just pretty up diagram in Photoshop, right?
Re:We're doing this right now (Score:3, Interesting)
At my $place_of_employment, we use the Fluke Optiview console. What it does is it polls every port and every device on every port. Then you can either dig down a list of hosts, printers, servers, etc - or you can have it print out a network diagram (using MS Visio) or give you a switch port printout, which lists what is on each switch - down to the IP, computer name, MAC address, you name it.
It only works with Layer 2, though - so you need remote endpoints on each of your routabl
Re:We're doing this right now (Score:1)
We have the Fluke Optiview stuff too. I don't know if it came cheaper because we bought a Fluke LAN meter (~$12K at the time) as well. Handy piece of software.
Re:We're doing this right now (Score:4, Insightful)
10/100 switches are extremely inexpensive nowadays; even managed switches with VLAN support. Buy some extra switches, run extra drops per VLAN, label the drops at each end and describe textually (in your *DF) which drop connects to which port. De-activate unused ports if you must and activate them on demand.
Re:We're doing this right now (Score:2)
To play devil's advocate, against both of us, I've been told on several occasions that the cost of rewiring space that has only one data drop per location was too high, and that I must find a solution with what I have. At that point, it was all about using a centralized SNMP management interface and managing the switch ports to be on certain VLANs and subnets.
Now if the original poster had said that they had no budg
Re:We're doing this right now (Score:1)
with SVG your perl scripts can also make basic diagrams. If you don't want to generate with SVG, try using Graphviz.
I've also had success using Visio 2000 and formatted text files to generate diagrams, but its very difficult to automate.
Whatever you are going to do, automate as much as possible. NetAdmins don't do P
Re:We're doing this right now (Score:2, Funny)
That should be in your sig.
Re:Don't forget (Score:2)
Re:We're doing this right now (Score:1)
Simple solution really (Score:5, Insightful)
Photoshop is the *wrong* tool (Score:5, Insightful)
For that matter graph paper, a ruler, and a pen would work equally well.
Re:Photoshop is the *wrong* tool (Score:2)
Re:Photoshop is the *wrong* tool (Score:2)
Re:Photoshop is the *wrong* tool (Score:2)
Re:Photoshop is the *wrong* tool (Score:2)
Or if you want something free, you could try "dia" or "kivio".
hrm? (Score:2)
Re:hrm? (Score:1)
I've also used CADKey 97 to create that type of thing as well.
Re:hrm? (Score:2)
Re:hrm? (Score:2)
But hey, this is slashdot linux == good, microsoft == evil right?
right?
Re:hrm? (Score:2)
But hey, this is slashdot. Reading the post
Spreadsheet? (Score:4, Insightful)
Re: (Score:2)
Re:Spreadsheet? (Score:2)
No. That's what VLAN does - a separate, virtual network using the same infrastructure.
One of the most basic (although not the coolest) functions of VLAN is to create two (or more) networks on the same switch - you can group ports on your switch so that the devices can't see or talk to each other (so if you want separate networks, there's no need to buy a separate switch for each one.)
Re:Spreadsheet? (Score:2)
(Taking the bait...)
So, what's the coolest function of VLAN, other than creating two broadcast domains on the same switch?
Re:Spreadsheet? (Score:1)
Re:Spreadsheet? (Score:2)
Also, why would you want your printers on a separate VLAN? (Serious question) I understand why you would want servers on different networks than the client devices.
I'm sorry for being incoherent. I'm a little slow today.
Re:Spreadsheet? (Score:2)
Re:Spreadsheet? (Score:2)
For starters, you want the printer to be as close to the users as possible. If your printers are in a different VLAN from the users, and the local switch isn't Layer-3 aware, you'll have to send all of the traffic from the local switch up to the distribution layer of the network (perhaps even higher, to where there is a Layer-3 device (a router)), so that it can be directed to the correct VLAN, and then sent back down the same trunk link back to the local switch.
You are saturatin
Re:Spreadsheet? (Score:2)
If your router supports trunking on its ethernet ports, you can do what's called "routing on a stick," creating logical channels off the physical router port, so the router can have a presence in each VLAN, though it only occupies on physical switch port.
You definately need a Layer-3 device to support inter-Vlan traffic. That's the point of VLANs.
Re:Spreadsheet? (Score:2)
Re:Spreadsheet? (Score:2)
Re:Spreadsheet? (Score:2)
I don't have a spreadsheet installed on my home computer, just a spreadsheet reader. At work it's different.
Re:Spreadsheet? (Score:2)
Re:Spreadsheet? (Score:3, Interesting)
We use a wiki. Switch ports are in a table on the wiki. Click on the machine name in the port assignment and it goes to the wiki page for the machine. Back and forth links. And the IP address table, firewall translations, etc. All on the wiki. Apache config notes? On the wiki. Docs for new users? Policies? On the wiki. Why have 15 different documents?
Re:Spreadsheet? (Score:2)
Re:Spreadsheet? (Score:1)
Re:Spreadsheet? (Score:2)
Pardon my ignorance.. (Score:5, Interesting)
Re:Pardon my ignorance.. (Score:3, Interesting)
Visio and Racktools (Score:1, Insightful)
Be warry though as I mostly use it to design racks for Pro-Audio Instalations. so it might not work that well. but for my needs its awsome.
Visio (Score:2, Informative)
Re:Visio (Score:1)
emacs (Score:1)
This can be as complicated or simple as you like. Diagram with ascii art or just a list of components. I prefer this to Visio. I keep mine on an internal web server with network config backups. Internal read only to the right people and I keep documentation updated.
My manager loves pretty pictures, I'll update the many colors on slow days when I don't feel like working, but I can lay out an ascii network diagram in minutes. A Visio diagram can
Legend (Score:1)
I really do think it's important to keep this type of documentation. So good on you for the initiative.
Kurt
Photoshop?! (Score:1)
A Wiki? (Score:1, Interesting)
photoshop is nice. (Score:5, Funny)
I do what you do, just not with photoshop (Score:2, Interesting)
I like to see how things are connected, what ports are in what blocks, what's wired to to what but my diagrams are simple boxes within boxes connected by lines with a simple ledgend. For what you are doing, you do not need to spend time drawing an exact replica of your 3com 3300 switches with color, the light display, the 3com label, etc. That's just a waste of time. I use open office for my diagrams. If you are using windows, ms paint should suffice.
Visio or Dia (Score:3, Informative)
Try this (Score:2)
GOOD FIND! (Score:2)
NetDisco (Score:3, Informative)
You want something like NetDisco [netdisco.org]. It will go out and discover every switch on your network and can figure out how they're interconnected. You can then query ports for VLAN, speed, and duplex settings, among other things. Finally, you can toggle ports on and off. It can even produce graphs of your network layout using GraphViz. You'll need a *nix box, Perl, Apache, and Postgresql, as well as managed switches that support SNMP.
If all of this scares you, then go out and buy Visio, but all you'll get out of that is pretty pictures.
Re:NetDisco (Score:2)
there are LOTS of network management tools out there. I realize HP Openview might be outside the budget of a school, but I've used it and it does exactly what you want. It will automatically colour code your ports to show you wants in use and whats not, which ports are having problems, etc.
There are a couple opensource replacements which I'm sure yo ucan find with google pretty easily.
If you've got good hardware (ie: something SNMP manageable) then you're set. If you're using home/small busines
Re:NetDisco (Score:1)
Re:NetDisco (Score:1)
seconded, BUT (Score:3, Insightful)
roll your own? (Score:2)
Today I'd probably consider using GraphViz (open source graph renderer that takes a simple text description and figures out the best layout), perhaps with a simple database backend to let you update the information over the Web and draw a new picture automatically.
I'm assuming you got the images of the hardware from the manufacturer's Web site; you could use the same images in GraphViz, with a littl
Re:roll your own? (Score:2)
If anyone has a link to an example or a patch or extension to graphviz for this I would appreciate it.
SVG or graphviz (Score:2)
MS Paint and Word (Score:2)
Its a shitty way to do stuff, but still better than using photoshop.
Eh? Copy, paste, print. (Score:1)
If you're using Cisco switches, just print the VLAN list [and comment the VLANs accordingly], and then the port list. Tape to racks as needed. It doesn't take a CCNA to match the number on the list to the number under the port.
Other brands should have similar cli admin mechanisms, which should allow for similar use.
Re:Eh? Copy, paste, print. (Score:1)
if you're going to do documentation... (Score:1)
Web UI (Score:2)
First, open your PSD in ImageReady (free with Photoshop) to divide the image in slices around the ports. Export the different port colors as rollover states. Also export the HTML as a template for your web programmer.
On the server side, the programmer need to make DB queries to figure out which port gets w
Re:Web UI (Score:2)
The data is centralized but easily accessible from remote locations.
Anm
graphviz (Score:3, Funny)
Re:graphviz (Score:2)
Oh, and you owe me a new keyboard!
--
I know what you're thinking, but I am not a nut-bag. -- Millroy the Magician
Dynamicaly assigned (VMPS, 802.1x) (Score:2)
So basically, once you have a db of all your network devices (hosts), you can configure a server to automatically assign the proper VLAN.
AFAIK, this is cisco proprietary, but an opensource server exists.
Another standard/open alternative would be to use 802.1x.
how about a good old fashioned text file? (Score:1)
it's 100% cross-platform.
it's substantially smaller than an image.
it's editable by anyone.
why not a text file?
heck, even an ASCII art text file:
| IDF4-Switch3 Dell PowerEdge 3024 |
| 1 3 5 7 9 11 13 15 17 19 21 23 g1 |
| 2 4 6 8 10 12 14 16 18 20 22 24 g2 |
Port Assignments:
1 --> VLAN1
2 --> VLAN2
3 --> VLAN1
...etcetera. a simple sed/awk/grep search would tell you what switches were ass