IBM logoEnterprise Cloud Management SupportContact Us
ArticlesArticles Most Popular ArticlesMost Popular Articles Most Helpful ArticlesMost Helpful Articles Submit A QuestionSubmit A Question
RSS Feeds
Skip Navigation
DrillDown Icon Table of Contents
DrillDown Icon Enterprise Cloud
DrillDown Icon Release Notes
DrillDown Icon Known Issues
DrillDown Icon Cannot Mount ISO
DrillDown Icon Console Connect with a Proxy
DrillDown Icon IPv6 and Windows Server 2003
DrillDown Icon Policies
DrillDown Icon Registration and Login
DrillDown Icon Infinicenter Console
DrillDown Icon Enterprise Cloud API
DrillDown Icon Best Practices
DrillDown Icon FAQs
DrillDown Icon Troubleshooting
DrillDown Icon Enterprise Cloud Managed Edition
DrillDown Icon Sales and Support
DrillDown Icon Proprietary Statement
  Email This ArticlePrint PreviewPrint Current Article and All Sub-Articles
 
IPv6 and Windows Server 2003

IPv6 and Windows Server 2003

Note: Microsoft® ended all support, including security updates, for Windows Server 2003 on 14 July 2015. IBM strongly recommends migrating any remaining Windows Server 2003 virtual machines to Windows Server 2008 or newer.

Issue

Creating or copying Windows Server virtual machines with one or more IPv6 addresses may result in incorrect IPv6 addresses on the new server.

The issue arises when creating or copying a Windows Server virtual machine configured with any IPv6 addresses.

Creating

As part of the create request, one or more new IPv6 addresses are assigned. Correct behavior would have Windows on the virtual machine add the new IPv6 address, supplied in the create request. However, a Windows Server 2003 virtual machine fails to add the new IPv6 address.

Copying

As part of the copy request, one or more new IPv6 addresses are assigned. Correct behavior during a copy would have Windows on the virtual machine delete the existing IPv6 address, copied from the source virtual machine, and add the new IPv6 address, supplied in the copy request. However, a Windows Server 2003 virtual machine retains the existing IPv6 address and fails to add the new IPv6 address.

Potential Impact:

For creates, no IPv6 communication is possible because the new virtual machine has no IPv6 address. For copies, an IP address conflict results because the new virtual machine and the source virtual machine have a common IP address. At least one of the two virtual machines, typically the last powered on, will not communicate on the IPv6 network.

ETA:

No ETA available at this time. Microsoft acknowledges this issue. However, it is unlikely to be resolved because Microsoft announced that Windows Server 2003 support ended July 14, 2015.

Source of Issue:

A Microsoft issue prevents the System Preparation tool from properly removing the existing IPv6 address and, in the case of Windows Server 2003, from adding the new IPv6 address.

Infinicenter Console

Infinicenter Console requires manual intervention on the newly created virtual machine using the console connect feature. Console connect does not use networking for access and therefore can repair the networking configuration. The source virtual machine must be powered off before a copy may commence. The source virtual machine must remain powered off until the IPv6 addresses are corrected on the newly created virtual machine.

Workaround:

  1. For a copy, note the IPv6 address(es) on the source virtual machine.
  2. Create the virtual machine or copy the source virtual machine.
  3. When the operation completes, power on the newly created virtual machine.
  4. Console connect to the newly copied virtual machine.
  5. Following a copy, remove the common IPv6 address(es) from Windows networking.
  6. Following a create or copy, add the desired IPv6 address(es) to Windows networking.
Enterprise Cloud API

The Enterprise Cloud API requires intervention on the newly created virtual machine using the Action Virtual Machines Guest Process call. Action Virtual Machines Guest Process does not use networking for access and therefore can repair the networking configuration. The source virtual machine must be powered off before a copy may commence. The source virtual machine must remain powered off until the IPv6 addresses are corrected on the newly created virtual machine.

Use the netsh command line tool to add or remove IPv6 addresses.

netsh interface ipv6 {add | delete} address [[interface=]String] [address=]IPv6Address [[store=]{active | persistent}]

This command will add or delete an IPv6 address on a specified interface.

Parameters

[[interface=]String]

Specifies an interface name or index. The index is the zone number after the percent sign in the IPv6 address of an ipconfig response.

[address=]IPv6Address

Required. Specifies the IPv6 address to delete.

[[store=]{active | persistent}]

Specifies whether the deletion lasts only until the next boot (active) or is persistent (persistent). The default selection is persistent.

This example command deletes the address fe80::39c1:c3ba:8abc:6684 from the interface named "Local Area Connection 3" with a zone of 22 from the ipconfig example below.

netsh interface ipv6 delete address "Local Area Connection 3" fe80::39c1:c3ba:8abc:6684

netsh interface ipv6 delete address "22" fe80::39c1:c3ba:8abc:6684

Workaround:

To use netsh with the API, use the following procedure. Assume the newly created virtual machine should have IPv6 address fe80::39c1:c3ba:8abc:7684 on interface "Local Area Connection 3" or zone 22.

  1. For a copy, Get Virtual Machines by ID the source virtual machine.
  2. For a copy, note the IPv6 address(es) on the source virtual machine.
  3. Action Virtual Machines Create the virtual machine or Action Virtual Machines Create Copy the source virtual machine.
  4. When the operation completes, Action Virtual Machines Power On the newly created virtual machine.
  5. Action Virtual Machines Guest Process the following body to the newly created virtual machine to retrieve the IP configuration from the virtual machine.

    <CreateGuestProcess>

    <Interpreter></Interpreter>

    <Script>ipconfig > c:\ipconfig.txt</Script>

    </CreateGuestProcess>

  6. Get Virtual Machines Guest File with the query parameter "?path= c:\ipconfig.txt" to retrieve the IPv6 address(es) from Windows. The file should look similar to the following.

    Windows IP Configuration

    Ethernet adapter Local Area Connection 3:

    Connection-specific DNS Suffix. . : corp.com

    Link-local IPv6 Address . . . . . : fe80::39c1:c3ba:8abc:6684%22

    IPv4 Address. . . . . . . . . . . : 10.255.4.218

    Subnet Mask . . . . . . . . . . . : 255.255.255.0

    Default Gateway . . . . . . . . . : 10.255.4.1

  7. Following a copy, Action Virtual Machines Guest Process the following body to the newly created virtual machine for each common IPv6 to remove the common IPv6 address(es) from the source virtual machine noted in step 2.

    <CreateGuestProcess>

    <Interpreter></Interpreter>

    <Script>netsh interface ipv6 delete address "Local Area Connection 3" fe80::39c1:c3ba:8abc:6684</Script>

    </CreateGuestProcess>

  8. Following a create or copy, Action Virtual Machines Guest Process the following body to the newly created virtual machine to add the desired IPv6.

    <CreateGuestProcess>

    <Interpreter></Interpreter>

    <Script>netsh interface ipv6 add address "Local Area Connection 3" fe80::39c1:c3ba:8abc:7684</Script>

    </CreateGuestProcess>

  9. Repeat steps 5 and 6 to verify the IPv6 address(es) were removed or added.
  10. Action Virtual Machines Guest Process the following body to the newly created virtual machine to remove the text file from the virtual machine.

    <CreateGuestProcess>

    <Interpreter></Interpreter>

    <Script>del c:\ipconfig.txt</Script>

    </CreateGuestProcess>