ELS Messages for PPP over Ethernet (PPOE)
- Level:
- C-INFO
- Short Syntax:
- PPOE.001 Sess Up=( session_id
) AC_mac_addr
AC= AC_name
, Network_ID
- Long Syntax:
- PPOE.001 Session Stage Up=( session_id
) AC_mac_addr
AC= AC_name
, Network_ID
- Description:
- The PPPoE discovery stage was successful
and PPPoE session stage may begin now.
The Network_ID identifies which PPPoE interface
and which Ethernet is involved. Network_ID has the form
"NETxoEy" where x is the number of the virtual PPP interface
and y is the interface number of the Ethernet that
PPP is running over. For example, "NET2oE0" would mean that the
PPPoE interface is interface 2, which is running over the Ethernet
associated with interface 0.
The involved AC's name is displayed.
The session number and AC's MAC address are displayed
in the form (session_number)MAC-ADDRESS.
- Level:
- CE-ERROR
- Short Syntax:
- PPOE.002 Conn Ind Failed: cookie= cookie_hex_value
, Network_ID
- Long Syntax:
- PPOE.002 Connection Ind Failed: cookie= cookie_hex_value
, Network_ID
- Description:
- PPPoE's attempt to connect the data subchannel of the PPPoE
STACK failed.
- Action:
- None unless blocking. Call customer service if blocking.
- Level:
- UE-ERROR
- Short Syntax:
- PPOE.003 bad len: pkt_len= pkt_length
pppoe_len= pppoe_length
Eth= src_mac
-> dst_mac
( ether_type
)
- Long Syntax:
- PPOE.003 bad length: packet_len= pkt_length
pppoe_length= pppoe_length
Eth= src_mac
-> dst_mac
( ether_type
)
- Description:
- Received PPPoE packet length is too short. The length must
be at least six bytes for a PPPoE header. Packet is discarded.
Both the packet length and the length in the PPPoE header are
displayed. Ethernet header is shown. Ethernet type
is expected to be 8863 for PPPoE discovery stage or 8864 for PPPoE
session stage traffic.
- Cause:
- Such a small PPPoE packet is not useful, so the packet
has been damaged.
- Action:
- If the problem persists, examine a line trace to determine if
the packet is being damaged by the sender or the receiver.
- Level:
- UE-ERROR
- Short Syntax:
- PPOE.004 bad ver/type= version_type_byte
Eth= src_mac
-> dst_mac
( ether_type
)
- Long Syntax:
- PPOE.004 bad version/type byte= version_type_byte
Eth= src_mac
-> dst_mac
( ether_type
)
- Description:
- Received PPPoE packet did not have 0x11 in the version type byte.
- Cause:
- The other machine has a never version of PPPoE that this machine
does not support.
- Action:
- Change the software loads on your machines
so that they are running compatible versions of PPPoE.
- Cause:
- The packet has been damaged.
- Action:
- If the problem persists, examine a line trace to determine if
the packet is being damaged by the sender or the receiver.
- Level:
- UE-ERROR
- Short Syntax:
- PPOE.005 bad code= PPPoE_code_byte
Eth= src_mac
-> dst_mac
( ether_type
)
- Long Syntax:
- PPOE.005 bad code= PPPoE_code_byte
Eth= src_mac
-> dst_mac
( ether_type
)
- Description:
- Received session-stage PPPoE packet did not have 0x00 in the code byte.
- Cause:
- The packet has been damaged.
- Action:
- If the problem persists, examine a line trace to determine if
the packet is being damaged by the sender or the receiver.
- Level:
- UE-ERROR
- Short Syntax:
- PPOE.006 no matching session= session_number
Eth= src_mac
-> dst_mac
( ether_type
)
- Long Syntax:
- PPOE.006 no matching session= session_number
Eth= src_mac
-> dst_mac
( ether_type
)
- Description:
- The session number for the received PPPoE PPP session stage
packet did not match any known PPPoE session
involved with the sender of the packet.
- Cause:
- The PPPoE session has recently terminated, but the other side still
thinks that the PPPoE session stage is up.
- Action:
- None, if short-lived. If long-lasting,
the other machine may need to configure on
PPP ECHO keep-alives to detect this situation.
- Cause:
- The PPPoE session stage has just been established,
but the remainder of the PPPoE interface is still initializing and
not yet ready to receive a packet.
- Action:
- None. This should be short-lived.
- Level:
- P-TRACE
- Short Syntax:
- PPOE.007 SessIn =( session_number
) pppoe_length
len= payload_bytes
( src_mac
) AC= acname
, Network_ID
- Long Syntax:
- PPOE.007 Session Packet In: length= session_number
( pppoe_length
) AC= payload_bytes
session=( src_mac
) acname
, Network_ID
- Description:
- A PPP Session stage packet was successfully received.
is being delivered to a PPPoE interface.
The length in the PPPoE header is shown and
the first 4 bytes of the payload are shown in the form:
"len=(<4-hex-bytes>)";
the first two bytes of the payload are the PPP header bytes.
The Network_ID identifies which PPPoE interface
and which Ethernet device are involved.
The involved AC's name is displayed.
The session number and AC's MAC address are displayed
in the form sess=(session_number)MAC-ADDRESS.
- Level:
- P-TRACE
- Short Syntax:
- PPOE.008 SessOut=( session_number
) pppoe_length
len= payload_bytes
( src_mac
) AC= acname
, Network_ID
- Long Syntax:
- PPOE.008 Session Packet Out: AC= session_number
length= pppoe_length
( payload_bytes
) session=( src_mac
) acname
, Network_ID
- Description:
- A PPP Session stage packet has been built by a PPPoE interface
and is being sent.
The length in the PPPoE header is shown and
the first 4 bytes of the payload are shown in the form:
"len=(<4-hex-bytes>)";
the first two bytes of the payload are the PPP header bytes.
The Network_ID identifies which PPPoE interface
and which Ethernet are involved.
The involved AC's name is displayed.
The session number and AC's MAC address are displayed
in the form sess=(session_number)MAC-ADDRESS.
- Level:
- CE-ERROR
- Short Syntax:
- PPOE.009 I/O buf not avail, Network_ID
- Long Syntax:
- PPOE.009 I/O buffer not available, Network_ID
- Description:
- An packet buffer was not available to build a PPPoE discovery packet.
- Action:
- None if temporary. If blocking, restart/reload router
and inform customer service of the problem.
- Level:
- P-TRACE
- Short Syntax:
- PPOE.010 Snt PADI, srv_name= service_name
, Network_ID
- Long Syntax:
- PPOE.010 Sent PADI, service_name= service_name
, Network_ID
- Description:
- A PADI has been sent to the broadcast MAC address, 0xffffffffffff.
The service requested is displayed.
- Level:
- CI-ERROR
- Short Syntax:
- PPOE.011 pkt fail to dest_mac_addr
, rsn= reason_code
len= pppoe_length
( payload_bytes
), Network_ID
- Long Syntax:
- PPOE.011 pkt failed to dest_mac_addr
, rsn= reason_code
length= pppoe_length
( payload_bytes
), Network_ID
- Description:
- An attempt was made to send the PPPoE packet on the involved Ethernet
and it was not accepted for transmission for displayed reason.
The length in the PPPoE header is shown and
the first 4 bytes of the payload are shown in the form:
"len=(<4-hex-bytes>)";
- Cause:
- Reason=1. Miscellaneous handler error.
- Action:
- Check for error messages from handler.
- Cause:
- Reason=2. Congestion.
- Action:
- Alleviate congestion.
- Cause:
- Reason=3. Network down.
- Action:
- Investigate why the Ethernet is down. Check cables.
- Level:
- C-INFO
- Short Syntax:
- PPOE.012 Begin Discovery, Network_ID
- Long Syntax:
- PPOE.012 Begin Discovery, Network_ID
- Description:
- The PPPoE discovery stage is beginning from its initial state.
Any run-time config changes affecting the discovery process
becomes effective at this point.
- Level:
- UI-ERROR
- Short Syntax:
- PPOE.013 pkt too big to build, Network_ID
- Long Syntax:
- PPOE.013 pkt too big to build, Network_ID
- Description:
- The TAGS to placed into the PPPoE packet exceed the maximum size
allowed for the PPPoE packet.
- Cause:
- Service_name, AC name, etc are too big.
- Action:
- Reconfigure smaller names.
- Level:
- UI-ERROR
- Short Syntax:
- PPOE.014 pkt_type
from src_mac
, bd format
- Long Syntax:
- PPOE.014 pkt_type
from src_mac
, bd format
- Description:
- The received PPPoE packet, sent by the machine with
the displayed MAC address, could be interpretted because the TAGS
were not in the PPPoE standard 2-byte tag, 2-byte length,
value format. Possible PPPoE packet types are: PADO, PADS, PADT.
- Cause:
- Packet corrupted by one of the following: the sender,
an intermediate relay node, or the receiver.
- Level:
- UI-ERROR
- Short Syntax:
- PPOE.015 pkt_type
from src_mac
, host-uniq no-match
- Long Syntax:
- PPOE.015 pkt_type
from src_mac
, host-uniq no-match
- Description:
- The received PPPoE packet, sent by the machine with
the displayed MAC address, did not match the "host-uniq",
or host cookie, of any of current PPPoE interfaces
in the router.
- Cause:
- The AC is not repeating the host's host-uniq value in
PADO and PADS messsages as required by the standard.
- Action:
- None, if not blocking. If blocking,
upgrade and fix the software on the AC machine.
- Level:
- C-INFO
- Short Syntax:
- PPOE.016 Accept PADO from src_mac
srv_name= service_name
AC= ac_name
, Network_ID
- Long Syntax:
- PPOE.016 Accepted PADO from src_mac
service_name= service_name
AC= ac_name
, Network_ID
- Description:
- The received PADO has been accepted by the service name and
AC acceptance criteria. This completes the first
exchange of the discovery protocol.
- Level:
- C-INFO
- Short Syntax:
- PPOE.017 Refused PADO from src_mac
rsn= reject_reason
, ACerrmsg= error_msg
, Network_ID
- Long Syntax:
- PPOE.017 Refused PADO from src_mac
reason= reject_reason
, ACerrmsg= error_msg
, Network_ID
- Description:
- The received PADO was not successful and has been refused.
Possible reasons are: (1) "too-late" - the PPPoE interface is no
longer in a state ready to receive a PADO,
or the host-uniq supplied with the PADO is old and aged-out.
This will be a normal occurrence if more than one AC sends a PADO.
(2) "Serv-Name-Err", "AC-System-Err", "AC-Generic-Err" - the AC has
indicated that there is an error at the AC.
If the AC supplied an explanatory error msg, then it is displayed
after "acerrmsg=".
(3) "AC-name mis-match" - the AC's name in the PADO
did not match our configured AC-name.
(4) "no AC-name" - the PADO did not have a AC-name TAG.
(5) "service-name mis-match" - none of service(s) in the PADO
matched our configured service.
(6) "no service-name" - the PADO did not have any service-name TAGs.
- Level:
- C-TRACE
- Short Syntax:
- PPOE.018 info trace: PADO from src_mac
ac_name= ac_name
, Network_ID
- Long Syntax:
- PPOE.018 info trace: PADO from src_mac
ac_name= ac_name
, Network_ID
- Description:
- This message is here to help you learn about the AC-names
in your environment. The message displays the AC-names that
are found in any PADO packet that responds to our PADIs.
One log message is used for each AC-name in the PADO packet.
Most PADO packets will probably only contain one AC-name.
- Level:
- C-TRACE
- Short Syntax:
- PPOE.019 info trace: PADO from src_mac
srv_name= service_name
, Network_ID
- Long Syntax:
- PPOE.019 info trace: PADO from src_mac
srv_name= service_name
, Network_ID
- Description:
- This message is here to help you learn about the service names
in your environment. This message displays the
service-names in any PADO packet that responds to our PADIs.
One log message is used for each service name found
in a PADO packet. It is not unusual for a PADO packet
to contain more than one service name.
- Level:
- P-TRACE
- Short Syntax:
- PPOE.020 Snt PADR to dst_mac
, service= service_name
AC= ac_nae
, Network_ID
- Long Syntax:
- PPOE.020 Sent PADR to dst_mac
, service= service_name
AC= ac_nae
, Network_ID
- Description:
- A PADR has been sent to the chosen AC, at the displayed MAC address.
The involved service name and ac_name are shown.
- Level:
- C-INFO
- Short Syntax:
- PPOE.021 Accept PADS from src_mac
srv_name= service_name
sess= session_number
, Network_ID
- Long Syntax:
- PPOE.021 Accepted PADS from src_mac
service_name= service_name
session_id= session_number
, Network_ID
- Description:
- The received PADS from the AC is accepted and completes the
discovery stage. The interface now enters the
PPP-session stage. The PPPoE session_id assigned by the AC
is shown.
- Level:
- C-INFO
- Short Syntax:
- PPOE.022 Refused PADS from src_mac
rsn= reject_reason
ACerrmsg= error_msg
serv_name= service_name
, Network_ID
- Long Syntax:
- PPOE.022 Refused PADS from src_mac
reason= reject_reason
ACerrmsg= error_msg
service_name= service_name
, Network_ID
- Description:
- The received PADS was not successful and has been refused.
Possible reasons are: (1) "too-late" - the PPPoE interface is no
longer in a state ready to receive a PADS,
or the host-uniq supplied with the PADS is old and aged-out.
This will be a normal occurrence if more than one PADS is sent.
(2) "Serv-Name-Err", "AC-System-Err", "AC-Generic-Err" - the AC has
indicated that there is an error at the AC.
If the AC supplied an explanatory error msg, then it is displayed
after "acerrmsg=".
(3) "bad src-mac" - the AC's MAC address is not the same MAC
address learned during the PADI/PADO exchange.
(4) "service-name mis-match" - the service name in the PADS
does not match the service name sent in our PADR packet.
- Level:
- P-TRACE
- Short Syntax:
- PPOE.023 Snt PADT to dst_mac
, sess= session_number
, Network_ID
- Long Syntax:
- PPOE.023 Sent PADT to dst_mac
, session_id= session_number
, Network_ID
- Description:
- A PADT has been sent to the AC at the displayed MAC address.
The involved session number is shown.
- Level:
- U-INFO
- Short Syntax:
- PPOE.024 rcv PADT -- no matching sess= session_number
Eth= src_mac
-> dst_mac
( ether_type
)
- Long Syntax:
- PPOE.024 receive PADT -- no matching session_id= session_number
Eth= src_mac
-> dst_mac
( ether_type
)
- Description:
- The session number for the received PPPoE PADT
packet did not match any known established PPPoE session.
- Cause:
- The PPPoE session has recently already terminated
and everything is fine. One of this may be completely
normal as the session terminates.
- Action:
- None, But if the PADTs continue, inform the sender
that they are sending unwanted PADTs.
- Level:
- P-TRACE
- Short Syntax:
- PPOE.025 rcv PADT from src_mac
sess= session_number
, Network_ID
- Long Syntax:
- PPOE.025 receive PADT from src_mac
session_id= session_number
, Network_ID
- Description:
- A PADT has been received on a PPPoE interface
in the PPP-session stage; the interface will be put
back into discovery stage.