Conference netcad::hub_mgnt

> is there anyone who can help me?

  I'd be the person;  I wrote the Recovery Manager script that performs 
  backup & restore operations of the hub900.




> i'm playing arround with the recovery manager of clearvisn because i have to 
> upgrade 22 HUB's on customer side. my demo-hub has the following config:
>   slot 4: decswitch 900ee
>   slot 5: portswitch 900fp
>   slot 6: concentrator 900mx
>   slot 7: portswitch 900tp
>   slot 8: decswitch 900ef
> all modules have the newest firmware revision. the fddi on 900ef is 
> configured port b to backplane, the concentrator is configred with port a to
> backplane.  the back-up operation of the hub-configuration works without any
> error.  the restore operation stops with the following error:
> 
> -----------------start of logfile-------------------------------------
> 
> --- Start of restore script: DEChub 900 Manager ---
>     Restoring backplane configuration (LAN interconnect): 
>         Setting FDDI Auto-Healing DISABLED... OK
>         Verify current and saved hub populations match... OK
>         Reading tables from SDF... OK
>         Reading tables from device: 
>             Reading Port table... OK
>             Reading Port Subtype table... OK
>             Reading Ligo table... OK
>             Reading Ligo Subtype table... OK
>             Reading Ligo Label table... OK
>         Translating Port & Ligo table indices: 
>             Translating Port table indices... OK
>             Translating PortSubtype table indices... OK
>             Translating Ligo table indices... OK
>             Translating LigoSubtype table indices... ERROR...
>  No translation between sdf & dev LigoSubtypeTable: no match. 
>     Restore script status: FAILED 
> --- End of restore script: DEChub 900 Manager ---
> 
> 
> ---------------------------end of logfile----------------------------


  First, let me emphasize that for the hub900, all error checking is done
  during the restore operation.  There are very few errors possible on a
  hub900 backup operation.  To have the fullest confidence in your backup,
  you should immediately perform a restore operation to the same hub.

  What this error is pointing to is that the the hub900 restore script 
  cannot correlate your saved cofiguration with the configuration of the hub
  which you are trying to restore to.

  The most common explanation for such trouble would be that a module was
    - inserted or removed
    - powering-up or powering-down
  while either the backup or restore operation was in progress.  Note that
  some modules take a minute or more to come up, so you should not start a
  backup or restore within a minute or two of module or hub power-up or 
  module insertion.

  If no modules were inserted or removed just prior to the backup or restore,
  another possibility is that your demo hub, while working, is corrupted.
  I would suggest a "reset with current settings" on the hub, and then re-try
  both the backup and the restore operations.

  If this fails, let me know.  There are other things to try, but I might need
  some data from you before we loose this configuration.
                                                               Carl Mower.
                                                               clearVISN

    Hi Carl,
    thank's for your quick response. this morning i tried the
    backup/restore again, and i wrote down every step i made.
    
    1. start of clearVisn MultiChassis Manager
    2. start of clearVisn Recovery Manager
       - select Backup
       - select Backup from : 16.185.160.221
       - select Community-Window and  click on "show" buttom
       -- clearVisn starts getting Agent-Information
       -- all hub-items appear in the window "Select items to backup"
       - click on "select all" Buttom
       - select "Save File" window and click on "Browse" buttom
       -- filename -> test_bck
       -- filtype  -> saved data (*.sdf)
       -- click on "save" Buttom
       - select "Log File" window and click on "Browse" buttom
       -- filename -> test_bck
       -- filetype -> Log File (*.log)
       -- click on save
       - select perform backup
       - click "Apply" buttom to start backup
    
     the clearVisn Recovery Manager say saving Data
     there are no errors reported in the status window
     finaly the operation status say SUCCESS
    
     3. Quit the Status window by click on cancel buttom
    
     4. Quit the Backup window by click on cancel buttom
    
     I left the HUB as he is. No restart, no changes.
    
     5. I start the clearVisn Recovery Manager Restore
    
        - slect "Restore to" window 
        -- restore to 16.185.160.221 ( the same HUB )
        - select "Community" window and click on "show" buttom
        - select "Save File" window and click on "Browse" buttom
        -- select backup file -> test_bck.sdf
        -- click on "open" buttom
        - select " Select Item to restore" window and click on "Select all"
        - select "Log File" window click on "Browse" buttom
        -- Filename -> test_res.log
        - select Perform restore
        - click on "Apply" buttom to start restore operation
        - the clearVisn Recovery Manager say "Restoring Data"
        
        in the Status window is the same error reported as i send in the
        initial note-entry.
    
    
        probably this will help you to find areason for the error.
    
    
        i have two anothe Questions:
    
        1. can you give me an explanation on things arround the LIGO Table or
        can you tell me where i can get some informations
    
        2. can i do with the option "save to command file"
    
    probably it will help you if i send you the errorlog file or the config
    file. Please let me know if i should do so. 
    
    thanks and regards Volker Stichternath, Cologne
    
       
    
     
     
      
       

 Volker,
   Thanks for detailing the steps you followed.

