| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Still no counter on Clearvisn 1.1a TFTP Server like the old TFTP
counter under HW for Windows. Customers like this ... prevents
them from yanking modules during firmware loads ... counter gives
them a warm and fuzzy feeling that firmware load is happening ...
the counter does'nt have to be exact ... even %'s would help.
-Charlie
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4276.1 | We need it! | PTOJJD::DANZAK | Pittsburgher � | Sat Mar 15 1997 10:58 | 4 |
I agree.....how DO you know what is happening and prevent yanking out
that module....arugh.
j
| |||||
| 4276.2 | That would be a good feature to have again... | NETCAD::BATTERSBY | Mon Mar 17 1997 10:09 | 14 | |
One method I use to check on a module's status, (after having
started a firmware upgrade on a specific module), is to try
to re-direct to it from the console terminal. If I'm not physically
connected to the HUB via a local console, and don't have an
OBM connection either to do the same, and if the module has an
IP address, I'll try to telnet to it or ping it periodically (this
of course assumes that I am upgrading from a "T" image to a "V"
image or from a "V" to newer "V" image.
Having suggested all the above ways to check on a modules upgrade
status, I too agree that the counter indicator being requested would
be most ideal, as it is easy to see the progress, and also takes
into account those modules which are upgraded via a MAM-assisted load.
Bob
| |||||