Re: Network Issue with Cluster

2024-03-01 Thread Wei ZHOU
If you use shared network, it is definitely a network issue, as Cloudstack
only provides dns/dhcp/userdata service for shared networks.

-Wei


On Friday, March 1, 2024, Bharat Bhushan Saini
 wrote:

> Hi Jayanth,
>
>
>
> As per my analysis, I think some latches has been with cloudstack. This is
> why because the IP on MS is working file but the IP which is allocated to
> the VM or cluster having issue. It is dropping the ICMP.
>
>
>
> Thanks and Regards,
>
> Bharat Saini
>
>
>
> [image: signature_3250556292]
>
>
>
>
>


Re: Network Issue with Cluster

2024-03-01 Thread Bharat Bhushan Saini
Hi Jayanth,

As per my analysis, I think some latches has been with cloudstack. This is why 
because the IP on MS is working file but the IP which is allocated to the VM or 
cluster having issue. It is dropping the ICMP.

Thanks and Regards,
Bharat Saini

[signature_3250556292]

From: Jayanth Babu A 
Date: Friday, 1 March 2024 at 8:59 PM
To: users@cloudstack.apache.org 
Subject: Re: Network Issue with Cluster
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


I think this has something to do with your network and not CloudStack. Let us 
know what you find after the analysis.


Thanks,
Jayanth

From: Bharat Bhushan Saini 
Sent: Friday, March 1, 2024 6:02:09 PM
To: users@cloudstack.apache.org 
Subject: Re: Network Issue with Cluster


Hi Jayanth,



My point is not among the vm’s. Concern in the shared network, as what the IP 
allocated in that range is having latency.

Day before yesterday, the network is working fine.



Thanks and Regards,

Bharat Saini



[signature_1001564804]



From: Jayanth Babu A 
Date: Friday, 1 March 2024 at 5:33 PM
To: users@cloudstack.apache.org 
Subject: Re: Network Issue with Cluster

EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

Are you saying that you're observing the latency among the VMs in the same 
network?


Thanks,
Jayanth


From: Bharat Bhushan Saini 
Sent: Friday, March 1, 2024 5:20:22 pm
To: users@cloudstack.apache.org 
Subject: Network Issue with Cluster

Hi All,

Yesterday cloudstack deployment is running fine. Today I encountered an issue 
in the cloudstack 4.18.1.

The connectivity of the VM’s in the cloudstack dashboard having latches eg 
control and worker node. I also restarted the network but the issue is persist. 
Sharing the ping status of control node below,


PING 10.x.x.185 (10.x.x.185): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

Request timeout for icmp_seq 6

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

Request timeout for icmp_seq 9

64 bytes from 10.x.x.185: icmp_seq=10 ttl=63 time=4.954 ms

64 bytes from 10.x.x.185: icmp_seq=11 ttl=63 time=6.642 ms

Request timeout for icmp_seq 12

Request timeout for icmp_seq 13

Request timeout for icmp_seq 14

Request timeout for icmp_seq 15

Request timeout for icmp_seq 16

Request timeout for icmp_seq 17

^C

--- 10.x.x.185 ping statistics ---

19 packets transmitted, 2 packets received, 89.5% packet loss

round-trip min/avg/max/stddev = 4.954/5.798/6.642/0.844 ms

Ping status of MS as MS and KVM running on same machine as below,

PING 10.x.x.101 (10.1.10.101): 56 data bytes

64 bytes from 10.x.x.101: icmp_seq=0 ttl=63 time=9.528 ms

64 bytes from 10.x.x.101: icmp_seq=1 ttl=63 time=6.201 ms

64 bytes from 10.x.x.101: icmp_seq=2 ttl=63 time=8.534 ms

64 bytes from 10.x.x.101: icmp_seq=3 ttl=63 time=12.364 ms

64 bytes from 10.x.x.101: icmp_seq=4 ttl=63 time=12.948 ms

64 bytes from 10.x.x.101: icmp_seq=5 ttl=63 time=13.043 ms

^C

--- 10.x.x.101 ping statistics ---

6 packets transmitted, 6 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 6.201/10.436/13.043/2.556 ms


Thanks and Regards,
Bharat Saini

[signature_1700367617]

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Disclaimer *** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION 
intended solely for the use of the addressee(s). If you are not the intended 
recipient, please notify the sender by e-mail and delete the original message. 
Further, you are not authorised to copy, disclose, or distribute this e-mail or 
its contents to any other person and any such actions are unlawful and strictly 
prohibited. This e-mail may contain viruses. NxtGen Datacenter & Cloud 
Technologies Private Ltd (“NxtGen”) has taken every reasonable precaution to 
minimize this risk but is not liable for any damage you may sustain as a result 
of any virus in this e-mail. You should carry out 

