Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle Internet Directory
11g Release 1 (11.1.1)

Part Number E10029-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

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

10 Managing IP Addresses

This chapter discusses how to manage Oracle Internet Directory's IP addresses. It contains the following sections:

10.1 Introduction to Managing IP Addresses

When you install Oracle Internet Directory on a dual stack (IPV4/IPV6) host, Oracle Internet Directory listens on both addresses. You cannot install Oracle Internet Directory on a host with only an IPV6 address because the Oracle Database requires an IPV4 address to connect to.

If you install Oracle Internet Directory on an IPV4 host and then change the host's address to IPV6, you must configure Oracle Internet Directory's IP address separately to the IPV6 address by changing the orclhostname attribute in the instance-specific configuration entry.

If you must have Oracle Internet Directory listen on a specific address for some other reason, you also do that by changing the orclhostname attribute in the instance-specific configuration entry.

10.2 Configuring an IP Address for IP V6, Cold Failover Cluster, or Virtual IP

Perform the following steps to configure Oracle Internet Directory to listen on a specific IP address:

  1. Create an LDIF file similar to this:

    dn: cn=COMPONENT_NAME, cn=osdldapd, cn=subconfigsubentry
    changetype: modify
    replace: orclhostname
    orclhostname: IP_address
    
  2. Execute the following ldapmodify command:

    ldapmodify -D cn=orcladmin -q -p portNum -h hostname -f ldifFile 
    
  3. Restart Oracle Internet Directory by using opmnctl, as follows:

    opmnctl stopall
    opmnctl startall
    
  4. Update the registration of the Oracle Internet Directory component, as described in Section 8.3.4, "Updating the Component Registration of an Oracle Instance by Using opmnctl." For example:

    $ORACLE_INSTANCE/bin/opmnctl updatecomponentregistration \
     -adminHost myhost \
     -adminPort 7001 \
     -adminUsername weblogic \
     -componentType OID  \
     -componentName oid2\
     -Port 3061
     -Sport 3131
    

    If you fail to perform this step, you will be unable to use Fusion Middleware Control or wlst to manage that component.

You can also use ODSM to change the orclhostname attribute in the instance-specific configuration entry. See Section 9.5, "Managing System Configuration Attributes by Using ODSM Data Browser."

10.3 Configuring IP Addresses for Notifications in a Cluster

In a cluster environment, Oracle Internet Directory servers need to communicate with each other when cached data is changed. These servers communicate using the LDAP protocol. Hence, in a cluster environment at least one non-SSL port must be available for this communication.

For better performance, use a dedicated IP address and Oracle Internet Directory instance for notifications. Create a new component and then add the instance configuration, as follows:

ldapmodify -p oidPort -D cn=orcladmin -w adminPasswd -f ldiffile

In this example, ldiffile contains:

dn: cn=oid-instance,cn=osdldapd,cn=subconfigsubentry
changetype: modify
add: orclcachenotifyip;port-number-to-use
orclcachenotifyip;port-number-to-use: IP-address-to-use

where:

For example, on node 1 if you have two IP address 10.10.10.1 and 10.10.10.2 and you want to use 10.10.10.2 for notifications, perform the following configuration, where oid1 is the component name on node 1:

ldapmodify -p oidPort -D cn=orcladmin -w adminPasswd -f ldiffile

In this example, ldiffile contains:

dn: cn=oid1,cn=osdldapd,cn=subconfigsubentry
changetype: modify
add: orclcachenotifyip
orclcachenotifyip: 10.10.10.2

Similarly on node 2, if you have two IP address 10.10.10.3 and 10.10.10.4 and if you want to use 10.10.10.4 for notifications, perform the following configuration, where oid2 is the component name on node 2:

ldapmodify -p oidPort -D cn=orcladmin -w adminPasswd -f ldiffile

In this example, ldiffile contains:

dn: cn=oid2,cn=osdldapd,cn=subconfigsubentry
changetype: modify
add: orclcachenotifyip
orclcachenotifyip: 10.10.10.4

Note:

When orclcachenotifyip is configured for an Oracle Internet Directory instance, the IP address must be local to the node where that instance is running.

For example, if Oracle Internet Directory on node 1 is cn=oid1,cn=osdldapd,cn=subconfigsubentry and Oracle Internet Directory on node 2 is cn=oid2,cn=osdldapd,cn=subconfigsubentry, then Oracle Internet Directory on node 1 will check configuration information of node 2 (which is cn=oid2,cn=osdldapd,cn=subconfigsubentry).

When Oracle Internet Directory server on node 1 is started, it will use this information to connect to Oracle Internet Directory on node 2 (10.10.10.4).

If you do not want production traffic to be affected with notification LDAP traffic, then create a new OID instance on each node. For example, on node 1, create oid3 with port number 5678, as follows:

ldapmodify -p oidPort -D cn=orcladmin -w adminPasswd -f ldiffile

In this example, ldiffile contains:

dn: cn=oid3,cn=osdldapd,cn=subconfigsubentry
changetype: modify
add: orclcachenotifyip;5678
orclcachenotifyip;5678: 10.10.10.2

Repeat the same procedure on node 2 to create the oid4 instance with port number 5678, as follows:

ldapmodify -p oidPort -D cn=orcladmin -w adminPasswd -f ldiffile

In this example, ldiffile contains:

dn: cn=oid4,cn=osdldapd,cn=subconfigsubentry
changetype: modify
add: orclcachenotifyip;5678
orclcachenotifyip;5678: 10.10.10.4