To enable fixed access sessions, a capture-sap must be provisioned under service vpls with appropriate values for trigger-packet and a link to the pfcp association. The triggers are mandatory and are not automatically derived from the default IBCP tunnel.
Sessions without any encapsulation are supported on a dot1q capture SAP. The system creates internal constructs to correctly handle sessions without encapsulation. These sessions can be combined with dot1q encapsulated sessions on the same capture SAP.
The following example shows trigger-packet provisioning in a PFCP association configuration:
A:admin@DUT-B# info
pfcp {
association "BNG-CPF"
}
trigger-packet {
pppoe true
}
To identify sessions in the data plane, the BNG CPF must provide the following parameters.
The logical port (also known as the l2-access-id) identifies the port, LAG, or pw-port where the session is terminated.
The VLAN tags, along with the logical port, identify a SAP where the session is terminated, also known as a Layer 2 circuit (l2-circuit). The BNG CPF must signal all the VLAN tags to match the encapsulation type provisioned for the port; for example, only signaling an s-tag for a q-in-q port is not allowed. As an exception, the BNG CPF can install sessions without any VLAN tags on a dot1q capture SAP, as described at the beginning of this section.
The source MAC address is required.
The PPPoE session ID is used for PPPoE only.
The IP anti-spoofing IP address is optionally used to enable IP anti-spoofing. While this can be signaled per session, the BNG UPF only supports a single anti-spoof type per SAP. When a second session on the same SAP has a conflicting anti-spoof indication, the setup fails. IP anti-spoofing is not supported for framed routes.
For PPPoE, the BNG UPF can perform LCP keep-alive offload, if supported and signaled by the BNG CPF. The BNG UPF automatically signals support for this feature when the PFCP association is created.