Re: Accessing CI of BayStack 350T switch via serial connection
Actually, it was a PEBKAC (Problem Exists Between Keyboard and Chair).
The serial cable I 'assumed' was straight thru wasn't. Minicom works
fine. (The electrons sure don't wiz around the ole' brain as fast as
they used to!)
Roger
On Sat, 2005-03-05 at 12:58, Tom Brown wrote:
> On Saturday 05 March 2005 06:10, Roger Ellison wrote:
> > I've been googling around and apparently my old brain can't solve
> > what should be a fairly easy problem. I've got a donated BayStack
> > 350T switch and need to access the Console Interface to setup the
> > switch. Accessing the CI thru a network connection isn't possible
> > without the switch's IP, which we don't have. (I'm running an nmap
> > ping sweep against the private address ranges to see if I get lucky,
> > but no joy so far). The switch's default IP is 0.0.0.0,; so,
> > resetting the switch to it's deaults doesn't do any good and can't be
> > done outside of the CI anyhow. I had hoped the switch was setup to
> > get it's IP over the network via BootP; so, I setup DHCP with the
> > switches MAC address, hoping to give the swtich a static IP on
> > powerup, but no luck there. (Can DHCP satisfy BootP requests?) So, a
> > proper serial cable is connected between the switches management port
> > and ttyS1 of the computer and the port is set to 9600,N,8,1. How do
> > I get a terminal emulator pointed at ttyS1, so I can send the switch
> > Ctrl-C to access the CI? I tried minicom, but apparently it wants to
> > use a modem, unless I'm missing something?
> >
> > Roger
>
> minicom should work. Did you go through the serial port setup?
>
> Tom
>
Reply to: