Wireless Networks Thread, Problems connecting to switch via serial in Technical; We've got a Managed switch which is currently acting as just a switch but 1 of the 2 uplink ports ...
7th December 2011, 01:31 PM #1
Problems connecting to switch via serial
We've got a Managed switch which is currently acting as just a switch but 1 of the 2 uplink ports is mated to an SFP port that isn't in use so I need to change it back to the copper port as currently it does work but only at 100Mbps, instead of 1000Mbps.
The Switch is an Allied Telesyn AT-8350GB the manual says its also got a web interface but without knowing the IP address I've no way of logging into that.
We got the switch second hand and I assume it was never restored to factory defaults.
So my question is how can I log into the switch to configure it? I've tried via serial using various telnet programs and using the settings from the manual.
But the programs just appear to connect but I don't get any login screen, just a flashing "I" bar.
We also have an AT-8326GB with the same problem.
IDG Tech News
7th December 2011, 01:39 PM #2
Use Hyperterminal: COM1,19200,8,n,1 is usually the norm.
Tried pressing enter a couple of times after it connects to get the username/password prompt?
7th December 2011, 01:47 PM #3
ive found sometimes i need to reboot switches with serial lead connected to get into them
7th December 2011, 01:52 PM #4
Tried pressing Enter as I've read that could help but it doesnt. Also tried the 19200 baud speed, it wants 9800 though.
Rebooting doesn't help either.
I've tried Hyperterminal, LogmeTT and SecureCRT
Last edited by Gaz; 7th December 2011 at 01:54 PM.
7th December 2011, 01:56 PM #5
are youusing the right type of serial lead straight or null?
7th December 2011, 02:00 PM #6
I assume I am. The serial cable came with a Cisco SG300-52 switch but I assume it would work.
Is there anyway to tell the difference between the two types? The connectors on both ends of the cable are female.
7th December 2011, 02:06 PM #7
multimeter and check pin 1 goes to pin 1 and so on
Originally Posted by Gaz
7th December 2011, 02:08 PM #8
It could be the cable: we have some 3com switches which will ONLY talk via their own serial cables; it's possible others are the same I guess.
7th December 2011, 02:09 PM #9
Bah, I left my multimeter in my car which is in the garage and the ones we have here are crap and the probes are probably to big to insert, I shall try never the less and report back.
7th December 2011, 02:13 PM #10
cheat connect the probes to some bent paper clips dosent need to be a good multimeter you could even probably get away with a battery and an led
Originally Posted by Gaz
7th December 2011, 02:22 PM #11
Managed to find some decent probes in the electronics lab. It appears to be a straight cable as all the pins matched their corrisponding numbers.
Does this mean I need a (ethernet crossover equivelent) cable? If its not working with this straight cable.
7th December 2011, 02:24 PM #12
possibly some switches want one some t'other its been a while since ive used allied telesyn kit and i just cant remember
Originally Posted by Gaz
7th December 2011, 02:27 PM #13
I just assumed as the cable came with a Cisco switch (brand new) that it would be the same technology accross the board.
I'll buy a crossover type and see if that has any effect.
Cheers for the help.
9th December 2011, 10:07 AM #14
Worked like a charm. I can only assume that newer Cisco switches require a straight cable instead of a crossover cable.
9th December 2011, 01:42 PM #15
- Rep Power
OK, I've just downloaded the manual and had a quick look.
Page 78 says that you need a null modem cable - this is the "moral equivalent of an ethernet cross-over cable" that you mention. You should be able to buy one, or an adaptor, from Maplins.
Page 79 says that you need to set your terminal emulation program to:
‰ Baud rate: 9600
‰ Data bits: 8
‰ Parity: None
‰ Stop bits: 1
‰ Flow control: None
IIRC this is the default for Hyperterm, though maybe you would need to turn flow control off. These days I tend to use putty.exe (http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe) as my terminal emulator, as well as for ssh.
You are correct - pressing Enter can "wake up" a serial connection. This is sometimes because the device can do auto-baud-rate recognition, based on the bit pattern of an ASCII Enter sequence, but I should stick to 9600 initially nonetheless.
By russdev in forum Scripts
Last Post: 9th December 2010, 10:10 PM
By Andie in forum Wireless Networks
Last Post: 6th October 2008, 01:13 PM
By Geoff in forum Wireless Networks
Last Post: 17th May 2007, 02:12 PM
By k1r5tymm in forum Hardware
Last Post: 8th February 2007, 11:30 PM
Last Post: 17th February 2006, 04:49 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)