Вход на сайт

Просмотр новости

Найдите то, что Вас интересует

The Case of Partitioned Networks after Networking Changes in #AzureStackHCI

Дата публикации: 16-09-2019 18:33:22

Categories: HyperConverged, S2DTags: Azure Stack HCI, Networking, Partitioned Network, S2D, Storage Spaces DirectHey Checkyourlogs Fans, First off if you haven’t had a chance make sure you come and join us in our Azure Stack HCI (Storage Spaces Direct) Community at http://slack.storagespacesdirect.com . There are currently almost 1000 members on the group, and we have the best support in the world there for Azure Stack HCI. I had […](Read more...)

Основное содержимое страницы с новостью.

Hey Checkyourlogs Fans,

First off if you haven’t had a chance make sure you come and join us in our Azure Stack HCI (Storage Spaces Direct) Community at http://slack.storagespacesdirect.com . There are currently almost 1000 members on the group, and we have the best support in the world there for Azure Stack HCI.

I had an issue that I had seen before, and instead of banging my head against the wall, I thought I would reach out and ask my friends.


Within a matter of minutes, I had multiple replies from the community.

Anyways, to my problem à Here is what I posted:

Has anyone seen this before? My network team at one of my sites was upgrading the firmware on some switches and rebooted the switches that my management ports were connected. Everything stayed online in my cluster but then it gets stuck in partitioned state. The only way I have found to fix this is to reboot one of the nodes. Anyone else sees this. Things seem to work ok I can RDP via that IP into both servers. Close Failover Manager and reopen this persists until the reboot. I’ve seen this more than once now when the network drops off for the MGMT adapters. This is a 2-Node S2D Cluster direct connect for the other networks that is why they are all online.


I have seen this before, and I would reboot a node, and it would fix itself.

Because of this fantastic community and our of the All-Star member Jan-Tore Pedersen ( https://jtpedersen.com/), told me just to disable and enable the MGMT Virtual adapter instead of rebooting. He confirmed that this fix works in Server 2016 as well.

Thanks to the Storage Spaces Direct Slack community for the assist on this one.

Love you guys and gals,

Dave

Схожие новости

#Наименование новостиТональностьИнформативностьДата публикации
1Navigating Network Configuration Challenges in Hyper-V Cluster Management013.9403-02-2024
2Configuring Networking for #StorageSpacesDirect with #SCVMM #PowerShell #MVPBuzz012.0102-02-2018
3Storage Failures in Hyper-V Cluster Management013.9104-02-2024
4Optimizing Resource Allocation in Hyper-V Clusters014.2105-02-2024
5The Case of the broken network on an Upgrade of Windows Server 2012 R2 to Windows Server 2019 – #HyperV #WindowsadminCenter014.8308-09-2018
6Mastering Cluster Quorum Management in Hyper-V Clusters: Ensuring Resilience and Availability011.1902-02-2024
7The Case of the Poor Internet Connection #MVPHour #Canitpro09.209-11-2017
8#ADFS and Azure AD Authentication with a #Netscaler 11.1 acting as a Proxy09.9823-02-2018
9SQL Server в гибридных облачных средах (видео)0315-05-2014
10MVPDays V-Conf Attendee Questions – #MVPBuzz #MVPHour @MVPAward #Canitpro011.4318-01-2018

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 12.33. Источник: www.checkyourlogs.net.