Solving Problems With Quick Config Manager - 3Com PS Hub 40 User Manual

Solving Problems
With Quick Config
Manager
DUA1640-5AAA02
2 Specify the IP address of the TFTP server that has the upgrade file on it.
3 Specify the file name.
Do not enter a path. The upgrade file must be in the appropriate
directory on the TFTP server that the server has been configured to look
in.
The file name format is:
PS Hub 40 software upgrade —
PS Hub 50 software upgrade —
Where xx_yy is the version of agent software. You can specify multiple
file names (separated by spaces), to upgrade PS Hub 40 and
PS Hub 50 units in the stack at the same time, for example:
psh02_00.bin psf02_00.bin
4 Click OK.
You cannot access the hub over a serial connection for the first
time. There may be a number of reasons for this:
For a successful local management connection, you need to use a
standard null modem cable, and have the hub's console port set to
9600 baud or auto-configuration enabled. These are the default
settings. For information on the console port settings, refer to
"Changing the Console Port Settings" on page B-27.
It may be that you have made your management connection to a
serial port, on your management station, which is not the port
Quick Config Manager is using. Quick Config Manager uses COM1
as the default serial port. For information on changing this, refer to
"Running Quick Config Manager" on page B-4.
When using Quick Config Manager with Windows '95 and
managing through the console port, you must first disable FIFO
buffers in the Advanced Port Settings window in Windows '95.
For information on doing this, refer to "Through the Console Port"
on page 5-13.
There may be another application running on your management
station, that is using the management station's serial (COM) port,
for example HyperTerminal.

Solving Problems With Quick Config Manager

xx_yy
psh .bin
xx_yy
psf .bin
B-29