Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
385 questions
Problems creating L3 in SDN by Azure local
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 73%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
David Rivera Fernández
0
Reputation points
We deployed Azure Local and now we are trying to deploy SDN using SDNExpress script with 3NC, 3GW and 3MUXES. The SDN seems to be OK and we have connection between the MUXES and the BGP
Now we need to create an L3 Gateway connection but is disconnected and uninitialized and I don’t know why
We tried to create an L3 on WAC and by script but with the same result
{count} votes
-
Prrudram-MSFT 27,576 Reputation points2025-01-02T05:47:49.5166667+00:00 Hi @David Rivera Fernández
I will review this with product team. In the interim, please check below steps and considerations that might help you troubleshoot and resolve the issue:Check the Configuration Files: Ensure that the configuration files for the SDNExpress script are correctly set up. The configuration file is a PSD1 file that contains variables for your Network Controller deployment. Make sure all necessary parameters and settings are correctly filled out
Network Interface Diagnosis: If the L3 Gateway connection is disconnected and uninitialized, it might be related to issues at the network interface level. The diagnosis process involves checking L2 and L3 connectivity. Ensure that the network interfaces are correctly configured and bound to the necessary protocol
Health Probes: The L3 Gateway needs to probe the health of the service module instances. Ensure that the health probes are correctly set up and functioning. This helps in monitoring the health of the service module instances and can provide insights into why the L3 Gateway connection is not initializing
Unified Connection Troubleshoot: Utilize tools like Azure Network Watcher's enhanced connection troubleshoot feature. This tool provides a unified solution for diagnosing issues related to NSG, user-defined routes, and blocked ports. It offers actionable insights and step-by-step guides to resolve connectivity issues
Review Logs and Error Messages: Check the logs and error messages generated during the deployment process. These logs can provide valuable information about what might be causing the L3 Gateway connection to remain uninitialized.
https://learn.microsoft.com/en-us/windows-server/networking/sdn/deploy/deploy-network-controller-failover-clustering?tabs=windows-admin-center&pivots=windows-server -
Prrudram-MSFT 27,576 Reputation points
2025-01-03T07:56:08.6833333+00:00 @David Rivera Fernández
This requires deeper troubleshooting involving the diagnosis of the logs. I would recommend reaching out to technical support by creating a support ticket with Azure VM team. If you don't have an active support plan, let me know. -
David Rivera Fernández 0 Reputation points
2025-01-03T08:05:18.25+00:00 We have already requested support from Microsoft and are awaiting a meeting by teams.
Sign in to comment
Sign in to answer