"Non-standard networking settings" - Hyper-v Upgrade | Nutanix Community
Skip to main content
Question

"Non-standard networking settings" - Hyper-v Upgrade

D
Forum|alt.badge.img+2

Hello

I am attempting to upgrade a Hyper-v 2012 R2 Cluster to 2016. I've completed the necessary Kerberos settings, however I am receiving an error during the pre-upgrade check

"Non-Standard Network Settings, cannot proceed with hypervisor upgrade"

This makes me sad 😪 the KB number referenced does not exist so I'm a bit of a loss on what to do next. Is there anyway to find out what it thinks the non-standard settings are - or perhaps work out what it think standard should be?

TIA

Dave
1 Attachments
    This topic has been closed for comments

    3 replies

    RichardsonPorto
    Nutanix Employee
    Forum|alt.badge.img+5
    Hi @davidhood

    Can you confirm how many teaming you have configured in your cluster and also the teaming mode.

    From any CVM you may can run the following command "winsh get-netlbfoteam" and post the output here?
    Richardson Porto - LinkedIn: http://linkedin.com/in/richardsonporto
    D
    Forum|alt.badge.img+2
    • davidhood
    • Author
    • Voyager
    • 2 replies
    • June 27, 2019
    Hi

    it was having an lacp switch that caused it to fail. Changing that to switch independent sorted.

    thanks
    RichardsonPorto
    Nutanix Employee
    Forum|alt.badge.img+5
    Hi @davidhood

    Exactly, we do not support upgrade if you have more than one NIC teaming or are using LACP, and these restrictions you can found on KB6468 as described on pre-upgrade checks:

    Error message: Non-standard network settings, cannot proceed with hypervisor upgrade
    Solution: Make sure that the current networking configuration on Hyper-V hosts meets following requirements:
    • Only one network team is created;
    • Network team is configured in 'SwitchIndependent' mode. For example, the below snippet demonstrates that there is a network team confgured in LACP mode, which is not currently supported for Hyper-V upgrade:
    Richardson Porto - LinkedIn: http://linkedin.com/in/richardsonporto
    Terms & Conditions