none
Hyper-V Server 2016 - HNV 1.0 - configuration lost after a while

    Pergunta

  • Hi Expert,

    Background and issue:

    1. Hypervisor: Hyper-V Server 2016 (note that it's not Windows Server 2016)
    2. Deployment Model:Standalone
    3. Host Network: NIC teaming is used, and 2 physical NICs
    4. Hyper-V Network Virtualization: 1.0 (just consider it's supported by Hyper-V Server 2016 since both HNV1 & HNV2 are supported by Windows Server 2016)
    5. Want to implement network isolation by using HNV 1.0
    6. run the following PowerShell command: 
    New-NetVirtualizationLookupRecord -VirtualSubnetID "5001" -CustomerAddress "10.156.1.1" -ProviderAddress "172.31.153.101" -MACAddress "00155D971F27" -Rule "TranslationMethodEncap"

        7. after that, I can view the lookup record by running get-NetVirtualizationLookupRecord, but almost 3-5 minutes later, run get-NetVirtualizationLookupRecord again, no any output, seems that the configuration is totally lost.

    Thanks in advance!


    amoschb

    quinta-feira, 28 de junho de 2018 11:14

Todas as Respostas

  • Hi,

    Thanks for your question.

    I am currently performing research on this issue and will get back to you as soon as possible. I appreciate your patience.

    If you have any updates during this process, please feel free to let me know.

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    sexta-feira, 29 de junho de 2018 10:14
  • Thanks very much for your support, if you need to troubleshoot in my environment, pls feel free to let me know:)

    amoschb

    quarta-feira, 11 de julho de 2018 10:45
  • Hi Amoschb,

    I’m very sorry for my delay.

    For now, I couldn't find more clue about this issue.

    If this issue persists, I would suggest you contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue. In addition, if the issue has been proved as system flaw, the consulting fee would be refund. You may find phone number for your region accordingly from the link below:

    https://support.microsoft.com/en-us/gp/customer-service-phone-numbers

    Meanwhile, I'll follow up this thread. If there’s any update, I’ll post it here as soon as possible.

    Sorry for the inconvenience and thank you for your understanding and patience. Highly appreciate your successive effort and time.

    Best regards,    

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    sábado, 21 de julho de 2018 07:54