Page 2 Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Page 3 REGARDING LICENSE TERMS. 1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or Juniper Networks (Cayman) Limited (if the Customer’s principal office is located outside the Americas) (such applicable entity being referred to herein as “Juniper”), and (ii) the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable...
Page 4 Customer shall be liable for any such violations. The version of the Software supplied to Customer may contain encryption or other capabilities restricting Customer’s ability to export the Software without an export license. Copyright © 2010, Juniper Networks, Inc.
Page 5 (including Juniper modifications, as appropriate) available upon request for a period of up to three years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA http://www.gnu.org/licenses/gpl.html...
Page 57 Juniper Networks website at http://www.juniper.net/techpubs/ Juniper Networks supports a technical book program to publish books by Juniper Networks engineers and subject matter experts with book publishers around the world. These books go beyond the technical documentation to explore the nuances of network architecture, deployment, and administration using the Junos operating system (Junos OS) and Juniper Networks devices.
Page 58 This guide is designed for network administrators who are configuring and monitoring a Juniper Networks M Series, MX Series, T Series, EX Series, or J Series router or switch. To use this reference, you need a broad understanding of networks in general, the Internet in particular, networking principles, and network configuration.
Page 59 0 { family inet { address 10.0.0.1/24; Merge the contents of the file into your routing platform configuration by issuing the load merge configuration mode command: [edit] user@host# load merge /var/tmp/ex-script.conf load complete Copyright © 2010, Juniper Networks, Inc.
Page 60 Indicates a situation that might result in loss of data or hardware damage. Warning Alerts you to the risk of personal injury or death. Laser warning Alerts you to the risk of personal injury from a laser. Copyright © 2010, Juniper Networks, Inc.
Page 61 Indention and braces ( { } ) Identify a level in the configuration [edit] hierarchy. routing-options { static { route default { ; (semicolon) Identifies a leaf statement at a nexthop address; configuration hierarchy level. retain; Copyright © 2010, Juniper Networks, Inc.
Page 62 7 days a week, 365 days a year. Self-Help Online Tools and Resources For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features: lxii Copyright ©...
Page 63 Download the latest versions of software and review release notes: http://www.juniper.net/customers/csc/software/ Search technical bulletins for relevant hardware and software notifications: https://www.juniper.net/alerts/ Join and participate in the Juniper Networks Community Forum: http://www.juniper.net/company/communities/ Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/...
Page 67: Chapter 1 Configuring System Log Messages
Configuring System Logging for a Single-Chassis System on page 7 Configuring System Logging for a Routing Matrix on page 26 Displaying and Interpreting System Log Messages on page 35 Getting Help About System Log Messages on page 46 Copyright © 2010, Juniper Networks, Inc.
Page 68 For information about the minimum and default system log settings on routing platforms that run the Junos OS, see the following sections: Minimum System Logging Configuration on page 5 Default System Log Settings on page 5 Copyright © 2010, Juniper Networks, Inc.
Page 69 Format of messages Standard Junos [edit system syslog] “Logging logged to a file format, based on file filename { Messages in UNIX format structured-data; Structured-Data Format” on page 11 Copyright © 2010, Juniper Networks, Inc.
Page 70 The master Routing Engine on each T640 routing node in a routing matrix forwards to the master Routing Engine on the TX Matrix platform all messages with a severity of info and higher. This is equivalent to the following configuration statement included on the TX Matrix platform: Copyright © 2010, Juniper Networks, Inc.
Page 71 Junos OS. System logging configuration for the Junos-FIPS software and for Juniper Networks routing platforms in a Common Criteria environment is the same as for the Junos OS. For more information, see the Secure Configuration Guide for Common Criteria and Junos-FIPS.
Page 72 When you configure logging for a facility and destination, you specify a severity level for each facility. Messages from the facility that are rated at that level or higher are logged to the following destination: Copyright © 2010, Juniper Networks, Inc.
Page 73 XML protocol or NETCONF client kernel Actions performed or errors encountered by the Junos kernel Actions performed or errors encountered by the Packet Forwarding Engine user Actions performed or errors encountered by user-space processes Copyright © 2010, Juniper Networks, Inc.
Page 74 [ edit system syslog ] hierarchy level: [edit system syslog] file filename { facility severity ; explicit-priority; match "regular-expression"; structured-data { brief; archive { files number ; size size; (world-readable | no-world-readable); Copyright © 2010, Juniper Networks, Inc.
Page 75 NOTE: If you include either or both of the statements explicit-priority time-format along with the structured-data statement, they are ignored. These statements apply to the standard Junos system log format, not to structured-data format. Copyright © 2010, Juniper Networks, Inc.
Page 76 The remote machine must be running the standard syslogd utility. We do not recommend directing messages to another Juniper Networks routing platform. In each system log message directed to the remote machine, the hostname of the local Routing Engine appears after the timestamp to indicate that it is the source for the message.
Page 77 Severity of Messages to Include in the Log” on page 8. In the recommended configuration, a remote machine designated at the [ edit system syslog host hostname hierarchy level is not a Juniper Networks routing platform, so its syslogd utility cannot interpret the Junos-specific names.
Page 78 (the Juniper Networks routing platform or the remote machine itself). For example, the following statements in the...
Page 79 Examples: Assigning an Alternative Facility Log all messages generated on the local routing platform at the error level or higher to facility on the remote machine called local0 monitor.mycompany.com [edit system syslog] host monitor.mycompany.com { any error; Copyright © 2010, Juniper Networks, Inc.
Page 80 Adding a String Add the string M120 to all messages to indicate that the router is an M120 router, and direct the messages to the remote machine hardware-logger.mycompany.com: [edit system syslog] host hardware-logger.mycompany.com { any info; Copyright © 2010, Juniper Networks, Inc.
Page 81 [edit system syslog file filename] facility severity; archive { files number; size size; (world-readable | no-world-readable); number specifies the number of files to create before the oldest file is overwritten. files The value can be from through 1000 Copyright © 2010, Juniper Networks, Inc.
Page 82 (The tag is a unique identifier assigned to some Junos system log messages; for more information, see “Interpreting Messages Generated in Structured-Data Format” on page 36, “Interpreting Messages Generated in Standard Format by Services on a PIC” on page 41, Copyright © 2010, Juniper Networks, Inc.
Page 83 Actions performed or errors encountered by the dynamic flow capture process Packet filtering actions FIREWALL firewall performed by a firewall filter Actions performed or errors encountered by the FTP process Copyright © 2010, Juniper Networks, Inc.
Page 84 Critical conditions, such as critical hard drive errors Error conditions that generally error have less serious consequences than errors in the emergency, alert, and critical levels Copyright © 2010, Juniper Networks, Inc.
Page 85 The modified timestamp is used in messages directed to each destination configured by , or statement at the [ ] hierarchy level, but not to file console user edit system syslog destinations configured by a statement. host Copyright © 2010, Juniper Networks, Inc.
Page 86 In the descriptions, the term term refers to either a single alphanumeric character or a set of characters enclosed in square brackets, parentheses, or braces. NOTE: The statement is not case-sensitive. match Copyright © 2010, Juniper Networks, Inc.
Page 87 . Omit messages generated by the SNMP /var/log/process-errors process (snmpd), instead directing them to the file /var/log/snmpd-errors [edit system syslog] file process-errors { daemon error; Copyright © 2010, Juniper Networks, Inc.
Page 88 [edit system] syslog { file cli-commands { interactive-commands info; authorization info; user * { interactive-commands info; authorization info; Log all changes in the state of alarms to the file /var/log/alarms Copyright © 2010, Juniper Networks, Inc.
Page 89 . The example writes the messages to the terminal of user commit philip —Logs a message when users issue a command that restarts a software warning process. The example writes the messages to the console. Copyright © 2010, Juniper Networks, Inc.
Page 90 "regular-expression"; structured-data { brief; archive { files number; size size; (world-readable | no-world-readable); host (hostname | other-routing-engine | scc-master) { facility severity; explicit-priority; facility-override facility; log-prefix string; match "regular-expression"; source-address source-address; Copyright © 2010, Juniper Networks, Inc.
Page 91 Configuring Message Forwarding in the Routing Matrix on page 28 Configuring Optional Features for Forwarded Messages on page 31 Directing Messages to a Remote Destination from the Routing Matrix on page 32 Configuring System Logging Differently on Each Platform on page 33 Copyright © 2010, Juniper Networks, Inc.
Page 92 Messages Logged When Local and Forwarded Severity Level Are the Same on page 29 Messages Logged When Local Severity Level Is Lower on page 29 Messages Logged When Local Severity Level Is Higher on page 30 Copyright © 2010, Juniper Networks, Inc.
Page 93 For example, you can specify severity notice for the /var/log/messages file and severity for forwarded messages critical [edit system syslog] file messages { any notice; host scc-master { any critical; Copyright © 2010, Juniper Networks, Inc.
Page 94 Forwarded from T640 routing critical nodes We do not recommend this type of configuration, because it wastes bandwidth for the routing nodes to forward messages that are not recorded in the log on the TX Matrix platform. Copyright © 2010, Juniper Networks, Inc.
Page 95 /var/log/messages information for messages with severity and higher from all facilities. The log on notice the TX Matrix platform also includes messages with those characteristics forwarded from the T640 routing nodes. Copyright © 2010, Juniper Networks, Inc.
Page 96 [ edit system syslog host scc-master ] hierarchy level. statement does not interact with message forwarding from the other-routing-engine T640 routing nodes to the TX Matrix platform. For example, if you include the statement Copyright © 2010, Juniper Networks, Inc.
Page 97 In rare circumstances, however, you might choose to log different messages on different platforms. For example, if one platform in the routing matrix is experiencing problems with authentication, a Juniper Networks support representative might instruct you to log messages from the authorization facility on that platform.
Page 98 ... same statements as for re0 ... lcc0-re0 { system { syslog { file messages { authorization info; lcc0-re1 { ... same statements as for lcc0-re0 ... lcc1-re0 { system { syslog { file messages { any notice; lcc0-re1 { Copyright © 2010, Juniper Networks, Inc.
Page 100 In particular, the standardized format for reporting the value of variables (elements in the English-language message that vary depending on the circumstances that triggered the message) makes it easy for an application to extract Copyright © 2010, Juniper Networks, Inc.
Page 101 Name of the Junos process that process generated the message. processID UNIX process ID (PID) of the Junos 3046 process that generated the message. Junos system log message tag, which UI_DBASE_LOGOUT_EVENT uniquely identifies the message. Copyright © 2010, Juniper Networks, Inc.
Page 102 “Specifying the Facility and Severity of Messages to Include in the Log” on page 8. Table 16: Facility and Severity Codes in the priority-code Field Severity Facility (number) emergency alert critical error warning notice info debug kernel (0) user (1) Copyright © 2010, Juniper Networks, Inc.
Page 103 (20) conflict-log (21) change-log (22) interactive-commands (23) Table 17 on page 40 lists the numerical identifiers for routing platforms that appear in platform field. The identifier is derived from the platform’s SNMP object identifier Copyright © 2010, Juniper Networks, Inc.
Page 104 Junos 10.3 System Log Messages Reference (OID) as defined in the Juniper Networks routing platform MIB. For more information about OIDs, see the Junos Network Management Configuration Guide. Table 17: Platform Identifiers in the platform Field Identifier Platform Name M40 router 1.1.1.2.1...
Page 105 System Log Messages. Interpreting Messages Generated in Standard Format by Services on a PIC Standard-format system log messages generated by services on a PIC, such as the Adaptive Services (AS) PIC, have the following syntax: Copyright © 2010, Juniper Networks, Inc.
Page 106 Format by a JUNOS Process or Library” on page 41 has two or more subfields, depending on whether the message is logged on a single-chassis system or on a platform in a routing matrix, and whether message forwarding is configured in the routing matrix. Copyright © 2010, Juniper Networks, Inc.
Page 107 Whether the message was generated by a kernel or user-space process, or by the microkernel on a hardware component. Table 20 on page 44 specifies the format of the message-source field in the various cases. Copyright © 2010, Juniper Networks, Inc.
Page 108 Matrix platform that generated the message (the range of values for depends on the component type). For example, refers to a process on one of the processor spmb1 GSIB boards in the Switch Interface Board (SIB) with index 1. Copyright © 2010, Juniper Networks, Inc.
Page 109 Examples: Displaying a Log File Display the contents of the /var/log/messages file stored on the local Routing Engine. (The directory is the default location for log files, so you do not need to include /var/log Copyright © 2010, Juniper Networks, Inc.
Page 110 For a list of the prefixes for messages described in this reference, see System Log Messages. For information about displaying and interpreting messages, see the following sections: Displaying and Interpreting System Log Message Descriptions on page 47 Examples: Displaying System Log Message Descriptions on page 48 Copyright © 2010, Juniper Networks, Inc.
Page 111 — Help Short description of the message, which also appears in the right-hand column of CLI output for the help syslog command when the output lists multiple messages. Copyright © 2010, Juniper Networks, Inc.
Page 112 Request failed because assembly ID was unknown BOOTPD_BOOTSTRING tnp.bootpd provided boot string BOOTPD_CONFIG_ERR tnp.bootpd could not parse configuration file; used default settings BOOTPD_CONF_OPEN tnp.bootpd could not open configuration file BOOTPD_DUP_REV Extra boot string definitions for revision were ignored ---(more 4%)--- Copyright © 2010, Juniper Networks, Inc.
Page 113 Description: The indicated user typed the indicated command at the CLI prompt and pressed the Enter key, sending the command string to the management process (mgd). Type: Event: This message reports an event, not an error Severity: info Copyright © 2010, Juniper Networks, Inc.
Page 115 ESWD System Log Messages on page 249 EVENTD System Log Messages on page 257 FCD System Log Messages on page 265 FLOW System Log Messages on page 267 FPCLOGIN System Log Messages on page 269 Copyright © 2010, Juniper Networks, Inc.
Page 116 NSTRACED System Log Messages on page 457 PFE System Log Messages on page 459 PFED System Log Messages on page 469 PGCPD System Log Messages on page 471 PING System Log Messages on page 473 Copyright © 2010, Juniper Networks, Inc.
Page 117 VCCPD System Log Messages on page 659 VRRPD System Log Messages on page 663 VSYSD System Log Messages on page 667 WEB System Log Messages on page 669 WEBFILTER System Log Messages on page 675 Copyright © 2010, Juniper Networks, Inc.
Page 119: Chapter 2 Acct System Log Messages
The size limit configured for the indicated file is smaller than the record to be written to Type Error: An error occurred Severity warning Facility LOG_PFE ACCT_BAD_RECORD_FORMAT System Log Message Invalid statistics record: entry Copyright © 2010, Juniper Networks, Inc.
Page 120 Error: An error occurred Severity error Facility LOG_PFE ACCT_GETHOSTNAME_ERROR System Log Message Error error-code trying to get hostname Description A call to the gethostname() function failed. Type Error: An error occurred Severity error Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 121 Error error-code in invoking command command to transfer file filename Description A call to the popen() function failed when the accounting statistics process invoked the indicated command to transfer the indicated file. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 123: Chapter 3 Alarmd System Log Messages
Contact your technical support representative. ALARMD_CONFIG_PARSE_ERROR System Log Message Unable to parse configuration; using defaults Description The alarm process (alarmd) could not parse the configuration and used default values while initializing. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 124 Description The alarm process (alarmd) exited because it discovered that another alarmd process is already running. Type Event: This message reports an event, not an error Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 125 Description The alarm process (alarmd) detected an error in an interprocess communication (IPC) message with the indicated characteristics. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 126 Contact your technical support representative. ALARMD_MEM_ALLOC_FAILURE System Log Message function-name: alarmd memory allocation failed Description The alarm process (alarmd) could not allocate memory. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 127 ALARMD_PIPE_WRITE_ERROR System Log Message Pipe write error: error-message Description The alarm process (alarmd) experienced a fatal error while writing to a pipe. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 128 Severity error Facility LOG_DAEMON ALARMD_UNEXPECTED_EXIT System Log Message evMainLoop returned return-value (errno error-code) Description The alarm process (alarmd) exited unexpectedly and reported the indicated error. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 129: Chapter 4 Ancpd System Log Messages
System Log Message ancpd_cmd_opts called with option index arg argument Description ancpd process cmd line options not handled by junos_app_init Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 131: Chapter 5 Antispam System Log Messages
Event: This message reports an event, not an error Severity info Facility LOG_PFE Cause The email is detected as a spam Action Verify the spam to make sure it is not a false positive Copyright © 2010, Juniper Networks, Inc.
Page 133: Chapter 6 Appidd System Log Messages
Failed to update application packge. error: error-message Description The scheduled application-identification application package update failed to start. Device will try it again at the next scheduled time Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 135: Chapter 7 Apptrack System Log Messages
Description A security session being tracked by the Application tracking service was closed. Type Event: This message reports an event, not an error Severity info Facility Copyright © 2010, Juniper Networks, Inc.
Page 136 Description Periodic updates are sent for a session monitored by the Application tracking service. The periodicity is decided by configuration. Type Event: This message reports an event, not an error Severity info Facility Copyright © 2010, Juniper Networks, Inc.
Page 137: Chapter 8 Apppxy System Log Messages
ApplicationProxy: session from source-address:source-port to destination-address:destination-port aborted due to error-message (code error-code) Description Report application protocol (ftp/http/pop3/smtp/imap) session is aborted Type Event: This message reports an event, not an error Severity warning Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 139: Chapter 9 Asp System Log Messages
'threshold' statement at the [edit services rule <rule-name> term <term-name> then logging] hierarchy level. This message is logged every 60 seconds until the rate no longer exceeds the threshold. Type Event: This message reports an event, not an error Severity error Copyright © 2010, Juniper Networks, Inc.
Page 140 The request's version number did not match the version number of requests that IDS can service. Type Error: An error occurred Severity critical Facility LOG_PFE Action Contact your technical support representative. ASP_IDS_INV_SHOW_QUERY System Log Message SHOW: Invalid query type received-value expecting expected-value Copyright © 2010, Juniper Networks, Inc.
Page 141 (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type Description The stateful firewall discarded the packet with the indicated characteristics and did not create a new flow, because the flow rate at the firewall exceeded the intrusion detection Copyright © 2010, Juniper Networks, Inc.
Page 142 (numerical identifier and name), source (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Severity notice Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 143 <rule-name> term <term-name> then session-limit by-destination] hierarchy level. The discarded packet contained the indicated information about its protocol (numerical identifier and name), source (logical interface name, IP address, and port number), and destination (IP address and port number). Copyright © 2010, Juniper Networks, Inc.
Page 144 Not enough memory for show command Description Intrusion detection services (IDS) could not service a request to show information from IDS tables, because not enough memory was available. Type Error: An error occurred Severity critical Copyright © 2010, Juniper Networks, Inc.
Page 145 (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Severity info Facility LOG_PFE ASP_IDS_SYN_COOKIE_OFF System Log Message Host destination-address, SYN-COOKIE protection deactivated Copyright © 2010, Juniper Networks, Inc.
Page 146 (numerical identifier and name), source (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Severity error Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 147 (IPC) request for statistics because it included the indicated the number of queries, which exceeds the limit as indicated. Type Error: An error occurred Severity error Facility LOG_PFE ASP_L2TP_STATS_VERSION_INVALID System Log Message Invalid version received-value on statistics request (expected expected-value) Copyright © 2010, Juniper Networks, Inc.
Page 148 Unable to change tunnel group group-id: ID is invalid Description The Layer 2 Tunneling Protocol (L2TP) could not change the tunnel group with the indicated internal ID, because the ID is invalid. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 149 Type Event: This message reports an event, not an error Severity info Facility LOG_PFE ASP_NAT_RULE_MATCH System Log Message syslog-prefix error-code: proto protocol-id (protocol-name) application: application, source-interface-nameseparatorsource-address:source-port -> Copyright © 2010, Juniper Networks, Inc.
Page 150 The configuration is invalid, because only those ALGs are supported in combination with twice NAT. The ALG configured in the stateful firewall or CoS rule was ignored, and only the application configured in the twice-NAT rule was applied. The Copyright © 2010, Juniper Networks, Inc.
Page 151 The packet contained the indicated information about its protocol (numerical identifier and name), source (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Severity notice Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 152 (numerical identifier and name), application, source (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Severity notice Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 153 The matching packet contained the indicated information about its protocol (numerical identifier and name), application, source (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 154 576. The discarded packet contained the indicated information about its protocol (numerical identifier and name), source (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 155 (numerical identifier and name), source (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Severity notice Copyright © 2010, Juniper Networks, Inc.
Page 156 (numerical identifier and name), source (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Severity notice Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 157 (numerical identifier and name), source (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Severity notice Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 158 (numerical identifier and name), source (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Severity notice Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 159 A new stateful firewall policy was installed. Type Event: This message reports an event, not an error Severity critical Facility LOG_PFE ASP_SFW_NO_IP_PACKET System Log Message syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type Copyright © 2010, Juniper Networks, Inc.
Page 160 (numerical identifier and name), source (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 161 System Log Message reject configuration because reason Description A newly installed stateful firewall policy was rejected for the indicated reason. Type Event: This message reports an event, not an error Severity critical Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 162 Internet Control Message Protocol (ICMP) error message. If the packet used the Transmission Control Protocol (TCP), the stateful firewall generated an RST packet. The matching packet contained the indicated information about its Copyright © 2010, Juniper Networks, Inc.
Page 163 (numerical identifier and name), source (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 164 The discarded packet contained the indicated information about its protocol (numerical identifier and name), source (logical interface name, IP address, and port number), and destination (IP address and port number). Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 165 The event was reported to intrusion detection services (IDS) and can cause IDS to activate SYN cookie protection. The RST packet contained the indicated information about its protocol (numerical identifier and name), source Copyright © 2010, Juniper Networks, Inc.
Page 166 The stateful firewall discarded the User Datagram Protocol (UDP) packet with the indicated characteristics, because the length field in the packet header was shorter than the minimum 8 bytes required for an UDP packet. The discarded packet contained the Copyright © 2010, Juniper Networks, Inc.
Page 167 System Log Message syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type Description The stateful firewall discarded the packet with the indicated characteristics, because the packet was malformed. The discarded packet contained the indicated information Copyright © 2010, Juniper Networks, Inc.
Page 168 60 seconds that the system noted the excessive number of flows. Type Event: This message reports an event, not an error Severity notice Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 169: Chapter 10 Auditd System Log Messages
LOG_DAEMON AUDITD_RADIUS_REQ_CREATE_FAILED System Log Message Unable to create RADIUS request: error-message Description The audit process (auditd) could not create a RADIUS accounting request for the indicated reason. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 170 The RADIUS server is not responding. Possible reasons include (a) the server machine is down, too busy, or unreachable (b) the server application is down or too busy (c) the shared RADIUS secret sent by auditd does not match the secret on the server. Copyright © 2010, Juniper Networks, Inc.
Page 171 The indicated socket operation failed with the indicated error. Type Error: An error occurred Severity emergency Facility LOG_DAEMON Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 173: Chapter 11 Authd System Log Messages
Unable to bind to socket file-descriptor: error-message (errno error-code) Description The generic authentication service process (authd) could not bind the server to the address specified. Type Error: An error occurred Severity error Facility LOG_AUTH Copyright © 2010, Juniper Networks, Inc.
Page 174 Unable to listen on socket file-descriptor: error-message (errno error-code) Description The generic authentication service process (authd) could not initialize listening on the server for the indicated socket. Type Error: An error occurred Severity error Facility LOG_AUTH Copyright © 2010, Juniper Networks, Inc.
Page 175: Chapter 12 Autoconfd System Log Messages
The indicated number of license failures occurred and the clients were denied access and configuration. Type Error: An error occurred Severity alert Facility LOG_DAEMON Action Add or update the license for authentication Copyright © 2010, Juniper Networks, Inc.
Page 177: Chapter 13 Autod System Log Messages
Contact your technical support representative. AUTOD_RECV_FAILURE System Log Message Unable to receive on socket: error-message Description The autoinstallation process (autod) received the indicated error when it tried to receive data on a socket. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 178 Unable to create socket: error-message Description The autoinstallation process (autod) received the indicated error when it tried to create a socket. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 179: Chapter 14 Av System Log Messages
Description The antivirus scanner dropped the received traffic because the maximum number of concurrent messages to scan is exceeded Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 180 The device was unable to access or retrieve an antivirus pattern file from a server, identified by IP address and port number, through HTTP. The error code provides information you need to get help from Juniper Networks technical support Type...
Page 181 AntiVirus: db file signature mismatch: error-message. Description The device is unable to use Kaspersky's pattern file. The error message provides information you need to give Juniper Networks technical support Type Event: This message reports an event, not an error Severity...
Page 182 The antivirus scan engine is ready to scan the traffic Type Event: This message reports an event, not an error Severity notice Facility LOG_FIREWALL Cause The antivirus scan engine is ready Action No recommended action Copyright © 2010, Juniper Networks, Inc.
Page 183 The antivirus scanner has detected a virus; the log will show source and destination port and IP, source zone, contaminated file, virus name and URL link with virus description Type Event: This message reports an event, not an error Severity warning Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 185: Chapter 15 Bfdd System Log Messages
(bfdd) determined that the versions of Junos OS on the Routing Engines were incompatible. Type Error: An error occurred Severity warning Facility LOG_DAEMON Action Update the Junos OS to compatible versions on the master and backup Routing Engines. Copyright © 2010, Juniper Networks, Inc.
Page 186 (error-message) Description The Bidirectional Forwarding Detection process (bfdd) could not write a message to the indicated type of pipe. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 187: Chapter 16 Bootpd System Log Messages
System Log Message Boot string: boot-string Description As each hardware component on the routing platform initializes, it requests a boot string from the boot parameter process (tnp.bootpd). tnp.bootpd responded with the indicated boot string. Copyright © 2010, Juniper Networks, Inc.
Page 188 Physical Interface Card (PIC) slot in the indicated Flexible PIC Concentrator (FPC), so tnp.bootpd used the first definition it found. Type Event: This message reports an event, not an error Severity notice Facility Action Remove the extra definitions from the configuration file. Copyright © 2010, Juniper Networks, Inc.
Page 189 The boot parameter process (tnp.bootpd) could not complete an operation in the hardware database maintained by the chassis process (chassisd), for the indicated reason. Type Error: An error occurred Severity error Facility BOOTPD_MODEL_CHK System Log Message Unexpected ID 0xidentifier for model model Copyright © 2010, Juniper Networks, Inc.
Page 190 (tnp.bootpd). The boot strings are defined in the configuration file for tnp.bootpd. The file did not include a boot string for the hardware component with the indicated characteristics. Type Error: An error occurred Severity warning Facility Copyright © 2010, Juniper Networks, Inc.
Page 191 System Log Message select: error-message Description The boot parameter process (tnp.bootpd) issued the select() system call, which returned the indicated error message. Type Error: An error occurred Severity warning Facility Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 192 (tnp.bootpd) initialized using the default value of 30 seconds. Type Error: An error occurred Severity warning Facility Action Provide an acceptable value for the -t argument; acceptable values are '1' (second) and larger. Copyright © 2010, Juniper Networks, Inc.
Page 193: Chapter 17 Cfmd System Log Messages
(CCM) with an incorrect transmission interval or MEP ID, which indicates a configuration error. Type Event: This message reports an event, not an error Severity error Facility Cause The configuration is invalid. Copyright © 2010, Juniper Networks, Inc.
Page 194 (CCM)s from one of the other MEPs in its maintenance association (MA), which indicates a MEP failure or network failure. Type Event: This message reports an event, not an error Severity error Facility Copyright © 2010, Juniper Networks, Inc.
Page 195 An internal software failure occurred. CFMD_PARSE_CMD_EXTRA System Log Message executable-name: extraneous information on command line: option Description The enterprise switching process (cfmd) terminated because of an internal error. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 196 The connectivity fault management process (cfmd) could not write a message on the pipe to the periodic packet management process (ppmd). Type Error: An error occurred Severity error Facility Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 197: Chapter 18 Chassisd System Log Messages
The chassis process (chassisd) could not read the serial number recorded in the ROM of the anti-counterfeit device for the Routing Engine. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 198 System Log Message Unknown option option Description The indicated option, provided on the 'chassisd' command line, is invalid. The chassis process (chassisd) initialized but ignored the invalid option. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 199 Unable to open 'bus-type' bus device, error error-message (error-code) Description The chassis process (chassisd) could not open the indicated bus device for the indicated reason. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 200 (chassisd) ignored the request. The control board for M40e and M160 routers is the Miscellaneous Control Subsystem (MCS). The control board for M320, T320, and T640 routing platforms is the Control Board (CB). Copyright © 2010, Juniper Networks, Inc.
Page 201 Contact your technical support representative. CHASSISD_CLOCK_FAILURE System Log Message function-name: fru-name error-message Description The chassis process (chassisd) determined that the indicated clock source failed in the indicated way. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 202 FRU) confirm that it was online. The indicated error occurred when the FRU sent its response. In the normal case, the chassis process performed any additional action necessary to guarantee that the FRU came online. Copyright © 2010, Juniper Networks, Inc.
Page 203 The chassis process (chassisd) experienced the indicated problem while attempting to parse the configuration database. Type Error: An error occurred Severity error Facility LOG_DAEMON Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 204 The chassis process (chassisd) could not open the device file for the indicated device. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. CHASSISD_EXEC_ERROR System Log Message function-name: error-message Copyright © 2010, Juniper Networks, Inc.
Page 205 The indicated fan or impeller failed. The chassis process (chassisd) raised an alarm and increased the speed of the remaining fans (and impellers, if applicable) to full speed. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 206 Fchip (CB control-board-slot, ID fchip-id): HSL configuration failed (error error-message) Description The chassis process (chassisd) could not configure high speed links (HSL) for the indicated F chip on the indicated Control Board (CB). Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 207 The Packet Forwarding Engine divides packets into smaller units called cells for more efficient processing. As the indicated F chip on the indicated Control Board (CB) processed data before sending it to the indicated Packet Forwarding Engine on the indicated Flexible Copyright © 2010, Juniper Networks, Inc.
Page 208 The chassis process (chassisd) could not lock a phased-lock loop (PLL) for the indicated F chip on the indicated Control Board (CB). Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 209 System Log Message Fchip: configuration already completed Description The chassis process (chassisd) detected an attempt to configure an F chip when configuration was already complete. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 210 Fchip fchip-id: Ftoken overflow/underflow set (data) at address Description The chassis process (chassisd) detected an underflow or overflow error on the indicated F chip. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 211 The chassis process (chassisd) could not initialize the indicated high-speed receiver (HSR) link for the indicated F chip. Type Error: An error occurred Severity error Facility LOG_DAEMON CHASSISD_FCHIP_HSR_RESET_ERROR System Log Message Fchip fchip-id: hsr_reset error in fchip_init() on link link-id Copyright © 2010, Juniper Networks, Inc.
Page 212 System Log Message Fchip fchip-id: hst_reset error in fchip_init() on link link-id Description A high-speed transmitter (HST) reset error occurred during initialization of the indicated F chip and link. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 213 Fchip fchip-id: read error in function-name() for link#link-id, at address address in register register Description The indicated routine failed with a read error at the indicated address and register for the indicated F chip and link. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 214 Unable to start fru-name fru-slot because F chips were not initialized Description The indicated Switch Interface Board (SIB) did not start because the F chips on it were not initialized. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 215 Fchip: fhsr_read() failed at address address Description The high-speed receiver (HSR) read routine failed at the indicated address on an F-chip register. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 216 The chassis process (chassisd) could not open the indicated file for the indicated reason. Type Error: An error occurred Severity critical Facility LOG_DAEMON CHASSISD_FILE_STAT System Log Message File stat: filename, error: error-code -- error-message Copyright © 2010, Juniper Networks, Inc.
Page 217 The chassis process (chassisd) on the SFC routing node detected an error in the electrical path between the indicated port on the indicated F2SIB and F13SIB on the indicated plane. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 218 In a Tx-Plus routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the T1600 routing nodes (called ST-SIB-Ls) and the SIBs in the TX Matrix Plus platform (called F13SIBs and F2S-SIBs). Copyright © 2010, Juniper Networks, Inc.
Page 220 The chassis process (chassisd) on the SFC routing node that houses the indicated F13SIB detected higher than configured receive power difference levels on the indicated fiber-bundles connected to the indicated LCC ST-SIB-L. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 221 (chassisd) on the routing node that houses the indicated SIB-L detected the indicated error as packets that were traveling in the indicated direction were translated between electrical and optical media. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 222 The chassis process (chassisd) on the routing node that houses the indicated ST-SIB-L detected an error in the electrical path between the indicated ST-SIB-L and the indicated PFE on the FPC. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 223 ST-SIB-Ls) and the SIBs in the TX Matrix Plus platform (called F13SIBs and F2S-SIBs). The chassis process (chassisd) on the routing node that houses the indicated ST-SIB-L detected higher than configured receive power levels on the indicated fiber-bundles connected to the indicated LCC ST-SIB-L. Copyright © 2010, Juniper Networks, Inc.
Page 224 Action Contact your technical support representative. CHASSISD_FM_MEMORY_ERROR System Log Message function-name: unable to allocate memory; error-message Description The chassis process (chassisd) could not allocate memory for a fabric operation. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 225 Flexible PIC Concentrator (FPC) that houses it. Type Error: An error occurred Severity warning Facility LOG_DAEMON Action Contact your technical support representative. CHASSISD_FPC_PIC_DETECT_TIMEOUT System Log Message function-name: PIC detection on FPC fpc-slot timed out Copyright © 2010, Juniper Networks, Inc.
Page 226 The chassis process (chassisd) received a request to bring the indicated component (field-replaceable unit, or FRU) online, but the FRU was already online. Type Event: This message reports an event, not an error Severity warning Facility LOG_DAEMON CHASSISD_FRU_EVENT System Log Message function-name: state fru-name fru-slot Copyright © 2010, Juniper Networks, Inc.
Page 227 0xoffset (error-message) Description The chassis process (chassisd) could not perform the indicated I/O operation at the indicated byte offset. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 228 (chassisd) tried several times to take the FRU offline and powered it down if all attempts failed. Type Event: This message reports an event, not an error Severity warning Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 229 (field-replaceable unit, or FRU) online, but the attempts failed. In another attempt to bring the FRU online, the chassisd process issued the restart command for the FRU. Type Event: This message reports an event, not an error Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 230 (RTIME_PWR_COND = 0xvalue) Description The GBUS was not ready when the chassis process (chassisd) first tried to power it on, and the power-up operation timed out. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 231 The chassis process (chassisd) checks its management GBUS with a set of test operations when it is started. The tests failed. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. CHASSISD_GENERIC_ERROR System Log Message function-name: error-message Copyright © 2010, Juniper Networks, Inc.
Page 232 The fans (and impellers, if applicable) were in the indicated state. The chassis process (chassisd) increased the speed of all functioning fans and impellers to full speed. Copyright © 2010, Juniper Networks, Inc.
Page 233 Provided number of HSR elements (count) was invalid Description The indicated routine for processing a certain number of high-speed receiver (HSR) elements failed, because the supplied number of elements was invalid. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 234 Contact your technical support representative. CHASSISD_I2C_FIC_PRESENCE_READ System Log Message function-name: fru-name unable to get presence masks (error-message) Description The chassis process (chassisd) could not read I2C data with presence information about the indicated component (field-replaceable unit, or FRU). Copyright © 2010, Juniper Networks, Inc.
Page 235 I2C data for the indicated component (field-replaceable unit, or FRU). Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. CHASSISD_I2C_IO_FAILURE System Log Message function-name: fru-name operation failed for group group-id at address 0xaddress Copyright © 2010, Juniper Networks, Inc.
Page 236 0xaddress, offset offset Description The chassis process (chassisd) could not read I2C data from the indicated device. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 237 Necessary resources might have been unavailable. Action Contact your technical support representative. CHASSISD_IFDEV_CREATE_NOTICE System Log Message function-name: created device-name for interface-name Description The chassis process (chassisd) created the initial interface device for the indicated newly installed PIC or pseudodevice. Copyright © 2010, Juniper Networks, Inc.
Page 238 System Log Message ifdev_detach(pseudo devices: porttype port-type, sdev=sdev-number, edev=edev-number) Description The chassis process (chassisd) detached the interface devices for the indicated pseudodevices. Type Event: This message reports an event, not an error Severity notice Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 239 System Log Message Unable to retrieve information for interface device interface-name: error-message Description The chassis process (chassisd) could not obtain information about the indicated interface device. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 240 Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. CHASSISD_IOCTL_FAILURE System Log Message function-name: reason for fru-name (error-message) Copyright © 2010, Juniper Networks, Inc.
Page 241 The socket is for a connection to another process that runs on the Routing Engine and helps manage the chassis. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 242 The connection to a component (field-replaceable unit, or FRU) no longer exists, so the chassisd process cannot send all messages immediately as it usually does. Action Contact your technical support representative. CHASSISD_IPC_MSG_ERROR System Log Message function-name: error code error-code, type message-type, subtype message-subtype, opcode message-opcode Copyright © 2010, Juniper Networks, Inc.
Page 243 The chassis process (chassisd) received an interprocess communication (IPC) message about the indicated FRU. The message had the indicated characteristics. The chassisd process could not handle the message. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 244 The chassis process (chassisd) could not send a message to the indicated component (field-replaceable unit, or FRU) because the interprocess communication (IPC) pipe to the FRU no longer existed. Type Error: An error occurred Severity warning Copyright © 2010, Juniper Networks, Inc.
Page 245 CHASSISD_ISSU_ERROR System Log Message action error-code(error-message) Description The chassisd process (chassisd) encountered the indicated error for the indicated in service software upgrade process (issu) action. Type Error: An error occurred Severity notice Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 246 The version of the Junos OS on the master Routing Engine did not match the version on the TX Matrix platform's master Routing Engine. The version on the backup Routing Engine did match the TX Matrix platform. Copyright © 2010, Juniper Networks, Inc.
Page 247 The chassis process (chassisd) could not obtain a media access control (MAC) address for the indicated interface because of an internal error. Type Error: An error occurred Severity error Facility LOG_DAEMON CHASSISD_MAC_ADDRESS_FABRIC_ERR System Log Message Unable to allocate MAC address for fabric interface device-id Copyright © 2010, Juniper Networks, Inc.
Page 248 System Log Message Using default MAC address base Description The chassis process (chassisd) used the default base media access control (MAC) address. Type Event: This message reports an event, not an error Severity info Copyright © 2010, Juniper Networks, Inc.
Page 249 Error: An error occurred Severity critical Facility LOG_DAEMON CHASSISD_MBUS_ERROR System Log Message fru-name fru-slot: management bus failed sanity test Description Startup tests on the indicated FRU's management bus failed. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 250 (errno error-code) Description The chassis process (chassisd) could not to open a pipe for interprocess communication (IPC) to a component (field-replaceable unit, or FRU). Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 251 The chassis process (chassisd) could not find an operational SONET Clock Generator (SCG). To continue functioning correctly, SONET/SDH interfaces that use an SCG as their clock source must find another source. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 252 When this message was logged, the indicated number of seconds remained before shutdown. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Increase cooling in the area around the chassis. Copyright © 2010, Juniper Networks, Inc.
Page 253 System Log Message function-name: peer not connected Description The chassis process (chassisd) processed a packet for a peer with an invalid or missing connection. Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 254 Severity warning Facility LOG_DAEMON Action Check the status of the circuit breaker and the input connections. CHASSISD_PEM_NOT_SUFFICIENT System Log Message Unable to power up FPC fpc-slot, because no three-input 240-A power supply is installed Copyright © 2010, Juniper Networks, Inc.
Page 255 The indicated power entry module (PEM) reported a problem with its output voltage. Type Event: This message reports an event, not an error Severity warning Facility LOG_DAEMON Cause There might have been excessive load on the PEM. Copyright © 2010, Juniper Networks, Inc.
Page 256 System Log Message PIC pic-slot in FPC fpc-slot (PIC type pic-type, version version) had hardware error Description The indicated PIC experienced a hardware error. The chassis process (chassisd) did not bring the PIC online. Copyright © 2010, Juniper Networks, Inc.
Page 257 PIC pic-slot in FPC fpc-slot (type pic-type, version version) will be reset on switchover Description The chassis process (chassisd) noted that the PIC with the indicated characteristics needs to be reset when a graceful switchover occurs. Copyright © 2010, Juniper Networks, Inc.
Page 258 LOG_DAEMON Cause The chassisd process might have detected that another chassisd process was running and tried to read the file so that it could use the PID recorded there when terminating the other process. Copyright © 2010, Juniper Networks, Inc.
Page 259 On a J-series Services Router, the component is a Physical Interface Module (PIM) or other module that installs in a PIM slot. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 260 (status bits: 0xstatus-code); Input failure Description The chassis process (chassisd) detected the input voltage/warning fault condition for the indicated power supply unit (PSU). Type Event: This message reports an event, not an error Severity warning Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 261 System Log Message function-name: '0xvalue' is invalid value for object-name (out of range) Description The indicated value was outside the valid range of values for the indicated object. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 262 System Log Message Routing Engine routing-engine-slot temperature (temperature C) over threshold degrees Description The temperature of the indicated Routing Engine exceeded the indicated temperature, which is the upper of two thresholds. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 263 (threshold C) Description The temperature of the indicated Routing Engine exceeded the indicated temperature, which is the lower of two thresholds. Type Event: This message reports an event, not an error Severity error Copyright © 2010, Juniper Networks, Inc.
Page 264 FRU did not restart after a successful software upgrade. Action Upgrade the software and reboot the routing platform. CHASSISD_SENSOR_RANGE_NOTICE System Log Message fru-name fru-slot temperature is temperature degrees C, which is outside operating range Copyright © 2010, Juniper Networks, Inc.
Page 265 CHASSISD_SFM_NOT_ONLINE System Log Message function-name: SFM sfm-slot not online Description The indicated Switching and Forwarding Module (SFM) was offline. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 266 The system management bus (SMB) could not download field-programmable gate array (FPGA) information and returned the indicated status code. The chassis process (chassisd) took the indicated action. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 267 SNMP trap generated: trap (argument1 value1) Description The chassisd process (chassisd) generated the indicated simple network management protocol (snmp) trap with the indicated value. Type Event: This message reports an event, not an error Severity notice Copyright © 2010, Juniper Networks, Inc.
Page 268 0xaddress, error error-message Description The chassis process (chassisd) could not perform the indicated ioctl() operation on the indicated register of the spi device. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 269 The chassis process (chassisd) was running in the indicated standalone Flexible PIC Concentrator (FPC) mode. This message was logged in case the administrator wants it to run in a different mode. Type Event: This message reports an event, not an error Severity warning Copyright © 2010, Juniper Networks, Inc.
Page 270 Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. CHASSISD_TERM_SIGNAL System Log Message Received SIGTERM request, shutting down Copyright © 2010, Juniper Networks, Inc.
Page 271 The timer returned a null identifier, so the chassisd process could not clear the timer. Type Error: An error occurred Severity error Facility LOG_DAEMON CHASSISD_UNEXPECTED_EXIT System Log Message evMainLoop returned return-value (errno error-code) Description The chassis process (chassisd) exited unexpectedly and reported the indicated error. Copyright © 2010, Juniper Networks, Inc.
Page 272 Type Error: An error occurred Severity warning Facility LOG_DAEMON Action Contact your technical support representative. CHASSISD_UNSUPPORTED_PIC System Log Message PIC pic-slot in FPC fpc-slot (type pic-type, version version) is not supported Copyright © 2010, Juniper Networks, Inc.
Page 273 As a component (field-replaceable unit, or FRU) comes online, the chassis process (chassisd) verifies that the FRU's revision level or version is supported. The revision level of the indicated FRU was unsupported or otherwise invalid. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 274 Description The chassis process (chassisd) could not initialize the voltage sensor for the indicated component (field-replaceable unit, for FRU). Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 275: Chapter 19 Content System Log Messages
Event: This message reports an event, not an error Severity info Facility LOG_PFE Cause The transaction is in content filtering's block list Action Check the transaction to make sure it is not a false positive Copyright © 2010, Juniper Networks, Inc.
Page 277: Chapter 20 Cosd System Log Messages
For most interface types, a scheduler map must be applied to all interfaces on the PIC; therefore, a wildcard must be used to specify the interfaces. One exception to this rule is the Gigabit Ethernet IQ PIC. Copyright © 2010, Juniper Networks, Inc.
Page 278 -I failure), the first commit is 'commit' and not 'commit full'(cosd.conf will not commit is 'commit' and not 'commit full'(cosd.conf will not automatically be created), [class-of-service forwarding-classes] does notexist(the file cosd.conf will not get exported with plain 'commit') Action Do a 'commit full' Copyright © 2010, Juniper Networks, Inc.
Page 279 [edit class-of-service schedulers <scheduler-name> transmit-rate (<rate> | percent <percentage>)] hierarchy level. The scheduler is included in a scheduler map that is associated with a traffic control profile. The traffic control profile is named Copyright © 2010, Juniper Networks, Inc.
Page 280 'medium-high, ' or 'strict-high' for more than one of the schedulers in the map. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Correct the configuration so that the scheduler map includes only one scheduler with high, medium-high, or strict-high priority. Copyright © 2010, Juniper Networks, Inc.
Page 281 Traffic shaping not supported on interface device interface-name Description The class-of-service (CoS) process (cosd) did not apply the shaping rate that is configured for the indicated interface. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 282 CoS for L2TP. In terms of configuration, the 'per-session-scheduler' statement is not included at the [edit interfaces <interface-name> unit <logical-unit-number>] hierarchy level. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 283 Include the 'session-shaping' statement in the configuration for the PIC. COSD_LARGE_DELAY_BUFFER_INVALID System Log Message Error for interface interface-name error-message Description The class-of-service (CoS) process (cosd) did not apply the large delay buffer setting that is configured for the indicated interface. Copyright © 2010, Juniper Networks, Inc.
Page 284 The class-of-service (CoS) process (cosd) did not apply the fragmentation map to the indicated interface, even though it matches the wildcard, because the setting in the map exceeds the indicated class limit, which is configured on the interface itself. Copyright © 2010, Juniper Networks, Inc.
Page 285 [edit class-of-service schedulers <scheduler-name> transmit-rate <rate> | percent <percentage>] hierarchy level. The scheduler is included in the scheduler map applied to the interface. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 286 It will use the ifd-shaping rate/ifd-transmit rate for implementation of rate-limit. Description The 'rate-limit' statement is configured in one or more schedulers that are part of the indicated scheduler map. In order to apply this scheduler map to the indicated interface, Copyright © 2010, Juniper Networks, Inc.
Page 287 Interface interface-name cannot be bound to scheduler-map scheduler-map. It will be bound to default scheduler-map Description Interfaces belonging to a group cannot be bound to different scheduler maps. They will be bound to the default scheduler map. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 288 There is no need to explicitly set it. Description Tri-color marking is always enabled on this platform. There is no need to explicitly set it. Type Error: An error occurred Severity warning Facility LOG_DAEMON Action Remove the 'tri-color' configuration statement Copyright © 2010, Juniper Networks, Inc.
Page 289 Decrease the value of one or more 'transmit-rate' statements so that the sum is less than the interface transmission or shaping rate. COSD_UNKNOWN_CLASSIFIER System Log Message classifier type classifier-type is invalid Description The class-of-service (CoS) process (cosd) did not recognize the indicated classifier type from the rtsock library. Copyright © 2010, Juniper Networks, Inc.
Page 290 The class-of-service (CoS) process (cosd) did not recognize the indicated translation table type from the rtsock library. Type Error: An error occurred Severity warning Facility LOG_DAEMON Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 291: Chapter 21 Dcd System Log Messages
A software bug caused a memory leak, or the routing platform had insufficient memory. Action Contact your technical support representative. DCD_PARSE_CFG_WARNING System Log Message configuration-statement : warning-message Description The interface-control process (dcd) found a discrepant configuration Copyright © 2010, Juniper Networks, Inc.
Page 292 The 'hierarchical-scheduler' statement is included at the [edit interfaces] hierarchy level for the indicated interface, but is not supported either by the PIC or the configured type of encapsulation. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 293 PIC or the configured type of encapsulation. Type Error: An error occurred Severity warning Facility LOG_DAEMON Action Remove the 'per-unit-scheduler' or 'shared-scheduler' statement from the configuration for the interface. Copyright © 2010, Juniper Networks, Inc.
Page 294 This is a warning and the configuration will not be supported in future release. Action Contact your technical support representative. DCD_PARSE_MINI_EMERGENCY System Log Message dcd_mini_config: errors while parsing configuration overlay Description The interface process (dcd) encountered an unhandled internal state during interface parsing. Copyright © 2010, Juniper Networks, Inc.
Page 295 The interface process (dcd) encountered an unhandled internal state during interface parsing. Type Error: An error occurred Severity emergency Facility LOG_DAEMON Cause There might be a bug in the dcd process' parser. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 297: Chapter 22 Dfcd System Log Messages
System Log Message GENCFG write failed for Reason: error-message (error-code) Description The dynamic flow capture process (dfcd) could not send gencfg message, for the indicated reason. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 298 Error: An error occurred Severity error Facility LOG_DAEMON DFCD_SAMPLE_CLASS_ADD_FAILED System Log Message Unable to add sample class: error-message (error-code) Description The dynamic flow capture process (dfcd) could not add a sample class, for the indicated reason. Copyright © 2010, Juniper Networks, Inc.
Page 299 System Log Message Unable to delete sample class: error-message (error-code) Description The dynamic flow capture process (dfcd) could not delete a sample class, for the indicated reason. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 301: Chapter 23 Dfwd System Log Messages
Error: An error occurred Severity error Facility LOG_DAEMON Cause There might be a bug in the parser. Action Contact your technical support representative. DFWD_PARSE_STATE_EMERGENCY System Log Message dfwd encountered unhandled state while parsing interface Copyright © 2010, Juniper Networks, Inc.
Page 302 The firewall process (dfwd) detected that number of interface policers configured is exceeding maximum allowed. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Reduce the number of interface policers to within allowed limit. Copyright © 2010, Juniper Networks, Inc.
Page 303: Chapter 24 Dhcpd System Log Messages
Cause There might be a problem with the lease cache directory used to store persistent lease information. Action Contact your technical support representative. DHCPD_MEMORY_ALLOCATION_FAILURE System Log Message Unable to allocate memory for object-name: error-message Copyright © 2010, Juniper Networks, Inc.
Page 304 Exiting due to too many recvmsg() failures Description The Dynamic Host Configuration Protocol server process (dhcpd) could not receive data from the network, which it needs to do during normal operation. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 305 (address and routing instance) to the indicated destination (port and address), which it needs to do during normal operation. Type Error: An error occurred Severity error Facility LOG_AUTH Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 306 System Log Message socket(arguments) failed: error-message Description The Dynamic Host Configuration Protocol server process (dhcpd) could not create a socket. Type Error: An error occurred Severity error Facility LOG_AUTH Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 307: Chapter 25 Dynamic System Log Messages
Event: This message reports an event, not an error Severity error Facility LOG_AUTH DYNAMIC_VPN_AUTH_INVALID System Log Message type username is invalid Description The connection manager authentication failed due to invalid user/token Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 308 The connection manager authentication process was able to authenticate the indicated user/token successfully Type Event: This message reports an event, not an error Severity notice Facility LOG_AUTH DYNAMIC_VPN_CLIENT_CONFIG_WRITE System Log Message Client VPN config is saved in file filename for user username Copyright © 2010, Juniper Networks, Inc.
Page 309 Event: This message reports an event, not an error Severity notice Facility LOG_AUTH DYNAMIC_VPN_INIT_SUCCESSFUL System Log Message Connection manager initialization succeeded. Description Connection manager is initialized successfully. Type Event: This message reports an event, not an error Severity notice Facility LOG_AUTH Copyright © 2010, Juniper Networks, Inc.
Page 310 System Log Message Dynamic VPN license returned, license limit free, count overdrafted, current-value used Description The Access Manager client has disconnected and returned its license. Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 311 System Log Message Dynamic VPN license name installed, license limit total, count free Description An Access Manager license was installed successfully on this device. Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 312 Dynamic VPN license name deleted, license limit total, count free Description An Access Manager license is removed from this device. Type Event: This message reports an event, not an error Severity info Facility LOG_FIREWALL Copyright © 2010, Juniper Networks, Inc.
Page 313: Chapter 26 Eswd System Log Messages
Description The ARP request/response receieved on this port cannot be linked to any of the IPs assigned by DHCP. Type Error: An error occurred Severity alert Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 314 MAC limit (limit) exceeded at interface-name: shutting down the interface Description Interface was blocked because the number of MAC addresses learned on an interface has exceeded the user configured limit. Type Error: An error occurred Severity alert Copyright © 2010, Juniper Networks, Inc.
Page 315 A MAC address moved to a different interface more times per second than the user configured. ESWD_MAC_MOVE_LIMIT_DROP System Log Message MAC move limit (limit) exceeded at vlan-name for MAC address mac-addresse; dropping the packet on interface interface-name Copyright © 2010, Juniper Networks, Inc.
Page 316 Update the JUNOS software on the master Routing Engine, standby Routing Engine, or both, so that they are running compatible versions. ESWD_MIRROR_VERSION_MISMATCH System Log Message Mirror versions on Routing Engines are incompatible: mastermaster-is-local has version master-version, standbystandby-is-local has version standby-version Copyright © 2010, Juniper Networks, Inc.
Page 317 (error-message) Description The ethernet bridging process (eswd) could not write a message on the pipe to the periodic packet management process (ppmd). Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 318 Error: An error occurred Severity alert Facility LOG_DAEMON ESWD_STP_ROOT_PROTECT_IN_EFFECT System Log Message interface-name: root protect in effect for instance instance-id Description This condition occurs when STP root protect condition occurs. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 319 Log message to alert the user to the storm control setting. Type Error: An error occurred Severity alert Facility LOG_DAEMON ESWD_SYSTEM_CALL_FAILED System Log Message reason: error-message Description A system call made by enterprise switching process (eswd) failed. Copyright © 2010, Juniper Networks, Inc.
Page 320 Junos 10.3 System Log Messages Reference Type Error: An error occurred Severity error Facility LOG_DAEMON Cause It is possible that the kernel lacked the resources to fulfill the request. Copyright © 2010, Juniper Networks, Inc.
Page 321: Chapter 27 Eventd System Log Messages
(such as an interface name), which the eventd process replaces with actual values related to the event when it issues the command. Variable substitution failed for the indicated command. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 322 Facility LOG_DAEMON EVENTD_FORK_ERR System Log Message Unable to fork: error-message Description The event processing process (eventd) could not create a child process for executing policies. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 323 The event processing process (eventd) could not upload the indicated file to the indicated destination. Type Error: An error occurred Severity error Facility LOG_DAEMON EVENTD_POPEN_FAIL System Log Message Error error-code in invoking command 'command' Copyright © 2010, Juniper Networks, Inc.
Page 324 Command 'command' failed during rotation of file 'filename': error-message Description The event processing process (eventd) invoked the indicated command while attempting to rotate the indicated file. The command failed. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 325 (eventd) tried to change its privilege level to that of the indicated Junos user. The attempt failed. It made the attempt because the user-name statement is included at one of several possible levels under the [edit event-options policy <policy-name> then] hierarchy level. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 326 The event processing process (eventd) invoked the indicated command while attempting to transfer the indicated file. The command failed. Type Error: An error occurred Severity error Facility LOG_DAEMON EVENTD_TRANSFER_FORK_EXCEEDED System Log Message Unable to fork: too many child processes Copyright © 2010, Juniper Networks, Inc.
Page 327 Extensible Markup Language (XML) tagging like the following:<event-script-output-filename> output-file.tgz</event-script-output-filename>. The event processing process read the output filename and determined that its XML syntax was invalid. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 329: Chapter 28 Fcd System Log Messages
A system call made by the fibre channel process (fcd) failed. Type Error: An error occurred Severity error Facility LOG_DAEMON Cause It is possible that the kernel did not have enough resources to fulfill the request. Copyright © 2010, Juniper Networks, Inc.
Page 331: Chapter 29 Flow System Log Messages
Early aging of sessions is triggered when the number of concurrent session entries in the session table exceeds the configured high watermark. When the number of concurrent sessions drops below the configured low watermark, the router stops aggressively aging Copyright © 2010, Juniper Networks, Inc.
Page 332 This message notifies you that the number of concurrent sessions has dropped below the configured low watermark, and that aggressive aging of sessions has stopped. Type Event: This message reports an event, not an error Severity info Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 333: Chapter 30 Fpclogin System Log Messages
The Flexible PIC Concentrator (FPC) login process (pimlogin) could not send an interprocess communication (IPC) message to the indicated other process. The 'wxd' process is the WX Physical Interface Module process (wxd). Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 334 System Log Message Unable to complete 'error-message' operation Description The Flexible PIC Concentrator (FPC) login process (pimlogin) could not perform the indicated operation on a routing socket. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 335: Chapter 31 Fsad System Log Messages
Facility LOG_DAEMON FSAD_DIR_CREATE System Log Message Failed to create directory directory-name: error-message Description The File System Access process (fsad) could not create the indicated directory. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 336 Type Error: An error occurred Severity error Facility LOG_DAEMON Cause An internal software failure occurred. Action Contact your technical support representative. FSAD_FILE_REMOVE System Log Message Unable to remove file 'filename': reason Copyright © 2010, Juniper Networks, Inc.
Page 337 Error: An error occurred Severity error Facility LOG_DAEMON Cause The file path does not exist. Action Make sure the path specified in the request is valid. FSAD_FILE_SYNC System Log Message Unable to sync file 'filename': reason Copyright © 2010, Juniper Networks, Inc.
Page 338 The File System Access process (fsad) received a flow collector IPC message in which the type field was incorrect. Type Error: An error occurred Severity error Facility LOG_DAEMON FSAD_FLOWC_IPC_VERSION System Log Message Received flowc IPC message with incorrect version received-value (expected version expected-value) Copyright © 2010, Juniper Networks, Inc.
Page 339 Type Error: An error occurred Severity error Facility LOG_DAEMON FSAD_FS_STAT System Log Message statfs() failed for pathname pathname: reason Description The File System Access process (fsad) encountered an error in getting filesystem statistics. Copyright © 2010, Juniper Networks, Inc.
Page 340 Received generic IPC message with incorrect version received-value (expected version expected-value) Description The File System Access process (fsad) received an IPC message in which the version field was incorrect. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 341 The File System Access process (fsad) could not allocate memory. The system might be running low on memory. Type Error: An error occurred Severity error Facility LOG_DAEMON Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 342 'pathname' : not a directory : action Description The File System Access process (fsad) received a request for a pathname that was not a directory. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 343 The File System Access process (fsad) terminated a connection, stored the connection's (unwritten) data to disk, and purged it from its data structures. Type Event: This message reports an event, not an error Severity notice Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 344 Event: This message reports an event, not an error Severity error Facility LOG_DAEMON Cause The fsad process was invoked with incorrect command-line arguments. Action Check the usage and invoke the fsad process with the correct command-line arguments. Copyright © 2010, Juniper Networks, Inc.
Page 345: Chapter 32 Fud System Log Messages
FUD_BIND_FAILURE System Log Message bind(port port) failed: error-message Description The UDP forwarding process (fud) received the indicated error when it tried to bind a socket to a local address. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 346 Type Error: An error occurred Severity error Facility LOG_DAEMON Action Become the root user before issuing the 'fud' command. FUD_PIDLOCK_FAILURE System Log Message Unable to lock PID file; another program-name was running Copyright © 2010, Juniper Networks, Inc.
Page 347 Action Contact your technical support representative. FUD_RTSOCK_WRITE_FAILURE System Log Message Unable to write to routing socket: error-message Description The UDP Forwarding process (fud) could not write to its routing socket for the indicated reason. Copyright © 2010, Juniper Networks, Inc.
Page 348 System Log Message setsockopt(arguments) failed: error-message Description The UDP Forwarding process (fud) could not set the indicated socket option. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 349 Chapter 32: FUD System Log Messages FUD_SOCKET_FAILURE System Log Message socket(arguments) failed: error-message Description The UDP Forwarding process (fud) could not create a socket. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 351: Chapter 33 Fwauth System Log Messages
Event: This message reports an event, not an error Severity info Facility LOG_PFE FWAUTH_FTP_USER_AUTH_FAIL System Log Message User username at client-address is rejected. Description User authentication failed because the username or password was invalid. Copyright © 2010, Juniper Networks, Inc.
Page 352 Event: This message reports an event, not an error Severity info Facility LOG_PFE FWAUTH_TELNET_USER_AUTH_ACCEPTED System Log Message User username of group group-name at client-address is accepted. Description The authenticated user can start accessing protected resources Copyright © 2010, Juniper Networks, Inc.
Page 353 System Log Message WebAuth user username of group group-name at client-address is accepted. Description The authenticated user can start accessing protected resources. Type Event: This message reports an event, not an error Severity info Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 355: Chapter 34 Gprsd System Log Messages
As the general packet radio service daemon process (gprsd) restarted, one or more of its subcomponents could not read its configuration information from the configuration database. The gprsd process restarted regardless without affecting routing performance. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 357: Chapter 35 Hncached System Log Messages
Type Error: An error occurred Severity error Facility LOG_DAEMON Action 1)If the hostname used in config is incorrect, fix it. 2) Ensure that the configured name-server is reachabe and is working. Copyright © 2010, Juniper Networks, Inc.
Page 359: Chapter 36 Iccpd System Log Messages
ICCPD_OPEN_ERROR System Log Message error-message: open error on pipe Description The interchassis communication process (iccpd) could not initialize. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 360 Description The interchassis communication process (iccpd) could not write a message on a pipe for the indicated client. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 361: Chapter 37 Idp System Log Messages
The application-level distributed denial-of-service (AppDDoS) state transition occurred when the number of application transactions exceeded the user-configured connection or context thresholds Type Event: This message reports an event, not an error Severity info Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 362 Error: An error occurred Severity error Facility LOG_AUTH IDP_DAEMON_INIT_FAILED System Log Message Aborting...A failure was encountered;error-message Description An attempt to start IDP policy daemon failed because an error was encountered during initialization. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 363 IDP policy. Type Event: This message reports an event, not an error Severity notice Facility LOG_AUTH IDP_POLICY_UNLOAD_FAILED System Log Message Failed to unload IDP policy. reason: reason. Copyright © 2010, Juniper Networks, Inc.
Page 364 LOG_AUTH IDP_SECURITY_INSTALL_RESULT System Log Message security package install result(status) Description IDP background process has returned the security package install result Type Event: This message reports an event, not an error Severity notice Facility LOG_AUTH Copyright © 2010, Juniper Networks, Inc.
Page 365 IDP Signagure update license(ID=feature-id) has expired Description IDP signature update license key has expired. Signature update may not work any more. Type Event: This message reports an event, not an error Severity warning Facility LOG_AUTH Copyright © 2010, Juniper Networks, Inc.
Page 367: Chapter 38 Jade System Log Messages
Authentication succeded for user 'username' Description The jade authentication process authenticated the indicated user. Type Event: This message reports an event, not an error Severity notice Facility JADE_EXEC_ERROR System Log Message CLI xml-mode exec error: error-message Copyright © 2010, Juniper Networks, Inc.
Page 368 JADE_SOCKET_ERROR System Log Message Socket operation 'operation' failed: error-message Description The indicated socket operation, initiated by the JUNOScript authentication process (jade), failed for the indicated reason. Type Error: An error occurred Severity error Facility Copyright © 2010, Juniper Networks, Inc.
Page 369: Chapter 39 Jcs System Log Messages
Severity error Facility LOG_DAEMON JCS_BBD_NOT_FOUND System Log Message Blade slot bay data not found Description Blade bay data was not found for the specified blade. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 370 Severity error Facility LOG_DAEMON JCS_EXT_LINK_STATE System Log Message Switch slot EXT link state is state Description The JCS process (jcsd) detects a change of state for the external link of the indicated switch module. Copyright © 2010, Juniper Networks, Inc.
Page 371 System Log Message MM communication error (error-message) Description The JCS process (jcsd) could not send an SNMP request to the Management Module because of the indicated error. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 372 Severity error Facility LOG_DAEMON JCS_RSD_LINK_STATE System Log Message Switch slot RSD link state is state Description The JCS process (jcsd) detects a change of state for the RSD link of the indicated switch module. Copyright © 2010, Juniper Networks, Inc.
Page 373 Switch slot communication is OK Description The JCS process (jcsd) has established a communication link with the indicated Switch Module. Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 375: Chapter 40 Jdiameterd System Log Messages
System Log Message Unable to listen on internal-ip Description The Diameter process(jdiameterd) is unable to listen on the internal ip socket for function side connections. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 376 JDIAMETERD_FUNC_USCK_LISTEN_FAIL System Log Message Unable to listen on pathname Description The Diameter process(jdiameterd) is unable to listen on the unix socket for function side connections. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 377: Chapter 41 Jptspd System Log Messages
The packet triggered subscriber process (jptspd) could not dynamically allocate memory. Type Error: An error occurred Severity error Facility Cause A software bug caused a memory leak, or too many subscriber and service sessions. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 378 Severity info Facility JPTSPD_SRC_FAST_SYNC_START System Log Message JPTSPD fast synchronization started partition-name Description The packet triggered subscriber process (jptspd) started fast synchronization with SRC. Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 379 JPTSPD_SRC_FULL_SYNC_START System Log Message JPTSPD full synchronization started partition-name Description The packet triggered subscriber process (jptspd) started full synchronization with SRC. Type Event: This message reports an event, not an error Severity info Facility Copyright © 2010, Juniper Networks, Inc.
Page 382 Redundancy mode change will not be effective until all nodes in the cluster are rebooted simultaneously Description The Juniper Services Redundancy Protocol process (JSRPD) detected a change in chassis cluster redundancy mode. The new mode is not effective until all nodes in the cluster are rebooted. Copyright © 2010, Juniper Networks, Inc.
Page 383 Facility LOG_DAEMON JSRPD_SET_INTF_MON_FAILURE System Log Message Interface Monitor failed for redundancy-group rg-id Description The Juniper Services Redundancy Protocol process (JSRPD) detected interface monitoring failure for a redundancy group. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 384 The Juniper Services Redundancy Protocol process (JSRPD) detected Services Processing Unit (SPU) monitoring failure for a redundancy group. Type Error: An error occurred Severity error Facility LOG_DAEMON JSRPD_SOCKET_CREATION_FAILURE System Log Message Socket creation (server) failed unexpectedly error-message. Copyright © 2010, Juniper Networks, Inc.
Page 385 Interface Monitor failure recovered for redundancy-group rg-id Description The Juniper Services Redundancy Protocol process (JSRPD) detected that the previous interface monitoring failure no longer exists for a redundancy group. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 386 Services Processing Unit (SPU) monitoring failure no longer exists for a redundancy group. Type Error: An error occurred Severity error Facility LOG_DAEMON JSRPD_USAGE System Log Message Usage: jsrpd [-C] [-N] [-X] [-d debug-level] [-l] [-v] Copyright © 2010, Juniper Networks, Inc.
Page 387 Chapter 42: JSRPD System Log Messages Description The Juniper Services Redundancy Protocol process (JSRPD) was invoked with incorrect options. Type Event: This message reports an event, not an error Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 389: Chapter 43 Kmd System Log Messages
Description The key management process (kmd) maintains pools of logical interfaces for assignment to IP Security (IPSec) interfaces. It could not allocate a logical interface, because none were available in the indicated pool. Copyright © 2010, Juniper Networks, Inc.
Page 390 Facility LOG_AUTH Cause Failover attempts can fail repeatedly if both the primary and backup peers are unreachable during the failover. KMD_DPD_FAILOVER_NO_ACTIVE_PEER System Log Message Tunnel tunnel-name did not fail over: no active peer configured Copyright © 2010, Juniper Networks, Inc.
Page 391 (address and port) from the local peer. Type Error: An error occurred Severity error Facility LOG_AUTH KMD_DPD_INVALID_ADDRESS System Log Message Unable to send DPD reply: local peer local-address; remote peer remote-address Copyright © 2010, Juniper Networks, Inc.
Page 392 Event: This message reports an event, not an error Severity notice Facility LOG_AUTH KMD_DPD_REMOTE_PEER_NOT_FOUND System Log Message Unable to send DPD reply: DPD entry for remote peer remote-address:remote-port not found in IKE server instance service-set Copyright © 2010, Juniper Networks, Inc.
Page 393 The IKE Quick Mode notification message from the indicated remote gateway and remote port contains duplicate value for life duration. Hence Quick Mode notification payload is dropped. Type Error: An error occurred Severity error Facility LOG_SYSLOG Copyright © 2010, Juniper Networks, Inc.
Page 394 Description There is no local IKE server context in the indicated service set, hence failed to send the SPI delete notification request. Type Error: An error occurred Severity error Facility LOG_SYSLOG Copyright © 2010, Juniper Networks, Inc.
Page 395 : initiator = remote-initiator responder = remote-responder Description Initiator and responder identities at the local end are inconsistent with the remote peer's identities. Quick Mode negotiation is aborted. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 396 During Internet Key Exchange (IKE) Phase 2 negotiation, the indicated remote peer (address and port) sent a lifetime notification message with an unequal payload length. As a result, the key management process (kmd) discarded the notification message. Copyright © 2010, Juniper Networks, Inc.
Page 397 (SA) lifetime. The type is invalid (the acceptable units are seconds and kilobytes). As a result, the key management process (kmd) discarded the notification message. Type Error: An error occurred Severity error Facility LOG_AUTH Copyright © 2010, Juniper Networks, Inc.
Page 398 Description It is not possible to start the Phase-1 negotiation to the indicated remote gateway because there is no proposal present. Type Error: An error occurred Severity error Facility LOG_SYSLOG Copyright © 2010, Juniper Networks, Inc.
Page 399 The key management process (kmd) could not read the information in an Internet Key Exchange (IKE) Phase 1 proposal about the Diffie-Hellman (DH) group to use. Type Error: An error occurred Severity error Facility LOG_AUTH Copyright © 2010, Juniper Networks, Inc.
Page 400 A security policy database (SPD) handler is not registered for the indicated service set. As a result, Internet Key Exchange (IKE) Phase 1 negotiation did not begin. Type Error: An error occurred Severity error Facility LOG_AUTH Copyright © 2010, Juniper Networks, Inc.
Page 401 Phase 1 is not a valid value. The only valid value is the Internet Security Association and Key Management Protocol (ISAKMP). The key management process (kmd) rejected the transform. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 402 The indicated identifier for a transform negotiated during Internet Key Exchange (IKE) Phase 1 is not the indicated expected value. The key management process (kmd) rejected the transform. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 403 Description The configuration for the indicated security association (SA) did not include the information about local and remote traffic selectors required for Internet Key Exchange (IKE) Phase 2, so that phase did not begin. Copyright © 2010, Juniper Networks, Inc.
Page 404 Encapsulating Security Payload (ESP) was negotiated as the protocol During Internet Key Exchange (IKE) Phase 2, but no values were negotiated for the authentication and encryption algorithms. As a result, the key management process (kmd) rejected the transform. Copyright © 2010, Juniper Networks, Inc.
Page 405 Management Protocol (ISAKMP) or the value RESERVED was chosen as the protocol for the indicated security association (SA). They are not supported values, so the SA was not established. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 406 (SA) between the indicated local peer (address and port) and remote peer (address and port), because the indicated size of the associated Security Parameter Index (SPI) was not as expected. As a result, the SA was not deleted. Copyright © 2010, Juniper Networks, Inc.
Page 407 Local gateway local-address:local-port, Remote gateway remote-address:remote-port Description The SPI size in the delete notification is invalid. Hence delete request is rejected. Quick Mode notification payload is dropped. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 408 Failed to initiate the Phase-1 negotiation for local:local-peer and remote:remote-peer in instance:service-set Description Phase-1 negotiation can not be started because either the local gateway identity or the remote gateway identity is unknown. Type Error: An error occurred Severity error Facility LOG_SYSLOG Copyright © 2010, Juniper Networks, Inc.
Page 409 System Log Message New group mode not supported currently Description The IKE New Group mode negotiations failed, because this is not a supported feature currently. Type Error: An error occurred Severity error Facility LOG_SYSLOG Copyright © 2010, Juniper Networks, Inc.
Page 410 Simple Network Management Protocol (SNMP) statistics about IP Security (IPSec) security associations (SAs). As a result, it could not retrieve statistics from the indicated PIC. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 411 System Log Message The DF-BIT for VPN vpn-name has been set to argument. Description VPN DF bit status has been set. Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 412 System Log Message VPN vpn-name from remote-address is up. Description Notifiication to user that VPN monitor detects IPSec SA is up. Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 413: Chapter 44 L2Ald System Log Messages
Packet Forwarding Engines, because the indicated operation failed during configuration generation. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. L2ALD_IPC_MESSAGE_ERROR System Log Message Message (type message-type, subtype message-subtype, opcode message-opcode) received with error error-message Copyright © 2010, Juniper Networks, Inc.
Page 414 The Layer 2 address learning process (l2ald) could not write to an interprocess communication (IPC) pipe for the indicated reason. Type Error: An error occurred Severity error Facility LOG_DAEMON Cause One possible reason is that there was no reader for the pipe. Copyright © 2010, Juniper Networks, Inc.
Page 416 'interface-mac-limit' statement at the [edit routing-instances <routing-instance-name> protocol l2-learning] or the [edit routing-instances <routing-instance-name> protocols vpls] hierarchy level. L2ALD_MAC_LIMIT_RESET_BD System Log Message Resumed adding MAC addresses learned from routing instance 'routing-instance', domain 'bridge-domain:vlan-id'; current count is count Copyright © 2010, Juniper Networks, Inc.
Page 417 Resumed adding MAC addresses learned from routing instance 'routing-instance'; current count is count Description The Layer 2 address learning process (l2ald) resumed adding addresses to the MAC address table that were learned by interfaces in the indicated bridging domain, because Copyright © 2010, Juniper Networks, Inc.
Page 418 Unable to create pipe to Layer 2 address-learning manager: error-message Description The Layer 2 address learning process (l2ald) could not open a pipe for interprocess communication (IPC) with a Layer 2 address-learning manager process. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 419 The Layer 2 address learning process (l2ald) did not add an entry for the indicated logical interface to the interface table, because its name exceeds the indicated limit on the number of characters. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 420 (PBB) feature had discovered that one of the interfaces was on a revision A card. Type Error: An error occurred Severity warning Facility LOG_DAEMON Cause An interface was discovered on the revision A card. Revision A cards do not support provider backbone bridging (PBB) features. Copyright © 2010, Juniper Networks, Inc.
Page 421 (pip0) interface from the kernel. Type Error: An error occurred Severity critical Facility LOG_DAEMON Cause The chassis process may have been too slow in creating the interface. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 423: Chapter 45 L2Cpd System Log Messages
ID (PID) terminated because the indicated type of check failed at the indicated line number in the indicated source file. The process continued to run, but created a diagnostic core file for analysis by technical support personnel. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 424 Description The Layer 2 Control Protocol process (l2cpd) determined that the kernel supports an indicated older version of the indicated routing socket message type than it requires. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 425 The Layer 2 Control Protocol process (l2cpd) did not receive input from the indicated management peer within the timeout period. Type Error: An error occurred Severity warning Facility LOG_DAEMON Cause Messages that immediately follow this message in the system log might provide information about possible causes. Copyright © 2010, Juniper Networks, Inc.
Page 426 System Log Message function-name: write error on pipe to ppmd (error-message) Description The Layer 2 Control Protocol process (l2cpd) could not write a message on the pipe to the periodic packet management process (ppmd). Copyright © 2010, Juniper Networks, Inc.
Page 427 Protocol process (l2cpd) ran uninterrupted for the indicated period of time (the sum of the indicated user and system times), which is considered excessive. Type Event: This message reports an event, not an error Severity warning Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 428 System Log Message Child process 'task-name' stopped by SIGsignal-name Description While a child process of the Layer 2 Control Protocol process (l2cpd) was performing the indicated operation, it stopped in response to the indicated signal. Copyright © 2010, Juniper Networks, Inc.
Page 429 Unable to reinitialize Description The Layer 2 Control Protocol process (l2cpd) did not reinitialize as requested, because it was running in a state that did not allow reconfiguration. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 430 Error: An error occurred Severity error Facility LOG_DAEMON L2CPD_TASK_REINIT System Log Message Reinitialized Description The Layer 2 Control Protocol process (l2cpd) reinitialized. Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 431 The next commit of the configuration database will reenable tracing. Type Event: This message reports an event, not an error Severity error Facility LOG_DAEMON L2CPD_XSTP_SHUTDOWN_FAILED System Log Message Unable to shut down error-message module Copyright © 2010, Juniper Networks, Inc.
Page 432 The Layer 2 Control Protocol process (l2cpd) could not shut down the indicated Rapid Spanning Tree Protocol (RSTP) or Multiple Spanning Tree Protocol (MSTP) module. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 433: Chapter 46 L2Tpd System Log Messages
Type Error: An error occurred Severity error Facility LOG_NEWS Action Remove the CoS profile from the RADIUS database or contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 434 Unable to allocate memory for tunnel group Description The Layer 2 Tunneling Protocol process (l2tpd) could not allocate memory for the data structure used to record tunnel group information. Type Error: An error occurred Severity error Facility LOG_NEWS Copyright © 2010, Juniper Networks, Inc.
Page 435 Severity error Facility LOG_NEWS L2TPD_EVLIB_FD_NOT_REGISTERED System Log Message No file descriptor registered Description The Layer 2 Tunneling Protocol process (l2tpd) could not find a registered file descriptor while attempting to set an event mask. Copyright © 2010, Juniper Networks, Inc.
Page 436 LOG_NEWS L2TPD_FILTER_FILE_OPEN_FAILED System Log Message Unable to open file filename Description The Layer 2 Tunneling Protocol process (l2tpd) could not open the indicated filter file. Type Error: An error occurred Severity error Facility LOG_NEWS Copyright © 2010, Juniper Networks, Inc.
Page 437 It could not add the indicated interface device to the in-memory database. Type Error: An error occurred Severity error Facility LOG_NEWS L2TPD_IFD_DELETE_FAILED System Log Message function-name: unable to delete interface device interface-name Copyright © 2010, Juniper Networks, Inc.
Page 438 It could not add the indicated logical interface to the in-memory database. Type Error: An error occurred Severity error Facility LOG_NEWS L2TPD_IFL_DELETE_FAILED System Log Message function-name: unable to delete interface interface-name Copyright © 2010, Juniper Networks, Inc.
Page 439 Error: An error occurred Severity error Facility LOG_NEWS L2TPD_INSTANCE_CREATE_FAILED System Log Message Unable to create L2TP instance tunnel-group Description The Layer 2 Tunneling Protocol process (l2tpd) could not create an L2TP instance for the indicated tunnel group. Copyright © 2010, Juniper Networks, Inc.
Page 440 System Log Message Unable to allocate MLPPP bundle Description The Layer 2 Tunneling Protocol process (l2tpd) could not allocate memory for a multilink Point-to-Point Protocol (MLPPP) bundle. Type Error: An error occurred Severity error Facility LOG_NEWS Copyright © 2010, Juniper Networks, Inc.
Page 441 Unable to allocate bitmap field for MLPPP ID map Description The Layer 2 Tunneling Protocol process (l2tpd) could not allocate memory for a bitmap field in a multilink Point-to-Point Protocol (MLPPP) identifier map data structure. Copyright © 2010, Juniper Networks, Inc.
Page 442 The Layer 2 Tunneling Protocol process (l2tpd) could not add a link for the indicated multilink Point-to-Point Protocol (MLPPP) bundle in the indicated tunnel and session, because the maximum number of links was exceeded. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 443 The Layer 2 Tunneling Protocol process (l2tpd) could not add a link for the indicated multilink Point-to-Point Protocol (MLPPP) bundle in the indicated tunnel and session, because the bundle speed does not match. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 444 Unable to assign pool address (L2TP tunnel tunnel-id, session session-id) Description The Layer 2 Tunneling Protocol process (l2tpd) could not assign a pool address in the indicated tunnel and session. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 445 Profile profile-name not found Description The Layer 2 Tunneling Protocol process (l2tpd) could not locate an access profile from the configuration in order to find radius servers to authenticate. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 446 Type Error: An error occurred Severity notice Facility LOG_NEWS L2TPD_RADIUS_RT_INST_NOT_FOUND System Log Message Ignoring RADIUS server radius-server: unable to retrieve routing instance routing-instance (error-message) Copyright © 2010, Juniper Networks, Inc.
Page 447 LOG_NEWS L2TPD_RPD_ASYNC_UNREG_FAILED System Log Message Unable to unregister with rpd (return-value) Description The Layer 2 Tunneling Protocol process (l2tpd) could not unregister asynchronously with the routing protocol process (rpd). Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 448 L2TP tunnel tunnel-id, session session-id): error-message (error-code) Description The Layer 2 Tunneling Protocol process (l2tpd) could not delete a route for the indicated address and prefix, gateway, tunnel, and session. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 449 (rpd). Type Error: An error occurred Severity error Facility LOG_NEWS L2TPD_RPD_TBL_LOCATE_BY_NAME System Log Message Unable to locate rpd table by name: error-message (error-code) Copyright © 2010, Juniper Networks, Inc.
Page 450 System Log Message Unable to open routing socket connection Description The Layer 2 Tunneling Protocol process (l2tpd) could not open a routing socket connection, which it uses to communicate with the Junos operating system kernel. Copyright © 2010, Juniper Networks, Inc.
Page 451 The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the Junos configuration database in memory. It could not add information about the indicated session and tunnel to the in-memory configuration for the PIC. Copyright © 2010, Juniper Networks, Inc.
Page 452 Description The Layer 2 Tunneling Protocol process (l2tpd) could not retrieve the interface family structure for the indicated logical interface index in the indicated tunnel and session. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 453 The Layer 2 Tunneling Protocol process (l2tpd) detected that the configuration information for the indicated logical interface was deleted for a session. Type Error: An error occurred Severity error Facility LOG_NEWS L2TPD_SESSION_IFL_DELETE_FAILED System Log Message function-name: unable to delete session identifier from interface interface-name Copyright © 2010, Juniper Networks, Inc.
Page 454 System Log Message function-name: interface interface-name already has associated session (value1/value2) Description The Layer 2 Tunneling Protocol process (l2tpd) determined that the indicated logical interface already had an associated session. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 455 Description The Layer 2 Tunneling Protocol process (l2tpd) could not retrieve the indicated routing table associated with the indicated logical interface in the indicated tunnel and session. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 456 The 'show services l2tp multilink' command was issued with the indicated option to specify the amount of information to return, but the command does not support that option. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 457 Type Error: An error occurred Severity error Facility LOG_NEWS L2TPD_TRACE_FILE_OPEN_FAILED System Log Message Unable to open trace file: error-message Description The Layer 2 Tunneling Protocol process (l2tpd) could not open its trace file. Copyright © 2010, Juniper Networks, Inc.
Page 458 LOG_NEWS L2TPD_TUNNEL_DELETE_FAILED System Log Message Unable to delete L2TP tunnel tunnel-id (errno error-code) Description The Layer 2 Tunneling Protocol process (l2tpd) could not delete information about the indicated tunnel. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 459 Unable to delete tunnel group tunnel-group (service set service-set): error-code Description The Layer 2 Tunneling Protocol process (l2tpd) could not delete information about the indicated tunnel group and service set. Type Error: An error occurred Severity error Facility LOG_NEWS Copyright © 2010, Juniper Networks, Inc.
Page 460 The Layer 2 Tunneling Protocol process (l2tpd) could not restart a protocol tunnel group. Type Error: An error occurred Severity error Facility LOG_NEWS L2TPD_USER_AUTHN_NOT_FOUND System Log Message Unable to find user profile username during PPP authentication Copyright © 2010, Juniper Networks, Inc.
Page 461 The Layer 2 Tunneling Protocol process (l2tpd) could not retrieve the password for the indicated username, which it needs for Point-to-Point Protocol (PPP) authentication of a session. Type Error: An error occurred Severity error Facility LOG_NEWS Copyright © 2010, Juniper Networks, Inc.
Page 463: Chapter 47 Lacpd System Log Messages
System Log Message Unable to allocate memory for interface interface-name Description The Link Aggregation Control Protocol process (lacpd) could not allocate memory for the indicated interface. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 465: Chapter 48 Lfmd System Log Messages
Unable to open synchronous routing socket: error-message Description The Ethernet Operation, Administration and Management link-fault management process (lfmd) could not open a routing socket to create a connection. Type Error: An error occurred Severity error Facility LOG_AUTH Copyright © 2010, Juniper Networks, Inc.
Page 467: Chapter 49 Libesptask System Log Messages
The process using libesptask tried again to connect to the indicated Simple Network Management Protocol (SNMP) master agent after a connection attempt failed. Type Error: An error occurred Severity error Facility LIBESPTASK_SNMP_INVALID_SOCKET System Log Message function-name: socket file-descriptor is invalid Copyright © 2010, Juniper Networks, Inc.
Page 468 The process using libesptask 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. Type Error: An error occurred Severity error Facility Copyright © 2010, Juniper Networks, Inc.
Page 469: Chapter 50 Libjnx System Log Messages
A JUNOS process tried to use the indicated utility to create a compressed version of the indicated old system log file. The attempt failed for the indicated reason. Type Error: An error occurred Severity info Facility Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 470 Type Error: An error occurred Severity notice Facility Cause An internal software failure occurred. Action Contact your technical support representative. LIBJNX_EXEC_FAILED System Log Message Child exec failed for command 'command': error-message Copyright © 2010, Juniper Networks, Inc.
Page 471 System Log Message Command exited: PID pid, status return-valuecore-dump-status, command 'command' Description A JUNOS process created a child process to execute the indicated command for it. The child process exited abnormally with the indicated exit code. Copyright © 2010, Juniper Networks, Inc.
Page 472 A JUNOS process could not determine the hostname for the master Routing Engine on a routing node in a routing matrix, because the indicated chassis ID provided for the routing platform was invalid. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 473 System Log Message Unable to raise privilege level: error-message Description A JUNOS process attempted to set its effective user ID to the root user. The attempt failed. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 474 Description A JUNOS process could not perform the indicated operation on the indicated SNMP engine data file. Type Error: An error occurred Severity critical Facility Cause An internal software failure occurred. Copyright © 2010, Juniper Networks, Inc.
Page 475 XML encoding of the data was invalid. The parser skipped ahead to the likely endpoint for the invalid data. Type Error: An error occurred Severity error Facility Cause A possible cause is improper escaping of character constants in the data stream. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 477: Chapter 51 Libjsnmp System Log Messages
An internal software failure occurred. Action Contact your technical support representative. LIBJSNMP_IPC_READ_ERROR System Log Message Unable to read inbound-bytes bytes: sock: port (type: port-type) Description Error in reading IPC messages during SNMP related messaging Copyright © 2010, Juniper Networks, Inc.
Page 478 An internal software failure occurred. Action Contact your technical support representative. LIBJSNMP_NS_LOG_EMERG System Log Message EMERG: argument Description SNMP errors with LOG_EMERG as severity Type Error: An error occurred Severity emergency Facility Cause An internal software failure occurred. Copyright © 2010, Juniper Networks, Inc.
Page 479 An internal software failure occurred. Action Contact your technical support representative. LIBJSNMP_RTMSIZE_MISMATCH_ERR System Log Message routing socket msg size argument of argument1 (call buf = argument2) Description Error in message length while reading rtsocket for SNMP related operation Copyright © 2010, Juniper Networks, Inc.
Page 480 Contact your technical support representative. LIBJSNMP_SOCKET_OPEN_ERR System Log Message routing socket open error argument Description Failure in opening routing socket Type Error: An error occurred Severity error Facility Cause An internal software failure occurred. Copyright © 2010, Juniper Networks, Inc.
Page 481 Description Trying to send invalid object as varbind while creating SNMP traps Type Error: An error occurred Severity error Facility Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 483: Chapter 52 Libmsprpc System Log Messages
A JUNOS process (mspinfo) could not establish initialization of the kcom subsystem. Type Error: An error occurred Severity error Facility Cause Possible reasons: can't initialize kcom services. Action Contact your technical support representative. LIBMSPRPC_CLIENT_KCOM_NO_IF System Log Message No active extension-provider interfaces Copyright © 2010, Juniper Networks, Inc.
Page 484 PIC. Action Contact your technical support representative. LIBMSPRPC_CLIENT_PIC_DOWN System Log Message Interface interface-name is down Description Remote execution of the command given from the RE to the PIC failed, the PIC is down. Copyright © 2010, Juniper Networks, Inc.
Page 485 Remote execution of the command given from the RE to the PIC failed, PIC returned unexpected output. Type Error: An error occurred Severity notice Facility Cause Possible reasons: a)wrong command b)wrong arguments. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 487: Chapter 53 License System Log Messages
Error: An error occurred Severity error Facility LICENSE_CONN_TO_LI_CHECK_SUCCESS System Log Message Connected to license-check Description The indicated process succesfully connected to the license-check process. Type Event: This message reports an event, not an error Severity info Facility Copyright © 2010, Juniper Networks, Inc.
Page 488 Type Event: This message reports an event, not an error Severity alert Facility LOG_DAEMON LICENSE_GRACE_PERIOD_EXPIRED System Log Message License grace period for feature feature-name(feature-id) has expired Copyright © 2010, Juniper Networks, Inc.
Page 489 Error: An error occurred Severity error Facility LICENSE_REG_ERROR System Log Message Registration request failed: current-value Description The license registration request failed. A request needs to be resent to the license-check process. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 490 Error[error-argument]: Failed to write usage count to file filename Description The indicated process encountered a system error while attempting to write to the scale-usage file. Type Error: An error occurred Severity critical Facility LICENSE_SIGNATURE_VERIFY_FAILED System Log Message Signature verification failed: error-message Copyright © 2010, Juniper Networks, Inc.
Page 491 License verification failed for file 'error-message': filename (system error: system-error-message) Description The management process (mgd) could not verify the indicated license file because of the indicated internal file-handling error. Type Error: An error occurred Severity error Facility Copyright © 2010, Juniper Networks, Inc.
Page 493: Chapter 54 Lldpd System Log Messages
A system call made by the Link Layer Discovery Protocol process (LLDPD) failed. Type Error: An error occurred Severity error Facility LOG_KERN Cause It is possible that the kernel lacked the resources to fulfill the request. LLDPD will recover. Copyright © 2010, Juniper Networks, Inc.
Page 495: Chapter 55 Login System Log Messages
Description Several login attempts failed for the indicated username. Type Event: This message reports an event, not an error Severity notice Facility LOG_AUTH LOGIN_FAILED_SET_CONTEXT System Log Message Failed to set context for user username Copyright © 2010, Juniper Networks, Inc.
Page 496 Facility LOG_AUTH LOGIN_LOCAL_PASSWORD System Log Message Requested local password from user username Description The PAM authentication attempt failed for the indicated user, who was prompted for the password recorded in the local password file. Copyright © 2010, Juniper Networks, Inc.
Page 497 The number of failed PAM authentication attempts for the indicated user exceeded the maximum limit. Type Error: An error occurred Severity error Facility LOG_AUTH LOGIN_PAM_STOP System Log Message Failed to end PAM session: error-message Copyright © 2010, Juniper Networks, Inc.
Page 498 The indicated username was authenticated as a superuser and logged into the shell specified for the root user in the password file. Type Event: This message reports an event, not an error Severity info Copyright © 2010, Juniper Networks, Inc.
Page 499 System Log Message Login attempt timed out after duration seconds Description A login attempt failed to complete in the maximum time allowed. Type Event: This message reports an event, not an error Severity info Facility LOG_AUTH Copyright © 2010, Juniper Networks, Inc.
Page 501: Chapter 56 Lpdfd System Log Messages
System Log Message argument: Cannot retrieve peer info for session. Error: error-message Description The local policy decision function process (lpdfd) pconn server failed to initialize Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 503: Chapter 57 Lrmux System Log Messages
Unable to open PID file filename Description The Logical System Multiplexer process (lrmuxd) could not open the indicated PID lock file for a logical system process (rpd). Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 504 The Logical System Multiplexer process (lrmuxd) attempted to lock the file that records its process ID (PID), which serves to prevent multiple instances of the lrmuxd process from running simultaneously. The attempt failed. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 505: Chapter 58 Mcsnoopd System Log Messages
Connection to management peer process-name timed out waiting for input Description The connection between the snooping process (mcsnoopd) and the indicated management process (mgd) timed out before input arrived from the mgd process. Type Error: An error occurred Severity warning Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 507: Chapter 59 Mib2D System Log Messages
Facility LOG_DAEMON Cause The configuration was invalid. Action Correct the invalid portion of the configuration as described in the error message on the console. MIB2D_FILE_OPEN_FAILURE System Log Message Unable to open file 'filename': error-message Copyright © 2010, Juniper Networks, Inc.
Page 508 MIB2D_IFL_IFINDEX_FAILURE System Log Message SNMP index assigned to interface-name.interface-unit changed from old-value to new-value Description There was a change to the SNMP ifIndex assigned to the indicated existing interface. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 509 Type Event: This message reports an event, not an error Severity warning Facility LOG_DAEMON MIB2D_PMON_OVERLOAD_SET_TRAP System Log Message Overload name: overload-name, interface: interface-name Copyright © 2010, Juniper Networks, Inc.
Page 510 Description MIB2D can not assign snmp index for each interface. Type Error: An error occurred Severity error Facility LOG_DAEMON Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 511 MIB2D can not write into a file containing all the indices Type Error: An error occurred Severity error Facility LOG_DAEMON Cause An internal software failure occurred. Action Contact your technical support representative. MIB2D_SYSCTL_FAILURE System Log Message function-name: sysctl type failed: error-message Copyright © 2010, Juniper Networks, Inc.
Page 512 Description The MIB II process (mib2d) could not send a trap header. Type Error: An error occurred Severity error Facility LOG_DAEMON Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 513: Chapter 60 Mpls_Oam System Log Messages
LOG_DAEMON Action Configure traceroute to use a valid source address. MPLS_OAM_PATH_LIMIT_REACHED System Log Message fec-address: traceroute path limit was reached Description The traceroute path limit was reached. Type Error: An error occurred Severity info Copyright © 2010, Juniper Networks, Inc.
Page 514 Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. MPLS_OAM_TRACEROUTE_INTERRUPTED System Log Message fec-address: topology update interrupted traceroute Description A traceroute operation was interrupted by a topology change. Copyright © 2010, Juniper Networks, Inc.
Page 515 The Multiprotocol Label Switching (MPLS) Operation, Administration, and Maintenance (OAM) process (mplsoamd) therefore could not send a probe to the node. Type Error: An error occurred Severity info Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 517: Chapter 61 Nexthop System Log Messages
The limit on the number of logical interfaces for a next hop was reached for the indicated routing instance and bridging domain. Only a subset of new interfaces were added to the next hop. Type Event: This message reports an event, not an error Severity error Facility Copyright © 2010, Juniper Networks, Inc.
Page 519: Chapter 62 Nsd System Log Messages
One or more subcomponents could not sync their state on backup RE Description One or more subcomponents of the network security process (nsd) failed to synchronize their state when the nsd restarted on secondary mode. Copyright © 2010, Juniper Networks, Inc.
Page 521: Chapter 63 Nstraced System Log Messages
Subcomponent could not read configuration database Description When the USP trace process (nstraced) restarted, it could not read its configuration information from the configuration database. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 523: Chapter 64 Pfe System Log Messages
Could not create analyzer error-message table Description The logical interfaces (ifl) index failed to configure the analyzer because of an error. Type Error: An error occurred Severity error Facility PFE_ANALYZER_TASK_FAILED System Log Message Following task failed : error-message Copyright © 2010, Juniper Networks, Inc.
Page 524 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. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 525 The problematic firewall was automatically removed from the indicated interface. Type Error: An error occurred Severity error Facility LOG_PFE PFE_FW_PSF_DELETE_MISMATCH_ERR System Log Message Instance mismatch for type (installed-firewall-name != deleted-firewall-name) hardware label index family protocol-family Copyright © 2010, Juniper Networks, Inc.
Page 526 'syslog' action (A = Accept, D = Discard, R = Reject). Type Event: This message reports an event, not an error Severity info Facility PFE_FW_SYSLOG_IP6_ICMP System Log Message FW: interface-name action protocol-name source-address destination-address type type code error-code (count packets) Copyright © 2010, Juniper Networks, Inc.
Page 527 (DoS) attack. Examples of events that generate next-hop resolution requests include an attempt to forward a packet without an Address Resolution Protocol Copyright © 2010, Juniper Networks, Inc.
Page 528 Severity error Facility LOG_PFE PFE_SCCP_REG_RM_FAIL System Log Message Failed to register SCCP client to Resource Manager Description Failed to register the SCCP Resource Manager client. Type Error: An error occurred Severity error Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 529 System Log Message sflow configuration on hardware failed for ifl index = index Description The sflow configuration for the ifl index could not be programmed in the hardware Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 530 Error: An error occurred Severity error Facility LOG_PFE PFE_SIP_REG_HDL_FAIL System Log Message Failed to register object-name handle Description Failed to register the handler with the external module. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 533: Chapter 65 Pfed System Log Messages
Forwarding Engine process, which gathers and reports Packet Forwarding Engine statistics. PFED_NOTIFICATION_STATS_FAILED System Log Message Unable to retrieve notification statistics Description The Packet Forwarding Engine process (pfed) could not retrieve Packet Forwarding Engine notification statistics. Type Error: An error occurred Severity warning Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 535: Chapter 66 Pgcpd System Log Messages
Event: This message reports an event, not an error Severity notice Facility LOG_DAEMON PGCPD_SWITCH_OVER System Log Message switch over Description Switch over from active to backup Routing Engine Type Event: This message reports an event, not an error Severity warning Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 537: Chapter 67 Ping System Log Messages
The egress trip time measured for a probe exceeded the configured threshold during the indicated test conducted by the indicated user. Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 538 Facility LOG_DAEMON PING_RTT_JTR_THRESH_EXCEED System Log Message pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name Description The jitter for the round trip time exceeded the configured threshold during the indicated test conducted by the indicated user. Copyright © 2010, Juniper Networks, Inc.
Page 539 = test-owner, pingCtlTestName = test-name Description All probes were sent but the number of failed probes equaled or exceeded the pingCtlTrapTestFailureFilter threshold. Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 540 = test-owner, pingCtlTestName = test-name Description An unknown type of threshold event was reported during the indicated test conducted by the indicated user. Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 541: Chapter 68 Ppmd System Log Messages
(error-message) Description The periodic packet management process (ppmd) could not initialize the indicated protocol. Type Error: An error occurred Severity error Facility LOG_NEWS Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 542 Description The periodic packet management process (ppmd) could not write a message on a pipe for the indicated protocol. Type Error: An error occurred Severity error Facility LOG_NEWS Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 543: Chapter 69 Pppd System Log Messages
Unable to obtain hostname for outgoing CHAP message: error-message Description The Point-to-Point Protocol process (pppd) could not obtain the hostname needed to fill in the 'Name' field in an outgoing CHAP packet. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 544 (CHAP ID message-id) Description 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. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 545 PPPD_MEMORY_ALLOCATION_FAILURE System Log Message Unable to allocate memory for object object-name: error-message Description The Point-to-Point Protocol process (pppd) could not allocate memory from the heap for the indicated object. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 546 Unable to determine value for 'Password' in outgoing PAP packet Description 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. Copyright © 2010, Juniper Networks, Inc.
Page 547 The Point-to-Point Protocol process (pppd) could not add the indicated RADIUS server for the indicated access profile. Type Error: An error occurred Severity error Facility LOG_AUTH PPPD_RADIUS_ALLOC_PASSWD_FAILED System Log Message Unable to allocate RADIUS password of size size: error-message Copyright © 2010, Juniper Networks, Inc.
Page 548 Unknown response from RADIUS server: return-value Description The RADIUS authentication module for the Point-to-Point Protocol process (pppd) received a message from the RADIUS server that it could not process. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 549 The process of adding the required routing instance was still in progress when the message was logged. Action None required. Authentication with the indicated RADIUS server is automatically reattempted, and can succeed when the interface exists. Copyright © 2010, Juniper Networks, Inc.
Page 551: Chapter 70 Profiler System Log Messages
SIGHUP - re-reading configuration Description In response to a SIGHUP signal, the profiler service process (profilerd) read its configuration from the configuration database Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 553: Chapter 71 Rdd System Log Messages
(error-message) Description The redundant interfaces process (rdd) could not delete an interface device because an error occurred during the indicated call to the routing socket library. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 554 The attempt failed because the Adaptive Services (AS) Physical Interface Cards (PICs) that house the primary and secondary interfaces are not compatible. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 555 Event event-name changed state of interface interface-name from 'old-state' to 'new-state' Description The indicated event on the indicated redundant interface changed the interface state as indicated. Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 557: Chapter 72 Rmopd System Log Messages
System Log Message Unable to convert numeric address to string: error-message Description The remote Simple Network Management Protocol (SNMP) operations process (rmopd) could not convert a numeric host address to the corresponding hostname text string. Copyright © 2010, Juniper Networks, Inc.
Page 558 System Log Message No information for snmp-interface-index, message: error-message Description When a Simple Network Management Protocol (SNMP) client requests a remote operation, it can specify which interface to use as the source host address, identifying it Copyright © 2010, Juniper Networks, Inc.
Page 559 The indicated routing instance does not exist, so the Simple Network Management Protocol (SNMP) remote operations process (rmopd) could not retrieve information about it. Type Error: An error occurred Severity error Facility LOG_DAEMON RMOPD_TRACEROUTE_ERROR System Log Message Message: error-message Copyright © 2010, Juniper Networks, Inc.
Page 560 Junos 10.3 System Log Messages Reference Description The traceroute application reported the indicated error message to the Simple Network Management Protocol (SNMP) remote operations process (rmopd). Type Error: An error occurred Severity notice Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 561: Chapter 73 Rpd System Log Messages
Cause An internal software failure occurred. RPD_ACTIVE_TERMINATE System Log Message Exiting with active tasks: task-name Description After receiving multiple termination requests, the routing protocol process (rpd) exited without performing the indicated cleanup tasks. Copyright © 2010, Juniper Networks, Inc.
Page 562 Modify the configuration statement to use a valid value. RPD_AMT_CFG_LOC_ADDR_INVALID System Log Message An invalid local-address is configured Description An invalid local address was encountered while parsing AMT configuration. Type Event: This message reports an event, not an error Severity warning Copyright © 2010, Juniper Networks, Inc.
Page 563 Modify the configuration statement to use a valid value. RPD_AMT_RELAY_DISCOVERY System Log Message AMT relay discovery message from gateway destination-address port destination-port at time Description AMT relay discovery event. Type Event: This message reports an event, not an error Severity info Facility Copyright © 2010, Juniper Networks, Inc.
Page 564 Soft assertion failed executable-name[pid]: file "source-filename", line line-number: "message", daemon continued running Description 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 Copyright © 2010, Juniper Networks, Inc.
Page 565 Contact your technical support representative. RPD_BGP_CFG_ADDR_INVALID System Log Message Invalid argument address ip-address Description An invalid local or neighbor address was encountered while parsing BGP configuration. Type Event: This message reports an event, not an error Severity warning Copyright © 2010, Juniper Networks, Inc.
Page 566 The routing protocol process (rpd) failed to notify the dynamic configuration clients about its availability to process the dynamic configuration requests. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 567 Get session type for session client-session-id failed: error-code Description The routing protocol process (rpd) tried to get the session type from the session snapshot and failed. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 568 Severity error Facility LOG_DAEMON RPD_DYN_CFG_REGISTER_FAILED System Log Message Dynamic config registration failed: error-message Description The routing protocol process (rpd) tried to register with the dynamic configuration subsystem and failed. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 569 Failed to close session database: error-code Description The routing protocol process (rpd) tried to close the session database and failed. Type Error: An error occurred Severity error Facility LOG_DAEMON RPD_DYN_CFG_SDB_OPEN_FAILED System Log Message Failed to open session database: error-code Copyright © 2010, Juniper Networks, Inc.
Page 570 LOG_DAEMON Cause The communication path to the neighboring router was disrupted, a protocol error occurred, or the neighboring router was powered down. RPD_ESIS_ADJUP System Log Message ES-IS new adjacency-type adjacency to neighbor-nsap-netn on interface-name Copyright © 2010, Juniper Networks, Inc.
Page 571 Description 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. Copyright © 2010, Juniper Networks, Inc.
Page 572 System Log Message interface-name time Description Internet Group Management Protocol (IGMP) accounting for the indicated interface was disabled at the indicated time. Type Event: This message reports an event, not an error Severity info Copyright © 2010, Juniper Networks, Inc.
Page 573 The configuration request failed because the indicated configuration object contained a group that is out of range. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Modify configuration statement to use a valid value. Copyright © 2010, Juniper Networks, Inc.
Page 574 Unbind session id from existing interface. RPD_IGMP_DYN_CFG_INVALID_STMT System Log Message Invalid dynamic configuration statement: configuration-statement Description The indicated dynamic configuration statement was invalid. The dynamic configuration instantiation request was rejected. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 575 Event: This message reports an event, not an error Severity info Facility LOG_DAEMON RPD_IGMP_LEAVE System Log Message Listener source-address sent a leave to destination-address for group group-address source sender-address on interface interface-name at time Copyright © 2010, Juniper Networks, Inc.
Page 576 RPD_ISIS_ADJUP System Log Message IS-IS new Lisis-level adjacency to neighbor-system-ids on interface-name Description An IS-IS adjacency was established with the indicated neighboring router. The local router can now exchange information with it. Copyright © 2010, Juniper Networks, Inc.
Page 577 IS-IS Lisis-level LSP checksum error, interface interface-name, LSP id lspl, sequence sequence-number, checksum checksum, lifetime duration Description The indicated IS-IS informational link-state PDU (LSP) failed an internal checksum validity test, implying that it was corrupted. Type Error: An error occurred Severity warning Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 578 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. RPD_KRT_CCC_IFL_MODIFY System Log Message error-code, error-message Copyright © 2010, Juniper Networks, Inc.
Page 579 CHANGE for ifd interface-device-index address/prefix-length failed, error "error-message" Description The routing protocol process (rpd) sent a request to the kernel to change the state of the indicated interface. The request failed. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 580 (port, or trunk user-to-network interface [UNI], or trunk network-to-network interface [NNI]) was invalid. Type Error: An error occurred Severity notice Facility LOG_DAEMON RPD_KRT_IFD_CELL_RELAY_NO_MODE System Log Message No mode specified for interface device interface-name; defaulting to port mode Copyright © 2010, Juniper Networks, Inc.
Page 581 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. Type Error: An error occurred Severity notice Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 582 (count) exceeded the maximum allowed (maximum-value) -- truncating Description The number of next hops for the indicated route exceeded the indicated limit for a single route add operation. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 583 Routing socket message type message-type's version is not supported by kernel, expected rpd-version -- kernel upgrade required Description The routing protocol process (rpd) discovered that the kernel does not support the routing socket message types that it requires. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 584 (name and ID) in the indicated virtual private network (VPN) virtual circuit (VC), because the resulting number of labels would have exceeded the limit. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 585 The routing protocol process (rpd) determined that the Bidirectional Forwarding Detection (BFD) protocol session for the the indicated Layer 2 virtual private network (VPN) virtual circuit (VC) came up. Type Event: This message reports an event, not an error Severity notice Copyright © 2010, Juniper Networks, Inc.
Page 586 (FEC) terminated. Type Event: This message reports an event, not an error Severity notice Facility LOG_DAEMON RPD_LDP_BFD_DOWN_TRACEROUTE_FAIL System Log Message LDP BFD sessions for FEC fec-address going down due to traceroute failure Copyright © 2010, Juniper Networks, Inc.
Page 587 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. Type Event: This message reports an event, not an error Severity warning Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 588 The routing protocol process (rpd) determined that LSP ping returned error for the indicated forwarding equivalence class (FEC) of Label Distribution Protocol (LDP). Type Event: This message reports an event, not an error Severity notice Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 589 System Log Message operation operation failed: control channel logical-interface-index unknown Description 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. Copyright © 2010, Juniper Networks, Inc.
Page 590 Description The routing protocol process (rpd) could not perform the indicated operation for the peer with the indicated name and index, for the indicated reason. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 591 Severity error Facility LOG_DAEMON RPD_LMP_SEND System Log Message function-name: handling write exception (error-message, errno error-code) Description The routing protocol process (rpd) could not send a message to the Label Management Protocol (LMP) process (lmpd). Copyright © 2010, Juniper Networks, Inc.
Page 592 Type Error: An error occurred Severity error Facility LOG_DAEMON RPD_LMP_TE_LINK_INDEX System Log Message No more TE-link indexes Description No more traffic-engineering link indexes were available for allocation. Copyright © 2010, Juniper Networks, Inc.
Page 593 The system terminated this instance of rpd. Type Error: An error occurred Severity error Facility LOG_DAEMON Cause Another rpd is running. Action Use the 'show system process' command to verify that another rpd is running. Copyright © 2010, Juniper Networks, Inc.
Page 594 The routing protocol process (rpd) could not write a message on the write pipe to the Class Of Service process (cosd). Type Error: An error occurred Severity info Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 595 Description The dynamic configuration instantiation request was rejected because the request matched an existing dynamic configuration block that had a different session ID. Copyright © 2010, Juniper Networks, Inc.
Page 596 Connection to management peer process-name timed out waiting for input Description The connection between the routing protocol process (rpd) and the indicated management process (mgd) timed out before input arrived from the mgd process. Copyright © 2010, Juniper Networks, Inc.
Page 597 The Multicast Listener Discovery (MLD) accounting for the indicated interface was disabled at the indicated time. Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON RPD_MLD_ACCOUNTING_ON System Log Message interface-name time Copyright © 2010, Juniper Networks, Inc.
Page 598 Type Error: An error occurred Severity error Facility LOG_DAEMON Action Modify configuration statement to use a valid value. RPD_MLD_CFG_INVALID_VALUE System Log Message The object-name configuration object identifier field has an invalid value of value Copyright © 2010, Juniper Networks, Inc.
Page 599 Unbind session id from existing interface. RPD_MLD_DYN_CFG_INVALID_STMT System Log Message Invalid dynamic configuration statement: configuration-statement Description The indicated dynamic configuration statement was invalid. The dynamic configuration instantiation request was rejected. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 600 System Log Message Listener source-address sent a leave to destination-address for group group-address source sender-address on interface interface-name at time Description MLD leave event. Type Event: This message reports an event, not an error Severity info Copyright © 2010, Juniper Networks, Inc.
Page 601 There was a failure in stacking additional label to a nexthop which already has maximum number of labels allowed for the interface Type Error: An error occurred Severity error Facility LOG_DAEMON RPD_MPLS_LSP_AUTOBW_NOTICE System Log Message mpls LSP lsp-name Autobw already in progress, ignoring new trigger Copyright © 2010, Juniper Networks, Inc.
Page 602 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 Description The indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) switched from primary path to secondary path or vice versa. Copyright © 2010, Juniper Networks, Inc.
Page 603 Description The routing protocol process (rpd) could not read a message available on the read pipe from the MPLS Operation, Administration, and Maintenance process (mplsoamd). Type Error: An error occurred Severity info Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 604 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). Type Event: This message reports an event, not an error Severity notice Copyright © 2010, Juniper Networks, Inc.
Page 605 MPLS path pathname up on LSP lsp-name path bandwidth bandwidth bps Description The indicated Multiprotocol Label Switching (MPLS) path came up on the indicated label-switched path (LSP). Type Event: This message reports an event, not an error Severity warning Copyright © 2010, Juniper Networks, Inc.
Page 606 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. Type Event: This message reports an event, not an error Severity notice Copyright © 2010, Juniper Networks, Inc.
Page 607 Type Event: This message reports an event, not an error Severity notice Facility LOG_DAEMON RPD_MSDP_SRC_ACTIVE_UNDER_LIMIT System Log Message Number of MSDP source-active messages about originator no longer exceeded configured limit message Copyright © 2010, Juniper Networks, Inc.
Page 608 Ignored configured neighbors on point-to-point realm realm-name interface interface-name area area-idi Description 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. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 609 Event: This message reports an event, not an error Severity notice Facility LOG_DAEMON RPD_OSPF_NBRDOWN System Log Message 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) Copyright © 2010, Juniper Networks, Inc.
Page 610 Using size KB of memory, percentage-value percent of available Description The routing protocol process (rpd) is using the indicated amount and percentage of Routing Engine memory, which is considered excessive. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 611 Reissue the command and include the required argument. RPD_PARSE_CMD_DUPLICATE System Log Message executable-name: command-line option option is a duplicate Description The command line used to start the indicated process included the indicated duplicate option. The process did not start. Copyright © 2010, Juniper Networks, Inc.
Page 612 Failed to parse community string under policy-options: error-message Description The routing protocol process (rpd) encountered a non-catastrophic error in bgp community member string while parsing policy-options. Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 613 A conflict was detected while parsing the policy-options configuration hierarchy Type Event: This message reports an event, not an error Severity warning Facility RPD_PLCY_CFG_PREFIX_LEN_SHORT System Log Message prefix length prefix-length is too short for prefix route-prefix under policy-statement policy-name, ignoring excess host bits Copyright © 2010, Juniper Networks, Inc.
Page 614 Could not create entry for entry. Description The configuration request failed because the IPv6 routing advertisements failed to create the indicate configuration entry. Type Error: An error occurred Severity error Facility LOG_DAEMON Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 615 Failed to add dynamic configuration session id client-session-id to interface interface-name. Description The dynamic configuration instantiation request was rejected because it failed to associate the indicated session ID with the specified interface. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 616 The routing protocol process (rpd) did not enable router discovery on the interface. Type Error: An error occurred Severity warning Facility LOG_DAEMON Action Do not configure router discovery on the interface. Copyright © 2010, Juniper Networks, Inc.
Page 617 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. Type Event: This message reports an event, not an error Severity warning Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 618 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. Copyright © 2010, Juniper Networks, Inc.
Page 619 System Log Message RSVP bypass bypass-lsp-name for protecting interface interface-name came up Description The indicated RSVP link-protection bypass was established to protect the indicated interface. Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 620 System Log Message RSVP neighbor neighbor-address down on interface interface-name, reason Description The RSVP neighbor to the indicated address was terminated. Type Event: This message reports an event, not an error Severity warning Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 621 The object-name configuration object identifier field has an invalid value of value Description The configuration request failed because the indicated configuration object contained the indicated invalid value. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 622 Description The dynamic config request with a specific session id and routing-instance cannot be completed because a routing table where routes should be added was not found Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 623 Type Event: This message reports an event, not an error Severity warning Facility RPD_RT_PATH_LIMIT_BELOW System Log Message Number of paths (count) in table table-name is now less than the configured maximum (limit) Copyright © 2010, Juniper Networks, Inc.
Page 624 Type Event: This message reports an event, not an error Severity warning Facility LOG_DAEMON RPD_RT_PREFIX_LIMIT_REACHED System Log Message Number of prefixes (prefix-count) in table table-name status configured maximum (limit) Copyright © 2010, Juniper Networks, Inc.
Page 625 Type Error: An error occurred Severity error Facility LOG_DAEMON RPD_SCHED_CALLBACK_LONGRUNTIME System Log Message function-name: excessive runtime time during action of module Copyright © 2010, Juniper Networks, Inc.
Page 626 Description A task callback within the routing protocol process (rpd) ran uninterrupted for the indicated period of time, which is considered excessive. Type Event: This message reports an event, not an error Severity warning Copyright © 2010, Juniper Networks, Inc.
Page 627 Description The routing protocol process (rpd) tried again to connect to the indicated Simple Network Management Protocol (SNMP) master agent after a connection attempt failed. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 628 Simple Network Management Protocol (SNMP) master agent. Type Error: An error occurred Severity error Facility LOG_DAEMON RPD_START System Log Message Start executable-name[pid] version version built date Copyright © 2010, Juniper Networks, Inc.
Page 629 Description While a child process of the routing protocol process (rpd) was performing the indicated operation, it stopped in response to the indicated signal. Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 630 Assuming mastership Description The routing protocol process (rpd) became active when the Routing Engine on which it was running assumed mastership. Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 631 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. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 632 Some interfaces of the indicated vpls instance have not been configured under the sole site of the instance. Type Event: This message reports an event, not an error Severity warning Facility Action Configure all interfaces of the instace under its single site. Copyright © 2010, Juniper Networks, Inc.
Page 633: Chapter 74 Rt System Log Messages
Description A security session was created. Type Event: This message reports an event, not an error Severity info Facility LOG_PFE RT_FLOW_SESSION_DENY System Log Message session denied source-address/source-port->destination-address/destination-port service-name protocol-id(icmp-type) policy-name source-zone-name destination-zone-name Copyright © 2010, Juniper Networks, Inc.
Page 634 APN IE: name Description Displays the contents of the Access Point Name (APN) information element carried in the GPRS tunneling protocol (GTP) message. Type Event: This message reports an event, not an error Severity info Copyright © 2010, Juniper Networks, Inc.
Page 635 Displays the contents of the IPv4 End User Address information element carried in the GPRS tunneling protocol (GTP) message. The content includes the end user IP address. Type Event: This message reports an event, not an error Severity info Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 636 Description Displays the GPRS tunneling protocol (GTP) packet process result, providing information about whether the packet is passed or dropped. Type Event: This message reports an event, not an error Severity info Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 637 LOG_PFE RT_IPSEC_BAD_SPI System Log Message IPSec tunnel on int interface-name with tunnel ID 0xtunnel-id received a packet with a bad SPI. source-address->destination-address/length, type, SPI 0xindex, SEQ 0xsequence-number. Description Received IPSec packet with bad SPI Copyright © 2010, Juniper Networks, Inc.
Page 638 Failed to allocate memory for object-name Description Failed to allocate memory for the MGCP objects. Type Error: An error occurred Severity error Facility LOG_PFE RT_MGCP_REG_NAT_VEC_FAIL System Log Message Failed to add MGCP object-name to flow module Copyright © 2010, Juniper Networks, Inc.
Page 639 Description The Resource Manager has unregistered the MGCP Resource Manager client. Type Error: An error occurred Severity error Facility LOG_PFE RT_SCCP_CALL_LIMIT_EXCEED System Log Message Failed to create SCCP ALG call, call limit maximum-value exceeded Copyright © 2010, Juniper Networks, Inc.
Page 640 Failed to remove the SCCP ALG vector from the flow module. Type Error: An error occurred Severity error Facility LOG_PFE RT_SCCP_UNREG_RM_FAIL System Log Message Failed to unregister SCCP client from Resource Manager when the ALG was unregistered Copyright © 2010, Juniper Networks, Inc.
Page 641 Facility LOG_PFE RT_SCREEN_TCP System Log Message attack-name source: source-address:source-port, destination: destination-address:destination-port, zone name: source-zone-name, interface name: interface-name Description TCP attack category Type Event: This message reports an event, not an error Severity error Copyright © 2010, Juniper Networks, Inc.
Page 642 System Log Message ***SCTP configuration: message Description SCTP log info. Type Event: This message reports an event, not an error Severity info Facility RT_SCTP_PKT_INFO System Log Message ***SCTP (type message-type source-address/source-port -> destination-address/destination-port) message Copyright © 2010, Juniper Networks, Inc.
Page 643 Event: This message reports an event, not an error Severity info Facility RT_SIP_MEM_ALLOC_FAILED System Log Message Failed to allocate memory for object-name Description Failed to allocate memory from the memory pool. Type Error: An error occurred Severity error Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 645: Chapter 75 Rtlog System Log Messages
System Log Message source: source-address-source-port, destination: destination-address-destination-port, zone name: filter-name, interface name: interface-name Description Security LOG UTP fake TCP SYN flood attack. Type Event: This message reports an event, not an error Severity error Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 647: Chapter 76 Rtlogd System Log Messages
JUNOS JSR log daemon relays JSR logs from the dataplane to the system event daemon for logging. The JSR log daemon fails to read JSR logs for the indicated reason. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 649: Chapter 77 Rtperf System Log Messages
RTPERF_CPU_USAGE_OK System Log Message FPC fpc-slot PIC pic-slot CPU utilization returns to normal, current value=current-value Description PFE cpu usage okay Type Event: This message reports an event, not an error Severity info Facility LOG_PFE Copyright © 2010, Juniper Networks, Inc.
Page 651: Chapter 78 Saval System Log Messages
The MAC SA Validate system process (jsavald) experienced the indicated error with a routing socket. Type Error: An error occurred Severity info Facility LOG_DAEMON Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 653: Chapter 79 Sdxd System Log Messages
Extensible Exchange Protocol (BEEP), which it uses to connect to an SRC server. Type Error: An error occurred Severity error Facility LOG_DAEMON Cause An internal software failure might have occurred. SDXD_CHANNEL_START_FAIL System Log Message Notification channel could not be started (error-code): message Copyright © 2010, Juniper Networks, Inc.
Page 654 The Service Deployment System process (sdxd) called the indicated function in the event library. The function failed with the indicated error. Type Error: An error occurred Severity error Facility LOG_DAEMON Cause An internal software failure occurred. Copyright © 2010, Juniper Networks, Inc.
Page 655 SDXD_OUT_OF_MEMORY System Log Message Insufficient memory during operation Description The Service Deployment System (sdxd) attempted to allocate memory for an internal object during the indicated operation. The attempt failed. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 656 Type Error: An error occurred Severity error Facility LOG_DAEMON Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 657: Chapter 80 Smtpd System Log Messages
The smtp client process (smtpd) is unable to send mail payload. A gateway server must be configured. This server must allow relaying. Type Event: This message reports an event, not an error Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 659: Chapter 81 Snmp System Log Messages
System Log Message function-name operation failed for object-name: index1 index1 index2 index2 (error-message) Description An SNMP Get or GetNext request failed for the indicated object, which has the indicated indexes. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 660 Contact your technical support representative. SNMP_RTSLIB_FAILURE System Log Message function-name: reason: error-message Description A call to the indicated function in the routing socket library failed with the indicated error. Type Error: An error occurred Severity emergency Copyright © 2010, Juniper Networks, Inc.
Page 661 = test-owner, traceRouteCtlTestName = test-name Description The Simple Network Management Protocol (SNMP) remote operations process (rmopd) generated a tracerouteTestCompleted trap because the test completed and the full path to the target was determined. Copyright © 2010, Juniper Networks, Inc.
Page 662 The Simple Network Management Protocol (SNMP) remote operations process (rmopd) generated a tracerouteTestFailed trap because the test completed and the full path to the target was not determined. Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 663: Chapter 82 Snmpd System Log Messages
The indicated function failed because the Simple Network Management Protocol (SNMP) community making the access request did not have the required privileges. Type Error: An error occurred Severity notice Facility Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 664 Cause An administrator changed the Junos configuration for the process or for an interface. Cause The online/offline state changed for a PIC. This can also cause the address to become newly available or unavailable. Copyright © 2010, Juniper Networks, Inc.
Page 665 Contact your technical support representative. SNMPD_GROUP_ERROR System Log Message function-name: error in operation group: 'group-id' user 'username' model 'model' Description The indicated operation (creation, installation, or deletion) failed during configuration of the indicated group. Copyright © 2010, Juniper Networks, Inc.
Page 666 Contact your technical support representative. SNMPD_LIBJUNIPER_FAILURE System Log Message function-name: system_default_inaddr: error-message Description The indicated function from the Juniper Networks Simple Network Management Protocol (SNMP) library failed and returned the indicated error to the SNMP agent process (snmpd). Type Error: An error occurred...
Page 667 System Log Message function-name: operation: operation filename: error-message Description The indicated operation failed on the indicated remote monitoring (RMON) data file. Type Error: An error occurred Severity critical Facility LOG_DAEMON Cause An internal software failure occurred. Copyright © 2010, Juniper Networks, Inc.
Page 668 Action Contact your technical support representative. SNMPD_RTSLIB_ASYNC_EVENT System Log Message function-name: sequence mismatch (expected-value, received-value), resyncing Description A notification from the kernel to the Simple Network Management Protocol (SNMP) agent process (snmpd) was lost. Copyright © 2010, Juniper Networks, Inc.
Page 669 The Simple Network Management Protocol (SNMP) agent process (snmpd) could not generate a value for the self-monitoring object identifier (OID) of the indicated product. Type Error: An error occurred Severity error Facility LOG_DAEMON Cause An internal software failure occurred. Copyright © 2010, Juniper Networks, Inc.
Page 670 SNMP agent process (snmpd). Type Error: An error occurred Severity error Facility LOG_DAEMON Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 671 Description The Simple Network Management Protocol (SNMP) agent process (snmpd) generated a cold-start trap when the entire Routing Engine (including the snmpd process) initialized. Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 672 Event: This message reports an event, not an error Severity info Facility LOG_DAEMON Cause Possible causes include the following: (a) the system is not completely initialized, (b) a route does not exist, or (c) traps are being throttled. Copyright © 2010, Juniper Networks, Inc.
Page 673 The number of traps waiting for transmission exceeded the configured maximum, so the remaining traps were throttled. Type Event: This message reports an event, not an error Severity info Facility LOG_DAEMON SNMPD_TRAP_WARM_START System Log Message function-name: SNMP trap: warm start Copyright © 2010, Juniper Networks, Inc.
Page 674 The indicated operation (creation, installation, or deletion) failed during configuration of the indicated user. Type Error: An error occurred Severity error Facility LOG_DAEMON Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 675: Chapter 83 Spd System Log Messages
The adaptive services process (spd) did not receive a reply from the indicated interface on an Adaptive Services PIC for information requested in a Simple Network Management Protocol (SNMP) query. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 676 Aborting, unable to run in the background as a daemon: error-message Description The adaptive services process (spd) could not create a version of itself to run in the background as a daemon. Type Error: An error occurred Severity emergency Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 677 The adaptive services process (spd) uses an internal database to store information needed to reply to Simple Network Management Protocol (SNMP) queries. It could not allocate an entry in the database for the indicated service set. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 678 Error: An error occurred Severity error Facility LOG_DAEMON SPD_NOT_ROOT System Log Message Must be run as root Description The user who attempted to start the adaptive services process (spd) was not the root user. Copyright © 2010, Juniper Networks, Inc.
Page 679 System Log Message Unable to add service next hop: error-message (error-code) Description The adaptive services process (spd) could not add a service next hop for the indicated reason. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 680 Description The adaptive services process (spd) displayed the syntax statement for the 'spd' command because the command was invoked incorrectly. Type Event: This message reports an event, not an error Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 681: Chapter 84 Ssh System Log Messages
Contact your technical support representative. SSH_RELAY_USAGE System Log Message Usage: ssh-relay -s service-name Description The syntax statement for the 'ssh-relay' command was displayed because the command was invoked with one or more incorrect options, or without necessary options. Copyright © 2010, Juniper Networks, Inc.
Page 683: Chapter 85 Sshd System Log Messages
Specified number of login failures (limit) for user 'username' reached from 'remote-address' Description Several login attempts failed for the indicated username. Type Event: This message reports an event, not an error Severity notice Facility Copyright © 2010, Juniper Networks, Inc.
Page 686 Examine the messages that immediately follow this message in the system log for information about possible causes. TASK_LOCK_FLOCKED System Log Message Unable to obtain a lock on filename, is another copy of the process running? Copyright © 2010, Juniper Networks, Inc.
Page 687 An internal software failure occurred. TASK_OS_MEMHIGH System Log Message Using size KB of memory, percentage-value percent of available Description The process is using the indicated amount and percentage of Routing Engine memory, which is considered excessive. Copyright © 2010, Juniper Networks, Inc.
Page 688 Description Several submodules of this process ran uninterrupted for the indicated period of time, which is considered excessive. Type Event: This message reports an event, not an error Severity warning Facility Copyright © 2010, Juniper Networks, Inc.
Page 689 System Log Message reason: error-message Description A system call made by this process failed. Type Error: An error occurred Severity error Facility Cause It is possible that the kernel lacked the resources to fulfill the request. Copyright © 2010, Juniper Networks, Inc.
Page 690 This process failed to create the indicated child process. Type Error: An error occurred Severity error Facility TASK_TASK_GETWD System Log Message getwd: error-message Description The getwd() system call failed. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 691 This process tried to write to the file that records its process ID (PID), which serves to prevent multiple instances from running simultaneously. The attempt failed. Type Error: An error occurred Severity error Facility Copyright © 2010, Juniper Networks, Inc.
Page 692 This process could not write to the indicated trace file, and stopped attempting to do so. The next commit of the configuration database will reenable tracing. Type Event: This message reports an event, not an error Severity error Facility Copyright © 2010, Juniper Networks, Inc.
Page 693: Chapter 87 Tftpd System Log Messages
Error: An error occurred Severity error Facility TFTPD_CONNECT_ERR System Log Message connect: error-message Description Connection of a socket to an address failed due to a system error. Type Error: An error occurred Severity error Facility Copyright © 2010, Juniper Networks, Inc.
Page 694 TFTP process (tnp.tftpd). To service multiple clients simultaneously, tnp.tftpd calls the fork() system call to make a copy of itself for each request. The system call returned the indicated error. Type Error: An error occurred Severity error Facility Copyright © 2010, Juniper Networks, Inc.
Page 695 The system call failed. Type Error: An error occurred Severity error Facility TFTPD_RECV_ERR System Log Message recv: error-message Description The TFTP process (tnp.tftpd) could not receive data from the network. Copyright © 2010, Juniper Networks, Inc.
Page 696 The TFTP process (tnp.tftpd) issued the statfs() system call to obtain the status of the file system into which it needed to write a crash file. The system call failed with the indicated error. Type Error: An error occurred Severity error Facility Copyright © 2010, Juniper Networks, Inc.
Page 697: Chapter 88 Ui System Log Messages
An internal software failure occurred. Action Contact your technical support representative. UI_BOOTTIME_FAILED System Log Message Unable to fetch boot time: error-message Description The management process (mgd) could not retrieve the system boot time from the kernel. Copyright © 2010, Juniper Networks, Inc.
Page 698 The indicated user set a value for a configuration object, as indicated. For security, the actual value (which might be an authentication key or password, for example) is not recorded. Type Event: This message reports an event, not an error Copyright © 2010, Juniper Networks, Inc.
Page 699 The management process (mgd) invoked the exec() system call while creating a child processes to execute the indicated command on its behalf. The system call failed. Type Error: An error occurred Severity error Facility Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 700 Its attempt to create pipes for communication with the child process failed. Type Error: An error occurred Severity error Facility Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 701 System Log Message Invalid 'allow-deny' command authorization regular expression 'regular-expression': error-message Description An operation that attempted to set command or configuration authorization included the indicated regular expression. The operation failed because the expression syntax was invalid. Copyright © 2010, Juniper Networks, Inc.
Page 702 Event: This message reports an event, not an error Severity notice Facility UI_COMMIT_AT_FAILED System Log Message reason, scheduled commit cleared Description A 'commit at' operation did not complete, for the indicated reason. Type Error: An error occurred Severity error Copyright © 2010, Juniper Networks, Inc.
Page 703 Facility Cause When the commit operation began, the user who created the new container object had not populated it and was in configuration mode but not at the top level of the hierarchy. Copyright © 2010, Juniper Networks, Inc.
Page 704 The configuration might be in an indeterminate state. Type Error: An error occurred Severity error Facility LOG_AUTH Cause The cause of the problem might be recorded in messages that precede this message in the system log. Copyright © 2010, Juniper Networks, Inc.
Page 705 Description The management process (mgd) did not accept an incoming connection request. Type Error: An error occurred Severity error Facility LOG_AUTH Cause An internal software failure occurred. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 706 The management process (mgd) uses sockets to communicate with other Junos OS processes running on the routing platform. It could not allocate a socket. Type Error: An error occurred Severity error Facility LOG_AUTH Cause System resources are exhausted. Action Contact your technical support representative. Copyright © 2010, Juniper Networks, Inc.
Page 707 The management process (mgd) could not increase the configuration database to the indicated size. Type Error: An error occurred Severity error Facility Cause The hard disk is defective or is not installed in the routing platform. Action Repair or replace the hard disk. Copyright © 2010, Juniper Networks, Inc.
Page 708 Database header major version number mismatch for file 'filename': expecting expected-value, got received-value Description For compatibility, the version number recorded in the header of the configuration database must match the version of JUNOS software running on the routing platform. The Copyright © 2010, Juniper Networks, Inc.
Page 709 The database file is corrupted. Action Contact your technical support representative. UI_DBASE_MISMATCH_SEQUENCE System Log Message Database header sequence numbers mismatch for file 'filename'. If a package has just been added or deleted, please verify and commit the configuration. Copyright © 2010, Juniper Networks, Inc.
Page 710 Contact your technical support representative. UI_DBASE_OPEN_FAILED System Log Message Database open failed for file 'filename': reason Description The management process (mgd) could not open the indicated configuration database file. Type Error: An error occurred Severity error Facility Copyright © 2010, Juniper Networks, Inc.
Page 711 The management process (mgd) began to rebuild the configuration database file or its schema because that object was not current. The operation will complete shortly. Type Event: This message reports an event, not an error Severity alert Facility Copyright © 2010, Juniper Networks, Inc.
Page 712 Committing factory default configuration because CONFIG button was pressed and held Description The management process (mgd) began a commit operation to activate the factory default configuration, because the CONFIG button on the chassis was pressed and held for 15 seconds or more. Copyright © 2010, Juniper Networks, Inc.
Page 713 UI_INVALID_REMOTE_PERMISSION System Log Message invalid permissions from authorization server: permission-name Description RADIUS and TACACS+ authorization servers use Juniper Networks vendor-specific attributes (VSAs) to specify user permissions. A VSA included the indicated permission name, which is invalid. Type Error: An error occurred...
Page 714 System Log Message User 'username' login, class 'class-name' local-peer[pid], ssh-connection 'ssh-connection', client-mode 'client-mode' Description The indicated user started a JUNOS CLI session. Type Event: This message reports an event, not an error Severity info Copyright © 2010, Juniper Networks, Inc.
Page 715 The management process (mgd) could not create or write to the indicated file, which was the intended location for the message of the day (MOTD) configured at the [edit system login announcement] hierarchy level. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 716 The management process (mgd) uses the read() system call to access data sent by other JUNOS processes running on the routing platform (referred to as its peers). The system call failed for the indicated process. Type Error: An error occurred Severity error Facility Copyright © 2010, Juniper Networks, Inc.
Page 717 System Log Message User 'username' restarting daemon 'process-name'description Description The indicated software process restarted as requested by the indicated user. Type Event: This message reports an event, not an error Severity warning Facility LOG_AUTH Copyright © 2010, Juniper Networks, Inc.
Page 718 The JUNOS user interface schema file records all CLI commands and configuration statements available in the JUNOS software. Schema sequence numbers serve as a checksum of the configuration data schema and ensure that the software used to access Copyright © 2010, Juniper Networks, Inc.
Page 719 Error: An error occurred Severity notice Facility LOG_AUTH UI_VERSION_FAILED System Log Message Unable to fetch system version: error-message Description The management process (mgd) could not retrieve version information from the kernel. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 720 Re-establishing connection to peer 'peer-name' Description The management process (mgd) reconnected to the indicated JUNOS process running on the routing platform. Type Event: This message reports an event, not an error Severity notice Facility Copyright © 2010, Juniper Networks, Inc.
Page 721: Chapter 89 Utmd System Log Messages
: error-message Description The example process (utmd) encoutered an error while calling a function or from a callback of the ssamlib library. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 723: Chapter 90 Vccpd System Log Messages
Type Error: An error occurred Severity error Facility LOG_DAEMON Cause The kernel version is older than the VCCPD version. Action Upgrade the kernel package. Copyright © 2010, Juniper Networks, Inc.
Page 724 System Log Message LSP checksum error, interface interface-name, LSP id lspl, sequence sequence-number, checksum checksum, lifetime duration Description The indicated vccpd link-state PDU (LSP) failed an internal checksum validity test, implying that it was corrupted. Copyright © 2010, Juniper Networks, Inc.
Page 725 Description A system call made by this process failed. Type Error: An error occurred Severity error Facility LOG_DAEMON Cause It is possible that the kernel lacked the resources to fulfill the request. Copyright © 2010, Juniper Networks, Inc.
Page 727: Chapter 91 Vrrpd System Log Messages
RFC 2338, Virtual Router Redundancy Protocol. The message 'authentication-type-mismatch' means that the packet specifies an authentication type different from the type used by the interface that received the packet. The message Copyright © 2010, Juniper Networks, Inc.
Page 728 For VRRP with IPv6, the list is defined by the 'virtual-inet6-address [ <addresses> ]' statement at the [edit interfaces <interface-name> unit <logical-unit-number> family inet6 address <address> vrrp-inet6-group <group-number>] hierarchy level. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 729 <group-number>] hierarchy level. For VRRP with IPv6, the list is defined by the 'virtual-inet6-address [ <addresses> ]' statement at the [edit interfaces <interface-name> unit <logical-unit-number> family inet6 address <address> vrrp-inet6-group <group-number>] hierarchy level. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 731: Chapter 92 Vsysd System Log Messages
System Log Message Unable to find root virtual system Description The virtual system process (vsysd) did not initialize, because it could not find the root virtual system. Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 733: Chapter 93 Web System Log Messages
The checklogin process halted a login attempt because it took longer than the maximum processing time allowed. Type Error: An error occurred Severity error Facility LOG_AUTH WEB_CERT_FILE_NOT_FOUND System Log Message Could not find certificate file 'filename', disabling HTTPS Copyright © 2010, Juniper Networks, Inc.
Page 734 LOG_DAEMON WEB_COULDNT_START_HTTPD System Log Message Could not fork httpd process! Description The Web management gatekeeper process (httpd-gk) could not start the web management process (httpd). Type Error: An error occurred Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 735 Error: An error occurred Severity error Facility LOG_DAEMON WEB_MGD_CONNECT_ERROR System Log Message Could not connect to mgd management socket Description The web management process could not connect to the MGD management socket. Type Error: An error occurred Copyright © 2010, Juniper Networks, Inc.
Page 736 The Web management gatekeeper process (httpd-gk) attempted to lock the indicated file, which records its process ID (PID). The file serves to prevent multiple instances of httpd-gk from running simultaneously. The attempt failed for the indicated reason. Copyright © 2010, Juniper Networks, Inc.
Page 737 Event: This message reports an event, not an error Severity notice Facility LOG_DAEMON WEB_WEBAUTH_AUTH_OK System Log Message Web-authentication of user username with fwauthd successful Description The web-authentication authentication process was able to authenticate the indicated user successfully Copyright © 2010, Juniper Networks, Inc.
Page 738 Unable to connect to fwauthd on socket file-descriptor: error-message Description The web-authentication authentication process could not connect to fwauthd daemon on the indicated socket Type Event: This message reports an event, not an error Severity error Facility LOG_DAEMON Copyright © 2010, Juniper Networks, Inc.
Page 739: Chapter 94 Webfilter System Log Messages
An error is encountered in a periodical task or during a server update Action No recommended action WEBFILTER_REQUEST_NOT_CHECKED System Log Message Error encountered: server down, failed to check request error-message Description Web-filtering failed to check a web request, Copyright © 2010, Juniper Networks, Inc.
Page 740 WebFilter: An error is received from server name (0xstatus-code): error-message Description An error status is received from web server Type Event: This message reports an event, not an error Severity notice Facility LOG_FIREWALL Cause An error status is received from web server Copyright © 2010, Juniper Networks, Inc.
Page 741 REASON="error-message" PROFILE="profile-name" URL=object-name OBJ=pathname Description A web request is permitted Type Event: This message reports an event, not an error Severity info Facility LOG_FIREWALL Cause A web request is permitted Action No recommended action Copyright © 2010, Juniper Networks, Inc.
Page 745: Index
{ }, in configuration statements.........lxi CHASSISD system log messages........133 comments, in configuration statements......lxi regular expression operator Common Criteria system logging............23 system logging..............7 | (pipe), in syntax descriptions...........lxi conflict-log (system logging facility).........9 ACCT system log messages..........55 Copyright © 2010, Juniper Networks, Inc.
Page 746 JSRPD system log messages..........317 default for remote machine........14 Junos-FIPS for local machine..............9 system logging..............7 mapping of codes to names........19 facility-override statement system logging kernel (system logging facility)..........9 usage guidelines.............13 option to facility-override statement......15 FCD system log messages..........265 Copyright © 2010, Juniper Networks, Inc.
Page 747 SPD system log messages..........611 other-routing-engine option to host statement SSH system log messages..........617 usage guidelines SSHD system log messages..........619 routing matrix............32 structured-data statement single-chassis system...........12 usage guidelines...............11 Copyright © 2010, Juniper Networks, Inc.
Page 748 TASK system log messages..........621 technical support contacting JTAC..............lxii TFTPD system log messages..........629 time-format statement usage guidelines..............21 TX Matrix platform system logging..............26 UI system log messages............633 user (system logging facility)..........9 option to facility-override statement......15 Copyright © 2010, Juniper Networks, Inc.

This manual is also suitable for:

Junos os 10.3 - software

Juniper JUNOS OS 10.3 - SYSTEM LOG MESSAGES REFERENCE 7-12-2010 Reference Manual

Chapter 1 Configuring System Log Messages

Chapter 2 ACCT System Log Messages

Chapter 3 ALARMD System Log Messages

Chapter 4 ANCPD System Log Messages

Chapter 5 ANTISPAM System Log Messages

Chapter 6 APPIDD System Log Messages

Chapter 7 APPTRACK System Log Messages

Chapter 8 APPPXY System Log Messages

Chapter 9 ASP System Log Messages

Chapter 10 AUDITD System Log Messages

Chapter 11 AUTHD System Log Messages

Chapter 12 AUTOCONFD System Log Messages

Chapter 13 AUTOD System Log Messages

Chapter 14 AV System Log Messages

Chapter 15 BFDD System Log Messages

Chapter 16 BOOTPD System Log Messages

Chapter 17 CFMD System Log Messages

Chapter 18 CHASSISD System Log Messages

Chapter 19 CONTENT System Log Messages

Chapter 20 COSD System Log Messages

Chapter 21 DCD System Log Messages

Chapter 22 DFCD System Log Messages

Chapter 23 DFWD System Log Messages

Chapter 24 DHCPD System Log Messages

Chapter 25 DYNAMIC System Log Messages

Chapter 26 ESWD System Log Messages

Chapter 27 EVENTD System Log Messages

Chapter 28 FCD System Log Messages

Chapter 29 FLOW System Log Messages

Chapter 30 FPCLOGIN System Log Messages

Chapter 31 FSAD System Log Messages

Chapter 32 FUD System Log Messages

Chapter 33 FWAUTH System Log Messages

Chapter 34 GPRSD System Log Messages

Chapter 35 HNCACHED System Log Messages

Chapter 36 ICCPD System Log Messages

Chapter 37 IDP System Log Messages

Chapter 38 JADE System Log Messages

Chapter 39 JCS System Log Messages

Chapter 40 JDIAMETERD System Log Messages

Chapter 41 JPTSPD System Log Messages

Chapter 42 JSRPD System Log Messages

Chapter 43 KMD System Log Messages

Chapter 44 L2ALD System Log Messages

Chapter 45 L2CPD System Log Messages

Chapter 46 L2TPD System Log Messages

Chapter 47 LACPD System Log Messages

Chapter 48 LFMD System Log Messages

Chapter 49 LIBESPTASK System Log Messages

Chapter 50 LIBJNX System Log Messages

Chapter 51 LIBJSNMP System Log Messages

Chapter 52 LIBMSPRPC System Log Messages

Chapter 53 LICENSE System Log Messages

Chapter 54 LLDPD System Log Messages

Chapter 55 LOGIN System Log Messages

Chapter 56 LPDFD System Log Messages

Chapter 57 LRMUX System Log Messages

Chapter 58 MCSNOOPD System Log Messages

Chapter 59 MIB2D System Log Messages

Chapter 60 MPLS_OAM System Log Messages

Chapter 61 NEXTHOP System Log Messages

Chapter 62 NSD System Log Messages

Chapter 63 NSTRACED System Log Messages

Chapter 64 PFE System Log Messages

Chapter 65 PFED System Log Messages

Chapter 66 PGCPD System Log Messages

Chapter 67 PING System Log Messages

Chapter 68 PPMD System Log Messages

Chapter 69 PPPD System Log Messages

Chapter 70 PROFILER System Log Messages

Chapter 71 RDD System Log Messages

Chapter 72 RMOPD System Log Messages

Chapter 73 RPD System Log Messages

Chapter 74 RT System Log Messages

Chapter 75 RTLOG System Log Messages

Chapter 76 RTLOGD System Log Messages

Chapter 77 RTPERF System Log Messages

Chapter 78 SAVAL System Log Messages

Chapter 79 SDXD System Log Messages