RE: [!!Mass Mail]Re: Few questions about HA and IPv6
In logs I see: 2021-04-08 10:03:17,180 DEBUG [c.c.a.AlertManagerImpl] (HTTP-Dispatcher:null) (logid:) Done executing capacity updates for private ip 2021-04-08 10:03:17,180 DEBUG [c.c.a.AlertManagerImpl] (HTTP-Dispatcher:null) (logid:) Done recalculating system capacity 2021-04-08 10:03:19,583 DEBUG [c.c.h.x.r.XenServerConnectionPool] (ClusteredAgentManager Timer:ctx-a3eff58f) (logid:8760cdf3) Unable to create master connection to host(10.69.82.12) , due to org.apache.xmlrpc.XmlRpcException: Failed to read server's response: No route to host (Host unreachable) 2021-04-08 10:03:19,583 DEBUG [c.c.a.m.AgentManagerImpl] (ClusteredAgentManager Timer:ctx-a3eff58f) (logid:8760cdf3) Transition:[Resource state = Enabled, Agent event = AgentDisconnected, Host id = 10, name = xcp-ng76-u3229-03] 2021-04-08 10:03:19,589 WARN [c.c.a.m.ClusteredAgentManagerImpl] (ClusteredAgentManager Timer:ctx-a3eff58f) (logid:8760cdf3) can not load directly connected host 10(xcp-ng76-u3229-03) due to com.cloud.utils.exception.CloudRuntimeException: Unable to create master connection to host(10.69.82.12) , due to org.apache.xmlrpc.XmlRpcException: Failed to read server's response: No route to host (Host unreachable) at com.cloud.hypervisor.xenserver.resource.XenServerConnectionPool.getConnect(XenServerConnectionPool.java:168) at com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.CheckXenHostInfo(CitrixResourceBase.java:551) at com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.configure(CitrixResourceBase.java:856) at com.cloud.resource.DiscovererBase.reloadResource(DiscovererBase.java:158) at com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:705) at com.cloud.agent.manager.ClusteredAgentManagerImpl.scanDirectAgentToLoad(ClusteredAgentManagerImpl.java:225) at com.cloud.agent.manager.ClusteredAgentManagerImpl.runDirectAgentScanTimerTask(ClusteredAgentManagerImpl.java:190) at com.cloud.agent.manager.ClusteredAgentManagerImpl$DirectAgentScanTimerTask.runInContext(ClusteredAgentManagerImpl.java:241) at org.apache.cloudstack.managed.context.ManagedContextTimerTask$1.runInContext(ManagedContextTimerTask.java:30) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at org.apache.cloudstack.managed.context.ManagedContextTimerTask.run(ManagedContextTimerTask.java:32) at java.base/java.util.TimerThread.mainLoop(Timer.java:556) at java.base/java.util.TimerThread.run(Timer.java:506) Caused by: org.apache.xmlrpc.XmlRpcException: Failed to read server's response: No route to host (Host unreachable) at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:161) at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:143) at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTransport.java:69) ... 24 more Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable) at java.base/java.net.PlainSocketImpl.socketConnect(Native Method) at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:399) at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:242) ... 42 more 2021-04-08 10:03:22,113 DEBUG [o.a.c.m.PrometheusExporterServerImpl] (HTTP-Dispatcher:null) (logid:) Prometheus exporter received client request from: 10.69.82.211 2021-04-08 10:03:22,114 DEBUG [c.c.a.AlertManagerImpl] (HTTP-Dispatcher:null) (logid:) recalculating system capacity 2021-04-08 10:03:22,114 DEBUG [c.c.a.AlertManagerImpl] (HTTP-Dispatcher:null) (logid:) Executing cpu/ram capacity update But this host isn't pool master! -Original Message- From: Дикевич Евгений Александрович [mailto:evgeniy.dikev...@becloud.by] Sent: Thursday, April 8, 2021 10:02 AM To: users@cloudstack.apache.org Subject: RE: [!!Mass Mail]Re: Few questions about HA and IPv6 All other hosts in "UP" state. In hosts view I see - HA State = Disabled, HA Enabled = yes -Original Message- From: Vivek Kumar [mailto:vivek.ku...@indiqus.com.INVALID] Sent: Thursday, April 8, 2021 9:54 AM To: users@cloudstack.apache.org Subject: Re: [!!Mass Mail]Re: Few questions about HA and IPv6 When your host goes down, it takes sometime to trigger the HA o
RE: [!!Mass Mail]Re: Few questions about HA and IPv6
All other hosts in "UP" state. In hosts view I see - HA State = Disabled, HA Enabled = yes -Original Message- From: Vivek Kumar [mailto:vivek.ku...@indiqus.com.INVALID] Sent: Thursday, April 8, 2021 9:54 AM To: users@cloudstack.apache.org Subject: Re: [!!Mass Mail]Re: Few questions about HA and IPv6 When your host goes down, it takes sometime to trigger the HA on VMs, you can check logs for further investigations > On 08-Apr-2021, at 12:12 PM, Vivek Kumar wrote: > > What is the status of hosts, are rest of the hosts are showing in “UP” state > in ACS GUI? > >> On 08-Apr-2021, at 12:07 PM, Дикевич Евгений Александрович >> wrote: >> >> Hello. Thx for answer. I configured compute offering with HA enabled in it >> and with host tag "HA", in global setting I configured ha.tag = HA, on hosts >> I placed tag HA. When I shutdown host (via IPMI) I see in XCP-NG Center than >> VMs goes down, in ACS WEB UI VMs still in status running but I can't connect >> them via console. VMs didn't migrate. >> I have 4 hosts. >> >> -Original Message- >> From: Vivek Kumar [mailto:vivek.ku...@indiqus.com.INVALID] >> Sent: Wednesday, April 7, 2021 9:17 PM >> To: users@cloudstack.apache.org >> Subject: [!!Mass Mail]Re: Few questions about HA and IPv6 >> >> Hello, >> >> So in case of XenServer or XCP-NG, When we configure HA on XenServer pool, >> it’s not only migrate VMs when hosts goes offline but it’s also nominate a >> new master in pool whenever your master server goes down. So cloudStack >> connect to the pool master, So You should enable HA on XenServer pool so >> that if your host goes down, it will nominate the master again. >> >> For VM HA, you should configure compute offering with HA enabled in it, So >> whenever your VM or host goes down, CloudStack keep on checking the status >> of VM and it will trigger HA on failed host and will restart VM on another >> available host. >> >> Regards >> Vivek Kumar >> Manager - Cloud & DevOps >> >> >> >>> On 07-Apr-2021, at 6:42 PM, Дикевич Евгений Александрович >>> wrote: >>> >>> Thx Wido for explaining about IPv6. Now MB someone can help me with HA in >>> XCP-NG + ACS? >>> >>> -Original Message- >>> From: Wido den Hollander [mailto:w...@widodh.nl] >>> Sent: Tuesday, April 6, 2021 1:09 PM >>> To: users@cloudstack.apache.org; Дикевич Евгений Александрович >>> >>> Subject: Re: Few questions about HA and IPv6 >>> >>> >>> >>> On 05/04/2021 16:27, Дикевич Евгений Александрович wrote: >>>> Hi all! >>>> I am testing ACS 4.14 with XCP-NG hypervisor in my test environment and I >>>> have few questions. >>>> I have ACS 4.14 with XCP-NG 7.6 with presetup ISCSi storage. 1st question >>>> is how to configure VM HA? I created Service Offering with "HA offer" and >>>> enabled HA on pool but when I create VM I see in VM properties in Start >>>> options "Do not restart" (HA restart priority: Do not restart). I can >>>> change it but when I reboot/stop VM it reverts back to "Do not restart". I >>>> tried to configure ha.tag but it didn't help me. Mb I should smth to do >>>> else? >>>> 2nd question is how to configure IPv6 on VM? I tried to create >>>> shared network with both IPv4 and IPv6. After I created VM I saw >>>> only IPv4 address and I couldn't get IPv6 via DHCP. Same question - >>>> Mb I should smth to do else?) >>> >>> IPv6 does not work with DHCPv6. >>> >>> You need to make sure that the Router(s) in the network are sending >>> out >>> IPv6 Router Advertisements. This will make the VMs configure their NIC >>> using SLAAC. Make sure they use the MAC address. (EUI-64). >>> >>> Now CloudStack only needs to know the IPv6 subnet (/64) for the shared >>> network and then it should just work. >>> >>> Wido >>> >>>> >>>> Внимание! >>>> Это электронное письмо и все прикрепленные к нему файлы являются >>>> конфиденциальными и предназначены исключительно для использования лицом >>>> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом >>>> (лицами), которому (которым) предназначено это письмо, не копируйте и не >>>> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей
Re: [!!Mass Mail]Re: Few questions about HA and IPv6
When your host goes down, it takes sometime to trigger the HA on VMs, you can check logs for further investigations > On 08-Apr-2021, at 12:12 PM, Vivek Kumar wrote: > > What is the status of hosts, are rest of the hosts are showing in “UP” state > in ACS GUI? > >> On 08-Apr-2021, at 12:07 PM, Дикевич Евгений Александрович >> wrote: >> >> Hello. Thx for answer. I configured compute offering with HA enabled in it >> and with host tag "HA", in global setting I configured ha.tag = HA, on hosts >> I placed tag HA. When I shutdown host (via IPMI) I see in XCP-NG Center than >> VMs goes down, in ACS WEB UI VMs still in status running but I can't connect >> them via console. VMs didn't migrate. >> I have 4 hosts. >> >> -Original Message- >> From: Vivek Kumar [mailto:vivek.ku...@indiqus.com.INVALID] >> Sent: Wednesday, April 7, 2021 9:17 PM >> To: users@cloudstack.apache.org >> Subject: [!!Mass Mail]Re: Few questions about HA and IPv6 >> >> Hello, >> >> So in case of XenServer or XCP-NG, When we configure HA on XenServer pool, >> it’s not only migrate VMs when hosts goes offline but it’s also nominate a >> new master in pool whenever your master server goes down. So cloudStack >> connect to the pool master, So You should enable HA on XenServer pool so >> that if your host goes down, it will nominate the master again. >> >> For VM HA, you should configure compute offering with HA enabled in it, So >> whenever your VM or host goes down, CloudStack keep on checking the status >> of VM and it will trigger HA on failed host and will restart VM on another >> available host. >> >> Regards >> Vivek Kumar >> Manager - Cloud & DevOps >> >> >> >>> On 07-Apr-2021, at 6:42 PM, Дикевич Евгений Александрович >>> wrote: >>> >>> Thx Wido for explaining about IPv6. Now MB someone can help me with HA in >>> XCP-NG + ACS? >>> >>> -Original Message- >>> From: Wido den Hollander [mailto:w...@widodh.nl] >>> Sent: Tuesday, April 6, 2021 1:09 PM >>> To: users@cloudstack.apache.org; Дикевич Евгений Александрович >>> >>> Subject: Re: Few questions about HA and IPv6 >>> >>> >>> >>> On 05/04/2021 16:27, Дикевич Евгений Александрович wrote: Hi all! I am testing ACS 4.14 with XCP-NG hypervisor in my test environment and I have few questions. I have ACS 4.14 with XCP-NG 7.6 with presetup ISCSi storage. 1st question is how to configure VM HA? I created Service Offering with "HA offer" and enabled HA on pool but when I create VM I see in VM properties in Start options "Do not restart" (HA restart priority: Do not restart). I can change it but when I reboot/stop VM it reverts back to "Do not restart". I tried to configure ha.tag but it didn't help me. Mb I should smth to do else? 2nd question is how to configure IPv6 on VM? I tried to create shared network with both IPv4 and IPv6. After I created VM I saw only IPv4 address and I couldn't get IPv6 via DHCP. Same question - Mb I should smth to do else?) >>> >>> IPv6 does not work with DHCPv6. >>> >>> You need to make sure that the Router(s) in the network are sending >>> out >>> IPv6 Router Advertisements. This will make the VMs configure their NIC >>> using SLAAC. Make sure they use the MAC address. (EUI-64). >>> >>> Now CloudStack only needs to know the IPv6 subnet (/64) for the shared >>> network and then it should just work. >>> >>> Wido >>> Внимание! Это электронное письмо и все прикрепленные к нему файлы являются конфиденциальными и предназначены исключительно для использования лицом (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом (лицами), которому (которым) предназначено это письмо, не копируйте и не разглашайте его содержимое и удалите это сообщение и все вложения из Вашей почтовой системы. Любое несанкционированное использование, распространение, раскрытие, печать или копирование этого электронного письма и прикрепленных к нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, является незаконным и запрещено. Принимая во внимание, что передача данных посредством Интернет не является безопасной, мы не несем никакой ответственности за любой потенциальный ущерб, причиненный в результате ошибок при передаче данных или этим сообщением и прикрепленными к нему файлами. Attention! This email and all attachments to it are confidential and are intended solely for use by the person (or persons) referred to (mentioned) as the intended recipient (recipients). If you are not the intended recipient of this email, do not copy or disclose its contents and delete the message and any attachments to it from your e-mail system. Any unauthorized use, dissemination, disclosure, printing or copying of this e-mail and files attached to it, except by the intended recipient, is illegal
Re: [!!Mass Mail]Re: Few questions about HA and IPv6
What is the status of hosts, are rest of the hosts are showing in “UP” state in ACS GUI? > On 08-Apr-2021, at 12:07 PM, Дикевич Евгений Александрович > wrote: > > Hello. Thx for answer. I configured compute offering with HA enabled in it > and with host tag "HA", in global setting I configured ha.tag = HA, on hosts > I placed tag HA. When I shutdown host (via IPMI) I see in XCP-NG Center than > VMs goes down, in ACS WEB UI VMs still in status running but I can't connect > them via console. VMs didn't migrate. > I have 4 hosts. > > -Original Message- > From: Vivek Kumar [mailto:vivek.ku...@indiqus.com.INVALID] > Sent: Wednesday, April 7, 2021 9:17 PM > To: users@cloudstack.apache.org > Subject: [!!Mass Mail]Re: Few questions about HA and IPv6 > > Hello, > > So in case of XenServer or XCP-NG, When we configure HA on XenServer pool, > it’s not only migrate VMs when hosts goes offline but it’s also nominate a > new master in pool whenever your master server goes down. So cloudStack > connect to the pool master, So You should enable HA on XenServer pool so that > if your host goes down, it will nominate the master again. > > For VM HA, you should configure compute offering with HA enabled in it, So > whenever your VM or host goes down, CloudStack keep on checking the status of > VM and it will trigger HA on failed host and will restart VM on another > available host. > > Regards > Vivek Kumar > Manager - Cloud & DevOps > > > >> On 07-Apr-2021, at 6:42 PM, Дикевич Евгений Александрович >> wrote: >> >> Thx Wido for explaining about IPv6. Now MB someone can help me with HA in >> XCP-NG + ACS? >> >> -Original Message- >> From: Wido den Hollander [mailto:w...@widodh.nl] >> Sent: Tuesday, April 6, 2021 1:09 PM >> To: users@cloudstack.apache.org; Дикевич Евгений Александрович >> >> Subject: Re: Few questions about HA and IPv6 >> >> >> >> On 05/04/2021 16:27, Дикевич Евгений Александрович wrote: >>> Hi all! >>> I am testing ACS 4.14 with XCP-NG hypervisor in my test environment and I >>> have few questions. >>> I have ACS 4.14 with XCP-NG 7.6 with presetup ISCSi storage. 1st question >>> is how to configure VM HA? I created Service Offering with "HA offer" and >>> enabled HA on pool but when I create VM I see in VM properties in Start >>> options "Do not restart" (HA restart priority: Do not restart). I can >>> change it but when I reboot/stop VM it reverts back to "Do not restart". I >>> tried to configure ha.tag but it didn't help me. Mb I should smth to do >>> else? >>> 2nd question is how to configure IPv6 on VM? I tried to create shared >>> network with both IPv4 and IPv6. After I created VM I saw only IPv4 >>> address and I couldn't get IPv6 via DHCP. Same question - Mb I >>> should smth to do else?) >> >> IPv6 does not work with DHCPv6. >> >> You need to make sure that the Router(s) in the network are sending >> out >> IPv6 Router Advertisements. This will make the VMs configure their NIC using >> SLAAC. Make sure they use the MAC address. (EUI-64). >> >> Now CloudStack only needs to know the IPv6 subnet (/64) for the shared >> network and then it should just work. >> >> Wido >> >>> >>> Внимание! >>> Это электронное письмо и все прикрепленные к нему файлы являются >>> конфиденциальными и предназначены исключительно для использования лицом >>> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом >>> (лицами), которому (которым) предназначено это письмо, не копируйте и не >>> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей >>> почтовой системы. Любое несанкционированное использование, распространение, >>> раскрытие, печать или копирование этого электронного письма и прикрепленных >>> к нему файлов, кроме как лицом (лицами) которому (которым) они >>> предназначены, является незаконным и запрещено. Принимая во внимание, что >>> передача данных посредством Интернет не является безопасной, мы не несем >>> никакой ответственности за любой потенциальный ущерб, причиненный в >>> результате ошибок при передаче данных или этим сообщением и прикрепленными >>> к нему файлами. >>> >>> Attention! >>> This email and all attachments to it are confidential and are intended >>> solely for use by the person (or persons) referred to (mentioned) as the >>> intended recipient (recipients). If you are not the intended recipient of >>> this email, do not copy or disclose its contents and delete the message and >>> any attachments to it from your e-mail system. Any unauthorized use, >>> dissemination, disclosure, printing or copying of this e-mail and files >>> attached to it, except by the intended recipient, is illegal and is >>> prohibited. Taking into account that data transmission via Internet is not >>> secure, we assume no responsibility for any potential damage caused by data >>> transmission errors or this message and the files attached to it. >>> >
RE: [!!Mass Mail]Re: Few questions about HA and IPv6
Hello. Thx for answer. I configured compute offering with HA enabled in it and with host tag "HA", in global setting I configured ha.tag = HA, on hosts I placed tag HA. When I shutdown host (via IPMI) I see in XCP-NG Center than VMs goes down, in ACS WEB UI VMs still in status running but I can't connect them via console. VMs didn't migrate. I have 4 hosts. -Original Message- From: Vivek Kumar [mailto:vivek.ku...@indiqus.com.INVALID] Sent: Wednesday, April 7, 2021 9:17 PM To: users@cloudstack.apache.org Subject: [!!Mass Mail]Re: Few questions about HA and IPv6 Hello, So in case of XenServer or XCP-NG, When we configure HA on XenServer pool, it’s not only migrate VMs when hosts goes offline but it’s also nominate a new master in pool whenever your master server goes down. So cloudStack connect to the pool master, So You should enable HA on XenServer pool so that if your host goes down, it will nominate the master again. For VM HA, you should configure compute offering with HA enabled in it, So whenever your VM or host goes down, CloudStack keep on checking the status of VM and it will trigger HA on failed host and will restart VM on another available host. Regards Vivek Kumar Manager - Cloud & DevOps > On 07-Apr-2021, at 6:42 PM, Дикевич Евгений Александрович > wrote: > > Thx Wido for explaining about IPv6. Now MB someone can help me with HA in > XCP-NG + ACS? > > -Original Message- > From: Wido den Hollander [mailto:w...@widodh.nl] > Sent: Tuesday, April 6, 2021 1:09 PM > To: users@cloudstack.apache.org; Дикевич Евгений Александрович > > Subject: Re: Few questions about HA and IPv6 > > > > On 05/04/2021 16:27, Дикевич Евгений Александрович wrote: >> Hi all! >> I am testing ACS 4.14 with XCP-NG hypervisor in my test environment and I >> have few questions. >> I have ACS 4.14 with XCP-NG 7.6 with presetup ISCSi storage. 1st question is >> how to configure VM HA? I created Service Offering with "HA offer" and >> enabled HA on pool but when I create VM I see in VM properties in Start >> options "Do not restart" (HA restart priority: Do not restart). I can >> change it but when I reboot/stop VM it reverts back to "Do not restart". I >> tried to configure ha.tag but it didn't help me. Mb I should smth to do else? >> 2nd question is how to configure IPv6 on VM? I tried to create shared >> network with both IPv4 and IPv6. After I created VM I saw only IPv4 >> address and I couldn't get IPv6 via DHCP. Same question - Mb I >> should smth to do else?) > > IPv6 does not work with DHCPv6. > > You need to make sure that the Router(s) in the network are sending > out > IPv6 Router Advertisements. This will make the VMs configure their NIC using > SLAAC. Make sure they use the MAC address. (EUI-64). > > Now CloudStack only needs to know the IPv6 subnet (/64) for the shared > network and then it should just work. > > Wido > >> >> Внимание! >> Это электронное письмо и все прикрепленные к нему файлы являются >> конфиденциальными и предназначены исключительно для использования лицом >> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом >> (лицами), которому (которым) предназначено это письмо, не копируйте и не >> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей >> почтовой системы. Любое несанкционированное использование, распространение, >> раскрытие, печать или копирование этого электронного письма и прикрепленных >> к нему файлов, кроме как лицом (лицами) которому (которым) они >> предназначены, является незаконным и запрещено. Принимая во внимание, что >> передача данных посредством Интернет не является безопасной, мы не несем >> никакой ответственности за любой потенциальный ущерб, причиненный в >> результате ошибок при передаче данных или этим сообщением и прикрепленными к >> нему файлами. >> >> Attention! >> This email and all attachments to it are confidential and are intended >> solely for use by the person (or persons) referred to (mentioned) as the >> intended recipient (recipients). If you are not the intended recipient of >> this email, do not copy or disclose its contents and delete the message and >> any attachments to it from your e-mail system. Any unauthorized use, >> dissemination, disclosure, printing or copying of this e-mail and files >> attached to it, except by the intended recipient, is illegal and is >> prohibited. Taking into account that data transmission via Internet is not >> secure, we assume no responsibility for any potential damage caused by data >> transmission errors or this message and the files attached to it. >>