>  probably this will help you to find areason for the error.

   Unfortunately, no.  By listing the steps you followed, you have ruled-out
   some possible explanations, (such as modules coming-up/down during the
   backup or restore), but I do not yet know what is causing the problem.

   While it would still be useful for you to try resetting the MAM with
   current settings and trying the backup and restore again, I think I'd
   rather get more data first, if you don't mind.

   If you would be so kind, please follow these steps to get more a more
   detailed log file for me to analyze:

   1. Go to the directory where Recovery Manager has been installed;
      (if you don't know where this is, just do a search of your entire
       hard drive for the file "hub900.hbr" - you probably will only find
       one on the entire machine).

   2. Copy hub900.hbr to hub900.sav

   3. Edit hub900.hbr;  search for the 1st occurance of "ffffffff";
      that section of the file should look like:

      +-------
      |      :
      | #  ASSIGN  PRT = 0xffffffff;   # use this to see all detail possible
      |    ASSIGN  PRT = 0;            # use this in shipping version
      |      :
      +-------

   4. "#" is a comment character in this language;  all characters on the line
      after the "#" are ignored.  Remove the "#" from the first of the above 2
      lines, and add a "#" to the second line.  Save the file and exit the 
      editor.

   5. Invoke Recovery Manager, (it must not be running when you edit hub900.hbr
      above).  Re-run the backup and restore operations.  make sure to send the
      status output to log files, (different files for the backup and restore
      please).  The status window, and the log files, will be loaded with
      literally 1000's of lines of status which will tell me exactly what is
      happening.  Because of the large amount of status output, the backup and
      restore operations will take much, much longer;  please be patient.
      Please Email these 2 log files to me at NETCAD::MOWER.

   6. Rename hub900.sav to hub900.hbr


    
    
   As for your other questions:

>  1. can you give me an explanation on things arround the LIGO Table or
>     can you tell me where i can get some informations

   There are 8 MIB tables that clearVISN applications use to read or modify
   backplane connectivity.  Three of those 8 tables express information about 
   "LIGOs".  LIGOs are the choices you make for a bridge/switch as to if an
   Ethernet port is on the "front" or "back" of the bridge/switch;  LIGOs are
   also the choice you make for a bridge/switch or FDDI concentrator as to if
   you want, (in the form front/back):
      "AB/-" (A&B on front, nothing on back),
      "A/B"  (A on front, B on backplane),
      "B/A"
      "-/AB"
      "AB/M"
      "MS/-"
      "M/S"
      "S/M"
      "-/MS"
   These choices are made by selecting a slot in the MCM LAN interconnect
   window, and hitting the "config" button, which leads to the "station
   configuration" window.



>  2. can i do with the option "save to command file"

   This option is used to make a command file which contains one or more
   backup and/or restore operations;  once you have created such a command
   file, you can cause this command file to run at a later time using NT's
   batch-job scheduling features.  (More details on this can be found in
   this notesfile, and in the Recovery Manager documentation).  I'll leave
   any further questions on command files to someone more knowledgeble.


   Thanks for helping us track-down this problem.
   Carl.

 From John Gillis @Carl's workstation...

> >  2. can i do with the option "save to command file"
> 
>    This option is used to make a command file which contains one or more
>    backup and/or restore operations;  once you have created such a command
>    file, you can cause this command file to run at a later time using NT's
>    batch-job scheduling features.  (More details on this can be found in
>    this notesfile, and in the Recovery Manager documentation).  I'll leave
>    any further questions on command files to someone more knowledgeble.



Recovery Manager Command Files
------------------------------

The "save to Command File" dialog allows one to save the current Backup/Restore 
job to a file (represented in command file syntax) to be run in batch mode.

Note that command files are built through the GUI only; we supply the command
file syntax to the customer in unsupported documentation files on the kit,
but we don't support building of command files outside of the GUI.

Furthermore, the "save to Command File" dialog has a radiobutton prompting
the user to Append or Overwrite the selected command file name with the
command file data for the current Backup/Restore job .... this allows the
user to build suites of command files that execute multiple Backup and/or
Restore jobs. 

One can execute Recovery Manager command files through the GUI's command file
button on the Main window, or run the command file directly in a DOS
window. The latter gives the ability to run a batch file using Windows NT's



Schedule service.
-----------------

One consequence of the above: a network manager has to initially Backup/Restore 
each hub in his network manually through the GUI; if at the same time,
however, he also saves/appends each job to a suite of command files by selecting
the Save to Command File checkbox on the Backup/Restore window, he can at a
later time automate the Backup/Restore process for all hubs in the network.

Suites of command files can be built to Restore a group of hubs with
one set of configuration data for evening use, and another for daily use,
for example.
 
Editing of command files is also possible through the GUI's command file
button on the Main window.



For more info, check the product docs, or use the online help pointer
Release Information->General Recovery Manager Issues->
Scheduling Recovery Manager Batch Jobs on Windows NT and
Automatic Network Configuration with Recovery Manager

John Gillis ([email protected]  netcad::gillis)

    Hi Carl,
    first of all, thanks for all the informations and for the support. Im
    sorry, but i was not in the office for several days and this way i was
    unable to read your reply. 
    Now i am back in the office and i did all the steps again i did several
    times before to get the configuration restored. i dont believe what i
    saw, probably i am crazy or i had some problems with my fingers. This
    time the restore operation finished succesfully.
    I realy was not drunken when i did the restore before, but now i think
    i need some drinks...
    
    cheers 
    Volker