Creating a Configuration File for the Integration of an Operational
T1600 Router
Using the current T1600 router configuration, create
a configuration file on the operational T1600 router that will be
merged into the TX Matrix Plus router configuration:
- Save the T1600 router configuration. For example:
user@host# save T1600-config.conf
We strongly recommend that you transfer the saved T1600 router
configuration to an intermediate server on the out-of-band management
network accessible by the T1600 router.
- The Routing Engines in the TX Matrix Plus router and the
T1600 routers in the routing matrix do not support the fxp0 management interface, or the fxp1 and fxp2 internal
Ethernet interfaces. References in the configuration file to fxp0, fxp1, or fxp2 must be modified to em0, ixgbe0, and ixgbe1.
- 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 Plus router. If the T1600 router configuration contains these
groups, you must change them to lcc0-re0 and lcc0-re1.
- 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 ]
- 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.
- Save the modified T1600 router configuration. Use a different
filename from the one you selected for the saved configuration. For
example:
user@host# save txp-config.conf
 | Caution:
Do not commit the configuration. |
This is an example of a modified T1600 router configuration
at the [group lcc0-re0] hierarchy level:
group lcc0-re0 {system {host-name host-name;backup-router address destination destination-address;}interfaces {em0 {unit 0 {family inet {address address/prefix-length}}}}}
Published: 2011-12-19