 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
This chapter describes messages with the PPPD prefix. They are generated by the Point-to-Point Protocol (PPP) process (pppd), which processes packets that use PPP.
Unable to allocate authentication handle: error-message
The Point-to-Point Protocol process (pppd) could not allocate an authentication object, for the indicated reason.
Error: An error occurred
error
Interface interface-name received response 'operation' with CHAP ID message-id, but was still authenticating previous response
The Point-to-Point Protocol process (pppd) received another Challenge Handshake Authentication Protocol (CHAP) response from a peer while authenticating a previous CHAP response sent by that peer. The peer is resending CHAP responses faster than the pppd process can process them.
Error: An error occurred
error
interface-name: Unable to obtain hostname for outgoing CHAP message: error-message
The Point-to-Point Protocol process (pppd) could not obtain the hostname needed to fill in the 'Name' field in an outgoing CHAP packet.
Error: An error occurred
error
Interface interface-name received 'operation' message with CHAP ID message-id instead of expected ID expected-value
The Point-to-Point Protocol process (pppd) received a Challenge Handshake Authentication Protocol (CHAP) message from a peer that included the indicated message identifier, which did not match the indicated expected value.
Error: An error occurred
info
interface-name: received invalid operation code operation (type operation-code, CHAP ID message-id)
The Point-to-Point Protocol process (pppd) received a Challenge Handshake Authentication Protocol (CHAP) message that included the indicated operation code, which is invalid.
Error: An error occurred
error
Unable to determine value for 'Name' in outgoing CHAP packet
The Point-to-Point Protocol process (pppd) could not determine the value needed to fill in the 'Name' field in an outgoing Challenge Handshake Authentication Protocol (CHAP) packet, because either the local name was not specified or pppd could not determine the hostname.
Error: An error occurred
error
interface-name: unexpected operation type operation (CHAP ID message-id)
The Challenge Handshake Authentication Protocol (CHAP) message with the indicated identifier had the indicated operation type, which the Point-to-Point Protocol process (pppd) did not expect.
Error: An error occurred
info
interface-name: received operation with CHAP ID message-id, which is identical to an outstanding challenge. Peer is trying to exhort response value.
During an exchange of authentication messages, a peer responded to a challenge message from the Point-to-Point Protocol process (pppd) by returning the same message. The pppd process did not respond to the peer, because doing so would provide the answer to the original challenge. The peer must provide the answer on its own for authentication to succeed.
Error: An error occurred
error
Unable to create event context: error-message
The Point-to-Point Protocol process (pppd) could not create a context for handling asynchronous events, for the indicated reason.
Error: An error occurred
error
Unable to allocate LOCAL module handle: error-message
The Point-to-Point Protocol process (pppd) attempted to allocate a locally configured 'password' authentication module as part of its authentication sequence. The allocation failed.
Error: An error occurred
error
Unable to allocate memory for object object-name: error-message
The Point-to-Point Protocol process (pppd) could not allocate memory from the heap for the indicated object.
Error: An error occurred
error
Contact your technical support representative.
Unable to obtain hostname for PAP message sent from interface interface-name: error-message
The Point-to-Point Protocol process (pppd) could not obtain the hostname it needed to fill in the 'Name' field in an outgoing Password Authentication Protocol (PAP) packet sent from the indicated interface.
Error: An error occurred
error
Interface interface-name received 'operation' message with PAP ID message-id instead of expected ID expected-value
The Point-to-Point Protocol process (pppd) received a Password Authentication Protocol (PAP) message from a peer that included the indicated identifier, which did not match the indicated expected value.
Error: An error occurred
info
Interface interface-name received 'operation' message with PAP ID message-id and invalid operation code operation-code
The Point-to-Point Protocol process (pppd) received a Password Authentication Protocol (PAP) message from a peer that included the indicated operation code, which is invalid.
Error: An error occurred
error
Unable to determine value for 'Password' in outgoing PAP packet
The Point-to-Point Protocol process (pppd) could not determine the value to write in the 'Password' field in an outgoing Password Authentication Protocol (PAP) packet.
Error: An error occurred
error
The local password was not defined for the local hostname.
interface-name: unexpected operation type operation (PAP ID message-id)
The Point-to-Point Protocol process (pppd) received a Password Authentication Protocol (PAP) message with the indicated identifier and operation type. The operation type was not valid.
Error: An error occurred
info
No addresses available in pool "pool-name" to assign to remote peer on interface interface-name
The Point-to-Point Protocol process (pppd) could not assign an address from the indicated address pool to the remote peer on the indicated interface, because there were no more addresses available in the pool.
Error: An error occurred
error
Increase the number of addresses in the address pool.
Unable to add RADIUS server radius-server for profile access-profile: error-message
The Point-to-Point Protocol process (pppd) could not add the indicated RADIUS server for the indicated access profile.
Error: An error occurred
error
Unable to allocate RADIUS password of size size: error-message
The Point-to-Point Protocol process (pppd) could not allocate space for a temporary Challenge Handshake Authentication Protocol (CHAP) RADIUS password of the indicated size.
Error: An error occurred
error
Unable to allocate RADIUS module handle: error-message
The Point-to-Point Protocol process (pppd) attempted to allocate a RADIUS authentication module as part of its authentication sequence. The allocation failed.
Error: An error occurred
error
Unable to create RADIUS access request message: error-message
The Point-to-Point Protocol process (pppd) could not create an access request message to send to the RADIUS server.
Error: An error occurred
error
Unable to obtain hostname for outgoing RADIUS message: error-message
The Point-to-Point Protocol process (pppd) could not obtain the hostname it needed to fill in the PPP_IDENTIFIER field in an outgoing RADIUS message.
Error: An error occurred
error
Unknown response from RADIUS server: return-value
The RADIUS authentication module for the Point-to-Point Protocol process (pppd) received a message from the RADIUS server that it could not process.
Error: An error occurred
error
Unable to find valid RADIUS server for profile access-profile
The Point-to-Point Protocol process (pppd) could not access a valid RADIUS server to use for the indicated access profile.
Error: An error occurred
error
rad_auth_open failed: error-message
The Point-to-Point Protocol process (pppd) could not create a RADIUS object handle, which it uses to communicate with the RADIUS server.
Error: An error occurred
error
Ignored RADIUS server radius-server for profile access-profile because routing instance routing-instance did not exist
The indicated routing instance, which the Point-to-Point Protocol process (pppd) uses for routing of RADIUS packets, was not defined.
Event: This message reports an event, not an error
notice
The process of adding the required routing instance was still in progress when the message was logged.
None required. Authentication with the indicated RADIUS server is automatically reattempted, and can succeed when the interface exists.
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |