Console port access on 3c16671 Linkbuilder FMS II hub

[ToddTech]

We are trying to get into a mgmt module on a 3com Linkbuilder FMS II hub (3c1667) to change a few critical port settings. We've been trying to use the Serial Console port since we are not postive about the assigned IP of the unit, but cannot get any access. we've also used the 3com Network Supervisor software to "discover" a the device, but no luck either.

We've tried modem and null modem cables (confirmed test of null modem between 2 PC's and software OK). Latest test is with Kermit95 to be able to send a Ctrl-Break, but still no luck. With the Kermit95 it will only establish a connection with the Null modem attached -- with other cables (ie modem) or no cables it will just close the session indicating there is nothing to connect to.

We don't get any indication or reponse from the hub, not even gibberish (tried all the baud rates but aways used 8-n-1). Tried many Returns, Ctrl-C, Ctrl-Break etc, but nothing. This unit is the standard 24-port hub with the optional Mgmt modual slid in the back that has the serial console port on it. The closest documentation I can find on the optional mgmt module is:

http://support.3com.com/infodeli/tools/switches/s_stack2/3c16950/manual.b03/16950ub3.pdf

Which if for a little newer switch, but I figure is close to the same vintage.

Does anyone know about how to accomplish this or how to zap the existing settings to start fresh? Any help you can offer would be greatly apprciated.

 

[ImpetusEra]

I used to have a few of those. I was able to access them using a laplink style serial cable and hyperterminal with the settings of 9600 baud, 8-bits, no parity, 1 stop bit and hardware flow control. The old netbuilder routers behind the vent holes had a little momentary switch that would kick it to a service prompt which allowed you to reflash the firmware therefore removing any passwords and restoring the settings to defaults. I don't recall there being options on the hubs though to change the settings of the console port so it's either a cable or software issue I'd think.