search

Azure / Enterprise-Scale-for-AVS

Enterprise-scale for AVS represents the strategic design path and target technical state for an Azure VMware Solution (AVS) deployment. This solution provides an architectural approach and reference implementation to prepare landing zone subscriptions for a scalable Azure VMware Solution (AVS) cluster.
MIT License
126 stars 84 forks source link

New Compute Segment, allowing for on-prem communications #279

Closed jnordsving closed 1 year ago

jnordsving commented 1 year ago

I created a new Compute Segment of 10.5.5.0/24 - GW - .1 this does not exist on premises. I would like the VMs on this Segment to communicate with my on-premises VMs residing 10.89.20.0/24. -this network is where our VDI systems are running, & for access to AVS vCenter, & NSX-T. which is working perfectly through our VPN.

I've updated the VPN (policy based) with the new SDDC Compute Segment on both sides. but yet no traffic is being passed.
I have another test compute segment on the SDDC of 192.168.5.0/24, which between the two segments I can ping the VMs. Next issue is, I have internet out connectivity on the 192.168.5.x. network, where my VMs on the 10.5.5.x segment are having problems getting internet out.

Hopefully you can help me clear some of these issues up.

I've attached the compute segment screen capture configuration.

Screenshot 2023-08-14 at 9 53 15 PM

Also, it would be great if you had a connectivity testing tab for running DNS/IP tests from within the Azure Portal. See attached file.. this is from our VMware on AWS SDDC

Screenshot 2023-08-14 at 9 46 54 PM
michielvanschaik commented 1 year ago

@fguerri Is this something you can help with?

jnordsving commented 1 year ago

Any help on this?

I created a new Compute Segment of 10.5.5.0/24 - GW - .1 this does not exist on premises. I would like the VMs on this Segment to communicate with my on-premises VMs residing 10.89.20.0/24. -this network is where our VDI systems are running, & for access to AVS vCenter, & NSX-T. which is working perfectly through our VPN.

I've updated the VPN (policy based) with the new SDDC Compute Segment on both sides. but yet no traffic is being passed. I have another test compute segment on the SDDC of 192.168.5.0/24, which between the two segments I can ping the VMs.

husamhilal commented 1 year ago

@michielvanschaik I think we should device this into two asks: one is the troubleshooting part, I'm helping @jnordsving with that as we speak, and the feature request as he is asking for connectivity testing feature similar to VMC on AWS.

michielvanschaik commented 1 year ago

@jnordsving Please open a support ticket with Microsoft Support for support on your issue. We will consider taking your feature request to the backlog.