Synchronizing the Configuration on Both Routing Engines

To synchronize a configuration on a redundant Routing Engine system, a client application needs to enclose the empty <synchronize/> tag in <commit-configuration> and <rpc> tag elements:

The JUNOScript server verifies the configuration’s syntactic correctness on the Routing Engine where the <synchronize/> tag is emitted (referred to as the local Routing Engine), copies the configuration to the remote Routing Engine and verifies its syntactic correctness there, and then commits the configuration on both Routing Engines.

The JUNOScript server encloses its response in <rpc-reply> and <commit-results> tag elements. It emits a separate <routing-engine> tag element for each operation on each Routing Engine:

• If the syntax check succeeds on a Routing Engine, the <routing-engine> tag element encloses the <commit-check-success/> tag and the <name> tag element, which reports the name of the Routing Engine on which the check succeeded (re0 or re1):

  <routing-engine>
      <name>(re0 | re1)</name>
      <commit-check-success/>
  </routing-engine>
  
  

  If the configuration is incorrect, an <xnm:error> tag element encloses a description of the error.

• If the commit operation succeeds on a Routing Engine, the <routing-engine> tag element encloses the <commit-success/> tag and the <name> tag element, which reports the name of the Routing Engine on which the commit operation succeeded:

  <routing-engine>
      <name>(re0 | re1)</name>
      <commit-success/>
  </routing-engine>
  
  

  If the commit operation fails, an <xnm:error> tag element encloses a description of the error. The most common causes of failure are semantic or syntactic errors in the configuration.

Example: Synchronizing the Configuration on Both Routing Engines

The following example shows how to commit and synchronize the candidate configuration on both Routing Engines.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.