Matrix; Creating A Configuration File On The T1600 Router For Integration Into The Routing Matrix - Juniper TX MATRIX PLUS Hardware Manual

Hide thumbs Also See for TX MATRIX PLUS:
Table of Contents

Advertisement

Creating a Configuration File on the T1600 Router for Integration into the Routing

Matrix

Copyright © 2010, Juniper Networks, Inc.
Verifying the State of the Interfaces on a T1600 Router on page 250
Using the current T1600 router configuration, create a configuration file on the T1600
router that will be merged into the TX Matrix Plus router configuration:
Save the T1600 router configuration. For example:
1.
user@host# save T1600-config.conf
As described in "Configuration Groups" on page 73, special configuration groups
2.
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
and
lcclcc-number-re0
the router.
If the configuration includes special Routing Engine configuration groups, include the
3.
apply-groups
statement at the
apply-groups [ lcc0-re0 lcc0-re1 ]
Change the configuration hierarchy of all statements at the
4.
hierarchy level to the
fpc slot-number]
hierarchy level.
If the chassis ID of the T1600 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 Plus Interface Names Overview" on page 75.
Save the modified T1600 router configuration using a different filename from the one
6.
you selected for the saved configuration. For example:
user@host# save txp-config.conf
NOTE: Do not commit the configuration.
This is an example of a modified T1600 router configuration at the
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
Chapter 18: Integrating an Offline T1600 Router into a Routing Matrix
, where
lcclcc-number-re1
lcc-number
[edit]
hierarchy level. For example:
[edit chassis lcc lcc-number fpc slot-number]
0
, you do not need to change interface names
re0
equals the chassis ID of
[edit chassis
[group lcc0-re0]
243

Advertisement

Table of Contents
loading

Table of Contents