6 Monitoring and Troubleshooting Scripts

This chapter explains the features available for checking scripts.

Checking the Status of Scripts

Once you have applied driver scripts you can check the points in the system at which they will run.

Device scripts can be applied to different levels of objects in the system: customers, VPNs, sites, networks, devices, interfaces, sub-interfaces or VC endpoints. You can check each object to see which scripts currently apply to it.

To check the status of a script:

1. In the Oracle Communications IP Service Activator client, double-click the relevant object (for example, a site, device or interface) from the hierarchy tree or the topology map.

   The configuration applied to this object appears in the Details pane.

2. Click the Driver Scripts tab to view relevant scripts.

Just as with rules, each abstract (parent) script is followed by a list of the concrete scripts that have been created at appropriate interfaces. Parent scripts appear on a white background if they have been set up on the selected object and on a gray background if they have been inherited from a higher-level object.

Figure 6-1 shows the Driver Scripts tab on the Details pane.

Figure 6-1 The Driver Scripts Tab

Rules are listed under the following headings:

• Name: the name of the script.

• State: the current status of the script. For concrete scripts the status is one of the following:

  • Inactive: the script has been created, but not yet propagated to the devices.

  • Active: the script has been propagated to proxy agents, but is not yet configured on a device.

  • Installed: the script has been propagated to proxy agents and has been successfully installed on the designated device.

  • Failed: the proxy agent experienced a failure trying to install the script and it has therefore been discarded. Note that for a repeating script a further attempt will be made to install the script on the next propagate.

  • Rejected: the script has been rejected by the device driver (for example because of a syntax error).

• Level: the level at which the script is implemented.

• Driver Type: the device driver that will run the script.

• Script Type: the type of script. Values are: Device, Interface, Sub-interface, ATM PVC, or Frame Relay PVC.

• Device Role: the role of devices that this script will be applied to. Values are: Access, Gateway, Core, Shadow, or Any Role.

• Interface Role: for Interface, Sub-interface, ATM PVC and FR PVC scripts, the interface role that this script will be applied to. Values are Core, Local, Access, or Any Role.

• Installed: indicates when this script will be applied relative to other configuration changes applied as part of the propagate. Value is either Before config changes or Following successful config changes.

• Frequency: indicates how often the configuration will be applied. Value is either Once only (that is, on the next propagate) or Repeat (on each propagate until the script is removed).

• Install on restart: indicates if the script is to be run when a device restart is detected. Value is either True or False.

• Owner: if ownership of the script has been specified the value is the owner's username.

• Owner Group: the group to which the owner belongs.

Understanding Warnings and Error Messages

Table 6-1 lists the warnings and errors that may be raised if scripts are incorrectly applied.

Note:

Scripts are not checked or validated by the IP Service Activator client.

Table 6-1 Script Warning and Error Messages

Number	Severity	String	Explanation
2100	Warning	Driver Script name will not have any effect when applied here.	Raised if a script is applied at too low a level for its type, for example, a device script is linked to an interface.
2101	Warning	Driver Script name will not have any effect when applied here because of the type of the script.	Raised if a script is applied at an object where it can't take effect because of the roles specified, for example, an Access interface script is linked to a Local interface.
2205	Error	Driver Script has no effect due to mismatch with Device Driver type.	Raised if a script cannot be applied to the specified object because it is not applicable to the driver managing the site.
3309	Error	Driver script failed with error details: details	Raised if a driver script fails when run by the device driver. Any user information incorporated within the driver script is displayed in the details string.

Checking Logs

All device configuration changes applied by the Cisco device driver are recorded in a specific log file. You can check these log files to see if configuration applied by driver scripts is being successfully applied to a device.

On Solaris systems, the log files are in /opt/OracleCommunications/IPServiceActivator/AuditTrails

On Windows systems, the log files are created in Program Files\ Oracle Communications\IP Service Activator\AuditTrails

Commands delivered to the devices are also logged in the Device Configuration Log.

To check the Device Configuration Log

1. On the System tab, open the System Logs folder.

2. Choose Device Configuration Log.

   The Device Configuration Log appears in the details pane.