 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
This chapter describes messages with the RPD prefix. They are generated by the routing protocol process (rpd), which controls the routing protocols that run on the routing platform.
abort executable-name[pid] version version built by builder on date: error-message
The routing protocol process (rpd) terminated because of an internal error.
Error: An error occurred
error
Examine the messages that immediately follow this message in the system log for information about possible causes.
An internal software failure occurred.
Exiting with active tasks: task-name
After receiving multiple termination requests, the routing protocol process (rpd) exited without performing the indicated cleanup tasks.
Event: This message reports an event, not an error
notice
Assertion failed executable-name[pid]: file "source-filename", line line-number: "message"
The source code for the routing protocol process (rpd) includes internal self-consistency checks. A check failed at the indicated line number in the indicated source file, causing the instance of rpd that was using the indicated binary and had the indicated process ID (PID) to terminate. The process created a diagnostic core dump for analysis by technical support personnel.
Error: An error occurred
error
An internal software failure occurred.
Examine the messages that immediately follow this message in the system log for information about possible causes. Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core dump, if requested.
Soft assertion failed executable-name[pid]: file "source-filename", line line-number: "message", daemon continued running
The source code for the routing protocol process (rpd) includes internal self-consistency checks. A check failed at the indicated line number in the indicated source file, but the instance of rpd that was using the indicated binary and had the indicated process ID (PID) continued running. The process created a diagnostic core dump for analysis by technical support personnel.
Error: An error occurred
error
An internal software failure occurred.
Examine the messages that immediately follow this message in the system log for information about possible causes. Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core dump, if requested.
Read error on pipe from bfdd: reason (error-message)
The routing protocol process (rpd) could not read a message available on the read pipe from the Bidirectional Forwarding Detection process (bfdd).
Error: An error occurred
info
Contact your technical support representative.
function-name: write error on pipe to bfdd (error-message)
The routing protocol process (rpd) could not write a message on the pipe to the Bidirectional Forwarding Detection process (bfdd).
Error: An error occurred
error
Contact your technical support representative.
BGP peer peer-name changed state from old-state to new-state (event event-type)
During BGP negotiation with the local router, the state of the indicated BGP neighbor (peer) changed as indicated. The ESTABLISHED state is the final state in the neighbor negotiation.
Event: This message reports an event, not an error
warning
Received unexpected dynamic config opcode operation-code
The routing protocol process (rpd) received a dynamic configuration request with an unexpected operation code.
Error: An error occurred
error
Get dynamic profiles failed: error-code
The routing protocol process (rpd) tried to load a profile from the database and failed.
Error: An error occurred
error
Get session id client-session-id snapshot failed: error-code
The routing protocol process (rpd) tried to load client session data from the database and failed.
Error: An error occurred
error
Failed to close profile database: error-code
The routing protocol process (rpd) tried to close the profile database and failed.
Error: An error occurred
error
Failed to open profile database: error-code
The routing protocol process (rpd) tried to open the profile database and failed.
Error: An error occurred
error
Module module failed to process dynamic configuration
The routing protocol process (rpd) tried to process dynamic configuration and failed.
Error: An error occurred
error
Dynamic config registration failed: error-message
The routing protocol process (rpd) tried to register with the dynamic configuration subsystem and failed.
Error: An error occurred
error
Failed to ack request data-id: error-code
The routing protocol process (rpd) tried to acknowledge a dynamic configuration request and failed.
Error: An error occurred
error
Could not open configuration schema: error-message
The routing protocol process (rpd) tried to open the configuration schema and failed.
Error: An error occurred
error
Failed to close session database: error-code
The routing protocol process (rpd) tried to close the session database and failed.
Error: An error occurred
error
Failed to open session database: error-code
The routing protocol process (rpd) tried to open the session database and failed.
Error: An error occurred
error
Set dynamic config context for profile profile-name session client-session-idailed
The routing protocol process (rpd) tried to set up the dynamic configuration context and failed.
Error: An error occurred
error
ES-IS lost adjacency-type adjacency to neighbor-nsap-netn on interface-name, reason: reason
An ES-IS adjacency with the indicated neighboring router was terminated. The local router no longer exchanges routing information with, or directs traffic to, the neighboring router.
Event: This message reports an event, not an error
notice
The communication path to the neighboring router was disrupted, a protocol error occurred, or the neighboring router was powered down.
ES-IS new adjacency-type adjacency to neighbor-nsap-netn on interface-name
An ES-IS adjacency was established with the indicated neighboring router. The local router can now exchange information with it.
Event: This message reports an event, not an error
info
Exit executable-name[pid] version version built by builder on date, caller address
The routing protocol process (rpd) exited, either in response to a user request or because of a system error.
Event: This message reports an event, not an error
notice
A system resource was unavailable, rpd did not understand an error, or a user terminated the process.
Examine the messages that immediately follow this message in the system log for information about possible causes.
Physical interface collision -- same name, different index (new new-interface-name new-index old old-interface-name old-value)
The routing protocol process (rpd) received a message from the kernel in which the numerical index associated with the indicated interface name differed from the index-to-name mapping maintained by rpd.
Error: An error occurred
error
It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.
Physical interface collision -- different name, same index (new new-interface-name new-index, old old-interface-name old-value)
The routing protocol process (rpd) received a message from the kernel in which the name associated with the indicated numerical interface index differed from the name-to-index mapping maintained by rpd.
Error: An error occurred
error
It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.
Logical interface collision -- same name, different index (new new-interface-name new-index old old-interface-name old-value)
The routing protocol process (rpd) received a message from the kernel in which the numerical index associated with the indicated interface name differed from the index-to-name mapping maintained by rpd.
Error: An error occurred
error
It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.
Logical interface collision -- different name, same index (new new-interface-name new-index, old old-interface-name old-value)
The routing protocol process (rpd) received a message from the kernel in which the name associated with the indicated numerical interface index differed from the name-to-index mapping maintained by rpd.
Error: An error occurred
error
It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.
interface-name time
Internet Group Management Protocol (IGMP) accounting for the indicated interface was disabled at the indicated time.
Event: This message reports an event, not an error
info
interface-name time
Internet Group Management Protocol (IGMP) accounting for the indicated interface was enabled at the indicated time.
Event: This message reports an event, not an error
info
Could not create entry for entry.
Internet Group Management Protocol (IGMP) failed to create the indicated configuration entry. The configuration request failed.
Error: An error occurred
error
Contact your technical support representative.
The object-name configuration object identifier field has an invalid value of value
The configuration request failed because the indicated configuration object contained the indicated invalid value.
Error: An error occurred
error
Modify configuration statement to use a valid value.
Dynamic configuration session id client-session-id for interface interface-name is already bound to interface old-interface-name.
The indicated dynamic configuration session id is already bound to another interface. The dynamic configuration instantiation request was rejected.
Error: An error occurred
error
Unbind session id from existing interface.
Invalid dynamic configuration statement: configuration-statement
The indicated dynamic configuration statement was invalid. The dynamic configuration instantiation request was rejected.
Error: An error occurred
error
Remove the unsupported configuration statement.
Dynamic configuration entry for interface interface-name with session id client-session-id found an existing entry with a different session id of client-session-id-1.
The dynamic configuration instantiation request matched an existing dynamic configuration block that had a different session id. The dynamic configuration instantiation request was rejected.
Error: An error occurred
error
Contact your technical support representative.
Listener source-address sent a join to destination-address for group group-address source sender-address on interface interface-name at time
IGMP join event.
Event: This message reports an event, not an error
info
Listener source-address sent a leave to destination-address for group group-address source sender-address on interface interface-name at time
IGMP leave event.
Event: This message reports an event, not an error
info
Membership timeout for listener source-address for group group-address source sender-address on interface interface-name at time
IGMP group membership timeout.
Event: This message reports an event, not an error
info
IS-IS lost Lisis-level adjacency to neighbor-system-ids on interface-name, reason: reason
An IS-IS adjacency with the indicated neighboring router was terminated. The local router no longer exchanges routing information with, or directs traffic to, the neighboring router.
Event: This message reports an event, not an error
notice
The communication path to the neighboring router was disrupted, a protocol error occurred, or the neighboring router was powered down.
IS-IS new Lisis-level adjacency to neighbor-system-ids on interface-name
An IS-IS adjacency was established with the indicated neighboring router. The local router can now exchange information with it.
Event: This message reports an event, not an error
info
IS-IS new Lisis-level adjacency to neighbor-system-ids on interface-name without an address
An IS-IS adjacency was established with the indicated neighboring router, which is not configured for IS-IS for IP.
Event: This message reports an event, not an error
notice
The neighboring router is misconfigured: it is enabled for IS-IS but not for exchange of IP route information.
Configure the neighboring router for IS-IS with IP, or remove it from the IS-IS mesh.
IS-IS interface interface-name advertised with infinite metric for duration seconds already due to loss of synchronization with LDP
The IS-IS protocol lost synchronization with the Label Distribution Protocol (LDP) on the indicated interface. As a consequence, it began advertising an infinite metric for the interface and has been doing so for the indicated number of seconds.
Error: An error occurred
warning
Determine why LDP lost synchronization with IS-IS.
IS-IS Lisis-level LSP checksum error, interface interface-name, LSP id lspl, sequence sequence-number, checksum checksum, lifetime duration
The indicated IS-IS informational link-state PDU (LSP) failed an internal checksum validity test, implying that it was corrupted.
Error: An error occurred
warning
The packet was corrupted in transit between the neighboring IS-IS router and this router, or memory on one of the routers was corrupted.
None, unless a large number of these messages appear in the system log file. The corrupted LSP is silently discarded.
IS-IS instance does not have a valid router ID
The IS-IS instance did not have a valid router ID.
Error: An error occurred
alert
When a router ID is not explicitly configured for an instance, IPv4 addresses configured under the instance are considered in the selection of the router ID. In this case, the instance did not have a router ID configured and no IPv4 addresses were configured.
Either configure a router ID by including the 'routing-instance' statement under the instance, or configure an IPv4 address by including the 'family inet' statement under one of the interfaces of the instance. You can also configure both.
IS-IS database overload
The IS-IS link-state database is full and no additional memory can be allocated for it.
Error: An error occurred
alert
No additional memory is available for storing IS-IS link-state information. Either system resources are exhausted or a software error occurred (such as a memory leak in the routing protocol process [rpd]). In the former case, IS-IS might be carrying too much information, or the router configuration includes too many features that use large amounts of system memory.
Perform one or more of the following actions: (1) Check for unusually high memory usage by the IS-IS task or rpd, (2) Unconfigure features that use large amounts of memory, (3) Add more memory to the Routing Engine, (4) Carry fewer IS-IS routes.
error-code, error-message
The routing protocol process (rpd) attempted to modify the state for a logical interface that is related to circuit cross-connect (CCC), but the request failed.
Event: This message reports an event, not an error
info
It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.
task-name: received deleted routing table from the kernel for family address-family-type table ID table-id
The routing protocol process (rpd) received a message from the kernel that referred to a routing table that no longer exists.
Error: An error occurred
error
ifa generation mismatch -- rpd rpd-generation kernel kernel-generation
The routing protocol process (rpd) received a message from the kernel in which the interface address associated with the indicated numerical index differed from the address-to-index mapping maintained by rpd.
Event: This message reports an event, not an error
notice
It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.
task-name CHANGE for ifd interface-device-index address/prefix-length failed, error "error-message"
The routing protocol process (rpd) sent a request to the kernel to change the state of the indicated interface. The request failed.
Error: An error occurred
error
It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.
task-name IFDEST GET for ifd rpd-interface-name failed, error "error-message"
The routing protocol process (rpd) requested state information about the indicated interface from the kernel. The request failed.
Error: An error occurred
error
It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.
task-name GET index for ifd interface-name failed, error "error-message"
The routing protocol process (rpd) requested state information about the indicated interface from the kernel. The request failed.
Error: An error occurred
error
It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.
Invalid mode (mode) specified for interface device interface-name; defaulting to port mode
The routing protocol process (rpd) received a message from the kernel that specified the cell-relay encapsulation for the indicated physical interface, but the specified cell-relay mode (port, or trunk user-to-network interface [UNI], or trunk network-to-network interface [NNI]) was invalid.
Error: An error occurred
notice
No mode specified for interface device interface-name; defaulting to port mode
The routing protocol process (rpd) received a message from the kernel that specified the cell-relay encapsulation for the indicated physical interface, but not the cell-relay mode.
Error: An error occurred
notice
ifd interface-device-index generation mismatch -- rpd rpd-generation kernel kernel-generation
The routing protocol process (rpd) received a message from the kernel in which the physical interface associated with the indicated numerical index differed from the interface-to-index mapping maintained by rpd.
Event: This message reports an event, not an error
notice
It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.
Invalid mode (mode) specified for logical interface interface-name; defaulting to port mode
The routing protocol process (rpd) received a message from the kernel that specified the cell-relay encapsulation for the indicated logical interface, but the specified cell-relay mode (port, virtual-circuit, or virtual-path) was invalid.
Error: An error occurred
notice
No mode specified for logical interface interface-name; defaulting to port mode
The routing protocol process (rpd) received a message from the kernel that specified the cell-relay encapsulation for the indicated logical interface but not the cell-relay mode.
Error: An error occurred
notice
ifl logical-interface-index generation mismatch -- rpd rpd-interface-name rpd-generation kernel kernel-interface-name.kernel-interface-unit kernel-generation
The routing protocol process (rpd) received a message from the kernel in which the logical interface associated with the indicated numerical index differed from the interface-to-index mapping maintained by rpd.
Event: This message reports an event, not an error
notice
It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.
task-name: lost interface-hierarchy logical-interface-index for route route-prefix
As it restarted, the routing protocol process (rpd) could not process a route obtained from the kernel because the route contained references to objects that are no longer valid.
Event: This message reports an event, not an error
warning
rpd did not recognize some elements in the route message, such as the logical interface index or an address family.
rpd can probably solve the problem, but check the entry for the indicated route prefix in the forwarding table. If the prefix's route and forwarding table entry are inconsistent, contact a technical support representative for instructions.
type route-prefix: number of next hops (count) exceeded the maximum allowed (maximum-value) -- truncating
The number of next hops for the indicated route exceeded the indicated limit for a single route add operation.
Error: An error occurred
error
An indexed next hop can use multiple forwarding next hops per forwarding class. It is possible to have more next hops per route than can be carried in a single message. This requires that next hops be reused across forwarding classes, which is not recommended.
Eliminate common next hops across forwarding classes, thereby reducing the total number of next hops that must be specified.
No device interface-device-index for interface logical-interface-index (interface-name)
The routing protocol process (rpd) received a message from the kernel that associated the indicated physical interface device and logical interface. The rpd process has no record of the device.
Error: An error occurred
error
It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.
Routing socket version mismatch (kernel kernel-version != rpd rpd-version) -- kernel upgrade required
The routing protocol process (rpd) discovered that the kernel does not support the version of routing sockets it requires.
Error: An error occurred
error
The kernel version is older than the rpd version.
Upgrade the kernel package.
Routing socket message type message-type's version is not supported by kernel, expected rpd-version -- kernel upgrade required
The routing protocol process (rpd) discovered that the kernel does not support the routing socket message types that it requires.
Error: An error occurred
error
The kernel version is older than the rpd version.
Upgrade the kernel package.
Routing socket message type message-type's version is older than expected (kernel-version <rpd-version) -- consider upgrading the kernel
The routing protocol process (rpd) discovered that the kernel uses an older version of routing socket message types than it does.
Error: An error occurred
error
The kernel version is older than the rpd version.
Upgrade the kernel package.
Unable to modify VPLS-related state: error-code (errno error-message)
The routing protocol process (rpd) attempted to modify the state for a logical interface that is related to virtual private LAN service (VPLS), but the request failed.
Event: This message reports an event, not an error
info
It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.
Unable to allocate label-type labels for site name with ID identifier in instance vpn-name
The routing protocol process (rpd) could not allocate labels of the indicated type for the indicated site (name and ID) in the indicated virtual private network (VPN) virtual circuit (VC), because the resulting number of labels would have exceeded the limit.
Error: An error occurred
error
Two remote PEs (RDs route-discriminator and route-discriminator2) have the same site ID (identifier) in VPN vpn-name
The routing protocol process (rpd) for the indicated virtual private network (VPN) received an advertisement from a remote provider edge (PE) router with the first indicated route discriminator, but the associated site ID also belongs to a remote site with the second route discriminator.
Event: This message reports an event, not an error
warning
Same site ID identifier configured on remote PE (RD route-discriminator) and local PE in VPN vpn-name (non-multihomed site name)
The routing protocol process (rpd) for the indicated virtual private network (VPN) received an advertisement from a remote provider edge (PE) router, but the associated site ID belongs to a local site.
Event: This message reports an event, not an error
error
State of Layer 2 VC vc-name changed from UP to state
The state of the indicated Layer 2 virtual private network (VPN) virtual circuit (VC) changed as indicated (to either down or deleted).
Event: This message reports an event, not an error
notice
State of Layer 2 VC vc-name changed to UP
The state of the indicated Layer 2 virtual private network (VPN) virtual circuit (VC) changed to up.
Event: This message reports an event, not an error
info
LDP BFD session for FEC fec-address went down
The routing protocol process (rpd) determined that the Label Distribution Protocol (LDP) Bidirectional Forwarding Detection (BFD) protocol session for the indicated forwarding equivalence class (FEC) terminated.
Event: This message reports an event, not an error
notice
LDP BFD sessions for FEC fec-address going down due to traceroute failure
The routing protocol process (rpd) determined that the Label Distribution Protocol (LDP) Bidirectional Forwarding Detection (BFD) protocol session for the indicated forwarding equivalence class (FEC) was terminated due to traceroute failure.
Event: This message reports an event, not an error
notice
LDP BFD session for FEC fec-address came up
The routing protocol process (rpd) determined that the Label Distribution Protocol (LDP) Bidirectional Forwarding Detection (BFD) protocol session for the indicated forwarding equivalence class (FEC) came up.
Event: This message reports an event, not an error
notice
Duplicate session ID detected from neighbor-addressi, interface interface-name, blocking interface
Label Distribution Protocol (LDP) operations were blocked on the indicated interface because the same session ID was detected across multiple interfaces but per-interface transport addresses are in use.
Event: This message reports an event, not an error
warning
LDP interface interface-name is now unblocked
The indicated interface returned to the normal Label Distribution Protocol (LDP) operational state. It was previously blocked because the routing protocol process (rpd) noticed that a duplicate session ID was being used.
Event: This message reports an event, not an error
warning
LDP neighbor neighbor-addressi (interface-name) is down
A Label Distribution Protocol (LDP) adjacency was terminated because the indicated neighbor stopped communicating. If the adjacency was the only one with this neighbor, the routing protocol process (rpd) terminated the associated LDP session.
Event: This message reports an event, not an error
notice
LDP neighbor neighbor-addressi (interface-name) is up
A Label Distribution Protocol (LDP) adjacency with the indicated neighbor became active. The routing protocol process (rpd) established an LDP session with the neighbor if one did not already exist.
Event: This message reports an event, not an error
info
LDP session neighbor-addressi is down, reason: reason
The routing protocol process (rpd) terminated a Label Distribution Protocol (LDP) session with the indicated neighbor and deleted all labels exchanged during the session.
Event: This message reports an event, not an error
notice
LDP session neighbor-addressi is up
The routing protocol process (rpd) established a Label Distribution Protocol (LDP) session with the indicated neighbor. The routers began exchanging labels.
Event: This message reports an event, not an error
info
Unknown context in ALLOC_ACK message
The routing protocol process (rpd) received a label allocation acknowledgment that contained invalid context.
Error: An error occurred
error
Allocation request timeout for context 0xaddress, client request ID 0xrequest-id
The label allocation request with the indicated client request ID and for the indicated context timed out before completion.
Event: This message reports an event, not an error
error
operation operation failed: control channel logical-interface-index unknown
The routing protocol process (rpd) received a message that specified the indicated type of operation on the indicated control channel. The channel does not exist.
Error: An error occurred
error
No function callback for label removed event
The routing protocol process (rpd) could not notify a client that a label was removed, because there was no function callback for the removal event.
Error: An error occurred
error
function-name: malloc() failed (error-message, errno error-code)
The routing protocol process (rpd) could not allocate memory.
Error: An error occurred
error
An internal software failure occurred.
Peer peer-id not found for TE link link-name (index link-id)
The routing protocol process (rpd) could not locate the indicated peer while processing a TE LINK message for the traffic-engineering link with the indicated name and index.
Error: An error occurred
error
operation operation failed: peer peer-name (index peer-id) reason
The routing protocol process (rpd) could not perform the indicated operation for the peer with the indicated name and index, for the indicated reason.
Error: An error occurred
error
operation operation failed because reason for peer peer-name (index peer-id): error-message (errno error-code)
The routing protocol process (rpd) could not perform the indicated operation for the peer with the indicated name and index, for the indicated reason.
Error: An error occurred
error
No more peer indexes
No more peer indexes were available for allocation.
Event: This message reports an event, not an error
error
operation operation failed: resource resource (type type, index index) reason
The routing protocol process (rpd) could not perform the indicated operation for the resource with the indicated name, type, and index, for the indicated reason.
Error: An error occurred
error
TE link link-id not found for resource resource (type type, index index)
The routing protocol process (rpd) could not locate the indicated traffic-engineering link for the resource with the indicated name, type, and index.
Error: An error occurred
error
function-name: handling write exception (error-message, errno error-code)
The routing protocol process (rpd) could not send a message to the Label Management Protocol (LMP) process (lmpd).
Error: An error occurred
error
Unable to send allocation message: error-message (error-code)
The routing protocol process (rpd) could not send an allocation message.
Error: An error occurred
error
Unable to start type timer
The routing protocol process (rpd) discovered that the Label Management Protocol (LMP) process (lmpd) was not running. The rpd process attempted to start the indicated type of timer for restarting the lmpd process or reestablishing a connection to it, but the attempt failed.
Error: An error occurred
error
An internal software failure occurred.
Examine the messages that immediately follow this message in the system log for information about possible reasons that lmpd failed.
operation operation failed: TE link link-name (index index) reason
The routing protocol process (rpd) could not perform the indicated operation for the traffic-engineering link with the indicated name and index, for the indicated reason.
Error: An error occurred
error
No more TE-link indexes
No more traffic-engineering link indexes were available for allocation.
Event: This message reports an event, not an error
error
message-type message had unexpected operation code operation-code
The routing protocol process (rpd) received the indicated type of message, which had the indicated invalid operation code.
Error: An error occurred
error
Unable to obtain a lock on filename, is another copy of rpd running?
The routing protocol process (rpd) could not obtain the mutual exclusion lock that prevents more than one instance of rpd from running simultaneously. The system terminated the indicated process.
Error: An error occurred
error
Another rpd process is running.
Use the 'show system process' command to verify that another rpd is running.
Unable to obtain a lock on filename, program-name[pid] is still running
The routing protocol process (rpd) could not obtain the mutual exclusion lock that prevents more than one instance of rpd from running simultaneously. The system terminated this instance of rpd.
Error: An error occurred
error
Another rpd is running.
Use the 'show system process' command to verify that another rpd is running.
Designated forwarder changed to ip-address for backup-pe-group group-name in routing-instance instance
The routing protocol daemon (rpd) assigned the indicated Provider Edge (PE) as the new designated forwarder of the indicated routing instance for the indicated backup-pe-group.
Event: This message reports an event, not an error
notice
Local PE is now the designated forwarder for backup-pe-group group-name in routing-instance instance
The routing protocol daemon (rpd) selected the local Provider Edge (PE) as the designated forwarder of the indicated routing instance for the indicated backup-pe-group.
Event: This message reports an event, not an error
notice
Interface interface-name is rejected due to lack of bw
When multicast bandwidth admission control is applied, an interface may not be put into the downstream interface list for a forwarding cache if the interface does not have enough bandwidth for the flow, even when a multicast protocol determines that there are local/downstream receivers.
Event: This message reports an event, not an error
info
Interface interface-name is re-admitted with newly available bw
The indicated downstream interface that was previously rejected was readmitted for the flow because there was newly availabe bandwidth on the interface.
Event: This message reports an event, not an error
info
Connection to management peer process-name timed out waiting for input
The connection between the routing protocol process (rpd) and the indicated management process (mgd) timed out before input arrived from the mgd process.
Error: An error occurred
warning
Unable to establish mirror connection between Routing Engines: error-message
The routing protocol process (rpd) could not establish the mirror connection (which supports nonstop routing) between the master and backup Routing Engines.
Error: An error occurred
warning
The master and backup Routing Engines are running incompatible versions of the JUNOS software.
Update the JUNOS software to compatible versions on the master and backup Routing Engines.
Versions of mirror software on Routing Engines are incompatible: error-message
While trying to establish the mirror connection between the master and backup Routing Engines (which supports nonstop routing), the routing protocol process (rpd) determined that the versions of JUNOS software on the Routing Engines were incompatible.
Error: An error occurred
warning
Update the JUNOS software to compatible versions on the master and backup Routing Engines.
interface-name time
The Multicast Listener Discovery (MLD) accounting for the indicated interface was disabled at the indicated time.
Event: This message reports an event, not an error
info
interface-name time
The Multicast Listener Discovery (MLD) accounting for the indicated interface was enabled at the indicated time.
Event: This message reports an event, not an error
info
Could not create entry for entry.
MLD failed to create the indicated configuration entry. The configuration request failed.
Error: An error occurred
error
Contact your technical support representative.
The object-name configuration object identifier field has an invalid value of value
The configuration request failed because the indicated configuration object contained the indicated invalid value.
Error: An error occurred
error
Modify configuration statement to use a valid value.
Invalid dynamic configuration statement: configuration-statement
The indicated dynamic configuration statement was invalid. The dynamic configuration instantiation request was rejected.
Error: An error occurred
error
Remove the unsupported configuration statement.
Dynamic configuration entry for interface interface-name with session id client-session-id found an existing entry with a different session id of client-session-id-1.
The dynamic configuration instantiation request matched an existing dynamic configuration block that had a different session id. The dynamic configuration instantiation request was rejected.
Error: An error occurred
error
Contact your technical support representative.
Listener source-address sent a join to destination-address for group group-address source sender-address on interface interface-name at time
MLD join event.
Event: This message reports an event, not an error
info
Listener source-address sent a leave to destination-address for group group-address source sender-address on interface interface-name at time
MLD leave event.
Event: This message reports an event, not an error
info
Membership timeout for listener source-address for group group-address source sender-address on interface interface-name at time
MLD group membership timeout.
Event: This message reports an event, not an error
info
MPLS LSP lsp-name bandwidth changed, lsp bandwidth bandwidth bps
The bandwidth associated with the indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) changed.
Event: This message reports an event, not an error
warning
MPLS LSP lsp-name change on path-type(pathname) Route lsp-rro lsp bandwidth bandwidth bps
The indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) was rerouted and its Record Route Object (RRO) changed.
Event: This message reports an event, not an error
warning
MPLS LSP lsp-name down on path-type(pathname)
The indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) went down and could not be used to send traffic.
Event: This message reports an event, not an error
warning
MPLS LSP lsp-name switch from old-path-type(old-pathname) to new-path-type(new-pathname), Route lsp-rro: reason lsp bandwidth bandwidth bps
The indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) switched from primary path to secondary path or vice versa.
Event: This message reports an event, not an error
warning
MPLS LSP lsp-name up on path-type(pathname) Route lsp-rro lsp bandwidth bandwidth bps
The indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) came up and could be used to send traffic.
Event: This message reports an event, not an error
warning
Unable to read from pipe to MPLS OAM process: reason (error-message)
The routing protocol process (rpd) could not read a message available on the read pipe from the MPLS Operation, Administration, and Maintenance process (mplsoamd).
Error: An error occurred
info
Contact your technical support representative.
Unable to write to pipe to MPLS OAM process: (error-message)
The routing protocol process (rpd) could not write a message on the write pipe to the MPLS Operation, Administration, and Maintenance process (mplsoamd).
Error: An error occurred
info
Contact your technical support representative.
MPLS path pathname (lsp lsp-name) bandwidth changed, path bandwidth bandwidth bps
The bandwidth associated with the indicated Multiprotocol Label Switching (MPLS) path changed.
Event: This message reports an event, not an error
warning
BFD session for MPLS path pathname went down on LSP lsp-name
The routing protocol process (rpd) determined that the Bidirectional Forwarding Detection (BFD) protocol session for the indicated Multiprotocol Label Switching (MPLS) path terminated on the indicated label-switched path (LSP).
Event: This message reports an event, not an error
notice
BFD session for MPLS path pathname came up on LSP lsp-name
The routing protocol process (rpd) determined that the Bidirectional Forwarding Detection (BFD) protocol session for the the indicated Multiprotocol Label Switching (MPLS) path came up on the indicated label-switched path (LSP).
Event: This message reports an event, not an error
notice
Unable to satisfy bandwidth configured for MPLS path pathname on LSP lsp-name
The bandwidth setting for the indicated Multiprotocol Label Switching (MPLS) path and label-switched path (LSP) was changed recently, but attempts to apply the new setting failed. The LSP continued to use the previous amount of bandwidth.
Event: This message reports an event, not an error
warning
Determine the reason that the bandwidth could not change and make the necessary changes to the software configuration, hardware configuration, or both.
MPLS path pathname down on LSP lsp-name
The indicated Multiprotocol Label Switching (MPLS) path went down on the indicated label-switched path (LSP).
Event: This message reports an event, not an error
warning
MPLS path pathname up on LSP lsp-name path bandwidth bandwidth bps
The indicated Multiprotocol Label Switching (MPLS) path came up on the indicated label-switched path (LSP).
Event: This message reports an event, not an error
warning
MSDP peer peer-address peer-group peer-group out of Established state
The indicated MSDP peer left the Established state. The routing protocol process (rpd) deleted all active sources learned from the peer and will no longer send 'Source Active' messages to it.
Event: This message reports an event, not an error
notice
MSDP peer peer-address peer-group peer-group into Established state
The indicated MSDP peer entered the Established state.
Event: This message reports an event, not an error
info
Number of MSDP source-active messages about originator exceeded configured limit message
The number of MSDP source-active messages received from the indicated instance, peer, or source exceeded the configured limit. All source-active messages are discarded until the limit is no longer exceeded. During periods when the event reported by this message occurs frequently, the routing protocol process (rpd) does not log every occurrence. In this case, the repetitions field in the message indicates how many times the event occurred since the rpd process previously logged this message.
Event: This message reports an event, not an error
notice
Number of MSDP source-active messages about originator exceeded configured threshold message
The number of MSDP source-active messages received from the indicated instance, peer, or source exceeded the configured threshold. Until the threshold is no longer exceeded, a random early discard (RED) profile is applied to incoming messages so that only some of them are accepted. During periods when the event reported by this message occurs frequently, the routing protocol process (rpd) does not log every occurrence. In this case, the repetitions field in the message indicates how many times the event occurred since the rpd process previously logged this message.
Event: This message reports an event, not an error
notice
Number of MSDP source-active messages about originator no longer exceeded configured limit message
The number of MSDP source-active messages received from the indicated instance, peer, or source no longer exceeded the configured limit. Active-source messages are no longer discarded automatically. During periods when the event reported by this message occurs frequently, the routing protocol process (rpd) does not log every occurrence. In this case, the repetitions field in the message indicates how many times the event occurred since the rpd process previously logged this message.
Event: This message reports an event, not an error
notice
Number of MSDP source-active messages about originator no longer exceeded configured threshold message
The number of MSDP source-active messages received from the indicated instance, peer, or source no longer exceeded the configured threshold. A random early discard (RED) profile is no longer applied to incoming messages. During periods when the event reported by this message occurs frequently, the routing protocol process (rpd) does not log every occurrence. In this case, the repetitions field in the message indicates how many times the event occurred since the rpd process previously logged this message.
Event: This message reports an event, not an error
notice
Ignored configured neighbors on point-to-point realm realm-name interface interface-name area area-idi
For point-to-point interfaces, OSPF neighbors are learned by using hello messages, so the implicit configuration of neighbors was ignored for the indicated point-to-point interface.
Error: An error occurred
warning
Remove the neighbor configuration for the indicated interface.
OSPF realm realm-name interface interface-name area area-idi advertised with infinite metric for duration seconds already due to loss of synchronization with LDP
The OSPF protocol lost synchronization with the Label Distribution Protocol (LDP) on the indicated interface. As a consequence, it began advertising an infinite metric for the interface and has been doing so for the indicated number of seconds.
Error: An error occurred
warning
Determine why LDP lost synchronization with OSPF.
OSPF neighbor neighbor-address (realm realm-name interface-name area area-idi) state changed from old-state to new-state due to event-name (event reason: reason)
An OSPF adjacency with the indicated neighboring router was terminated. The local router no longer exchanges routing information with, or directs traffic to, the neighboring router.
Event: This message reports an event, not an error
notice
OSPF neighbor neighbor-address (realm realm-name interface-name area area-idi) state changed from old-state to new-state due to event-name (event reason: reason)
An OSPF adjacency was established with the indicated neighboring router. The local router can now exchange information with it.
Event: This message reports an event, not an error
info
OSPF instance instance topology topology is going into overload state: number of export prefixes (count) exceeded maximum allowed (maximum-value)
The indicated topology in the indicated OSPF instance became overloaded and will remain in that state until an administrator intervenes.
Error: An error occurred
warning
The number of export prefixes exceeded the configured limit.
Unconfigure or modify export policies that inject a large number of routes.
Using size KB of memory, percentage-value percent of available
The routing protocol process (rpd) is using the indicated amount and percentage of Routing Engine memory, which is considered excessive.
Error: An error occurred
error
Either rpd is leaking memory or the use of system resources is excessive, perhaps because routing filters are misconfigured or the configured network topology is very complex.
Increase the amount of RAM in the Routing Engine.
executable-name: logical router name "logical-router-name"exceeds count characters
The indicated logical router name exceeds the indicated maximum number of characters.
Error: An error occurred
error
Assign a shorter name.
executable-name: command-line option option is invalid
The command line used to start the indicated process included the indicated option, which is invalid. The process did not start.
Error: An error occurred
error
Reissue the command without the invalid option.
executable-name: missing required argument for command-line option option
The command line used to start the indicated process did not include the argument required by the indicated option. The process did not start.
Error: An error occurred
error
Reissue the command and include the required argument.
executable-name: command-line option option is a duplicate
The command line used to start the indicated process included the indicated duplicate option. The process did not start.
Error: An error occurred
error
Reissue the command without the duplicate option.
executable-name: command-line option option is extraneous
The command line used to start the indicated process included the indicated option, which is extraneous. The process did not start.
Error: An error occurred
error
Reissue the command and omit the extraneous option.
PIM neighbor neighbor-address (interface-name) removed due to: reason
The routing protocol process (rpd) declared the indicated PIM neighbor inactive.
Event: This message reports an event, not an error
notice
PIM new neighbor neighbor-address interface interface-name
The routing protocol process (rpd) discovered the indicated new PIM neighbor on the indicated interface.
Event: This message reports an event, not an error
info
Read error on pipe from ppmd: reason (error-message)
The routing protocol process (rpd) could not read a message available on the read pipe from the periodic packet management process (ppmd).
Error: An error occurred
info
Contact your technical support representative.
function-name: write error on pipe to ppmd (error-message)
The routing protocol process (rpd) could not write a message on the pipe to the periodic packet management process (ppmd).
Error: An error occurred
error
Contact your technical support representative.
Bad checksum for router solicitation from source-address to destination-address
The routing protocol process (rpd) ignored a router discovery solicitation message from the indicated address because the checksum in the message's ICMP header was invalid.
Event: This message reports an event, not an error
warning
The solicitation message was incorrectly generated or damaged in transit.
Examine the host that generated the solicitation message.
Ignoring interface interface-address on interface-name -- multicast not available
The indicated interface was configured for router discovery, but does not support IP multicast operations as required. The routing protocol process (rpd) did not enable router discovery on the interface.
Error: An error occurred
warning
Do not configure router discovery on the interface.
Unable to locate interface for router solicitation from source-address to destination-address
The routing protocol process (rpd) ignored a router discovery solicitation message from the indicated router because the router's IP address does not share the IP prefix of the local router. The local router is not a candidate for the indicated router because they are not on the same network.
Event: This message reports an event, not an error
warning
Although the indicated router seems to be locally attached, no interfaces on the local router are configured to handle its IP address. Either the indicated router is configured with the wrong IP address, or the local router is not correctly configured for the network that the indicated router is using.
Ignore this message if it indicates the desired configuration, or reconfigure one or both routers to share a common network.
Expected multicast (expected-address) for router solicitation from source-address to destination-address
A router discovery solicitation message received from the indicated address was not sent to the expected multicast address for all routers.
Event: This message reports an event, not an error
warning
Examine the configuration of the router that generated the router discovery solicitation message.
Nonzero ICMP code (value) for router solicitation from source-address to destination-address
The routing protocol process (rpd) ignored a router discovery solicitation message from the indicated router because the ICMP code in the message header was nonzero.
Event: This message reports an event, not an error
warning
The solicitation message was incorrectly generated.
Examine the host that generated the solicitation message.
Insufficient length (length) for router solicitation from source-address to destination-address
The routing protocol process (rpd) ignored a router discovery solicitation message from the indicated router, because the indicated message length is too short.
Event: This message reports an event, not an error
warning
The solicitation message was incorrectly generated.
Examine the host that generated the solicitation message.
Update with invalid authentication from source-address (interface-name)
The routing protocol process (rpd) ignored a RIP update because authentication of the update failed.
Event: This message reports an event, not an error
notice
Unable to get broadcast address on interface-name; using the all-ones address
RIP cannot run on the indicated interface because the routing protocol process (rpd) could not obtain the broadcast address on the interface as required for running RIP version 1 or version 2 in compatibility mode.
Error: An error occurred
error
Unable to join multicast group on interface-name: error-message
RIP cannot run on the indicated interface, because the routing protocol process (rpd) could not join the RIP multicast group as required for RIP version 2 multicast updates.
Error: An error occurred
error
Backup for protecting LSP lsp-name down, using bypass bypass-lsp-namereason
When link protection is enabled, a backup label-switched path (LSP) is needed to maintain a protected LSP's control-plane connectivity when topology failures are detected. The backup LSP for the indicated protected LSP failed. The failure can cause traffic loss because the protected LSP tears down when there is no backup. If the reason for the backup failure can be determined, it is reported in the message.
Event: This message reports an event, not an error
warning
RSVP bypass bypass-lsp-name for protecting interface interface-name went downreason
The indicated RSVP link-protection bypass, which was protecting the indicated interface, was terminated. If the reason for the termination can be determined, it is reported in the message.
Event: This message reports an event, not an error
warning
RSVP bypass bypass-lsp-name for protecting interface interface-name came up
The indicated RSVP link-protection bypass was established to protect the indicated interface.
Event: This message reports an event, not an error
warning
RSVP LSP lsp-name switched to backup; using bypass LSP bypass-lsp-name, route lsp-rro
RSVP detected a failure downstream for the indicated label-switched path (LSP) and switched it to a backup using the indicated bypass LSP.
Event: This message reports an event, not an error
warning
The downstream interface or router for the LSP went down.
RSVP maximum session limit of limit reached
The routing protocol process (rpd) could not set up an RSVP session because the indicated limit on the number of sessions was reached.
Event: This message reports an event, not an error
warning
RSVP neighbor neighbor-address down on interface interface-name, reason
The RSVP neighbor to the indicated address was terminated.
Event: This message reports an event, not an error
warning
The communication path to the neighboring router was disrupted, a protocol error occurred, or the neighboring router was powered down.
RSVP neighbor neighbor-address up on interface interface-name
An RSVP neighbor was established to the indicated address.
Event: This message reports an event, not an error
warning
routing-instance routing-instance has duplicate route-distinguisher route-discriminator as routing-instance existing-routing-instance
The route-distinguisher assigned to this routing instance has already been assigned to another routing instance (as indicated).
Error: An error occurred
error
rt_event_event-name: fatal state error
A route in the routing table was found to be in an unrecoverable error state.
Error: An error occurred
critical
UP route for interface interface-name index logical-interface-index address/prefix-length
The interface route for the indicated interface and prefix changed state from down to up, becoming available for routing.
Event: This message reports an event, not an error
warning
Number of paths (count) in table table-name is now less than the configured maximum (limit)
The number of paths in the indicated routing table previously equaled or exceeded the indicated limit, but went down to the indicated number, which is below the limit.
Event: This message reports an event, not an error
warning
Number of paths (count) in table table-name status configured maximum (limit)
The indicated total number of paths in the indicated routing table equaled or exceeded the indicated configured limit. Attempts to add some types of path to the table fail while this condition holds, but the path count can exceed the limit if paths are forcibly added (for example, for static routes). This message first appears in the log when the limit is reached and repeats periodically until the number of paths goes below the limit.
Error: An error occurred
error
Number of paths (count) in table table-name reached warning threshold (threshold percent of configured maximum limit)
The indicated total number of paths in the indicated routing table reached the threshold for a warning. The threshold is the indicated percentage of the indicated configured limit on the number of paths.
Event: This message reports an event, not an error
warning
Number of prefixes (prefix-count) in table table-name is now less than the configured maximum (limit)
The number of prefixes in the indicated routing table previously equaled or exceeded the indicated limit, but went down to the indicated number, which is below the limit.
Event: This message reports an event, not an error
warning
Number of prefixes (prefix-count) in table table-name status configured maximum (limit)
The indicated total number of prefixes in the indicated routing table equaled or exceeded the indicated configured limit. Attempts to add some types of prefix to the table fail while this condition holds, but the prefix count can exceed the limit if prefixes are forcibly added (for example, for static routes). This message first appears in the log when the limit is reached and repeats periodically until the number of prefixes goes below the limit.
Error: An error occurred
error
Number of prefixes (prefix-count) in table table-name reached warning threshold (threshold percent of configured maximum limit)
The indicated total number of prefixes in the indicated routing table reached the threshold for a warning. The threshold is the indicated percentage of the indicated configured limit on the number of prefixes.
Event: This message reports an event, not an error
warning
invalid display mode (mode)
The indicated display mode was specified in a 'show route' command and is unsupported.
Error: An error occurred
error
Unable to allocate object-name for routing instance instance
The routing protocol process (rpd) could not allocate either labels or subunits (as indicated) for the indicated routing instance, because the result number of objects would have exceeded the limit.
Error: An error occurred
error
function-name: excessive runtime time during action of module
The indicated submodule of the routing protocol process (rpd) ran uninterrupted for the indicated period of time, which is considered excessive.
Event: This message reports an event, not an error
warning
The duration was noted because task accounting is enabled. The function might be implemented inefficiently.
function-name: excessive runtime (total of time in count callbacks) after action of module
Several submodules of the routing protocol process (rpd) ran uninterrupted for the indicated period of time, which is considered excessive.
Event: This message reports an event, not an error
warning
The duration was noted because task accounting is enabled. The function might be implemented inefficiently.
function-name: excessive runtime time during action of module
Several submodules of the routing protocol process (rpd) ran uninterrupted for the indicated period of time, which is considered excessive.
Event: This message reports an event, not an error
warning
The duration was noted because task accounting is enabled. The function might be implemented inefficiently.
function-name ran for total-time (user-time user, system-time system) doing action
A task callback within the routing protocol process (rpd) ran uninterrupted for the indicated period of time, which is considered excessive.
Event: This message reports an event, not an error
warning
The duration was noted because task accounting is enabled. The function might be implemented inefficiently.
signal-name termination signal received
In response to the indicated termination request, the routing protocol process (rpd) terminated adjacencies with neighbors and shut down.
Event: This message reports an event, not an error
notice
function-name: error-message
The indicated error occurred while the routing protocol process (rpd) was connecting to the Simple Network Management Protocol (SNMP) master agent.
Error: An error occurred
info
function-name: unable to connect to SNMP agent (pathname): error-message
The routing protocol process (rpd) could not connect to the indicated Simple Network Management Protocol (SNMP) master agent.
Error: An error occurred
error
function-name: reattempting connection to SNMP agent (pathname): error-message
The routing protocol process (rpd) tried again to connect to the indicated Simple Network Management Protocol (SNMP) master agent after a connection attempt failed.
Error: An error occurred
error
function-name: socket file-descriptor is invalid
The routing protocol process (rpd) could not send a message to a Simple Network Management Protocol (SNMP) master agent because the indicated socket is invalid.
Error: An error occurred
error
function-name: unable to set nonblocking option
The routing protocol process (rpd) could not set a socket to nonblocking mode after connecting to the Simple Network Management Protocol (SNMP) master agent.
Error: An error occurred
error
function-name: unable to set recvbuf option
The routing protocol process (rpd) could not set the size of the kernel receive buffer, which allows it to accept the largest possible packet from the Simple Network Management Protocol (SNMP) master agent.
Error: An error occurred
error
function-name: unable to set sendbf option
The routing protocol process (rpd) could not set the size of the kernel send buffer, which allows it to send the largest possible packet to the Simple Network Management Protocol (SNMP) master agent.
Error: An error occurred
error
Start executable-name[pid] version version built date
The routing protocol process (rpd) started.
Event: This message reports an event, not an error
info
reason: error-message
A system call made by the routing protocol process (rpd) failed.
Error: An error occurred
info
It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.
Commencing routing updates, version rpd-version, built date by builder
The routing protocol process (rpd) started.
Event: This message reports an event, not an error
notice
task-name terminated by SIGsignal-namecore-dump-status
While a child process of the routing protocol process (rpd) was performing the indicated operation, it terminated in response to the indicated signal.
Event: This message reports an event, not an error
error
task-name stopped by SIGsignal-name
While a child process of the routing protocol process (rpd) was performing the indicated operation, it stopped in response to the indicated signal.
Event: This message reports an event, not an error
error
Unable to fork task-name: error-message
The routing protocol process failed to create the indicated child process.
Error: An error occurred
error
getwd: error-message
The getwd() system call made by the routing protocol process (rpd) failed.
Error: An error occurred
error
It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.
Assuming mastership
The routing protocol process (rpd) became active when the Routing Engine on which it was running assumed mastership.
Event: This message reports an event, not an error
info
Reinitialization not possible
The routing protocol process (rpd) failed to reinitialize as requested, because it was running in a state that did not allow reconfiguration.
Error: An error occurred
error
Unable to close and remove filename: error-message
The routing protocol process (rpd) tried to close and remove the file that records its process ID (PID), which serves to prevent multiple instances of rpd from running simultaneously. The attempt failed.
Error: An error occurred
error
flock(filename, LOCK_EX): error-message
The routing protocol process (rpd) issued the flock() system call on the file that records its process ID (PID), which serves to prevent multiple instances of rpd from running simultaneously. The system call failed.
Error: An error occurred
error
Unable to write to fd filename: error-message
The routing protocol process (rpd) tried to write to the file that records its process ID (PID), which serves to prevent multiple instances of rpd from running simultaneously. The attempt failed.
Error: An error occurred
error
Reinitializing
The routing protocol process (rpd) reinitialized.
Event: This message reports an event, not an error
info
sigaction(SIGsignal-name): error-message
The routing protocol process (rpd) informed the kernel that it wished to ignore the indicated signal, but the kernel failed to process the request.
Error: An error occurred
error
Unable to write to trace file filename
The routing protocol process (rpd) could not write to the indicated trace file, and stopped attempting to do so. The next commit of the configuration database will reenable tracing.
Event: This message reports an event, not an error
error
| Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |