H3C Technologies H3C SecPath F5020 - Manual (Page 23)

15
Configuring PFC negotiation
PPP can compress the protocol field of PPP packets from 2 bytes to 1 byte to increase the payload size.
PFC negotiation notifies the peer that the local end can receive packets with a single-byte protocol field.
PFC negotiation is implemented at the LCP negotiation stage. After PFC negotiation is completed, the
device compresses the protocol field of sent non-LCP packets. If the first eight bits of the protocol field are
all zeros, the device does not add those bits into the packet. To ensure successful LCP negotiation, PPP
does not apply the compression to LCP packets.
H3C recommends that you use this configuration option on low-speed links.
To configure the local end to send PFC requests:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter interface view.
interface interface-type
interface-number
N/A
3. Configure the local end to
send PFC requests by
including the PFC option in
outbound LCP negotiation
requests.
ppp pfc local request
By default, the local end does not
include the PFC option in
outbound LCP negotiation
requests.
To configure the local end to reject PFC requests received from the peer:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter interface view.
interface interface-type
interface-number
N/A
3. Configure the local end to
reject PFC requests received
from the peer.
ppp pfc remote-reject
By default, the device accepts PFC
requests received from the peer,
and performs PFC on frames sent
to the peer.
Enabling PPP accounting
PPP accounting collects PPP statistics, including the numbers of received and sent PPP packets and bytes.
AAA can use the PPP statistics for accounting. For more information about AAA, see Security
Configuration Guide.