Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

PowerProtect Data Manager 19.13 Google Cloud Platform Deployment Guide

PDF

Configure network firewall rules

Configure network traffic rules to allow inbound and outbound connections with other networks.

About this task

CAUTION:

When configuring network firewall rules, do not allow IP addresses that belong to the 172.24.0.192/26 subnet. IP addresses in the 172.24.0.192–172.24.0.255 range are used for Docker network configuration, and unexpected results can occur if they are also used by PowerProtect Data Manager.

The following example describes the procedure to allow inbound TCP traffic on port 9000.

NOTE: GCP uses the terms ingress and egress for inbound and outbound traffic.

Steps

  1. From the Google Cloud Console, navigate to VPC network > Firewall, and click CREATE FIREWALL RULE.
  2. Under Direction of traffic, select Ingress.
  3. Under Action on match, select Allow.
  4. Under Targets select Specified target tags.
  5. Under Target tags, enter the name of the network firewall rule.
  6. Under Source IP ranges, enter the subnet of the allowed inbound traffic..
  7. Under Protocols and ports, select Specified protocols and ports, select tcp, and enter 9000.
  8. Navigate to Compute Engine > VM Instances, select the PowerProtect Data Manager instance, and click EDIT.
  9. Under Network tags, add the network firewall rule you created in step 5.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\