{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover/",
        "slug": "dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover",
        "url": "https://update.dsesecurity.com/updates/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover/"
        },
        "title": "Keep Linux guest adapter identity stable during cluster failover",
        "summary": "What network-adapter settings should be reviewed before failing over a Linux VM?",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "identity-cloud",
            "label": "Identity & cloud",
            "alt": "Governed cloud identity system with connected service and lifecycle nodes.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-09-08T18:15:07+00:00",
        "modified_at": "2026-09-08T18:23:27+00:00",
        "reviewed_on": "2026-09-08",
        "reading_minutes": 1,
        "word_count": 202,
        "potentially_affected": "Administrators operating Linux VMs on Hyper-V failover clusters.",
        "dse_recommendation": "Record the expected guest interface names and addresses alongside the configured virtual adapters.",
        "primary_source": {
            "name": "Best Practices for running Linux on Hyper-V",
            "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/Best-Practices-for-running-Linux-on-Hyper-V",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<h2>Source facts</h2>\n<p>Microsoft recommends a static MAC address for every virtual adapter of a clustered Linux VM. Some Linux versions can lose network configuration after failover if a different MAC address is assigned. Its Linux guidance also recommends the Hyper-V-specific virtual Ethernet adapter. Mixing legacy and Hyper-V-specific adapters can produce unexpected interface names, so Microsoft advises removing legacy adapters when using the Hyper-V-specific adapter. <a href=\"https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/Best-Practices-for-running-Linux-on-Hyper-V\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft documentation</a>.</p>\n<h2>Applicability</h2>\n<p>Identify the Linux distribution and release, guest integration components, adapter types, MAC assignments, and network configuration files. Check the distribution-specific support guidance before changing guest networking.</p>\n<h2>DSE recommendation</h2>\n<p>Record the expected guest interface names and addresses alongside the configured virtual adapters. Have the Linux and virtualization owners review the mapping and approve any removal of an unused legacy adapter. Define a recovery route that does not depend solely on the interface being changed.</p>\n<h2>Verification</h2>\n<p>Test a controlled cluster move and compare the guest’s adapter identities and connectivity before and afterward. Include a guest restart and an application transaction using the intended interface. Record an unexpected rename or missing network configuration as a failure to resolve before scheduling routine failover operations.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/Best-Practices-for-running-Linux-on-Hyper-V\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Best Practices for running Linux on Hyper-V</a>. Source reviewed September 8, 2026.</p>",
        "content_text": "Source facts\nMicrosoft recommends a static MAC address for every virtual adapter of a clustered Linux VM. Some Linux versions can lose network configuration after failover if a different MAC address is assigned. Its Linux guidance also recommends the Hyper-V-specific virtual Ethernet adapter. Mixing legacy and Hyper-V-specific adapters can produce unexpected interface names, so Microsoft advises removing legacy adapters when using the Hyper-V-specific adapter. Microsoft documentation.\nApplicability\nIdentify the Linux distribution and release, guest integration components, adapter types, MAC assignments, and network configuration files. Check the distribution-specific support guidance before changing guest networking.\nDSE recommendation\nRecord the expected guest interface names and addresses alongside the configured virtual adapters. Have the Linux and virtualization owners review the mapping and approve any removal of an unused legacy adapter. Define a recovery route that does not depend solely on the interface being changed.\nVerification\nTest a controlled cluster move and compare the guest’s adapter identities and connectivity before and afterward. Include a guest restart and an application transaction using the intended interface. Record an unexpected rename or missing network configuration as a failure to resolve before scheduling routine failover operations.\nOfficial references\nMicrosoft Learn: Best Practices for running Linux on Hyper-V. Source reviewed September 8, 2026.",
        "content_markdown": "## Source facts\n\nMicrosoft recommends a static MAC address for every virtual adapter of a clustered Linux VM. Some Linux versions can lose network configuration after failover if a different MAC address is assigned. Its Linux guidance also recommends the Hyper-V-specific virtual Ethernet adapter. Mixing legacy and Hyper-V-specific adapters can produce unexpected interface names, so Microsoft advises removing legacy adapters when using the Hyper-V-specific adapter. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/Best-Practices-for-running-Linux-on-Hyper-V).\n\n## Applicability\n\nIdentify the Linux distribution and release, guest integration components, adapter types, MAC assignments, and network configuration files. Check the distribution-specific support guidance before changing guest networking.\n\n## DSE recommendation\n\nRecord the expected guest interface names and addresses alongside the configured virtual adapters. Have the Linux and virtualization owners review the mapping and approve any removal of an unused legacy adapter. Define a recovery route that does not depend solely on the interface being changed.\n\n## Verification\n\nTest a controlled cluster move and compare the guest’s adapter identities and connectivity before and afterward. Include a guest restart and an application transaction using the intended interface. Record an unexpected rename or missing network configuration as a failure to resolve before scheduling routine failover operations.\n\n## Official references\n\n[Microsoft Learn: Best Practices for running Linux on Hyper-V](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/Best-Practices-for-running-Linux-on-Hyper-V). Source reviewed September 8, 2026."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-08"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Keep Linux guest adapter identity stable during cluster failover",
                        "item": "https://update.dsesecurity.com/updates/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover/",
                "headline": "Keep Linux guest adapter identity stable during cluster failover",
                "description": "What network-adapter settings should be reviewed before failing over a Linux VM?",
                "abstract": "What network-adapter settings should be reviewed before failing over a Linux VM?",
                "articleBody": "Source facts\nMicrosoft recommends a static MAC address for every virtual adapter of a clustered Linux VM. Some Linux versions can lose network configuration after failover if a different MAC address is assigned. Its Linux guidance also recommends the Hyper-V-specific virtual Ethernet adapter. Mixing legacy and Hyper-V-specific adapters can produce unexpected interface names, so Microsoft advises removing legacy adapters when using the Hyper-V-specific adapter. Microsoft documentation.\nApplicability\nIdentify the Linux distribution and release, guest integration components, adapter types, MAC assignments, and network configuration files. Check the distribution-specific support guidance before changing guest networking.\nDSE recommendation\nRecord the expected guest interface names and addresses alongside the configured virtual adapters. Have the Linux and virtualization owners review the mapping and approve any removal of an unused legacy adapter. Define a recovery route that does not depend solely on the interface being changed.\nVerification\nTest a controlled cluster move and compare the guest’s adapter identities and connectivity before and afterward. Include a guest restart and an application transaction using the intended interface. Record an unexpected rename or missing network configuration as a failure to resolve before scheduling routine failover operations.\nOfficial references\nMicrosoft Learn: Best Practices for running Linux on Hyper-V. Source reviewed September 8, 2026.",
                "datePublished": "2026-09-08T18:15:07+00:00",
                "dateModified": "2026-09-08T18:23:27+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-124-keep-linux-guest-adapter-identity-stable-during-cluster-failover/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Keep Linux guest adapter identity stable during cluster failover"
                },
                "articleSection": [
                    "IT",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "IT",
                    "Networks & Infrastructure",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 202,
                "timeRequired": "PT1M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Best Practices for running Linux on Hyper-V",
                    "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/Best-Practices-for-running-Linux-on-Hyper-V"
                }
            }
        ]
    }
}