2 Installation and Set-up Notes

This chapter contains important notes on setting up the Juniper M-series Device Driver.

For full details about installing Oracle Communications IP Service Activator, including the Juniper M-series Device Driver, refer to IP Service Activator Installation Guide.

Installation Notes

The Juniper M-series Device Driver is a separate executable component called juniper_device_driver.

The Juniper M-series Device Driver is installed by default when you select the Proxy Agent component for installation.

Command-line Parameters

Table 2-1 summarizes available command-line parameters. For more details of the options for off-line configuration, see "Lengthening the Time Between IP Service Activator Commit Commands".

Table 2-1 Command-line Parameters

Parameter	Description
-ComponentName name	Specifies the name of the Juniper M-series Device Driver component as displayed in the client.
-ComponentLocation hostname	Specifies the hostname on which the Juniper M-series Device Driver component is installed.
-ConnectTimeout n	Socket connection timeout, where n is an integer specifying the number of seconds. Default is 30 seconds.
-LineDelay milliseconds	Amount of time, in milliseconds, that IP Service Activator waits between delivering lines of configuration to the device. Note: This parameter is only applicable if you access the device through Telnet, and not SSH.
-NoSystemGroupAddresses	If this flag is specified, VPN site addresses are specified in the orchestream configuration group instead of the system configuration group. Use this option if you need to manually provision additional addresses on an interface that will co-exist with IP Service Activator managed addresses on that interface. Note: Ensure that manually configured addresses in the system group do not conflict with IP Service Activator configured addresses in the orchestream group.
-OverwriteInterfaceDescription	The interface description configured in the Site Properties dialog is enabled only when the device driver is started with this option.
-ReadTimeout n	Socket read timeout in seconds, where n is an integer specifying number of seconds. Default is 30 seconds.
-UseRIBGroup	Use rib-group definitions statements when provisioning routing instances in MPLS VPNs. This overrides the use of policy-based mechanisms such as the auto-export JUNOS command.
-WriteTimeout n	Socket write timeout in seconds, where n is an integer specifying number of seconds. Default is 30 seconds.
-FileConfigDelivery	With this command enabled the device driver does not attempt to enter configure mode on the device and does not apply any changes to the FileInterface file. Instead, all configuration commands are delivered to a file named orchestream-config-device_name-time-date.txt. This file is created in a directory specified by -FileConfigDeliveryDir
-FileConfigDeliveryDir name	Specifies the location of the orchestream-config-device_name-time-date.txt file.
-NoDeviceComm	If this flag is specified, both CLI and SNMP connections are disabled, preventing the device driver connecting to the device.
-UseMaxPrefixes	Supports maximum prefixes from JDD when a new command line option -UseMaxPrefixes is passed to JDD.This option can also be set from ComponentParametes.By default this flag is off and not passed as cmd line option. If it is passed or set to true from ComponentParameters, JDD will push maximum-prefixes instead maximum-routes.

Note:

For delivery of configuration to file instead of the device, the following commands must be configured:

-FileConfigDelivery
-FileConfigDeliveryDir
-NoDeviceComm

There are also command-line parameters that control debugging logs for all IP Service Activator components. These are described in full in IP Service Activator Administrator's Guide.

The device driver must be restarted for any changes to these command-line parameters to take effect.

Setting Command-line Parameters on Oracle Solaris

Command-line options are specified in the cman.cfg file located in the /opt/OracleCommunications/Service Activator/config directory.

Using a text editor such as vi, edit the juniper entry in the cman.cfg file with the relevant option.

Exporting Routes Between Routing Instances in Overlapping MPLS VPNs

Starting with IP Service Activator version 4.2, the JUNOS auto-export command is used by default to implement policy-based export of routes between routing instances in overlapping MPLS VPNs. This greatly simplifies the device configuration required to set up overlapping VPNs.

The Juniper Device Driver and Existing RIB-group Statements

If you have upgraded to IP Service Activator version 4.2 or higher and your devices have RIB groups defined, or if you have been using the -UseRIBGroup command-line parameter (see Table 2-1) and have removed it, the Juniper device driver handles existing configuration in the following way. It will:

Delete rib-group definition statements inside group orchestream
For each routing instance inside group orchestream:
- Change the routing-options to auto-export
- Delete the interface-routes sections which defines the RIB group
Delete the definition of the family inet which refers to the RIB group, inside the protocols definition

Because of these changes, a simple upgrade procedure is recommended. See "Upgrading Devices from Using RIB Groups to Using auto-export".

Upgrading Devices from Using RIB Groups to Using auto-export

If you have upgraded to IP Service Activator version 4.2 or higher and your devices have RIB groups defined, or if you have been using the -UseRIBGroup command-line parameter and are removing it, upgrade you devices to use auto-export.

To upgrade your devices:

Un-manage affected devices.
Perform the upgrade (or de-implement the -UseRIBGroup command-line parameter).
Restart IP Service Activator.
Manage the affected devices.

When the devices are re-managed, the new configuration using the auto-export command is pushed.

Over-riding the auto-export Command with -UseRIBGroup

To configure the Juniper device driver to use RIB groups instead of the auto-export command to export routes in MPLS VPNS, use the -UseRIBGroup command-line parameter. This mimics the handling of export routes in versions of IP Service Activator prior to version 4.2. See "Setting Command-line Parameters on Oracle Solaris".