Restoring the Database from a Backup Without Affecting Service

Use this procedure to restore the database on an uncommissioned CMM without affecting service. This procedure first commissions the CMM and then restores the database.

It is primarily used for in-service replacement of a CMM in a chassis that has no active CMMs, such as in a system where the sole CMM in a single CMM chassis or both CMMs in a dual CMM chassis have failed.

This procedure does not affect service as long as the database being restored matches the existing service provisioning on the chassis.

Warning: Service modules are automatically warm reloaded as part of this procedure. Software-based features on the service module (such as PM collection, APSD, APR, FPSD) are disabled while a service module warm reloads.

Note: The backed-up configuration must be compatible with the software and chassis: A configuration database is specific to a software version. In order to restore a backed-up database onto a replacement CMM, you must ensure that the replacement CMM is running the same software version as the software version running when the backup was created. In releases lower than 4.2, a configuration database is also specific to a chassis. You can only restore a backed-up database to a replacement CMM on a chassis if the database was backed up from that chassis. You cannot restore a database to a CMM on a chassis if the database was backed up from another chassis. Starting with release 4.2, this restriction is relaxed. You can restore a backed-up database to any chassis of the same chassis type (BTI7801 to BTI7801, BTI7802 to BTI7802, BTI7814 to BTI7814).

Prerequisites

• If you are replacing a CMM in a chassis, see Replacing the CMM in a Single CMM System before starting this procedure.
• The configuration database that you want to restore is compatible with the chassis and with the software version on the CMM.
• The replacement CMM is uncommissioned for this chassis.

1. Seat the CMM into slot A. If your system has two CMMs, leave the other CMM unseated.
2. Log in locally to the CMM in slot A over the craft serial or craft Ethernet port.

   For information on how to do this, see Logging In to the CMM Craft Ethernet or Craft Serial Ports.

3. Enter setup mode. This is known as the commissioning shell.
   localhost console

   localhost login: admin 
   Password:  
   
   Shell Help: List of the commands you can use: 
   setup  - Commission the CMM 
   cli    - Open CLI interface to the system 
   reboot - Reboot the CMM 
   exit   - Logout  
   
   scm1:~$ setup  
   
   Welcome to the BTI 7800 Series - CMM Commissioning Application! 
   Note: This process commissions one CMM at a time. 
   Type 'help' or '?' for the list of the commands. Press '<Ctrl> + C' at 
   any time to exit. 
   (cmm-setup)$

4. To see the list of available commands, type help.

   Note: The commands in the commissioning shell should only be used on an uncommissioned system. Do not use the commissioning shell commands as a substitute for regular CLI commands.

5. Set the time zone.

   For example:

   (cmm-setup)$ settz

   Please identify a location so that time zone rules can be set 
   correctly. 
   Please select a continent or ocean.  
   1) Africa  
   2) Americas  
   3) Antarctica  
   4) Arctic Ocean  
   5) Asia  
   6) Atlantic Ocean  
   7) Australia  
   8) Europe  
   9) Indian Ocean 
   10) Pacific Ocean 
   11) none - I want to specify the time zone using the Posix TZ format. 
   #? 

   Follow the series of menu-driven options to set the time zone.

   Note: You must manually set the correct time zone, date, and time even if you use NTP servers. The BTI7800 requires a correct clock at all times, including the period prior to the establishment of NTP server connectivity. Use of NTP servers is recommended.

6. Set the date.

   For example:

   (cmm-setup)$ setdate

   Set the system date and confirm setting.  
   
   The current date is 2015-01-01. 
   Enter the new date (in the format YYYY-MM-DD): 2015-06-12 
   System Date will be set to 2015-06-12 
   Confirm (yes/no/abort): yes  
   
   System Date is set to 2015-06-12 

7. Set the time.

   For example:

   (cmm-setup)$ settime

   Set the system time and confirm setting.  
   
   The current time is 00:02:48, Timezone is America/New_York. 
   Enter the new time (in 24-hour format-- HH:MM:SS): 12:13:00 
   System time will be set to 12:13:00 
   Confirm (yes/no/abort): yes  
   
   System time is set to 12:13:00

8. Set up the networking parameters.

   Note: All parameters are required to be set for proper operation of the BTI7800.

   For example:

   (cmm-setup)$ commission

   Set the parameters required for initial, basic CMM setup and system 
   management, and confirm the settings.  
   
   Controller Id: 1  
   
   Note: The System Management (Shared), Individual CMM, and Default 
   Gateway IP Addresses must be in the same network.  
   
   Enter System Management (Shared) Address (a.b.c.d): 10.10.1.22  
   
   Enter Management Netmask (/N or a.b.c.d): 255.255.255.0  
   
   Enter Default Gateway Address (a.b.c.d): 10.10.1.1  
   
   Enter NTP Server address (a.b.c.d): 192.168.35.251  
   
   Enter DNS Server address (a.b.c.d): 10.10.1.1  
   
   You have entered following values: 
   Controller ID                            : 1 
   System Management (Shared) Address       : 10.10.1.22 
   Management Netmask                       : 255.255.255.0 
   Default Gateway Address                  : 10.10.1.1 
   NTP servers                              : 192.168.35.251 
   DNS servers                              : 10.10.1.1  
   
   Confirm (yes/no/abort): yes 
   
   Do you wish to reset the database to factory defaults? This will impact traffic.
   Confirm (yes/no):
   

