Description

​With respect to RFC1918 CSO allocated private IP address ranges and it's purpose. The table below capture changes implemented in 5.3 release and further.

Symptoms

An IPv4 address exhaustion is may occur if the defined address's subnet is not known.

Solution

This table provides the IP address range, reserved purpose and description:
 

IP Address range Reserved for  Can be used in the LAN Subnets  Comments 
Prior to 5.3 Post 5.3  
10.0.0.0/8 172.30.0.0/16 
  		Assigned to st0 and gr interfaces for overlay tunnels  No  Yes  Config changes will fix and allow it in LAN subnet 
192.168.1.0/24 192.168.2.0/24 
  		Used by NFX150 platform. (as part of default config, for JDM & VNFs connectivity, flowd connectivity)
  		No  Yes  Config changes will fix and allow it in LAN subnet 
100.124.0.0/14 # 
OAM IP address configured on device loopback interface.  (For on-prem, User can input a different IP at the time of the site-onboarding.) 
  		Reserved pool  Reserved pool  OAM IPs needs to be avoided in LAN 
192.0.2.0/24  Used by NFX250 platform. (as part of default config, for JDM and VNFs connectivity) 
Reserved Pool  		Reserved Pool  Needs to be avoided in LAN 
172.31.31.0/24  Internal use by CSO for LT interfaces on spoke devices (fixed set of IPs reserved in a release)  No  Yes  Being migrated to 100.123.255.0/24. 172.31.31.0/24
Is available for LAN 
172.31.32.0/24  Internal use by CSO used for dedicated DC per department on E-hubs. (not used on spokes)  No  Yes 
  		Being migrated to 100.123.254.0/24. 172.31.32.0/24
Is available for LAN