Conference netcad::hub_mgnt

3791.0. "Hubwatch V4.1 to clearVISN MCM Upgrade procedure" by CENPCS::BIRMINGHAM (Transporter Room - 1 to beam up...) Wed Aug 14 1996 15:18

    I couldn't find any discussion of upgrading procedures to go
    from HUBwatch V4.1.1 to clearVISN MultiChassis Manager V5.0, so
    I need to ask some questions.
    
    Customer Situation:
    
    1. Customer says modules in DH900/MS are all at latest revisions.
       Modules run well with H/Watch V4.1.1. I have not verified this.
       Cobfiguration includes two DC900-MX in Auto-healing configuration.
    
    2. Customer now needs to upgrade to allow using more that 4 front panel
       ports on the backplane when using FDDI ring. We have recommended
       upgrading to clearVSIN MCM. This may require updating firmware
       in DS900-EF, DC900-MX, or DR900-FP modules. I know that FLASH Loader
       component will handle this part and that the Consolidated Firmware kit 
       is on CD-ROM.
    
    3. Installation Manual for clearVISN MCM suggests that it can be
       installed as an upgrade over existing H/Watch V4.1.1 files and
       will preserve configuration.
    
    4. Customer is a city government data center, and due to problems with
       new Alpha systems is very sensitized to any extended downtime. Thus we
       have to have our act together to do this upgrade or advise customer
       on correct procedure.
    
    Question:
    
    1. Will upgrading a module or the DH900/MS MAM Using the FLASH Loader 
       erase current settings ( port connections, etc...) ?
    
    2. Will installing the MCM software preserve current configuration 
       information to allow a RESTORE operation to reconfigure upgraded 
       modules ? 
    
       (The H/Watch Management PC is on a DR90-T connection in the DH900/MS being 
        upgraded.)
    
    3. Should the customer write down all config data ( IP Addresses,
       community names, etc...) *before* starting firmware upgrade ?
    
    4. Can MCM RESTORE settings if Management PC is on Default T/W backbone
       segment or will I have to go in via the serial port with a terminal 
       to set initial settings ?
    
    
    I know it sounds like I'm a real dummy here ( Maybe I am... ;8^)   )
    but this is the first *upgrade* I have been involved with, and only the
    second DH900 installation I've worked on. I will be grateful for any
    suggestions, comments, and advice on how to get this done without
    downing the network permanently...
    
    Thanks,
    George

Hi George -

I can answer some hub parts of your questions.

First, the DEChub Multiswitch 900 Owner's Manual and the DEChub MS 900
release notes that accompany new version contain upgrade instructions.
The release notes in particular discuss issues such as auto-healing
during upgrade (disable it).

Owner's Manuals and release notes for each individual module you are
upgrading are also available on the net.

>    1. Will upgrading a module or the DH900/MS MAM Using the FLASH Loader 
>       erase current settings ( port connections, etc...) ?

For the DH900 MS, current settings will be preserved provided the
hub is version 3.0 or later.  Your customer should be fine.
    
>    3. Should the customer write down all config data ( IP Addresses,
>       community names, etc...) *before* starting firmware upgrade ?

Your customer should always have this written down!  Not only could
a user hit the "Reset to Factory Defaults" item by mistake, but the
hub is designed to erase its non-volatile data if it resets too often
in a short period of time ("thrash protection").

	Dotsie
    

George,

Let me try to answer questions 2 and 4.

Currently, MCM does not have any database. All the information it displays 
is obtained from the devices via SNMP. Therefore, upgrading from HUBwatch
to MCM does not affect module information.

One other product that would be useful to your customer is the
clearVISN/Recovery Manager. This product will backup and restore
settable SNMP data. Therefore, module and backplane configurations
set up through MCM can be saved. This is not only useful for
problems that may arise, but can be used for cloning hubs or
switching network configurations for different times of the day...

Hope this helps,

Steve

    Dotsie, and Steve,
    
    Thanks for the reply. Can I assume that the Recovery Manager is
    available automatically to current HubWatch/Windows users, or is
    this part an *extra* cost option that will require some sort of
    license ?
    
    
    Thanks,
    George

    Sorry to butt in, but...
    
    Recovery Manager is NOT free, unless you're a VMS customer who is being
    migrated to W95/NT.  see SPD 64.41, part number QB-4YJAA-SA for win
    3.1, list $495.  W95/NT is QB-4YJBA-SA, same price.  Upgrades are $99.
    
    Tom Herendeen
    NPB SE