Conference netcad::hub_mgnt

Charlie,

There are two sections of code in the MS624T: the boot block
and the main block (operational firmware). The boot block
contains the primitive loader, the segment of code which
handles downline upgrades. When you are loading the new
firmware from the web, you are upgrading only the main block.

So, if the main block gets hosed somehow (bad load,
crc check failure,...), the module will revert to a state
in the boot block we call "needsProgramLoad". This is the
state I think your module is in. When in this state, the
module can do nothing but wait for an initiation of a DLU.

(If the module is in a DEChub900, the LCD display will
 show this state. If in a stack, a show current settings
 of the stack director should show status of all the modules
 in the stack.)

We believe the firmware image off of the web to be good
(the .bin file should be of size 497664 bytes), and I
assume that you have it saved on your tftp server.

Try the following:

1. [Obviously], make sure there is network connectivity
   to your hub/stack (either OBM or In-Band through
   another module), and that an IP address has been
   assigned. These can be set through the console
   "Config IP" selection.
2. Using the console of the hub/stack (do not redirect to
   the module), select the option for "Downline Upgrade"
   (press return to continue).
3. Enter in the slot in which the MS624T is in.
4. Enter the filename of the image which exists on
   your tftp server (dlmr2110.bin or whatever you
   saved it as).
5. Enter the ip address of your tftp server.
6. Hit return and it may or may not prompt you for
   the channel through which to perform the load
   (either the OBM port or through another module
   in the hub/stack). Select the appropriate one.
7. After hiting return I think once more, the console
   should say something like "DLU Process Started"
   and then start printing out a bunch of dots on screen.
   (The MS624T leds should also be indicative of the loading
   process by jumping between something like the 2nd and
   fourth leds). In any case the load should last about
   5-7 minutes, or two and a half lines of dots on the
   console screen.
8. Feel free to call me or send email with any questions.
     Nilesh Gandhi    DTN 226-6252  (508-486-6252)
     NETCAD::GANDHI   LAB 226-5190  (508-486-5190)
[Posted by WWW Notes gateway]

    Thanks for your quick response ... but I think I may have confused
    matters ... My concern is as follows: most SEs as well as most
    customers firmware upgrade hub modules/backplanes using either the 
    COMET BOOTP or Rtr Mgr TFTP Server along with Clearvisn Flash Loader...
    using the console downline load method is not always the "best" due
    to the availability of or connection to console port. 
    
    what i attempted to do ... was upgrade an MS624T in a Stack Director
    using the Comet BOOTP and Flash Loader . The MS624T was running v1.0
    ... I started COMET BOOTP ... started Flash Loader V1.3A ...
    entered the IP address of the Stack Director ... clicked on HUB
    managed button... picked slot #1 ...clicked on the SHOW button...
    verified that v1.0 was installed on the MS624T... entered the following
    in the load file location the following
    c:\clearvis\firmware\dlmr211.bin and pushed the load button ... off it
    went ... the Comet Bootp window indicated something about block 5 error
    .... then indicated that the load was complete... I waited a good 5+
    minutes ... and kept trying to redirect to that via the console ... 
    but the MS624T ... never came back (out to lunch) (perhaps based on
    your message I got a little impatient). Finally after several more 
    minutes gave it the famous yank the power cord salute ... it came back
    after the power cycle but was still running v1.0 ... so i said to
    myself maybe the v1.1 that I pulled off the web is bad ... let's try to
    load it with v1.0 again ... Comet BOOTP indicated everything was ok ...
    but module never came back ... stayed in weird state where the Leds on
    (2) ports flash at intervals ... could not be redirected to from
    console ... I waited about 5+ minutes ... and then power cycled the
    device ... again it would'nt come back... 
    
    I am the first to admit that I don't read the documentation very well 
    ... sometimes not at all ... but if the COMET BOOTP Server or RTR Mgr
    TFTP Server cannot be used along Flash Loader to upgrade these modules
    ... it is important to know this ... maybe i grew impatient ... I never 
    thought that a repeater would take 5-7 minutes to upgrade ... DS900EFs
    hub assisted loads only take 7-8 minutes... Paul in the TAC center was
    also able to duplicate this ... 
    
    Perhaps
    I am the one who is "out to lunch"
    Thanks for your help 
    -Charlie 

Hi,

I checked the MS624T image off the web and it seems to be ok.
(Downloaded it off the web, and "diffed" the .bin file
 with another local copy of the image and found no difference.
 Also, went on to load the image using Flash Loader, and it
 loaded ok.) Perhaps the error you saw may have been due to
 heavy network traffic?

Also, I guess I didn't realize so much that most SEs and customers
would use Flash Loader vs. a console to do stuff, though as I think
about it that makes sense (though for us here in the lab it's opposite).

But anyway, I was thinking for your deadline, and for the quantity
of modules you need to upgrade (67!), it might be better for you to
use the console (since you have it) because then you can kick-off loads
of more than one MS624T at a time, while Flash Loader is expected to
support this in an upcoming release (confirmed by Erin of the Flash
Loader team).

Oh yeah, also, the MS624T is also loaded via the hub ("hub assisted"),
so it should take longer than some of the older repeaters to load.

Good luck,
Hmm, it's half past noon,
time for me to go "out to lunch"...
Nilesh

[Posted by WWW Notes gateway]