Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Creating an IP Address Pool

 

You, the Service Designer, can create consistent IP address pools for Layer 3 VPNs from Prestage Devices > Manage IP Addresses > Create IP Address Pools. The IP addresses assigned to each PE/CE link need to allow routing across the customer’s entire Layer 3 VPN, as long as the PE/CE addresses are not exposed outside of that VPN. If the PE/CE link addresses are accessible from outside the customer’s VPN, then those IP addresses may also need to be globally unique across the internet, instead of just within the customer’s VPN.

When you create an IP address pool, it appears in the Prestage Devices > Manage IP Addresses inventory page. See Managing IPv4 Addresses for Layer 3 VPNs

Note

Preferably, create all IPv4 address pools at the beginning of the pre-staging process (see Prestaging Devices Overview), before you run Role Discovery (see Discovering and Assigning All N-PE Devices), so that any IPv4 IP addresses found on devices during the role discovery process can be marked as already allocated in the corresponding IPv4 IP address pools.

To create an IPv4 IP address pool:

  1. In the Network Activate task pane, select Navigate to Prestage Devices > Manage IP Addresses > Create IP Address Pools.

    The Create IP Address Pool page appears.

  2. In the IP pool type drop-down list box, select either Global or Customer.
    • A Global IP address pool pertains to the service provider. There can be more than one global IPv4 address pool. However, each global pool must have its own unique name and its set of IPv4 addresses must not overlap with those of any other global pool. You can allocate addresses from global pools across multiple Layer 3 VPNs across multiple customers.

    • A Customer IP address pool pertains to an existing customer. These pools are associated with the corresponding customer. You can associate more than one customer IPv4 pool with each customer. However, each customer pool must have its own set of IPv4 addresses which must not overlap with those of any other pool belonging to the same customer. You can allocate addresses from customer pools across multiple Layer 3 VPNs for a particular customer.

  3. In the Pool name field, enter a unique name.

    An IP address Pool name can be no more than 50 characters.

  4. In the Pool description field, enter a helpful description.

    The Pool Description can be no longer than 200 characters.

  5. In the IP address pool field, enter an IPv4 IP address pool.

    Any IPv4 address pool in Junos Space maps directly onto the Classless Interdomain Routing (CIDR) notation for IPv4 network addresses. The CIDR network address, 192.168.1.0/24 is a contiguous block of 256 individual IPv4 addresses: 192.168.1.0/32 through 192.168.1.255/32, inclusive. The network address 10.0.99.20/30 is a contiguous block of 4 individual IPv4 addresses: 10.0.99.20/32 through 10.0.99.23/32, inclusive. As a consequence, any Junos Space IPv4 address pool directly maps to (and is identified by) its CIDR network address. The Junos Space IPv4 address pool, 192.168.1.0/24, contains all of the addresses from 192.168.1.0/32 to 192.168.1.255/32, while the IPv4 address pool, 10.0.99.20/30 contains all of the addresses from 10.0.99.20/32 to 10.0.99.23/32.

  6. If you are creating a Customer IP address pool, the Associate with customer drop-down list box appears. Select an existing customer name. To create a customer, see Adding a New Customer.
  7. Click Create.

    Junos Space saves the IP address pool information in the database. The IP address pool appears in the Manage IP Address inventory page. The Pool Type column differentiates global from customer IP address pools.

    Note

    You need to create IP address pools only if the operation of your network requires it. Alternatively, you can use the global IP pools provided by the Network Activate software for Layer 3 VPN services.