[Contents] [Prev] [Next] [Index] [Report an Error]

Committing Configurations on a Routing Matrix

You must commit configuration changes for a routing matrix on the TX Matrix platform rather than on the individual T640 routing nodes. If you commit a configuration directly on a T640 routing node within a routing matrix, the configuration is not distributed to the TX Matrix platform or the other T640 routing nodes in the routing matrix. Conversely, all configuration changes you commit on the TX Matrix platform are distributed to all the T640 routing nodes in the routing matrix and override any changes committed directly on a T640 routing node.

There are two main ways to commit configurations on a TX Matrix platform. When you issue the commit synchronize command, you synchronize the configurations of both the primary and backup Routing Engines on the TX Matrix platform and the primary and backup Routing Engines of all the associated T640 routing nodes.

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 platform, this action updates only the master Routing Engines of the TX Matrix platform and the T640 routing nodes in the routing matrix.

user@router# commit

scc-re0:
configuration check succeeds
lcc0-re0:
commit complete
lcc1-re0:
commit complete
scc-re0:
commit complete

[Contents] [Prev] [Next] [Index] [Report an Error]