Juniper TX MATRIX Hardware Manual page 199

Related
Documentation
Creating a Configuration File on the T640 Router for Integration into the Routing Matrix
Copyright © 2010, Juniper Networks, Inc.
% exit
Issue the commit synchronize
6.
errors:
user@host# commit synchronize
Overview of Converting a T640 Router on page 161
TX Matrix Software and CLI Overview on page 145
Using the current T640 router configuration, create a configuration file on the T640 router
that will be merged into the TX Matrix router configuration:
Save the T640 router configuration. For example:
1.
user@host# save t640-config.conf
As described in "Configuration Groups" on page 146, special configuration groups
2.
and apply to the Routing Engines in slots 0 and 1 of the TX Matrix router. If the
re1
T640 router configuration contains these groups, you must change them to
and
lcclcc-number-re0
the router.
If the configuration includes special Routing Engine configuration groups, include the
3.
statement at the
apply-groups
apply-groups [ lcc0-re0 lcc0-re1 ]
Change the configuration hierarchy of all statements at the
4.
fpc slot-number] hierarchy level to the
hierarchy level.
If the chassis ID of the T640 router is
5.
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" on page 147.
Save the modified T640 router configuration using a different filename from the one
6.
you selected in Step 1. For example:
user@host# save tx-config.conf
NOTE: Do not commit the configuration.
Transfer the modified T640 router configuration to the TX Matrix router. You can use
7.
an intermediate server on the out-of-band management network accessible by both
the T640 router and the TX Matrix router.
On an external management device connected to the console or auxiliary port of the
8.
TX-CIP, load the configuration saved in 6. Use the
command, and ensure that there are no synchronization
, where
lcclcc-number-re1 lcc-number
hierarchy level. For example:
[edit]
[edit chassis lcc lcc-number fpc slot-number]
, you do not need to change interface names
0
Chapter 19: Converting a T640 Router
equals the chassis ID of
[edit chassis
merge option as follows:
re0
167