21.03.2013 Views

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.<br />

When the service name table is properly configured, packets sent and received increment<br />

symmetrically. The following sample output shows a PADO sent count equal to the PADI<br />

received count, and PADS sent count equal to the PADR received count. This output<br />

indicates that the PPPoE negotiation is proceeding successfully and that the service<br />

name table is not misconfigured.<br />

user@host> show pppoe statistics ge-2/0/3.1<br />

Active PPPoE sessions: 2<br />

PacketType Sent Received<br />

PADI 0 16<br />

PADO 16 0<br />

PADR 0 16<br />

PADS 16 0<br />

PADT 0 0<br />

Service name error 0 0<br />

AC system error 0 0<br />

Generic error 0 0<br />

Malformed packets 0 0<br />

Unknown packets 0 0<br />

When the service name table is misconfigured, the output of the show pppoe statistics<br />

command indicates that the number of PADI packets received on the underlying interface<br />

is increasing, but the number of PADO packets sent remains at zero. The following sample<br />

output shows a PADI count of 100 and a PADO count of 0.<br />

user@host> show pppoe statistics ge-2/0/3.1<br />

Active PPPoE sessions: 0<br />

PacketType Sent Received<br />

PADI 0 100<br />

PADO 0 0<br />

PADR 0 0<br />

PADS 0 0<br />

PADT 0 0<br />

Service name error 0 0<br />

AC system error 0 0<br />

Generic error 0 0<br />

Malformed packets 0 0<br />

Unknown packets 0 0<br />

When you believe a misconfiguration exists, use the monitor traffic interface command<br />

on the underlying interface to determine which service name is being requested by the<br />

PPPoE client. The following sample output shows that the client is requesting Service1<br />

in the service name tag.<br />

Chapter 30: Configuring Point-to-Point Protocol over <strong>Ethernet</strong><br />

user@host> monitor traffic interface ge-2/0/3.1 print-hex print-ascii<br />

Listening on ge-2/0/3.1, capture size 96 bytes<br />

11:49:41.436682 In PPPoE PADI [Service-Name "Service1"] [Host-Uniq UTF8]<br />

[TAG-0x120 UTF8] [Vendor-Specific UTF8]<br />

0x0000 ffff ffff ffff 0090 1a42 0ac1 8100 029a .........B......<br />

0x0010 8863 1109 0000 00c9 0101 0008 5365 7276 .c..........Serv<br />

0x0020 6963 6531 0103 0004 1200 9c43 0120 0002 ice1.......C....<br />

0x0030 044a 0105 00ab 0000 0de9 0124 783a 3132 .J.........$x:12<br />

0x0040 3030 3963 009c<br />

You can then use the show pppoe service-name-tables command to determine whether<br />

you have misspelled the name of the service or perhaps not configured the service at all.<br />

427

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!