Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Details of the limitations in IPv6 support

The following table provides full details about the limitations in IPv6 support in the various components and areas in BMC Server Automation:

Area in productLimitation or non-supported feature
AgentBMC Server Automation does not support HP-UX agents over IPv6.
Application Server

The BMC Server Automation Application Server has the following IPv6 limitations:

  • Workflow Job configuration accepts the host name of a BMC Atrium Orchestrator (AO) server only if the server is hosted over an IPv6 machine. To work around this limitation, provide the AO server URL during configuration, with either an IPv4 address or a host name, and it will resolve to an IPv6 address.
  • The Continuous Compliance use case requires providing the AO server URL during AO configuration with either an IPv4 address or a host name, so that this URL will resolve to an IPv6 address.
  • The Agent Installer Job does not support Windows targets that are registered with their explicit IPv6 addresses in BMC Server Automation. This limitation is from the PsExec tool that the implementation uses.
  • Remote host authentication on Windows for PsExec servers does not support IPv6 addresses.

  • Communication through SOCKS proxies between an IPv6 Application Server and IPv6 targets is not supported.

Database

The databases that BMC Server Automation works with have the following IPv6 limitations:

  • Oracle 10g R2 does not support IPv6.
  • Oracle 11g RAC is not supported by BMC Server Automation in an IPv6 environment.
Virtualization

The virtualization feature in BMC Server Automation has the following IPv6 limitations:

  • Support for IPv6 guest customization on a VMare virtualization platform is experimental because the VMware vSphere 5.0 SDK supports the IPv6 guest customization in experimental mode only. Also, VMware does not claim official support of this feature through a vSphere client or manual sysprep on the guest.
  • VMware vSphere's API for IPv6 guest customization does not provide an option for specifying the connection-specific DNS suffix for IPv6. Therefore, IPv6 guest customization cannot be applied through BMC Server Automation.

  • Domain addition for an IPv6 domain is not supported, due to the limitations of the experimental API. As a workaround for adding a guest to the IPv6 domain, you can create a batch script or NSH script and run it after the Virtual Guest Job.
  • For distribution of the Citrix custom configuration object, the Citrix proxy machine must be a dual stack machine.
    This requirement is due to the fact that the Citrix XenServer host’s management IP configuration supports only IPv4 (for all versions of Citrix XenServer). However, the Application Server is pure IPv6 only, so the proxy host must communicate with the Application Server on IPv6, while communicating with the XenServer host on IPv4.

  • Citrix VM customization does not work if the Application Server has only IPv6 enabled (that is, IPv4 is disabled) and the Citrix XenServer is version 5.6FP1 or 6.0.
  • Citrix VM customization does not work if the Citrix custom template has only IPv6 enabled (that is, IPv4 is disabled) and the Citrix XenServer is version 5.6 FP1 or 6.0.
  • The virtualization feature no longer supports Win2k3 because the sysprep API does not support IPv6 tags.

  • If you assign a static IPv6 IP to an NIC interface of a VM along with the static IPv6 IP provided, the NIC also acquires additional global scope IPs from DHCPv6 / IPv6 auto-configuration.
    This behavior is as designed. For more information, see http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/02a3ef30-cf2a-4c45-b3b9-d5490e4e224f/.
  • For the Red Hat Enterprise Virtualization (RHEV) custom configuration object, a pure IPv6 application server does not work. The application server must be either IPv4 or dual stack.
    This requirement is due to the fact that the RHEV Manager does not support IPv6 (in all versions).
  • IBM provisioning over IPv6 is not supported.
Provisioning

The provisioning feature in BMC Server Automation has the following IPv6 limitations:

  • PXE boot is not supported over IPv6 and the initial provisioning steps need to be over IPv4. As long as you have a dual stack and PXE, TFTP, and DHCP are on IPv4 for the bare metal provisioning steps, the resultant machine can have an IPv6 IP.
  • During bare metal OS provisioning, you cannot specify a static IPv6 IP for a Linux machine.
  • AIX, Solaris and HPUX  provisioning over IPv6 is not supported.
  • Windows 2003 provisioning does not support specifying IPv6 addresses.
  • Citrix XenServer provisioning is not supported over IPv6.

  • The UCS Manager does not support IPv6. Therefore, provisioning of blade servers over IPv6 is not supported, though the resultant blade server can support IPv6.

  • When using a data store over IPv6, Linux provisioning is not stable, due to limitations in RedHat Linux.

SecurityRSA SecurID authentication does not support IPv6 connections.
BMC BladeLogic Decision Support for Server Automation

BMC BladeLogic Decision Support for Server Automation supports only dual stack and not pure IPv6 because the ODI (an ETL tool) does not support pure IPv6.

Was this page helpful? Yes No Submitting... Thank you

Comments