Planning the Infrastructure Implementation › IPv6 Support › Restrictions in Context of IPv6 Support

Restrictions in Context of IPv6 Support

The following restrictions apply in the context of IPv6 support in CA Client Automation (Client Automation):

• If you have set the protocolprecedence parameter in comstore to “ipv6,ipv4” and you are using an Oracle MDB, you will find that the product tends to run slowly. This is because database connections will first try IPv6 addresses, which will fail to connect to the Oracle database, before trying an IPv4 address. To prevent this performance degradation, while continuing to use IPv6 addresses by preference in other parts of the product, please create the following DWORD with a value of 1 in the registry, HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Unicenter ITRM\ UseIPv4ForDB.
• OS Installation Management (OSIM) is only available in networks supporting IPv4. The reason is that OSIM relies on PXE, which relies on IPv4.
• Client Automation does not support link local addresses when addressing infrastructure components, except for the following two cases:
  • When connecting from a remote control viewer to a remote control host, a link local address may be entered into the remote control viewer.
  • When using remote control to browse the local network, link local addresses are displayed and can be selected.

  Note: Link local addresses are collected and displayed as part of Inventory Collection and Display.

• The NOS download method for a software delivery (SD) job is not supported over pure IPv6 under the following conditions:
  • The agent on any platform is using Samba or NFS
  • The agent is a Windows platform older than Windows Vista and is using Microsoft NOS

  If however the Windows platform is Windows Server 2003, the following steps can be taken to enable NOS download:

  1. The following registry key must be set to 1 on the agent computers:

     HKLM\System\CurrentControlSet\Services\smb\Parameters\IPv6EnableOutboundGlobal (REG_DWORD)

  2. The two hot fix updates listed below must be applied to any agent computers wishing to mount its DSM scalability server library share:

     http://support.microsoft.com/kb/947369/en-us

     http://support.microsoft.com/kb/950092/en-us

  3. The host name of the scalability server computer must resolve to a global IPv6 address.
  4. The scalability server library share (as held in the scalability server comstore) must use a host name (and not an IP address). To verify whether an IP address is being used, run the following commands:

     ccnfcmda -cmd GetParameterValue -ps itrm/usd/shared -pn exportarchive
     ccnfcmda -cmd GetParameterValue -ps itrm/usd/shared -pn msiadminpathunc
     

     If either command returns a value that includes an IP address, replace the address with a hostname using the following commands:

     ccnfcmda -cmd SetParameterValue -ps itrm/usd/shared -pn exportarchive 
     -v IP_replaced_with_hostname
     

     ccnfcmda -cmd SetParameterValue -ps itrm/usd/shared -pn msiadminpathunc 
     -v IP_replaced_with_hostname
     

     For example, if the GetParameterValue for msiadminpathunc returned \\2001:db9:1:2:f045:c89:5c2:bdf5\SDMSILIB, the new value would be \\foobar.testarea.ca.com\SDMSILIB.

     Note: For more detailed information about the ccnfcmda configuration agent command, type <command> /? at the command prompt.

  In practice, if the above NOS download method fails, software delivery will fall back to using the NOSless download method. However, if the fallback is disabled by changing the default policy, the SD job will fail under these circumstances.

• Data Transport Service (DTS) WorldView dynamic container membership only supports IPv4 address ranges.
• Infrastructure Deployment and Continuous Discovery support IPv4 address ranges only.
• The Unmanaged Computers wizard, which lets the user enter one or more subnets used to filter out unmanaged computers, only supports IPv4 subnets.
• The CAF Service Locator may only work in a local subnet, which may affect the Packager that will find managers only in the local subnet. (This depends on whether routers allow scoped multicast.)
• The DTS PPP protocol does not support IPv6.
• Client Automation does not support disabling IPv4 on Windows Server 2003 and Windows XP, because disabling IPv4 on these Windows platforms is generically not supported.
• On Windows Vista and Windows Server 2008, Client Automation supports pure IPv6. IPv4 needs to be removed on these platforms using the following command from a command prompt:

  netsh interface ipv4 uninstall
  

  A message is displayed if a reboot is required.