Setting Up a Multichassis System

Use this procedure to set up a multichassis system from two independent chassis. A multichassis system is managed as a single system, and consists of two chassis with their management planes connected together. The CMMs automatically detect that the management planes are connected together. Only minimal configuration is required.

Note: This procedure is service-affecting on the satellite chassis. Traffic will be affected. There is no rollback.

1. Back up the existing configuration and save a snapshot of the state on both chassis.
   1. Log in to the CLI of one of the chassis using the shared management IP address.
   2. Save the configuration database to a remote location.

      For example:

      bti7800# system database backup remote-url ftp://user@10.64.7.51

      Value for 'password' (<string>): *********** 
      bti7800# show system database  
      
      Backup Status 
      ------------- 
      
      CurrentStatus   : ready-to-backup 
      RemoteUrl       : ftp://user@10.64.7.51/10.1.220.104_BTI7800v1.6.0_18346_20150706_185955.tar.gz 
      NotificationMsg : Backup successful 

      Look for the Backup successful message in the output.

   3. Save the running configuration to a remote location.

      For example:

      bti7800# show running-config | nomore | save 10.1.220.104_running_config_20150706

      Value for 'password' (<string>): *********** 
      bti7800# copy file 10.1.220.104_running_config_20150706 remote-url ftp://user@10.64.7.51/10.1.220.104_running_config_20150706 
      Value for 'password' (<string>): 

   4. Save the state information to a remote location.

      For example:

      bti7800# show tech-support remote-url ftp://user@10.64.7.51

      Value for 'password' (<string>): 
      Searching Inventory..................................Done  
      Exploring data at Chassis:1 Collecting data from pld:1/2....Done 
      Collecting data from pld:1/5....Done Collecting data from pld:1/8....Done 
      Collecting data from pld:1/10....Done Collecting data from pld:1/11....Done 
      Collecting data from pld:1/13....Done Collecting data from cmm:1/A....Done 
      Creating archive..Done 
      Transferring file.... 
      10.1.220.104_chassis-1_tech-support_2015-07-06_19-30-32.tar.gz 
      transferred successfully! 

   5. Repeat for the second chassis.
2. Verify that the chassis you want to be the hub is ready for this procedure.
   1. Identify the chassis you want to be the hub and log in to its CLI using the shared management IP address.
   2. Ensure there are no outstanding CMM alarms on the hub chassis.

      Use the show conditions command to list the outstanding faults on the system. Resolve any outstanding CMM faults before proceeding.

   3. Check to see if a second chassis is already configured.

      You cannot configure a new multichassis system from an existing multichassis system. You must deprovision the existing multichassis system first.

      To check if a second chassis is already configured:

      bti7800# show system chassis

      Serial-Number     Chassis ID 
      ----------------  ---------- 
      2413CR-010        1 
      2413CR-020        2 

      In this example, there is already a second chassis provisioned (serial number 2413CR-020). Follow the procedure in Converting a Multichassis System Into Two Single Chassis to properly convert this existing multichassis system into a single chassis system, and then start this procedure again.

      If there is no second chassis provisioned, proceed to the next step.

3. Bring the chassis that you want to be the satellite back to an uncommissioned state.

   This step is performed by bringing each CMM in the chassis back to an uncommissioned state one at a time. The CMM that is not being worked on must be unseated. See Uncommissioning a CMM.

4. Unseat both CMMs in the chassis that you want to be the satellite.
5. Power-cycle the chassis that you want to be the satellite by unpowering and powering it back up.
6. Physically connect the two chassis together using Ethernet CAT5e UTP cables or better.
   1. Connect an Ethernet cable directly between the EXP-1 port on the CMM in slot A on the hub chassis and the EXP-1 port on the CMM in slot A on the satellite chassis.
   2. Connect an Ethernet cable directly between the EXP-1 port on the CMM in slot B on the hub chassis and the EXP-1 port on the CMM in slot B on the satellite chassis.

   Note: Connect the Ethernet cables directly. Do not use a switch or a hub.

7. Reseat the CMMs in the satellite chassis. Ensure the CMMs are completely seated and connected to the backplane.

   Once the satellite CMMs are seated, the satellite CMMs receive instructions over the inter-chassis links and assume the role of MRMs.

8. Assign a chassis identifier to the satellite chassis.
   1. Log in to the CLI using the shared management IP address.

      By doing this, you are logging in to the active SCM on the hub chassis.

   2. Make sure that the system has detected the presence of the satellite chassis.

      For example:

      bti7800# show system chassis

      Serial-Number     Chassis ID 
      ----------------  ---------- 
      2413CR-010        1 
      2413CR-011 

      Do not proceed to the next step until the satellite chassis appears in the output. In this example, the satellite chassis is identified by serial number 2413CR-011. Note that there is no chassis identifier associated with this chassis.

   3. Assign the chassis identifier. The chassis identifier for the satellite chassis must always be 2.

      For example:

      Note: Ensure that you enter the correct serial number in the command below. Double check before committing.

      bti7800# config

      bti7800(config)# system chassis 2413CR-011 chassis-id 2 
      bti7800(config-chassis-2413CR-011)# commit 
      Commit complete.

9. Verify that the satellite chassis is running the correct software and firmware.

   By assigning a chassis identifier to the satellite chassis, the SCM recognizes that it must now manage the satellite chassis, and proceeds to upgrade the software and firmware on all modules in the satellite chassis in order to bring them to the software level that is running on the hub chassis. It can take 15 minutes or longer for the system to be brought to the correct software and firmware level. Until this upgrade is complete, equipment in the satellite chassis will not be operationally up.

   Verify that the upgrade is complete by issuing the show system version, show system firmware, show inventory, and show equipment commands. You should see the correct software and firmware versions on all modules (except possibly the satellite CMM firmware, which might need to be upgraded manually), and you should see all equipment in inventory.

   Note: If the satellite CMMs require a firmware upgrade, you might need to do so manually. See Upgrading the CMM Firmware for information on how to do this.

10. Confirm that there are no new alarms caused by this procedure.

    Use the show conditions command to see the list of outstanding faults.

11. Back up the new multichassis configuration and save the current state. This is useful for future troubleshooting purposes.

    Use the system database backup remote-url and show tech-support remote-url commands.

The two single chassis systems have now become a multichassis system.