Juniper Networks
Log in
|
How to Buy
|
Contact Us
|
United States (Change)
Choose Country
Close

Choose Country

North America

  • United States

Europe

  • Deutschland - Germany
  • España - Spain
  • France
  • Italia - Italy
  • Россия - Russia
  • United Kingdom

Asia Pacific

  • Asean Region (Vietnam, Indonesia, Singapore, Malaysia)
  • Australia
  • 中国 - China
  • India
  • 日本 - Japan
  • 대한민국 - Korea
  • 台灣 - Taiwan
Solutions
Products & Services
Company
Partners
Support
Education
Community
Security Intelligence Center

Technical Documentation

Support
Technical Documentation
Content Explorer New
 
Enterprise MIBs
 
EOL Documentation
 
File Format Help
 
Glossary
 
Portable Libraries
 
 
Home > Support > Technical Documentation > T Series Routers > TX Matrix Plus Router Hardware > Creating a Configuration File for the Integration of an Operational T1600 Router
Print
Rate and give feedback:  Feedback Received. Thank You!
Rate and give feedback: 
Close
This document helped resolve my issue.  Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  
E-mail: 
Submitting...
 

Related Documentation

  • T Series
  • Overview of Upgrading and Integrating an Operational T1600 Router
  • Transferring the T1600 Router Configuration to the TX Matrix Plus Router in an Operational T1600 Router
 

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:

  1. 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.

  2. 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.
  3. 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.
  4. 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 ]
  5. 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.
  6. 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}}}}}
 

Related Documentation

  • T Series
  • Overview of Upgrading and Integrating an Operational T1600 Router
  • Transferring the T1600 Router Configuration to the TX Matrix Plus Router in an Operational T1600 Router
 

Published: 2011-12-19

 
  • About Juniper
  • The New Network
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • Support
  • Technical Documentation
  • Knowledge Base (KB)
  • Software Downloads
  • Product Licensing
  • Contact Support
Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2012 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out