Troubleshooting Pppoe Service Name Tables - Juniper JUNOS 10.1 - CONFIGURATION GUIDE 1-2010 Configuration Manual

Table 82: PPPoE Trace Operation Flags (continued)
To configure the flags for the events to be logged, configure the flags:

Troubleshooting PPPoE Service Name Tables

A misconfiguration of a PPPoE service name table can prevent PPPoE services from
Problem
being properly activated. Configuration options for PPPoE service name tables are
simple, which should simplify discovering where a misconfiguration exists. PPPoE
clients cannot connect if the service name table contains no match for the service
name tag carried in the PADI packet.
The symptom of a service name table misconfiguration is that the client connection
process stops at the negotiation stage and the PADI packets are ignored. You can
use the
problem.
When the service name table is properly configured, packets sent and received
increment symmetrically. The following sample output shows a PADO sent count
equal to the PADI received count, and PADS sent count equal to the PADR received
count. This output indicates that the PPPoE negotiation is proceeding successfully
and that the service name table is not misconfigured.
user@host> show pppoe statistics ge-2/0/3.1
When the service name table is misconfigured, the output of the
command indicates that the number of PADI packets received on the underlying
Flag
signal
state
timer
ui
[edit protocols pppoe traceoptions]
user@host# set flag authentication
show pppoe statistics
Active PPPoE sessions: 2
PacketType
PADI
PADO
PADR
PADS
PADT
Service name error
AC system error
Generic error
Malformed packets
Unknown packets
Chapter 57: Configuring Point-to-Point Protocol over Ethernet
Description
Trace signal operations
Trace state handling events
Trace timer processing
Trace user interface processing
command to examine the PPPoE packet counts for a
Sent Received
0
16
0
16
0
0
0
0
0
0
Troubleshooting PPPoE Service Name Tables
16
0
16
0
0
0
0
0
0
0
show pppoe statistics
847