Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 12 Next »

The GET-CONFIGS directive An optional \[MODE\] can be specified to the right of the ":" to indicate whether synchronous or asynchronous behavior is desired. Valid values for \[MODE\] are "synchronous" and "asynchronous". If not specified, \[MODE\] defaults to "synchronous". Synchronous behavior implies that the script will block until the GC operation has completed (i.e. the operation terminates with an OK status) or abort if an error is encountered (i.e. the operation terminates with an Error status). Asynchronous behavior implies that the script will continue processing after the GC request is initiated. An example follows:

Example

# Ensure that NetMRI has the most up-to-date configurations
# on file. The script will block until the Get Configs operation has 
# completed since the default synchronous mode is used.
    # Ensure that NetMRI has the most up-to-date configurations on file. The script
    # will block until the Get Configs operation has completed since the
    # synchronous mode is used.    
    GET-CONFIGS:
    # Modify the interface description for Fa0/1.    
    config t    
    interface Fa0/1
            description Get Configs Test
    end
    # Request another Get Configs operation to audit the above change. Since this
    # is the end of the script and there is no need to block until the Get Configs
    # operation has completed, the asynchronous mode is used.    
    GET-CONFIGS: asynchronous

After script execution completes, output similar to the following can be seen in the Status Log of the Job Details Viewer:

+++ 1. Action: Get Configs Test
+++ 1. [Action-Commands] 
++ Requesting on demand configuration collection (synchronous) ........ OK
+++ Received TrackingID 1 ............................................. OK
+++ Getting the status of TrackingID 1 ................................ PENDING
+++ Sending 'Keep Alive CR/LF' ........................................ OK
+++ Getting the status of TrackingID 1 ................................ QUEUED
+++ Sending 'Keep Alive CR/LF' ........................................ OK
+++ Getting the status of TrackingID 1 ................................ QUEUED
+++ Sending 'Keep Alive CR/LF' ........................................ OK
+++ Getting the status of TrackingID 1 ................................ RUNNING
+++ Sending 'Keep Alive CR/LF' ........................................ OK
+++ Getting the status of TrackingID 1 ................................ OK
+++ 1. Sending 'config t' ............................................. OK
+++ 1. Sending 'interface Fa0/1' ...................................... OK
+++ 1. Sending 'description Get Configs Test' ......................... OK
+++ 1. Sending 'end' ...................................................OK
+++ Requesting on demand configuration collection (asynchronous) ...... OK
+++ Closing session ................................................... OK
*** Successfully ran configuration command script ***


  • No labels