Setting up an Azure Big IP F5 device

%3CLINGO-SUB%20id%3D%22lingo-sub-1082887%22%20slang%3D%22en-US%22%3ESetting%20up%20an%20Azure%20Big%20IP%20F5%20device%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1082887%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20inherited%20an%20Azure%20F5%20implementation.%26nbsp%3B%3C%2FP%3E%3CP%3EBelow%20is%20the%20subnet%20layout.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3Eexternal%3C%2FP%3E%3CP%3E192.168.20.0%2F24%20(234%20Addresses)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Einternal%3CBR%20%2F%3E192.168.30.0%2F24%20(244%20Addresses)%3CBR%20%2F%3E*F5%20Route%20configuration%20%3D%20Gateway%20192.168.30.1%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Emanagement%3CBR%20%2F%3E192.168.1.0%2F24%20(244%20Addresses)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGatewaySubnet%3CBR%20%2F%3E192.168.0.0%2F26%20(59%20Addresses)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENote%3A%3C%2FP%3E%3CP%3EThe%20*F5%20Route%20configuration%20is%20a%20configuration%20item%20in%20the%20F5%20operating%20system.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20subnet%20layout%20and%20F5%20configuration%20above%20is%20currently%20in%20production%20and%20functioning%20as%20expected.%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20inherited%20the%20F5%20subnet%20layout%20below.%26nbsp%3B%3C%2FP%3E%3CP%3ELooking%20at%20the%20subnet%20layout%20below%2C%20what%20is%20the%20%22internal%22%20subnet%20gateway%3F%3C%2FP%3E%3CP%3EHow%20is%20this%20determined%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eexternal%3CBR%20%2F%3E172.20.0.64%2F27%20(32%20addresses)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Einternal%3CBR%20%2F%3E172.20.0.96%2F27%20(32%20addresses)%3C%2FP%3E%3CP%3EGateway%20Address%20(%3F%3F%3F%3F%3F%3F)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Emanagement%3CBR%20%2F%3E172.20.7.0%2F24%20(248%20addresses)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGatewaySubnet%3CBR%20%2F%3E172.20.0.0%2F26%20(59%20addresses)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESubnet%20FAQ's%3C%2FP%3E%3CH3%20id%3D%22toc-hId-1060376095%22%20id%3D%22toc-hId-1060397947%22%3EAre%20there%20any%20restrictions%20on%20using%20IP%20addresses%20within%20these%20subnets%3F%3C%2FH3%3E%3CP%3EYes.%20Azure%20reserves%205%20IP%20addresses%20within%20each%20subnet.%20These%20are%20x.x.x.0-x.x.x.3%20and%20the%20last%20address%20of%20the%20subnet.%20x.x.x.1-x.x.x.3%20is%20reserved%20in%20each%20subnet%20for%20Azure%20services.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3Ex.x.x.0%3A%20Network%20address%3C%2FLI%3E%3CLI%3Ex.x.x.1%3A%20Reserved%20by%20Azure%20for%20the%20default%20gateway%3C%2FLI%3E%3CLI%3Ex.x.x.2%2C%20x.x.x.3%3A%20Reserved%20by%20Azure%20to%20map%20the%20Azure%20DNS%20IPs%20to%20the%20VNet%20space%3C%2FLI%3E%3CLI%3Ex.x.x.255%3A%20Network%20broadcast%20address%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1082887%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eaddressing%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20F5%20Subnet%20gateway%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Erouting%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esubnetting%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Visitor

 

I've inherited an Azure F5 implementation. 

Below is the subnet layout. 


external

192.168.20.0/24 (234 Addresses)

 

internal
192.168.30.0/24 (244 Addresses)
*F5 Route configuration = Gateway 192.168.30.1

 

management
192.168.1.0/24 (244 Addresses)

 

GatewaySubnet
192.168.0.0/26 (59 Addresses)

 

Note:

The *F5 Route configuration is a configuration item in the F5 operating system.

 

The subnet layout and F5 configuration above is currently in production and functioning as expected. 

I've inherited the F5 subnet layout below. 

Looking at the subnet layout below, what is the "internal" subnet gateway?

How is this determined?

 

external
172.20.0.64/27 (32 addresses)

 

internal
172.20.0.96/27 (32 addresses)

Gateway Address (??????)

 

management
172.20.7.0/24 (248 addresses)

 

GatewaySubnet
172.20.0.0/26 (59 addresses)

 

 

 

 

 

Subnet FAQ's

Are there any restrictions on using IP addresses within these subnets?

Yes. Azure reserves 5 IP addresses within each subnet. These are x.x.x.0-x.x.x.3 and the last address of the subnet. x.x.x.1-x.x.x.3 is reserved in each subnet for Azure services.

 

  • x.x.x.0: Network address
  • x.x.x.1: Reserved by Azure for the default gateway
  • x.x.x.2, x.x.x.3: Reserved by Azure to map the Azure DNS IPs to the VNet space
  • x.x.x.255: Network broadcast address

 

 

0 Replies