T.R | Title | User | Personal Name | Date | Lines |
---|
3227.1 | FEENID::AP$ROOT:[000000] | PTOJJD::DANZAK | Pittsburgher � | Sat Feb 03 1996 17:49 | 18 |
| Try:
FEENIX::AP$ROOT:[RELEASE] (under the appropriate directory i.e. V21
etc.)
NOTE...be sure to be connected to the WIRED side of the LAN when
upgrading...(i.e. u can't upgrade if you're connected wireless)
Also note that if in a hub, the console port of the access point is
disabled - (a pain if in a 90)
use option 11 (module specific options) and download flash to upgrade
REgards,
j
p.s. it seems to timeout on a busy network...
|
3227.2 | | EDISTO::greene | Michael Greene | Sun Feb 04 1996 12:43 | 8 |
|
Also don't bother trying to use HUBloader -- there is no
HUBloader support in the AP image. Just use a TFTP server
(eg NetRider Loader V1.0 (aka HUBwatch's TFTP Server), or
NetRider Loader V1.1) and the AP image jon gave you the pointer to
earlier...
Michael
|
3227.3 | Right - just use the TFTP server part | PTOJJD::DANZAK | Pittsburgher � | Mon Feb 05 1996 18:16 | 11 |
| Mike - right...you just need the TFTP server part...(I tend to lump 'em
all together....)
Dennis -
You just need to put the image in the 'hubload' directory, the hardware
address of the AP etc., as if you were loading a DECserver etc..
|
3227.4 | ??? | CSC32::D_PERRIN | | Tue Apr 09 1996 11:31 | 3 |
| The v21.bin is not on gatekeeper. Should customers be able to get
this and upgrade the firmware themselves?
|
3227.5 | | CSC32::D_PERRIN | | Thu Apr 11 1996 13:14 | 3 |
| and the answer is: for customers, the firmware for these
modules is available at http://www.networks.digital.com.
|