Skip to content

Instantly share code, notes, and snippets.

@binario200
Last active July 15, 2020 02:53
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save binario200/68a2681ce41139c83d5b94a27f661ea8 to your computer and use it in GitHub Desktop.
Save binario200/68a2681ce41139c83d5b94a27f661ea8 to your computer and use it in GitHub Desktop.
notes for the azure 103 certification content

https://docs.microsoft.com/en-us/learn/certifications/exams/az-103

Plan IP addressing for your networks

Before planning your network IP address scheme, you must gather the requirements for your infrastructure. These requirements also will help you prepare for future growth by reserving extra IP addresses and subnets. Here are two of the questions you might ask to discover the requirements:

  • How many devices do you have on the network?
  • How many devices are you planning to add to the network in the future?

When your network expands, you don't want to redesign the IP address scheme. Here are some other questions you could ask:

Based on the services running on the infrastructure, what devices do you need to separate?

  • How many subnets do you need?
  • How many devices per subnet will you have?
  • How many devices are you planning to add to the subnets in future?
  • Are all subnets going to be the same size?
  • How many subnets do you want or plan to add in future?

the number of possible addresses on an Azure subnet is 2^n-5, where n represents the number of host bits.

You choose the private IP addresses that are reserved by the Internet Assigned Numbers Authority (IANA) based on your network requirements:

  • 10.0.0.0/8
  • 172.16.0.0/12
  • 192.168.0.0/16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment