VIAVI TestCenter: Are overlapping addresses allowed for multiple address pools with same addresses like 192.168.x.x or 10.x.x.x for multiple subscribers.

VIAVI TestCenter: Are overlapping addresses allowed for multiple address pools with same addresses like 192.168.x.x or 10.x.x.x for multiple subscribers.

• DHCPv4 Overlapping address – expected GA Q4 2015 • Use case: Move home DHCP server/router from home to Service Provider in the Cloud, virtual CPE (vCPE)with NAT  • Up to 8 –16 addresses per customer(Vlan ID).There will be 8-16 DHCPv4 clients per Vlan ID.  • Can go up to 64 addresses with smart homes have 50+ devices requiring IP addresses. • 192.168.1.x/24 or 10.x.x.x/24 address pool for multiple customers.  • Reuse same address space for all customers • Each customer is identified by Circuit ID or Vlan ID, option 82,  • Simple DHCP over Ethernet encapsulation • DUT is a relay agent • DHCP server needs to be updated, no work on Client side • Server needs to talk to relay agent using source address not gi_addr in message. Not to client directly using gi_addr • Preferable to have 1 DHCP server/MAC address for 40K- 64K DHCPV4 Clients,  that would be 2500 – 4000 customers (Vlans) each with 16 Clients per port • Scale 400K addresses – 25K vlans with 16 DHCPv4 clients per customer • STC DHCPv4 Server requirements: • Need up to 10K address pools each with up to 64 addresses.  • Each address block has 8-16 (up to 64) addresses with a Vlan ID or Circuit ID Identifier with Start and Count • For Example: • Address pool IP 10.1.1.0/24, Count=16, Customer Circuit ID/Vlan ID Start=1, Count =2000. • This implies create 2000 address pools (AP-1 to AP-2000) each with 16 addresses from 10.1.1.1 - 10.1.1.16. • When a client request comes in for Address 10.1.1.x with Circuit ID=100, then assign address from the address pool AP-100