Skip Headers
Oracle® Communications IP Service Activator Juniper M-series Device Support Guide
Release 7.2

Go to Documentation Home
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

8 Troubleshooting

This chapter provides troubleshooting guidelines for configuring Juniper M-series devices with Oracle Communications IP Service Activator.

Checking the Juniper M-series Device Logs

The Juniper device driver records all device configuration changes that it makes in an audit log file. You can check these log files to see if configuration is being successfully applied to a device.

A new log file is created following the first transaction after midnight. The same log file is used if a device driver is stopped and started within a 24-hour period.

The log files are created in /opt/OracleCommunications/ServiceActivator/AuditTrails.

Each file is named For example, the log for a Tuesday would be After a week, the log files are automatically overwritten, so you should archive them within this period if you want to keep them.

Log files are text files, recording the date, time and details of each configuration change made to the devices controlled by the device driver.

Discovering Juniper M-series Devices

It is possible to discover devices in IP Service Activator by specifying an IP address and hop count to discover connected devices within a certain number of hops from the specified device.

The ability to discover devices using this method is dependent on each device's routing information being available in SNMP, the protocol used by IP Service Activator to interrogate routers and network segments. Juniper devices do not provide access to their routing tables through SNMP. Specifying a hop count other than zero therefore does not affect the number of devices discovered.


Oracle recommends that you set the Discovery Method to Segment scan in the Discovery dialog box if the devices are known to have large routing tables.

Communication Problems

Ensure that an SNMP Read community is set up on the device. The following command should be included with a suitable community string:

[edit snmp]
community public {
  authorization read-only;

Commit Errors

Errors or conflicts in the configuration sent to the device are detected by JUNOS when the device driver runs the commit check command. The device driver saves the failed configuration to a file named orchestream_last_failed_config.txt in the /var/home/user_name directory on the Juniper device.

You can investigate the cause of the failure by entering configuration mode, loading the orchestream_last_failed_config.txt file and running the commit check command as follows:

hostname> configure
hostname# load override orchestream_last_failed_config.txt
hostname# commit check

JUNOS checks the configuration file and displays a message indicating the cause of the error. For example:

[edit policy-options community Orch-jm10_2_fe_0_0_1-SOO members origin:0:0]
 invalid autonomous system value at '0' not in range 1 to 65535
error: configuration check-out failed

Inheritance Groups

Items in the Base configuration group are inherited from the Orchestream configuration group. However, where there are like-named items found in both groups, the item in the Base configuration takes priority. If configuration you have set up in IP Service Activator is not being activated, you may have a naming collision between the two groups.

Useful JUNOS Commands

There are a number of commands that can be useful in checking device configuration. For full details of the command syntax and an explanation of the reported information, see the Juniper documentation.

Table 8-1 lists some general configuration commands for checking device configuration.

Table 8-1 General Configuration JUNOS Commands

Command Description

show configuration

Displays the configuration that is currently running on the device.

show chassis hardware

Indicates whether a device has an Internet Processor or an Internet Processor II ASIC.

Table 8-2 lists monitoring and troubleshooting commands that can be used to display information and statistics about the software and test network connectivity.

Table 8-2 Monitoring and Troubleshooting JUNOS Commands

Command Description
clear option

Clears information from various router and protocol databases.

commit check

Verifies the syntax of a configuration but does not activate it.

monitor (start | stop | list) interface traffic

Performs real-time debugging of various software components, including the routing protocols and interfaces.


Determines the reachability of a remote network host.

show option

Displays the current configuration and information about interfaces, routing protocols, routing tables, routing policy filters, and the chassis.

test option

Tests the configuration and application of policy filters and AS path regular expressions.


Traces the route to a remote network host.

For detailed information on using these commands see the JUNOS Internet Software Operational Mode Command Reference.