10 Managing IP Addresses

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

• Introduction to Managing IP Addresses

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

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 "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
   

   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 "Managing System Configuration Attributes by Using ODSM Data Browser".