 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
This chapter describes messages with the PFE prefix. They are generated by the Packet Forwarding Engine controller, which manages packet forwarding functions.
Internet Processor I does not support CoS-based forwarding
The Internet Processor I application-specific integrated circuit (ASIC) does not support class-of-service (CoS)-based forwarding (CBF).
Event: This message reports an event, not an error
warning
Instance mismatch for type (installed-firewall-name != deleted-firewall-name) ifl logical-interface-index family protocol-family
Before a firewall is deleted, it is sanity checked against what is installed in the forwarding topology. A mismatch was detected between the firewall to be deleted and the forwarding topology, and the delete operation was canceled.
Error: An error occurred
error
DFW: output type (firewall-name) on ifl logical-interface-index rejected, invalid interface
Firewalls that use the ipsec-sa action to forward traffic to an IP Security (IPSec) security association (SA) cannot be configured on the ES Physical Interface Card (PIC) that services the SA. That configuration creates traffic loops within the router and was probably unintended. The problematic filter was automatically removed from the indicated interface.
Error: An error occurred
error
DFW: input type (firewall-name) on ifl logical-interface-index rejected, invalid interface
Firewalls that use the ipsec-sa action to forward traffic to an IP Security (IPSec) security association (SA) cannot be configured on the ES Physical Interface Card (PIC) that services the SA. That configuration creates traffic loops within the router and was probably unintended. The problematic firewall was automatically removed from the indicated interface.
Error: An error occurred
error
DFW: output type (firewall-name) on ifl logical-interface-index rejected, invalid interface
Firewalls that use the ipsec-sa action to forward traffic to an IP Security (IPSec) security association (SA) cannot be configured on the ES Physical Interface Card (PIC) that services the SA. That configuration creates traffic loops within the router and was probably unintended. The problematic firewall was automatically removed from the indicated interface.
Error: An error occurred
error
Instance mismatch for type (installed-firewall-name != deleted-firewall-name) hardware label index family protocol-family
Before a postservice firewall is deleted, it is sanity checked against what is installed in the forwarding topology. A mismatch was detected between the firewall to be deleted and the forwarding topology, and the delete operation was canceled.
Error: An error occurred
error
FW: interface-name action protocol-name source-address destination-address source-port-or-type destination-port-or-code (count packets)
An IP packet matched against a stateless firewall filter with the indicated 'syslog' action (A = Accept, D = Discard, R = Reject).
Event: This message reports an event, not an error
info
FW: interface-name action protocol-name source-address destination-address (count packets)
An IP version 6 (IPv6) packet matched against a stateless firewall filter with the indicated 'syslog' action (A = Accept, D = Discard, R = Reject).
Event: This message reports an event, not an error
info
FW: interface-name action protocol-name source-address destination-address type type code error-code (count packets)
An IP version 6 (IPv6) Internet Control Message Protocol (ICMP) packet matched against a stateless firewall filter with the indicated 'syslog' action (A = Accept, D = Discard, R = Reject).
Event: This message reports an event, not an error
info
FW: interface-name action protocol-name source-address destination-address sport:source-port dport:destination-port (count packets)
An IP version 6 (IPv6) Transmission Control Protocol/User Datagram Protocol (TCP/UDP) packet matched against a stateless firewall filter with the indicated 'syslog' action (A = Accept, D = Discard, R = Reject).
Event: This message reports an event, not an error
info
Failed to add the MGCP Call Agent port to application definition table
Failed to add the MGCP Call Agent port to the application definition table.
Error: An error occurred
error
Failed to add the MGCP UA port to application definition table
Failed to add the MGCP User Agent port to the application definition table.
Error: An error occurred
error
Failed to delete the MGCP Call Agent port from application definition table
Failed to remove the MGCP Call Agent port from the application definition table.
Error: An error occurred
error
Failed to delete the MGCP User Agent port from application definition table
Failed to remove the MGCP User Agent port from the application definition table.
Error: An error occurred
error
Failed to create memory pool for error-message
Failed to initialize the MGCP memory pool.
Error: An error occurred
error
Failed to register object-name handle
Failed to register the handler with the external module.
Error: An error occurred
error
Next-hop resolution requests from interface logical-interface-index throttled
The Packet Forwarding Engine throttled next-hop resolution requests from the indicated interface, because the high number of requests might constitute an attempted denial-of-service (DoS) attack. Examples of events that generate next-hop resolution requests include an attempt to forward a packet without an Address Resolution Protocol (ARP) entry and receiving a multicast data packet with no matching route. Normally, the Packet Forwarding Engine forwards the requests to the Routing Engine.
Event: This message reports an event, not an error
info
Failed to add SCCP ALG port to application definition table
Failed to add the SCCP port to the application definition table.
Error: An error occurred
error
Failed to remove SCCP ALG port from application definition table
Failed to delete the SCCP port from application definition table.
Error: An error occurred
error
Failed to add SCCP ALG vector to flow module
Failed to register the SCCP vector with the flow module.
Error: An error occurred
error
Failed to register SCCP client to Resource Manager
Failed to register the SCCP Resource Manager client.
Error: An error occurred
error
Failed to register SCCP client to VoIP State IP port
Failed to register the SCCP client to VoIP State IP port.
Error: An error occurred
error
Failed to get SCCP Resource Manager client identifier
Failed to get the SCCP Resource Manager client identifier.
Error: An error occurred
error
fail to operation the screen config due to error-message
faile to change the configuration of screen module
Error: An error occurred
error
[operation]: screen name - context-name
configuration of screen module is changed
Event: This message reports an event, not an error
info
failed to operation the screen config due to error-message
failed to change the configuration of screen module
Error: An error occurred
error
[operation]: screen name - context-name
configuration of screen module is changed
Event: This message reports an event, not an error
info
Failed to add SIP ALG port to application definition table
Failed to add the SIP port to the application definition table.
Error: An error occurred
error
Failed to delete SIP ALG port from application definition table
Failed to remove the SIP port from the application definition table.
Error: An error occurred
error
Failed to create memory pool for object-name
Failed to create a memory pool for SIP.
Error: An error occurred
error
Failed to register object-name handle
Failed to register the handler with the external module.
Error: An error occurred
error
USP Trace buffer created for identifier.
The USP Packet Forwarding Engine (PFE) created a trace buffer for the indicated identifier.
Event: This message reports an event, not an error
info
Deleting USP trace buffer for identifier.
The USP Packet Forwarding Engine (PFE) deleted a trace buffer for the indicated identifier.
Event: This message reports an event, not an error
info
Number of buffered records limited to requested-size for identifier.
The USP Packet Forwarding Engine (PFE) trace buffers were limited to the indicated size for the indicated identifier.
Event: This message reports an event, not an error
info
Cannot allocate buffer to hold requested-size records for identifier.
The USP Packet Forwarding Engine (PFE) did not allocate buffers of the indicated size for the indicated identifier.
Error: An error occurred
error
USP Trace buffer modified for identifier.
The USP Packet Forwarding Engine (PFE) modified trace buffers for the indicated identifier.
Event: This message reports an event, not an error
info
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |