Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
77 lines (71 sloc) 7.29 KB

Installation instructions

PCE Steps

  • On PCE, create unmanaged workloads for all the Azure VM's as shown below:
  • Make sure that the public IP address for the VM is added as an additional interface, for example in above image the public IP is added as eth1:<Public IP here>.
  • Now please make sure PCE is accessible from Azure IP range using following steps:
    • Click on the "function name" , then click "platform features" and then finally click "properties" as shown in the image below:
    • Now on the properties page, note down the "additional outbound IP Address" as shown below:
    • Please make sure PCE is accessible from these IP addresses noted down above.
    • Finally if you need to open up IPs for broader Azure services, here is the list for them:
  • Now create new API key for azure functions as shown below and store it locally temporarily since it is not shown again:

Azure NSG Flow Logs Steps

  1. Log in to Azure portal and turn on NSG Flow logging for the VM's/Networks which are to be visualized in PCE.
  2. The steps for doing it are listed here:
  3. Once NSG flow logs are enabled test it by downloading them as shown here:
  4. If the download section doesn't show the json log files, please repeat step 2 to see if NSG flow logs are enabled correctly.
  5. Now note down the log path in the download section, it should be something like shown below, please store it, since we are going to need it in Azure Function Creation section below.

Azure Function Creation

  1. Now, log into Azure Portal and follow the step by step instructions only in "Create an Azure Function app" section to create a Blob triggered Azure function:
  2. The function has to be in the same Availability zone as that of NSG Log flows storage account created in above section.
  3. Once the function is created, follow following steps to connect NSG flow logs storage to the function:
    1. Click Integrate below the function and click on the myBlob trigger as shown in image below:
    2. Now click the Storage Account Connection and see if NSG Flow log storage is shown there. If it doesn't show up, click on the New button and try to add the storage account as shown in image above.
    3. If the storage account section shown above doesn't have the storage account for NSG flow listed there, it means you have created the function in different availability zone and thus you will have to repeat the steps above to before proceeding to create the function in same availability zone.
    4. Now once you have connected the storage account for NSG Flow logs with this functions, let us set the Path (highlighted in yellow in above image) to the one listed in step 5 in above Azure NSG Flow Logs Steps section or as shown in the next step below:
    5. Now still on the function Integrate page click on the advanced editor link in top corner and check if the settings look somewhat similar to the one listed in src/function.json file.
    6. If they look same, we are all set now from storage point of view.
  4. Once storage is set, let us set the PCE environment variables for the functions.
    1. Click on the function itself and click platform as shown in the image below:
    2. Now click configuration and configuration page will show up.
    3. Now follow the steps mentioned in Application setting section on this page and set the following highlighted PCE and NSG variables from first section above:
    4. List of PCE and NSG variables:
    5. The values for NSG_TRAFFIC_DECISION are all, allowed or denied. The default value for NSG_TRAFFIC_DECISION is allowed if the variable is empty string, not set, or a typo.
    6. PCE_APITOKEN example: beb62c646efb6fa7c7b3ed6dLie4yahKeegohNiekasuc516a7989675570982ac
    7. PCE_APIUSER example: api_puheVahd3naeFungi
    8. Make sure the PCE_HOSTADDR is set as https://<PCE-host>:<PCE-port>/ for example,
    9. PCE_ORG example: 1
    10. Once the variables are set, we can proceed to next steps.
  5. Now click on the BlobTrigger1 function itself and an editor will open up with a single run() function in it.
  6. Remove the the code there and replace it with the one in the src/run.csx file.
  7. Once the above code is pasted in the editor, Click Save and then Run and then open the Log section below to see if the function has started.
  8. You will see in the log that the function is being triggered (it can take few minutes for initial run, but then it is fast after that) and the log shows how many flows were uploaded to PCE as shown below:
    2019-07-03T21:29:56.639 [Information] Executing 'Functions.BlobTrigger1' (Reason='New blob detected: insights-logs-networksecuritygroupflowevent/resourceId=/SUBSCRIPTIONS/<snip>/RESOURCEGROUPS/<snip>/PROVIDERS/MICROSOFT.NETWORK/NETWORKSECURITYGROUPS/<snip>/y=2019/m=07/d=03/h=21/m=00/macAddress=<snip>/PT1H.json', Id=<snip>)
    2019-07-03T21:29:56.639 [Information] Uploading NSG Flows to PCE
    2019-07-03T21:29:56.869 [Information] Created
    2019-07-03T21:29:56.869 [Information] {"num_flows_received":68,"num_flows_failed":0,"failed_flows":[]}
    2019-07-03T21:29:56.869 [Information] Uploaded flow to: https://<snip>:8443/api/v2/orgs/<snip>/agents/bulk_traffic_flows
    2019-07-03T21:29:56.869 [Information] Executed 'Functions.BlobTrigger1' (Succeeded, Id=<snip>)
  9. Thats it, you have a working Azure function which uploads NSG Flow logs to PCE for visualization as shown below:
You can’t perform that action at this time.