Re: Network Issue with Cluster

2024-03-01 Thread Jayanth Babu A
I think this has something to do with your network and not CloudStack. Let us 
know what you find after the analysis.


Thanks,
Jayanth

From: Bharat Bhushan Saini 
Sent: Friday, March 1, 2024 6:02:09 PM
To: users@cloudstack.apache.org 
Subject: Re: Network Issue with Cluster


Hi Jayanth,



My point is not among the vm’s. Concern in the shared network, as what the IP 
allocated in that range is having latency.

Day before yesterday, the network is working fine.



Thanks and Regards,

Bharat Saini



[signature_1001564804]



From: Jayanth Babu A 
Date: Friday, 1 March 2024 at 5:33 PM
To: users@cloudstack.apache.org 
Subject: Re: Network Issue with Cluster

EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

Are you saying that you're observing the latency among the VMs in the same 
network?


Thanks,
Jayanth


From: Bharat Bhushan Saini 
Sent: Friday, March 1, 2024 5:20:22 pm
To: users@cloudstack.apache.org 
Subject: Network Issue with Cluster

Hi All,

Yesterday cloudstack deployment is running fine. Today I encountered an issue 
in the cloudstack 4.18.1.

The connectivity of the VM’s in the cloudstack dashboard having latches eg 
control and worker node. I also restarted the network but the issue is persist. 
Sharing the ping status of control node below,


PING 10.x.x.185 (10.x.x.185): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

Request timeout for icmp_seq 6

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

Request timeout for icmp_seq 9

64 bytes from 10.x.x.185: icmp_seq=10 ttl=63 time=4.954 ms

64 bytes from 10.x.x.185: icmp_seq=11 ttl=63 time=6.642 ms

Request timeout for icmp_seq 12

Request timeout for icmp_seq 13

Request timeout for icmp_seq 14

Request timeout for icmp_seq 15

Request timeout for icmp_seq 16

Request timeout for icmp_seq 17

^C

--- 10.x.x.185 ping statistics ---

19 packets transmitted, 2 packets received, 89.5% packet loss

round-trip min/avg/max/stddev = 4.954/5.798/6.642/0.844 ms

Ping status of MS as MS and KVM running on same machine as below,

PING 10.x.x.101 (10.1.10.101): 56 data bytes

64 bytes from 10.x.x.101: icmp_seq=0 ttl=63 time=9.528 ms

64 bytes from 10.x.x.101: icmp_seq=1 ttl=63 time=6.201 ms

64 bytes from 10.x.x.101: icmp_seq=2 ttl=63 time=8.534 ms

64 bytes from 10.x.x.101: icmp_seq=3 ttl=63 time=12.364 ms

64 bytes from 10.x.x.101: icmp_seq=4 ttl=63 time=12.948 ms

64 bytes from 10.x.x.101: icmp_seq=5 ttl=63 time=13.043 ms

^C

--- 10.x.x.101 ping statistics ---

6 packets transmitted, 6 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 6.201/10.436/13.043/2.556 ms


Thanks and Regards,
Bharat Saini

[signature_1700367617]

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Disclaimer *** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION 
intended solely for the use of the addressee(s). If you are not the intended 
recipient, please notify the sender by e-mail and delete the original message. 
Further, you are not authorised to copy, disclose, or distribute this e-mail or 
its contents to any other person and any such actions are unlawful and strictly 
prohibited. This e-mail may contain viruses. NxtGen Datacenter & Cloud 
Technologies Private Ltd (“NxtGen”) has taken every reasonable precaution to 
minimize this risk but is not liable for any damage you may sustain as a result 
of any virus in this e-mail. You should carry out your own virus checks before 
opening the e-mail or attachment. NxtGen reserves the right to monitor and 
review the content of all messages sent to or from this e-mail address. 
Messages sent to or from this e-mail address may be stored on the NxtGen e-mail 
system. *** End of Disclaimer ***NXTGEN***

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloud

Re: Network Issue with Cluster

2024-03-01 Thread Bharat Bhushan Saini
Hi Jayanth,

My point is not among the vm’s. Concern in the shared network, as what the IP 
allocated in that range is having latency.
Day before yesterday, the network is working fine.

Thanks and Regards,
Bharat Saini

[signature_1001564804]

