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

Synchronizing Configurations Simultaneously with Other Operations

The <synchronize/> tag can be combined with the other tag elements that can occur within the <commit-configuration> tag element. The JUNOScript server checks, copies, and commits the configuration, and emits the same response tag elements as when the <synchronize/> tag is used by itself. The possible combinations are described in the following sections.

Verifying the Configuration on Both Routing Engines

To check the syntactic correctness of a local configuration on both Routing Engines without committing it, the application encloses the <synchronize/> and <check/> tag elements in <commit-configuration> and <rpc> tag elements:



<rpc>
    <commit-configuration>
        
<synchronize/> 

        
<check/> 

    </commit-configuration>
</rpc>

The <force-synchronize/> tag cannot be combined with the <check/> tag elements.

For more information about verifying configurations, see Verifying a Configuration Before Committing It.

Scheduling Synchronization for a Specified Time

To commit a configuration on both Routing Engines at a specified time in the future, the application encloses the <synchronize/> and <at-time> tag elements in <commit-configuration> and <rpc> tag elements:



<rpc>
    <commit-configuration>
        
<synchronize/> 

        
<at-time>time</at-time> 

    </commit-configuration>
</rpc>
     

<rpc>
    <commit-configuration>
        
<force-synchronize/>

        
<at-time>time</at-time>

    </commit-configuration>
</rpc>

As when the <at-time> tag element is emitted by itself, the JUNOScript server verifies syntactic correctness immediately and does not emit additional tag elements when it actually performs the commit operation on each Routing Engine. For information about how to specify the time in the <at-time> tag element, see Committing the Candidate Configuration Only After Confirmation.

Synchronizing Configurations but Requiring Confirmation

To commit the candidate configuration on both Routing Engines but require confirmation for the commit to become permanent, the application encloses the <synchronize/>, <confirmed/>, and (optionally) <confirm-timeout> tag elements in <commit-configuration> and <rpc> tag elements:



<rpc>
    <commit-configuration>
        
<synchronize/> 

        
<confirmed/> 

            [<confirm-timeout>minutes</confirm-timeout>] 
    </commit-configuration>
</rpc>

The same rollback deadline applies to both Routing Engines and can be extended on both at once by again emitting the <synchronize/>, <confirmed/>, and (optionally) <confirm-timeout> tag elements on the Routing Engine where the tag elements were emitted the first time.

The <force-synchronize/> tag cannot be combined with the <confirmed/> and <confirm-timeout> tag elements.

For more information about confirmed commit operations, see Committing the Candidate Configuration Only After Confirmation.

Logging a Message About Synchronized Configurations

To synchronize configurations and record a log message when the commit succeeds on each Routing Engine, the application encloses the <synchronize/> and <log/> tag elements in <commit-configuration> and <rpc> tag elements:



<rpc>
    <commit-configuration>
        
<synchronize/> 

        
<log>message</log> 

    </commit-configuration>
</rpc>


<rpc>
    <commit-configuration>
        
<force-synchronize/>

        
<log>message</log>

    </commit-configuration>
</rpc>

The commit operation proceeds as previously described in the <synchronize/> or <force-synchronize/> tag descriptions. The message for each Routing Engine is recorded in the separate /var/log/commits file maintained by that Routing Engine. For more information about logging, see Logging a Message About a Commit Operation.

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