none
Hyper-v обработка отказа (репликация) Debian RRS feed

  • Вопрос

  • Доброго времени суток! Есть основной ЦОД и Реплика! С виртуалками на винде проблем нет отработка на отказ проходит на ура, а вот с линукс машинами (Debian) проблема, а именно с сетью! У меня между ЦОД-и поднят EoIP, проблем с IP-ми не наблюдается! Проблема в шлюзах! Есть какое то стандартное решение от виндовс? Пока на линукс машинах использую скрипт для определения валидности шлюза!

    И еще постоянно сыпется ошибка по поводу служб интеграции! 

    - System
    - Provider
    [ Name] Microsoft-Windows-Hyper-V-VmSwitch
    [ Guid] {67DC0D66-3695-47C0-9642-33F76F7BD7AD}
    EventID 27
    Version 0
    Level 3
    Task 1019
    Opcode 0
    Keywords 0x8000000000000000
    - TimeCreated
    [ SystemTime] 2013-06-10T20:59:48.163429700Z
    EventRecordID 65101
    Correlation
    - Execution
    [ ProcessID] 4
    [ ThreadID] 264
    Channel System
    Computer Storage-server2.skillserver.com.ua
    - Security
    [ UserID] S-1-5-18
    - EventData
    VMNameLen 15
    VMName Debian 7 — тест
    VMIdLen 36
    VMId 32E85AE1-BD86-42DC-BE06-88917D68E43D
    ServerVersionLen 3
    ServerVersion 4.0
    ClientVersionLen 3
    ClientVersion 3.2

    Networking driver in Debian 7  loaded but has a different version from the server. Server version 4.0  Client version 3.2 (Virtual machine ID 32E85AE1-BD86-42DC-BE06-88917D68E43D). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

    10 июня 2013 г. 22:52

Ответы

  • Компоненты интеграции, конечно, стоит обновить до 3.4, а в целом уведомление можно игнорировать.

    Касается шлюзов - используйте DHCP, разрешение имен посредством DNS и относительно короткий TTL в DNS.

    • Помечено в качестве ответа Sergey_kill 11 июня 2013 г. 8:16
    11 июня 2013 г. 5:54
    Модератор
  • И еще постоянно сыпется ошибка по поводу служб интеграции! 

    - System
    - Provider
    [ Name] Microsoft-Windows-Hyper-V-VmSwitch
    [ Guid] {67DC0D66-3695-47C0-9642-33F76F7BD7AD}
    EventID 27
    Version 0
    Level 3
    Task 1019
    Opcode 0
    Keywords 0x8000000000000000
    - TimeCreated
    [ SystemTime] 2013-06-10T20:59:48.163429700Z
    EventRecordID 65101
    Correlation
    - Execution
    [ ProcessID] 4
    [ ThreadID] 264
    Channel System
    Computer ZZZZZZZZZz
    - Security
    [ UserID] S-1-5-18
    - EventData
    VMNameLen 15
    VMName Debian 7 — тест
    VMIdLen 36
    VMId 32E85AE1-BD86-42DC-BE06-88917D68E43D
    ServerVersionLen 3
    ServerVersion 4.0
    ClientVersionLen 3
    ClientVersion 3.2

    Networking driver in Debian 7  loaded but has a different version from the server. Server version 4.0  Client version 3.2 (Virtual machine ID 32E85AE1-BD86-42DC-BE06-88917D68E43D). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

    ~

    http://social.technet.microsoft.com/Forums/en-US/linuxintegrationservices/thread/c9019f84-2375-4196-ac8d-4eb7da66d5ea

    ==

    This error occurs because the ( {LIS version in Debian 7.0, Ubuntu 12.04} VVM: and EL 6.4 ) doesn't know about Windows Server 2012 Hyper-V.  But the error message is bogus because the LIS is compatible with WS 2012 Hyper-V.   Everything is working properly and you can ignore the message.  The product team is looking at how we can prevent this error from occurring in the future when new versions of Hyper-V come out.


    Michael Kelley, Lead Program Manager, Open Source Technology Center

    ~

    ~

    ==

    ~

    +

    http://social.technet.microsoft.com/Forums/en-US/linuxintegrationservices/thread/31a57862-1371-41af-9839-92dc3de1a558/

    ==

    You can ignore the message about "NICs are degraded".  The error is spurious.  Going forward, we're trying to get some changes made so this error goes away.

    Michael Kelley, Lead Program Manager, Open Source Technology Center

    ==

    ~



    • Изменено Victor Miasnikov 11 июня 2013 г. 8:07
    • Помечено в качестве ответа Sergey_kill 11 июня 2013 г. 8:16
    11 июня 2013 г. 7:58

Все ответы

  • Компоненты интеграции, конечно, стоит обновить до 3.4, а в целом уведомление можно игнорировать.

    Касается шлюзов - используйте DHCP, разрешение имен посредством DNS и относительно короткий TTL в DNS.

    • Помечено в качестве ответа Sergey_kill 11 июня 2013 г. 8:16
    11 июня 2013 г. 5:54
    Модератор
  • И еще постоянно сыпется ошибка по поводу служб интеграции! 

    - System
    - Provider
    [ Name] Microsoft-Windows-Hyper-V-VmSwitch
    [ Guid] {67DC0D66-3695-47C0-9642-33F76F7BD7AD}
    EventID 27
    Version 0
    Level 3
    Task 1019
    Opcode 0
    Keywords 0x8000000000000000
    - TimeCreated
    [ SystemTime] 2013-06-10T20:59:48.163429700Z
    EventRecordID 65101
    Correlation
    - Execution
    [ ProcessID] 4
    [ ThreadID] 264
    Channel System
    Computer ZZZZZZZZZz
    - Security
    [ UserID] S-1-5-18
    - EventData
    VMNameLen 15
    VMName Debian 7 — тест
    VMIdLen 36
    VMId 32E85AE1-BD86-42DC-BE06-88917D68E43D
    ServerVersionLen 3
    ServerVersion 4.0
    ClientVersionLen 3
    ClientVersion 3.2

    Networking driver in Debian 7  loaded but has a different version from the server. Server version 4.0  Client version 3.2 (Virtual machine ID 32E85AE1-BD86-42DC-BE06-88917D68E43D). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu.

    ~

    http://social.technet.microsoft.com/Forums/en-US/linuxintegrationservices/thread/c9019f84-2375-4196-ac8d-4eb7da66d5ea

    ==

    This error occurs because the ( {LIS version in Debian 7.0, Ubuntu 12.04} VVM: and EL 6.4 ) doesn't know about Windows Server 2012 Hyper-V.  But the error message is bogus because the LIS is compatible with WS 2012 Hyper-V.   Everything is working properly and you can ignore the message.  The product team is looking at how we can prevent this error from occurring in the future when new versions of Hyper-V come out.


    Michael Kelley, Lead Program Manager, Open Source Technology Center

    ~

    ~

    ==

    ~

    +

    http://social.technet.microsoft.com/Forums/en-US/linuxintegrationservices/thread/31a57862-1371-41af-9839-92dc3de1a558/

    ==

    You can ignore the message about "NICs are degraded".  The error is spurious.  Going forward, we're trying to get some changes made so this error goes away.

    Michael Kelley, Lead Program Manager, Open Source Technology Center

    ==

    ~



    • Изменено Victor Miasnikov 11 июня 2013 г. 8:07
    • Помечено в качестве ответа Sergey_kill 11 июня 2013 г. 8:16
    11 июня 2013 г. 7:58