From: Jayanth Babu A 
Date: Friday, 1 March 2024 at 5:33 PM
To: users@cloudstack.apache.org 
Subject: Re: Network Issue with Cluster
EXTERNAL EMAIL: Please verify the sender email address before taking any 
action, replying, clicking any link or opening any attachment.


Hello Bharat,

Are you saying that you're observing the latency among the VMs in the same 
network?


Thanks,
Jayanth


From: Bharat Bhushan Saini 
Sent: Friday, March 1, 2024 5:20:22 pm
To: users@cloudstack.apache.org 
Subject: Network Issue with Cluster

Hi All,

Yesterday cloudstack deployment is running fine. Today I encountered an issue 
in the cloudstack 4.18.1.

The connectivity of the VM’s in the cloudstack dashboard having latches eg 
control and worker node. I also restarted the network but the issue is persist. 
Sharing the ping status of control node below,


PING 10.x.x.185 (10.x.x.185): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

Request timeout for icmp_seq 6

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

Request timeout for icmp_seq 9

64 bytes from 10.x.x.185: icmp_seq=10 ttl=63 time=4.954 ms

64 bytes from 10.x.x.185: icmp_seq=11 ttl=63 time=6.642 ms

Request timeout for icmp_seq 12

Request timeout for icmp_seq 13

Request timeout for icmp_seq 14

Request timeout for icmp_seq 15

Request timeout for icmp_seq 16

Request timeout for icmp_seq 17

^C

--- 10.x.x.185 ping statistics ---

19 packets transmitted, 2 packets received, 89.5% packet loss

round-trip min/avg/max/stddev = 4.954/5.798/6.642/0.844 ms

Ping status of MS as MS and KVM running on same machine as below,

PING 10.x.x.101 (10.1.10.101): 56 data bytes

64 bytes from 10.x.x.101: icmp_seq=0 ttl=63 time=9.528 ms

64 bytes from 10.x.x.101: icmp_seq=1 ttl=63 time=6.201 ms

64 bytes from 10.x.x.101: icmp_seq=2 ttl=63 time=8.534 ms

64 bytes from 10.x.x.101: icmp_seq=3 ttl=63 time=12.364 ms

64 bytes from 10.x.x.101: icmp_seq=4 ttl=63 time=12.948 ms

64 bytes from 10.x.x.101: icmp_seq=5 ttl=63 time=13.043 ms

^C

--- 10.x.x.101 ping statistics ---

6 packets transmitted, 6 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 6.201/10.436/13.043/2.556 ms


Thanks and Regards,
Bharat Saini

[signature_1700367617]

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Disclaimer *** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION 
intended solely for the use of the addressee(s). If you are not the intended 
recipient, please notify the sender by e-mail and delete the original message. 
Further, you are not authorised to copy, disclose, or distribute this e-mail or 
its contents to any other person and any such actions are unlawful and strictly 
prohibited. This e-mail may contain viruses. NxtGen Datacenter & Cloud 
Technologies Private Ltd (“NxtGen”) has taken every reasonable precaution to 
minimize this risk but is not liable for any damage you may sustain as a result 
of any virus in this e-mail. You should carry out your own virus checks before 
opening the e-mail or attachment. NxtGen reserves the right to monitor and 
review the content of all messages sent to or from this e-mail address. 
Messages sent to or from this e-mail address may be stored on the NxtGen e-mail 
system. *** End of Disclaimer ***NXTGEN***

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Informa

Re: Network Issue with Cluster

2024-03-01 Thread Jayanth Babu A
Hello Bharat,

Are you saying that you're observing the latency among the VMs in the same 
network?


Thanks,
Jayanth


From: Bharat Bhushan Saini 
Sent: Friday, March 1, 2024 5:20:22 pm
To: users@cloudstack.apache.org 
Subject: Network Issue with Cluster

Hi All,

Yesterday cloudstack deployment is running fine. Today I encountered an issue 
in the cloudstack 4.18.1.

The connectivity of the VM’s in the cloudstack dashboard having latches eg 
control and worker node. I also restarted the network but the issue is persist. 
Sharing the ping status of control node below,


PING 10.x.x.185 (10.x.x.185): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

Request timeout for icmp_seq 6

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

Request timeout for icmp_seq 9

64 bytes from 10.x.x.185: icmp_seq=10 ttl=63 time=4.954 ms

64 bytes from 10.x.x.185: icmp_seq=11 ttl=63 time=6.642 ms

Request timeout for icmp_seq 12

Request timeout for icmp_seq 13

Request timeout for icmp_seq 14

Request timeout for icmp_seq 15

Request timeout for icmp_seq 16

Request timeout for icmp_seq 17

^C

