Committing Configurations on a Routing Matrix with a TX Matrix Router
You must commit configuration changes for a routing matrix with a TX Matrix router on the TX Matrix router rather than on the individual T640 routers. If you commit a configuration directly on a T640 router within a routing matrix, the configuration is not distributed to the TX Matrix router or the other T640 routers in the routing matrix. Conversely, all configuration changes you commit on the TX Matrix router are distributed to all the T640 routers in the routing matrix and override any changes committed directly on a T640 router.
There are two main ways to commit configurations on a TX Matrix router. When you issue the commit synchronize command, you synchronize the configurations of both the primary and backup Routing Engines on the TX Matrix router and the primary and backup Routing Engines of all the associated T640 routers.
user@router# commit synchronize
scc-re0: configuration check succeeds lcc0-re1: commit complete lcc0-re0: commit complete lcc1-re1: commit complete lcc1-re0: commit complete scc-re1: commit complete scc-re0: commit complete
If you issue the basic form of the commit command on the TX Matrix router, this action updates only the master Routing Engines of the TX Matrix router and the T640 routers in the routing matrix.
user@router# commit
scc-re0: configuration check succeeds lcc0-re0: commit complete lcc1-re0: commit complete scc-re0: commit complete
Published: 2012-11-28
Related Documentation
- T Series
- Overview of the Routing Matrix with a TX Matrix Router
- Roadmap to Configuring a Routing Matrix with a TX Matrix Router
- Example: Routing Matrix with a TX Matrix Router Configuration
- Additional Information
- Routing Matrix with a TX Matrix Router