We have requirement to allow communication between SUSE Linux based VM located in Microsoft Azure and on premise SUSE Linux based server. Also need to configure NPM to detect network issues like traffic black holing, routing errors etc.
Steps:
We have configured NPM based on steps mentioned in below link. (also opened TCP in bound and out bound port 8084 for Azure SUSE Linux based VM).
https://learn.microsoft.com/en-us/azure/log-analytics/log-analytics-network-performance-monitor
Issue: As seen in screenshot 1, NPM workspace shows that 2 VM’s are connected (i.e. On premise and Azure VM’s) .
However when “Discover Express Route Resources” is clicked, it doesn’t show any nodes. See screenshot 2 for reference. Even if you click on “Add Azure Agents”, there is no agent/node discovered.
Are we missing anything here?
Related
I am running an Ubuntu self-hosted build agent for Azure DevOps in Container Instances and container outputs only: Determining matching Azure Pipelines agent. and that's it.
It has PAT with full access to whole organization, given agent pool really exists and the URL is correct as well. THe only thing that comes to my mind is that I see our URL as https://XXXX.visualstudio.com/ but I gave the agent url like https://dev.azure.com/XXX which still seems to be working when used in the browser.
How to solve this, please?
I suppose that your issue is caused by the agent upgrades to support .NET 6 (.NET core 3.1 will be out of support in December). You could test to upgrade the container version to 20.04 or higher.
You could also refer to this issue#3834 for more information.
The problem was that Agent was put into the subnet which had not NSG, therefore it denied all in/outbound traffic. So we added a NSG to this subnet with outbound rule for port 443 TCP and it works now.
My team have created an IR in an on-premises VM and we are trying to create a Linked Service to an on-prem DB using that IR
Whenever we click on Test Connection in the Linked Service, the connection fails and IR goes into a limited state
We also whitelisted the IPs provided by Microsoft for IR ADF and also checked the network traces and all seems fine there
Also, we stopped and restarted the IR, uninstalled and installed it again but still the problem resists
Have anyone faced a similar kind of issue?
As this has been a long time we are facing this issue which has now become a blocker for us
Thanks!
This is observed when nodes can't communicate with each other.
You can Log in to the node-hosted virtual machine (VM). Go to Applications and Services Logs > Integration Runtime, open Event Viewer, and filter the error logs. If you find the error System.ServiceModel.EndpointNotFoundException or Cannot connect to worker manager
Follow the official documentation with detailed steps for Troubleshooting Error message: Self-hosted integration runtime node/logical self-hosted IR is in Inactive/ "Running (Limited)" state
As it states:
try one or both of the following methods to fix:
- Put all the nodes in the same domain.
- Add the IP to host mapping in all the hosted VM's host files.
I ran into same issue. Our organization has firewall rules preventing specific ports or url's from outside network. We added Data factory services tags with internet facing in Route table, and IR then connected successfully.
I've a nodejs app using this npm package (https://github.com/ancasicolica/node-wifi-scanner ) which basically use netsh wlan command to list all surrounding wifi. when I run this locally, everything fine but when /I deploy this to Azure Web App, it will only return the connected WiFi but bit surrounding. Any idea of what might have been wrong on Azure?
As the Technical background describes:
The module uses command line tools for gathering the network information:
netsh on Windows: netsh wlan show networks mode=Bssid
And we do not have sufficient permission to run this command on Azure Web Apps.
And secondly, As #astaykov said, Azure is a cloud compute platform, all the services and resources are in the Azure Data Centers, which cannot detect your WiFi environment on your local.
You cannot approach your requirement on any cloud compute platforms. You need to to the detection operations on your client side or devices.
There is nothing wrong on Azure!
Do you really expect to scan for WiFi networks inside an Azure Data Center (the chance that there is a WiFi network inside Azure Data Center is close zero) ?!
Do you believe that servers running inside Azure Data Center do have WiFi adapters (I don't) ?!
And what exactly are you trying to achieve - a server based application running on server somewhere on Internet, using netsch on the server to scan for WiFi networks available on your laptop? No, this is not possible. And this is not Azure limitation, and has nothing to do with Azure.
I am trying to setup OrientDb instance under Azure. I followed the procedure documented at OrientDB website (OrientDB Community Edition 2.0.10). I was able to setup the instance as described. After setting up all I could do is to ssh to the instance using the username:db as mentioned in the document (well I could have used any name, but for simplicity I followed word to word from the doc). I couldn't find information on user:root or user:orientdb (and a few other users and groups) that were part of this image. Additional users/groups are available in /etc/passwd. I am unable to get access to those users/groups. I am unable to find the documentation.
I tried to connect to the OrientDb web interface http://10.0.0.4:2480 (hosted on internal network interface within Azure region) and it doesn't even allow me to create db or login. It keeps asking for the username and password which I dont know (not documented).
Anyone know where can I found additional documentation/help on this image.
I can always setup a plain linux OS, install java and setup orient-db and configure it to use azure storage (bound as local disk storage). As much as possible, I would like to use the image provided by the orient-db team as I think it would come with recommended configuration.
I want to host/run a clustered orientdb instance on Azure. Any help is appreciated
You'll need to ssh to the virtual machine using the username and password that you specified when you created the Azure instance.
To obtain the credentials for Studio, Pabzt is right, just take a look at the sections of orientdb-server-config.xml and look for the root user. Its password will be auto-generated. You can change this.
Pabzt, regarding accessing Studio, you might make sure the OrientDB instance is still runnning:
sudo systemctl status orientdb
Usually, ports 22 and 2480 are open by default in the OrientDB Azure image. So, it's strange you can't access it.
I had the same problem today. You could connect using ssh. The default password and username can be found in the "orientdb-server-config.xml":
/opt/orientdb/config/orientdb-server-config.xml
The only thing i can't do is accessing the OrientDB Studio. While i can connect to the public ip address of the vm using ssh, i cant open the OrientDB Studio on port 2480 using the same public ip address. I tried adding an inbound securty rule in the network security settings for the orientdb vm but that didn't help. Still can't connect.
EDIT 22.10.2015 21:00
But I'm sure the password and username is working (from "orientdb-server-config.xml"), because i tried using the binary protocol on port 2424 with the "official .Net Driver" for OrientDB in a client application written in C#, and they worked. I was able to connect and create a new Database. Also i was able to access the default database: "GratefulDeadConcerts". I used the same public ip address that i used to connect via ssh.
I compared the OrientDB VM created by the image from the azure marketplace and couldn't find the option to set Endpoints (Azure VM Settings). All my other Azure VMs have this option in the Azure VM Settings. I always used the Endpoint settings to open ports on the virtual machines i have. It seems that i can only use the Endpoints for ssh and port 2424. Maybe those are the ones which are open by default. Any Ideas?
EDIT 23.10.2015 14:00 Uhr
Okay i found the solution, the OrientDB image from the azure marketplace works. I just added a new securty rule that allows connections from any port (*) to port 2480 (OrientDB Studio) and now it works.
I had this problem and realized I had missed something. On Azure go to All Resources, click on the Network Security Group for your server, and add an Inbound Security Rule allowing TCP port 2480. I didn't have to add anything using iptables on the server even though 2480 is not listed there. I hope this helps someone else.
The endpoints, by default are set to 22 and 2480. Strange that you had to set 2480 to * for incoming. But I'm glad you got it to work!
The root in the orientdb-server-config.xml is just for OrientDB and is not related to the system root account.
You should be able to sudo as the system username that you specified when you created the Azure VM. If you can sudo commands you should be able to change the system root password as well.
Just installed azure connect on my localhost, but it won't connect. I see my machine dbates-HP as a active endpoint in my vistual network/connect section on my azure portal and organized it into a group.
I can see in the azure connect portal that the machine endpoint is active, and that it refreshes since the last connected updates.
My local connect client lists the following diagnostics messages:
Policy Check: There is no connectivity policy on this machine.
IPsec certificate check: No IPsec certificate was found.
Also tried with firewall turned off.
Duncan
In some scenarios getting Windows Azure connect to working becomes very complex. I have worked on multiple such scenarios and found most common issues are related with network settings. To start investigate you need to collect the Azure Connect logs first from your machine and try to figure the problem out by yourself. I have described some info about collecting log here:
http://blogs.msdn.com/b/avkashchauhan/archive/2011/05/17/collecting-diagnostics-information-for-windows-azure-connect-related-issues.aspx
To open a free Windows Azure support incident please use link below:
https://support.microsoft.com/oas/default.aspx?gprid=14928&st=1&wfxredirect=1&sd=gn
Have you "linked" your Azure role with the machine group you created? The message "There is no connectivity policy on this machine" suggests that you haven't defined (in portal) to whom this machine should connect to.