--- 10.x.x.185 ping statistics ---

19 packets transmitted, 2 packets received, 89.5% packet loss

round-trip min/avg/max/stddev = 4.954/5.798/6.642/0.844 ms

Ping status of MS as MS and KVM running on same machine as below,

PING 10.x.x.101 (10.1.10.101): 56 data bytes

64 bytes from 10.x.x.101: icmp_seq=0 ttl=63 time=9.528 ms

64 bytes from 10.x.x.101: icmp_seq=1 ttl=63 time=6.201 ms

64 bytes from 10.x.x.101: icmp_seq=2 ttl=63 time=8.534 ms

64 bytes from 10.x.x.101: icmp_seq=3 ttl=63 time=12.364 ms

64 bytes from 10.x.x.101: icmp_seq=4 ttl=63 time=12.948 ms

64 bytes from 10.x.x.101: icmp_seq=5 ttl=63 time=13.043 ms

^C

--- 10.x.x.101 ping statistics ---

6 packets transmitted, 6 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 6.201/10.436/13.043/2.556 ms


Thanks and Regards,
Bharat Saini

[signature_1700367617]

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.

Disclaimer *** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION 
intended solely for the use of the addressee(s). If you are not the intended 
recipient, please notify the sender by e-mail and delete the original message. 
Further, you are not authorised to copy, disclose, or distribute this e-mail or 
its contents to any other person and any such actions are unlawful and strictly 
prohibited. This e-mail may contain viruses. NxtGen Datacenter & Cloud 
Technologies Private Ltd (“NxtGen”) has taken every reasonable precaution to 
minimize this risk but is not liable for any damage you may sustain as a result 
of any virus in this e-mail. You should carry out your own virus checks before 
opening the e-mail or attachment. NxtGen reserves the right to monitor and 
review the content of all messages sent to or from this e-mail address. 
Messages sent to or from this e-mail address may be stored on the NxtGen e-mail 
system. *** End of Disclaimer ***NXTGEN***


Network Issue with Cluster

2024-03-01 Thread Bharat Bhushan Saini
Hi All,

Yesterday cloudstack deployment is running fine. Today I encountered an issue 
in the cloudstack 4.18.1.

The connectivity of the VM’s in the cloudstack dashboard having latches eg 
control and worker node. I also restarted the network but the issue is persist. 
Sharing the ping status of control node below,


PING 10.x.x.185 (10.x.x.185): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

Request timeout for icmp_seq 6

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

Request timeout for icmp_seq 9

64 bytes from 10.x.x.185: icmp_seq=10 ttl=63 time=4.954 ms

64 bytes from 10.x.x.185: icmp_seq=11 ttl=63 time=6.642 ms

Request timeout for icmp_seq 12

Request timeout for icmp_seq 13

Request timeout for icmp_seq 14

Request timeout for icmp_seq 15

Request timeout for icmp_seq 16

Request timeout for icmp_seq 17

^C

--- 10.x.x.185 ping statistics ---

19 packets transmitted, 2 packets received, 89.5% packet loss

round-trip min/avg/max/stddev = 4.954/5.798/6.642/0.844 ms

Ping status of MS as MS and KVM running on same machine as below,

PING 10.x.x.101 (10.1.10.101): 56 data bytes

64 bytes from 10.x.x.101: icmp_seq=0 ttl=63 time=9.528 ms

64 bytes from 10.x.x.101: icmp_seq=1 ttl=63 time=6.201 ms

64 bytes from 10.x.x.101: icmp_seq=2 ttl=63 time=8.534 ms

64 bytes from 10.x.x.101: icmp_seq=3 ttl=63 time=12.364 ms

64 bytes from 10.x.x.101: icmp_seq=4 ttl=63 time=12.948 ms

64 bytes from 10.x.x.101: icmp_seq=5 ttl=63 time=13.043 ms

^C

--- 10.x.x.101 ping statistics ---

6 packets transmitted, 6 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 6.201/10.436/13.043/2.556 ms


Thanks and Regards,
Bharat Saini

[signature_1700367617]

--- Disclaimer: --
This message and its contents are intended solely for the designated addressee 
and are proprietary to Kloudspot. The information in this email is meant 
exclusively for Kloudspot business use. Any use by individuals other than the 
addressee constitutes misuse and an infringement of Kloudspot's proprietary 
rights. If you are not the intended recipient, please return this email to the 
sender. Kloudspot cannot guarantee the security or error-free transmission of 
e-mail communications. Information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. Therefore, Kloudspot 
shall not be liable for any issues arising from the transmission of this email.