• Supported Platforms
• T640 Routers, TX Matrix Routers

• Related Topics
• Overview of Converting a T640 Router
• TX Matrix Software and CLI Overview

Creating a Configuration File on the T640 Router for Integration into the Routing Matrix

Using the current T640 router configuration, create a configuration file on the T640 router that will be merged into the TX Matrix router configuration:

1. Save the T640 router configuration. For example:
   
   

   user@host# save t640-config.conf
2. As described in Configuration Groups, special configuration groups re0 and re1 apply to the Routing Engines in slots 0 and 1 of the TX Matrix router. If the T640 router configuration contains these groups, you must change them to lcclcc-number-re0 and lcclcc-number-re1, where lcc-number equals the chassis ID of the router.
3. If the configuration includes special Routing Engine configuration groups, include the apply-groups statement at the [edit] hierarchy level. For example:
   apply-groups [ lcc0-re0 lcc0-re1 ]
4. Change the configuration hierarchy of all statements at the [edit chassis fpc slot-number] hierarchy level to the [edit chassis lcc lcc-number fpc slot-number] hierarchy level.
5. If the chassis ID of the T640 router is 0, you do not need to change interface names or the configuration hierarchy of any other statements. Otherwise, you must modify the FPC number throughout the configuration based on the chassis ID you select. For more information, see TX Matrix Interface Names Overview.
6. Save the modified T640 router configuration using a different filename from the one you selected in Step 1. For example:
   
   

   user@host# save tx-config.conf

   Note: Do not commit the configuration.

7. Transfer the modified T640 router configuration to the TX Matrix router. You can use an intermediate server on the out-of-band management network accessible by both the T640 router and the TX Matrix router.
8. On an external management device connected to the console or auxiliary port of the TX-CIP, load the configuration saved in 6. Use the merge option as follows:
   
   

   user@host# load merge tx-config.conf
9. Commit the configuration on both the master and the backup Routing Engines.
   
   

   user@host# commit synchronize

   Note: If you elect to run different Junos OS releases on the Routing Engines, or if you want a different configuration on the backup Routing Engine, issue the commit command without the synchronize option. In either case, you must create a configuration for the backup Routing Engine. To do this, log in to the backup Routing Engine and follow the procedure in this section. The TX Matrix router will copy this configuration to all the backup Routing Engines in the routing matrix after control is transferred to the TX Matrix router.

This is an example of a modified T640 router configuration at the [group lcc0-re0] hierarchy level: