Oracle® Traffic Director Release Notes

11g Release 1 (11.1.1.7.0)

E21039-03

Oracle® Traffic Director

Release Notes

11g Release 1 (11.1.1.7.0)

E21039-03

August 2013

This document contains information about the known issues for Oracle Traffic Director 11.1.1.7.0. For information about the new features in this release of Oracle Traffic Director, see "What's New in this Release" in the Oracle Traffic Director Administrator's Guide.

1 Known Issues

This section provides information about the known issues for Oracle Traffic Director 11.1.1.7.0 along with possible workarounds:

- "Oracle Linux on Exalogic"

- "Oracle Solaris on Exalogic and Oracle SuperCluster"

1.1 Oracle Linux on Exalogic

This section provides information about the known issues for Oracle Traffic Director 11.1.1.7.0 installed on Oracle Linux on Exalogic.

1.1.1 Increase Limit of <max-connections> for an Origin Server

The server.xml schema enforces a limit on the maximum number of connections that can be made to a single origin server. This limit is 20480.

1.1.2 SNMP Agent Crashes when an Oracle Traffic Director Instance is Stopped

If Oracle Traffic Director instances are reconfigured before running the snmpwalk command, snmpagt does not initialize correctly and it crashes.

Workaround

This is an initialization issue with the Oracle Traffic Director snmp agent. The agent can be initialized by performing the following steps:

1. Start the instance server.

2. Start snmpagt.

3. Run the following snmp command:

snmpwalk -v2c -c public <host:11161> 1.3.6.1.4.1

The snmpwalk command will force snmpagt to initialize correctly.

Note:

Make sure to execute the snmpwalk command once whenever snmpagt is started or restarted.

1.1.3 Error Message is Displayed when Uppercase is Used for Host Name

If you use the --node-host option while configuring an administration node and specify the host name in uppercase, then the following error might be displayed for that particular node when performing lifecycle operations such as starting, stopping, reconfiguring Oracle Traffic Director instances or deploying Oracle Traffic Director configuration changes:

OTD-63763, Configuration <config-name> has not been deployed to node <node-name>.

Workaround

While configuring an administration node, specify the value for --node-host option in lowercase.

1.1.4 Incorrect Toggle Message for Failover Nodes

After the primary and backup failover nodes have been toggled using the administration console, the nodes are correctly listed as toggled. However, a message in the Console Messages pane will incorrectly indicate that the nodes were not toggled.

1.1.5 Default Value for Sticky Cookie is Wrong

JSESSIONID is the value that is displayed as the default value for the sticky cookie property for routes in the administration console and CLI. This value is wrong, and the correct default value for sticky cookie is asterisk (*).

1.1.6 Oracle Traffic Director Administration Console Does Not List Network Interface Aliases

In the Oracle Traffic Director administration console, while creating failover groups using the New Failover Group wizard, it is not possible to configure failover groups based on network interface aliases.

Workaround

Perform the following steps to configure failover groups using network interface aliases. For example, to configure the VIP on the bond0:3 interface alias:

1. Create a failover group on the bond0 interface. For information about creating a failover group, see "Creating Failover Groups" in the Oracle Traffic Director Administrator's Guide.

2. Edit the keepalived.conf file, located at INSTANCE_HOME/net-config_name/config, and add the alias name as a label for the IP address. In the example below, the virtual_ipaddress option is edited to include label bond0:3:
Before editing:

vrrp_instance otd-vrrp-router-1 {
priority 225
interface bond0
virtual_ipaddress {
10.244.64.187/24
}
virtual_router_id 253

After editing:

vrrp_instance otd-vrrp-router-1 {
priority 225
interface bond0
virtual_ipaddress {
10.244.64.187/24 label bond0:3
}
virtual_router_id 253

3. After editing the keepalived.conf file, start /stop the instance for the changes to take effect.

Note:

When creating a failover group, if the administration node process is running as non-root on the node where the instances are located, then you must run start-failover on those nodes as a root user. This is to manually start the failover. If this command is not executed, failover will not start and there will be no high availability.

1.1.7 Cannot Prevent Oracle Traffic Director Services from Automatically Starting on Boot

Services are enabled/disabled per node, and there is no way to enable/disable services on specific instances running on a node.

Workaround

Use the chkconfig command to prevent a service from starting after a boot/reboot. For example, to disable service for specific instances on a node, run the following command:

chkconfig <service-instance-name> off

1.1.8 Cannot Create a Failover Group When There Are No Instances

When creating a failover group using the administration console or the CLI, if the administration nodes that you select for high availability do not have Oracle Traffic Director instances available on them, then the following error message will be displayed:

Error occurred in creating the failover group with virtual IP <ip_address>.
java.lang.NoSuchMethodException:
com.sun.web.admin.mbeans.ConfigurationMBean.createInstance(com.sun.web.admin.configlib.Configuration, com.sun.web.admin.configlib.DeployedConfiguration,
java.lang.Boolean, java.lang.Boolean, java.util.List, com.sun.web.admin.exceptions.MultiNodeException)

Workaround

Before creating the failover group, ensure that the primary and backup instances are available. For more information about creating instances, see "Creating Oracle Traffic Director Instances" in the Oracle Traffic Director Administrator's Guide.

1.2 Oracle Solaris on Exalogic and Oracle SuperCluster

This section provides information about the known issues for Oracle Traffic Director 11.1.1.7.0 installed on Oracle Solaris on Exalogic, and Oracle SuperCluster.

1.2.1 NIC Auto Detection is Choosing an Unsupported IPMP Interface during HA Failover

Auto detection of network interface fails when creating a failover group using the tadm command in Solaris SuperCluster. The same command succeeds when network interface is specified.

1.2.2 Oracle Traffic Director High Availability Configuration for Exalogic (Solaris) and Oracle Super Cluster Can Only Support EoIB interface on a Global Zone

Oracle Traffic Director cannot be configured to provide high availability on IP over IB. Currently, on Solaris, Oracle Traffic Director supports high availability only on Ethernet over IB on a global zone.

2 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Oracle Traffic Director Release Notes, 11g Release 1 (11.1.1.7.0)

E21039-03

Copyright © 2012, 2013 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Copyright © 2012, 2013, Oracle and/or its affiliates. All rights reserved.