9. Since you are restoring the database instead of setting it to factory defaults, type no.

   For example:

   Do you wish to reset the database to factory defaults? This will impact traffic.
   Confirm (yes/no): no
   
   No database restore to factory defaults will be performed. It is highly recommended that you perform a restorelocaldb or restoreremotedb operation immediately.
   
   The following values are set:
   Controller ID : 1
   System Management (Shared) Address : 10.10.1.22
   Management Netmask : 255.255.255.0
   Default Gateway Address : 10.10.1.1
   NTP servers : 192.168.35.251
   DNS servers : 10.10.1.1
   
   If you are going to restore a database as part of commissioning, do that next - otherwise, reboot for IP settings to take effect.

10. Restore the database.
    1. To restore the database from a backed-up configuration file stored at a remote location:

       For example:

       (cmm-setup)$ restoreremotedb

       Setting up for remote restore...
       
       Do you want to restore a remote database to this system? (yes/no)
       
       Warning: this will perform an automatic warm restart of the system.
       yes  
       Enter the URL for the remote database you wish to restore: 
       sftp://user@10.1.1.1/10.75.0.5_BTI7800v2.1.0_23151_20160309_205021.tar.gz 
       Value for 'password' (<string>):
       
       Do you want to keep local system name/mgmt address/gateway address/controller address after restore a remote database to this system? (yes/no)
       no 
       
       The system is going to warm reboot....
       
       
       Broadcast message from root@scm2 (console) (Mon Jul 31 13:43:55 2017):
       
       The system is going down for reboot NOW!
       

       This command finishes by performing an automatic warm reload of the CMM and all modules. The commissioning shell displays a set of log messages as the CMM reboots.

    2. To restore the CMM from a backed-up configuration file stored in local chassis storage:

       Note: This option is available only for the BTI7801.

       (cmm-setup)$ restorelocaldb

       Setting up for local restore... 
       Primary Backup Status: 
       Time: '2016-03-22 10:35:53' 
       Ver: '2.1.0-23464' 
       Chassis ID: '1' 
       Management Address: '10.1.203.13/10' 
       NTP: '172.25.0.61' 
       DNS: '172.25.0.61' 
       MD5: '5354691dde242a12863bbbd8b8cd43b5' 
       Size: 303602 
       Status: 'valid' 
       ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
       ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
       ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
       ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ   
       
       Secondary Backup Status: 
       Time: '2016-03-22 10:35:53' 
       Ver: '2.1.0-23464' 
       Chassis ID: '1' 
       Management Address: '10.1.203.13/10' 
       NTP: '172.25.0.61' 
       DNS: '172.25.0.61' 
       MD5: '5354691dde242a12863bbbd8b8cd43b5' 
       Size: 303602 
       Status: 'valid' 
       ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
       ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
       ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
       ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ  
       
       Do you want to restore the database from the local chassis? (yes/no)  
       Warning: This command will perform an automatic warm restart of the system. 
       yes 

       This command might take 15 minutes or more, and finishes by performing an automatic warm reload of the CMM and all modules.

11. You will be logged out as the CMM reboots. When you see the login prompt, log back in to the craft serial or craft Ethernet port and start the commissioning shell.
    localhost console

    localhost login: admin 
    Password:  
    
    Shell Help: List of the commands you can use: 
    setup  - Commission the CMM 
    cli    - Open CLI interface to the system 
    reboot - Reboot the CMM 
    exit   - Logout  
    
    scm1:~$ setup  
    
    Welcome to the BTI 7800 Series - CMM Commissioning Application! 
    Note: This process commissions one CMM at a time. 
    Type 'help' or '?' for the list of the commands. Press '<Ctrl> + C' at 
    any time to exit. 
    (cmm-setup)$

12. Reboot the CMM. This last reboot is required to ensure the CMMs and all service modules are synchronized.
    (cmm-setup)$ reboot

    Do you want this CMM to reboot? (yes/no) : yes  
    
    Broadcast message from root@scm1 (pts/0) (Fri Jun 12 12:41:37 2015):  
    
    The system is going down for reboot NOW! 

    The CMM in slot A reboots into the specified configuration and assumes the role of the active system controller module (SCM). Service modules are also rebooted. This might take several minutes. Proceed to the next step after the CMM finishes rebooting.

13. If you have a dual CMM system, seat the other CMM into slot B. The CMM in slot B will now synchronize with the CMM in slot A. This might take several minutes. When this is finished, the Active LED on the CMM in slot B turns green.
14. Log in to the CLI using the shared management IP address and verify that the CMMs are synchronized if applicable. For information on how to log in to the CLI, see Logging In to the CLI.

    The examples below have been edited to show only the relevant output.

    In a dual CMM system, the CMMs are synchronized when the HA Status is In Sync:

    bti7800# show system

    Active Controller         : cmm:1/A 
    Backup Controller         : cmm:1/B 
    HA Status                 : In Sync 

    In a single CMM system, only the active controller is listed:

    bti7800# show system

    Active Controller         : cmm:1/A 
    HA Status                 : Not Ready 

The chassis is now commissioned and the database restored.