I agree with George, telnet to the IP address is the way to go. If you're familiar with Cisco, Dell or HP switches it'll look similar. They did call a few things different stuff, the syntax was different as well,? Is your friend. If you have a specific question on how to do something I could take a shot at dusting the cobwebs off those memories.
Feel free to ask.The GUI never worked out that great for me.I would suggest attempting to explain MTBF to management.Also, you can score some used Cisco switches relatively cheap. That or grab an extra of the 3Com devices if they're available and make text file backups of your configs to paste in when one fails. Mr.Reagan wrote:I agree with George, telnet to the IP address is the way to go.
If you're familiar with Cisco, Dell or HP switches it'll look similar. They did call a few things different stuff, the syntax was different as well,? Is your friend. If you have a specific question on how to do something I could take a shot at dusting the cobwebs off those memories. Feel free to ask.The GUI never worked out that great for me.I would suggest attempting to explain MTBF to management.Also, you can score some used Cisco switches relatively cheap. That or grab an extra of the 3Com devices if they're available and make text file backups of your configs to paste in when one fails.Thanks for the reply!
I'm new to switches in general, that's why I was hoping for a GUI. I may be able to get some new switches through techsoup, I'll just have to skimp on my new server. If you're not trying to do anything super sophisticated you can maybe get away with the GUI.It wasn't as reliable for me. Say for example you'd change a port from one vlan to another, it wouldn't actually change the membership or it'd end up with the wrong tagging.If the GUI isn't turned on you can enable it via the command line.
Once it's on just go to your web browser and type in (where xxx.xxx.xxx.xxx is the IP of the switch you want to manage).Took a quick look, HP bought 3Com, they still have the command reference up.That looks overwhelming to me and I used to manage a hundred or so 3Com switches including the 3300's and 1100's.Kinda curious, how many of these have you got and what are you trying to do? If you don't have at least cat5 what have you got?
Mr.Reagan wrote:If you're not trying to do anything super sophisticated you can maybe get away with the GUI.It wasn't as reliable for me. Say for example you'd change a port from one vlan to another, it wouldn't actually change the membership or it'd end up with the wrong tagging.If the GUI isn't turned on you can enable it via the command line. Once it's on just go to your web browser and type in (where xxx.xxx.xxx.xxx is the IP of the switch you want to manage).Took a quick look, HP bought 3Com, they still have the command reference up.That looks overwhelming to me and I used to manage a hundred or so 3Com switches including the 3300's and 1100's.Kinda curious, how many of these have you got and what are you trying to do? If you don't have at least cat5 what have you got? Cat3?We have two 4200's and one 2816. Most of our cabling is cat5 for data and cat3 for phones.
I'm just wanting to get in there to see their configurations and if it'd be worthwhile to try anything fancy with them. I'm embarrassed to say, I don't even know their IP's.
Lol, no worries, you're moving in the right direction trying to get it sorted. You're also honest about it. That's respectable. Everyone has to start somewhere.If I recall correctly, you can push gigabit down cat5, you don't need cat5e. Think there may be a higher error rate over distances close to the 100 Meter limit or if you're really trying to utilize the full gigabit pipe for an extended period of time but I doubt you'll be doing that.You can probably get the IP for at least one by checking your default gateway. Typically that'll be the top level switch.
The other alternative is to get a DB9 serial cable and plug into the console port from a computer/laptop that also has a DB9 serial port or some sort of USB port replicator that has one. Can't recall if you need some kind of null modem adapter to go on one end of the cable??Another idea to determine the addresses would be to run nmap or something similar. Do a full scan on your ip scope and you'll likely get device signatures and IP addresses. GbE will work well on cat5 as long as your runs are under 100m, as Mr Reagan said.I don't know your budget but there is currently an HP switch on ebay for 124 USD that is much more capable than those 4200s. You don't need to go top shelf here, there are many capable switches on the secondary market.A serial cable is probably the quickest way to find out the info on the 3com switch.
I think you need a db9 female to female cross over cable to do the job. Since Win7 doesn't have hyperterm you can either use an XP system, transport the hyperterm stuff to Win7 or use putty in serial telnet mode to interface with the switch. Yes, definitely Hyperterminal - forgot to mention that! Find an xp/win2k install to run from or copy these files to a Win 7 box:C:Program FilesWindows NThypertrm.exeC:WINODWSsystem32hypertrm.dllC:WINODWSHelphypertrm.chmFound a link for an intro to configuring 3com switches that jogged some memory.There was no network documentation at all? Did the last guy leave on bad terms? Good luck with passwords.
It's definitely in your best interest to copy the configs off or install something new before they fail and everyone can't work. They'll expect a pretty quick resolution.
Ordering new devices and then configuring them isn't quick.Wow, I didn't realize those HP gigabit switches were so inexpensive. At that price I'd buy two of them - here is another for $135:If there are enough ports I'd set them up where I populated the top row of ports in the top one and the bottom row in the bottom one. Use identical port config, if one fails move the cables up or down as necessary.If you don't mind 100Mb, and don't need all the ports, you can get a couple of these WS-C3560-24PS-S cisco catalyst switches with POE at about the same price point. Might make sense if you want to put in some IP cameras, wireless access points or whatever in the future.You can pick up a couple gigabit SFP modules to link them up as well. Thank you Mr. Reagan and George1421, This is truly helpful and I appreciate it!Simple is the watchword, as my place of work is a non-profit and I'm the sole IT guy. I'm in the process of getting a new server as our old ones are Win 2k3 32 an 64 bit. Getting something that will last them for 5 to 7 years means a lot!
As my position is part time they've had some turn over, some not giving any notice, no there's no documentation and no DB9 crossover. I think I did figure out the IP's with nmap though for the 4200's anyway (our gateway is a sonicwall 2400). A web interface comes up looking for credentials, which I don't have. I may try the recover/recover thing to try and reset the passwords.If GB will work over cat5 on our 35 person network, then I'll reconsider getting a 48 and a 24 port gigaswitch! We'd talked about getting an IP phone system, but the wiring of course wouldn't be sufficient at cat5 for doing both data and phone. I really don't mind plunking down some (. Lknowlton wrote: We'd talked about getting an IP phone system, but the wiring of course wouldn't be sufficient at cat5 for doing both data and phone.This is not necessarily true.
3com Wireless Infrastructure Device Manager Software Droid
A VOIP call consumes 100Kb/s or less per call. Adding voip to your network will have almost 0 impact on a GbE network with only 35 users.
I would setup QoS on the switch just to ensure your users have near (POTS) line quality audio. One flat network will work just fine for a campus of this size.If you have the funds to go with a 2960s then go for it and don't look back. The cisco small business SG300 or SG500 series line is also good for a SMB install.Something else you might want to consider especially if you are considering voip is to go with a PoE switch to power the handsets. You can also go with a regular switch you will just need a power brick at each voip phone.If you purchase a stackable switch you could have one module as PoE and one module as non-PoE. The point is you can mix and match in the stack to your requirements.
Android Device Manager Find My Phone
The stacks do have a requirement is the stack member must be part of the same switch family.