14.12.2012 Views

Junos OS Interfaces Command Reference - Juniper Networks

Junos OS Interfaces Command Reference - Juniper Networks

Junos OS Interfaces Command Reference - 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.

<strong>Junos</strong> <strong>OS</strong> 12.1 <strong>Interfaces</strong> <strong>Command</strong> <strong>Reference</strong><br />

Table 89: show pppoe underlying-interfaces Output Fields (continued)<br />

Field Name<br />

Index<br />

State<br />

Operational States<br />

Max Sessions<br />

Max Sessions VSA<br />

Ignore<br />

Active Sessions<br />

Duplicate<br />

Protection<br />

Short Cycle<br />

Protection<br />

AC Name<br />

496<br />

Field Description<br />

Index number of the logical interface, which reflects its initialization sequence.<br />

Origin of the logical interface: Static or Dynamic. Indicates whether the interface<br />

was statically or dynamically created.<br />

Fields in this block are actual operational values rather than simply the<br />

configured values. The operational values can be the result of RADIUS-initiated<br />

changes.<br />

Maximum number of PPPoE logical interfaces that can be activated on the<br />

underlying interface. When this number of logical interfaces has been<br />

established, all subsequent PPPoE Active Discovery Initiation (PADI) packets<br />

are dropped and all subsequent PPPoE Active Discovery Request (PADR)<br />

packets trigger PPPoE Active Discovery Session (PADS) error responses.<br />

Whether the router is configured to ignore (clear) the PPPoE maximum session<br />

value returned by RADIUS in the Max-Clients-Per-Interface <strong>Juniper</strong> <strong>Networks</strong><br />

VSA [26-143] and restore the PPPoE maximum session value on the underlying<br />

interface to the value configure with the max-sessions statement: Off (default)<br />

or On.<br />

Number of active PPPoE sessions on the underlying interface. If a dynamic<br />

profile is listed, then it is the number of active PPPoE sessions on the underlying<br />

interface that are using this profile. The Active Sessions value must not exceed<br />

the Max Sessions value.<br />

State of PPPoE duplicate protection: On or Off. When duplicate protection is<br />

configured for the underlying interface, a dynamic PPPoE logical interface cannot<br />

be activated when an existing active logical interface is present for the same<br />

PPPoE client. The uniqueness of the PPPoE client is determined by the client's<br />

MAC address.<br />

State of PPPoE short cycle protection: On or Off. Enabling short cycle protection,<br />

also known as PPPoE lockout, on the PPPoE underlying interface temporarily<br />

prevents (locks out) a failed or short-lived (short-cycle) PPPoE subscriber<br />

session from reconnecting to the router for a default or configurable period of<br />

time. PPPoE client sessions are identified by their unique media access control<br />

(MAC) source address.<br />

Name of the access concentrator.<br />

Level of Output<br />

detail extensive<br />

detail extensive<br />

detail extensive<br />

detail extensive<br />

detail extensive none<br />

detail extensive<br />

detail extensive<br />

detail extensive<br />

detail extensive<br />

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

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

Saved successfully!

Ooh no, something went wrong!