dominar250 opened a new issue, #9407:
URL: https://github.com/apache/cloudstack/issues/9407

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    
    * Other
   
   ##### COMPONENT NAME
   <!--
   SSVM
   -->
   ~~~
   
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   CloudStack 4.19.0.1
   -->
   
   ~~~
   
   ~~~
   
   ##### CONFIGURATION
   <!--
   advanced networking
   -->
   
   
   ##### OS / ENVIRONMENT
   <!--
   Ubuntu 22.04 virtual machine on vcentre
   -->
   
   
   ##### SUMMARY
   I'm using nested environment over vmware. promiscuous mode and MAC address 
change ,Forged Transmit are enabled in port group level. SSVM and console proxy 
agents are up.I'm having issue with packet loss from kvm machine to SSVM 
/Console proxy vm both private and public ip address. Unable to ping SSVM 
public ips .Ping from ssvm to management /kvm is good
   
   <img width="737" alt="Screenshot 2024-07-17 122504" 
src="https://github.com/user-attachments/assets/cfbd09a0-b098-4970-b7d9-2340f7800f2a";>
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   root@cloudstack-kvm:~# brctl show
   bridge name     bridge id               STP enabled     interfaces
   cloud0          8000.fe00a9fe08c6       no              vnet24
                                                           vnet27
   cloudbr0                8000.005056b4a6ca       yes             ens192
                                                           vnet25
                                                           vnet28
   cloudbr1                8000.005056b48ea4       yes             ens224
                                                           vnet26
                                                           vnet29
   root@cloudstack-kvm:~# ip addr show cloudbr0
   5: cloudbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state 
UP group default qlen 1000
       link/ether 00:50:56:b4:a6:ca brd ff:ff:ff:ff:ff:ff
       inet 10.158.65.11/25 brd 10.158.65.127 scope global cloudbr0
          valid_lft forever preferred_lft forever
       inet6 fe80::250:56ff:feb4:a6ca/64 scope link
          valid_lft forever preferred_lft forever
   root@cloudstack-kvm:~#
   root@cloudstack-kvm:~# ip addr show ens192
   2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master 
cloudbr0 state UP group default qlen 1000
       link/ether 00:50:56:b4:a6:ca brd ff:ff:ff:ff:ff:ff
       altname enp11s0
   root@cloudstack-kvm:~#
   root@cloudstack-kvm:~# ip addr show cloudbr1
   6: cloudbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state 
UP group default qlen 1000
       link/ether 00:50:56:b4:8e:a4 brd ff:ff:ff:ff:ff:ff
       inet6 fe80::250:56ff:feb4:8ea4/64 scope link
          valid_lft forever preferred_lft forever
   root@cloudstack-kvm:~# ip addr show ens224
   3: ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master 
cloudbr1 state UP group default qlen 1000
       link/ether 00:50:56:b4:8e:a4 brd ff:ff:ff:ff:ff:ff
       altname enp19s0
   
   ~~~
   
   
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   Able to ping ssvm public/private range from kvm/management server 
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   root@cloudstack-kvm:~# ping -O 10.158.209.11
   PING 10.158.209.11 (10.158.209.11) 56(84) bytes of data.
   no answer yet for icmp_seq=1
   no answer yet for icmp_seq=2
   no answer yet for icmp_seq=3
   no answer yet for icmp_seq=4
   
   --- 10.158.209.11 ping statistics ---
   5 packets transmitted, 0 received, 100% packet loss, time 4081ms
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   
   ~~~
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to