Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

How IPv4 Address Negotiation and Release for Static PPP Subscribers Works in a Subscriber Access Network

You can use on-demand IPv4 address allocation or de-allocation for static dual-stack subscribers.

IPv4 Address Negotiation for Static PPP Subscribers

1. PPP Link Control Protocol (LCP) is established and an IPv6 control protocol is successfully negotiated.
2. The broadband network gateway (BNG) receives an Internet Protocol Control Protocol (IPCP) Configure Request with a 0.0.0.0 IPv4 address option from the customer premises equipment (CPE).
3. The BNG sends an IPCP Configure Request with a local IPv4 address option to the CPE.
4. The BNG sends an Access-Request message with the Unisphere-Ipv4-release-control VSA (if configured) to the RADIUS server.
5. The BNG receives an IPCP Configure ACK from the CPE.
6. The BNG receives an Access-Accept message from the RADIUS server.
   • If a Framed-IP-Address attribute is received, then a duplicate address check (if configured) is performed on the BNG. If a duplicate address check is completed successfully, then PPP continues IPCP negotiation with the CPE. Otherwise, the entire PPP session is brought down by sending an LCP terminate request to the CPE.
   • If a Framed-Pool attribute is received, then the IPv4 address is allocated from the specified local address pool configured in the BNG. If the IP pool is not configured in the BNG and there is no other IP pool available, then the IPCP protocol reject is sent to the CPE.
   • If neither a Framed-IP-Address attribute nor a Framed-Pool attribute is received, then the BNG allocates an IPv4 address from one of the configured local address pools. If the BNG cannot allocate an IPv4 address, then the IPCP protocol reject is sent to the CPE.
   • If neither a Framed-IP-Address attribute nor a Framed-Pool attribute is received, then the BNG allocates an IPv4 address from one of the configured local address pools. If the BNG cannott allocate an IPv4 address, then the IPCP protocol reject is sent to the CPE.
   • If there is no response from the RADIUS server, then the IPCP is terminated.
   • If ADFv4 filters are present in the Access-Accept message, then they need to be reinstalled for that subscriber in the BNG.
   • If both IPv4 primary and secondary DNS addresses are present in the Access-Accept message, then both need to be updated for that subscriber in the BNG. If either an IPv4 primary DNS address or an IPv4 secondary DNS address is present in the Access-Accept message, then only the corresponding DNS address needs to be updated for that subscriber.
7. The BNG sends an IPCP Configure NACK with the new IPv4 address option to the CPE.
8. The lawful intercept service (if present for inet family) is activated.

   The BNG sends an immediate Interim-Accounting message (if configured) with the Unisphere-Ipv4-release-control VSA (if configured) and the Framed-IP-Address attribute to the RADIUS server.

9. The BNG receives an IPCP Configure Request with new IPv4 address option from the CPE.
10. The BNG receives an Interim-Accounting response from the RADIUS server.
11. The BNG sends an IPCP Configure ACK to the CPE.

IPv4 Address Release for Static PPP Subscribers

1. The BNG receives an IPCP terminate request from the CPE.
2. The BNG sends an IPCP terminate ACK to the CPE.
3. The following actions occur:
   • The lawful intercept service (if present for inet family) is de-instantiated.
   • If an IPv4 address was allocated from local address pool, the address then becomes available.
   • The IPv4 address entry is cleared from the subscriber record.
   • The BNG sends an immediate Interim-Accounting message (if configured) with the Unisphere-Ipv4-release-control VSA (if configured) to the RADIUS server and the Framed-IP-Address attribute is not included.
   • User Session Statistics are retained for the entire PPP session and are not cleared when the IPv4 address is released.
4. The BNG receives an Interim-Accounting response from the RADIUS server.

   No action is taken in the BNG whether or not it receives a response from the RADIUS server.