Juniper Networks JUNOS Software

System Log Messages Reference

Release 10.1

Juniper Networks, Inc.

1194 North Mathilda Avenue Sunnyvale, California 94089 USA 408-745-2000

www.juniper.net
Published: 2010-01-10

This product includes the Envoy SNMP Engine, developed by Epilogue Technology, an Integrated Systems Company. Copyright 1986-1997, Epilogue Technology Corporation. All rights reserved. This program and its documentation were developed at private expense, and no part of them is in the public domain. This product includes memory allocation software developed by Mark Moraes, copyright 1988, 1989, 1993, University of Toronto. This product includes FreeBSD software developed by the University of California, Berkeley, and its contributors. All of the documentation and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by the Regents of the University of California. Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994. The Regents of the University of California. All rights reserved. GateD software copyright 1995, the Regents of the University. All rights reserved. Gate Daemon was originated and developed through release 3.0 by Cornell University and its collaborators. Gated is based on Kirtons EGP, UC Berkeleys routing daemon (routed), and DCNs HELLO routing protocol. Development of Gated has been supported in part by the National Science Foundation. Portions of the GateD software copyright 1988, Regents of the University of California. All rights reserved. Portions of the GateD software copyright 1991, D. L. S. Associates. This product includes software developed by Maker Communications, Inc., copyright 1996, 1997, Maker Communications, Inc. Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, ScreenOS, and Steel-Belted Radius are registered trademarks of Juniper Networks, Inc. in the United States and other countries. JUNOSe is a trademark of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. 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.

JUNOS Software System Log Messages Reference Release 10.1 Copyright 2010, Juniper Networks, Inc. All rights reserved. Printed in USA. Writing: Paka Sheryll Marion Sampson Editing: Nancy Kurahashi Cover Design: Edmonds Design Revision History January 2010 R1 JUNOS 10.1 The information in this document is current as of the date listed in the revision history. YEAR 2000 NOTICE Juniper Networks hardware and software products are Year 2000 compliant. The JUNOS Software has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.

ii

END USER LICENSE AGREEMENT

READ THIS END USER LICENSE AGREEMENT (AGREEMENT) BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE. BY DOWNLOADING, INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS CONTAINED HEREIN, YOU (AS CUSTOMER OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO BIND THE CUSTOMER) CONSENT TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS. 1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customers principal office is located in the Americas) or Juniper Networks (Cayman) Limited (if the Customers 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 license(s) for use of the Software (Customer) (collectively, the Parties). 2. The Software. In this Agreement, Software means the program modules and features of the Juniper or Juniper-supplied software, for which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by Juniper in equipment which Customer purchased from Juniper or an authorized Juniper reseller. Software also includes updates, upgrades and new releases of such software. Embedded Software means Software which Juniper has embedded in or loaded onto the Juniper equipment and any updates, upgrades, additions or replacements which are subsequently embedded in or loaded onto the equipment. 3. License Grant. Subject to payment of the applicable fees and the limitations and restrictions set forth herein, Juniper grants to Customer a non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the following use restrictions: a. Customer shall use Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by Customer from Juniper or an authorized Juniper reseller. b. Customer shall use the Software on a single hardware chassis having a single processing unit, or as many chassis or processing units for which Customer has paid the applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey Access Client software only, Customer shall use such Software on a single computer containing a single physical random access memory space and containing any number of processors. Use of the Steel-Belted Radius or IMS AAA software on multiple computers or virtual machines (e.g., Solaris zones) requires multiple licenses, regardless of whether such computers or virtualizations are physically contained on a single chassis. c. Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may specify limits to Customers use of the Software. Such limits may restrict use to a maximum number of seats, registered endpoints, concurrent users, sessions, calls, connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of separate licenses to use particular features, functionalities, services, applications, operations, or capabilities, or provide throughput, performance, configuration, bandwidth, interface, processing, temporal, or geographical limits. In addition, such limits may restrict the use of the Software to managing certain kinds of networks or require the Software to be used only in conjunction with other specific Software. Customers use of the Software shall be subject to all such limitations and purchase of all applicable licenses. d. For any trial copy of the Software, Customers right to use the Software expires 30 days after download, installation or use of the Software. Customer may operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer may not extend or create an additional trial period by re-installing the Software after the 30-day trial period. e. The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customers enterprise network. Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the Steel-Belted Radius software to support any commercial network access services. The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase the applicable license(s) for the Software from Juniper or an authorized Juniper reseller. 4. Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees not to and shall not: (a) modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized copies of the Software (except as necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the Software, in any form, to any third party; (d) remove any proprietary notices, labels, or marks on or in any copy of the Software or any product in which the Software is embedded; (e) distribute any copy of the Software to any third party, including as may be embedded in Juniper equipment sold in the secondhand market; (f) use any locked or key-restricted feature, function, service, application, operation, or capability without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even if such feature, function, service, application, operation, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper to any third party; (h) use the Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i) use Embedded Software on non-Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that the Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking of the Software to any third party without the prior written consent of Juniper; or (l) use the Software in any manner other than as expressly provided herein. 5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper, Customer shall furnish such records to Juniper and certify its compliance with this Agreement.

iii

6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper. As such, Customer shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence, which at a minimum includes restricting access to the Software to Customer employees and contractors having a need to use the Software for Customers internal business purposes. 7. Ownership. Juniper and Junipers licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to the Software, associated documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance of any right, title, or interest in the Software or associated documentation, or a sale of the Software, associated documentation, or copies of the Software. 8. Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall be as set forth in the warranty statement that accompanies the Software (the Warranty Statement). Nothing in this Agreement shall give rise to any obligation to support the Software. Support services may be purchased separately. Any such support shall be governed by a separate, written support services agreement. TO THE MAXIMUM EXTENT PERMITTED BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA, OR COSTS OR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, OR FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT, THE SOFTWARE, OR ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. IN NO EVENT SHALL JUNIPER BE LIABLE FOR DAMAGES ARISING FROM UNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY STATEMENT TO THE EXTENT PERMITTED BY LAW, JUNIPER DISCLAIMS ANY AND ALL WARRANTIES IN AND TO THE SOFTWARE (WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE), INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES JUNIPER WARRANT THAT THE SOFTWARE, OR ANY EQUIPMENT OR NETWORK RUNNING THE SOFTWARE, WILL OPERATE WITHOUT ERROR OR INTERRUPTION, OR WILL BE FREE OF VULNERABILITY TO INTRUSION OR ATTACK. In no event shall Junipers or its suppliers or licensors liability to Customer, whether in contract, tort (including negligence), breach of warranty, or otherwise, exceed the price paid by Customer for the Software that gave rise to the claim, or if the Software is embedded in another Juniper product, the price paid by Customer for such other product. Customer acknowledges and agrees that Juniper has set its prices and entered into this Agreement in reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same reflect an allocation of risk between the Parties (including the risk that a contract remedy may fail of its essential purpose and cause consequential loss), and that the same form an essential basis of the bargain between the Parties. 9. Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination of the license granted herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software and related documentation in Customers possession or control. 10. Taxes. All license fees payable under this agreement are exclusive of tax. Customer shall be responsible for paying Taxes arising from the purchase of the license, or importation or use of the Software. If applicable, valid exemption documentation for each taxing jurisdiction shall be provided to Juniper prior to invoicing, and Customer shall promptly notify Juniper if their exemption is revoked or modified. All payments made by Customer shall be net of any applicable withholding tax. Customer will provide reasonable assistance to Juniper in connection with such withholding taxes by promptly: providing Juniper with valid tax receipts and other required documentation showing Customers payment of any withholding taxes; completing appropriate applications that would reduce the amount of withholding tax to be paid; and notifying and assisting Juniper in any audit or tax proceeding related to transactions hereunder. Customer shall comply with all applicable tax laws and regulations, and Customer will promptly pay or reimburse Juniper for all costs and damages related to any liability incurred by Juniper as a result of Customers non-compliance or delay with its responsibilities herein. Customers obligations under this Section shall survive termination or expiration of this Agreement. 11. Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any applicable foreign agency or authority, and not to export or re-export the Software or any direct product thereof in violation of any such restrictions, laws or regulations, or without all necessary approvals. Customer shall be liable for any such violations. The version of the Software supplied to Customer may contain encryption or other capabilities restricting Customers ability to export the Software without an export license. 12. Commercial Computer Software. The Software is commercial computer software and is provided with restricted rights. Use, duplication, or disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS 227.7201 through 227.7202-4, FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable. 13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer with the interface information needed to achieve interoperability between the Software and another independently created program, on payment of applicable fee, if any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use such information in compliance with any applicable terms and conditions upon which Juniper makes such information available. 14. Third Party Software. Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniper whose products or technology are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement, and such licensor or vendor shall have the right to enforce this Agreement in its own name as if it were Juniper. In addition, certain third party software may be provided with the Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the extent portions of the Software are distributed under and subject to open source licenses obligating Juniper to make the source code for such portions publicly available (such as the GNU General Public License (GPL) or the GNU Library General Public License (LGPL)), Juniper will make such source code portions (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 94089, ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and a copy of the LGPL at http://www.gnu.org/licenses/lgpl.html. 15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws principles. The provisions of the U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes arising under this Agreement, the Parties hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and federal courts within Santa Clara County, California. This Agreement constitutes the entire and sole agreement between Juniper and the Customer with respect to the Software, and supersedes all prior and contemporaneous

iv

agreements relating to the Software, whether oral or written (including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained herein. No modification to this Agreement nor any waiver of any rights hereunder shall be effective unless expressly assented to in writing by the party to be charged. If any portion of this Agreement is held invalid, the Parties agree that such invalidity shall not affect the validity of the remainder of this Agreement. This Agreement and associated documentation has been written in the English language, and the Parties agree that the English version will govern. (For Canada: Les parties aux prsents confirment leur volont que cette convention de mme que tous les documents y compris tout avis qui s'y rattach, soient redigs en langue anglaise. (Translation: The parties confirm that this Agreement and all related documentation is and will be in the English language)).

vi

Abbreviated Table of Contents

About This Guide lvii

Part 1
Chapter 1

Overview
Configuring System Log Messages 3

Part 2
Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Chapter 9 Chapter 10 Chapter 11 Chapter 12 Chapter 13 Chapter 14 Chapter 15 Chapter 16 Chapter 17 Chapter 18 Chapter 19 Chapter 20 Chapter 21 Chapter 22 Chapter 23 Chapter 24 Chapter 25 Chapter 26 Chapter 27 Chapter 28 Chapter 29 Chapter 30

System Log Messages

ACCT System Log Messages ALARMD System Log Messages ANCPD System Log Messages ANTISPAM System Log Messages APPIDD System Log Messages APPPXY System Log Messages ASP System Log Messages AUDITD System Log Messages AUTHD System Log Messages AUTOCONFD System Log Messages AUTOD System Log Messages AV System Log Messages BFDD System Log Messages BOOTPD System Log Messages CFMD System Log Messages CHASSISD System Log Messages CONNECTION System Log Messages CONTENT System Log Messages COSD System Log Messages DCD System Log Messages DFCD System Log Messages DFWD System Log Messages DHCPD System Log Messages DYNAMIC System Log Messages ESWD System Log Messages EVENTD System Log Messages FCD System Log Messages FLOW System Log Messages FPCLOGIN System Log Messages 57 61 63 65 67 69 71 101 105 107 109 111 119 121 127 131 213 215 217 231 237 241 243 247 253 261 269 271 273

Abbreviated Table of Contents

vii

JUNOS 10.1 System Log Messages Reference

Chapter 31 Chapter 32 Chapter 33 Chapter 34 Chapter 35 Chapter 36 Chapter 37 Chapter 38 Chapter 39 Chapter 40 Chapter 41 Chapter 42 Chapter 43 Chapter 44 Chapter 45 Chapter 46 Chapter 47 Chapter 48 Chapter 49 Chapter 50 Chapter 51 Chapter 52 Chapter 53 Chapter 54 Chapter 55 Chapter 56 Chapter 57 Chapter 58 Chapter 59 Chapter 60 Chapter 61 Chapter 62 Chapter 63 Chapter 64 Chapter 65 Chapter 66 Chapter 67 Chapter 68 Chapter 69 Chapter 70 Chapter 71 Chapter 72 Chapter 73 Chapter 74

FSAD System Log Messages FUD System Log Messages FWAUTH System Log Messages GPRSD System Log Messages HNCACHED System Log Messages ICCPD System Log Messages IDP System Log Messages JADE System Log Messages JCS System Log Messages JDIAMETERD System Log Messages JSRPD System Log Messages KMD System Log Messages L2ALD System Log Messages L2CPD System Log Messages L2TPD System Log Messages LACPD System Log Messages LFMD System Log Messages LIBESPTASK System Log Messages LIBJNX System Log Messages LIBJSNMP System Log Messages LIBMSPRPC System Log Messages LICENSE System Log Messages LLDPD System Log Messages LOGIN System Log Messages LPDFD System Log Messages LRMUX System Log Messages MCSNOOPD System Log Messages MIB2D System Log Messages MPLS_OAM System Log Messages NEXTHOP System Log Messages NSD System Log Messages NSTRACED System Log Messages PFE System Log Messages PFED System Log Messages PGCPD System Log Messages PING System Log Messages PPMD System Log Messages PPPD System Log Messages PROFILER System Log Messages RDD System Log Messages RMOPD System Log Messages RPD System Log Messages RT System Log Messages RTLOG System Log Messages

275 285 291 295 297 299 301 307 309 315 317 321 347 357 367 399 401 403 405 413 419 423 427 429 435 437 439 441 449 453 455 457 459 471 473 475 479 481 489 491 495 499 567 589

viii

Abbreviated Table of Contents

Chapter 75 Chapter 76 Chapter 77 Chapter 78 Chapter 79 Chapter 80 Chapter 81 Chapter 82 Chapter 83 Chapter 84 Chapter 85 Chapter 86 Chapter 87 Chapter 88 Chapter 89 Chapter 90 Chapter 91

RTLOGD System Log Messages RTPERF System Log Messages SAVAL System Log Messages SDXD System Log Messages SMTPD System Log Messages SNMP System Log Messages SNMPD System Log Messages SPD System Log Messages TASK System Log Messages TFTPD System Log Messages UI System Log Messages UTMD System Log Messages VCCPD System Log Messages VRRPD System Log Messages VSYSD System Log Messages WEB System Log Messages WEBFILTER System Log Messages

591 593 595 597 601 603 607 619 625 635 641 667 669 673 677 679 685

Part 3

Index
Index 691

Abbreviated Table of Contents

ix

JUNOS 10.1 System Log Messages Reference

Table of Contents
About This Guide lvii JUNOS Documentation and Release Notes ....................................................lvii Objectives ....................................................................................................lviii Audience ......................................................................................................lviii Supported Platforms ....................................................................................lviii Using the Examples in This Manual ...............................................................lix Merging a Full Example ...........................................................................lix Merging a Snippet ....................................................................................lx Documentation Conventions ..........................................................................lx Documentation Feedback .............................................................................lxii Requesting Technical Support .......................................................................lxii Self-Help Online Tools and Resources ...................................................lxiii Opening a Case with JTAC .....................................................................lxiii

Part 1
Chapter 1

Overview
Configuring System Log Messages 3

System Logging Configuration Statements ......................................................4 Minimum and Default System Logging Configuration ......................................4 Minimum System Logging Configuration ..................................................5 Default System Log Settings ......................................................................5 Configuring System Logging for a Single-Chassis System ................................7 Specifying the Facility and Severity of Messages to Include in the Log .....................................................................................................9 Directing Messages to a Log File .............................................................11 Logging Messages in Structured-Data Format ...................................12 Directing Messages to a User Terminal ...................................................12 Directing Messages to the Console ..........................................................13 Directing Messages to a Remote Machine or the Other Routing Engine ..............................................................................................13 Specifying an Alternative Source Address for System Log Messages ...................................................................................14 Changing the Alternative Facility Name for Remote Messages .........14 Examples: Assigning an Alternative Facility ......................................16 Adding a Text String to System Log Messages ..................................17 Adding a String .................................................................................17 Configuring the Size and Number of Log Files ........................................18 Including Priority Information in System Log Messages ..........................19

Table of Contents

xi

JUNOS 10.1 System Log Messages Reference

Including the Year or Millisecond in Timestamps ....................................22 Using Regular Expressions to Refine the Set of Logged Messages ...........23 Disabling Logging of a Facility ................................................................25 Examples: Configuring System Logging ..................................................25 Configuring System Logging for a Routing Matrix ..........................................28 Configuring Message Forwarding in the Routing Matrix ..........................29 Messages Logged When Local and Forwarded Severity Level Are the Same .........................................................................................30 Messages Logged When Local Severity Level Is Lower ......................31 Messages Logged When Local Severity Level Is Higher .....................32 Configuring Optional Features for Forwarded Messages .........................33 Including Priority Information in Forwarded Messages .....................33 Adding a Text String to Forwarded Messages ...................................34 Using Regular Expressions to Refine the Set of Forwarded Messages ...................................................................................34 Directing Messages to a Remote Destination from the Routing Matrix ...............................................................................................34 Configuring System Logging Differently on Each Platform ......................35 Displaying and Interpreting System Log Messages ........................................37 Displaying a Log File from a Single-Chassis System ................................37 Displaying a Log File from a Routing Matrix ...........................................37 Interpreting System Log Messages ..........................................................38 Interpreting Messages Generated in Structured-Data Format ............38 Interpreting Messages Generated in Standard Format by a JUNOS Process or Library ......................................................................43 Interpreting Messages Generated in Standard Format by Services on a PIC .....................................................................................44 Format of the message-source Field ........................................................45 The message-source Field on a Single-Chassis System ......................45 The message-source Field on a TX Matrix Platform ..........................45 The message-source Field on a T640 Routing Node in a Routing Matrix ........................................................................................47 Examples: Displaying a Log File ..............................................................48 Getting Help About System Log Messages .....................................................49 Displaying and Interpreting System Log Message Descriptions ...............49 Examples: Displaying System Log Message Descriptions ........................51

Part 2
Chapter 2

System Log Messages

ACCT System Log Messages 57

ACCT_ACCOUNTING_FERROR ......................................................................57 ACCT_ACCOUNTING_FOPEN_ERROR ...........................................................57 ACCT_ACCOUNTING_SMALL_FILE_SIZE .......................................................57 ACCT_BAD_RECORD_FORMAT ....................................................................58 ACCT_CU_RTSLIB_ERROR ............................................................................58 ACCT_FORK_ERR .........................................................................................58 ACCT_FORK_LIMIT_EXCEEDED ....................................................................58

xii

Table of Contents

Table of Contents

ACCT_GETHOSTNAME_ERROR .....................................................................59 ACCT_MALLOC_FAILURE ..............................................................................59 ACCT_UNDEFINED_COUNTER_NAME ..........................................................59 ACCT_XFER_FAILED .....................................................................................59 ACCT_XFER_POPEN_FAIL ............................................................................60 Chapter 3 ALARMD System Log Messages 61

ALARMD_WRITE_ERROR ..............................................................................61 Chapter 4 ANCPD System Log Messages 63

ANCPD_COMMAND_OPTIONS ......................................................................63 Chapter 5 ANTISPAM System Log Messages 65

ANTISPAM_SPAM_DETECTED ......................................................................65 ANTISPAM_SPAM_DETECTED_MT ................................................................65 Chapter 6 APPIDD System Log Messages 67

APPIDD_SCHEDULED_UPDATE_FAILED .......................................................67 Chapter 7 APPPXY System Log Messages 69

APPPXY_RESOURCE_OVERUSED .................................................................69 APPPXY_RESOURCE_OVERUSED_MT ..........................................................69 APPPXY_SESSION_ABORT ............................................................................69 APPPXY_SESSION_ABORT_MT .....................................................................70 Chapter 8 ASP System Log Messages 71

ASP_COS_RULE_MATCH ...............................................................................71 ASP_IDS_HOST_RATE ...................................................................................71 ASP_IDS_HOST_RATE_APP ...........................................................................72 ASP_IDS_INV_CLEAR_QUERY .......................................................................72 ASP_IDS_INV_CLEAR_QUERY_VER ..............................................................72 ASP_IDS_INV_SHOW_QUERY .......................................................................72 ASP_IDS_INV_SHOW_QUERY_VER ...............................................................73 ASP_IDS_LIMIT_FLOW_RATE_BY_DEST .......................................................73 ASP_IDS_LIMIT_FLOW_RATE_BY_PAIR ........................................................73 ASP_IDS_LIMIT_FLOW_RATE_BY_SRC .........................................................74 ASP_IDS_LIMIT_OPEN_FLOWS_BY_DEST ....................................................74 ASP_IDS_LIMIT_OPEN_FLOWS_BY_PAIR .....................................................75 ASP_IDS_LIMIT_OPEN_FLOWS_BY_SRC .......................................................75 ASP_IDS_LIMIT_PKT_RATE_BY_DEST ..........................................................75 ASP_IDS_LIMIT_PKT_RATE_BY_PAIR ...........................................................76

Table of Contents

xiii

JUNOS 10.1 System Log Messages Reference

ASP_IDS_LIMIT_PKT_RATE_BY_SRC .............................................................76 ASP_IDS_NO_MEM_SHOW_CMD ..................................................................76 ASP_IDS_NULL_CLEAR_QUERY ....................................................................77 ASP_IDS_NULL_SHOW_QUERY ....................................................................77 ASP_IDS_RULE_MATCH ................................................................................77 ASP_IDS_SYN_COOKIE_OFF .........................................................................77 ASP_IDS_SYN_COOKIE_ON ..........................................................................78 ASP_IDS_TCP_SYN_ATTACK .........................................................................78 ASP_L2TP_MESSAGE_INCOMPLETE .............................................................79 ASP_L2TP_NO_MEM .....................................................................................79 ASP_L2TP_OBJ_CAC_FAIL .............................................................................79 ASP_L2TP_STATS_BULK_QUERY_FAILED .....................................................79 ASP_L2TP_STATS_VERSION_INVALID ..........................................................80 ASP_L2TP_TUN_GRP_ADD_FAIL_ALLOC ......................................................80 ASP_L2TP_TUN_GRP_ADD_FAIL_EXISTS ......................................................80 ASP_L2TP_TUN_GRP_CHG_FAIL_ALLOC ......................................................80 ASP_L2TP_TUN_GRP_CHG_FAIL_INVLD .......................................................81 ASP_L2TP_TUN_GRP_DEL_FAIL_INVLD ........................................................81 ASP_NAT_OUTOF_ADDRESSES ....................................................................81 ASP_NAT_OUTOF_PORTS .............................................................................81 ASP_NAT_POOL_RELEASE ............................................................................82 ASP_NAT_RULE_MATCH ...............................................................................82 ASP_PGCP_IPC_MSG_WRITE_FAILED ...........................................................82 ASP_PGCP_IPC_PIPE_WRITE_FAILED ...........................................................82 ASP_SFW_ALG_LEVEL_ADJUSTED ................................................................83 ASP_SFW_ALG_PROMOTION_FAILED ..........................................................83 ASP_SFW_APP_MSG_TOO_LONG .................................................................84 ASP_SFW_CHANGE_INACTIVITY_TIMER ......................................................84 ASP_SFW_CREATE_ACCEPT_FLOW .............................................................84 ASP_SFW_CREATE_DISCARD_FLOW ............................................................85 ASP_SFW_CREATE_REJECT_FLOW ...............................................................85 ASP_SFW_FTP_ACTIVE_ACCEPT ..................................................................85 ASP_SFW_FTP_PASSIVE_ACCEPT .................................................................86 ASP_SFW_ICMP_ERROR_DROP ....................................................................86 ASP_SFW_ICMP_HEADER_LEN_ERROR .......................................................86 ASP_SFW_ICMP_PACKET_ERROR_LENGTH .................................................87 ASP_SFW_IP_FRAG_ASSEMBLY_TIMEOUT ...................................................87 ASP_SFW_IP_FRAG_OVERLAP ......................................................................87 ASP_SFW_IP_OPTION_DROP_PACKET .........................................................88 ASP_SFW_IP_PACKET_CHECKSUM_ERROR .................................................88 ASP_SFW_IP_PACKET_DST_BAD ..................................................................88 ASP_SFW_IP_PACKET_FRAG_LEN_INV .........................................................89 ASP_SFW_IP_PACKET_INCORRECT_LEN ......................................................89 ASP_SFW_IP_PACKET_LAND_ATTACK .........................................................89 ASP_SFW_IP_PACKET_NOT_VERSION_4 ......................................................90 ASP_SFW_IP_PACKET_PROTOCOL_ERROR .................................................90 ASP_SFW_IP_PACKET_SRC_BAD ..................................................................90 ASP_SFW_IP_PACKET_TOO_LONG ...............................................................91 ASP_SFW_IP_PACKET_TOO_SHORT ............................................................91 ASP_SFW_IP_PACKET_TTL_ERROR ..............................................................91 ASP_SFW_NEW_POLICY ...............................................................................92

xiv

Table of Contents

Table of Contents

ASP_SFW_NO_IP_PACKET ............................................................................92 ASP_SFW_NO_POLICY ..................................................................................92 ASP_SFW_NO_RULE_DROP ..........................................................................92 ASP_SFW_PING_DUPLICATED_SEQNO ........................................................93 ASP_SFW_PING_MISMATCHED_SEQNO .......................................................93 ASP_SFW_PING_OUTOF_SEQNO_CACHE .....................................................93 ASP_SFW_POLICY_REJECT ...........................................................................94 ASP_SFW_RULE_ACCEPT .............................................................................94 ASP_SFW_RULE_DISCARD ...........................................................................94 ASP_SFW_RULE_REJECT ...............................................................................95 ASP_SFW_SYN_DEFENSE .............................................................................95 ASP_SFW_TCP_BAD_SYN_COOKIE_RESP ....................................................96 ASP_SFW_TCP_FLAGS_ERROR .....................................................................96 ASP_SFW_TCP_HEADER_LEN_ERROR .........................................................96 ASP_SFW_TCP_NON_SYN_FIRST_PACKET ...................................................97 ASP_SFW_TCP_PORT_ZERO .........................................................................97 ASP_SFW_TCP_RECONSTRUCT_DROP .........................................................97 ASP_SFW_TCP_SCAN ....................................................................................98 ASP_SFW_TCP_SEQNO_AND_FLAGS_ZERO .................................................98 ASP_SFW_TCP_SEQNO_ZERO_FLAGS_SET ..................................................98 ASP_SFW_UDP_HEADER_LEN_ERROR .........................................................99 ASP_SFW_UDP_PORT_ZERO ........................................................................99 ASP_SFW_UDP_SCAN ...................................................................................99 ASP_SFW_VERY_BAD_PACKET ..................................................................100 ASP_SVC_SET_MAX_FLOWS_EXCEEDED ...................................................100 Chapter 9 AUDITD System Log Messages 101

AUDITD_RADIUS_AV_ERROR .....................................................................101 AUDITD_RADIUS_OPEN_FAILED ................................................................101 AUDITD_RADIUS_REQ_CREATE_FAILED ....................................................101 AUDITD_RADIUS_REQ_DROPPED ..............................................................102 AUDITD_RADIUS_REQ_SEND_ERROR ........................................................102 AUDITD_RADIUS_REQ_TIMED_OUT ..........................................................102 AUDITD_RADIUS_SERVER_ADD_ERROR ....................................................103 AUDITD_SOCKET_FAILURE ........................................................................103 Chapter 10 AUTHD System Log Messages 105

AUTHD_AUTH_CREATE_FAILED .................................................................105 AUTHD_RADIUS_GETHOSTNAME_FAILED .................................................105 AUTHD_SERVER_INIT_BIND_FAIL ..............................................................105 AUTHD_SERVER_INIT_LISTEN_FAIL ...........................................................106 Chapter 11 AUTOCONFD System Log Messages 107

AUTOCONFD_AUTHENTICATE_LICENSE ....................................................107

Table of Contents

xv

JUNOS 10.1 System Log Messages Reference

Chapter 12

AUTOD System Log Messages

109

AUTOD_BIND_FAILURE ..............................................................................109 AUTOD_HOSTNAME_EXPANSION_FAILURE ..............................................109 AUTOD_RECV_FAILURE ..............................................................................109 AUTOD_RES_MKQUERY_FAILURE .............................................................110 AUTOD_SEND_FAILURE .............................................................................110 AUTOD_SOCKET_CREATE_FAILURE ..........................................................110 Chapter 13 AV System Log Messages 111

AV_HUGE_FILE_DROPPED .........................................................................111 AV_HUGE_FILE_DROPPED_MT ...................................................................111 AV_HUGE_FILE_NOT_SCANNED .................................................................111 AV_HUGE_FILE_NOT_SCANNED_MT ..........................................................112 AV_MANY_MSGS_DROPPED .......................................................................112 AV_MANY_MSGS_DROPPED_MT ................................................................112 AV_MANY_MSGS_NOT_SCANNED ..............................................................112 AV_MANY_MSGS_NOT_SCANNED_MT .......................................................113 AV_PATTERN_GET_FAILED .........................................................................113 AV_PATTERN_KEY_EXPIRED ......................................................................113 AV_PATTERN_KL_CHECK_FAILED ..............................................................114 AV_PATTERN_TOO_BIG ..............................................................................114 AV_PATTERN_UPDATED ............................................................................114 AV_PATTERN_WRITE_FS_FAILED ..............................................................115 AV_SCANNER_DROP_FILE ..........................................................................115 AV_SCANNER_DROP_FILE_MT ...................................................................115 AV_SCANNER_ERROR_SKIPPED .................................................................115 AV_SCANNER_ERROR_SKIPPED_MT ..........................................................116 AV_SCANNER_READY .................................................................................116 AV_VIRUS_DETECTED ................................................................................116 AV_VIRUS_DETECTED_MT .........................................................................116 Chapter 14 BFDD System Log Messages 119

BFDD_MIRROR_ERROR ..............................................................................119 BFDD_MIRROR_VERSION_MISMATCH .......................................................119 BFDD_READ_ERROR ..................................................................................120 BFDD_TRAP_STATE_DOWN .......................................................................120 BFDD_TRAP_STATE_UP ..............................................................................120 BFDD_WRITE_ERROR ................................................................................120 Chapter 15 BOOTPD System Log Messages 121

BOOTPD_ARG_ERR ....................................................................................121 BOOTPD_BAD_ID .......................................................................................121 BOOTPD_BOOTSTRING ..............................................................................121

xvi

Table of Contents

Table of Contents

BOOTPD_CONFIG_ERR ...............................................................................122 BOOTPD_CONF_OPEN ...............................................................................122 BOOTPD_DUP_PIC_SLOT ...........................................................................122 BOOTPD_DUP_REV ....................................................................................123 BOOTPD_DUP_SLOT ...................................................................................123 BOOTPD_HWDB_ERROR ............................................................................123 BOOTPD_MODEL_CHK ...............................................................................123 BOOTPD_MODEL_ERR ...............................................................................124 BOOTPD_NEW_CONF .................................................................................124 BOOTPD_NO_BOOTSTRING .......................................................................124 BOOTPD_NO_CONFIG ................................................................................125 BOOTPD_PARSE_ERR .................................................................................125 BOOTPD_REPARSE .....................................................................................125 BOOTPD_SELECT_ERR ...............................................................................125 BOOTPD_TIMEOUT .....................................................................................126 Chapter 16 CFMD System Log Messages 127

CFMD_CCM_DEFECT_CROSS_CONNECT ....................................................127 CFMD_CCM_DEFECT_ERROR .....................................................................127 CFMD_CCM_DEFECT_MAC_STATUS ...........................................................128 CFMD_CCM_DEFECT_NONE .......................................................................128 CFMD_CCM_DEFECT_RDI ...........................................................................128 CFMD_CCM_DEFECT_RMEP .......................................................................128 CFMD_CCM_DEFECT_UNKNOWN ..............................................................129 Chapter 17 CHASSISD System Log Messages 131

CHASSISD_ANTICF_PIM_CHECK_FAILED ...................................................131 CHASSISD_ANTICF_RE_CHECK_FAILED .....................................................131 CHASSISD_ANTICF_RE_ROM_READ_FAIL ..................................................131 CHASSISD_ANTICF_RE_SHA_READ_FAIL ...................................................132 CHASSISD_ANTICF_ROM_READ_FAILED ....................................................132 CHASSISD_ANTICF_SHA_READ_FAILED .....................................................132 CHASSISD_ARGUMENT_ERROR ..................................................................132 CHASSISD_BLOWERS_SPEED .....................................................................133 CHASSISD_BLOWERS_SPEED_FULL ...........................................................133 CHASSISD_BLOWERS_SPEED_MEDIUM .....................................................133 CHASSISD_BUS_DEVICE_OPEN_FAILURE ...................................................133 CHASSISD_CB_CLOCK_CHECKSUM ............................................................134 CHASSISD_CB_MASTER_BP_IGNORED .......................................................134 CHASSISD_CB_READ ..................................................................................134 CHASSISD_CB_RE_ONLINE_BP_IGNORED ..................................................135 CHASSISD_CFEB_POWER_FAILURE ...........................................................135 CHASSISD_CLEAR_CONFIG_ERROR ...........................................................135 CHASSISD_CLOCK_FAILURE .......................................................................136 CHASSISD_CLOCK_NOTICE ........................................................................136 CHASSISD_CMB_READBACK_ERROR .........................................................136 CHASSISD_COMMAND_ACK_ERROR ..........................................................136 CHASSISD_COMMAND_ACK_SFM_ERROR .................................................137

Table of Contents

xvii

JUNOS 10.1 System Log Messages Reference

CHASSISD_CONCAT_MODE_ERROR ..........................................................137 CHASSISD_CONFIG_ACCESS_ERROR .........................................................137 CHASSISD_CONFIG_CHANGE_IFDEV_DEL ..................................................138 CHASSISD_CONFIG_INIT_ERROR ...............................................................138 CHASSISD_CONFIG_WARNING ...................................................................138 CHASSISD_DEVICE_OPEN_ERROR .............................................................138 CHASSISD_EXEC_ERROR ............................................................................139 CHASSISD_EXISTS ......................................................................................139 CHASSISD_EXISTS_TERM_OTHER ..............................................................139 CHASSISD_FAN_FAILURE ...........................................................................139 CHASSISD_FASIC_CONFIG_COMPLETE ......................................................140 CHASSISD_FASIC_FTOKEN_ERROR ............................................................140 CHASSISD_FASIC_FTOKEN_INIT_ERROR ...................................................140 CHASSISD_FASIC_HSL_CONFIG_ERROR ....................................................141 CHASSISD_FASIC_HSL_LINK_ERROR .........................................................141 CHASSISD_FASIC_INIT_ERROR ..................................................................141 CHASSISD_FASIC_INPUT_DROP .................................................................141 CHASSISD_FASIC_OUTPUT_DROP ..............................................................142 CHASSISD_FASIC_PIO_READ_ERROR ........................................................142 CHASSISD_FASIC_PIO_WRITE_ERROR .......................................................142 CHASSISD_FASIC_PLL_ERROR ...................................................................142 CHASSISD_FASIC_RESET_ERROR ...............................................................143 CHASSISD_FASIC_SRAM_ERROR ................................................................143 CHASSISD_FASIC_VERSION_ERROR ..........................................................143 CHASSISD_FCHIP_CONFIG_COMPLETE ......................................................144 CHASSISD_FCHIP_CONFIG_MD_ERROR .....................................................144 CHASSISD_FCHIP_CONFIG_RATE_ERROR ..................................................144 CHASSISD_FCHIP_CONFIG_READ_ERROR .................................................144 CHASSISD_FCHIP_FTOKEN_ERROR ...........................................................145 CHASSISD_FCHIP_FTOKEN_INIT_ERROR ...................................................145 CHASSISD_FCHIP_HSR_ERROR ..................................................................145 CHASSISD_FCHIP_HSR_INIT_ERROR ..........................................................145 CHASSISD_FCHIP_HSR_INIT_LINK_ERR .....................................................146 CHASSISD_FCHIP_HSR_RESET_ERROR ......................................................146 CHASSISD_FCHIP_HST_ERROR ..................................................................146 CHASSISD_FCHIP_HST_INIT_ERROR ..........................................................146 CHASSISD_FCHIP_HST_INIT_LINK_ERR .....................................................147 CHASSISD_FCHIP_HST_RESET_ERROR ......................................................147 CHASSISD_FCHIP_INIT_ERROR ..................................................................147 CHASSISD_FCHIP_LINK_ERROR .................................................................147 CHASSISD_FCHIP_MONITOR_ERROR .........................................................148 CHASSISD_FCHIP_PIO_READ_ERROR ........................................................148 CHASSISD_FCHIP_PIO_WRITE_ERROR ......................................................148 CHASSISD_FCHIP_POLL_ERROR ................................................................148 CHASSISD_FCHIP_RATE_ERROR ................................................................149 CHASSISD_FCHIP_SIB_NOT_STARTED .......................................................149 CHASSISD_FCHIP_VERSION_ERROR ..........................................................149 CHASSISD_FEB_REVERSION .......................................................................149 CHASSISD_FEB_SWITCHOVER ...................................................................150 CHASSISD_FHSR_READ_REG_ERROR ........................................................150 CHASSISD_FHSR_WRITE_REG_ERROR .......................................................150

xviii

Table of Contents

Table of Contents

CHASSISD_FHST_READ_REG_ERROR .........................................................150 CHASSISD_FHST_WRITE_REG_ERROR .......................................................151 CHASSISD_FILE_OPEN ................................................................................151 CHASSISD_FILE_STAT .................................................................................151 CHASSISD_FM_BAD_STATE ........................................................................151 CHASSISD_FM_ERROR ...............................................................................152 CHASSISD_FM_ERROR_CLOS_F13_HSR .....................................................152 CHASSISD_FM_ERROR_CLOS_F13_HST .....................................................152 CHASSISD_FM_ERROR_CLOS_F2_HSR .......................................................153 CHASSISD_FM_ERROR_CLOS_F2_HST .......................................................153 CHASSISD_FM_ERROR_F13_FB_HSR_TXP .................................................153 CHASSISD_FM_ERROR_F13_FB_RX_VC .....................................................154 CHASSISD_FM_ERROR_F13_FB_TXP ..........................................................154 CHASSISD_FM_ERROR_F13_FB_TX_VC .....................................................154 CHASSISD_FM_ERROR_F13_VC_PWR ........................................................155 CHASSISD_FM_ERROR_SIB_L_FB_HSR .......................................................155 CHASSISD_FM_ERROR_SIB_L_FB_RX_VC ..................................................156 CHASSISD_FM_ERROR_SIB_L_FB_SMF ......................................................156 CHASSISD_FM_ERROR_SIB_L_FB_TXP .......................................................156 CHASSISD_FM_ERROR_SIB_L_FB_TX_VC ...................................................157 CHASSISD_FM_ERROR_SIB_L_HSR_PFE .....................................................157 CHASSISD_FM_ERROR_SIB_L_HSR_TXP ....................................................157 CHASSISD_FM_ERROR_SIB_L_MISMATCH .................................................158 CHASSISD_FM_ERROR_SIB_L_VC_PWR .....................................................158 CHASSISD_FM_ERROR_SIB_S_FB_HSR ......................................................158 CHASSISD_FM_ERROR_SIB_S_FB_SMF ......................................................159 CHASSISD_FM_MEMORY_ERROR ..............................................................159 CHASSISD_FM_SIB_ERROR ........................................................................159 CHASSISD_FM_SIB_FPC_TYPE_ERROR ......................................................160 CHASSISD_FPC_NOT_FOUND .....................................................................160 CHASSISD_FPC_PIC_DETECT_TIMEOUT .....................................................160 CHASSISD_FPC_TYPE_SIB_TYPE_ERROR ...................................................160 CHASSISD_FRU_ALREADY_OFFLINE ..........................................................161 CHASSISD_FRU_ALREADY_ONLINE ...........................................................161 CHASSISD_FRU_EVENT ..............................................................................161 CHASSISD_FRU_INVALID_SLOT ..................................................................161 CHASSISD_FRU_IO_ERROR ........................................................................162 CHASSISD_FRU_IO_OFFSET_ERROR ..........................................................162 CHASSISD_FRU_IPC_WRITE_ERROR ..........................................................162 CHASSISD_FRU_OFFLINE_FAILED ..............................................................163 CHASSISD_FRU_OFFLINE_NOTICE .............................................................163 CHASSISD_FRU_OFFLINE_TIMEOUT ..........................................................163 CHASSISD_FRU_ONLINE_TIMEOUT ............................................................163 CHASSISD_FRU_STEP_ERROR ....................................................................164 CHASSISD_FRU_UNRESPONSIVE ................................................................164 CHASSISD_FRU_UNRESPONSIVE_RETRY ...................................................164 CHASSISD_FRU_UNSUPPORTED ................................................................164 CHASSISD_FRU_VERSION_MISMATCH .......................................................165 CHASSISD_GASIC_ID_ERROR .....................................................................165 CHASSISD_GBUS_NOT_READY ...................................................................165 CHASSISD_GBUS_READBACK_ERROR ........................................................166

Table of Contents

xix

JUNOS 10.1 System Log Messages Reference

CHASSISD_GBUS_RESET_EVENT ................................................................166 CHASSISD_GBUS_SANITY_ERROR ..............................................................166 CHASSISD_GENERIC_ERROR ......................................................................166 CHASSISD_GENERIC_WARNING .................................................................167 CHASSISD_GETTIMEOFDAY ........................................................................167 CHASSISD_GRES_UNSUPP_PIC ...................................................................167 CHASSISD_HIGH_TEMP_CONDITION .........................................................167 CHASSISD_HOST_TEMP_READ ...................................................................168 CHASSISD_HSR_CONFIG_READ_ERROR ....................................................168 CHASSISD_HSR_CONFIG_WRITE_ERROR ...................................................168 CHASSISD_HSR_ELEMENTS_ERROR ..........................................................168 CHASSISD_HSR_FIFO_ERROR ....................................................................169 CHASSISD_I2CS_READBACK_ERROR .........................................................169 CHASSISD_I2C_BAD_IDEEPROM_FORMAT ................................................169 CHASSISD_I2C_FIC_PRESENCE_READ .......................................................169 CHASSISD_I2C_GENERIC_ERROR ...............................................................170 CHASSISD_I2C_INVALID_ASSEMBLY_ID .....................................................170 CHASSISD_I2C_IOCTL_FAILURE .................................................................170 CHASSISD_I2C_IO_FAILURE .......................................................................171 CHASSISD_I2C_MIDPLANE_CORRUPT ........................................................171 CHASSISD_I2C_RANGE_ERROR ..................................................................171 CHASSISD_I2C_READ_ERROR ....................................................................171 CHASSISD_I2C_WRITE_ERROR ..................................................................172 CHASSISD_IDEEPROM_READ_ERROR ........................................................172 CHASSISD_IFDEV_CREATE_FAILURE .........................................................172 CHASSISD_IFDEV_CREATE_NOTICE ...........................................................173 CHASSISD_IFDEV_DETACH_ALL_PSEUDO .................................................173 CHASSISD_IFDEV_DETACH_FPC ................................................................173 CHASSISD_IFDEV_DETACH_PIC .................................................................173 CHASSISD_IFDEV_DETACH_PSEUDO .........................................................174 CHASSISD_IFDEV_DETACH_TLV_ERROR ...................................................174 CHASSISD_IFDEV_GETBYNAME_NOTICE ...................................................174 CHASSISD_IFDEV_GET_BY_INDEX_FAIL ....................................................174 CHASSISD_IFDEV_GET_BY_NAME_FAIL .....................................................175 CHASSISD_IFDEV_NO_MEMORY ................................................................175 CHASSISD_IFDEV_RETRY_NOTICE .............................................................175 CHASSISD_IFDEV_RTSLIB_FAILURE ...........................................................176 CHASSISD_IOCTL_FAILURE ........................................................................176 CHASSISD_IPC_ANNOUNCE_TIMEOUT ......................................................176 CHASSISD_IPC_CONNECTION_DROPPED ..................................................176 CHASSISD_IPC_DAEMON_WRITE_ERROR ..................................................177 CHASSISD_IPC_ERROR ...............................................................................177 CHASSISD_IPC_FLUSH_ERROR ...................................................................177 CHASSISD_IPC_MSG_DROPPED .................................................................178 CHASSISD_IPC_MSG_ERROR ......................................................................178 CHASSISD_IPC_MSG_FRU_NOT_FOUND ....................................................178 CHASSISD_IPC_MSG_QFULL_ERROR ..........................................................179 CHASSISD_IPC_MSG_UNHANDLED ............................................................179 CHASSISD_IPC_UNEXPECTED_MSG ...........................................................179 CHASSISD_IPC_UNEXPECTED_RECV ..........................................................179 CHASSISD_IPC_WRITE_ERROR ..................................................................180

xx

Table of Contents

Table of Contents

CHASSISD_IPC_WRITE_ERR_NO_PIPE .......................................................180 CHASSISD_IPC_WRITE_ERR_NULL_ARGS ..................................................180 CHASSISD_ISSU_BLOB_ERROR ..................................................................180 CHASSISD_ISSU_DAEMON_ERROR ............................................................181 CHASSISD_ISSU_ERROR .............................................................................181 CHASSISD_ISSU_FRU_ERROR .....................................................................181 CHASSISD_ISSU_FRU_IPC_ERROR .............................................................181 CHASSISD_JTREE_ERROR ...........................................................................182 CHASSISD_LCC_RELEASE_MASTERSHIP ....................................................182 CHASSISD_LOST_MASTERSHIP ..................................................................182 CHASSISD_MAC_ADDRESS_AE_ERROR .....................................................182 CHASSISD_MAC_ADDRESS_CBP_ERROR ...................................................183 CHASSISD_MAC_ADDRESS_ERROR ............................................................183 CHASSISD_MAC_ADDRESS_FABRIC_ERR ...................................................183 CHASSISD_MAC_ADDRESS_IRB_ERROR ....................................................183 CHASSISD_MAC_ADDRESS_PIP_ERROR .....................................................184 CHASSISD_MAC_ADDRESS_VLAN_ERROR .................................................184 CHASSISD_MAC_DEFAULT .........................................................................184 CHASSISD_MALLOC_FAILURE ....................................................................184 CHASSISD_MASTER_PCG_REMOVED .........................................................185 CHASSISD_MASTER_SCG_REMOVED .........................................................185 CHASSISD_MBUS_ERROR ...........................................................................185 CHASSISD_MCHASSIS_SWITCH_WARNING ................................................185 CHASSISD_MCS_INTR_ERROR ....................................................................186 CHASSISD_MGR_CONNECT ........................................................................186 CHASSISD_MIC_OFFLINE_NOTICE .............................................................186 CHASSISD_MULTILINK_BUNDLES_ERROR .................................................187 CHASSISD_NO_PCGS ..................................................................................187 CHASSISD_NO_SCGS ..................................................................................187 CHASSISD_OFFLINE_NOTICE .....................................................................187 CHASSISD_OID_GEN_FAILED .....................................................................188 CHASSISD_OVER_TEMP_CONDITION .........................................................188 CHASSISD_OVER_TEMP_SHUTDOWN_TIME ..............................................188 CHASSISD_PARSE_COMPLETE ...................................................................189 CHASSISD_PCI_ERROR ...............................................................................189 CHASSISD_PEER_UNCONNECTED ..............................................................189 CHASSISD_PEM_BREAKER_TRIP ................................................................189 CHASSISD_PEM_IMPROPER .......................................................................190 CHASSISD_PEM_INPUT_BAD ......................................................................190 CHASSISD_PEM_NOT_SUFFICIENT .............................................................190 CHASSISD_PEM_OVERLOAD ......................................................................191 CHASSISD_PEM_TEMPERATURE ................................................................191 CHASSISD_PEM_VOLTAGE .........................................................................191 CHASSISD_PIC_CMD_GIVEUP .....................................................................191 CHASSISD_PIC_CMD_TIMEOUT ..................................................................192 CHASSISD_PIC_CONFIG_ERROR ................................................................192 CHASSISD_PIC_HWERROR .........................................................................192 CHASSISD_PIC_OFFLINE_NOTICE ..............................................................193 CHASSISD_PIC_OID_GEN_FAILED ..............................................................193 CHASSISD_PIC_OID_UNKNOWN ................................................................193 CHASSISD_PIC_RESET_ON_SWITCHOVER .................................................193

Table of Contents

xxi

JUNOS 10.1 System Log Messages Reference

CHASSISD_PIC_SPEED_INVALID .................................................................194 CHASSISD_PIC_VERSION_ERROR ..............................................................194 CHASSISD_PIDFILE_OPEN ..........................................................................194 CHASSISD_PIPE_WRITE_ERROR ................................................................195 CHASSISD_POWER_CHECK ........................................................................195 CHASSISD_POWER_EVENT ........................................................................195 CHASSISD_POWER_RATINGS_EXCEEDED .................................................195 CHASSISD_PSD_RELEASE_MASTERSHIP ....................................................196 CHASSISD_PSU_ERROR ..............................................................................196 CHASSISD_PSU_FAN_FAIL ..........................................................................196 CHASSISD_PSU_INPUT_BAD .......................................................................197 CHASSISD_PSU_OVERLOAD .......................................................................197 CHASSISD_PSU_TEMPERATURE .................................................................197 CHASSISD_PSU_VOLTAGE ..........................................................................197 CHASSISD_RANGE_CHECK .........................................................................198 CHASSISD_RECONNECT_SUCCESSFUL .......................................................198 CHASSISD_RELEASE_MASTERSHIP ............................................................198 CHASSISD_RE_INIT_INVALID_RE_SLOT .....................................................198 CHASSISD_RE_OVER_TEMP_CONDITION ..................................................199 CHASSISD_RE_OVER_TEMP_SHUTDOWN ..................................................199 CHASSISD_RE_OVER_TEMP_WARNING .....................................................199 CHASSISD_RE_WARM_TEMP_CONDITION .................................................200 CHASSISD_ROOT_MOUNT_ERROR ............................................................200 CHASSISD_RTS_SEQ_ERROR ......................................................................200 CHASSISD_SBOARD_VERSION_MISMATCH ................................................200 CHASSISD_SENSOR_RANGE_NOTICE .........................................................201 CHASSISD_SERIAL_ID .................................................................................201 CHASSISD_SFM_MODE_ERROR .................................................................201 CHASSISD_SFM_NOT_ONLINE ....................................................................202 CHASSISD_SHUTDOWN_NOTICE ...............................................................202 CHASSISD_SIB_INVALID_SLOT ...................................................................202 CHASSISD_SIGPIPE .....................................................................................202 CHASSISD_SMB_ERROR .............................................................................203 CHASSISD_SMB_INVALID_PS ......................................................................203 CHASSISD_SMB_IOCTL_FAILURE ...............................................................203 CHASSISD_SMB_READ_FAILURE ................................................................204 CHASSISD_SNMP_TRAP1 ............................................................................204 CHASSISD_SNMP_TRAP10 ..........................................................................204 CHASSISD_SNMP_TRAP6 ............................................................................204 CHASSISD_SNMP_TRAP7 ............................................................................205 CHASSISD_SPMB_RESTART ........................................................................205 CHASSISD_SPMB_RESTART_TIMEOUT .......................................................205 CHASSISD_SSB_FAILOVERS ........................................................................205 CHASSISD_STANDALONE_FPC_NOTICE .....................................................206 CHASSISD_SYSCTL_ERROR ........................................................................206 CHASSISD_TEMP_HOT_NOTICE .................................................................206 CHASSISD_TEMP_SENSOR_FAILURE ..........................................................206 CHASSISD_TERM_SIGNAL ...........................................................................207 CHASSISD_TIMER_CLR_ERR .......................................................................207 CHASSISD_TIMER_ERR ...............................................................................207 CHASSISD_TIMER_VAL_ERR .......................................................................208

xxii

Table of Contents

Table of Contents

CHASSISD_UNEXPECTED_EXIT ..................................................................208 CHASSISD_UNEXPECTED_VALUE ...............................................................208 CHASSISD_UNSUPPORTED_FPC .................................................................208 CHASSISD_UNSUPPORTED_MODEL ...........................................................209 CHASSISD_UNSUPPORTED_PIC ..................................................................209 CHASSISD_UNSUPPORTED_PIC_MODE ......................................................209 CHASSISD_UNSUPPORTED_SIB ..................................................................209 CHASSISD_VERSION_MISMATCH ...............................................................210 CHASSISD_VOLTAGE_READ_FAILED ..........................................................210 CHASSISD_VOLTAGE_SENSOR_INIT ...........................................................210 Chapter 18 CONNECTION System Log Messages 213

CONNECTION_CHASSISD_FAIL ..................................................................213 CONNECTION_CRAFTD_FAIL .....................................................................213 CONNECTION_RTLOGD_FAIL .....................................................................213 CONNECTION_SEND_ERROR .....................................................................214 Chapter 19 CONTENT System Log Messages 215

CONTENT_FILTERING_BLOCKED ...............................................................215 CONTENT_FILTERING_BLOCKED_MT .........................................................215 Chapter 20 COSD System Log Messages 217

COSD_AGGR_CONFIG_INVALID ..................................................................217 COSD_CHASSIS_SCHED_MAP_INVALID ......................................................217 COSD_CLASSIFIER_NO_SUPPORT_LSI .......................................................218 COSD_CONF_OPEN_FAILURE .....................................................................218 COSD_DB_OPEN_FAILED ...........................................................................218 COSD_EXACT_RATE_UNSUPP_INTERFACE ................................................219 COSD_EXACT_RATE_UNSUPP_SESSION ....................................................219 COSD_FRAGMENTATION_MAP_CONFLICT .................................................220 COSD_HIGH_PRIO_QUEUES_INTERFACE ...................................................220 COSD_HIGH_PRIO_QUEUES_SESSION .......................................................220 COSD_HWDB_OPEN_FAILED .....................................................................221 COSD_IFD_OUTPUT_SHAPING_RATE_ERR ................................................221 COSD_IFD_SHAPER_ERR ............................................................................222 COSD_INTERFACE_NO_MEDIA ...................................................................222 COSD_L2TP_COS_NOT_CONFIGURED .......................................................222 COSD_L2TP_COS_NOT_SUPPORTED .........................................................223 COSD_L2TP_SHAPING_NOT_CONFIGURED ................................................223 COSD_LARGE_DELAY_BUFFER_INVALID ...................................................223 COSD_MALLOC_FAILED .............................................................................224 COSD_MPLS_DSCP_CLASS_NO_SUPPORT .................................................224 COSD_MULTILINK_CLASS_CONFLICT .........................................................224 COSD_NULL_INPUT_ARGUMENT ................................................................225 COSD_RATE_LIMIT_INVALID ......................................................................225 COSD_RATE_LIMIT_NOT_SUPPORTED .......................................................225

Table of Contents

xxiii

JUNOS 10.1 System Log Messages Reference

COSD_REWRITE_RULE_LIMIT_EXCEEDED .................................................226 COSD_SCHEDULER_MAP_CONFLICT ..........................................................226 COSD_STREAM_IFD_CREATE_FAILURE .....................................................227 COSD_TIMER_ERROR .................................................................................227 COSD_TRICOLOR_NOT_SUPPORTED .........................................................227 COSD_TX_QUEUE_RATES_TOO_HIGH .......................................................228 COSD_UNKNOWN_CLASSIFIER ..................................................................228 COSD_UNKNOWN_REWRITE .....................................................................228 COSD_UNKNOWN_TRANSLATION_TABLE .................................................229 Chapter 21 DCD System Log Messages 231

DCD_GRE_CONFIG_INVALID ......................................................................231 DCD_MALLOC_FAILED_INIT .......................................................................231 DCD_PARSE_EMERGENCY ..........................................................................232 DCD_PARSE_ERROR_CLOCK ......................................................................232 DCD_PARSE_ERROR_HIER_SCHEDULER ...................................................232 DCD_PARSE_ERROR_IFLSET ......................................................................233 DCD_PARSE_ERROR_MAX_HIER_LEVELS ..................................................233 DCD_PARSE_ERROR_SCHEDULER .............................................................233 DCD_PARSE_ERROR_SCHEDULER_LIMIT ..................................................234 DCD_PARSE_ERROR_VLAN_TAGGING ........................................................234 DCD_PARSE_ERR_INCOMPATIBLE_CFG .....................................................234 DCD_PARSE_MINI_EMERGENCY ................................................................234 DCD_PARSE_STATE_EMERGENCY ..............................................................235 Chapter 22 DFCD System Log Messages 237

DFCD_FTAP_PIC_UNSUPPORTED ...............................................................237 DFCD_GENCFG_MALLOC_FAILED ..............................................................237 DFCD_GENCFG_WRITE_FAILED .................................................................237 DFCD_LINH_MALLOC_FAILED ....................................................................238 DFCD_LI_NEXT_HOP_ADD_FAILED ...........................................................238 DFCD_NEXT_HOP_ADD_FAILED ................................................................238 DFCD_NEXT_HOP_DELETE_FAILED ...........................................................238 DFCD_SAMPLE_CLASS_ADD_FAILED .........................................................238 DFCD_SAMPLE_CLASS_DELETE_FAILED ....................................................239 Chapter 23 DFWD System Log Messages 241

DFWD_MALLOC_FAILED_INIT ....................................................................241 DFWD_PARSE_FILTER_EMERGENCY ..........................................................241 DFWD_PARSE_STATE_EMERGENCY ..........................................................242 DFWD_POLICER_LIMIT_EXCEEDED ...........................................................242

xxiv

Table of Contents

Table of Contents

Chapter 24

DHCPD System Log Messages

243

DHCPD_BIND_FAILURE ..............................................................................243 DHCPD_DEGRADED_MODE .......................................................................243 DHCPD_MEMORY_ALLOCATION_FAILURE ................................................244 DHCPD_OVERLAY_CONFIG_FAILURE ........................................................244 DHCPD_OVERLAY_PARSE_FAILURE ..........................................................244 DHCPD_RECVMSG_FAILURE ......................................................................244 DHCPD_RTSOCK_FAILURE .........................................................................245 DHCPD_SENDMSG_FAILURE ......................................................................245 DHCPD_SENDMSG_NOINT_FAILURE ..........................................................245 DHCPD_SETSOCKOPT_FAILURE .................................................................246 DHCPD_SOCKET_FAILURE .........................................................................246 Chapter 25 DYNAMIC System Log Messages 247

DYNAMIC_VPN_AUTH_CONNECT_FAIL ......................................................247 DYNAMIC_VPN_AUTH_FAIL .......................................................................247 DYNAMIC_VPN_AUTH_INVALID .................................................................247 DYNAMIC_VPN_AUTH_NO_CONFIG ...........................................................248 DYNAMIC_VPN_AUTH_NO_LICENSE ..........................................................248 DYNAMIC_VPN_AUTH_OK ..........................................................................248 DYNAMIC_VPN_CLIENT_CONFIG_WRITE ...................................................248 DYNAMIC_VPN_CONN_DEL_NOTIFY .........................................................249 DYNAMIC_VPN_CONN_DEL_REQUEST ......................................................249 DYNAMIC_VPN_CONN_EST_NOTIFY ..........................................................249 DYNAMIC_VPN_INIT_SUCCESSFUL .............................................................249 DYNAMIC_VPN_LICENSE_ASSIGNED ..........................................................249 DYNAMIC_VPN_LICENSE_CHECK_FAILED .................................................250 DYNAMIC_VPN_LICENSE_CHECK_OK ........................................................250 DYNAMIC_VPN_LICENSE_EXHAUSTED ......................................................250 DYNAMIC_VPN_LICENSE_FREED ...............................................................250 DYNAMIC_VPN_LICENSE_FREE_FAILED ....................................................251 DYNAMIC_VPN_LICENSE_FREE_OK ...........................................................251 DYNAMIC_VPN_LICENSE_GET_FAILED ......................................................251 DYNAMIC_VPN_LICENSE_GET_OK .............................................................251 DYNAMIC_VPN_LICENSE_INSTALLED ........................................................251 DYNAMIC_VPN_LICENSE_REQUIRED .........................................................252 DYNAMIC_VPN_LICENSE_UNINSTALLED ....................................................252 Chapter 26 ESWD System Log Messages 253

ESWD_BPDU_BLOCK_ERROR_DISABLED ..................................................253 ESWD_BPDU_BLOCK_ERROR_ENABLED ...................................................253 ESWD_DAI_FAILED .....................................................................................253 ESWD_DHCP_UNTRUSTED .........................................................................254 ESWD_INVALID_MAC_ADDRESS ................................................................254 ESWD_MAC_LIMIT_BLOCK .........................................................................254

Table of Contents

xxv

JUNOS 10.1 System Log Messages Reference

ESWD_MAC_LIMIT_DROP ..........................................................................254 ESWD_MAC_LIMIT_EXCEEDED ..................................................................255 ESWD_MAC_MOVE_LIMIT_BLOCK .............................................................255 ESWD_MAC_MOVE_LIMIT_DROP ...............................................................255 ESWD_MAC_MOVE_LIMIT_EXCEEDED .......................................................256 ESWD_MIRROR_ERROR .............................................................................256 ESWD_MIRROR_VERSION_MISMATCH ......................................................256 ESWD_MODULE_SHUTDOWN_FAILURE ....................................................257 ESWD_PPM_READ_ERROR .........................................................................257 ESWD_PPM_WRITE_ERROR .......................................................................257 ESWD_STP_BASE_MAC_ERROR .................................................................257 ESWD_STP_LOOP_PROTECT_CLEARED .....................................................258 ESWD_STP_LOOP_PROTECT_IN_EFFECT ...................................................258 ESWD_STP_ROOT_PROTECT_CLEARED ....................................................258 ESWD_STP_ROOT_PROTECT_IN_EFFECT ..................................................258 ESWD_ST_CTL_BW_INFO ...........................................................................259 ESWD_ST_CTL_ERROR_DISABLED .............................................................259 ESWD_ST_CTL_ERROR_ENABLED ..............................................................259 ESWD_ST_CTL_INFO ..................................................................................259 ESWD_SYSTEM_CALL_FAILED ....................................................................259 Chapter 27 EVENTD System Log Messages 261

EVENTD_ACK_FAILED ................................................................................261 EVENTD_ALARM_CLEAR ............................................................................261 EVENTD_COMMAND_SUBSTITUTE_ERROR ...............................................261 EVENTD_ESCRIPT_EXECUTION ..................................................................262 EVENTD_EVENT_SEND_FAILED .................................................................262 EVENTD_FORK_ERR ...................................................................................262 EVENTD_PIPE_CREATION_FAILED .............................................................262 EVENTD_POLICY_ACTION_FAILED ............................................................263 EVENTD_POLICY_LIMIT_EXCEEDED ..........................................................263 EVENTD_POLICY_UPLOAD_FAILED ...........................................................263 EVENTD_POPEN_FAIL ................................................................................263 EVENTD_READ_ERROR ..............................................................................264 EVENTD_REGEXP_INVALID ........................................................................264 EVENTD_REG_VERSION_MISMATCH ..........................................................264 EVENTD_ROTATE_COMMAND_FAILED ......................................................264 EVENTD_ROTATE_FORK_EXCEEDED ........................................................265 EVENTD_ROTATE_FORK_FAILED ...............................................................265 EVENTD_SCRIPT_CHECKSUM_MISMATCH .................................................265 EVENTD_SET_PROCESS_PRIV_FAILED .......................................................265 EVENTD_SET_TIMER_FAILED .....................................................................266 EVENTD_SYSLOG_FWD_FAILED .................................................................266 EVENTD_TEST_ALARM ...............................................................................266 EVENTD_TRANSFER_COMMAND_FAILED ..................................................266 EVENTD_TRANSFER_FORK_EXCEEDED .....................................................267 EVENTD_TRANSFER_FORK_FAILED ...........................................................267 EVENTD_VERSION_MISMATCH ..................................................................267 EVENTD_XML_FILENAME_INVALID ............................................................267

xxvi

Table of Contents

Table of Contents

Chapter 28

FCD System Log Messages

269

FCD_SYS_CALL_FAILED ..............................................................................269 Chapter 29 FLOW System Log Messages 271

FLOW_HIGH_WATERMARK_TRIGGERED ...................................................271 FLOW_IP_ACTION ......................................................................................271 FLOW_LOW_WATERMARK_TRIGGERED ....................................................271 FLOW_SESSION_CLOSE ..............................................................................272 FLOW_SESSION_CREATE ...........................................................................272 FLOW_SESSION_DENY ...............................................................................272 Chapter 30 FPCLOGIN System Log Messages 273

FPCLOGIN_ADDRESS_GET_FAILED ............................................................273 FPCLOGIN_IPC_RECEIVE_FAILED ...............................................................273 FPCLOGIN_IPC_SEND_FAILED ....................................................................273 FPCLOGIN_LOGIN_FAILED ..........................................................................274 FPCLOGIN_MESSAGE_INVALID ...................................................................274 FPCLOGIN_SOCKET_OPERATION_FAILED .................................................274 Chapter 31 FSAD System Log Messages 275

FSAD_CONFIG_ERROR ...............................................................................275 FSAD_CONNTIMEDOUT ..............................................................................275 FSAD_DIR_CREATE .....................................................................................275 FSAD_DIR_STAT .........................................................................................276 FSAD_FAILED .............................................................................................276 FSAD_FILE_FAILED .....................................................................................276 FSAD_FILE_REMOVE ..................................................................................277 FSAD_FILE_RENAME ..................................................................................277 FSAD_FILE_STAT ........................................................................................277 FSAD_FILE_SYNC ........................................................................................278 FSAD_FLOWC_IPC_PAYLOAD_SIZE ............................................................278 FSAD_FLOWC_IPC_SUBTYPE .....................................................................278 FSAD_FLOWC_IPC_TYPE ............................................................................278 FSAD_FLOWC_IPC_VERSION ......................................................................279 FSAD_FLOWC_SERVICE_INACTIVE ............................................................279 FSAD_FREE_SPACE_LOG ............................................................................279 FSAD_FREE_SPACE_TMP ............................................................................279 FSAD_FS_STAT ...........................................................................................280 FSAD_GEN_IPC_PAYLOAD_SIZE .................................................................280 FSAD_GEN_IPC_SUBTYPE ...........................................................................280 FSAD_GEN_IPC_TYPE .................................................................................280 FSAD_GEN_IPC_VERSION ...........................................................................281 FSAD_GEN_SERVICE_INACTIVE ..................................................................281

Table of Contents

xxvii

JUNOS 10.1 System Log Messages Reference

FSAD_GEN_SERVICE_INIT_FAILED .............................................................281 FSAD_MAXCONN ........................................................................................281 FSAD_MEMORYALLOC_FAILED ..................................................................282 FSAD_NOT_ROOT .......................................................................................282 FSAD_PARENT_DIRECTORY .......................................................................282 FSAD_PATH_IS_DIRECTORY ......................................................................282 FSAD_PATH_IS_NOT_DIRECTORY ..............................................................283 FSAD_PATH_IS_SPECIAL ............................................................................283 FSAD_RECVERROR .....................................................................................283 FSAD_RENAME ...........................................................................................283 FSAD_TERMINATED_CONNECTION ...........................................................284 FSAD_TRACEOPEN_FAILED ........................................................................284 FSAD_USAGE ..............................................................................................284 Chapter 32 FUD System Log Messages 285

FUD_ARGUMENT_FAILURE .........................................................................285 FUD_BAD_SERVER_ADDR_FAILURE ..........................................................285 FUD_BIND_FAILURE ...................................................................................285 FUD_DAEMON_FAILURE ............................................................................286 FUD_MEMORY_ALLOCATION_FAILURE .....................................................286 FUD_PERMISSION_FAILURE .......................................................................286 FUD_PIDLOCK_FAILURE .............................................................................287 FUD_PIDUPDATE_FAILURE ........................................................................287 FUD_RECVMSG_FAILURE ...........................................................................287 FUD_RTSOCK_WRITE_FAILURE .................................................................288 FUD_SENDMSG_FAILURE ...........................................................................288 FUD_SENDMSG_NOINT_FAILURE ...............................................................288 FUD_SETSOCKOPT_FAILURE ......................................................................288 FUD_SOCKET_FAILURE ..............................................................................289 Chapter 33 FWAUTH System Log Messages 291

FWAUTH_FTP_LONG_PASSWORD .............................................................291 FWAUTH_FTP_LONG_USERNAME ..............................................................291 FWAUTH_FTP_USER_AUTH_ACCEPTED .....................................................291 FWAUTH_FTP_USER_AUTH_FAIL ...............................................................291 FWAUTH_HTTP_USER_AUTH_ACCEPTED ..................................................292 FWAUTH_HTTP_USER_AUTH_FAIL ............................................................292 FWAUTH_TELNET_LONG_PASSWORD .......................................................292 FWAUTH_TELNET_LONG_USERNAME ........................................................292 FWAUTH_TELNET_USER_AUTH_ACCEPTED ..............................................293 FWAUTH_TELNET_USER_AUTH_FAIL .........................................................293 FWAUTH_WEBAUTH_FAIL ..........................................................................293 FWAUTH_WEBAUTH_SUCCESS ..................................................................293

xxviii

Table of Contents

Table of Contents

Chapter 34

GPRSD System Log Messages

295

GPRSD_MEMORY_ALLOC_FAILED ..............................................................295 GPRSD_RESTART_CCFG_READ_FAILED .....................................................295 Chapter 35 HNCACHED System Log Messages 297

HNCACHED_HOST_ADDRESS_CHANGED ...................................................297 HNCACHED_NAME_RESOLUTION_FAILURE ...............................................297 Chapter 36 ICCPD System Log Messages 299

ICCPD_ASSERT_SOFT .................................................................................299 ICCPD_OPEN_ERROR .................................................................................299 ICCPD_READ_ERROR .................................................................................300 ICCPD_WRITE_ERROR ................................................................................300 Chapter 37 IDP System Log Messages 301

IDP_APPDDOS_APP_ATTACK_EVENT ........................................................301 IDP_APPDDOS_APP_STATE_EVENT ...........................................................301 IDP_ATTACK_LOG_EVENT ..........................................................................302 IDP_DAEMON_INIT_FAILED .......................................................................302 IDP_INTERNAL_ERROR ..............................................................................302 IDP_POLICY_COMPILATION_FAILED ..........................................................302 IDP_POLICY_LOAD_FAILED ........................................................................303 IDP_POLICY_LOAD_SUCCEEDED ...............................................................303 IDP_POLICY_UNLOAD_FAILED ...................................................................303 IDP_POLICY_UNLOAD_SUCCEEDED ..........................................................303 IDP_SCHEDULEDUPDATE_START_FAILED .................................................304 IDP_SCHEDULED_UPDATE_STARTED ........................................................304 IDP_SECURITY_INSTALL_RESULT ...............................................................304 IDP_SESSION_LOG_EVENT .........................................................................304 IDP_SIGNATURE_LICENSE_EXPIRED ..........................................................304 Chapter 38 JADE System Log Messages 307

JADE_ATTRIBUTES_TOO_LONG ..................................................................307 JADE_AUTH_FAILURE .................................................................................307 JADE_AUTH_SUCCESS ................................................................................307 JADE_EXEC_ERROR ....................................................................................308 JADE_PAM_ERROR .....................................................................................308 JADE_PAM_NO_LOCAL_USER .....................................................................308 JADE_SOCKET_ERROR ...............................................................................308

Table of Contents

xxix

JUNOS 10.1 System Log Messages Reference

Chapter 39

JCS System Log Messages

309

JCS_BBD_LOAD_FAILURE ...........................................................................309 JCS_BBD_LOCAL_MISMATCH ......................................................................309 JCS_BBD_NOT_FOUND ...............................................................................309 JCS_BBD_NOT_VALID .................................................................................310 JCS_BBD_PARSE_ERROR ............................................................................310 JCS_BBD_PEER_MISMATCH ........................................................................310 JCS_BBD_SYSTEM_CONFLICT .....................................................................310 JCS_EXT_LINK_STATE .................................................................................311 JCS_INVALID_BANDWIDTH_ERROR ...........................................................311 JCS_KERNEL_RSD_LINK_DOWN .................................................................311 JCS_KERNEL_RSD_LINK_ENABLED .............................................................311 JCS_MM_COMMUNICATION_ERROR ..........................................................312 JCS_MM_COMMUNICATION_OK .................................................................312 JCS_PEER_BLADE_STATE ............................................................................312 JCS_READ_BANDWIDTH_ERROR ...............................................................312 JCS_READ_BBD_ERROR ..............................................................................312 JCS_RSD_LINK_STATE ................................................................................313 JCS_SWITCH_BANDWIDTH_CONFIG ..........................................................313 JCS_SWITCH_COMMUNICATION_ERROR ...................................................313 JCS_SWITCH_COMMUNICATION_OK ..........................................................313 Chapter 40 JDIAMETERD System Log Messages 315

JDIAMETERD_FUNC_ACCEPT_FAIL ............................................................315 JDIAMETERD_FUNC_ACCEPT_NOT_FOUND ...............................................315 JDIAMETERD_FUNC_OUT_OF_SYNC ..........................................................315 JDIAMETERD_FUNC_SOCK_BIND_FAIL ......................................................316 JDIAMETERD_FUNC_SOCK_CREATE_FAIL ..................................................316 JDIAMETERD_FUNC_SOCK_LISTEN_FAIL ...................................................316 JDIAMETERD_MEMRLIM_REQUEST_FAIL ...................................................316 Chapter 41 JSRPD System Log Messages 317

JSRPD_DAEMONIZE_FAILED ......................................................................317 JSRPD_DUPLICATE ......................................................................................317 JSRPD_NOT_ROOT .....................................................................................317 JSRPD_PID_FILE_LOCK ...............................................................................318 JSRPD_PID_FILE_UPDATE ..........................................................................318 JSRPD_SOCKET_CREATION_FAILURE ........................................................318 JSRPD_SOCKET_LISTEN_FAILURE ..............................................................318 JSRPD_SOCKET_RECV_HB_FAILURE ..........................................................319 JSRPD_USAGE .............................................................................................319

xxx

Table of Contents

Table of Contents

Chapter 42

KMD System Log Messages

321

KMD_CFG_IF_ID_POOL_NOT_FOUND ........................................................321 KMD_CFG_IF_ID_POOL_NO_ENTRY ...........................................................321 KMD_CFG_IF_ID_POOL_NO_INTERFACE ...................................................321 KMD_CFG_IF_ID_POOL_RETURN_FAILED ..................................................322 KMD_DPD_FAILOVER_MANUAL_TUNNEL ..................................................322 KMD_DPD_FAILOVER_MAX_ATTEMPTS ....................................................322 KMD_DPD_FAILOVER_NO_ACTIVE_PEER ..................................................323 KMD_DPD_FAILOVER_NO_BACKUP_PEER ................................................323 KMD_DPD_FAILOVER_NO_TUNNEL_CFG ...................................................323 KMD_DPD_IKE_SERVER_NOT_FOUND ......................................................323 KMD_DPD_INVALID_ADDRESS ..................................................................324 KMD_DPD_INVALID_SEQUENCE_NUMBER ................................................324 KMD_DPD_NO_LOCAL_ADDRESS ..............................................................324 KMD_DPD_REMOTE_ADDRESS_CHANGED ................................................324 KMD_DPD_REMOTE_PEER_NOT_FOUND ..................................................325 KMD_DPD_UNEXPECTED_IKE_STATUS .....................................................325 KMD_PM_AUTH_ALGORITHM_INVALID .....................................................325 KMD_PM_DUPLICATE_LIFE_DURATION .....................................................325 KMD_PM_DYNAMIC_SA_INSTALL_FAILED .................................................326 KMD_PM_ENCRYPTION_INVALID ..............................................................326 KMD_PM_IKE_SERVER_LOOKUP_FAILED ..................................................326 KMD_PM_IKE_SERVER_NOT_FOUND ........................................................326 KMD_PM_IKE_SRV_NOT_FOUND_CREATE ................................................327 KMD_PM_IKE_SRV_NOT_FOUND_DELETE .................................................327 KMD_PM_ILLEGAL_REMOTE_GW_ID .........................................................327 KMD_PM_INCONSISTENT_P2_IDS ..............................................................328 KMD_PM_INVALID_LIFE_TYPE ...................................................................328 KMD_PM_KEY_NOT_SUPPORTED ..............................................................328 KMD_PM_LIFETIME_DUPLICATE ................................................................328 KMD_PM_LIFETIME_LENGTH_UNEQUAL ...................................................329 KMD_PM_LIFETIME_NO_DURATION ..........................................................329 KMD_PM_LIFETIME_TYPE_UNDEFINED .....................................................329 KMD_PM_LIFETIME_UNITS_INVALID .........................................................330 KMD_PM_NEW_GROUP_UNSUPPORTED ...................................................330 KMD_PM_NO_LIFETIME .............................................................................330 KMD_PM_NO_LIFE_TYPE ...........................................................................330 KMD_PM_NO_PROPOSAL_FOR_PHASE1 ...................................................331 KMD_PM_NO_SPD_PHASE1_FUNC_PTR ....................................................331 KMD_PM_P1_POLICY_LOOKUP_FAILURE ..................................................331 KMD_PM_P2_POLICY_LOOKUP_FAILURE ..................................................331 KMD_PM_PHASE1_GROUP_UNREADABLE .................................................332 KMD_PM_PHASE1_GROUP_UNSPECIFIED .................................................332 KMD_PM_PHASE1_IKE_SRV_NOT_FOUND ................................................332 KMD_PM_PHASE1_NO_IDENTITIES ...........................................................332 KMD_PM_PHASE1_NO_SPD_HANDLER .....................................................333 KMD_PM_PHASE1_POLICY_LOOKUP_FAIL ................................................333 KMD_PM_PHASE1_POLICY_NOT_FOUND ..................................................333

Table of Contents

xxxi

JUNOS 10.1 System Log Messages Reference

KMD_PM_PHASE1_POLICY_SEARCH_FAIL .................................................333 KMD_PM_PHASE1_PROTO_INVALID ..........................................................334 KMD_PM_PHASE1_PROTO_NOT_ISAKMP ..................................................334 KMD_PM_PHASE1_PROTO_TWICE ............................................................334 KMD_PM_PHASE1_TXFORM_INCOMPLETE ...............................................334 KMD_PM_PHASE1_TXFORM_INVALID .......................................................335 KMD_PM_PHASE2_IDENTITY_MISMATCH ..................................................335 KMD_PM_PHASE2_NOTIF_UNKNOWN ......................................................335 KMD_PM_PHASE2_POLICY_LOOKUP_FAIL ................................................335 KMD_PM_PHASE2_SELECTOR_UNDEFINED ..............................................336 KMD_PM_PROPOSAL_NO_AUTH ................................................................336 KMD_PM_PROPOSAL_NO_ENCRYPTION ...................................................336 KMD_PM_PROPOSAL_NO_KEY_LENGTH ...................................................337 KMD_PM_PROPOSAL_NULL_ESP ...............................................................337 KMD_PM_PROPOSAL_PROTOCOL_INVALID ..............................................337 KMD_PM_PROTO_INVALID ........................................................................337 KMD_PM_PROTO_IPCOMP_UNSUPPORTED ..............................................338 KMD_PM_PROTO_ISAKMP_RESV_UNSUPP ................................................338 KMD_PM_PROTO_NOT_NEGOTIATED .......................................................338 KMD_PM_REMOTE_PEER_INVALID ............................................................338 KMD_PM_SA_CFG_NOT_FOUND ................................................................339 KMD_PM_SA_DELETE_REJECT ...................................................................339 KMD_PM_SA_INDEX_GEN_FAILED .............................................................339 KMD_PM_SA_PEER_ABSENT ......................................................................339 KMD_PM_SA_PEER_NOT_FOUND ..............................................................340 KMD_PM_SPI_DELETE_REJECT ..................................................................340 KMD_PM_UNEQUAL_PAYLOAD_LENGTH ...................................................340 KMD_PM_UNINITIALISE_ERROR ................................................................340 KMD_PM_UNINITIALIZE_FAILED ................................................................341 KMD_PM_UNKNOWN_P1_IDENTITIES .......................................................341 KMD_PM_UNKNOWN_PHASE2_ENTITIES ..................................................341 KMD_PM_UNKNOWN_QM_NOTIFICATION ................................................342 KMD_PM_UNSUPPORTED_KEY ..................................................................342 KMD_PM_UNSUPPORTED_MODE ..............................................................342 KMD_SNMP_EXTRA_RESPONSE .................................................................342 KMD_SNMP_FATAL_ERROR .......................................................................343 KMD_SNMP_IKE_SERVER_NOT_FOUND ....................................................343 KMD_SNMP_MALLOC_FAILED ....................................................................343 KMD_SNMP_PIC_CONNECTION_FAILED ....................................................343 KMD_SNMP_PIC_NO_RESPONSE ...............................................................344 KMD_SNMP_PIC_SLOT_NOT_FOUND .........................................................344 KMD_VPN_DFBIT_STATUS_MSG .................................................................344 KMD_VPN_DOWN_ALARM_USER ...............................................................344 KMD_VPN_UP_ALARM_USER .....................................................................345 Chapter 43 L2ALD System Log Messages 347

L2ALD_DUPLICATE_RBEB_MAC .................................................................347 L2ALD_GENCFG_OP_FAILED ......................................................................347 L2ALD_IPC_MESSAGE_ERROR ....................................................................348

xxxii

Table of Contents

Table of Contents

L2ALD_IPC_MESSAGE_INVALID ..................................................................348 L2ALD_IPC_MESSAGE_SEND_FAILED .........................................................348 L2ALD_IPC_PIPE_WRITE_ERROR ...............................................................348 L2ALD_MAC_LIMIT_REACHED_BD .............................................................349 L2ALD_MAC_LIMIT_REACHED_GLOBAL .....................................................349 L2ALD_MAC_LIMIT_REACHED_IF ...............................................................350 L2ALD_MAC_LIMIT_REACHED_IFBD ..........................................................350 L2ALD_MAC_LIMIT_REACHED_RTT ...........................................................350 L2ALD_MAC_LIMIT_RESET_BD ...................................................................351 L2ALD_MAC_LIMIT_RESET_GLOBAL ..........................................................351 L2ALD_MAC_LIMIT_RESET_IF ....................................................................351 L2ALD_MAC_LIMIT_RESET_RTT .................................................................352 L2ALD_MAC_MOVE_NOTIFICATION ...........................................................352 L2ALD_MALLOC_FAILED ............................................................................352 L2ALD_MANAGER_CONNECT .....................................................................353 L2ALD_NAME_LENGTH_IF_DEVICE ............................................................353 L2ALD_NAME_LENGTH_IF_FAMILY ............................................................353 L2ALD_NAME_LENGTH_IF_LOGICAL ..........................................................353 L2ALD_PBBN_IFL_REVA .............................................................................354 L2ALD_PBBN_REINSTATE_IFBDS ...............................................................354 L2ALD_PBBN_RETRACT_IFBDS ..................................................................355 L2ALD_PIP_IFD_READ_RETRY ...................................................................355 Chapter 44 L2CPD System Log Messages 357

L2CPD_ASSERT ...........................................................................................357 L2CPD_ASSERT_SOFT .................................................................................357 L2CPD_EXIT ................................................................................................358 L2CPD_KERNEL_VERSION ..........................................................................358 L2CPD_KERNEL_VERSION_OLD .................................................................358 L2CPD_KERNEL_VERSION_UNSUPP ...........................................................359 L2CPD_MEMORY_EXCESSIVE .....................................................................359 L2CPD_MGMT_TIMEOUT ............................................................................359 L2CPD_MIRROR_ERROR ............................................................................360 L2CPD_MIRROR_VERSION_MISMATCH ......................................................360 L2CPD_PPM_READ_ERROR ........................................................................360 L2CPD_PPM_WRITE_ERROR ......................................................................361 L2CPD_RUNTIME_MODULE ........................................................................361 L2CPD_RUNTIME_OPERATION ...................................................................361 L2CPD_RUNTIME_TASK ..............................................................................362 L2CPD_RUNTIME_TOTAL ...........................................................................362 L2CPD_TASK_BEGIN ...................................................................................362 L2CPD_TASK_CHILD_KILLED .....................................................................362 L2CPD_TASK_CHILD_STOPPED ..................................................................363 L2CPD_TASK_FORK ....................................................................................363 L2CPD_TASK_GETWD .................................................................................363 L2CPD_TASK_MASTERSHIP ........................................................................363 L2CPD_TASK_NO_REINIT ...........................................................................364 L2CPD_TASK_PID_CLOSE ...........................................................................364 L2CPD_TASK_PID_LOCK ............................................................................364

Table of Contents

xxxiii

JUNOS 10.1 System Log Messages Reference

L2CPD_TASK_PID_WRITE ...........................................................................364 L2CPD_TASK_REINIT ..................................................................................365 L2CPD_TASK_SIGNAL_IGNORE ...................................................................365 L2CPD_TERMINATE_ACTIVE ......................................................................365 L2CPD_TERMINATE_SIGNAL ......................................................................365 L2CPD_TRACE_FAILED ...............................................................................366 L2CPD_XSTP_SHUTDOWN_FAILED ............................................................366 Chapter 45 L2TPD System Log Messages 367

L2TPD_COS_PROFILE_ADD ........................................................................367 L2TPD_COS_PROFILE_DELETE ...................................................................367 L2TPD_DB_ADD_FAILED ............................................................................368 L2TPD_DB_DELETE_FAILED .......................................................................368 L2TPD_DB_INIT_FAILED .............................................................................368 L2TPD_DB_TUN_GRP_ALLOC_FAILED ........................................................368 L2TPD_DEFAULT_PROTO_CREATE_FAIL ...................................................369 L2TPD_EVLIB_CREATE_FAILED ..................................................................369 L2TPD_EVLIB_FD_DEREGISTER_FAILED ....................................................369 L2TPD_EVLIB_FD_DESELECT_FAILED ........................................................369 L2TPD_EVLIB_FD_NOT_REGISTERED .........................................................369 L2TPD_EVLIB_FD_SELECT_FAILED .............................................................370 L2TPD_EVLIB_TIMER_CLEAR_FAILED ........................................................370 L2TPD_EVLIB_TIMER_SET_FAILED .............................................................370 L2TPD_FILTER_FILE_OPEN_FAILED ...........................................................370 L2TPD_GLOBAL_CFG_ADD_FAILED ............................................................371 L2TPD_GLOBAL_CFG_CHANGE_FAILED .....................................................371 L2TPD_GLOBAL_CFG_DELETE_FAILED ......................................................371 L2TPD_IFD_ADD_FAILED ...........................................................................371 L2TPD_IFD_DELETE_FAILED ......................................................................372 L2TPD_IFD_MSG_REGISTER_FAILED ..........................................................372 L2TPD_IFD_ROOT_ALLOC_FAILED ............................................................372 L2TPD_IFL_ADD_FAILED ............................................................................372 L2TPD_IFL_DELETE_FAILED .......................................................................373 L2TPD_IFL_MSG_REGISTER_FAILED ...........................................................373 L2TPD_IFL_NOT_FOUND ............................................................................373 L2TPD_IFL_ROOT_ALLOC_FAILED .............................................................373 L2TPD_INSTANCE_CREATE_FAILED ...........................................................374 L2TPD_INSTANCE_RESTART_FAILED .........................................................374 L2TPD_INTERFACE_ID_NOT_FOUND .........................................................374 L2TPD_MESSAGE_REGISTER_FAILED .........................................................374 L2TPD_MLPPP_BUNDLE_ALLOC_FAILED ...................................................375 L2TPD_MLPPP_BUNDLE_CREATE_FAILED .................................................375 L2TPD_MLPPP_BUNDLE_INVALID_ID .........................................................375 L2TPD_MLPPP_COPY_CFG_FAILED ............................................................375 L2TPD_MLPPP_ID_ALLOC_FAILED .............................................................376 L2TPD_MLPPP_ID_BITMAP_ALLOC_FAIL ...................................................376 L2TPD_MLPPP_ID_NODE_ADD_FAILED .....................................................376 L2TPD_MLPPP_ID_ROOT_ALLOC_FAILED ..................................................376 L2TPD_MLPPP_LINK_CREATE_FAILED .......................................................377

xxxiv

Table of Contents

Table of Contents

L2TPD_MLPPP_LINK_MAX_EXCEEDED ......................................................377 L2TPD_MLPPP_POOL_ADDRESS_FAILED ...................................................377 L2TPD_MLPPP_SESSION_CREATE_FAIL .....................................................377 L2TPD_MLPPP_SESSION_DELETE_FAIL ......................................................378 L2TPD_MLPPP_SPEED_MISMATCH ............................................................378 L2TPD_NH_DELETE_FAILED .......................................................................378 L2TPD_POLICER_ADD_FAILED ...................................................................378 L2TPD_POLICER_PROFILE_DEL_FAILED ....................................................379 L2TPD_POOL_ADDRESS_FAILED ...............................................................379 L2TPD_POOL_ASSIGN_ADDRESS_FAILED ..................................................379 L2TPD_PPP_ROUTE_ADD_FAILED .............................................................379 L2TPD_PPP_ROUTE_DELETE_FAILED ........................................................380 L2TPD_PROFILE_NOT_FOUND ...................................................................380 L2TPD_PROFILE_NO_RADIUS_SERVERS ....................................................380 L2TPD_RADIUS_ACCT_PORT_ZERO ...........................................................380 L2TPD_RADIUS_GETHOSTNAME_FAILED ...................................................381 L2TPD_RADIUS_RT_INST_ENOENT ............................................................381 L2TPD_RADIUS_RT_INST_NOT_FOUND .....................................................381 L2TPD_RADIUS_SERVER_NOT_FOUND ......................................................381 L2TPD_RADIUS_SRC_ADDR_BIND_FAIL .....................................................382 L2TPD_RADIUS_SRC_ADDR_ENOENT ........................................................382 L2TPD_RPD_ASYNC_UNREG_FAILED .........................................................382 L2TPD_RPD_ROUTE_ADD_CB_FAILED .......................................................382 L2TPD_RPD_ROUTE_ADD_FAILED .............................................................383 L2TPD_RPD_ROUTE_DELETE_CB_FAILED .................................................383 L2TPD_RPD_ROUTE_DELETE_FAILED .......................................................383 L2TPD_RPD_ROUTE_PREFIX_TOO_LONG ..................................................383 L2TPD_RPD_SESS_CREATE_FAILED ...........................................................384 L2TPD_RPD_SESS_HANDLE_ALLOC_FAIL ..................................................384 L2TPD_RPD_SOCKET_ALLOC_FAILED ........................................................384 L2TPD_RPD_TBL_LOCATE_BY_NAME ........................................................384 L2TPD_RPD_TBL_LOCATE_FAILED ............................................................385 L2TPD_RPD_VERSION_MISMATCH ............................................................385 L2TPD_RTSLIB_ASYNC_OPEN_FAILED .......................................................385 L2TPD_RTSLIB_OPEN_FAILED ....................................................................385 L2TPD_SERVER_START_FAILED .................................................................386 L2TPD_SERVICE_NH_ADD_FAILED ............................................................386 L2TPD_SERVICE_NH_DELETE_FAILED .......................................................386 L2TPD_SESSION_CFG_ADD_ERROR ...........................................................386 L2TPD_SESSION_CFG_ADD_FAILED ...........................................................387 L2TPD_SESSION_CFG_DELETE_FAILED .....................................................387 L2TPD_SESSION_DELETE_FAILED ..............................................................387 L2TPD_SESSION_IFF_NOT_FOUND ............................................................387 L2TPD_SESSION_IFL_ADD_FAILED ............................................................388 L2TPD_SESSION_IFL_ALLOC_FAILED .........................................................388 L2TPD_SESSION_IFL_CLI_TREE_ALLOC .....................................................388 L2TPD_SESSION_IFL_DELETED ..................................................................388 L2TPD_SESSION_IFL_DELETE_FAILED .......................................................389 L2TPD_SESSION_IFL_GET_FAILED .............................................................389 L2TPD_SESSION_IFL_NOT_EQUAL .............................................................389 L2TPD_SESSION_IFL_NOT_FOUND ............................................................389

Table of Contents

xxxv

JUNOS 10.1 System Log Messages Reference

L2TPD_SESSION_IFL_OCCUPIED ................................................................390 L2TPD_SESSION_IFL_REMOVE_FAILED .....................................................390 L2TPD_SESSION_INVALID_PEER_IP ...........................................................390 L2TPD_SESSION_ROUTE_ADD_FAILED ......................................................390 L2TPD_SESSION_RT_TBL_NOT_FOUND .....................................................391 L2TPD_SESSION_TUNNEL_ID_MISMATCH .................................................391 L2TPD_SETSOCKOPT_FAILED ....................................................................391 L2TPD_SET_ASYNC_CONTEXT ...................................................................391 L2TPD_SHOW_MULTILINK .........................................................................392 L2TPD_SHOW_SESSION .............................................................................392 L2TPD_SHOW_TUNNEL ..............................................................................392 L2TPD_SOCKET_FAILED .............................................................................392 L2TPD_SUBUNIT_ROUTE_ALLOC_FAILED ..................................................393 L2TPD_TRACE_FILE_OPEN_FAILED ...........................................................393 L2TPD_TUNNEL_CFG_ADD_FAILED ...........................................................393 L2TPD_TUNNEL_CFG_ADD_INV_ADDR ......................................................393 L2TPD_TUNNEL_CFG_DELETE_FAILED ......................................................394 L2TPD_TUNNEL_DELETE_FAILED ..............................................................394 L2TPD_TUNNEL_DEST_IF_LOOKUP_FAIL ..................................................394 L2TPD_TUNNEL_GROUP_ADD_FAILED ......................................................394 L2TPD_TUNNEL_GROUP_CFG_ADD_FAIL ..................................................395 L2TPD_TUNNEL_GROUP_CFG_DEL_FAIL ...................................................395 L2TPD_TUNNEL_GROUP_CREATE_FAILED .................................................395 L2TPD_TUNNEL_GROUP_DELETE_FAILED .................................................395 L2TPD_TUNNEL_GROUP_IDX_MISMATCH .................................................396 L2TPD_TUNNEL_GROUP_RESTART_FAIL ...................................................396 L2TPD_USER_AUTHN_NOT_FOUND ...........................................................396 L2TPD_USER_AUTHN_ORDER_UNKNOWN ................................................396 L2TPD_USER_AUTHN_PWD_NOT_FOUND .................................................397 Chapter 46 LACPD System Log Messages 399

LACPD_MEMORY_ALLOCATION_FAILED ...................................................399 Chapter 47 LFMD System Log Messages 401

LFMD_RTSOCK_OPEN_FAILED ...................................................................401 Chapter 48 LIBESPTASK System Log Messages 403

LIBESPTASK_SNMP_CONN_PROG ..............................................................403 LIBESPTASK_SNMP_CONN_QUIT ...............................................................403 LIBESPTASK_SNMP_CONN_RETRY .............................................................403 LIBESPTASK_SNMP_INVALID_SOCKET .......................................................404 LIBESPTASK_SNMP_SOCKOPT_BLOCK ......................................................404 LIBESPTASK_SNMP_SOCKOPT_RECVBUF ..................................................404 LIBESPTASK_SNMP_SOCKOPT_SENDBUF ..................................................404

xxxvi

Table of Contents

Table of Contents

Chapter 49

LIBJNX System Log Messages

405

LIBJNX_AUDIT_ERROR ...............................................................................405 LIBJNX_COMPRESS_EXEC_FAILED .............................................................405 LIBJNX_DEFAULT_IP_ADDR_NOT_SET .......................................................406 LIBJNX_EVLIB_FAILURE ..............................................................................406 LIBJNX_EXEC_EXITED ................................................................................406 LIBJNX_EXEC_FAILED .................................................................................407 LIBJNX_EXEC_PIPE .....................................................................................407 LIBJNX_EXEC_SIGNALED ............................................................................407 LIBJNX_EXEC_WEXIT ..................................................................................408 LIBJNX_FILE_COPY_FAILED ........................................................................408 LIBJNX_FILE_SYSTEM_FAIL ........................................................................408 LIBJNX_FILE_SYSTEM_SPACE .....................................................................408 LIBJNX_INVALID_CHASSIS_ID .....................................................................409 LIBJNX_INVALID_RE_SLOT_ID ....................................................................409 LIBJNX_INVALID_XML_DATA ......................................................................409 LIBJNX_PRIV_LOWER_FAILED ....................................................................409 LIBJNX_PRIV_RAISE_FAILED ......................................................................410 LIBJNX_REPLICATE_RCP_ERROR ...............................................................410 LIBJNX_REPLICATE_RCP_EXEC_FAILED .....................................................410 LIBJNX_SNMP_ENGINE_FILE_FAILURE .......................................................411 LIBJNX_SNMP_ENGINE_SCAN_FAILURE .....................................................411 LIBJNX_SOCKET_FAILURE ..........................................................................411 LIBJNX_XML_DECODE_FAILED ..................................................................412 Chapter 50 LIBJSNMP System Log Messages 413

LIBJSNMP_CTX_FAILURE ............................................................................413 LIBJSNMP_IPC_ERROR ................................................................................413 LIBJSNMP_IPC_READ_ERROR .....................................................................413 LIBJSNMP_MTHD_API_UNKNOWN_TYPE ...................................................414 LIBJSNMP_NS_LOG_CRIT ............................................................................414 LIBJSNMP_NS_LOG_EMERG ........................................................................414 LIBJSNMP_NS_LOG_ERR .............................................................................415 LIBJSNMP_OID_GEN_FAILED ......................................................................415 LIBJSNMP_READ_LEN_ERR .........................................................................415 LIBJSNMP_RTMSIZE_MISMATCH_ERR ........................................................416 LIBJSNMP_SMS_HDR_ERR ..........................................................................416 LIBJSNMP_SMS_MSG_ERR ..........................................................................416 LIBJSNMP_SOCKET_OPEN_ERR ..................................................................416 LIBJSNMP_SOCKET_VER_MISMATCH .........................................................417 LIBJSNMP_TRAP_API_FAILURE ...................................................................417 LIBJSNMP_TRAP_UTILS_ERR ......................................................................417

Table of Contents

xxxvii

JUNOS 10.1 System Log Messages Reference

Chapter 51

LIBMSPRPC System Log Messages

419

LIBMSPRPC_CLIENT_INIT_FAILED ..............................................................419 LIBMSPRPC_CLIENT_KCOM_FAILED ..........................................................419 LIBMSPRPC_CLIENT_NO_CONNECTION .....................................................419 LIBMSPRPC_CLIENT_NO_REPLY .................................................................420 LIBMSPRPC_CLIENT_PIC_DOWN ................................................................420 LIBMSPRPC_CLIENT_WRONG_OUTPUT ......................................................420 Chapter 52 LICENSE System Log Messages 423

LICENSE_CONNECT_FAILURE .....................................................................423 LICENSE_CONN_TO_LI_CHECK_FAILURE ...................................................423 LICENSE_CONN_TO_LI_CHECK_SUCCESS ..................................................423 LICENSE_EXPIRED ......................................................................................424 LICENSE_GRACE_PERIOD_APPROACHING .................................................424 LICENSE_GRACE_PERIOD_EXCEEDED .......................................................424 LICENSE_GRACE_PERIOD_EXPIRED ..........................................................424 LICENSE_LIST_MANAGEMENT ....................................................................425 LICENSE_NEARING_EXPIRY ........................................................................425 LICENSE_READ_ERROR ..............................................................................425 LICENSE_REG_ERROR ................................................................................425 LICENSE_SIGNATURE_VERIFY_FAILED .......................................................426 LICENSE_UNKNOWN_RESPONSE_TYPE .....................................................426 LICENSE_VERIFICATION_FILE_ERROR .......................................................426 Chapter 53 LLDPD System Log Messages 427

LLDPD_SYSTEM ..........................................................................................427 Chapter 54 LOGIN System Log Messages 429

LOGIN_ABORTED ........................................................................................429 LOGIN_FAILED ............................................................................................429 LOGIN_FAILED_SET_CONTEXT ...................................................................429 LOGIN_FAILED_SET_LOGIN ........................................................................430 LOGIN_HOSTNAME_UNRESOLVED .............................................................430 LOGIN_INFORMATION ................................................................................430 LOGIN_LOCAL_PASSWORD ........................................................................430 LOGIN_MALFORMED_USER ........................................................................431 LOGIN_PAM_AUTHENTICATION_ERROR ....................................................431 LOGIN_PAM_ERROR ...................................................................................431 LOGIN_PAM_MAX_RETRIES .......................................................................431 LOGIN_PAM_STOP ......................................................................................431 LOGIN_PAM_USER_UNKNOWN ..................................................................432 LOGIN_PASSWORD_EXPIRED ....................................................................432 LOGIN_REFUSED ........................................................................................432

xxxviii

Table of Contents

Table of Contents

LOGIN_ROOT ..............................................................................................432 LOGIN_TIMED_OUT ....................................................................................433 Chapter 55 LPDFD System Log Messages 435

LPDFD_DYN_PDB_OPEN_FAILED ...............................................................435 LPDFD_DYN_REGISTER_FAILED .................................................................435 LPDFD_PCONN_SERVER ............................................................................435 Chapter 56 LRMUX System Log Messages 437

LRMUX_FAILED_EXEC ................................................................................437 LRMUX_LRPD_PID_LOCK ...........................................................................437 LRMUX_LRPD_PID_OPEN ...........................................................................437 LRMUX_LRPD_SEND_HUP ..........................................................................438 LRMUX_PID_LOCK ......................................................................................438 Chapter 57 MCSNOOPD System Log Messages 439

MCSNOOPD_MGMT_TIMEOUT ...................................................................439 Chapter 58 MIB2D System Log Messages 441

MIB2D_ATM_ERROR ...................................................................................441 MIB2D_CONFIG_CHECK_FAILED ................................................................441 MIB2D_FILE_OPEN_FAILURE ......................................................................442 MIB2D_IFD_IFDINDEX_FAILURE ................................................................442 MIB2D_IFD_IFINDEX_FAILURE ...................................................................442 MIB2D_IFL_IFINDEX_FAILURE ...................................................................443 MIB2D_IF_FLAPPING_MISSING ...................................................................443 MIB2D_KVM_FAILURE ................................................................................443 MIB2D_PMON_OVERLOAD_CLEARED_TRAP .............................................443 MIB2D_PMON_OVERLOAD_SET_TRAP .......................................................444 MIB2D_RTSLIB_READ_FAILURE .................................................................444 MIB2D_RTSLIB_SEQ_MISMATCH ................................................................444 MIB2D_SNMP_INDEX_ASSIGN ....................................................................445 MIB2D_SNMP_INDEX_DUPLICATE .............................................................445 MIB2D_SNMP_INDEX_UPDATE_STAT ........................................................445 MIB2D_SNMP_INDEX_WRITE .....................................................................446 MIB2D_SYSCTL_FAILURE ............................................................................446 MIB2D_TRAP_HEADER_FAILURE ...............................................................446 MIB2D_TRAP_SEND_FAILURE ....................................................................446 Chapter 59 MPLS_OAM System Log Messages 449

MPLS_OAM_FANOUT_LIMIT_REACHED .....................................................449 MPLS_OAM_INVALID_SOURCE_ADDRESS ..................................................449

Table of Contents

xxxix

JUNOS 10.1 System Log Messages Reference

MPLS_OAM_PATH_LIMIT_REACHED ..........................................................449 MPLS_OAM_SEND_FAILED .........................................................................450 MPLS_OAM_SOCKET_OPEN_FAILED ..........................................................450 MPLS_OAM_SOCKET_SELECT_FAILED .......................................................450 MPLS_OAM_TRACEROUTE_INTERRUPTED ................................................450 MPLS_OAM_TTL_EXPIRED .........................................................................451 MPLS_OAM_UNREACHABLE .......................................................................451 Chapter 60 NEXTHOP System Log Messages 453

NEXTHOP_COMPONENTS_LIMIT_REACHED ..............................................453 Chapter 61 NSD System Log Messages 455

NSD_MEMORY_ALLOC_FAILED ..................................................................455 NSD_RESTART_COMP_CFG_READ_FAILED ................................................455 NSD_SEC_NODE_COMP_SYNC_FAILED ......................................................455 Chapter 62 NSTRACED System Log Messages 457

NSTRACED_MEMORY_ALLOC_FAILED .......................................................457 NSTRACED_RESTART_CFG_READ_FAILED .................................................457 Chapter 63 PFE System Log Messages 459

PFE_ANALYZER_CFG_FAILED .....................................................................459 PFE_ANALYZER_SHIM_CFG_FAILED ..........................................................459 PFE_ANALYZER_TABLE_WRITE_FAILED ....................................................459 PFE_ANALYZER_TASK_FAILED ...................................................................460 PFE_CBF_UNSUPPORTED ...........................................................................460 PFE_COS_B2_ONE_CLASS ..........................................................................460 PFE_COS_B2_UNSUPPORTED ....................................................................460 PFE_FW_DELETE_MISMATCH_ERR ............................................................461 PFE_FW_IF_DIALER_ERR ...........................................................................461 PFE_FW_IF_INPUT_ERR .............................................................................461 PFE_FW_IF_OUTPUT_ERR ..........................................................................461 PFE_FW_PSF_DELETE_MISMATCH_ERR ....................................................462 PFE_FW_SYSLOG_ETH ...............................................................................462 PFE_FW_SYSLOG_IP ...................................................................................462 PFE_FW_SYSLOG_IP6_GEN ........................................................................462 PFE_FW_SYSLOG_IP6_ICMP .......................................................................463 PFE_FW_SYSLOG_IP6_TCP_UDP ................................................................463 PFE_MGCP_ADD_CA_PORT_FAIL ...............................................................463 PFE_MGCP_ADD_UA_PORT_FAIL ...............................................................463 PFE_MGCP_DEL_CA_PORT_FAIL ................................................................464 PFE_MGCP_DEL_UA_PORT_FAIL ................................................................464 PFE_MGCP_MEM_INIT_FAILED ...................................................................464 PFE_MGCP_REG_HDL_FAIL ........................................................................464

xl

Table of Contents

Table of Contents

PFE_NH_RESOLVE_THROTTLED ................................................................464 PFE_SCCP_ADD_PORT_FAIL .......................................................................465 PFE_SCCP_DEL_PORT_FAIL .......................................................................465 PFE_SCCP_REG_NAT_VEC_FAIL .................................................................465 PFE_SCCP_REG_RM_FAIL ...........................................................................465 PFE_SCCP_REG_VSIP_FAIL .........................................................................466 PFE_SCCP_RM_CLIENTID_FAIL ..................................................................466 PFE_SCREEN_CFG_ERROR .........................................................................466 PFE_SCREEN_CFG_EVENT ..........................................................................466 PFE_SCREEN_MT_CFG_ERROR ..................................................................466 PFE_SCREEN_MT_CFG_EVENT ...................................................................467 PFE_SFLOW_CONFIGURATION_FAILED .....................................................467 PFE_SFLOW_HARDWARE_CFG_FAILED .....................................................467 PFE_SIP_ADD_PORT_FAIL ..........................................................................467 PFE_SIP_DEL_PORT_FAIL ...........................................................................468 PFE_SIP_MEM_INIT_FAILED .......................................................................468 PFE_SIP_REG_HDL_FAIL .............................................................................468 PFE_USP_TRACE_BUFFER_CREATE ............................................................468 PFE_USP_TRACE_BUFFER_DELETE ............................................................468 PFE_USP_TRACE_BUFFER_LIMIT ................................................................469 PFE_USP_TRACE_BUFFER_MEM_FAIL ........................................................469 PFE_USP_TRACE_BUFFER_MODIFY ...........................................................469 Chapter 64 PFED System Log Messages 471

PFED_NOTIFICATION_STATS_FAILED ........................................................471 Chapter 65 PGCPD System Log Messages 473

PGCPD_SHUTDOWN ...................................................................................473 PGCPD_STARTUP ........................................................................................473 PGCPD_SWITCH_OVER ...............................................................................473 Chapter 66 PING System Log Messages 475

PING_EGRESS_JITTER_THRESH_EXCEED ...................................................475 PING_EGRESS_STDDEV_THRESH_EXCEED ................................................475 PING_EGRESS_THRESHOLD_EXCEEDED ....................................................475 PING_INGRESS_JTR_THRESH_EXCEED .......................................................476 PING_INGRESS_STDDV_THRESH_EXCEED .................................................476 PING_INGRESS_THRESHOLD_EXCEEDED ..................................................476 PING_PROBE_FAILED .................................................................................476 PING_RTT_JTR_THRESH_EXCEED ..............................................................477 PING_RTT_STDDV_THRESH_EXCEED .........................................................477 PING_RTT_THRESHOLD_EXCEEDED ..........................................................477 PING_TEST_COMPLETED ............................................................................477 PING_TEST_FAILED ....................................................................................478 PING_UNKNOWN_THRESH_TYPE_EXCEED ...............................................478

Table of Contents

xli

JUNOS 10.1 System Log Messages Reference

Chapter 67

PPMD System Log Messages

479

PPMD_ASSERT_SOFT ..................................................................................479 PPMD_OPEN_ERROR ..................................................................................479 PPMD_READ_ERROR ..................................................................................480 PPMD_WRITE_ERROR ................................................................................480 Chapter 68 PPPD System Log Messages 481

PPPD_AUTH_CREATE_FAILED ....................................................................481 PPPD_CHAP_AUTH_IN_PROGRESS ............................................................481 PPPD_CHAP_GETHOSTNAME_FAILED ........................................................481 PPPD_CHAP_INVALID_IDENTIFIER ............................................................482 PPPD_CHAP_INVALID_OPCODE .................................................................482 PPPD_CHAP_LOCAL_NAME_UNAVAILABLE ...............................................482 PPPD_CHAP_OPERATION_UNEXPECTED ...................................................482 PPPD_CHAP_REPLAY_ATTACK_DETECTED ...............................................483 PPPD_EVLIB_CREATE_FAILURE .................................................................483 PPPD_LOCAL_CREATE_FAILED ..................................................................483 PPPD_MEMORY_ALLOCATION_FAILURE ...................................................483 PPPD_PAP_GETHOSTNAME_FAILED ..........................................................484 PPPD_PAP_INVALID_IDENTIFIER ...............................................................484 PPPD_PAP_INVALID_OPCODE ...................................................................484 PPPD_PAP_LOCAL_PASSWORD_UNAVAIL .................................................484 PPPD_PAP_OPERATION_UNEXPECTED .....................................................485 PPPD_POOL_ADDRESSES_EXHAUSTED .....................................................485 PPPD_RADIUS_ADD_SERVER_FAILED .......................................................485 PPPD_RADIUS_ALLOC_PASSWD_FAILED ...................................................486 PPPD_RADIUS_CREATE_FAILED ................................................................486 PPPD_RADIUS_CREATE_REQ_FAILED ........................................................486 PPPD_RADIUS_GETHOSTNAME_FAILED ....................................................486 PPPD_RADIUS_MESSAGE_UNEXPECTED ...................................................487 PPPD_RADIUS_NO_VALID_SERVERS ..........................................................487 PPPD_RADIUS_OPEN_FAILED ....................................................................487 PPPD_RADIUS_ROUTE_INST_ENOENT .......................................................487 Chapter 69 PROFILER System Log Messages 489

PROFILER_RECONFIGURE_SIGHUP ............................................................489 Chapter 70 RDD System Log Messages 491

RDD_EVLIB_CREATE_FAILURE ...................................................................491 RDD_IFDEV_ADD_FAILURE ........................................................................491 RDD_IFDEV_DELETE_FAILURE ...................................................................491 RDD_IFDEV_GET_FAILURE .........................................................................492 RDD_IFDEV_INCOMPATIBLE_REVERT .......................................................492

xlii

Table of Contents

Table of Contents

RDD_IFDEV_INCOMPATIBLE_SWITCH .......................................................492 RDD_IFDEV_RETRY_NOTICE ......................................................................493 RDD_NEW_INTERFACE_STATE ..................................................................493 Chapter 71 RMOPD System Log Messages 495

RMOPD_ADDRESS_MULTICAST_INVALID ..................................................495 RMOPD_ADDRESS_SOURCE_INVALID .......................................................495 RMOPD_ADDRESS_STRING_FAILURE .........................................................495 RMOPD_ADDRESS_TARGET_INVALID ........................................................496 RMOPD_ICMP_ADDR_TYPE_UNSUPPORTED .............................................496 RMOPD_IFINDEX_NOT_ACTIVE .................................................................496 RMOPD_IFINDEX_NO_INFO .......................................................................496 RMOPD_IFNAME_NOT_ACTIVE ..................................................................497 RMOPD_IFNAME_NO_INFO ........................................................................497 RMOPD_ROUTING_INSTANCE_NO_INFO ...................................................497 RMOPD_TRACEROUTE_ERROR ..................................................................497 Chapter 72 RPD System Log Messages 499

RPD_ABORT ................................................................................................499 RPD_ACTIVE_TERMINATE ..........................................................................499 RPD_ASSERT ...............................................................................................500 RPD_ASSERT_SOFT ....................................................................................500 RPD_BFD_READ_ERROR ............................................................................501 RPD_BFD_WRITE_ERROR ..........................................................................501 RPD_BGP_NEIGHBOR_STATE_CHANGED ...................................................501 RPD_DYN_CFG_BUSY_SIGNAL_FAILED ......................................................501 RPD_DYN_CFG_GET_PROFILE_FAILED ......................................................502 RPD_DYN_CFG_GET_PROF_NAME_FAILED ................................................502 RPD_DYN_CFG_GET_SES_STATE_FAILED ..................................................502 RPD_DYN_CFG_GET_SES_TYPE_FAILED ....................................................502 RPD_DYN_CFG_GET_SNAPSHOT_FAILED ..................................................503 RPD_DYN_CFG_PDB_CLOSE_FAILED .........................................................503 RPD_DYN_CFG_PDB_OPEN_FAILED ..........................................................503 RPD_DYN_CFG_PROCESSING_FAILED .......................................................503 RPD_DYN_CFG_REGISTER_FAILED ............................................................504 RPD_DYN_CFG_REQUEST_ACK_FAILED ....................................................504 RPD_DYN_CFG_RESPONSE_SLOW .............................................................504 RPD_DYN_CFG_SCHEMA_OPEN_FAILED ...................................................504 RPD_DYN_CFG_SDB_CLOSE_FAILED .........................................................505 RPD_DYN_CFG_SDB_OPEN_FAILED ...........................................................505 RPD_DYN_CFG_SES_RECOVERY_FAILED ...................................................505 RPD_DYN_CFG_SET_CONTEXT_FAILED .....................................................505 RPD_ESIS_ADJDOWN .................................................................................506 RPD_ESIS_ADJUP ........................................................................................506 RPD_EXIT ...................................................................................................506 RPD_IFD_INDEXCOLLISION .......................................................................507 RPD_IFD_NAMECOLLISION ........................................................................507 RPD_IFL_INDEXCOLLISION ........................................................................507

Table of Contents

xliii

JUNOS 10.1 System Log Messages Reference

RPD_IFL_NAMECOLLISION .........................................................................508 RPD_IGMP_ACCOUNTING_OFF ..................................................................508 RPD_IGMP_ACCOUNTING_ON ....................................................................508 RPD_IGMP_ALL_SUBSCRIBERS_DELETED ..................................................508 RPD_IGMP_CFG_CREATE_ENTRY_FAILED .................................................509 RPD_IGMP_CFG_GROUP_OUT_OF_RANGE ................................................509 RPD_IGMP_CFG_INVALID_VALUE ...............................................................509 RPD_IGMP_CFG_SOURCE_OUT_OF_RANGE ...............................................510 RPD_IGMP_DYN_CFG_ALREADY_BOUND ..................................................510 RPD_IGMP_DYN_CFG_INVALID_STMT ........................................................510 RPD_IGMP_DYN_CFG_SES_ID_ADD_FAIL ..................................................510 RPD_IGMP_DYN_CFG_SES_ID_MISMATCH .................................................511 RPD_IGMP_JOIN .........................................................................................511 RPD_IGMP_LEAVE ......................................................................................511 RPD_IGMP_MEMBERSHIP_TIMEOUT ..........................................................512 RPD_IGMP_ROUTER_VERSION_MISMATCH ...............................................512 RPD_ISIS_ADJDOWN ..................................................................................512 RPD_ISIS_ADJUP .........................................................................................512 RPD_ISIS_ADJUPNOIP .................................................................................513 RPD_ISIS_LDP_SYNC ..................................................................................513 RPD_ISIS_LSPCKSUM ..................................................................................513 RPD_ISIS_NO_ROUTERID ...........................................................................514 RPD_ISIS_OVERLOAD .................................................................................514 RPD_KRT_CCC_IFL_MODIFY ......................................................................514 RPD_KRT_DELETED_RTT ...........................................................................515 RPD_KRT_IFA_GENERATION ......................................................................515 RPD_KRT_IFDCHANGE ...............................................................................515 RPD_KRT_IFDEST_GET ...............................................................................516 RPD_KRT_IFDGET .......................................................................................516 RPD_KRT_IFD_CELL_RELAY_INV_MODE ...................................................516 RPD_KRT_IFD_CELL_RELAY_NO_MODE ....................................................517 RPD_KRT_IFD_GENERATION ......................................................................517 RPD_KRT_IFL_CELL_RELAY_INV_MODE ....................................................517 RPD_KRT_IFL_CELL_RELAY_NO_MODE .....................................................517 RPD_KRT_IFL_GENERATION ......................................................................518 RPD_KRT_KERNEL_BAD_ROUTE ................................................................518 RPD_KRT_NEXTHOP_OVERFLOW ..............................................................518 RPD_KRT_NOIFD ........................................................................................519 RPD_KRT_VERSION ....................................................................................519 RPD_KRT_VERSIONNONE ..........................................................................520 RPD_KRT_VERSIONOLD .............................................................................520 RPD_KRT_VPLS_IFL_MODIFY .....................................................................520 RPD_L2VPN_LABEL_ALLOC_FAILED ..........................................................521 RPD_L2VPN_REMOTE_SITE_COLLISION ....................................................521 RPD_L2VPN_SITE_COLLISION ....................................................................521 RPD_LAYER2_VC_BFD_DOWN ...................................................................521 RPD_LAYER2_VC_BFD_UP .........................................................................522 RPD_LAYER2_VC_DOWN ...........................................................................522 RPD_LAYER2_VC_PING_DOWN ..................................................................522 RPD_LAYER2_VC_UP ..................................................................................522 RPD_LDP_BFD_DOWN ...............................................................................523

xliv

Table of Contents

Table of Contents

RPD_LDP_BFD_DOWN_TRACEROUTE_FAIL ..............................................523 RPD_LDP_BFD_UP ......................................................................................523 RPD_LDP_INTF_BLOCKED ..........................................................................523 RPD_LDP_INTF_UNBLOCKED .....................................................................524 RPD_LDP_NBRDOWN .................................................................................524 RPD_LDP_NBRUP .......................................................................................524 RPD_LDP_PING_DOWN ..............................................................................524 RPD_LDP_SESSIONDOWN ..........................................................................525 RPD_LDP_SESSIONUP ................................................................................525 RPD_LMP_ALLOC_ACK ...............................................................................525 RPD_LMP_ALLOC_REQUEST_TIMEOUT .....................................................525 RPD_LMP_CONTROL_CHANNEL .................................................................526 RPD_LMP_NO_CALLBACK ..........................................................................526 RPD_LMP_NO_MEMORY ............................................................................526 RPD_LMP_NO_PEER ...................................................................................526 RPD_LMP_PEER ..........................................................................................527 RPD_LMP_PEER_IFL ...................................................................................527 RPD_LMP_PEER_INDEX ..............................................................................527 RPD_LMP_RESOURCE ................................................................................527 RPD_LMP_RESOURCE_NO_LINK ................................................................528 RPD_LMP_SEND .........................................................................................528 RPD_LMP_SEND_ALLOCATION_MESSAGE .................................................528 RPD_LMP_SYSFAIL .....................................................................................528 RPD_LMP_TE_LINK .....................................................................................529 RPD_LMP_TE_LINK_INDEX ........................................................................529 RPD_LMP_UNEXPECTED_OPCODE ............................................................529 RPD_LOCK_FLOCKED .................................................................................529 RPD_LOCK_LOCKED ..................................................................................530 RPD_MC_CFG_CREATE_ENTRY_FAILED .....................................................530 RPD_MC_COSD_WRITE_ERROR .................................................................530 RPD_MC_DESIGNATED_PE_CHANGE .........................................................531 RPD_MC_DYN_CFG_ALREADY_BOUND .....................................................531 RPD_MC_DYN_CFG_SES_ID_ADD_FAIL ......................................................531 RPD_MC_DYN_CFG_SES_ID_MISMATCH ....................................................531 RPD_MC_LOCAL_DESIGNATED_PE ............................................................532 RPD_MC_OIF_REJECT .................................................................................532 RPD_MC_OIF_RE_ADMIT ............................................................................532 RPD_MGMT_TIMEOUT ................................................................................533 RPD_MIRROR_ERROR ................................................................................533 RPD_MIRROR_VERSION_MISMATCH .........................................................533 RPD_MLD_ACCOUNTING_OFF ...................................................................534 RPD_MLD_ACCOUNTING_ON .....................................................................534 RPD_MLD_ALL_SUBSCRIBERS_DELETED ...................................................534 RPD_MLD_CFG_CREATE_ENTRY_FAILED ..................................................534 RPD_MLD_CFG_GROUP_OUT_OF_RANGE ..................................................535 RPD_MLD_CFG_INVALID_VALUE ................................................................535 RPD_MLD_CFG_SOURCE_OUT_OF_RANGE ................................................535 RPD_MLD_DYN_CFG_ALREADY_BOUND ...................................................535 RPD_MLD_DYN_CFG_INVALID_STMT .........................................................536 RPD_MLD_DYN_CFG_SES_ID_ADD_FAIL ...................................................536 RPD_MLD_DYN_CFG_SES_ID_MISMATCH ..................................................536

Table of Contents

xlv

JUNOS 10.1 System Log Messages Reference

RPD_MLD_JOIN ...........................................................................................537 RPD_MLD_LEAVE .......................................................................................537 RPD_MLD_MEMBERSHIP_TIMEOUT ...........................................................537 RPD_MLD_ROUTER_VERSION_MISMATCH ................................................537 RPD_MPLS_INTERFACE_ROUTE_ERROR ....................................................538 RPD_MPLS_INTF_MAX_LABELS_ERROR .....................................................538 RPD_MPLS_LSP_AUTOBW_NOTICE ............................................................538 RPD_MPLS_LSP_BANDWIDTH_CHANGE ....................................................538 RPD_MPLS_LSP_CHANGE ...........................................................................539 RPD_MPLS_LSP_DOWN ..............................................................................539 RPD_MPLS_LSP_SWITCH ............................................................................539 RPD_MPLS_LSP_UP ....................................................................................539 RPD_MPLS_OAM_LSP_PING_REPLY_ERR ...................................................540 RPD_MPLS_OAM_PING_REPLY_TIMEOUT ..................................................540 RPD_MPLS_OAM_READ_ERROR ................................................................540 RPD_MPLS_OAM_WRITE_ERROR ...............................................................540 RPD_MPLS_PATH_BANDWIDTH_CHANGE .................................................541 RPD_MPLS_PATH_BFD_DOWN ..................................................................541 RPD_MPLS_PATH_BFD_UP .........................................................................541 RPD_MPLS_PATH_BW_NOT_AVAILABLE ....................................................541 RPD_MPLS_PATH_DOWN ...........................................................................542 RPD_MPLS_PATH_PING_DOWN .................................................................542 RPD_MPLS_PATH_UP .................................................................................542 RPD_MPLS_TABLE_ROUTE_ERROR ............................................................542 RPD_MSDP_PEER_DOWN ..........................................................................543 RPD_MSDP_PEER_UP .................................................................................543 RPD_MSDP_SRC_ACTIVE_OVER_LIMIT ......................................................543 RPD_MSDP_SRC_ACTIVE_OVER_THRESH ..................................................543 RPD_MSDP_SRC_ACTIVE_UNDER_LIMIT ....................................................544 RPD_MSDP_SRC_ACTIVE_UNDER_THRESH ...............................................544 RPD_OSPF_CFGNBR_P2P ...........................................................................544 RPD_OSPF_LDP_SYNC ................................................................................545 RPD_OSPF_NBRDOWN ...............................................................................545 RPD_OSPF_NBRUP .....................................................................................545 RPD_OSPF_OVERLOAD ..............................................................................546 RPD_OS_MEMHIGH ....................................................................................546 RPD_PARSE_BAD_LR_NAME ......................................................................546 RPD_PARSE_BAD_OPTION .........................................................................547 RPD_PARSE_CMD_ARG ..............................................................................547 RPD_PARSE_CMD_DUPLICATE ...................................................................547 RPD_PARSE_CMD_EXTRA ..........................................................................547 RPD_PIM_NBRDOWN .................................................................................548 RPD_PIM_NBRUP ........................................................................................548 RPD_PPM_READ_ERROR ............................................................................548 RPD_PPM_WRITE_ERROR ..........................................................................548 RPD_RA_CFG_CREATE_ENTRY_FAILED .....................................................549 RPD_RA_CFG_INVALID_VALUE ..................................................................549 RPD_RA_DYN_CFG_ALREADY_BOUND ......................................................549 RPD_RA_DYN_CFG_INVALID_STMT ...........................................................550 RPD_RA_DYN_CFG_SES_ID_ADD_FAIL ......................................................550 RPD_RA_DYN_CFG_SES_ID_MISMATCH .....................................................550

xlvi

Table of Contents

Table of Contents

RPD_RDISC_CKSUM ...................................................................................550 RPD_RDISC_NOMULTI ................................................................................551 RPD_RDISC_NORECVIF ..............................................................................551 RPD_RDISC_SOLICITADDR .........................................................................552 RPD_RDISC_SOLICITICMP ..........................................................................552 RPD_RDISC_SOLICITLEN ............................................................................552 RPD_RIP_AUTH_REQUEST .........................................................................553 RPD_RIP_AUTH_UPDATE ...........................................................................553 RPD_RIP_JOIN_BROADCAST ......................................................................553 RPD_RIP_JOIN_MULTICAST ........................................................................553 RPD_RSVP_BACKUP_DOWN ......................................................................554 RPD_RSVP_BYPASS_DOWN .......................................................................554 RPD_RSVP_BYPASS_UP ..............................................................................554 RPD_RSVP_LSP_SWITCH ............................................................................554 RPD_RSVP_MAXIMUM_SESSIONS ..............................................................555 RPD_RSVP_NBRDOWN ...............................................................................555 RPD_RSVP_NBRUP .....................................................................................555 RPD_RT_CFG_BR_CONFLICT ......................................................................555 RPD_RT_CFG_CREATE_ENTRY_FAILED .....................................................556 RPD_RT_CFG_INVALID_VALUE ...................................................................556 RPD_RT_DUPLICATE_RD ............................................................................556 RPD_RT_ERROR .........................................................................................556 RPD_RT_IFUP .............................................................................................557 RPD_RT_PATH_LIMIT_BELOW ...................................................................557 RPD_RT_PATH_LIMIT_REACHED ................................................................557 RPD_RT_PATH_LIMIT_WARNING ...............................................................557 RPD_RT_PREFIX_LIMIT_BELOW .................................................................558 RPD_RT_PREFIX_LIMIT_REACHED .............................................................558 RPD_RT_PREFIX_LIMIT_WARNING ............................................................558 RPD_RT_SHOWMODE ................................................................................559 RPD_RT_TAG_ID_ALLOC_FAILED ...............................................................559 RPD_SCHED_CALLBACK_LONGRUNTIME ...................................................559 RPD_SCHED_CUMULATIVE_LONGRUNTIME ..............................................559 RPD_SCHED_MODULE_LONGRUNTIME .....................................................560 RPD_SCHED_TASK_LONGRUNTIME ...........................................................560 RPD_SIGNAL_TERMINATE ..........................................................................560 RPD_SNMP_CONN_PROG ...........................................................................560 RPD_SNMP_CONN_QUIT ............................................................................561 RPD_SNMP_CONN_RETRY .........................................................................561 RPD_SNMP_INVALID_SOCKET ...................................................................561 RPD_SNMP_SOCKOPT_BLOCK ...................................................................561 RPD_SNMP_SOCKOPT_RECVBUF ...............................................................562 RPD_SNMP_SOCKOPT_SENDBUF ...............................................................562 RPD_START ................................................................................................562 RPD_SYSTEM ..............................................................................................562 RPD_TASK_BEGIN .......................................................................................563 RPD_TASK_CHILDKILLED ...........................................................................563 RPD_TASK_CHILDSTOPPED .......................................................................563 RPD_TASK_DYN_REINIT .............................................................................563 RPD_TASK_FORK .......................................................................................564 RPD_TASK_GETWD ....................................................................................564

Table of Contents

xlvii

JUNOS 10.1 System Log Messages Reference

RPD_TASK_MASTERSHIP ............................................................................564 RPD_TASK_NOREINIT .................................................................................564 RPD_TASK_PIDCLOSED ..............................................................................565 RPD_TASK_PIDFLOCK ................................................................................565 RPD_TASK_PIDWRITE ................................................................................565 RPD_TASK_REINIT ......................................................................................565 RPD_TASK_SIGNALIGNORE ........................................................................566 RPD_TRACE_FAILED ...................................................................................566 Chapter 73 RT System Log Messages 567

RT_FLOW_SESSION_CLOSE ........................................................................567 RT_FLOW_SESSION_CREATE .....................................................................567 RT_FLOW_SESSION_DENY .........................................................................567 RT_GTP_BAD_LICENSE ...............................................................................568 RT_GTP_DEL_TUNNEL_V0 ..........................................................................568 RT_GTP_DEL_TUNNEL_V1 ..........................................................................568 RT_GTP_PKT_APN_IE .................................................................................568 RT_GTP_PKT_DESCRIPTION_CHARGING ....................................................569 RT_GTP_PKT_DESCRIPTION_V0 .................................................................569 RT_GTP_PKT_DESCRIPTION_V1 .................................................................569 RT_GTP_PKT_ENDUSER_ADDR_IE_IPV4 ....................................................569 RT_GTP_PKT_GSNADDR_IE ........................................................................570 RT_GTP_PKT_IMSI_IE .................................................................................570 RT_GTP_PKT_MSISDN_IE ...........................................................................570 RT_GTP_PKT_RESULT .................................................................................570 RT_GTP_SANITY_EXTENSION_HEADER .....................................................571 RT_GTP_SYSTEM_ERROR ...........................................................................571 RT_H323_CALL_LIMIT_EXCEED .................................................................571 RT_H323_NAT_COOKIE_NOT_FOUND .......................................................571 RT_H323_RAS_REQ_FLOOD .......................................................................571 RT_IPSEC_BAD_SPI .....................................................................................572 RT_IPSEC_REPLAY ......................................................................................572 RT_MGCP_CALL_LIMIT_EXCEED ................................................................572 RT_MGCP_DECODE_FAIL ...........................................................................572 RT_MGCP_MEM_ALLOC_FAILED ................................................................573 RT_MGCP_REG_NAT_VEC_FAIL ..................................................................573 RT_MGCP_REG_RM_FAIL ............................................................................573 RT_MGCP_REM_NAT_VEC_FAIL .................................................................573 RT_MGCP_RM_CLIENTID_FAIL ...................................................................573 RT_MGCP_UNREG_BY_RM ..........................................................................574 RT_SCCP_CALL_LIMIT_EXCEED ..................................................................574 RT_SCCP_CALL_RATE_EXCEED ..................................................................574 RT_SCCP_DECODE_FAIL ............................................................................574 RT_SCCP_NAT_COOKIE_NOT_FOUND .......................................................574 RT_SCCP_REM_NAT_VEC_FAIL ..................................................................575 RT_SCCP_UNREG_RM_FAIL ........................................................................575 RT_SCREEN_ICMP ......................................................................................575 RT_SCREEN_ICMP_FLOOD .........................................................................575 RT_SCREEN_ICMP_FRAG ............................................................................576

xlviii

Table of Contents

Table of Contents

RT_SCREEN_ICMP_ID .................................................................................576 RT_SCREEN_ICMP_LARGE ..........................................................................576 RT_SCREEN_ICMP_PING_DEATH ................................................................576 RT_SCREEN_IP ............................................................................................577 RT_SCREEN_IP_BAD_OPT ..........................................................................577 RT_SCREEN_IP_FRAG .................................................................................577 RT_SCREEN_IP_LAND .................................................................................577 RT_SCREEN_IP_OPT_FILTER_ROUTE .........................................................578 RT_SCREEN_IP_OPT_LSR ...........................................................................578 RT_SCREEN_IP_OPT_RECORD ...................................................................578 RT_SCREEN_IP_OPT_SCHT .........................................................................578 RT_SCREEN_IP_OPT_SSR ...........................................................................579 RT_SCREEN_IP_OPT_STREAM ....................................................................579 RT_SCREEN_IP_OPT_TIMESTAMP ..............................................................579 RT_SCREEN_IP_SPOOFING .........................................................................579 RT_SCREEN_IP_SWEEP ..............................................................................580 RT_SCREEN_IP_UNKNOWN_PROT .............................................................580 RT_SCREEN_MAL_URL ...............................................................................580 RT_SCREEN_OVER_SESSION_DST ..............................................................580 RT_SCREEN_OVER_SESSION_SRC ..............................................................581 RT_SCREEN_PORT_SCAN ...........................................................................581 RT_SCREEN_SESSION_LIMIT ......................................................................581 RT_SCREEN_SYN_ACK_ACK .......................................................................581 RT_SCREEN_TCP ........................................................................................582 RT_SCREEN_TCP_DST_IP ...........................................................................582 RT_SCREEN_TCP_FIN_NO_ACK ..................................................................582 RT_SCREEN_TCP_FRAG ..............................................................................582 RT_SCREEN_TCP_NO_FLAG .......................................................................583 RT_SCREEN_TCP_SRC_IP ...........................................................................583 RT_SCREEN_TCP_SYN_FIN .........................................................................583 RT_SCREEN_TCP_SYN_FLOOD ...................................................................583 RT_SCREEN_TEAR_DROP ...........................................................................584 RT_SCREEN_UDP ........................................................................................584 RT_SCREEN_UDP_FLOOD ..........................................................................584 RT_SCREEN_WINNUKE ...............................................................................584 RT_SIP_CALL_LIMIT_EXCEED .....................................................................585 RT_SIP_DECODE_FAIL ................................................................................585 RT_SIP_INIT_EP_FAIL .................................................................................585 RT_SIP_INIT_LISTENER_FAIL ......................................................................585 RT_SIP_MEM_ALLOC_FAILED .....................................................................585 RT_SIP_REG_NAT_VEC_FAIL ......................................................................586 RT_SIP_REG_RM_FAIL ................................................................................586 RT_SIP_REM_NAT_VEC_FAIL ......................................................................586 RT_SIP_UNREG_BY_RM ..............................................................................586 RT_SOURCE_NAT_ALARM_CLEAR ..............................................................586 RT_SOURCE_NAT_ALARM_RAISE ...............................................................587 RT_SRC_NAT_ALARM_CLEAR .....................................................................587 RT_SRC_NAT_ALARM_RAISE ......................................................................587

Table of Contents

xlix

JUNOS 10.1 System Log Messages Reference

Chapter 74

RTLOG System Log Messages

589

RTLOG_SOURCE_INIT .................................................................................589 RTLOG_UTP_TCP_SYN_FLOOD ..................................................................589 Chapter 75 RTLOGD System Log Messages 591

RTLOGD_LOG_BIND_ERROR ......................................................................591 RTLOGD_LOG_READ_ERROR .....................................................................591 Chapter 76 RTPERF System Log Messages 593

RTPERF_CPU_THRESHOLD_EXCEEDED .....................................................593 RTPERF_CPU_USAGE_OK ...........................................................................593 Chapter 77 SAVAL System Log Messages 595

SAVAL_RTSOCK_FAILURE ..........................................................................595 Chapter 78 SDXD System Log Messages 597

SDXD_BEEP_FIN_FAIL ................................................................................597 SDXD_BEEP_INIT_FAIL ...............................................................................597 SDXD_CHANNEL_START_FAIL ....................................................................597 SDXD_CONNECT_FAIL ................................................................................598 SDXD_DAEMONIZE_FAIL ............................................................................598 SDXD_EVLIB_FAILURE ................................................................................598 SDXD_KEEPALIVES_MISSED .......................................................................599 SDXD_KEEPALIVE_SEND_FAIL ...................................................................599 SDXD_MGMT_SOCKET_IO ..........................................................................599 SDXD_OUT_OF_MEMORY ..........................................................................599 SDXD_PID_FILE_UPDATE ...........................................................................600 SDXD_SOCKET_FAILURE ............................................................................600 Chapter 79 SMTPD System Log Messages 601

SMTPD_DROP_MAIL_PAYLOAD .................................................................601 SMTPD_NO_CONFIGURED_SERVER ...........................................................601 Chapter 80 SNMP System Log Messages SNMP_GET_ERROR1 SNMP_GET_ERROR2 SNMP_GET_ERROR3 SNMP_GET_ERROR4 603

...................................................................................603 ...................................................................................603 ...................................................................................604 ...................................................................................604

Table of Contents

Table of Contents

SNMP_RTSLIB_FAILURE ..............................................................................604 SNMP_TRAP_LINK_DOWN .........................................................................605 SNMP_TRAP_LINK_UP ................................................................................605 SNMP_TRAP_TRACERT_PATH_CHANGE .....................................................605 SNMP_TRAP_TRACERT_TEST_COMPLETED ...............................................605 SNMP_TRAP_TRACERT_TEST_FAILED ........................................................606 Chapter 81 SNMPD System Log Messages 607

SNMPD_AUTH_FAILURE .............................................................................607 SNMPD_AUTH_PRIVILEGES_EXCEEDED ....................................................607 SNMPD_AUTH_RESTRICTED_ADDRESS .....................................................608 SNMPD_AUTH_WRONG_PDU_TYPE ...........................................................608 SNMPD_BIND_INFO ....................................................................................608 SNMPD_CONFIG_ERROR ............................................................................609 SNMPD_CONTEXT_ERROR .........................................................................609 SNMPD_FILE_FAILURE ...............................................................................609 SNMPD_GROUP_ERROR .............................................................................609 SNMPD_HEALTH_MON_THRESH_CROSS ...................................................610 SNMPD_INIT_FAILED ..................................................................................610 SNMPD_LIBJUNIPER_FAILURE ....................................................................610 SNMPD_RADIX_FAILURE ............................................................................611 SNMPD_RECEIVE_FAILURE ........................................................................611 SNMPD_RMONFILE_FAILURE .....................................................................611 SNMPD_RMON_COOKIE .............................................................................612 SNMPD_RMON_EVENTLOG ........................................................................612 SNMPD_RMON_MIBERROR ........................................................................612 SNMPD_RTSLIB_ASYNC_EVENT .................................................................613 SNMPD_SEND_FAILURE .............................................................................613 SNMPD_SET_FAILED ..................................................................................613 SNMPD_SMOID_GEN_FAILURE ...................................................................613 SNMPD_SOCKET_FAILURE .........................................................................614 SNMPD_SOCKET_FATAL_FAILURE .............................................................614 SNMPD_SYSLIB_FAILURE ...........................................................................614 SNMPD_SYSOID_FAILURE ..........................................................................615 SNMPD_SYSOID_GEN_FAILURE .................................................................615 SNMPD_THROTTLE_QUEUE_DRAINED ......................................................615 SNMPD_TRAP_COLD_START ......................................................................616 SNMPD_TRAP_GEN_FAILURE .....................................................................616 SNMPD_TRAP_INVALID_DATA ...................................................................616 SNMPD_TRAP_QUEUED .............................................................................617 SNMPD_TRAP_QUEUE_DRAINED ...............................................................617 SNMPD_TRAP_QUEUE_MAX_ATTEMPTS ....................................................617 SNMPD_TRAP_QUEUE_MAX_SIZE ..............................................................617 SNMPD_TRAP_THROTTLED ........................................................................618 SNMPD_TRAP_WARM_START ....................................................................618 SNMPD_USER_ERROR ................................................................................618

Table of Contents

li

JUNOS 10.1 System Log Messages Reference

Chapter 82

SPD System Log Messages

619

SPD_CONFIGURATION_COMPILE ...............................................................619 SPD_CONN_FATAL_FAILURE ......................................................................619 SPD_CONN_NO_REPLY ..............................................................................619 SPD_CONN_OPEN_FAILURE .......................................................................620 SPD_CONN_SEND_FAILURE .......................................................................620 SPD_CONN_UNEXPECTED_MSG .................................................................620 SPD_DAEMONIZE_FAILED ..........................................................................620 SPD_DB_IF_ADD_FAILURE .........................................................................621 SPD_DB_IF_ALLOC_FAILURE ......................................................................621 SPD_DB_SVC_SET_ADD_FAILURE ..............................................................621 SPD_DB_SVC_SET_ALLOC_FAILURE ...........................................................621 SPD_DUPLICATE .........................................................................................622 SPD_EVLIB_CREATE_FAILURE ....................................................................622 SPD_EVLIB_EXIT_FAILURE .........................................................................622 SPD_NOT_ROOT .........................................................................................622 SPD_OUT_OF_MEMORY .............................................................................623 SPD_PID_FILE_LOCK ..................................................................................623 SPD_PID_FILE_UPDATE ..............................................................................623 SPD_SERVICE_NEXT_HOP_ADD_FAILED ...................................................623 SPD_SERVICE_NEXT_HOP_DEL_FAILED ....................................................624 SPD_TRAP_OID_GEN_FAILED .....................................................................624 SPD_TRAP_REQUEST_FAILURE ..................................................................624 SPD_USAGE ................................................................................................624 Chapter 83 TASK System Log Messages 625

TASK_ABORT ..............................................................................................625 TASK_ACTIVE_TERMINATE .........................................................................625 TASK_ASSERT .............................................................................................625 TASK_ASSERT_SOFT ...................................................................................626 TASK_EXIT ..................................................................................................626 TASK_LOCK_FLOCKED ...............................................................................627 TASK_LOCK_LOCKED .................................................................................627 TASK_MGMT_TIMEOUT ..............................................................................627 TASK_OS_MEMHIGH ...................................................................................628 TASK_SCHED_CALLBACK_LONGRUNTIME .................................................628 TASK_SCHED_CUMULATIVE_RUNTIME ......................................................628 TASK_SCHED_MODULE_LONGRUNTIME ....................................................629 TASK_SCHED_TASK_LONGRUNTIME ..........................................................629 TASK_SIGNAL_TERMINATE .........................................................................629 TASK_START ...............................................................................................629 TASK_SYSTEM ............................................................................................630 TASK_TASK_BEGIN .....................................................................................630 TASK_TASK_CHILDKILLED .........................................................................630 TASK_TASK_CHILDSTOPPED ......................................................................630 TASK_TASK_FORK ......................................................................................631 TASK_TASK_GETWD ...................................................................................631

lii

Table of Contents

Table of Contents

TASK_TASK_NOREINIT ...............................................................................631 TASK_TASK_PIDCLOSED ............................................................................631 TASK_TASK_PIDFLOCK ..............................................................................632 TASK_TASK_PIDWRITE ...............................................................................632 TASK_TASK_REINIT ....................................................................................632 TASK_TASK_SIGNALIGNORE ......................................................................632 TASK_TRACE_FAILED .................................................................................633 Chapter 84 TFTPD System Log Messages 635

TFTPD_AF_ERR ...........................................................................................635 TFTPD_BIND_ERR .......................................................................................635 TFTPD_CONNECT_ERR ...............................................................................635 TFTPD_CONNECT_INFO .............................................................................636 TFTPD_CREATE_ERR ..................................................................................636 TFTPD_FIO_ERR .........................................................................................636 TFTPD_FORK_ERR ......................................................................................636 TFTPD_NAK_ERR ........................................................................................637 TFTPD_OPEN_ERR ......................................................................................637 TFTPD_RECVCOMPLETE_INFO ...................................................................637 TFTPD_RECVFROM_ERR ............................................................................637 TFTPD_RECV_ERR ......................................................................................638 TFTPD_SENDCOMPLETE_INFO ...................................................................638 TFTPD_SEND_ERR ......................................................................................638 TFTPD_SOCKET_ERR ..................................................................................638 TFTPD_STATFS_ERR ...................................................................................638 Chapter 85 UI System Log Messages 641

UI_AUTH_EVENT ........................................................................................641 UI_AUTH_INVALID_CHALLENGE .................................................................641 UI_BOOTTIME_FAILED ...............................................................................641 UI_CFG_AUDIT_NEW ..................................................................................642 UI_CFG_AUDIT_OTHER ..............................................................................642 UI_CFG_AUDIT_SET ....................................................................................642 UI_CFG_AUDIT_SET_SECRET ......................................................................642 UI_CHILD_ARGS_EXCEEDED ......................................................................643 UI_CHILD_CHANGE_USER ..........................................................................643 UI_CHILD_EXEC ..........................................................................................643 UI_CHILD_EXITED ......................................................................................644 UI_CHILD_FOPEN .......................................................................................644 UI_CHILD_PIPE_FAILED ..............................................................................644 UI_CHILD_STOPPED ...................................................................................645 UI_CHILD_WAITPID ....................................................................................645 UI_CMDLINE_READ_LINE ...........................................................................645 UI_CMD_AUTH_REGEX_INVALID ................................................................646 UI_COMMIT ................................................................................................646 UI_COMMIT_AT_ABORT .............................................................................646 UI_COMMIT_AT_COMPLETED ....................................................................646 UI_COMMIT_AT_FAILED .............................................................................647

Table of Contents

liii

JUNOS 10.1 System Log Messages Reference

UI_COMMIT_COMPRESS_FAILED ...............................................................647 UI_COMMIT_CONFIRMED_REMINDER .......................................................647 UI_COMMIT_EMPTY_CONTAINER ..............................................................647 UI_COMMIT_NOT_CONFIRMED ..................................................................648 UI_COMMIT_PROGRESS .............................................................................648 UI_COMMIT_ROLLBACK_FAILED ................................................................648 UI_COMMIT_SYNC_FORCE .........................................................................649 UI_CONFIGURATION_ERROR .....................................................................649 UI_CONFIGURATION_WARNING .................................................................649 UI_DAEMON_ACCEPT_FAILED ...................................................................650 UI_DAEMON_FORK_FAILED .......................................................................650 UI_DAEMON_SELECT_FAILED ....................................................................650 UI_DAEMON_SOCKET_FAILED ...................................................................651 UI_DBASE_ACCESS_FAILED ........................................................................651 UI_DBASE_CHECKOUT_FAILED ..................................................................651 UI_DBASE_EXTEND_FAILED .......................................................................652 UI_DBASE_LOGIN_EVENT ...........................................................................652 UI_DBASE_LOGOUT_EVENT .......................................................................652 UI_DBASE_MISMATCH_EXTENT .................................................................652 UI_DBASE_MISMATCH_MAJOR ...................................................................653 UI_DBASE_MISMATCH_MINOR ...................................................................653 UI_DBASE_MISMATCH_SEQUENCE ............................................................654 UI_DBASE_MISMATCH_SIZE .......................................................................654 UI_DBASE_OPEN_FAILED ...........................................................................655 UI_DBASE_REBUILD_FAILED ......................................................................655 UI_DBASE_REBUILD_SCHEMA_FAILED ......................................................655 UI_DBASE_REBUILD_STARTED ...................................................................656 UI_DBASE_RECREATE ................................................................................656 UI_DBASE_REOPEN_FAILED .......................................................................656 UI_DUPLICATE_UID ....................................................................................657 UI_FACTORY_OPERATION .........................................................................657 UI_INITIALSETUP_OPERATION ...................................................................657 UI_INVALID_REMOTE_PERMISSION ...........................................................657 UI_JUNOSCRIPT_CMD .................................................................................658 UI_JUNOSCRIPT_ERROR .............................................................................658 UI_LCC_NO_MASTER ..................................................................................658 UI_LOAD_EVENT ........................................................................................658 UI_LOAD_JUNOS_DEFAULT_FILE_EVENT ...................................................659 UI_LOGIN_EVENT .......................................................................................659 UI_LOGOUT_EVENT ....................................................................................659 UI_LOST_CONN ..........................................................................................659 UI_MASTERSHIP_EVENT .............................................................................660 UI_MOTD_PROPAGATE_ERROR .................................................................660 UI_NETCONF_CMD .....................................................................................660 UI_NETCONF_ERROR .................................................................................660 UI_PARSE_JUNOSCRIPT_ATTRIBUTES ........................................................661 UI_READ_FAILED ........................................................................................661 UI_READ_TIMEOUT ....................................................................................661 UI_REBOOT_EVENT ....................................................................................662 UI_RESCUE_OPERATION ............................................................................662 UI_RESTART_EVENT ...................................................................................662

liv

Table of Contents

Table of Contents

UI_SCHEMA_CHECKOUT_FAILED ...............................................................662 UI_SCHEMA_MISMATCH_MAJOR ................................................................663 UI_SCHEMA_MISMATCH_SEQUENCE .........................................................663 UI_SCHEMA_SEQUENCE_ERROR ...............................................................663 UI_TACPLUS_ERROR ..................................................................................664 UI_VERSION_FAILED ..................................................................................664 UI_WRITE_RECONNECT .............................................................................664 Chapter 86 UTMD System Log Messages 667

UTMD_MALLOC_FAILURE ...........................................................................667 UTMD_SSAMLIB_FAILURE ..........................................................................667 Chapter 87 VCCPD System Log Messages 669

VCCPD_KNL_VERSION ................................................................................669 VCCPD_KNL_VERSIONNONE ......................................................................669 VCCPD_KNL_VERSIONOLD .........................................................................670 VCCPD_PROTOCOL_ADJDOWN .................................................................670 VCCPD_PROTOCOL_ADJUP ........................................................................670 VCCPD_PROTOCOL_LSPCKSUM .................................................................670 VCCPD_PROTOCOL_OVERLOAD ................................................................671 VCCPD_SYSTEM ..........................................................................................671 Chapter 88 VRRPD System Log Messages 673

VRRPD_ADVERT_TIME_MISMATCH ............................................................673 VRRPD_AUTH_INFO_INVALID ....................................................................673 VRRPD_GET_TRAP_HEADER_FAILED .........................................................674 VRRPD_LINK_LOCAL_ADD_MISMATCH .....................................................674 VRRPD_MISSING_VIP ..................................................................................674 VRRPD_NEW_BACKUP ...............................................................................675 VRRPD_NEW_MASTER ...............................................................................675 VRRPD_VIP_COUNT_MISMATCH ................................................................675 Chapter 89 VSYSD System Log Messages 677

VSYSD_INIT_FAILED ...................................................................................677 Chapter 90 WEB System Log Messages 679

WEB_AUTH_FAIL ........................................................................................679 WEB_AUTH_SUCCESS .................................................................................679 WEB_AUTH_TIME_EXCEEDED ...................................................................679 WEB_CERT_FILE_NOT_FOUND ..................................................................680 WEB_CHILD_STATE ....................................................................................680 WEB_CONFIG_OPEN_ERROR .....................................................................680

Table of Contents

lv

JUNOS 10.1 System Log Messages Reference

WEB_CONFIG_WRITE_ERROR ....................................................................680 WEB_COULDNT_START_HTTPD .................................................................680 WEB_EVENTLIB_INIT ..................................................................................681 WEB_KEYPAIR_FILE_NOT_FOUND ............................................................681 WEB_MGD_BIND_ERROR ...........................................................................681 WEB_MGD_CHMOD_ERROR ......................................................................681 WEB_MGD_CONNECT_ERROR ...................................................................682 WEB_MGD_FCNTL_ERROR .........................................................................682 WEB_MGD_LISTEN_ERROR ........................................................................682 WEB_MGD_RECVMSG_PEEK_ERROR .........................................................682 WEB_MGD_SOCKET_ERROR ......................................................................682 WEB_PIDFILE_LOCK ...................................................................................683 WEB_PIDFILE_UPDATE ..............................................................................683 WEB_UNAME_FAILED .................................................................................683 WEB_WEBAUTH_AUTH_FAIL .....................................................................683 WEB_WEBAUTH_AUTH_OK ........................................................................684 WEB_WEBAUTH_CONNECT_FAIL ...............................................................684 Chapter 91 WEBFILTER System Log Messages 685

WEBFILTER_CACHE_NOT_ENABLED ..........................................................685 WEBFILTER_INTERNAL_ERROR .................................................................685 WEBFILTER_REQUEST_NOT_CHECKED .....................................................685 WEBFILTER_SERVER_CONNECTED ............................................................686 WEBFILTER_SERVER_DISCONNECTED ......................................................686 WEBFILTER_SERVER_ERROR .....................................................................686 WEBFILTER_URL_BLOCKED .......................................................................687 WEBFILTER_URL_PERMITTED ....................................................................687

Part 3

Index
Index ...........................................................................................................691

lvi

Table of Contents

About This Guide

This preface provides the following guidelines for using the JUNOS Software System Log Messages Reference:

JUNOS Documentation and Release Notes on page lvii Objectives on page lviii Audience on page lviii Supported Platforms on page lviii Using the Examples in This Manual on page lix Documentation Conventions on page lx Documentation Feedback on page lxii Requesting Technical Support on page lxii

JUNOS Documentation and Release Notes

For a list of related JUNOS documentation, see http://www.juniper.net/techpubs/software/junos/ . If the information in the latest release notes differs from the information in the documentation, follow the JUNOS Release Notes. To obtain the most current version of all Juniper Networks technical documentation, see the product documentation page on the 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 JUNOS Software and Juniper Networks devices. In addition, the Juniper Networks Technical Library, published in conjunction with O'Reilly Media, explores improving network security, reliability, and availability using JUNOS configuration techniques. All the books are for sale at technical bookstores and book outlets around the world. The current list can be viewed at http://www.juniper.net/books .

JUNOS Documentation and Release Notes

lvii

JUNOS 10.1 System Log Messages Reference

Objectives
This reference describes system log messages generated by the JUNOS Software. Use the information to interpret system log messages and determine the appropriate corrective action for error conditions

NOTE: For additional information about JUNOS Softwareeither corrections to or information that might have been omitted from this guidesee the software release notes at http://www.juniper.net/.

Audience
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. You must also be familiar with one or more of the following Internet routing protocols:

Border Gateway Protocol (BGP) Distance Vector Multicast Routing Protocol (DVMRP) Intermediate System-to-Intermediate System (IS-IS) Internet Control Message Protocol (ICMP) router discovery Internet Group Management Protocol (IGMP) Multiprotocol Label Switching (MPLS) Open Shortest Path First (OSPF) Protocol-Independent Multicast (PIM) Resource Reservation Protocol (RSVP) Routing Information Protocol (RIP) Simple Network Management Protocol (SNMP)

Personnel operating the equipment must be trained and competent; must not conduct themselves in a careless, willfully negligent, or hostile manner; and must abide by the instructions provided by the documentation.

Supported Platforms
For the features described in this manual, JUNOS Software currently supports the following platforms:

J Series M Series

lviii

Objectives

About This Guide

MX Series T Series EX Series

Using the Examples in This Manual

If you want to use the examples in this manual, you can use the load merge or the load merge relative command. These commands cause the software to merge the incoming configuration into the current candidate configuration. If the example configuration contains the top level of the hierarchy (or multiple hierarchies), the example is a full example. In this case, use the load merge command If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In this case, use the load merge relative command. These procedures are described in the following sections.

Merging a Full Example

To merge a full example, follow these steps:
1.

From the HTML or PDF version of the manual, copy a configuration example into a text file, save the file with a name, and copy the file to a directory on your routing platform. For example, copy the following configuration to a file and name the file ex-script.conf. Copy the ex-script.conf file to the /var/tmp directory on your routing platform.
system { scripts { commit { file ex-script.xsl; } } } interfaces { fxp0 { disable; unit 0 { family inet { address 10.0.0.1/24; } } } }

2.

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

Using the Examples in This Manual

lix

JUNOS 10.1 System Log Messages Reference

Merging a Snippet
To merge a snippet, follow these steps:
1.

From the HTML or PDF version of the manual, copy a configuration snippet into a text file, save the file with a name, and copy the file to a directory on your routing platform. For example, copy the following snippet to a file and name the file ex-script-snippet.conf. Copy the ex-script-snippet.conf file to the /var/tmp directory on your routing platform.
commit { file ex-script-snippet.xsl; }

2.

Move to the hierarchy level that is relevant for this snippet by issuing the following configuration mode command:
[edit] user@host# edit system scripts [edit system scripts]

3.

Merge the contents of the file into your routing platform configuration by issuing the load merge relative configuration mode command:
[edit system scripts] user@host# load merge relative /var/tmp/ex-script-snippet.conf load complete

For more information about the load command, see the JUNOS CLI User Guide

Documentation Conventions
Table 1 on page lx defines notice icons used in this guide.
Table 1: Notice Icons
Icon Meaning Informational note Description Indicates important features or instructions.

Caution

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.

lx

Documentation Conventions

About This Guide

Table 2 on page lxi defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
Convention
Bold text like this

Description Represents text that you type.

Examples To enter configuration mode, type the configure command: user@host> configure

Fixed-width text like this

Represents output that appears on the terminal screen.

user@host> show chassis alarms No alarms currently active

Italic text like this

Introduces important new terms. Identifies book names. Identifies RFC and Internet draft titles.

A policy term is a named structure that defines match conditions and actions. JUNOS System Basics Configuration Guide RFC 1997, BGP Communities Attribute

Italic text like this

Represents variables (options for which you substitute a value) in commands or configuration statements.

Configure the machines domain name: [edit] root@# set system domain-name domain-name

Plain text like this

Represents names of configuration statements, commands, files, and directories; IP addresses; configuration hierarchy levels; or labels on routing platform components.

To configure a stub area, include the stub statement at the [edit

protocols ospf area area-id]

hierarchy level.

The console port is labeled CONSOLE.

< > (angle brackets) | (pipe symbol)

Enclose optional keywords or variables. Indicates a choice between the mutually exclusive keywords or variables on either side of the symbol. The set of choices is often enclosed in parentheses for clarity. Indicates a comment specified on the same line as the configuration statement to which it applies. Enclose a variable for which you can substitute one or more values.

stub <default-metric metric>; broadcast | multicast (string1 | string2 | string3)

# (pound sign)

rsvp { # Required for dynamic MPLS only

[ ] (square brackets)

community name members [ community-ids ]

Documentation Conventions

lxi

JUNOS 10.1 System Log Messages Reference

Table 2: Text and Syntax Conventions (continued)

Convention Indention and braces ( { } ) Description Identify a level in the configuration hierarchy. Identifies a leaf statement at a configuration hierarchy level. Examples [edit] routing-options { static { route default { nexthop address; retain; } } }

; (semicolon)

J-Web GUI Conventions

Bold text like this

Represents J-Web graphical user interface (GUI) items you click or select.

In the Logical Interfaces box, select All Interfaces. To cancel the configuration, click Cancel.

> (bold right angle bracket)

Separates levels in a hierarchy of J-Web selections.

In the configuration editor hierarchy, select Protocols>Ospf.

Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation. You can send your comments to techpubs-comments@juniper.net, or fill out the documentation feedback form at https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include the following information with your comments:

Document or topic name URL or page number Software release version (if applicable)

Requesting Technical Support

Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC). If you are a customer with an active J-Care or JNASC support contract, or are covered under warranty, and need postsales technical support, you can access our tools and resources online or open a case with JTAC.

JTAC policiesFor a complete understanding of our JTAC procedures and policies, review the JTAC User Guide located at http://www.juniper.net/customers/support/downloads/7100059-EN.pdf . Product warrantiesFor product warranty information, visit http://www.juniper.net/support/warranty/ . JTAC Hours of Operation The JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year.

lxii

Documentation Feedback

About This Guide

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:

Find CSC offerings: http://www.juniper.net/customers/support/ Search for known bugs: http://www2.juniper.net/kb/ Find product documentation: http://www.juniper.net/techpubs/ Find solutions and answer questions using our Knowledge Base:
http://kb.juniper.net/

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/

To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/

Opening a Case with JTAC

You can open a case with JTAC on the Web or by telephone.

Use the Case Management tool in the CSC at http://www.juniper.net/cm/ . Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

For international or direct-dial options in countries without toll-free numbers, visit us at http://www.juniper.net/support/requesting-support.html

Requesting Technical Support

lxiii

JUNOS 10.1 System Log Messages Reference

lxiv

Requesting Technical Support

Part 1

Overview

Configuring System Log Messages on page 3

Overview

JUNOS 10.1 System Log Messages Reference

Overview

Chapter 1

Configuring System Log Messages

The JUNOS Software generates system log messages (also called syslog messages) to record events that occur on the routing platform, including the following:

Routine operations, such as creation of an OSPF protocol adjacency or a user login into the configuration database Failure and error conditions, such as failure to access a configuration file or unexpected closure of a connection to a peer process Emergency or critical conditions, such as routing platform power-down due to excessive temperature

Each system log message identifies the JUNOS Software process that generated the message and briefly describes the operation or error that occurred. This reference provides more detailed information about each system log message and, when applicable, describes possible causes of the message and action you can take to correct error conditions.

NOTE: The configuration hierarchy in this chapter applies to JUNOS Software processes and libraries, not to the services on a PIC such as the Adaptive Services PIC. For information about configuring system logging for PIC services, see the JUNOS Services Interfaces Configuration Guide. For information about interpreting messages generated by services on a PIC, see Interpreting Messages Generated in Standard Format by Services on a PIC on page 44.

This chapter discusses the following topics:

System Logging Configuration Statements on page 4 Minimum and Default System Logging Configuration on page 4 Configuring System Logging for a Single-Chassis System on page 7 Configuring System Logging for a Routing Matrix on page 28 Displaying and Interpreting System Log Messages on page 37 Getting Help About System Log Messages on page 49

JUNOS 10.1 System Log Messages Reference

System Logging Configuration Statements

To configure the routing platform to log system messages, include the syslog statement at the [edit system] hierarchy level:
[edit system] syslog { archive { files number; size size; (world-readable | no-world-readable); } console { facility severity; } file filename { facility severity; explicit-priority; match "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; time-format (year | millisecond | year millisecond); user (username | *) { facility severity; match "regular-expression"; } }

Minimum and Default System Logging Configuration

For information about the minimum and default system log settings on routing platforms that run the JUNOS Software, see the following sections:

Minimum System Logging Configuration on page 5 Default System Log Settings on page 5

System Logging Configuration Statements

Chapter 1: Configuring System Log Messages

Minimum System Logging Configuration

To record or view system log messages, you must include the syslog statement at the [edit system] hierarchy level. Specify at least one destination for the messages, as described in Table 3 on page 5. For more information about the configuration statements, see Configuring System Logging for a Single-Chassis System on page 7.
Table 3: Minimum Configuration Statements for System Logging
Destination Minimum Configuration Statements

File

[edit system syslog] file filename { facility severity ; } [edit system syslog] user (username | *) { facility severity ; } [edit system syslog] console { facility severity ; } [edit system syslog] host (hostname | other-routing-engine) { facility severity ; }

Terminal session of one, several, or all users

Routing platform console

Remote machine or the other Routing Engine on the routing platform

Default System Log Settings

Table 4 on page 6 summarizes the default system log settings that apply to all platforms that run the JUNOS Software, and specifies which statement to include in the configuration to override the default value.

Minimum System Logging Configuration

JUNOS 10.1 System Log Messages Reference

Table 4: Default System Logging Settings

Setting Default Overriding Statement Instructions

Alternative facility for message forwarded to a remote machine

For change-log: local6 For conflict-log: local5 For dfc: local1 For firewall: local3 For
interactive-commands: local7

[edit system syslog] host hostname { facility-override facility; }

Changing the Alternative Facility Name for Remote Messages on page 14

For pfe: local4 Format of messages logged to a file Standard JUNOS format, based on UNIX format [edit system syslog] file filename { structured-data; } Logging Messages in Structured-Data Format on page 12 Configuring the Size and Number of Log Files on page 18

Maximum number of files in the archived set

10

[edit system syslog] archive { files number; } file filename { archive { files number ; } } [edit system syslog] archive { size size; } file filename { archive { size size; } } [edit system syslog] time-format format;

Maximum size of log file

J Series: 128 kilobytes (KB) M Series, MX Series, and T Series: 1 megabyte (MB) TX Matrix: 10 MB

Configuring the Size and Number of Log Files on page 18

Timestamp format

Month, date, hour, minute, second For example: Aug 21 12:36:30

Including the Year or Millisecond in Timestamps on page 22 Configuring the Size and Number of Log Files on page 18

Users who can read log files

root user and users

with the JUNOS

maintenance

permission

[edit system syslog] archive { world-readable; } file filename { archive { world-readable; } }

Default System Log Settings

Chapter 1: Configuring System Log Messages

In addition, the following messages are generated by default on specific platforms. To view either type of message, you must configure at least one destination for messages as described in Minimum System Logging Configuration on page 5

On J Series platforms, a message is logged when a process running in the kernel consumes 500 or more consecutive milliseconds of CPU time. To log the message on an M Series, MX Series, or T Series platform, include the kernel info statement at the appropriate hierarchy level:
[edit system syslog] (console | file filename | host destination | user username) { kernel info; }

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:
[edit system syslog] host scc-master { any info; }

Configuring System Logging for a Single-Chassis System

The JUNOS system logging utility is similar to the UNIX syslogd utility. This section describes how to configure system logging for a single-chassis system that runs the JUNOS Software. 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 Software. For more information, see the Secure Configuration Guide for Common Criteria and JUNOS-FIPS. For information about configuring system logging for a routing matrix, see Configuring System Logging for a Routing Matrix on page 28. Each system log message belongs to a facility, which groups together related messages. Each message is also preassigned a severity level, which indicates how seriously the triggering event affects routing platform functions. You always specify the facility and severity of the messages to include in the log. For more information, see Specifying the Facility and Severity of Messages to Include in the Log on page 9.

Configuring System Logging for a Single-Chassis System

JUNOS 10.1 System Log Messages Reference

You direct messages to one or more destinations by including the appropriate statement at the [edit system syslog] hierarchy level:

To a named file in a local file system, by including the file statement. See Directing Messages to a Log File on page 11. To the terminal session of one or more specific users (or all users) when they are logged in to the routing platform, by including the user statement. See Directing Messages to a User Terminal on page 12. To the routing platform console, by including the console statement. See Directing Messages to the Console on page 13. To a remote machine that is running the syslogd utility or to the other Routing Engine on the routing platform, by including the host statement. See Directing Messages to a Remote Machine or the Other Routing Engine on page 13.

By default, messages are logged in a standard format, which is based on a UNIX system log format; for detailed information, see Interpreting System Log Messages on page 38. You can alter the content and format of logged messages in the following ways:

In JUNOS 8.3 and later, you can log messages to a file in structured-data format instead of the standard JUNOS format. Structured-data format provides more information without adding significant length, and makes it easier for automated applications to extract information from the message. For more information, see Logging Messages in Structured-Data Format on page 12. A messages facility and severity level are together referred to as its priority. By default, the standard JUNOS format for messages does not include priority information. (Structured-data format includes a priority code by default.) To include priority information in standard-format messages directed to a file or a remote destination, include the explicit-priority statement. For more information, see Including Priority Information in System Log Messages on page 19. By default, the standard JUNOS format for messages specifies the month, date, hour, minute, and second when the message was logged. You can modify the timestamp on standard-format messages to include the year, the millisecond, or both. (Structured-data format specifies the year and millisecond by default.) For more information, see Including the Year or Millisecond in Timestamps on page 22. When directing messages to a remote machine, you can specify the IP address that is reported in messages as their source. You can also configure features that make it easier to separate JUNOS-specific messages or messages generated on particular routing platforms. For more information, see Directing Messages to a Remote Machine or the Other Routing Engine on page 13. The predefined facilities group together related messages, but you can also use regular expressions to specify more exactly which messages from a facility are logged to a file, a user terminal, or a remote destination. For more information, see Using Regular Expressions to Refine the Set of Logged Messages on page 23.

For a statement summary for the statements discussed in this chapter, see the JUNOS System Basics Configuration Guide.

Configuring System Logging for a Single-Chassis System

Chapter 1: Configuring System Log Messages

For detailed information about configuring system logging, see the following sections:

Specifying the Facility and Severity of Messages to Include in the Log on page 9 Directing Messages to a Log File on page 11 Directing Messages to a User Terminal on page 12 Directing Messages to the Console on page 13 Directing Messages to a Remote Machine or the Other Routing Engine on page 13 Configuring the Size and Number of Log Files on page 18 Including Priority Information in System Log Messages on page 19 Including the Year or Millisecond in Timestamps on page 22 Using Regular Expressions to Refine the Set of Logged Messages on page 23 Disabling Logging of a Facility on page 25 Examples: Configuring System Logging on page 25

Specifying the Facility and Severity of Messages to Include in the Log

Each system log message belongs to a facility, which groups together messages that either are generated by the same source (such as a software process) or concern a similar condition or activity (such as authentication attempts). Each message is also preassigned a severity level, which indicates how seriously the triggering event affects routing platform functions. 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:
[edit system syslog] (console | file filename | host destination | user username) { facility severity ; }

For more information about the destinations, see Directing Messages to a Log File on page 11,Directing Messages to a User Terminal on page 12,Directing Messages to the Console on page 13 and Directing Messages to a Remote Machine or the Other Routing Engine on page 13. To log messages belonging to more than one facility to a particular destination, specify each facility and associated severity as a separate statement within the set of statements for the destination. Table 5 on page 9 lists the facilities that you can specify in configuration statements at the [edit system syslog] hierarchy level.
Table 5: JUNOS System Logging Facilities
Facility Type of Event or Error

any authorization

All (messages from all facilities) Authentication and authorization attempts

Specifying the Facility and Severity of Messages to Include in the Log

JUNOS 10.1 System Log Messages Reference

Table 5: JUNOS System Logging Facilities (continued)

Facility Type of Event or Error

change-log conflict-log

Changes to the JUNOS configuration Specified configuration is invalid on the routing platform type Actions performed or errors encountered by system processes Events related to dynamic flow capture Packet filtering actions performed by a firewall filter Actions performed or errors encountered by the FTP process Commands issued at the JUNOS command-line interface (CLI) prompt or invoked by a client application such as a JUNOScript or NETCONF client Actions performed or errors encountered by the JUNOS kernel Actions performed or errors encountered by the Packet Forwarding Engine Actions performed or errors encountered by user-space processes

daemon

dfc firewall

ftp

interactive-commands

kernel

pfe

user

Table 6 on page 10 lists the severity levels that you can specify in configuration statements at the [edit system syslog] hierarchy level. The levels from emergency through info are in order from highest severity (greatest effect on functioning) to lowest. Unlike the other severity levels, the none level disables logging of a facility instead of indicating how seriously a triggering event affects routing functions. For more information, see Disabling Logging of a Facility on page 25
Table 6: System Log Message Severity Levels
Severity Level Description

any none emergency

Includes all severity levels Disables logging of the associated facility to a destination System panic or other condition that causes the routing platform to stop functioning Conditions that require immediate correction, such as a corrupted system database

alert

10

Specifying the Facility and Severity of Messages to Include in the Log

Chapter 1: Configuring System Log Messages

Table 6: System Log Message Severity Levels (continued)

Severity Level Description

critical error

Critical conditions, such as hard drive errors Error conditions that generally have less serious consequences than errors in the emergency, alert, and critical levels Conditions that warrant monitoring Conditions that are not errors but might warrant special handling Events or nonerror conditions of interest

warning notice info

Directing Messages to a Log File

To direct system log messages to a file in the /var/log directory of the local Routing Engine, include the file statement at the [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); } }

For the list of facilities and severity levels, see Specifying the Facility and Severity of Messages to Include in the Log on page 9. To prevent log files from growing too large, the JUNOS system logging utility by default writes messages to a sequence of files of a defined size. By including the archive statement, you can configure the number of files, their maximum size, and who can read them, for either all log files or a certain log file. For more information, see Configuring the Size and Number of Log Files on page 18. For information about the following statements, see the indicated sections:

explicit-prioritySee Including Priority Information in System Log Messages on

page 19.

matchSee Using Regular Expressions to Refine the Set of Logged Messages

on page 23.

structured-dataSee Logging Messages in Structured-Data Format on page 12.

Logging Messages in Structured-Data Format on page 12

Directing Messages to a Log File

11

JUNOS 10.1 System Log Messages Reference

Logging Messages in Structured-Data Format

In JUNOS 8.3 and later, you can log messages to a file in structured-data format instead of the standard JUNOS format. Structured-data format provides more information without adding significant length, and makes it easier for automated applications to extract information from a message. The structured-data format complies with Internet draft draft-ietf-syslog-protocol-21.txt, The draft establishes a standard message format regardless of the source or transport protocol for logged messages. To output messages to a file in structured-data format, include the structured-data statement at the [edit system syslog file filename] hierarchy level:
[edit system syslog file filename] facility severity; structured-data { brief; }

The optional brief statement suppresses the English-language text that appears by default at the end of a message to describe the error or event. For information about the fields in a structured-dataformat message, see Displaying a Log File from a Single-Chassis System on page 37 The structured format is used for all messages logged to the file that are generated by a JUNOS process or software library.

NOTE: If you include either or both of the explicit-priority and time-format statements along with the structured-data statement, they are ignored. These statements apply to the standard JUNOS system log format, not to structured-data format.

Directing Messages to a User Terminal

To direct system log messages to the terminal session of one or more specific users (or all users) when they are logged in to the local Routing Engine, include the user statement at the [edit system syslog] hierarchy level:
[edit system syslog] user (username | *) { facility severity; match "regular-expression"; }

Specify one or more JUNOS usernames, separating multiple values with spaces, or use the asterisk (*) to indicate all users who are logged in to the local Routing Engine. For the list of facilities and severity levels, see Specifying the Facility and Severity of Messages to Include in the Log on page 9. For information about the match

12

Logging Messages in Structured-Data Format

Chapter 1: Configuring System Log Messages

statement, see Using Regular Expressions to Refine the Set of Logged Messages on page 23.

Directing Messages to the Console

To direct system log messages to the console of the local Routing Engine, include the console statement at the [edit system syslog] hierarchy level:
[edit system syslog] console { facility severity; }

For the list of facilities and severity levels, see Specifying the Facility and Severity of Messages to Include in the Log on page 9.

Directing Messages to a Remote Machine or the Other Routing Engine

To direct system log messages to a remote machine or to the other Routing Engine on the routing platform, include the host statement at the [edit system syslog] hierarchy level:
[edit system syslog] host (hostname | other-routing-engine) { facility severity; explicit-priority; facility-override facility; log-prefix string; match "regular-expression"; } source-address source-address;

To direct system log messages to a remote machine, include the host hostname statement to specify the remote machines IP version 4 (IPv4) address, IP version 6 (IPv6) address, or fully qualified hostname. 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. To direct system log messages to the other Routing Engine on a routing platform with two Routing Engines installed and operational, include the host other-routing-engine statement. The statement is not automatically reciprocal, so you must include it in each Routing Engines configuration if you want them to direct messages to each other. In each message directed to the other Routing Engine, the string re0 or re1 appears after the timestamp to indicate the source for the message. For the list of facilities and severity levels to configure under the host statement, see Specifying the Facility and Severity of Messages to Include in the Log on page 9. To record facility and severity level information in each message, include the explicit-priority statement. For more information, see Including Priority Information in System Log Messages on page 19.

Directing Messages to the Console

13

JUNOS 10.1 System Log Messages Reference

For information about the match statement, see Using Regular Expressions to Refine the Set of Logged Messages on page 23. When directing messages to remote machines, you can include the source-address statement to specify the IP address of the routing platform that is reported in the messages as their source. In each host statement, you can also include the facility-override statement to assign an alternative facility and the log-prefix statement to add a string to each message. For more information, see the following sections:

Specifying an Alternative Source Address for System Log Messages on page 14 Changing the Alternative Facility Name for Remote Messages on page 14 Examples: Assigning an Alternative Facility on page 16 Adding a Text String to System Log Messages on page 17 Adding a String on page 17

Specifying an Alternative Source Address for System Log Messages

To specify the routing platform that is reported in system log messages as their source when they are directed to a remote machine, include the source-address statement at the [edit system syslog] hierarchy level:
[edit system syslog] source-address source-address; source-address is a valid IPv4 or IPv6 address configured on one of the routing platform

interfaces. The address is reported in the messages directed to all remote machines specified in host hostname statements at the [edit system syslog] hierarchy level, but not in messages directed to the other Routing Engine.

Changing the Alternative Facility Name for Remote Messages

Some facilities assigned to messages logged on the local routing platform have JUNOS-specific names (see Table 5 on page 9 in Specifying the Facility and Severity of Messages to Include in the Log on page 9. 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. To enable the standard syslogd utility to handle messages from these facilities, when messages are directed to a remote machine a standard localX facility name is used instead of the JUNOS-specific facility name. Table 7 on page 14 lists the default alternative facility name used for each JUNOS-specific facility name. For facilities that are not listed, the default alternative name is the same as the local facility name.
Table 7: Default Facilities for Messages Directed to a Remote Destination
Default Facility When Directed to Remote Destination local6 local5

JUNOS-Specific Local Facility change-log conflict-log

14

Specifying an Alternative Source Address for System Log Messages

Chapter 1: Configuring System Log Messages

Table 7: Default Facilities for Messages Directed to a Remote Destination (continued)

Default Facility When Directed to Remote Destination local1 local3 local7 local4

JUNOS-Specific Local Facility dfc firewall interactive-commands pfe

The syslogd utility on a remote machine handles all messages that belong to a facility in the same way, regardless of the source of the message (the Juniper Networks routing platform or the remote machine itself). For example, the following statements in the configuration of the routing platform called local-router direct messages from the authorization facility to the remote machine called monitor.mycompany.com:
[edit system syslog] host monitor.mycompany.com { authorization info; }

The default alternative facility for the local authorization facility is also authorization. If the syslogd utility on monitor is configured to write messages belonging to the authorization facility to the file /var/log/auth-attempts, the file contains both the messages generated when users log in to local-router and the messages generated when users log in to monitor. Although the name of the source machine appears in each system log message, the mixing of messages from multiple machines can make it more difficult to analyze the contents of the auth-attempts file. To make it easier to separate the messages from each source, you can assign an alternative facility to all messages generated on local-router when they are directed to monitor. You can then configure the syslogd utility on monitor to write messages with the alternative facility to a different file from messages generated on monitor itself. To change the facility used for all messages directed to a remote machine, include the facility-override statement at the [edit system syslog host hostname] hierarchy level:
[edit system syslog host hostname] facility severity; facility-override facility;

In general, it makes sense to specify an alternative facility that is not already in use on the remote machine, such as one of the localX facilities. On the remote machine, you must also configure the syslogd utility to handle the messages in the desired manner. Table 8 on page 16 lists the facilities that you can specify in the facility-override statement.

Changing the Alternative Facility Name for Remote Messages

15

JUNOS 10.1 System Log Messages Reference

Table 8: Facilities for the facility-override Statement

Facility Description

authorization daemon ftp kernel local0 local1 local2 local3 local4 local5 local6 local7 user

Authentication and authorization attempts Actions performed or errors encountered by system processes Actions performed or errors encountered by the FTP process Actions performed or errors encountered by the JUNOS kernel Local facility number 0 Local facility number 1 Local facility number 2 Local facility number 3 Local facility number 4 Local facility number 5 Local facility number 6 Local facility number 7 Actions performed or errors encountered by user-space processes

We do not recommend including the facility-override statement at the [edit system syslog host other-routing-engine] hierarchy level. It is not necessary to use alternative facility names when directing messages to the other Routing Engine, because its JUNOS system logging utility can interpret the JUNOS-specific names.

Examples: Assigning an Alternative Facility

Log all messages generated on the local routing platform at the error level or higher to the local0 facility on the remote machine called monitor.mycompany.com:
[edit system syslog] host monitor.mycompany.com { any error; facility-override local0; }

Configure routing platforms located in and routing platforms located in New York to send messages to a single remote machine called central-logger.mycompany.com. The messages from California are assigned alternative facility local0 and the messages from New York are assigned to alternative facility local2.

Configure California routing platforms to aggregate messages in the local0 facility:

[edit system syslog] host central-logger.mycompany.com {

16

Examples: Assigning an Alternative Facility

Chapter 1: Configuring System Log Messages

change-log info; facility-override local0; }

Configure New York routing platforms to aggregate messages in the local2 facility:
[edit system syslog] host central-logger.mycompany.com { change-log info; facility-override local2; }

On central-logger, you can then configure the system logging utility to write messages from the local0 facility to the file california-config and the messages from the local2 facility to the file new-york-config.

Adding a Text String to System Log Messages

To add a text string to every system log message directed to a remote machine or to the other Routing Engine, include the log-prefix statement at the [edit system syslog host] hierarchy level:
[edit system syslog host (hostname | other-routing-engine)] facility severity; log-prefix string;

The string can contain any alphanumeric or special character except the equal sign (=) and the colon (:). It also cannot include the space character; do not enclose the string in quotation marks ( ) in an attempt to include spaces in it. The JUNOS system logging utility automatically appends a colon and a space to the specified string. The string is inserted after the identifier for the Routing Engine that generated the message.

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; log-prefix M120; }

When these configuration statements are included on an M120 router called origin1, a message in the system log on hardware-logger.mycompany.com looks like the following:
Mar 9 17:33:23 origin1 M120: mgd[477]: UI_CMDLINE_READ_LINE: user root, command run show version

Adding a Text String to System Log Messages

17

JUNOS 10.1 System Log Messages Reference

Configuring the Size and Number of Log Files

To prevent log files from growing too large, the JUNOS system logging utility by default writes messages to a sequence of files of a defined size. The files in the sequence are referred to as archive files to distinguish them from the active file to which messages are currently being written. The default maximum size depends on the platform type:

128 kilobytes (KB) for J Series Services Routers 1 megabyte (MB) for M Series, MX Series, and T Series routing platforms

When an active log file called logfile reaches the maximum size, the logging utility closes the file, compresses it, and names the compressed archive file logfile.0.gz. The logging utility then opens and writes to a new active file called logfile. When the new logfile reaches the configured maximum size,logfile.0.gz is renamed logfile.1.gz, and the new logfile is closed, compressed, and renamed logfile.0.gz. By default, the logging utility creates up to 10 archive files in this manner. When the maximum number of archive files is reached, each time the active file reaches the maximum size the contents of the oldest archive file are lost (overwritten by the next oldest file). The logging utility by default also limits the users who can read log files to the root user and users who have the JUNOS maintenance permission. You can include the archive statement to change the maximum size of each file, how many archive files are created, and who can read log files. To configure values that apply to all log files, include the archive statement at the [edit system syslog] hierarchy level:
[edit system syslog] archive { files number; size size; (world-readable | no-world-readable); }

To configure values that apply to a particular log file, include the archive statement at the [edit system syslog file filename] hierarchy level:
[edit system syslog file filename] facility severity; archive { files number; size size; (world-readable | no-world-readable); } files number specifies the number of files to create before the oldest file is overwritten. The value can be from 1 through 1000. size size specifies the maximum size of each file. The value can be from 64 KB (64k) through 1 gigabyte (1g); to represent megabytes, use the letter m after the integer. There is no space between the digits and the k, m, or g units letter.

18

Configuring the Size and Number of Log Files

Chapter 1: Configuring System Log Messages

world-readable enables all users to read log files. To restore the default permissions, include the no-world-readable statement.

Including Priority Information in System Log Messages

A messages facility and severity level are together referred to as its priority. By default, messages logged in the standard JUNOS format do not include information about priority. To include priority information in standard-format messages directed to a file, include the explicit-priority statement at the [edit system syslog file filename] hierarchy level:
[edit system syslog file filename] facility severity; explicit-priority;

NOTE: Messages logged in structured-data format include priority information by default (structured-data format is available in JUNOS Release 8.3 and later and for file destinations only). If you include the structured-data statement at the [edit system syslog file filename] hierarchy level along with the explicit-priority statement, the explicit-priority statement is ignored and messages are logged in structured-data format. For information about the structured-data statement, see Logging Messages in Structured-Data Format on page 12. For information about the contents of a structured-data message, see Displaying a Log File from a Single-Chassis System on page 37.

To include priority information in messages directed to a remote machine or the other Routing Engine, include the explicit-priority statement at the [edit system syslog host (hostname | other-routing-engine)] hierarchy level:
[edit system syslog host (hostname | other-routing-engine)] facility severity; explicit-priority;

The priority recorded in a message always indicates the original, local facility name. If the facility-override statement is included for messages directed to a remote destination, the JUNOS system logging utility still uses the alternative facility for the messages themselves when directing them to the remote destination. For more information about alternative facilities, see Changing the Alternative Facility Name for Remote Messages on page 14. When the explicit-priority statement is included, the JUNOS logging utility prepends codes for the facility name and severity level to the message tag name, if the message has one:
FACILITY-severity[-TAG]

(The tag is a unique identifier assigned to some JUNOS system log messages; for more information, see Interpreting System Log Messages on page 38 and Displaying and Interpreting System Log Message Descriptions on page 49.)

Including Priority Information in System Log Messages

19

JUNOS 10.1 System Log Messages Reference

Table 9 on page 20 lists the facility codes that can appear in system log messages and maps them to facility names.

NOTE: If the second column in Table 9 on page 20 does not include the JUNOS facility name for a code, the facility cannot be included in a statement at the [edit system syslog] hierarchy level. The JUNOS Software might use the facilities in Table 9 on page 20and others that are not listedwhen reporting on internal operations

Table 9: Facility Codes Reported in Priority Information

Code AUTH JUNOS Facility Name authorization Type of Event or Error

Authentication and authorization attempts Authentication and authorization attempts that can be viewed by superusers only

AUTHPRIV

CHANGE

change-log

Changes to the JUNOS configuration Specified configuration is invalid on the routing platform type Messages written to /dev/console by the kernel console output driver Actions performed or errors encountered by the cron process

CONFLICT

conflict-log

CONSOLE

CRON

DAEMON

daemon

Actions performed or errors encountered by system processes Actions performed or errors encountered by the dynamic flow capture process Packet filtering actions performed by a firewall filter Actions performed or errors encountered by the FTP process Commands issued at the JUNOS CLI prompt or invoked by a client application such as a JUNOScript or NETCONF client

DFC

dfc

FIREWALL

firewall

FTP

ftp

INTERACT

interactive-commands

20

Including Priority Information in System Log Messages

Chapter 1: Configuring System Log Messages

Table 9: Facility Codes Reported in Priority Information (continued)

Code KERN JUNOS Facility Name kernel Type of Event or Error

Actions performed or errors encountered by the JUNOS kernel Actions performed or errors encountered by the Network Time Protocol (NTP) process

NTP

PFE

pfe

Actions performed or errors encountered by the Packet Forwarding Engine Actions performed or errors encountered by the JUNOS system logging utility

SYSLOG

USER

user

Actions performed or errors encountered by user-space processes

Table 10 on page 21 lists the numerical severity codes that can appear in system log messages and maps them to severity levels.
Table 10: Numerical Codes for Severity Levels Reported in Priority Information
Numerical Code 0 Severity Level emergency Description

System panic or other condition that causes the routing platform to stop functioning Conditions that require immediate correction, such as a corrupted system database Critical conditions, such as hard drive errors Error conditions that generally have less serious consequences than errors in the emergency, alert, and critical levels Conditions that warrant monitoring Conditions that are not errors but might warrant special handling

alert

critical

error

warning

notice

Including Priority Information in System Log Messages

21

JUNOS 10.1 System Log Messages Reference

Table 10: Numerical Codes for Severity Levels Reported in Priority Information (continued)
Numerical Code 6 Severity Level info Description

Events or nonerror conditions of interest Software debugging messages (these appear only if a technical support representative has instructed you to configure this severity level)

debug

In the following example, the CHASSISD_PARSE_COMPLETE message belongs to the daemon facility and is assigned severity info (6):
Aug 21 12:36:30 router1 chassisd[522]: %DAEMON-6-CHASSISD_PARSE_COMPLETE: Using new configuration

When the explicit-priority statement is not included, the priority does not appear in the message:
Aug 21 12:36:30 router1 chassisd[522]: CHASSISD_PARSE_COMPLETE: Using new configuration

For more information about message formatting, see Displaying and Interpreting System Log Messages on page 37.

Including the Year or Millisecond in Timestamps

By default, the timestamp recorded in a standard-format system log message specifies the month, date, hour, minute, and second when the message was logged, as in the following example:
Aug 21 12:36:30

To include the year, the millisecond, or both in the timestamp, include the time-format statement at the [edit system syslog] hierarchy level:
edit system syslog] time-format (year | millisecond | year millisecond);

The modified timestamp is used in messages directed to each destination configured by a file, console, or user statement at the [edit system syslog] hierarchy level, but not to destinations configured by a host statement.

22

Including the Year or Millisecond in Timestamps

Chapter 1: Configuring System Log Messages

The following example illustrates the format for a timestamp that includes both the millisecond (401) and the year (2006):
Aug 21 12:36:30.401 2006

NOTE: Messages logged in structured-data format (available in JUNOS Release 8.3 and later for file destinations) include the year and millisecond by default. If you include the structured-data statement at the [edit system syslog file filename] hierarchy level along with the time-format statement, the time-format statement is ignored and messages are logged in structured-data format. For information about the structured-data statement, see Logging Messages in Structured-Data Format on page 12. For information about the information in a structured-data message, see Displaying a Log File from a Single-Chassis System on page 37.

Using Regular Expressions to Refine the Set of Logged Messages

The predefined facilities group together related messages, but you can also use regular expression matching to specify more exactly which messages from a facility are logged to a file, a user terminal, or a remote destination. To specify the text string that must (or must not) appear in a message for the message to be logged to a destination, include the match statement and specify the regular expression which the text string must match:
match "regular-expression";

You can include this statement at the following hierarchy levels:

[edit system syslog file filename] (for a file) [edit system syslog user (username | *)] (for the terminal session of one or all

users)

[edit system syslog host (hostname | other-routing-engine)] (for a remote destination)

In specifying the regular expression, use the notation defined in POSIX Standard 1003.2 for extended (modern) UNIX regular expressions. Explaining regular expression syntax is beyond the scope of this document, but POSIX standards are available from the Institute of Electrical and Electronics Engineers (IEEE, http://www.ieee.org). Table 11 on page 24 specifies which character or characters are matched by some of the regular expression operators that you can use in the match statement. 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 match statement is not case-sensitive.

Using Regular Expressions to Refine the Set of Logged Messages

23

JUNOS 10.1 System Log Messages Reference

Table 11: Regular Expression Operators for the match Statement

Operator Matches

. (period) * (asterisk) + (plus sign) ? (question mark) | (pipe) ! (exclamation point)

One instance of any character except the space. Zero or more instances of the immediately preceding term. One or more instances of the immediately preceding term. Zero or one instance of the immediately preceding term. One of the terms that appear on either side of the pipe operator. Any string except the one specified by the expression, when the exclamation point appears at the start of the expression. Use of the exclamation point is JUNOS Softwarespecific. Start of a line when the caret appears outside square brackets. One instance of any character that does not follow it within square brackets, when the caret is the first character inside square brackets.

^ (caret)

$ (dollar sign) [ ] (paired square brackets)

End of a line. One instance of one of the enclosed alphanumeric characters. To indicate a range of characters, use a hyphen ( - ) to separate the beginning and ending characters of the range. For example, [a-z0-9] matches any letter or number. One instance of the evaluated value of the enclosed term. Parentheses are used to indicate the order of evaluation in the regular expression.

( ) (paired parentheses)

Using Regular Expressions

Filter messages that belong to the interactive-commands facility, directing those that include the string configure to the terminal of the root user:
[edit system syslog] user root { interactive-commands any; match .*configure.*; }

Messages like the following appear on the root users terminal when a user issues a configure command to enter configuration mode:
timestamp router-name mgd[PID]: UI_CMDLINE_READ_LINE: User 'user', command 'configure private'

Filter messages that belong to the daemon facility and have severity error or higher, directing them to the file /var/log/process-errors. Omit messages generated by the SNMP process (snmpd), instead directing them to the file /var/log/snmpd-errors:
[edit system syslog] file process-errors { daemon error; match !(.*snmpd.*);

24

Using Regular Expressions to Refine the Set of Logged Messages

Chapter 1: Configuring System Log Messages

} file snmpd-errors { daemon error; match .*snmpd.*; }

Disabling Logging of a Facility

To disable the logging of messages that belong to a particular facility, include the facility none statement in the configuration. This statement is useful when, for example, you want to log messages that have the same severity level and belong to all but a few facilities. Instead of including a statement for each facility you want to log, you can include the any severity statement and then a facility none statement for each facility that you do not want to log. For example, the following logs all messages at the error level or higher to the console, except for messages from the daemon and kernel facilities. Messages from those facilities are logged to the file /var/log/internals instead:
[edit system syslog] console { any error; daemon none; kernel none; } file internals { daemon info; kernel info; }

Examples: Configuring System Logging

Log messages about all commands entered by users at the CLI prompt or invoked by client applications such as JUNOScript or NETCONF clients, and all authentication or authorization attempts, both to the file cli-commands and to the terminal of any user who is logged in:
[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:

[edit system] syslog { file alarms { kernel warning;

Disabling Logging of a Facility

25

JUNOS 10.1 System Log Messages Reference

} }

Configure the handling of messages of various types, as described in the comments. Information is logged to two files, to the terminal of user alex, to a remote machine, and to the console:
[edit system] syslog { /* write all security-related messages to file /var/log/security */ file security { authorization info; interactive-commands info; } /* write messages about potential problems to file /var/log/messages: */ /* messages from authorization facility at level notice and above, */ /* messages from all other facilities at level warning and above */ file messages { authorization notice; any warning; } /* write all messages at level critical and above to terminal of user alex if */ /* that user is logged in */ user alex { any critical; } /* write all messages from the daemon facility at level info and above, and */ /* messages from all other facilities at level warning and above, to the */ /* machine monitor.mycompany.com */ host monitor.mycompany.com { daemon info; any warning; } /* write all messages at level error and above to the system console */ console { any error; } }

Configure the handling of messages generated when users issue JUNOS CLI commands, by specifying the interactive-commands facility at the following severity levels:

infoLogs a message when users issue any command at the CLI operational or

configuration mode prompt. The example writes the messages to the file /var/log/user-actions.

noticeLogs a message when users issue the configuration mode commands rollback and commit. The example writes the messages to the terminal of user philip. warningLogs a message when users issue a command that restarts a software

process. The example writes the messages to the console.

[edit system] syslog {

26

Examples: Configuring System Logging

Chapter 1: Configuring System Log Messages

file user-actions { interactive-commands info; } user philip { interactive-commands notice; } console { interactive-commands warning; } }

Examples: Configuring System Logging

27

JUNOS 10.1 System Log Messages Reference

Configuring System Logging for a Routing Matrix

This section explains how to configure system logging for the T640 Internet routing nodes and TX Matrix platform in a routing matrix. It assumes you are familiar with system logging for single-chassis systems, as described in Configuring System Logging for a Single-Chassis System on page 7. For more information about routing matrixes, see the JUNOS System Basics Configuration Guide and the TX Matrix Platform Hardware Guide. To configure system logging for all platforms in a routing matrix, include the syslog statement at the [edit system] hierarchy level on the TX Matrix platform. The syslog statement applies to every platform in the routing matrix.
[edit system] syslog { archive { files number; size size; (world-readable | no-world-readable); } console { facility severity; } file filename { facility severity; explicit-priority; match "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; time-format (year | millisecond | year millisecond); user (username | *) { facility severity ; match "regular-expression"; } }

28

Configuring System Logging for a Routing Matrix

Chapter 1: Configuring System Log Messages

When included in the configuration on the TX Matrix platform, the following configuration statements have the same effect as on a single-chassis system, except that they apply to every platform in the routing matrix:

archiveSets the size and number of log files archived on each platform in the

routing matrix. See Configuring the Size and Number of Log Files on page 18.

consoleDirects the specified messages to the console of each platform in the

routing matrix. See Directing Messages to the Console on page 13.

fileDirects the specified messages to a file of the same name on each platform

in the routing matrix. See Directing Messages to a Log File on page 11.

matchLimits the set of messages logged to a destination to those that contain

(or do not contain) a text string matching a regular expression. See Using Regular Expressions to Refine the Set of Logged Messages on page 23. The separate match statement at the [edit system syslog host scc-master] hierarchy level applies to messages forwarded from the T640 routing nodes to the TX Matrix platform. See Configuring Optional Features for Forwarded Messages on page 33.

source-addressSets the IP address of the routing platform to report in system

log messages as the message source, when the messages are directed to the remote machines specified in all host hostname statements at the [edit system syslog] hierarchy level, for each platform in the routing matrix. The address is not reported in messages directed to the other Routing Engine on each platform or forwarded to the TX Matrix platform by the T640 routing nodes. See Specifying an Alternative Source Address for System Log Messages on page 14.

structured-dataWrites messages to a file in structured-data format. See Logging

Messages in Structured-Data Format on page 12.

time-formatAdds the millisecond, year, or both to the timestamp in each

standard-format message. See Including the Year or Millisecond in Timestamps on page 22.

userDirects the specified messages to the terminal session of one or more

specified users on each platform in the routing matrix that they are logged in to. See Directing Messages to a User Terminal on page 12. The effect of the other statements differs somewhat for a routing matrix than for a single-chassis system. For more information, see the following sections:

Configuring Message Forwarding in the Routing Matrix on page 29 Configuring Optional Features for Forwarded Messages on page 33 Directing Messages to a Remote Destination from the Routing Matrix on page 34 Configuring System Logging Differently on Each Platform on page 35

Configuring Message Forwarding in the Routing Matrix

By default, the master Routing Engine on each T640 routing node forwards to the master Routing Engine on the TX Matrix platform all messages from all facilities with severity info and higher. To change the facility, the severity level, or both, include

Configuring System Logging for a Routing Matrix

29

JUNOS 10.1 System Log Messages Reference

the host scc-master statement at the [edit system syslog] hierarchy level on the TX Matrix platform:
[edit system syslog] host scc-master { facility severity; }

To disable message forwarding, set the facility to any and the severity level to none:
[edit system syslog] host scc-master { any none; }

In either case, the setting applies to all T640 routing nodes in the routing matrix. To capture the messages forwarded by the T640 routing nodes (as well as messages generated on the TX Matrix platform itself), you must also configure system logging on the TX Matrix platform. Direct the messages to one or more destinations by including the appropriate statements at the [edit system syslog] hierarchy level on the TX Matrix platform:

To a file, as described in Directing Messages to a Log File on page 11. To the terminal session of one or more specific users (or all users), as described in Directing Messages to a User Terminal on page 12. To the console, as described in Directing Messages to the Console on page 13. To a remote machine that is running the syslogd utility or to the other Routing Engine. For more information, see Directing Messages to a Remote Destination from the Routing Matrix on page 34.

As previously noted, the configuration statements included on the TX Matrix platform also configure the same destinations on each T640 routing node. When specifying the severity level for local messages (at the [edit system syslog (file | host | console | user)] hierarchy level) and forwarded messages (at the [edit system syslog host scc-master] hierarchy level), you can set the same severity level for both, set a lower severity level for local messages, or set a higher severity level for local messages. The following examples describe the consequence of each configuration. (For simplicity, the examples use the any facility in every case. You can also specify different severities for different facilities, with more complex consequences.)

Messages Logged When Local and Forwarded Severity Level Are the Same on page 30 Messages Logged When Local Severity Level Is Lower on page 31 Messages Logged When Local Severity Level Is Higher on page 32

Messages Logged When Local and Forwarded Severity Level Are the Same
When the severity level is the same for local and forwarded messages, the log on the TX Matrix platform contains all messages from the logs on the T640 routing

30

Messages Logged When Local and Forwarded Severity Level Are the Same

Chapter 1: Configuring System Log Messages

nodes. For example, you can specify severity info for the /var/log/messages file, which is the default severity level for messages forwarded by T640 routing nodes:
[edit system syslog] file messages { any info; }

Table 12 on page 31 pecifies which messages are included in the logs on the T640 routing nodes and the TX Matrix platform
Table 12: Example: Local and Forwarded Severity Level Are Both info
Log Location Source of Messages Lowest Severity Included info info info

T640 routing node TX Matrix platform

Local Local Forwarded from T640 routing nodes

Messages Logged When Local Severity Level Is Lower

When the severity level is lower for local messages than for forwarded messages, the log on the TX Matrix platform includes fewer forwarded messages than when the severities are the same. Locally generated messages are still logged at the lower severity level, so their number in each log is the same as when the severities are the same. For example, you can specify severity notice for the /var/log/messages file and severity critical for forwarded messages
[edit system syslog] file messages { any notice; } host scc-master { any critical; }

Messages Logged When Local Severity Level Is Lower

31

JUNOS 10.1 System Log Messages Reference

Table 13 on page 32 specifies which messages are included in the logs on the T640 routing nodes and the TX Matrix platform. The T640 routing nodes forward only those messages with severity critical and higher, so the log on the TX Matrix platform does not include the messages with severity error, warning, or notice that the T640 routing nodes log locally:
Table 13: Example: Local Severity Is notice, Forwarded Severity Is critical
Log Location Source of Messages Lowest Severity Included notice notice critical

T640 routing node TX Matrix platform

Local Local Forwarded from T640 routing nodes

Messages Logged When Local Severity Level Is Higher

When the severity level is higher for local messages than for forwarded messages, the log on the TX Matrix platform includes fewer forwarded messages than when the severities are the same, and all local logs contain fewer messages overall. For example, you can specify severity critical for the /var/log/messages file and severity notice for forwarded messages:
[edit system syslog] file messages { any critical; } host scc-master { any notice; }

Table 14 on page 32 specifies which messages are included in the logs on the T640 routing nodes and the TX Matrix platform. Although the T640 routing nodes forward messages with severity notice and higher, the TX Matrix platform discards any of those messages with severity lower than critical (does not log forwarded messages with severity error, warning, or notice). None of the logs include messages with severity error or lower.
Table 14: Example: Local Severity Is critical, Forwarded Severity Is notice
Log Location Source of Messages Lowest Severity Included critical critical critical

T640 routing node TX Matrix platform

Local Local Forwarded from T640 routing nodes

32

Messages Logged When Local Severity Level Is Higher

Chapter 1: Configuring System Log Messages

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.

Configuring Optional Features for Forwarded Messages

To configure additional optional features when specifying how the T640 routing nodes forward messages to the TX Matrix platform, include statements at the [edit system syslog host scc-master] hierarchy level. To include priority information (facility and severity level) in each forwarded message, include the explicit-priority statement. To insert a text string in each forwarded message, include the log-prefix statement. To use regular expression matching to specify more exactly which messages from a facility are forwarded, include the match statement.
[edit system syslog host scc-master] facility severity; explicit-priority; log-prefix string; match "regular-expression"; }

NOTE: You can also include the facility-override statement at the [edit system syslog host scc-master] hierarchy level, but we do not recommend doing so. It is not necessary to use alternative facilities for messages forwarded to the TX Matrix platform, because it runs the JUNOS system logging utility and can interpret the JUNOS-specific facilities. For more information about alternative facilities, see Changing the Alternative Facility Name for Remote Messages on page 14. 1. Including Priority Information in Forwarded Messages on page 33 2. Adding a Text String to Forwarded Messages on page 34 3. Using Regular Expressions to Refine the Set of Forwarded Messages on page 34

Including Priority Information in Forwarded Messages

When you include the explicit-priority statement at the [edit system syslog host scc-master] hierarchy level, messages forwarded to the TX Matrix platform include priority information. For the information to appear in a log file on the TX Matrix platform, you must also include the explicit-priority statement at the [edit system syslog file filename] hierarchy level for the file on the TX Matrix platform. As a consequence, the log file with the same name on each platform in the routing matrix also includes priority information for locally generated messages. To include priority information in messages directed to a remote machine from all platforms in the routing matrix, also include the explicit-priority statement at the [edit system syslog host hostname] hierarchy level for the remote machine. For more information, see Directing Messages to a Remote Destination from the Routing Matrix on page 34. In the following example, the /var/log/messages file on all platforms includes priority information for messages with severity notice and higher from all facilities. The log

Configuring Optional Features for Forwarded Messages

33

JUNOS 10.1 System Log Messages Reference

on the TX Matrix platform also includes messages with those characteristics forwarded from the T640 routing nodes.
[edit system syslog] host scc-master { any notice; explicit-priority; } file messages { any notice; explicit-priority; }

Adding a Text String to Forwarded Messages

When you include the log-prefix statement at the [edit system syslog host scc-master] hierarchy level, the string that you define appears in every message forwarded to the TX Matrix platform. For more information, see Adding a Text String to System Log Messages on page 17.

Using Regular Expressions to Refine the Set of Forwarded Messages

When you include the match statement at the [edit system syslog host scc-master] hierarchy level, the regular expression that you specify controls which messages from the T640 routing nodes are forwarded to the TX Matrix platform. The regular expression is not applied to messages from the T640 routing notes that are directed to destinations other than the TX Matrix platform. For more information about regular expression matching, see Using Regular Expressions to Refine the Set of Logged Messages on page 23.

Directing Messages to a Remote Destination from the Routing Matrix

You can configure a routing matrix to direct system logging messages to a remote machine or the other Routing Engine on each routing platform, just as on a single-chassis system. Include the host statement at the [edit system syslog] hierarchy level on the TX Matrix platform:
[edit system syslog] host (hostname | other-routing-engine) { facility severity ; explicit-priority; facility-override facility; log-prefix string; match "regular-expression"; } source-address source-address;

The TX Matrix platform directs messages to a remote machine or the other Routing Engine in the same way as a single-chassis system, and the optional statements (explicit-priority, facility-override, log-prefix, match, and source-address) also have the same effect as on a single-chassis system. For more information, see Directing Messages to a Remote Machine or the Other Routing Engine on page 13.

34

Adding a Text String to Forwarded Messages

Chapter 1: Configuring System Log Messages

For the TX Matrix platform to include priority information when it directs messages that originated on a T640 routing node to the remote destination, you must also include the explicit-priority statement at the [edit system syslog host scc-master] hierarchy level. The other-routing-engine statement does not interact with message forwarding from the T640 routing nodes to the TX Matrix platform. For example, if you include the statement in the configuration for the Routing Engine in slot 0 (re0), the re0 Routing Engine on each T640 routing node sends messages to the re1 Routing Engine on its platform only. It does not also send messages directly to the re1 Routing Engine on the TX Matrix platform. Because the configuration on the TX Matrix platform applies to the T640 routing nodes, any T640 routing node that has interfaces for direct access to the Internet also directs messages to the remote machine which has the following consequences:

If the T640 routing nodes are configured to forward messages to the TX Matrix platform (as in the default configuration), the remote machine receives two copies of some messages: one directly from the T640 routing node and the other from the TX Matrix platform. Which messages are duplicated depends on whether the severities are the same for local logging and for forwarded messages. For more information, see Configuring Message Forwarding in the Routing Matrix on page 29. If the source-address statement is configured at the [edit system syslog] hierarchy level, all platforms in the routing matrix report the same source routing platform in messages directed to the remote machine. This is appropriate, because the routing matrix functions as a single routing platform. If the log-prefix statement is included, the messages from all platforms in the routing matrix include the same text string. You cannot use the string to distinguish between the platforms in the routing matrix.

Configuring System Logging Differently on Each Platform

We recommend that all platforms in a routing matrix use the same configuration, which implies that you include system logging configuration statements on the TX Matrix platform only. 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. To configure platforms separately, include configuration statements in the appropriate groups at the [edit groups] hierarchy level on the TX Matrix platform:

To configure settings that apply to the TX Matrix platform but not the T640 routing nodes, include them in the re0 and re1 configuration groups. To configure settings that apply to particular T640 routing nodes, include them in the lccn-re0 and lccn-re1 configuration groups, where n is the line-card chassis (LCC) index number of the routing node.

Configuring System Logging Differently on Each Platform

35

JUNOS 10.1 System Log Messages Reference

When you use configuration groups, do not issue CLI configuration-mode commands to change the statements at the [edit system syslog] hierarchy level on the TX Matrix platform. If you do, the resulting statements overwrite the statements defined in configuration groups and apply to the T640 routing nodes also. (We further recommend that you do not issue CLI configuration mode commands on the T640 routing nodes at any time.) For more information about the configuration groups for a routing matrix, see the chapter about configuration groups in the JUNOS CLI User Guide. The following example shows how to configure the /var/log/messages files on three platforms to include different sets of messages:

On the TX Matrix platform, local messages with severity info and higher from all facilities. The file does not include messages from the T640 routing nodes, because the host scc-master statement disables message forwarding. On the T640 routing node designated LCC0, messages from the authorization facility with severity info and higher. On the T640 routing node designated LCC1, messages with severity notice from all facilities.
[edit groups] re0 { system { syslog { file messages { any info; } host scc-master { any none; } } } } re1 { ... 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;

36

Configuring System Logging Differently on Each Platform

Chapter 1: Configuring System Log Messages

} } } } lcc0-re1 { ... same statements as for lcc1-re0 ... }

Displaying and Interpreting System Log Messages

This section explains how to display a log file and interpret the contents of system log messages: For more information about the commands discussed in this section, see the JUNOS System Basics and Services Command Reference.

Displaying a Log File from a Single-Chassis System on page 37 Displaying a Log File from a Routing Matrix on page 37 Interpreting System Log Messages on page 38 Format of the message-source Field on page 45 Examples: Displaying a Log File on page 48

Displaying a Log File from a Single-Chassis System

To display a log file stored on a single-chassis system, enter JUNOS CLI operational mode and issue either of the following commands:
user@host> show loglog-filename user@host> file show log-file-pathname

By default, the commands display the file stored on the local Routing Engine. To display the file stored on a particular Routing Engine, prefix the file- or pathname with the string re0 or re1 and a colon. The following examples both display the /var/log/messages file stored on the Routing Engine in slot 1:
user@host> show log re1:messages user@host> file show re1:/var/log/messages

For information about the fields in a log message, see Interpreting System Log Messages on page 38. For examples, see Examples: Displaying a Log File on page 48.

Displaying a Log File from a Routing Matrix

One way to display a log file stored on the local Routing Engine of any of the individual platforms in a routing matrix (T640 routing nodes or TX Matrix platform) is to log in to a Routing Engine on the platform, enter JUNOS CLI operational mode, and issue the show log or file show command described in Displaying a Log File from a Single-Chassis System on page 37.

Displaying and Interpreting System Log Messages

37

JUNOS 10.1 System Log Messages Reference

To display a log file stored on a T640 routing node during a terminal session on the TX Matrix platform, issue the show log or file show command and add a prefix that specifies the T640 routing nodes LCC index number as lccn, followed by a colon. The index can be from 0 (zero) through 3:
user@host> show log lccn:log-filename user@host> file show lccn:log-file-pathname

By default, the show log and file show commands display the specified log file stored on the master Routing Engine on the T640 routing node. To display the log from a particular Routing Engine, prefix the file- or pathname with the string lccn-master, lccn-re0, or lccn-re1, followed by a colon. The following examples all display the /var/log/messages file stored on the master Routing Engine (in slot 0) on routing node LCC2:
user@host> user@host> user@host> user@host> show log lcc2:messages show log lcc2-master:messages show log lcc2-re0:messages file show lcc2:/var/log/messages

If the T640 routing nodes are forwarding messages to the TX Matrix platform (as in the default configuration), another way to view messages generated on a T640 routing node during a terminal session on the TX Matrix platform is simply to display a local log file. However, the messages are intermixed with messages from other T640 routing nodes and the TX Matrix platform itself. For more information about message forwarding, see Configuring Message Forwarding in the Routing Matrix on page 29. For information about the fields in a log message, see Interpreting System Log Messages on page 38. For examples, see Examples: Displaying a Log File on page 48.

Interpreting System Log Messages

The fields in a message written to the system log depend on whether the message was generated by a JUNOS process or subroutine library, or by services on a PIC, and whether it is in standard format or structured-data format. For more information, see the following sections:

Interpreting Messages Generated in Structured-Data Format on page 38 Interpreting Messages Generated in Standard Format by a JUNOS Process or Library on page 43 Interpreting Messages Generated in Standard Format by Services on a PIC on page 44

Interpreting Messages Generated in Structured-Data Format

Beginning in JUNOS Release 8.3, when the structured-data statement is included in the configuration for a log file, JUNOS processes and software libraries write messages to the file in structured-data format instead of the standard JUNOS format. For information about the structured-data statement, see Logging Messages in Structured-Data Format on page 12.

38

Interpreting Messages Generated in Structured-Data Format

Chapter 1: Configuring System Log Messages

Structured-format makes it easier for automated applications to extract information from the message. 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 those values. In standard format, the variables are interspersed in the message text and not identified as variables. The structured-data format for a message includes the following fields (which appear here on two lines only for legibility):
<priority code>version timestamp hostname process processID TAG [junos@2636.platform variable-value-pairs] message-text

Table 15 on page 39 describes the fields. If the system logging utility cannot determine the value in a particular field, a hyphen ( - ) appears instead.
Table 15: Fields in Structured-Data Messages
Field <priority code> Description Examples

Number that indicates the messages facility and severity. It is calculated by multiplying the facility number by 8 and then adding the numerical value of the severity. For a mapping of the numerical codes to facility and severity, see Table 16 on page 41. Version of the Internet Engineering Task Force (IETF) system logging protocol specification. Time when the message was generated, in one of two representations:

<165> for a message from the pfe facility (facility=20) with severity notice (severity=5).

version

1 for the initial version

timestamp

YYYY-MM-DDTHH:MM:SS.MSZ is the

year, month, day, hour, minute, second and millisecond in Universal Coordinated Time (UTC)

2007-02-15T09:17:15.719Z is 9:17 AM UTC on 15 February 2007. 2007-02-15T01:17:15.719 -08:00 is the same timestamp expressed as Pacific Standard Time in the United States.

YYYY-MM-DDTHH:MM:SS.MS+/-HH:MM

is the year, month, day, hour, minute, second and millisecond in local time; the hour and minute that follows the plus sign (+) or minus sign (-) is the offset of the local time zone from UTC
hostname

Name of the host that originally generated the message. Name of the JUNOS process that generated the message. UNIX process ID (PID) of the JUNOS process that generated the message.

router1

process

mgd

processID

3046

Interpreting Messages Generated in Structured-Data Format

39

JUNOS 10.1 System Log Messages Reference

Table 15: Fields in Structured-Data Messages (continued)

Field TAG Description Examples

JUNOS system log message tag, which uniquely identifies the message. For a list of the tags described in this reference, see System Log Messages on page 53. An identifier for the type of hardware platform that generated the message. The junos@2636 prefix indicates that the platform runs the JUNOS Software. It is followed by a dot-separated numerical identifier for the platform type. For a list of the identifiers, see Table 17 on page 42. A variable-value pair for each element in the message-text string that varies depending on the circumstances that triggered the message. Each pair appears in the format variable = "value". English-language description of the event or error (omitted if the brief statement is included at the [edit
system syslog file filename structured-data] hierarchy level). For

UI_DBASE_LOGOUT_EVENT

junos@2636.platform

junos@2636.1.1.1.2.18 for the M120 router

variable-value-pairs

username="regress"

message-text

User 'regress' exiting configuration mode

the text for each message, see the chapters following System Log Messages on page 53.

By default, the structured-data version of a message includes English text at the end, as in the following example (which appears on multiple lines only for legibility):
<165>1 2007-02-15T09:17:15.719Z router1 mgd 3046 UI_DBASE_LOGOUT_EVENT [junos@2636.1.1.1.2.18 username="regress"] User 'regress' exiting configuration mode

When the brief statement is included at the [edit system syslog file filename structured-data ] hierarchy level, the English text is omitted, as in this example:
<165>1 2007-02-15T09:17:15.719Z router1 mgd 3046 UI_DBASE_LOGOUT_EVENT [junos@2636.1.1.1.2.18 username="regress"]

Table 16 on page 41 maps the codes that appear in the priority-code field to facility and severity level.

NOTE: Not all of the facilities and severities listed in Table 16 on page 41 can be included in statements at the [edit system syslog] hierarchy level (some are used by internal processes). For a list of the facilities and severity levels that can be included in the configuration, see Specifying the Facility and Severity of Messages to Include in the Log on page 9.

40

Interpreting Messages Generated in Structured-Data Format

Chapter 1: Configuring System Log Messages

Table 16: Facility and Severity Codes in the priority-code Field

Severity emergency 1 8 16 24 32 40 48 56 64 72 80

Facility (number) kernel (0) user (1) mail (2) daemon (3) authorization (4) syslog (5) printer (6) news (7) uucp (8) clock (9) authorization-private (10) ftp (11) ntp (12) security (13) console (14) local0 (16) dfc (17) local2 (18) firewall (19) pfe (20) conflict-log (21) change-log (22) interactive-commands (23)

alert 1 9 17 25 33 41 49 57 65 73 81

critical 2 10 18 26 34 42 50 58 66 74 82

error 3 11 19 27 35 43 51 59 67 75 83

warning 4 12 20 28 36 44 52 60 68 76 84

notice 5 13 21 29 37 45 53 61 69 77 85

info 6 14 22 30 38 46 54 62 70 78 86

debug 7 15 23 31 39 47 55 63 71 79 87

88 96 104 112 128 136 144 152 160 168 176 184

89 97 105 113 129 137 145 153 161 169 177 185

90 98 106 114 130 138 146 154 162 170 178 186

91 99 107 115 131 139 147 155 163 171 179 187

92 100 108 116 132 140 148 156 164 172 180 188

93 101 109 117 133 141 149 157 165 173 181 189

94 102 110 118 134 142 150 158 166 174 182 190

95 103 111 119 135 143 151 159 167 175 183 191

Table 17 on page 42 lists the numerical identifiers for routing platforms that appear in the platform field. The identifier is derived from the platforms SNMP object

Interpreting Messages Generated in Structured-Data Format

41

JUNOS 10.1 System Log Messages Reference

identifier (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 1.1.1.2.1 1.1.1.2.2 1.1.1.2.3 1.1.1.2.4 1.1.1.2.5 1.1.1.2.6 1.1.1.2.7 1.1.1.2.8 1.1.1.2.9 1.1.1.2.10 1.1.1.2.11 1.1.1.2.13 1.1.1.2.14 1.1.1.2.15 1.1.1.2.17 1.1.1.2.18 1.1.1.2.19 1.1.1.2.20 1.1.1.2.23 1.1.1.2.24 Platform Name

M40 router M20 router M160 router M10 router M5 router T640 routing node T320 router M40e router M320 router M7i router M10i router J2300 Services Router J4300 Services Router J6300 Services Router TX Matrix platform M120 router J4350 Services Router J6350 Services Router J2320 Services Router J2350 Services Router

42

Interpreting Messages Generated in Structured-Data Format

Chapter 1: Configuring System Log Messages

Interpreting Messages Generated in Standard Format by a JUNOS Process or Library

The syntax of a standard-format message generated by a JUNOS Software process or subroutine library depends on whether it includes priority information:

When the explicit-priority statement is included at the [edit system syslog file filename] or [edit system syslog host (hostname | other-routing-engine)] hierarchy level, a system log message has the following syntax:
timestamp message-source: %facilityseverityTAG: message-text

When directed to the console or to users, or when the explicit-priority statement is not included for files or remote hosts, a system log message has the following syntax:
timestamp message-source: TAG: message-text

Table 18 on page 43 describes the message fields.

Table 18: Fields in Standard-Format Messages Generated by a JUNOS Process or Library
Field timestamp message-source Description

Time at which the message was logged. Identifier of the process or component that generated the message and the routing platform on which the message was logged. This field includes two or more subfields, depending on how system logging is configured. See Format of the message-source Field on page 45. Code that specifies the facility to which the system log message belongs. For a mapping of codes to facility names, see Table 9 on page 20. Numerical code that represents the severity level assigned to the system log message. For a mapping of codes to severity names, see Table 10 on page 21. Text string that uniquely identifies the message, in all uppercase letters and using the underscore (_) to separate words. The tag name begins with a prefix that indicates the generating software process or library. The entries in this reference are ordered alphabetically by this prefix. Not all processes on a routing platform use tags, so this field does not always appear. For a list of prefixes for the tags described in this reference, see System Log Messages on page 53.

facility

severity

TAG

message-text

Text of the message. For the text for each message, see the chapters following System Log Messages on page 53.

Interpreting Messages Generated in Standard Format by a JUNOS Process or Library

43

JUNOS 10.1 System Log Messages Reference

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:
timestamp (FPC Slot fpc-slot, PIC Slot pic-slot) {service-set} [SERVICE]: optional-string TAG: message-text

NOTE: System logging for services on PICs is not configured at the [edit system syslog] hierarchy level as discussed in this chapter. For configuration information, see the JUNOS Services Interfaces Configuration Guide. The (FPC Slot fpc-slot, PIC Slot pic-slot) field appears only when the standard system logging utility that runs on the Routing Engine writes the messages to the system log. When the PIC writes the message directly, the field does not appear.

Table 19 on page 44 describes the message fields.

Table 19: Fields in Messages Generated by a PIC
Field timestamp fpc-slot Description

Time at which the message was logged. Slot number of the Flexible PIC Concentrator (FPC) that houses the PIC that generated the message. Number of the PIC slot on the FPC in which the PIC that generated the message resides. Name of the service set that generated the message. Code representing the service that generated the message. The codes include the following:

pic-slot

service-set SERVICE

FWNATNetwork Address Translation (NAT) service IDSIntrusion detection service

optional-string

A text string that appears if the configuration for the PIC includes the log-prefix statement at the [edit interfaces interface-name services-options syslog] hierarchy level. For more information, see the JUNOS Services Interfaces Configuration Guide. Text string that uniquely identifies the message, in all uppercase letters and using the underscore (_) to separate words. The tag name begins with a prefix that indicates the generating PIC. The entries in this reference are ordered alphabetically by this prefix. Text of the message. For the text of each message, see System Log Messages on page 53.

TAG

message-text

44

Interpreting Messages Generated in Standard Format by Services on a PIC

Chapter 1: Configuring System Log Messages

Format of the message-source Field

The message-source field discussed in Interpreting Messages Generated in Standard Format by a JUNOS Process or Library on page 43 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. For more information, see the following sections:

The message-source Field on a Single-Chassis System on page 45 The message-source Field on a TX Matrix Platform on page 45 The message-source Field on a T640 Routing Node in a Routing Matrix on page 47

The message-source Field on a Single-Chassis System

The format of the message-source field in a message on a single-chassis system depends on whether the message was generated on the local Routing Engine or the other Routing Engine (on a system with two Routing Engines installed and operational). Messages from the other Routing Engine appear only if its configuration includes the other-routing-engine statement at the [edit system syslog host] hierarchy level.

When the local Routing Engine generated the message, there are two subfields:
hostname process[process-ID]

When the other Routing Engine generated the message, there are three subfields:
hostname reX process[process-ID]

hostname is the hostname of the local Routing Engine. process[process-ID] is the name and PID of the process that generated the message. If the reX field also appears, the process is running on the other Routing Engine. If a

process does not report its PID, the [process-ID] part does not appear.
reX indicates that the other Routing Engine generated the message (X is 0 or 1).

The message-source Field on a TX Matrix Platform

The format of the message-source field in a message on a TX Matrix platform depends on several factors:

Whether the message was generated on the TX Matrix platform or a T640 routing node in the routing matrix. By default, the master Routing Engine on each T640 routing node forwards messages from all facilities with severity info and higher to the master Routing Engine on the TX Matrix platform. When you configure system logging on the TX Matrix platform, its logs include the forwarded messages. For more information, see Configuring Message Forwarding in the Routing Matrix on page 29.

The message-source Field on a Single-Chassis System

45

JUNOS 10.1 System Log Messages Reference

Whether the message was generated on the local Routing Engine or the other Routing Engine on the originating machine (TX Matrix platform or T640 routing node). Messages from the other Routing Engine appear only if its configuration includes the other-routing-engine statement at the [edit system syslog host] hierarchy level. Whether the message was generated by a kernel or user-space process, or by the microkernel on a hardware component.

Table 20 on page 46 specifies the format of the message-source field in the various cases.
Table 20: Format of message-source Field in Messages Logged on TX Matrix Platform
Generating Routing Engine Process or Component

Generating Machine

Format hostname process[processID] hostname scc-reX process[processID] hostname scc-reX scc-componentZ process hostname scc-reX scc-componentZ process hostname lccY-masterprocess[processID] hostname lccY-master scc-componentZ process hostname lccY-master lccY-reX process[processID] hostname lccY-master lccY-reX lccY-componentZ process

TX Matrix platform

Local

Process Component

Other

Process

Component

T640 routing node

Local

Process

Component

Other

Process

Component

hostname is the hostname of the local Routing Engine on the TX Matrix platform. lccY-master is the master Routing Engine on the T640 routing node with the indicated LCC index number (Y is from 0 through 3). lccY-reX indicates that the backup Routing Engine on the T640 routing node generated the message (X is 0 or 1). The routing node has the indicated LCC index number (Y matches the value in the lccY-master field. lccY-componentZ process identifies the hardware component and process on the T640 routing node that generated the message (Y matches the value in the lccY-master field and the range of values for Z depends on the component type). For example, lcc2-fpc1 PFEMAN refers to a process on the FPC in slot 1 on the T640 routing node with index

LCC2.

46

The message-source Field on a TX Matrix Platform

Chapter 1: Configuring System Log Messages

process[process-ID] is the name and PID of the kernel or user-space process that generated the message. If the scc-reX or lccY-reX field also appears, the process is

running on the other Routing Engine. If a process does not report its PID, the [process-ID] part does not appear.
scc-componentZ process identifies the hardware component and process on the TX Matrix platform that generated the message (the range of values for Z depends on the component type). For example, spmb1 GSIB refers to a process on one of the

processor boards in the Switch Interface Board (SIB) with index 1.

scc-reX indicates that the other Routing Engine on the TX Matrix platform generated the message (X is 0 or 1).

The message-source Field on a T640 Routing Node in a Routing Matrix

The format of the message-source field in a message on a T640 routing node in a routing matrix depends on two factors:

Whether the message was generated on the local Routing Engine or the other Routing Engine. Messages from the other Routing Engine appear only if its configuration includes the other-routing-engine statement at the [edit system syslog host] hierarchy level. Whether the message was generated by a kernel or user-space process, or by the microkernel on a hardware component.

Table 21 on page 47 specifies the format of the message-source field in the various cases.
Table 21: Format of message-source Field in Messages Logged on TX Matrix Platform
Generating Routing Engine Process or Component Format hostname-lccY process[processID] hostname-lccY lccY-componentZ process hostname-lccY lccY-reX process[processID] hostname-lccY lccY-reX lccY-componentZ process

Local

Process

Component

Other

Process

Component

hostname-lccY is the hostname of the local Routing Engine and the T640 routing

nodes LCC index number.

lccY-componentZ process identifies the hardware component and process that generated the message (Y matches the value in the hostname-lccY field and the range of values for Z depends on the component type). For example, lcc0-fpc0 CMLC refers

to a process on the FPC in slot 0. The T640 routing node has index LCC0 in the routing matrix.

The message-source Field on a T640 Routing Node in a Routing Matrix

47

JUNOS 10.1 System Log Messages Reference

lccY-reX indicates that the other Routing Engine on the routing node generated the message (Y matches the value in the hostname-lccY field and X is 0 or 1). process[process-ID] is the name and PID of the kernel or user-space process that generated the message. If the lccY-reX field also appears, the process is running on the other Routing Engine. If a process does not report its PID, the [process-ID] part

does not appear.

Examples: Displaying a Log File

Display the contents of the /var/log/messages file stored on the local Routing Engine. (The /var/log directory is the default location for log files, so you do not need to include it in the filename. The messages file is a commonly configured destination for system log messages.)
user@host> show log messages Apr 11 10:27:25 router1 mgd[3606]: UI_DBASE_LOGIN_EVENT: User 'barbara' entering configuration mode Apr 11 10:32:22 router1 mgd[3606]: UI_DBASE_LOGOUT_EVENT: User 'barbara' exiting configuration mode Apr 11 11:36:15 router1 mgd[3606]: UI_COMMIT: User 'root' performed commit: no comment Apr 11 11:46:37 router1 mib2d[2905]: SNMP_TRAP_LINK_DOWN: ifIndex 82, ifAdminStatus up(1), ifOperStatus down(2), ifName at-1/0/0

Display the contents of the file /var/log/processes, which has been previously configured to include messages from the daemon facility. When issuing the file show command, you must specify the full pathname of the file:
user@host> file show /var/log/processes Feb 22 08:58:24 router1 snmpd[359]: SNMPD_TRAP_WARM_START: trap_generate_warm: SNMP trap: warm start Feb 22 20:35:07 router1 snmpd[359]: SNMPD_THROTTLE_QUEUE_DRAINED: trap_throttle_timer_handler: cleared all throttled traps Feb 23 07:34:56 router1 snmpd[359]: SNMPD_TRAP_WARM_START: trap_generate_warm: SNMP trap: warm start Feb 23 07:38:19 router1 snmpd[359]: SNMPD_TRAP_COLD_START: trap_generate_cold: SNMP trap: cold start

Display the contents of the file /var/log/processes when the explicit-priority statement is included at the [edit system syslog file processes] hierarchy level:
user@host> file show /var/log/processes Feb 22 08:58:24 router1 snmpd[359]: %DAEMON-3-SNMPD_TRAP_WARM_START: trap_generate_warm: SNMP trap: warm start Feb 22 20:35:07 router1 snmpd[359]: %DAEMON-6-SNMPD_THROTTLE_QUEUE_DRAINED: trap_throttle_timer_handler: cleared all throttled traps Feb 23 07:34:56 router1 snmpd[359]: %DAEMON-3-SNMPD_TRAP_WARM_START: trap_generate_warm: SNMP trap: warm start Feb 23 07:38:19 router1 snmpd[359]: %DAEMON-2-SNMPD_TRAP_COLD_START: trap_generate_cold: SNMP trap: cold start

48

Examples: Displaying a Log File

Chapter 1: Configuring System Log Messages

Getting Help About System Log Messages

System log message tag names begin with a prefix that indicates which JUNOS Software process, subroutine library, or service on a PIC generated the message. This section explains how to learn more about the messages with each prefix, both in this reference and while you are using the CLI. For a list of the prefixes for messages described in this reference, see System Log Messages on page 53. For information about displaying and interpreting messages, see the following sections:

Displaying and Interpreting System Log Message Descriptions on page 49 Examples: Displaying System Log Message Descriptions on page 51

Displaying and Interpreting System Log Message Descriptions

This reference lists the messages available at the time of its publication. To display the list of messages that applies to the version of the JUNOS Software that is running on a routing platform, enter JUNOS CLI operational mode and issue the following command:
user@host> help syslog ?

To display the list of available descriptions for tags whose names begin with a specific character string, substitute the string (in all capital letters) for the variable TAG-PREFIX (there is no space between the prefix and the question mark):
user@host> help syslog TAG-PREFIX?

To display the complete descriptions for tags whose name includes a regular expression, substitute the expression for the variable regex. The match is not case-sensitive.
user@host> help syslog regex

To display the complete description of a particular message, substitute its name for the variable TAG (in all capital letters):
user@host> help syslog TAG

Table 22 on page 49 describes the fields in a system log message description in this reference or in the CLI.
Table 22: Fields in System Log Message Descriptions
Field Name in Reference Field Name in CLI Name Description

The message tag in all capital letters.

Getting Help About System Log Messages

49

JUNOS 10.1 System Log Messages Reference

Table 22: Fields in System Log Message Descriptions (continued)

Field Name in Reference System Log Message Field Name in CLI Message Description

Text of the message written to the system log. In the log, a specific value is substituted for each variable that appears in italics in this reference or in angle brackets (<>) in the CLI. In this reference, the message text appears on the second line of the System Log Message field. The first line is the message tag (the same text as in the CLI Name field). The prefix on each tag identifies the message source and the rest of the tag indicates the specific event or error. System Log Messages on page 53 lists the prefixes for which this reference includes entries.

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. More detailed explanation of the message. Category to which the message belongs:

Description

Description

Type

Type

Error: The message

reports an error or failure condition that might require corrective action.

Event: The message

reports a condition or occurrence that does not generally require corrective action.
Severity Severity

Message severity level as described in Table 6 on page 10. (Optional) Possible cause for message generation. There can be more than one cause.

Cause

Cause

50

Displaying and Interpreting System Log Message Descriptions

Chapter 1: Configuring System Log Messages

Table 22: Fields in System Log Message Descriptions (continued)

Field Name in Reference Action Field Name in CLI Action Description

(Optional) Action you can perform to resolve the error or failure condition described in the message. If this field does not appear in an entry, either no action is required or the action is self-explanatory.

Examples: Displaying System Log Message Descriptions

Display the list of all currently available system log message descriptions:
user@host> help syslog ?
Possible completions: <syslog-tag> Syslog tag . . . . . . BOOTPD_ARG_ERR Command-line option was invalid BOOTPD_BAD_ID 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%)---

Display the list of all currently available system log message descriptions for tags that begin with the letters ACCT (there is no space between ACCT and the question mark, and some descriptions are shortened for legibility):
user@host> help syslog ACCT?
Possible completions: <syslog-tag> System log tag or regular expression ACCT_ACCOUNTING_FERROR Error occurred during file processing ACCT_ACCOUNTING_FOPEN_ERROR Open operation failed on file ACCT_ACCOUNTING_SMALL_FILE_SIZE Maximum file size is smaller than ... ACCT_BAD_RECORD_FORMAT Record format does not match accounting profile ACCT_CU_RTSLIB_ERROR Error occurred obtaining current class usage ... ACCT_FORK_ERR Could not create child process ACCT_FORK_LIMIT_EXCEEDED Could not create child process because of limit ACCT_GETHOSTNAME_ERROR gethostname function failed ACCT_MALLOC_FAILURE Memory allocation failed ACCT_UNDEFINED_COUNTER_NAME Filter profile used undefined counter name ACCT_XFER_FAILED Attempt to transfer file failed ACCT_XFER_POPEN_FAIL File transfer failed

Display the description of the UI_CMDLINE_READ_LINE message:

user@host> help syslog UI_CMDLINE_READ_LINE

Name:

UI_CMDLINE_READ_LINE

Examples: Displaying System Log Message Descriptions

51

JUNOS 10.1 System Log Messages Reference

Message: User '<users>', command '<input>' Help: User entered command at CLI prompt 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

52

Examples: Displaying System Log Message Descriptions

Part 2

System Log Messages

ACCT System Log Messages on page 57 ALARMD System Log Messages on page 61 ANCPD System Log Messages on page 63 ANTISPAM System Log Messages on page 65 APPIDD System Log Messages on page 67 APPPXY System Log Messages on page 69 ASP System Log Messages on page 71 AUDITD System Log Messages on page 101 AUTHD System Log Messages on page 105 AUTOCONFD System Log Messages on page 107 AUTOD System Log Messages on page 109 AV System Log Messages on page 111 BFDD System Log Messages on page 119 BOOTPD System Log Messages on page 121 CFMD System Log Messages on page 127 CHASSISD System Log Messages on page 131 CONNECTION System Log Messages on page 213 CONTENT System Log Messages on page 215 COSD System Log Messages on page 217 DCD System Log Messages on page 231 DFCD System Log Messages on page 237 DFWD System Log Messages on page 241 DHCPD System Log Messages on page 243 DYNAMIC System Log Messages on page 247 ESWD System Log Messages on page 253 EVENTD System Log Messages on page 261 FCD System Log Messages on page 269 FLOW System Log Messages on page 271 FPCLOGIN System Log Messages on page 273

System Log Messages

53

JUNOS 10.1 System Log Messages Reference

FSAD System Log Messages on page 275 FUD System Log Messages on page 285 FWAUTH System Log Messages on page 291 GPRSD System Log Messages on page 295 HNCACHED System Log Messages on page 297 ICCPD System Log Messages on page 299 IDP System Log Messages on page 301 JADE System Log Messages on page 307 JCS System Log Messages on page 309 JDIAMETERD System Log Messages on page 315 JSRPD System Log Messages on page 317 KMD System Log Messages on page 321 L2ALD System Log Messages on page 347 L2CPD System Log Messages on page 357 L2TPD System Log Messages on page 367 LACPD System Log Messages on page 399 LFMD System Log Messages on page 401 LIBESPTASK System Log Messages on page 403 LIBJNX System Log Messages on page 405 LIBJSNMP System Log Messages on page 413 LIBMSPRPC System Log Messages on page 419 LICENSE System Log Messages on page 423 LLDPD System Log Messages on page 427 LOGIN System Log Messages on page 429 LPDFD System Log Messages on page 435 LRMUX System Log Messages on page 437 MCSNOOPD System Log Messages on page 439 MIB2D System Log Messages on page 441 MPLS_OAM System Log Messages on page 449 NEXTHOP System Log Messages on page 453 NSD System Log Messages on page 455 NSTRACED System Log Messages on page 457 PFE System Log Messages on page 459 PFED System Log Messages on page 471 PGCPD System Log Messages on page 473 PING System Log Messages on page 475 PPMD System Log Messages on page 479

54

System Log Messages

Part 2: System Log Messages

PPPD System Log Messages on page 481 PROFILER System Log Messages on page 489 RDD System Log Messages on page 491 RMOPD System Log Messages on page 495 RPD System Log Messages on page 499 RT System Log Messages on page 567 RTLOG System Log Messages on page 589 RTLOGD System Log Messages on page 591 RTPERF System Log Messages on page 593 SAVAL System Log Messages on page 595 SDXD System Log Messages on page 597 SMTPD System Log Messages on page 601 SNMP System Log Messages on page 603 SNMPD System Log Messages on page 607 SPD System Log Messages on page 619 TASK System Log Messages on page 625 TFTPD System Log Messages on page 635 UI System Log Messages on page 641 UTMD System Log Messages on page 667 VCCPD System Log Messages on page 669 VRRPD System Log Messages on page 673 VSYSD System Log Messages on page 677 WEB System Log Messages on page 679 WEBFILTER System Log Messages on page 685

System Log Messages

55

JUNOS 10.1 System Log Messages Reference

56

System Log Messages

Chapter 2

ACCT System Log Messages

This chapter describes messages with the ACCT prefix. They are generated by the accounting statistics process, which collects and records interface, filter, and class usage statistics.

ACCT_ACCOUNTING_FERROR
System Log Message Description

Unexpected error error-code from file filename An error prevented the accounting statistics process from processing the indicated file. Error: An error occurred warning

Type Severity

ACCT_ACCOUNTING_FOPEN_ERROR
System Log Message Description Type Severity

Failed to open file filename: error-code The accounting statistics process could not open the indicated file. Error: An error occurred warning

ACCT_ACCOUNTING_SMALL_FILE_SIZE
System Log Message Description

File filename size (file-size) is smaller than record size (record-size) The size limit configured for the indicated file is smaller than the record to be written to it. Error: An error occurred warning

Type Severity

ACCT_ACCOUNTING_FERROR

57

JUNOS 10.1 System Log Messages Reference

ACCT_BAD_RECORD_FORMAT
System Log Message Description

Invalid statistics record: entry The number of columns in the indicated record does not match the number of columns in the accounting profile. Error: An error occurred warning

Type Severity

ACCT_CU_RTSLIB_ERROR
System Log Message Description Type Severity

Error getting class usage statistics for interface interface-name.unit-id: error-message The accounting statistics process could not obtain current class usage statistics. Error: An error occurred error

ACCT_FORK_ERR
System Log Message Description

Unable to fork: error-message The accounting statistics process could not create a child process for transferring files, for the indicated reason. Error: An error occurred error

Type Severity

ACCT_FORK_LIMIT_EXCEEDED
System Log Message Description

Unable to fork: too many child processes The accounting statistics process could not create a child process for transferring files, because adding another child would have made the number of children exceed the limit. Error: An error occurred error

Type Severity

58

ACCT_BAD_RECORD_FORMAT

Chapter 2: ACCT System Log Messages

ACCT_GETHOSTNAME_ERROR
System Log Message Description Type Severity

Error error-code trying to get hostname A call to the gethostname() function failed. Error: An error occurred error

ACCT_MALLOC_FAILURE
System Log Message Description Type Severity Cause Action

Memory allocation failed while reallocating filter profile interface list The accounting statistics process could not allocate memory from the heap. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

ACCT_UNDEFINED_COUNTER_NAME
System Log Message

Counter profile-name in accounting profile counter-name is not defined in a firewall using this filter profile The indicated filter profile referenced the indicated counter name, which is not defined in a firewall filter that uses the filter profile. Error: An error occurred warning Change the filter profile counter name to match the name defined in the firewall configuration.

Description

Type Severity Action

ACCT_XFER_FAILED
System Log Message Description Type

Error transferring filename An attempt to transfer the indicated file failed. Error: An error occurred

ACCT_GETHOSTNAME_ERROR

59

JUNOS 10.1 System Log Messages Reference

Severity

error

ACCT_XFER_POPEN_FAIL
System Log Message Description

Error error-code in invoking command command to transfer file filename A call to the popen() function failed when the accounting statistics process invoked the indicated command to transfer the indicated file. Error: An error occurred error

Type Severity

60

ACCT_XFER_FAILED

Chapter 3

ALARMD System Log Messages

This chapter describes messages with the ALARMD prefix. They are generated by the alarm process (alarmd).

ALARMD_WRITE_ERROR
System Log Message Description Type Severity

Alarmd error using ipc pipe: error-message The alarm process (alarmd) received an error while it was writing to a socket. Error: An error occurred error

ALARMD_WRITE_ERROR

61

JUNOS 10.1 System Log Messages Reference

62

ALARMD_WRITE_ERROR

Chapter 4

ANCPD System Log Messages

This chapter describes messages with the ANCPD prefix. They are generated by the Access Node Control Protocol process (ancpd), also known as Layer 2 control (l2c), which works with a special Internet Group Management Protocol (igmp) session to collect outgoing interface (oif) mapping events in a scalable manner.

ANCPD_COMMAND_OPTIONS
System Log Message Description

ancpd_cmd_opts called with option index arg argument The access node control protocol process (ancpd) command line options were not handled by junos_app_init. Event: This message reports an event, not an error info

Type Severity

ANCPD_COMMAND_OPTIONS

63

JUNOS 10.1 System Log Messages Reference

64

ANCPD_COMMAND_OPTIONS

Chapter 5

ANTISPAM System Log Messages

This chapter describes messages with the ANTISPAM prefix. They are generated by the antispam process, which decides what action should be performed when the device detects a message that it deems to be spam.

ANTISPAM_SPAM_DETECTED
System Log Message Description

AntiSpam: SPAM detected: source-name (source-address) action reason: reason The email is detected as a spam; the IP address of the source and its name will be logged together with the reason for it being categorized as spam Event: This message reports an event, not an error info The email is detected as a spam Verify the spam to make sure it is not a false positive

Type Severity Cause Action

ANTISPAM_SPAM_DETECTED_MT
System Log Message Description

AntiSpam: SPAM detected: source-name (source-address) action reason: reason The email is detected as a spam; the IP address of the source and its name will be logged together with the reason for it being categorized as spam Event: This message reports an event, not an error info The email is detected as a spam Verify the spam to make sure it is not a false positive

Type Severity Cause Action

ANTISPAM_SPAM_DETECTED

65

JUNOS 10.1 System Log Messages Reference

66

ANTISPAM_SPAM_DETECTED_MT

Chapter 6

APPIDD System Log Messages

This chapter describes messages with the APPIDD prefix. They are generated by the application identification process (appid), which is a passive application protocol identification library that implements a state machine for efficient pattern matching of regex-like application content signatures.

APPIDD_SCHEDULED_UPDATE_FAILED
System Log Message Description

Failed to update application packge. error: error-message The scheduled application-identification application package update failed to start. Device will try it again at the next scheduled time Error: An error occurred error

Type Severity

APPIDD_SCHEDULED_UPDATE_FAILED

67

JUNOS 10.1 System Log Messages Reference

68

APPIDD_SCHEDULED_UPDATE_FAILED

Chapter 7

APPPXY System Log Messages

This chapter describes messages with the APPPXY prefix. They are generated by the Application Proxy process (apppxyd) which performs all of the services of a proxy, but only for specific applications. The application proxy will only process packets that related to the applications it supports.

APPPXY_RESOURCE_OVERUSED
System Log Message

ApplicationProxy: Suspicious client source-address:source-port (->destination-address:destination-port) used percentage-value connections, which exceeded the maximum allowed maximum-value connections For ApplicationProxy, the amount of traffic from the specified source address exceeded the amount permitted from one source. The maximum amount of traffic from one source is a fixed percentage of the total amount of traffic. Event: This message reports an event, not an error error

Description

Type Severity

APPPXY_RESOURCE_OVERUSED_MT
System Log Message

ApplicationProxy: Suspicious client source-address:source-port (->destination-address:destination-port) used percentage-value connections, which exceeded the maximum allowed maximum-value connections For ApplicationProxy, the amount of traffic from the specified source address exceeded the amount permitted from one source. The maximum amount of traffic from one source is a fixed percentage of the total amount of traffic Event: This message reports an event, not an error error

Description

Type Severity

APPPXY_SESSION_ABORT
System Log Message

ApplicationProxy: session from source-address:source-port to destination-address:destination-port aborted due to error-message (code error-code)

APPPXY_RESOURCE_OVERUSED

69

JUNOS 10.1 System Log Messages Reference

Description Type Severity

Report application protocol (ftp/http/pop3/smtp/imap) session is aborted Event: This message reports an event, not an error warning

APPPXY_SESSION_ABORT_MT
System Log Message

ApplicationProxy: session from source-address:source-port to destination-address:destination-port aborted due to error-message (code error-code) Report application protocol (ftp/http/pop3/smtp/imap) session is aborted Event: This message reports an event, not an error warning

Description Type Severity

70

APPPXY_SESSION_ABORT

Chapter 8

ASP System Log Messages

This chapter describes messages with the ASP prefix. They are generated by services on the Adaptive Services PIC (AS PIC), such as stateful firewall, Network Address Translation (NAT), and intrusion detection service (IDS). For information about configuring system logging for services on the AS PIC, see the JUNOS Services Interfaces Configuration Guide. For information about the fields in messages with the ASP prefix, see Interpreting Messages Generated in Standard Format by Services on a PIC on page 43.

ASP_COS_RULE_MATCH
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name) application: application, source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type rule-set: rule-set-name, rule: rule-name, term: term-name A packet matched the indicated term in the indicated class-of-service (CoS) rule. If the rule belongs to a rule set, the name of the rule set is also displayed. 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). Event: This message reports an event, not an error info

Description

Type Severity

ASP_IDS_HOST_RATE
System Log Message Description

Host destination-address, event-type ... rate=rate events/sec The indicated event occurred at the indicated rate (events per second) for the indicated destination IP address. The rate exceeds the intrusion detection services (IDS) threshold configured with the '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. Event: This message reports an event, not an error error

Type Severity

ASP_COS_RULE_MATCH

71

JUNOS 10.1 System Log Messages Reference

ASP_IDS_HOST_RATE_APP
System Log Message Description

Host destination-address (application), event-type ... rate=rate events/sec The indicated event occurred at the indicated rate (events per second) for the indicated application at the indicated destination IP address. The rate exceeds the intrusion detection services (IDS) threshold set by the 'threshold' statement at the [edit services ids rule <rule-name> term <term-name> then logging] hierarchy level. The application is specified by the 'applications' or 'application-sets' statement at the [edit services ids rule <rule-name> term <term-name> from] hierarchy level. This message is logged every 60 seconds until the rate no longer exceeds the threshold. Event: This message reports an event, not an error error

Type Severity

ASP_IDS_INV_CLEAR_QUERY
System Log Message Description

CLEAR: Invalid query type received-value expecting expected-value Intrusion detection services (IDS) received a request to clear information from IDS tables. The request included the indicated type of query, which IDS cannot interpret. Error: An error occurred critical Contact your technical support representative.

Type Severity Action

ASP_IDS_INV_CLEAR_QUERY_VER
System Log Message Description

CLEAR: Invalid query version received-value expecting expected-value Intrusion detection services (IDS) received a request to clear information from IDS tables. The request's version number did not match the version number of requests that IDS can service. Error: An error occurred critical Contact your technical support representative.

Type Severity Action

ASP_IDS_INV_SHOW_QUERY
System Log Message

SHOW: Invalid query type received-value expecting expected-value

72

ASP_IDS_HOST_RATE_APP

Chapter 8: ASP System Log Messages

Description

Intrusion detection services (IDS) received a request to show information from IDS tables. The request included the indicated type of query, which IDS cannot interpret. Error: An error occurred critical Contact your technical support representative.

Type Severity Action

ASP_IDS_INV_SHOW_QUERY_VER
System Log Message Description

SHOW: Invalid query version received-value expecting expected-value Intrusion detection services (IDS) received a request to show information from IDS tables. The request's version number did not match the version number of requests that IDS can service. Error: An error occurred critical Contact your technical support representative.

Type Severity Action

ASP_IDS_LIMIT_FLOW_RATE_BY_DEST
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type 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 services (IDS) limit configured by the 'rate' statement at the [edit services ids rule <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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_IDS_LIMIT_FLOW_RATE_BY_PAIR
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type 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

Description

ASP_IDS_INV_SHOW_QUERY

73

JUNOS 10.1 System Log Messages Reference

detection services (IDS) limit configured by the 'rate' statement at the [edit services ids rule <rule-name> term <term-name> then session-limit by-pair] 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).
Type Severity

Event: This message reports an event, not an error notice

ASP_IDS_LIMIT_FLOW_RATE_BY_SRC
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type 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 services (IDS) limit configured by the 'rate' statement at the [edit services ids rule <rule-name> term <term-name> then session-limit by-source] 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_IDS_LIMIT_OPEN_FLOWS_BY_DEST
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics and did not create a new flow, because the number of open flows exceeded the intrusion detection services (IDS) limit configured by the 'maximum' statement at the [edit services ids rule <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). Event: This message reports an event, not an error notice

Description

Type Severity

74

ASP_IDS_LIMIT_FLOW_RATE_BY_PAIR

Chapter 8: ASP System Log Messages

ASP_IDS_LIMIT_OPEN_FLOWS_BY_PAIR
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics and did not create a new flow, because the number of open flows exceeded the intrusion detection services (IDS) limit configured by the 'maximum' statement at the [edit services ids rule <rule-name> term <term-name> then session-limit by-pair] 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_IDS_LIMIT_OPEN_FLOWS_BY_SRC
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics and did not create a new flow, because the number of open flows exceeded the intrusion detection services (IDS) limit configured by the 'maximum' statement at the [edit services ids rule <rule-name> term <term-name> then session-limit by-source] 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_IDS_LIMIT_PKT_RATE_BY_DEST
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics, because the number of packets per second (aggregated over all monitored flows) exceeded the intrusion detection services (IDS) limit configured by the 'packets' statement at the [edit services ids rule <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).

Description

ASP_IDS_LIMIT_OPEN_FLOWS_BY_PAIR

75

JUNOS 10.1 System Log Messages Reference

Type Severity

Event: This message reports an event, not an error notice

ASP_IDS_LIMIT_PKT_RATE_BY_PAIR
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics, because the number of packets per second (aggregated over all monitored flows) exceeded the intrusion detection services (IDS) limit configured by the 'packets' statement at the [edit services ids rule <rule-name> term <term-name> then session-limit by-pair] 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_IDS_LIMIT_PKT_RATE_BY_SRC
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics, because the number of packets per second (aggregated over all monitored flows) exceeded the intrusion detection services (IDS) limit configured by the 'packets' statement at the [edit services ids rule <rule-name> term <term-name> then session-limit by-source] 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_IDS_NO_MEM_SHOW_CMD
System Log Message Description

Not enough memory for show command Intrusion detection services (IDS) could not service a request to show information from IDS tables, because not enough memory was available. Error: An error occurred critical

Type Severity

76

ASP_IDS_LIMIT_PKT_RATE_BY_DEST

Chapter 8: ASP System Log Messages

ASP_IDS_NULL_CLEAR_QUERY
System Log Message Description

Failure: NULL query for CLEAR command. Intrusion detection services (IDS) invoked a query handler to service a request to clear information from IDS tables. The handler did not receive the request. Event: This message reports an event, not an error critical Contact your technical support representative.

Type Severity Action

ASP_IDS_NULL_SHOW_QUERY
System Log Message Description

Failure: NULL query for SHOW command. Intrusion detection services (IDS) invoked a query handler to service a request to show information from IDS tables. The handler did not receive the request. Event: This message reports an event, not an error critical Contact your technical support representative.

Type Severity Action

ASP_IDS_RULE_MATCH
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name) application: application, source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type rule-set: rule-set-name, rule: rule-name, term: term-name A packet matched the indicated term in the indicated intrusion detection services (IDS) rule. If the rule belongs to a rule set, the rule set name is also displayed. 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). Event: This message reports an event, not an error info

Description

Type Severity

ASP_IDS_SYN_COOKIE_OFF
System Log Message

Host destination-address, SYN-COOKIE protection deactivated

ASP_IDS_NULL_CLEAR_QUERY

77

JUNOS 10.1 System Log Messages Reference

Description

Intrusion detection services (IDS) deactivated SYN cookie protection for the indicated destination address. IDS deactivates this protection when it learns from the stateful firewall that the rate of certain events has returned to a level below the threshold set by the 'threshold' statement at the [edit services ids rule <rule-name> term <term-name> then syn-cookie] hierarchy level. The relevant events include the ones reported by the ASP_IDS_TCP_SYN_ATTACK, ASP_SFW_SYN_DEFENSE, and ASP_SFW_TCP_SCAN system log messages. Event: This message reports an event, not an error error

Type Severity

ASP_IDS_SYN_COOKIE_ON
System Log Message Description

Host destination-address, SYN-COOKIE protection activated Intrusion detection services (IDS) activated SYN cookie protection for the indicated destination address, because it learned from the stateful firewall that the rate of certain events exceeded the threshold set by the 'threshold' statement at the [edit services ids rule <rule-name> term <term-name> then syn-cookie] hierarchy level. The events include the ones reported by the ASP_IDS_TCP_SYN_ATTACK, ASP_SFW_SYN_DEFENSE, and ASP_SFW_TCP_SCAN system log messages. When SYN cookie protection is activated for a flow to a destination and the TCP handshake has not completed, the stateful firewall generates a SYN/ACK packet for each SYN packet directed to the destination. Event: This message reports an event, not an error error

Type Severity

ASP_IDS_TCP_SYN_ATTACK
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall received the packet with the indicated characteristics and determined that it was a duplicate Transmission Control Protocol (TCP) SYN packet (the SYN flag was set and a SYN packet was already received for the flow to the destination). The event was reported to intrusion detection services (IDS) and can cause IDS to activate SYN cookie protection. 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). Event: This message reports an event, not an error error

Description

Type Severity

78

ASP_IDS_SYN_COOKIE_OFF

Chapter 8: ASP System Log Messages

ASP_L2TP_MESSAGE_INCOMPLETE
System Log Message Description

IPC message lacked variable portion The Layer 2 Tunneling Protocol (L2TP) did not process an interprocess communication (IPC) message because the variable portion of the message was missing. Error: An error occurred error

Type Severity

ASP_L2TP_NO_MEM
System Log Message Description

Unable to allocate memory for L2TP flow for tunnel tunnel-id, session session-id The Layer 2 Tunneling Protocol (L2TP) could not allocate the memory it needed to create a flow for the indicated tunnel and session. Error: An error occurred error

Type Severity

ASP_L2TP_OBJ_CAC_FAIL
System Log Message

Unable to allocate object-cache memory for flow (unit unit-id, tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol (L2TP) could not allocate memory from an object cache for the flow defined by the indicated unit, tunnel, and session. Error: An error occurred error

Description

Type Severity

ASP_L2TP_STATS_BULK_QUERY_FAILED
System Log Message Description

Number of queries (num-queries) in statistics request exceeded limit (max-queries) The Layer 2 Tunneling Protocol (L2TP) did not process an interprocess communication (IPC) request for statistics because it included the indicated the number of queries, which exceeds the limit as indicated. Error: An error occurred error

Type Severity

ASP_L2TP_MESSAGE_INCOMPLETE

79

JUNOS 10.1 System Log Messages Reference

ASP_L2TP_STATS_VERSION_INVALID
System Log Message Description

Invalid version received-value on statistics request (expected expected-value) The Layer 2 Tunneling Protocol process (l2tpd) received a request for statistics with the indicated version, which is not the indicated, supported version. Error: An error occurred error

Type Severity

ASP_L2TP_TUN_GRP_ADD_FAIL_ALLOC
System Log Message Description

Unable to add tunnel group for service set service-set: could not allocate ID The Layer 2 Tunneling Protocol (L2TP) could not add a tunnel group for the indicated service set because it could not allocate an internal ID. Error: An error occurred error

Type Severity

ASP_L2TP_TUN_GRP_ADD_FAIL_EXISTS
System Log Message Description

Unable to add tunnel group group-id: it already exists The Layer 2 Tunneling Protocol (L2TP) could not add a tunnel group with the indicated ID because it already existed. Error: An error occurred error

Type Severity

ASP_L2TP_TUN_GRP_CHG_FAIL_ALLOC
System Log Message Description

Unable to change tunnel group for service set service-set: could not allocate ID The Layer 2 Tunneling Protocol (L2TP) could not change a tunnel group for the indicated service set because it could not allocate an internal ID. Error: An error occurred error

Type Severity

80

ASP_L2TP_STATS_VERSION_INVALID

Chapter 8: ASP System Log Messages

ASP_L2TP_TUN_GRP_CHG_FAIL_INVLD
System Log Message Description

Unable to change tunnel group group-id: ID is invalid The Layer 2 Tunneling Protocol (L2TP) could not change the tunnel group with the indicated internal ID, because the ID is invalid. Error: An error occurred error

Type Severity

ASP_L2TP_TUN_GRP_DEL_FAIL_INVLD
System Log Message Description

Unable to delete tunnel group group-id: ID is invalid The Layer 2 Tunneling Protocol (L2TP) could not delete the tunnel group with the indicated internal ID, because the ID is invalid. Error: An error occurred error

Type Severity

ASP_NAT_OUTOF_ADDRESSES
System Log Message Description

natpool nat-pool-name is out of addresses Network Address Translation (NAT) services could not allocate an address from the indicated NAT pool, because no addresses were available. Event: This message reports an event, not an error warning

Type Severity

ASP_NAT_OUTOF_PORTS
System Log Message Description

natpool nat-pool-name is out of ports Network Address Translation (NAT) services could not allocate a port from the indicated NAT pool, because no ports were available. Event: This message reports an event, not an error warning

Type Severity

ASP_L2TP_TUN_GRP_CHG_FAIL_INVLD

81

JUNOS 10.1 System Log Messages Reference

ASP_NAT_POOL_RELEASE
System Log Message Description

natpool release address:port[count] Network Address Translation (NAT) services made the indicated number of ports available in the pool for the indicated address, starting at the indicated port number. Event: This message reports an event, not an error info

Type Severity

ASP_NAT_RULE_MATCH
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name) application: application, source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type rule-set: rule-set-name, rule: rule-name, term: term-name A packet matched the indicated term in the indicated Network Address Translation (NAT) rule. If the rule belongs to a rule set, the rule set name is also displayed. 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). Event: This message reports an event, not an error info

Description

Type Severity

ASP_PGCP_IPC_MSG_WRITE_FAILED
System Log Message

Unable to write IPC message (type message-type, subtype message-subtype): status code status The Packet Gateway Control Protocol (PGCP) client on the MultiServices Physical Interface Card (PIC) could not write an interprocess communication (IPC) message to the end of its pipe. Error: An error occurred error

Description

Type Severity

ASP_PGCP_IPC_PIPE_WRITE_FAILED
System Log Message

Unable to write IPC message (type message-type, subtype message-subtype) to pipe: status code status

82

ASP_NAT_POOL_RELEASE

Chapter 8: ASP System Log Messages

Description

The Packet Gateway Control Protocol (PGCP) client on the MultiServices Physical Interface Card (PIC) could not write the contents of its interprocess communication (IPC) pipe to the socket layer. Error: An error occurred error

Type Severity

ASP_SFW_ALG_LEVEL_ADJUSTED
System Log Message

ALG sfw-application-name specified by stateful firewall or CoS rule was reduced to nat-application-name, because twice NAT does not support ALG application A twice Network Address Translation (NAT) rule is applied to the same source or destination addresses as a stateful firewall or class-of-service (CoS) rule that applies an application-level gateway (ALG) other than Internet Control Message Protocol (ICMP) or traceroute. 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 adaptive services software accomplished this internally by adjusting the indicated ALG value (which is not supported with twice NAT) to the indicated supported value. Event: This message reports an event, not an error warning Change the configuration so that twice-NAT rules (defined at the [edit services nat] hierarchy level) are not applied to the same source or destination addresses as rules defined at the [edit services stateful-firewall] or [edit services cos] hierarchy level that include ALGs other than the supported ones.

Description

Type Severity Action

ASP_SFW_ALG_PROMOTION_FAILED
System Log Message

ALG promotion failed. Stateful firewall application sfw-application-name conflicts with NAT application nat-application-name or conflicts with QoS application; request creation of discard flow A matching application-level gateway protocol (ALG) was found from both the indicated stateful firewall rule and either the indicated Network Address Translation (NAT) rule or a quality-of-service (QoS) rule, but the two ALGs were not at the same level. Event: This message reports an event, not an error critical Resolve the conflicting application-protocol matching conditions in the rules at the [edit services stateful-firewall] hierarchy level and either the [edit services cos] (for QoS rules) or [edit services nat] (for NAT rules) hierarchy level.

Description

Type Severity Action

ASP_PGCP_IPC_PIPE_WRITE_FAILED

83

JUNOS 10.1 System Log Messages Reference

ASP_SFW_APP_MSG_TOO_LONG
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Transmission Control Protocol (TCP) packet with the indicated characteristics, because the packet was so large that it exhausted memory resources. 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). Event: This message reports an event, not an error notice Delete active flows to forcibly free memory, or wait for the system to reclaim memory. Consider creating more service sets among which resources can be divided. Otherwise, contact your technical support representative.

Description

Type Severity Action

ASP_SFW_CHANGE_INACTIVITY_TIMER
System Log Message Description Type Severity

change global inactivity timer to value1 open timeout to value2 The global inactivity timer and the open timeout were set to the indicated values. Event: This message reports an event, not an error critical

ASP_SFW_CREATE_ACCEPT_FLOW
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name) application: application, source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type nat-information The packet with the indicated characteristics matched a stateful firewall rule that has the 'accept' action, and the stateful firewall created a flow. If the flow requires Network Address Translation (NAT) services, NAT information appears at the end of the message. 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). Event: This message reports an event, not an error info

Description

Type Severity

84

ASP_SFW_APP_MSG_TOO_LONG

Chapter 8: ASP System Log Messages

ASP_SFW_CREATE_DISCARD_FLOW
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name) application: application, source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The packet with the indicated characteristics matched a stateful firewall rule that has the 'discard' action, and the stateful firewall created a discard flow. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_CREATE_REJECT_FLOW
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name) application: application, source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The packet with the indicated characteristics matched a stateful firewall rule that has the 'reject' action, and the stateful firewall created a reject flow. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_FTP_ACTIVE_ACCEPT
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name) application: application, source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type nat-information When the stateful firewall receives PORT/EPRT commands in the control channel, it creates a flow in anticipation of an FTP data connection from client to server. The packet with the indicated characteristics matched such a flow. If the flow requires Network Address Translation (NAT) services, NAT information appears at the end of the message. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_CREATE_DISCARD_FLOW

85

JUNOS 10.1 System Log Messages Reference

ASP_SFW_FTP_PASSIVE_ACCEPT
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name) application: application, source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type nat-information When the stateful firewall receives PASV/EPSV commands in the control channel, it creates a flow in anticipation of an FTP data connection from server to client. The packet with the indicated characteristics matched such a flow. If the flow requires Network Address Translation (NAT) services, NAT information appears at the end of the message. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_ICMP_ERROR_DROP
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Internet Control Message Protocol (ICMP) error packet with the indicated characteristics, because the packet did not belong to an existing flow. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_ICMP_HEADER_LEN_ERROR
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Internet Control Message Protocol (ICMP) packet with the indicated characteristics, because the length field in the packet header was shorter than the minimum 8 bytes required for an ICMP packet. 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). Event: This message reports an event, not an error

Description

Type

86

ASP_SFW_FTP_PASSIVE_ACCEPT

Chapter 8: ASP System Log Messages

Severity

notice

ASP_SFW_ICMP_PACKET_ERROR_LENGTH
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Internet Control Message Protocol (ICMP) error packet with the indicated characteristics, because the packet contained fewer than 48 bytes of data, or more than 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_IP_FRAG_ASSEMBLY_TIMEOUT
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics and all related IP fragments it had previously received, because all fragments did not arrive within the four-second reassembly timeout period. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_IP_FRAG_OVERLAP
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics and all related IP fragments it had previously received, because the contents of two fragments overlapped. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_ICMP_HEADER_LEN_ERROR

87

JUNOS 10.1 System Log Messages Reference

ASP_SFW_IP_OPTION_DROP_PACKET
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics, because the packet contained nonconfigured IP option types. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_IP_PACKET_CHECKSUM_ERROR
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics, because the packet checksum was incorrect. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_IP_PACKET_DST_BAD
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics, because the packet destination address was either a multicast address or was in the range reserved for experimental use (248.0.0.0 through 255.255.255.254). 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). Event: This message reports an event, not an error notice

Description

Type Severity

88

ASP_SFW_IP_OPTION_DROP_PACKET

Chapter 8: ASP System Log Messages

ASP_SFW_IP_PACKET_FRAG_LEN_INV
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics and all related IP fragments it had previously received, because the length of a fragment was invalid. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_IP_PACKET_INCORRECT_LEN
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the IP packet with the indicated characteristics, because the packet length was invalid. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_IP_PACKET_LAND_ATTACK
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the IP packet with the indicated characteristics, because the source and destination address for the packet were the same (referred to as a land attack). 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_IP_PACKET_FRAG_LEN_INV

89

JUNOS 10.1 System Log Messages Reference

ASP_SFW_IP_PACKET_NOT_VERSION_4
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the IP packet with the indicated characteristics, because the packet version was not IP version 4 (IPv4). 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_IP_PACKET_PROTOCOL_ERROR
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the IP packet with the indicated characteristics, because the packet used an invalid protocol. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_IP_PACKET_SRC_BAD
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics, because the packet source address was one of the following: (1) a multicast address (2) a broadcast address (3) in the range 127.0.0.0 through 127.255.255.255 (4) in the range 248.0.0.0 through 255.255.255.254, which is reserved for experimental use. 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). Event: This message reports an event, not an error notice

Description

Type Severity

90

ASP_SFW_IP_PACKET_NOT_VERSION_4

Chapter 8: ASP System Log Messages

ASP_SFW_IP_PACKET_TOO_LONG
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the IP packet with the indicated characteristics, because the packet contained more than 64 kilobytes (KB) of data (referred to as a ping-of-death attack). 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_IP_PACKET_TOO_SHORT
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the IP packet with the indicated characteristics, because the packet did not contain the minimum amount of data required. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_IP_PACKET_TTL_ERROR
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the IP packet with the indicated characteristics, because the packet had a time-to-live (TTL) value of 0 (zero). 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_IP_PACKET_TOO_LONG

91

JUNOS 10.1 System Log Messages Reference

ASP_SFW_NEW_POLICY
System Log Message Description Type Severity

install new configuration A new stateful firewall policy was installed. Event: This message reports an event, not an error critical

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 The stateful firewall received the packet with the indicated characteristics, which was not an IP packet. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_NO_POLICY
System Log Message Description

source-address -> destination-addressNo policy The stateful firewall received packets with the indicated source and destination addresses. There was no matching policy for the traffic. Event: This message reports an event, not an error critical

Type Severity

ASP_SFW_NO_RULE_DROP
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics, because the packet did not match and stateful firewall rules. In this case, the default action is to discard the packet. 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).

Description

92

ASP_SFW_NEW_POLICY

Chapter 8: ASP System Log Messages

Type Severity

Event: This message reports an event, not an error notice

ASP_SFW_PING_DUPLICATED_SEQNO
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Internet Control Message Protocol (ICMP) echo request packet with the indicated characteristics, because packet's sequence number was the same as in a previous packet. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_PING_MISMATCHED_SEQNO
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Internet Control Message Protocol (ICMP) echo reply packet with the indicated characteristics, because the firewall had not previously received an echo request packet with the same sequence number. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_PING_OUTOF_SEQNO_CACHE
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Internet Control Message Protocol (ICMP) echo request packet with the indicated characteristics, because it had not received echo replies for an excessive number of previously received echo requests. 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).

Description

ASP_SFW_NO_RULE_DROP

93

JUNOS 10.1 System Log Messages Reference

Type Severity

Event: This message reports an event, not an error notice

ASP_SFW_POLICY_REJECT
System Log Message Description Type Severity

reject configuration because reason A newly installed stateful firewall policy was rejected for the indicated reason. Event: This message reports an event, not an error critical

ASP_SFW_RULE_ACCEPT
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name) application: application, source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type rule-set: rule-set-name, rule: rule-name, term: term-name The packet with the indicated characteristics matched the indicated term in the indicated stateful firewall rule, which has an 'accept' action. If the rule belongs to a rule set, the rule set name is also displayed. The stateful firewall accepted the flow to which the packet belongs. 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). Event: This message reports an event, not an error info

Description

Type Severity

ASP_SFW_RULE_DISCARD
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name) application: application, source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type rule-set: rule-set-name, rule: rule-name, term: term-name The packet with the indicated characteristics matched the indicated term in the indicated stateful firewall rule, which has a 'discard' action. If the rule belongs to a rule set, the rule set name is also displayed. The stateful firewall discarded the packet. 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). Event: This message reports an event, not an error notice

Description

Type Severity

94

ASP_SFW_PING_OUTOF_SEQNO_CACHE

Chapter 8: ASP System Log Messages

ASP_SFW_RULE_REJECT
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name) application: application, source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type rule-set: rule-set-name, rule: rule-name, term: term-name The packet with the indicated characteristics matched the indicated term in the indicated stateful firewall rule, which has a 'reject' action. If the rule belongs to a rule set, the rule set name is also displayed. If the packet used the User Datagram Protocol (UDP), the stateful firewall generated an 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 protocol (numerical identifier and name), application, source (logical interface name, IP address, and port number), and destination (IP address and port number). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_SYN_DEFENSE
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics, because the Transmission Control Protocol (TCP) handshake that is used to establish a session did not complete quickly enough. The time limit is set by the 'open-timeout' statement at the [edit interfaces <services-interface> services-options] hierarchy level or is four seconds by default. The event was reported to intrusion detection services (IDS) and can cause IDS to activate SYN cookie protection. 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). Event: This message reports an event, not an error notice Possible causes for the handshake failure include the following: (1) sequence numbers did not match in a SYN packet and a previous SYN packet (the second packet was not a retransmission) (2) sequence numbers did not match in a SYN/ACK packet and a previous SYN packet (3) either or both a SYN/ACK packet and an ACK packet did not arrive at the firewall within the time limit.

Description

Type Severity Cause

ASP_SFW_RULE_REJECT

95

JUNOS 10.1 System Log Messages Reference

ASP_SFW_TCP_BAD_SYN_COOKIE_RESP
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Transmission Control Protocol (TCP) ACK packet with the indicated characteristics, either because it is the first packet in a session, or because its sequence number did not match the sequence number in the SYN/ACK packet that the firewall previously generated for the session. The firewall generates SYN/ACK packets when SYN cookie protection is activated. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_TCP_FLAGS_ERROR
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Transmission Control Protocol (TCP) packet with the indicated characteristics, because the flags in the packet were set in one of the following combinations: (1) FIN and RST (2) SYN and one or more of FIN, RST, and URG. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_TCP_HEADER_LEN_ERROR
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Transmission Control Protocol (TCP) packet with the indicated characteristics, because the length field in the packet header was shorter than the minimum 20 bytes required for a TCP packet. 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).

Description

96

ASP_SFW_TCP_BAD_SYN_COOKIE_RESP

Chapter 8: ASP System Log Messages

Type Severity

Event: This message reports an event, not an error notice

ASP_SFW_TCP_NON_SYN_FIRST_PACKET
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Transmission Control Protocol (TCP) packet with the indicated characteristics, because it was the first packet in the TCP session but the SYN flag was not set. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_TCP_PORT_ZERO
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Transmission Control Protocol (TCP) packet with the indicated characteristics, because the source or destination port specified in the packet was zero (0). 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_TCP_RECONSTRUCT_DROP
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Transmission Control Protocol (TCP) packet with the indicated characteristics, because the session to which the packet belongs violated TCP standards. 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). Event: This message reports an event, not an error

Description

Type

ASP_SFW_TCP_HEADER_LEN_ERROR

97

JUNOS 10.1 System Log Messages Reference

Severity Cause

notice Possible causes include the following: (1) the amount of previously received but unacknowledged data exceeded the TCP window (2) there were sequence number errors (gaps in the sequence or packets with overlapping numbers).

ASP_SFW_TCP_SCAN
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall received a Transmission Control Protocol (TCP) RST packet from a server, indicating that the server rejected a connection attempt directed to the indicated destination address and port. 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 (logical interface name, IP address, and port number), and destination (IP address and port number). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_TCP_SEQNO_AND_FLAGS_ZERO
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Transmission Control Protocol (TCP) packet with the indicated characteristics, because the packet's sequence number was 0 (zero) and no flags were set. 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_TCP_SEQNO_ZERO_FLAGS_SET
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the Transmission Control Protocol (TCP) packet with the indicated characteristics, because the packet's sequence number was 0 (zero) and one or more of the FIN, PSH, and RST flags were set. The discarded packet

Description

98

ASP_SFW_TCP_RECONSTRUCT_DROP

Chapter 8: ASP System Log Messages

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 Severity

Event: This message reports an event, not an error notice

ASP_SFW_UDP_HEADER_LEN_ERROR
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type 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 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_UDP_PORT_ZERO
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the User Datagram Protocol (UDP) packet with the indicated characteristics, because the source or destination port specified in the packet was zero (0). 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). Event: This message reports an event, not an error notice

Description

Type Severity

ASP_SFW_UDP_SCAN
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall received an Internet Control Message Protocol (ICMP) error message from a server running at the indicated destination address and User Datagram Protocol (UDP) port. The error packet contained the indicated information

Description

ASP_SFW_TCP_SEQNO_ZERO_FLAGS_SET

99

JUNOS 10.1 System Log Messages Reference

about its protocol (numerical identifier and name), source (logical interface name, IP address, and port number), and destination (IP address and port number).
Type Severity

Event: This message reports an event, not an error notice

ASP_SFW_VERY_BAD_PACKET
System Log Message

syslog-prefix error-code: proto protocol-id (protocol-name), source-interface-nameseparatorsource-address:source-port -> destination-addressdestination-port, event-type The stateful firewall discarded the packet with the indicated characteristics, because the packet was malformed. 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). Event: This message reports an event, not an error critical

Description

Type Severity

ASP_SVC_SET_MAX_FLOWS_EXCEEDED
System Log Message

Number of flows (currently current-flows) exceeded configured limit (maximum-value) count times in previous 60 seconds A flow was not created for a service and service set, because the current number of flows for all supported services exceeded the limit configured with the 'max-flows' statement at the [edit services service-set <service-set-name>] hierarchy level. The message appears once per minute and reports the number of times in the previous 60 seconds that the system noted the excessive number of flows. Event: This message reports an event, not an error notice

Description

Type Severity

100

ASP_SFW_UDP_SCAN

Chapter 9

AUDITD System Log Messages

This chapter describes messages with the AUDITD prefix. They are generated by the audit process (auditd), which notifies the RADIUS accounting server of user activity on the routing platform, such as login, logout, and execution of command-line interface (CLI) commands.

AUDITD_RADIUS_AV_ERROR
System Log Message Description

Unable to create type record: error-message The audit process (auditd) experienced the indicated error when building RADIUS attribute-value (AV) pairs for the indicated type of accounting request, which can be a login or logout event, or a command issued in the CLI. Error: An error occurred error

Type Severity

AUDITD_RADIUS_OPEN_FAILED
System Log Message Description

function-name: unable to create RADIUS object handle (error-message) The audit process (auditd) could not create a RADIUS object handle, which it uses for various RADIUS operations. Error: An error occurred emergency

Type Severity

AUDITD_RADIUS_REQ_CREATE_FAILED
System Log Message Description

Unable to create RADIUS request: error-message The audit process (auditd) could not create a RADIUS accounting request for the indicated reason. Error: An error occurred

Type

AUDITD_RADIUS_AV_ERROR

101

JUNOS 10.1 System Log Messages Reference

Severity

error

AUDITD_RADIUS_REQ_DROPPED
System Log Message Description

Discarded Accounting-Request message; no RADIUS server responded The audit process (auditd) gathers information about system accounting events from other system processes and sends the information to RADIUS servers in an Accounting-Request message. The process repeatedly sent a message to all configured RADIUS servers without receiving a response, so it discarded the message. Error: An error occurred error The RADIUS accounting servers are not correctly configured or are unreachable, or the server applications are not responding.

Type Severity Cause

AUDITD_RADIUS_REQ_SEND_ERROR
System Log Message Description

function-name: error-message The audit process (auditd) experienced the indicated error when it requested accounting information from a RADIUS server. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

AUDITD_RADIUS_REQ_TIMED_OUT
System Log Message Description

Retransmitted request to RADIUS server radius-server The audit process (auditd) gathers information about system accounting events from other system processes and sends the information to RADIUS servers in an Accounting-Request message. After failing to receive a response from the indicated server, auditd waited for a timeout period and resent the message. Error: An error occurred error

Type Severity

102

AUDITD_RADIUS_REQ_CREATE_FAILED

Chapter 9: AUDITD System Log Messages

Cause

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.

AUDITD_RADIUS_SERVER_ADD_ERROR
System Log Message Description

Unable to add RADIUS server radius-server: error-message The audit process (auditd) read the RADIUS accounting server configuration, but could not add the indicated server to the internal structure used to track servers. Error: An error occurred error

Type Severity

AUDITD_SOCKET_FAILURE
System Log Message Description

function-name: unable to operation socket (error-message) The audit process (auditd) listens on a Transmission Control Protocol (TCP) socket for system accounting events reported by other processes on the routing platform. The indicated socket operation failed with the indicated error. Error: An error occurred emergency An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

AUDITD_RADIUS_REQ_TIMED_OUT

103

JUNOS 10.1 System Log Messages Reference

104

AUDITD_SOCKET_FAILURE

Chapter 10

AUTHD System Log Messages

This chapter describes messages with the AUTHD prefix. . They are generated by the generic authentication service process (authd) which is a security service that verifies an identity that is claimed by or for a system entity.

AUTHD_AUTH_CREATE_FAILED
System Log Message Description

Unable to allocate authentication handle: error-message The generic authentication service process (authd) could not allocate an authentication object for the indicated reason. Error: An error occurred error

Type Severity

AUTHD_RADIUS_GETHOSTNAME_FAILED
System Log Message Description

Unable to obtain hostname for outgoing RADIUS message: error-message The generic authentication service process (authd) could not obtain a hostname for an outgoing RADIUS message. Error: An error occurred error

Type Severity

AUTHD_SERVER_INIT_BIND_FAIL
System Log Message Description

Unable to bind to socket file-descriptor: error-message (errno error-code) The generic authentication service process (authd) could not bind the server to the address specified. Error: An error occurred error

Type Severity

AUTHD_AUTH_CREATE_FAILED

105

JUNOS 10.1 System Log Messages Reference

AUTHD_SERVER_INIT_LISTEN_FAIL
System Log Message Description

Unable to listen on socket file-descriptor: error-message (errno error-code) The generic authentication service process (authd) could not initialize listening on the server for the indicated socket. Error: An error occurred error

Type Severity

106

AUTHD_SERVER_INIT_LISTEN_FAIL

Chapter 11

AUTOCONFD System Log Messages

This chapter describes messages with the AUTOCONFD prefix. They are generated by the auto-configuration process (autoconfd).

AUTOCONFD_AUTHENTICATE_LICENSE
System Log Message Description

Authentication failed due to license error. Total license failures count The auto-configuration process (autoconfd) failed to authenticate the clients because there were no licenses or an insufficient number of licenses. The indicated number of license failures occurred and the clients were denied access and configuration. Error: An error occurred alert Add or update the license for authentication

Type Severity Action

AUTOCONFD_AUTHENTICATE_LICENSE

107

JUNOS 10.1 System Log Messages Reference

108

AUTOCONFD_AUTHENTICATE_LICENSE

Chapter 12

AUTOD System Log Messages

This chapter describes messages with the AUTOD prefix. They are generated by the autoinstallation process (autod), which controls the initialization of J Series Services Routers.

AUTOD_BIND_FAILURE
System Log Message Description

Unable to bind address to socket: error-message The autoinstallation process (autod) received the indicated error when it tried to bind a socket to an address. Error: An error occurred error Contact your technical support representative.

Type Severity Action

AUTOD_HOSTNAME_EXPANSION_FAILURE
System Log Message Description

Unable to expand compressed DNS domain name: error-message The autoinstallation process (autod) received the indicated error when it tried to expand a compressed Domain Name System (DNS) domain name. Error: An error occurred error Contact your technical support representative.

Type Severity Action

AUTOD_RECV_FAILURE
System Log Message Description

Unable to receive on socket: error-message The autoinstallation process (autod) received the indicated error when it tried to receive data on a socket.

AUTOD_BIND_FAILURE

109

JUNOS 10.1 System Log Messages Reference

Type Severity Action

Error: An error occurred error Contact your technical support representative.

AUTOD_RES_MKQUERY_FAILURE
System Log Message Description

DNS query failed: error-message The autoinstallation process (autod) received the indicated error when it made a Domain Name System (DNS) query. Error: An error occurred error Contact your technical support representative.

Type Severity Action

AUTOD_SEND_FAILURE
System Log Message Description

Unable to send on socket: error-message The autoinstallation process (autod) received the indicated error when it tried to send data on a socket. Error: An error occurred error Contact your technical support representative.

Type Severity Action

AUTOD_SOCKET_CREATE_FAILURE
System Log Message Description

Unable to create socket: error-message The autoinstallation process (autod) received the indicated error when it tried to create a socket. Error: An error occurred error Contact your technical support representative.

Type Severity Action

110

AUTOD_RECV_FAILURE

Chapter 13

AV System Log Messages

This chapter describes messages with the AV prefix. They are generated by the antivirus scanning process (avd).

AV_HUGE_FILE_DROPPED
System Log Message

AntiVirus: Content from source-address:source-port to destination-address:destination-port filename was dropped because maximum content size was exceeded. The antivirus scanner dropped the received traffic without scanning because the file size exceeded the maximum content limit. Event: This message reports an event, not an error warning

Description

Type Severity

AV_HUGE_FILE_DROPPED_MT
System Log Message

AntiVirus: Content from source-address:source-port to destination-address:destination-port filename was dropped because maximum content size was exceeded. The antivirus scanner dropped the received traffic without scanning because the file size exceeds the maximum content limit; see product Release Notes for the maximum content size supported on a device Event: This message reports an event, not an error warning

Description

Type Severity

AV_HUGE_FILE_NOT_SCANNED
System Log Message

AntiVirus: Content from source-address:source-port to destination-address:destination-port filename was not scanned because maximum content size was exceeded. The antivirus scanner passed the received traffic without scanning because the file size exceeded the maximum content limit.

Description

AV_HUGE_FILE_DROPPED

111

JUNOS 10.1 System Log Messages Reference

Type Severity

Event: This message reports an event, not an error warning

AV_HUGE_FILE_NOT_SCANNED_MT
System Log Message

AntiVirus: Content from source-address:source-port to destination-address:destination-port filename was not scanned because maximum content size was exceeded. The antivirus scanner passed the received traffic without scanning because the file size exceeds the maximum content limit; see product Release Notes for the maximum content size supported on a device Event: This message reports an event, not an error warning

Description

Type Severity

AV_MANY_MSGS_DROPPED
System Log Message

AntiVirus: Content from source-address:source-port to destination-address:destination-port filename dropped because the maximum number of concurrent messages was exceeded. The antivirus scanner dropped the received traffic because the maximum number of concurrent messages to scan was exceeded. Event: This message reports an event, not an error warning

Description

Type Severity

AV_MANY_MSGS_DROPPED_MT
System Log Message

AntiVirus: Content from source-address:source-port to destination-address:destination-port filename dropped because the maximum number of concurrent messages exceeded. The antivirus scanner dropped the received traffic because the maximum number of concurrent messages to scan is exceeded Event: This message reports an event, not an error warning

Description

Type Severity

AV_MANY_MSGS_NOT_SCANNED
System Log Message

AntiVirus: Content from source-address:source-port to destination-address:destination-port filename was not scanned because the maximum number of concurrent messages was exceeded.

112

AV_HUGE_FILE_NOT_SCANNED

Chapter 13: AV System Log Messages

Description

The antivirus scanner passed the received traffic without scanning because the maximum number of concurrent messages to scan was exceeded. Event: This message reports an event, not an error warning

Type Severity

AV_MANY_MSGS_NOT_SCANNED_MT
System Log Message

AntiVirus: Content from source-address:source-port to destination-address:destination-port filename was not scanned because the maximum number of concurrent messages are exceeded. The antivirus scanner passed the received traffic without scanning because the maximum number of concurrent messages to scan is exceeded Event: This message reports an event, not an error warning

Description

Type Severity

AV_PATTERN_GET_FAILED
System Log Message Description

AntiVirus: cannot retrieve pattern error-message file due to error-code (status-code). 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 Event: This message reports an event, not an error notice Unable to retrieve an antivirus pattern file from the server Contact Juniper Networks technical support

Type Severity Cause Action

AV_PATTERN_KEY_EXPIRED
System Log Message Description

AntiVirus: Attempt to time failed due to date, please renew to receive updates. The internal antivirus scanner was unsuccessful in downloading the antivirus pattern file, because the AV license key has been expired Event: This message reports an event, not an error notice Download the antivirus pattern file while antivirus license key has been expired

Type Severity Cause

AV_MANY_MSGS_NOT_SCANNED

113

JUNOS 10.1 System Log Messages Reference

Action

Renew the antivirus license key

AV_PATTERN_KL_CHECK_FAILED
System Log Message Description

AntiVirus: db file signature mismatch: error-message. The device is unable to use Kaspersky's pattern file. The error message provides information you need to give Juniper Networks technical support Event: This message reports an event, not an error critical The device is unable to use Kaspersky's pattern file Contact Juniper Networks technical suppor

Type Severity Cause Action

AV_PATTERN_TOO_BIG
System Log Message Description

AntiVirus: The pattern file specified in server is too large(file-size bytes) The pattern file size specified in the server initialization file (server.ini) exceeds the maximum prescribed limit Event: This message reports an event, not an error alert The pattern file size specified in the server initialization file exceeds the limit Contact Juniper Networks technical suppor

Type Severity Cause Action

AV_PATTERN_UPDATED
System Log Message Description

AntiVirus: Pattern file updated. Version: version; size: file-size bytes The internal antivirus scanner successfully updated the pattern file and may have changed the size of the file in the process Event: This message reports an event, not an error notice The internal antivirus scanner successfully updated the antivirus pattern file No recommended action

Type Severity Cause Action

114

AV_PATTERN_KEY_EXPIRED

Chapter 13: AV System Log Messages

AV_PATTERN_WRITE_FS_FAILED
System Log Message Description Type Severity Cause Action

AntiVirus: db file save failed: error-code The device is unable to save contents of an antivirus pattern file to the file system Event: This message reports an event, not an error critical The device is unable to save contents of an antivirus pattern file to the file syste Contact Juniper Networks technical support

AV_SCANNER_DROP_FILE
System Log Message

AntiVirus: Content from source-address:source-port to destination-address:destination-port filename was dropped because scan-engine error or constraint with code error-code for error-message. The antivirus scanner dropped the received traffic because of an internal error. Event: This message reports an event, not an error warning

Description Type Severity

AV_SCANNER_DROP_FILE_MT
System Log Message

AntiVirus: Content from source-address:source-port to destination-address:destination-port filename was dropped because scan-engine error or constraint with code error-code for error-message. The antivirus scanner dropped the received traffic because of an internal error Event: This message reports an event, not an error warning

Description Type Severity

AV_SCANNER_ERROR_SKIPPED
System Log Message

AntiVirus: Content from source-address:source-port to destination-address:destination-port filename was not scanned because scan-engine error or constraint with code error-code for error-message. The antivirus scanner passed the received traffic because of an internal error.

Description

AV_PATTERN_WRITE_FS_FAILED

115

JUNOS 10.1 System Log Messages Reference

Type Severity

Event: This message reports an event, not an error warning

AV_SCANNER_ERROR_SKIPPED_MT
System Log Message

AntiVirus: Content from source-address:source-port to destination-address:destination-port filename was not scanned because scan-engine error or constraint with code error-code for error-message. The antivirus scanner passed the received traffic because of an internal error Event: This message reports an event, not an error warning

Description Type Severity

AV_SCANNER_READY
System Log Message Description Type Severity Cause Action

AntiVirus:The scan engine is ready. The antivirus scan engine is ready to scan the traffic Event: This message reports an event, not an error notice The antivirus scan engine is ready No recommended action

AV_VIRUS_DETECTED
System Log Message

AntiVirus: Virus detected: from source-address:source-port to destination-address:destination-port filename file temporary-filename virus name The antivirus scanner detected a virus. See the log file to see the source and destination port and IP along with contaminated file and virus name. Event: This message reports an event, not an error warning

Description

Type Severity

AV_VIRUS_DETECTED_MT
System Log Message

AntiVirus: Virus detected: from source-address:source-port to destination-address:destination-port filename file temporary-filename virus name

116

AV_SCANNER_ERROR_SKIPPED

Chapter 13: AV System Log Messages

Description

The antivirus scanner has detected a virus; the log will show source and destination port and IP along with contaminated file and the virus name Event: This message reports an event, not an error warning

Type Severity

AV_VIRUS_DETECTED_MT

117

JUNOS 10.1 System Log Messages Reference

118

AV_VIRUS_DETECTED_MT

Chapter 14

BFDD System Log Messages

This chapter describes messages with the BFDD prefix. They are generated by the Bidirectional Forwarding Detection protocol process (bfdd), which detects failures in the bidirectional path between two routing platforms.

BFDD_MIRROR_ERROR
System Log Message Description

Unable to establish BFD mirror connection between Routing Engines: error-message The Bidirectional Forwarding Detection process (bfdd) could not establish the mirror connection (which supports nonstop routing) between the master and backup Routing Engines. Error: An error occurred warning The master and backup Routing Engines are running incompatible versions of the JUNOS Software. Update the JUNOS Software to compatible versions on the master and backup Routing Engines.

Type Severity Cause

Action

BFDD_MIRROR_VERSION_MISMATCH
System Log Message Description

Versions of BFD mirror software on Routing Engines are incompatible: error-message While trying to establish the mirror connection (which supports nonstop routing) between the master and backup Routing Engines, the Bidirectional Forwarding Detection process (bfdd) determined that the versions of JUNOS Software on the Routing Engines were incompatible. Error: An error occurred warning Update the JUNOS Software to compatible versions on the master and backup Routing Engines.

Type Severity Action

BFDD_MIRROR_ERROR

119

JUNOS 10.1 System Log Messages Reference

BFDD_READ_ERROR
System Log Message Description

Read error on pipe-type pipe: reason (error-message) The Bidirectional Forwarding Detection process (bfdd) could not read the message available on the indicated type of pipe. Error: An error occurred info Contact your technical support representative.

Type Severity Action

BFDD_TRAP_STATE_DOWN
System Log Message Description

local discriminator: session-id, new state: state The state changed to 'down' or 'admin down' for the indicated Bidirectional Forwarding Detection process (bfdd) session. Event: This message reports an event, not an error warning

Type Severity

BFDD_TRAP_STATE_UP
System Log Message Description

local discriminator: session-id, new state: state The state changed to 'up' for the indicated Bidirectional Forwarding Detection process (bfdd) session. Event: This message reports an event, not an error info

Type Severity

BFDD_WRITE_ERROR
System Log Message Description

function-name: write error on pipe-type pipe (error-message) The Bidirectional Forwarding Detection process (bfdd) could not write a message to the indicated type of pipe. Error: An error occurred error Contact your technical support representative.

Type Severity Action

120

BFDD_READ_ERROR

Chapter 15

BOOTPD System Log Messages

This chapter describes messages with the BOOTPD prefix. They are generated by the boot parameter process (tnp.bootpd), which provides the appropriate boot string to hardware components as they initialize.

BOOTPD_ARG_ERR
System Log Message Description

Ignoring unknown option -option The indicated option was provided on the 'tnp.bootpd' command line and is invalid. The boot parameter process (tnp.bootpd) initialized but ignored the invalid option. Error: An error occurred warning Remove the invalid option from the 'tnp.bootpd' command line.

Type Severity Action

BOOTPD_BAD_ID
System Log Message Description

Unexpected ID 0xassembly-id As each hardware component on the routing platform initializes, it requests a boot string from the boot parameter process (tnp.bootpd). The boot strings are defined in the configuration file tnp.bootpd. A request failed because it included the indicated assembly ID, for which there is no definition in the file. Event: This message reports an event, not an error notice

Type Severity

BOOTPD_BOOTSTRING
System Log Message Description

Boot string: boot-string 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.

BOOTPD_ARG_ERR

121

JUNOS 10.1 System Log Messages Reference

Type Severity

Event: This message reports an event, not an error info

BOOTPD_CONFIG_ERR
System Log Message Description

Problems with configuration file 'filename', using defaults The boot parameter process (tnp.bootpd) could not read the indicated configuration file, so it initialized using default settings defined at compile time. Error: An error occurred error Correct the configuration file.

Type Severity Action

BOOTPD_CONF_OPEN
System Log Message Description

Unable to open configuration file 'filename' The boot parameter process (tnp.bootpd) could not open the indicated configuration file, so it initialized using default settings defined at compile time. Event: This message reports an event, not an error notice Contact your technical support representative.

Type Severity Action

BOOTPD_DUP_PIC_SLOT
System Log Message Description

Duplicate default value defined for PIC pic-slot in FPC fpc-slot As each hardware component on the routing platform initializes, it requests a boot string from the boot parameter process (tnp.bootpd). The boot strings are defined in the configuration file for tnp.bootpd. There was more than one definition in the file for the indicated Physical Interface Card (PIC) slot in the indicated Flexible PIC Concentrator (FPC), so tnp.bootpd used the first definition it found. Event: This message reports an event, not an error notice Remove the extra definitions from the configuration file.

Type Severity Action

122

BOOTPD_BOOTSTRING

Chapter 15: BOOTPD System Log Messages

BOOTPD_DUP_REV
System Log Message Description

Duplicate revision: major-version.minor-version As each hardware component on the routing platform initializes, it requests a boot string from the boot parameter process (tnp.bootpd). The boot strings are defined in the configuration file for tnp.bootpd. There was more than one definition in the file for the indicated revision of a component, so tnp.bootpd used the first definition it found. Event: This message reports an event, not an error notice Remove the extra definitions from the configuration file.

Type Severity Action

BOOTPD_DUP_SLOT
System Log Message Description

Duplicate slot default: slot As each hardware component on the routing platform initializes, it requests a boot string from the boot parameter process (tnp.bootpd). The boot strings are defined in the configuration file for tnp.bootpd. There was more than one definition in the file for the indicated slot (combination of component assembly ID and revision), so tnp.bootpd used the first definition it found. Event: This message reports an event, not an error notice Remove the extra definitions from the configuration file.

Type Severity Action

BOOTPD_HWDB_ERROR
System Log Message Description

Operation in chassis hardware database failed: error-message 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. Error: An error occurred error

Type Severity

BOOTPD_MODEL_CHK
System Log Message

Unexpected ID 0xidentifier for model model

BOOTPD_DUP_REV

123

JUNOS 10.1 System Log Messages Reference

Description

As each hardware component on the routing platform initializes, it requests a boot string from the boot parameter process (tnp.bootpd). A request failed because it included the indicated assembly ID, which is inconsistent with the routing platform's model number. Error: An error occurred warning Contact your technical support representative.

Type Severity Action

BOOTPD_MODEL_ERR
System Log Message Description

Unsupported model model, assuming M40 defaults As each hardware component on the routing platform initializes, it requests a boot string from the boot parameter process (tnp.bootpd). The boot strings are defined in the configuration file for tnp.bootpd. A request included a model number for which there was no definition in the configuration file, so tnp.bootpd provided the boot string appropriate for an M40 router. Error: An error occurred warning Contact your technical support representative.

Type Severity Action

BOOTPD_NEW_CONF
System Log Message Description Type Severity

New configuration installed The boot parameter process (tnp.bootpd) loaded a new configuration file. Event: This message reports an event, not an error info

BOOTPD_NO_BOOTSTRING
System Log Message Description

No boot string found for type board-type major-version.minor-version command-type As each hardware component on the routing platform initializes, it requests a boot string from the boot parameter process (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. Error: An error occurred

Type

124

BOOTPD_MODEL_CHK

Chapter 15: BOOTPD System Log Messages

Severity Action

warning Contact your technical support representative.

BOOTPD_NO_CONFIG
System Log Message Description

No configuration file 'filename', using defaults The boot parameter process (tnp.bootpd) could not open the indicated configuration file, so it initialized using default settings defined at compile time. Event: This message reports an event, not an error notice

Type Severity

BOOTPD_PARSE_ERR
System Log Message Description

filename: return-value parse errors on SIGHUP There was an error in the configuration file for the boot parameter process (tnp.bootpd), so it initialized using default settings defined at compile time. Error: An error occurred error Correct the configuration file.

Type Severity Action

BOOTPD_REPARSE
System Log Message Description Type Severity

Reparsing configuration file 'filename' The boot parameter process (tnp.bootpd) reparsed the indicated configuration file. Event: This message reports an event, not an error info

BOOTPD_SELECT_ERR
System Log Message Description

select: error-message The boot parameter process (tnp.bootpd) issued the select() system call, which returned the indicated error message. Error: An error occurred

Type

BOOTPD_NO_BOOTSTRING

125

JUNOS 10.1 System Log Messages Reference

Severity Action

warning Contact your technical support representative.

BOOTPD_TIMEOUT
System Log Message Description

Timeout duration unreasonable The indicated timeout value was specified for the -t argument on the 'tnp.bootpd' command line, or no value was provided. The value was not acceptable, so the boot parameter process (tnp.bootpd) initialized using the default value of 30 seconds. Error: An error occurred warning Provide an acceptable value for the -t argument; acceptable values are '1' (second) and larger.

Type Severity Action

126

BOOTPD_SELECT_ERR

Chapter 16

CFMD System Log Messages

This chapter describes messages with the CFMD prefix. They are generated by the connectivity-fault management (CFM) process (cfmd), which supports Operation, Administration, and Maintenance (OAM) functions that are defined in the Institute of Electrical and Electronics Engineers (IEEE) 802.1ag standard for Ethernet interfaces.

CFMD_CCM_DEFECT_CROSS_CONNECT
System Log Message Description

CFM defect: error-message A connectivity-fault management (CFM) maintenance endpoint (MEP) received a continuity check message (CCM) that had an incorrect maintenance association (MA) ID or a maintenance domain (MD) level lower than that of the MEP, each of which indicates a cross-connect error. Event: This message reports an event, not an error error The configuration is invalid. Check whether the configured MD name, format, and level, or the MA name or format, is different from the remote endpoint.

Type Severity Cause Action

CFMD_CCM_DEFECT_ERROR
System Log Message Description

CFM defect: error-message A connectivity-fault management (CFM) maintenance endpoint (MEP) received a continuity check message (CCM) with an incorrect transmission interval or MEP ID, which indicates a configuration error. Event: This message reports an event, not an error error The configuration is invalid.

Type Severity Cause

CFMD_CCM_DEFECT_CROSS_CONNECT

127

JUNOS 10.1 System Log Messages Reference

Action

Verify that the configured continuity-check transmission interval does not differ from the remote endpoint, and that the configured MEP ID is valid.

CFMD_CCM_DEFECT_MAC_STATUS
System Log Message Description

CFM defect: error-message A connectivity-fault management (CFM) maintenance endpoint (MEP) received a continuity check message (CCM) that contained a 'Port Status' or 'Interface Status' type, length, value (TLV), which indicate a failed bridge port or aggregated port. Event: This message reports an event, not an error error

Type Severity

CFMD_CCM_DEFECT_NONE
System Log Message Description Type Severity

CFM defect: error-message No defect was detected. Event: This message reports an event, not an error error

CFMD_CCM_DEFECT_RDI
System Log Message Description

CFM defect: error-message A connectivity-fault management (CFM) maintenance endpoint (MEP) received a continuity check message (CCM) that had the 'Remote Defect Indication' (RDI) bit set, which indicates that not all configured MEPs are returning CCMs to the transmitting MEP. Event: This message reports an event, not an error error

Type Severity

CFMD_CCM_DEFECT_RMEP
System Log Message Description

CFM defect: error-message A connectivity-fault management (CFM) maintenance endpoint (MEP) did not receive three consecutive continuity check message (CCM)s from one of the other MEPs in its maintenance association (MA), which indicates a MEP failure or network failure. Event: This message reports an event, not an error

Type

128

CFMD_CCM_DEFECT_ERROR

Chapter 16: CFMD System Log Messages

Severity

error

CFMD_CCM_DEFECT_UNKNOWN
System Log Message Description Type Severity

CFM defect: error-message An unknown defect was detected. Event: This message reports an event, not an error error

CFMD_CCM_DEFECT_RMEP

129

JUNOS 10.1 System Log Messages Reference

130

CFMD_CCM_DEFECT_UNKNOWN

Chapter 17

CHASSISD System Log Messages

This chapter describes messages with the CHASSISD prefix. They are generated by the chassis process (chassisd), which controls hardware components on the routing platform.

CHASSISD_ANTICF_PIM_CHECK_FAILED
System Log Message Description

PIM pim-slot failed anti-counterfeit check The indicated Physical Interface Module (PIM) failed the anti-counterfeit check performed by the chassis process (chassisd). Error: An error occurred error

Type Severity

CHASSISD_ANTICF_RE_CHECK_FAILED
System Log Message Description

Routing Engine failed anti-counterfeit check The Routing Engine failed the anti-counterfeit check performed by the chassis process (chassisd). Error: An error occurred error

Type Severity

CHASSISD_ANTICF_RE_ROM_READ_FAIL
System Log Message Description

Unable to read serial number from anti-counterfeit device for Routing Engine The chassis process (chassisd) could not read the serial number recorded in the ROM of the anti-counterfeit device for the Routing Engine. Error: An error occurred error

Type Severity

CHASSISD_ANTICF_PIM_CHECK_FAILED

131

JUNOS 10.1 System Log Messages Reference

Action

Contact your technical support representative.

CHASSISD_ANTICF_RE_SHA_READ_FAIL
System Log Message Description

Unable to read SHA output from anti-counterfeit device for Routing Engine The chassis process (chassisd) could not read Secure Hash Algorithm (SHA) information from the anti-counterfeit device for the Routing Engine. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_ANTICF_ROM_READ_FAILED
System Log Message Description

Unable to read serial number from anti-counterfeit device for PIM pim-slot The chassis process (chassisd) could not read the serial number recorded in the ROM of the anti-counterfeit device for the indicated Physical Interface Module. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_ANTICF_SHA_READ_FAILED
System Log Message Description

Unable to read SHA output from anti-counterfeit device for PIM pim-slot The chassis process (chassisd) could not read Secure Hash Algorithm (SHA) information from the anti-counterfeit device for the indicated Physical Interface Module (PIM). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_ARGUMENT_ERROR
System Log Message

Unknown option option

132

CHASSISD_ANTICF_RE_ROM_READ_FAIL

Chapter 17: CHASSISD System Log Messages

Description

The indicated option, provided on the 'chassisd' command line, is invalid. The chassis process (chassisd) initialized but ignored the invalid option. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_BLOWERS_SPEED
System Log Message Description Type Severity

Fans and impellers are now running at normal speed The fans (and impellers, if applicable) were running at the normal speed. Event: This message reports an event, not an error notice

CHASSISD_BLOWERS_SPEED_FULL
System Log Message Description

Fans and impellers being set to full speed [reason] For the indicated reason, the chassis process (chassisd) increased the speed of fans (and impellers, if applicable) to the maximum. Event: This message reports an event, not an error notice

Type Severity

CHASSISD_BLOWERS_SPEED_MEDIUM
System Log Message Description

Fans and impellers being set to intermediate speed The chassis process (chassisd) increased the speed of fans (and impellers, if applicable) to the intermediate level because of a temperature increase in the chassis. Event: This message reports an event, not an error notice

Type Severity

CHASSISD_BUS_DEVICE_OPEN_FAILURE
System Log Message Description

Unable to open 'bus-type' bus device, error error-message (error-code) The chassis process (chassisd) could not open the indicated bus device for the indicated reason.

CHASSISD_ARGUMENT_ERROR

133

JUNOS 10.1 System Log Messages Reference

Type Severity Action

Error: An error occurred error Contact your technical support representative.

CHASSISD_CB_CLOCK_CHECKSUM
System Log Message Description

Clock module on M120 CB had configuration data checksum error The chassis process (chassisd) detected a checksum error for the clock module on an M120 Control Board (CB). Error: An error occurred error

Type Severity

CHASSISD_CB_MASTER_BP_IGNORED
System Log Message Description

Press of online/offline button ignored for master fru-name fru-slot The online/offline button for the indicated control board was pressed, but the chassis process (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). Event: This message reports an event, not an error error The control board was acting as master. Switch mastership to the other control board before taking the control board offline.

Type Severity Cause Action

CHASSISD_CB_READ
System Log Message Description Type Severity Action

Error reading midplane ID EEPROM, errno error-code The chassis process (chassisd) could not read the EEPROM on the midplane. Error: An error occurred error Contact your technical support representative.

134

CHASSISD_BUS_DEVICE_OPEN_FAILURE

Chapter 17: CHASSISD System Log Messages

CHASSISD_CB_RE_ONLINE_BP_IGNORED
System Log Message Description

Unable to take fru-name fru-slot offline because paired Routing Engine is online The online/offline button for the indicated control board was pressed, but the chassis process (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). Event: This message reports an event, not an error error The Routing Engine paired with the indicated control board is still online. Take the Routing Engine offline before taking the control board offline.

Type Severity Cause Action

CHASSISD_CFEB_POWER_FAILURE
System Log Message Description

function-name: unable to turn state power for CFEB cfeb-slot The chassis process (chassisd) could not turn on or turn off the power to the indicated Compact Forwarding Engine Board (CFEB). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_CLEAR_CONFIG_ERROR
System Log Message Description

function-name: status The chassis process (chassisd) encountered an error while trying to clear the state information associated with a copy of the management process (mgd) that it spawned to commit the rescue configuration. The commit operation succeeded or failed as indicated. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

CHASSISD_CB_RE_ONLINE_BP_IGNORED

135

JUNOS 10.1 System Log Messages Reference

CHASSISD_CLOCK_FAILURE
System Log Message Description

function-name: fru-name error-message The chassis process (chassisd) determined that the indicated clock source failed in the indicated way. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_CLOCK_NOTICE
System Log Message Description

fru-name: message The clock-synchronization status of the indicated component (field-replaceable unit, or FRU) changed as indicated. Event: This message reports an event, not an error notice

Type Severity

CHASSISD_CMB_READBACK_ERROR
System Log Message

Readback error from chassis management bus for fru-name fru-slot ([0xaddress, 0xoffset] -> 0xerror-code) The chassis process (chassisd) could not read back information from the Chassis Management Bus (CMB) about the indicated component (field-replaceable unit, or FRU). Error: An error occurred error The probable cause is hardware error. Contact your technical support representative.

Description

Type Severity Cause Action

CHASSISD_COMMAND_ACK_ERROR
System Log Message

Error occurred when fru-name fru-slot reported its online status: error-message (error code error-code)

136

CHASSISD_CLOCK_FAILURE

Chapter 17: CHASSISD System Log Messages

Description

The chassis process requested that the indicated component (field-replaceable unit, or 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. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_COMMAND_ACK_SFM_ERROR
System Log Message

function-name: SFM sfm-slot did not acknowledge FPC fpc-slot: error error-message (code error-code) The chassis process (chassisd) requires an acknowledgment from each Switching and Forwarding Module (SFM) before it registers a Flexible PIC Controller (FPC) as online. The acknowledgment message from the indicated SFM failed for the indicated FPC. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_CONCAT_MODE_ERROR
System Log Message Description

Cannot set no-concatenated mode for FPC fpc-slot PIC pic-slot The chassis process (chassisd) could not set channelized mode for the indicated SONET/SDH Physical Interface Card (PIC). Channelized mode is configured by including the no-concatenate statement at the [edit chassis fpc 'slot' pic 'slot'] hierarchy level. Event: This message reports an event, not an error warning

Type Severity

CHASSISD_CONFIG_ACCESS_ERROR
System Log Message Description

function-name: error-message The chassis process (chassisd) experienced the indicated problem while attempting to parse the configuration database. Error: An error occurred

Type

CHASSISD_COMMAND_ACK_ERROR

137

JUNOS 10.1 System Log Messages Reference

Severity Cause Action

error An internal software failure occurred. Contact your technical support representative.

CHASSISD_CONFIG_CHANGE_IFDEV_DEL
System Log Message Description

Deleting argument1 interface-typesdev-numberargument2 due to configuration change The chassis process (chassisd) deleted the indicated interface devices due to a change in the configuration. Event: This message reports an event, not an error warning

Type Severity

CHASSISD_CONFIG_INIT_ERROR
System Log Message Description

Unable to parse configuration; using defaults The chassis process (chassisd) could not parse the configuration, and used default values while initializing. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_CONFIG_WARNING
System Log Message Description

function-name: warning-message, FPC fpc-slot PIC pic-slot The configuration that was specified for the indicated Physical Interface Card (PIC) is invalid for that type of PIC. Event: This message reports an event, not an error warning

Type Severity

CHASSISD_DEVICE_OPEN_ERROR
System Log Message Description

Unable to open device-name device file (errno error-code) The chassis process (chassisd) could not open the device file for the indicated device.

138

CHASSISD_CONFIG_ACCESS_ERROR

Chapter 17: CHASSISD System Log Messages

Type Severity Action

Error: An error occurred error Contact your technical support representative.

CHASSISD_EXEC_ERROR
System Log Message Description

function-name: error-message While trying to commit the rescue configuration, the chassis process (chassisd) encountered an error. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

CHASSISD_EXISTS
System Log Message Description

chassisd already running; exiting The chassis process (chassisd) exited because it discovered that another chassisd process was already running. Event: This message reports an event, not an error error

Type Severity

CHASSISD_EXISTS_TERM_OTHER
System Log Message Description

Killing existing chassisd and exiting The chassis process (chassisd) discovered that another chassisd process was already running. It terminated the other process and exited. Event: This message reports an event, not an error error

Type Severity

CHASSISD_FAN_FAILURE
System Log Message

fru-name in slot fru-slot failed

CHASSISD_DEVICE_OPEN_ERROR

139

JUNOS 10.1 System Log Messages Reference

Description

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. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FASIC_CONFIG_COMPLETE
System Log Message Description

Fchip: configuration already completed The chassis process (chassisd) detected an attempt to configure an F chip on a Control Board (CB) when configuration was already complete. Error: An error occurred error

Type Severity

CHASSISD_FASIC_FTOKEN_ERROR
System Log Message

Fchip (CB control-board-slot, ID fchip-id): ftoken overflow/underflow set (data) at address The chassis process (chassisd) detected an underflow or overflow error on the indicated F chip on the indicated Control Board (CB). Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_FASIC_FTOKEN_INIT_ERROR
System Log Message

Fchip (CB control-board-slot, ID fchip-id): f8chip_ftoken_init() stuck in ftoken loop, addr=address, data=data The chassis process (chassisd) encountered an error while initializing memory at the indicated address for the indicated F chip on the indicated Control Board (CB). Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

140

CHASSISD_FAN_FAILURE

Chapter 17: CHASSISD System Log Messages

CHASSISD_FASIC_HSL_CONFIG_ERROR
System Log Message Description

Fchip (CB control-board-slot, ID fchip-id): HSL configuration failed (error error-message) The chassis process (chassisd) could not configure high speed links (HSL) for the indicated F chip on the indicated Control Board (CB). Error: An error occurred error

Type Severity

CHASSISD_FASIC_HSL_LINK_ERROR
System Log Message Description

Fchip (CB control-board-slot, ID fchip-id): link link-id failed because of error-message The chassis process (chassisd) detected an error for the indicated high speed link (HSL) for the indicated F chip on the indicated Control Board (CB). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FASIC_INIT_ERROR
System Log Message Description

Fchips were not configured yet The chassis process (chassisd) detected that F chips were not yet initialized on the Control Board (CB). Error: An error occurred error

Type Severity

CHASSISD_FASIC_INPUT_DROP
System Log Message

Fchip (CB control-board-slot, ID fchip-id): dropped drop-rate cells per second coming from Packet Forwarding Engine pfe on FPC fpc-slot 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 that was received from the indicated Packet Forwarding Engine on the indicated Flexible PIC Concentrator (FPC), it dropped the indicated number of cells per second. Error: An error occurred

Description

Type

CHASSISD_FASIC_HSL_CONFIG_ERROR

141

JUNOS 10.1 System Log Messages Reference

Severity Action

error Contact your technical support representative.

CHASSISD_FASIC_OUTPUT_DROP
System Log Message

Fchip (CB control-board-slot, ID fchip-id): dropped drop-rate cells per second destined for Packet Forwarding Engine pfe on FPC fpc-slot 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 Port Concentrator (FPC) for outgoing transmission, it dropped the indicated number of cells per second. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_FASIC_PIO_READ_ERROR
System Log Message

Fchip (CB control-board-slot, ID fchip-id): read error in function-name() for link#link-id at address address in register register The indicated routine failed with a read error at the indicated address and register for the indicated F chip and link on the indicated Control Board (CB). Error: An error occurred error

Description

Type Severity

CHASSISD_FASIC_PIO_WRITE_ERROR
System Log Message

Fchip (CB control-board-slot, ID fchip-id): write error in function-name() for link#link-id at address address in register register The indicated routine failed with a write error at the indicated address and register for the indicated F chip and link on the indicated Control Board (CB). Error: An error occurred error

Description

Type Severity

CHASSISD_FASIC_PLL_ERROR
System Log Message

Fchip (CB control-board-slot, ID fchip-id): unable to lock PLL

142

CHASSISD_FASIC_INPUT_DROP

Chapter 17: CHASSISD System Log Messages

Description

The chassis process (chassisd) could not lock a phased-lock loop (PLL) for the indicated F chip on the indicated Control Board (CB). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FASIC_RESET_ERROR
System Log Message Description

Fchip (CB control-board-slot, ID fchip-id): reset failed The chassis process (chassisd) could not reset the indicated F chip on the indicated Control Board (CB). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FASIC_SRAM_ERROR
System Log Message Description

Fchip (CB control-board-slot, ID fchip-id): SRAM fuse did not initialize The chassis process (chassisd) detected that static RAM (SRAM) did not initialize properly for the indicated F chip on the indicated Control Board (CB). Error: An error occurred error

Type Severity

CHASSISD_FASIC_VERSION_ERROR
System Log Message

Fchip (CB control-board-slot, ID fchip-id): part number part-number and version version were invalid The indicated part number and version detected for the indicated F chip on the indicated Control Board (CB) were not valid values. Error: An error occurred error

Description

Type Severity

CHASSISD_FASIC_PLL_ERROR

143

JUNOS 10.1 System Log Messages Reference

CHASSISD_FCHIP_CONFIG_COMPLETE
System Log Message Description

Fchip: configuration already completed The chassis process (chassisd) detected an attempt to configure an F chip when configuration was already complete. Error: An error occurred error

Type Severity

CHASSISD_FCHIP_CONFIG_MD_ERROR
System Log Message

Fchip fchip-id: invalid number of Md chips (count) for Packet Forwarding Engine pfe on FPC fpc-slot The chassis process (chassisd) detected an invalid number of Md chips for the indicated F chip, Packet Forwarding Engine and Flexible PIC Concentrator (FPC). Error: An error occurred error

Description

Type Severity

CHASSISD_FCHIP_CONFIG_RATE_ERROR
System Log Message Description

Fchip fchip-id: unable to set rate limit on port port The chassis process (chassisd) could not set the rate limit for the indicated F chip and port. Error: An error occurred error

Type Severity

CHASSISD_FCHIP_CONFIG_READ_ERROR
System Log Message Description

Fchip fchip-id: unable to read configuration register The chassis process (chassisd) could not read a configuration register on the indicated F chip. Error: An error occurred error

Type Severity

144

CHASSISD_FCHIP_CONFIG_COMPLETE

Chapter 17: CHASSISD System Log Messages

CHASSISD_FCHIP_FTOKEN_ERROR
System Log Message Description

Fchip fchip-id: Ftoken overflow/underflow set (data) at address The chassis process (chassisd) detected an underflow or overflow error on the indicated F chip. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FCHIP_FTOKEN_INIT_ERROR
System Log Message Description

Fchip fchip-id: fchip_ftoken_init() stuck in ftoken loop, addr=address, data=data The chassis process (chassisd) encountered an error while initializing memory at the indicated address for the indicated F chip. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FCHIP_HSR_ERROR
System Log Message Description

Fchip high-speed receiver (HSR) error: error-message The chassis process (chassisd) detected an error in the high-speed receiver (HSR) subsystem for the F chip with the indicated characteristics. Error: An error occurred error

Type Severity

CHASSISD_FCHIP_HSR_INIT_ERROR
System Log Message Description

HSR: No vectors supplied The chassis process (chassisd) could not initialize the high-speed receiver (HSR) subsystem for an F chip. Error: An error occurred

Type

CHASSISD_FCHIP_FTOKEN_ERROR

145

JUNOS 10.1 System Log Messages Reference

Severity

error

CHASSISD_FCHIP_HSR_INIT_LINK_ERR
System Log Message Description

Fchip fchip-id: unable to initialize HSR link link-id The chassis process (chassisd) could not initialize the indicated high-speed receiver (HSR) link for the indicated F chip. Error: An error occurred error

Type Severity

CHASSISD_FCHIP_HSR_RESET_ERROR
System Log Message Description

Fchip fchip-id: hsr_reset error in fchip_init() on link link-id A high-speed receiver (HSR) reset error occurred during initialization of the indicated F chip and link. Error: An error occurred error

Type Severity

CHASSISD_FCHIP_HST_ERROR
System Log Message Description

Fchip high-speed transmitter (HST) error: error-message The chassis process (chassisd) detected an error in the high-speed transmitter (HST) subsystem for the F chip with the indicated characteristics. Error: An error occurred error

Type Severity

CHASSISD_FCHIP_HST_INIT_ERROR
System Log Message Description

HST: No vectors supplied The chassis process (chassisd) could not initialize the high-speed transmitter (HST) subsystem for an F chip. Error: An error occurred error

Type Severity

146

CHASSISD_FCHIP_HSR_INIT_ERROR

Chapter 17: CHASSISD System Log Messages

CHASSISD_FCHIP_HST_INIT_LINK_ERR
System Log Message Description

Fchip fchip-id: unable to initialize HST link link-id The chassis process (chassisd) could not initialize the indicated high-speed transmitter (HST) link for the indicated F chip. Error: An error occurred error

Type Severity

CHASSISD_FCHIP_HST_RESET_ERROR
System Log Message Description

Fchip fchip-id: hst_reset error in fchip_init() on link link-id A high-speed transmitter (HST) reset error occurred during initialization of the indicated F chip and link. Error: An error occurred error

Type Severity

CHASSISD_FCHIP_INIT_ERROR
System Log Message Description Type Severity

Fchips were not configured yet The chassis process (chassisd) detected that F chips were not yet initialized. Error: An error occurred error

CHASSISD_FCHIP_LINK_ERROR
System Log Message Description

SIBsib-slot_F0: link-type link link-id was bad The chassis process (chassisd) detected an error for the indicated high-speed receiver (HSR) or high-speed transmitter (HST) link for an F chip on the indicated Switch Interface Board (SIB). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FCHIP_HST_INIT_LINK_ERR

147

JUNOS 10.1 System Log Messages Reference

CHASSISD_FCHIP_MONITOR_ERROR
System Log Message Description

F chip module was invalid The chassis process (chassisd) detected an invalid F-chip module while enabling or disabling the monitoring of F-chip functional blocks. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FCHIP_PIO_READ_ERROR
System Log Message

Fchip fchip-id: read error in function-name() for link#link-id, at address address in register register The indicated routine failed with a read error at the indicated address and register for the indicated F chip and link. Error: An error occurred error

Description

Type Severity

CHASSISD_FCHIP_PIO_WRITE_ERROR
System Log Message

Fchip fchip-id: write error in function-name() for link#link-id, at address address in register register The indicated routine failed with a write error at the indicated address and register for the indicated F chip and link. Error: An error occurred error

Description

Type Severity

CHASSISD_FCHIP_POLL_ERROR
System Log Message Description

Fchip fchip-id: link-type link-id poll returned error error-code An error with the indicated error number occurred during polling of the indicated high-speed receiver (HSR) or high-speed transmitter (HST) link for the indicated F chip. Error: An error occurred

Type

148

CHASSISD_FCHIP_MONITOR_ERROR

Chapter 17: CHASSISD System Log Messages

Severity Action

error Contact your technical support representative.

CHASSISD_FCHIP_RATE_ERROR
System Log Message Description

Fchip fchip-id: per-port rate limit was not enabled The chassis process (chassisd) detected that per-port rate limiting was not enabled when it attempted to set the rate limit on an individual port for the indicated F chip. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FCHIP_SIB_NOT_STARTED
System Log Message Description

Unable to start fru-name fru-slot because F chips were not initialized The indicated Switch Interface Board (SIB) did not start because the F chips on it were not initialized. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FCHIP_VERSION_ERROR
System Log Message Description

F chip fchip-id: part number (part-number) and version (version) were invalid The indicated part number and version detected for the indicated F chip were not valid values. Error: An error occurred error

Type Severity

CHASSISD_FEB_REVERSION
System Log Message Description

Reversion from FEB fru-slot to FEB slot The chassis daemon (chassisd) reverted to the indicated FEB from the specified FEB.

CHASSISD_FCHIP_POLL_ERROR

149

JUNOS 10.1 System Log Messages Reference

Type Severity

Event: This message reports an event, not an error error

CHASSISD_FEB_SWITCHOVER
System Log Message Description Type Severity

Switchover from FEB fru-slot to FEB slot The chassis daemon (chassisd) switched to the indicated FEB from the specified FEB. Event: This message reports an event, not an error error

CHASSISD_FHSR_READ_REG_ERROR
System Log Message Description

Fchip: fhsr_read() failed at address address The high-speed receiver (HSR) read routine failed at the indicated address on an F-chip register. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FHSR_WRITE_REG_ERROR
System Log Message Description

Fchip: fhsr_write() of value value failed at address address The high-speed receiver (HSR) write routine could not record the indicated value at the indicated address on an F-chip register. Error: An error occurred error

Type Severity

CHASSISD_FHST_READ_REG_ERROR
System Log Message Description

Fchip: fhst_read() failed at address address The high-speed transmitter (HST) read routine failed at the indicated address on an F-chip register. Error: An error occurred error

Type Severity

150

CHASSISD_FEB_REVERSION

Chapter 17: CHASSISD System Log Messages

Action

Contact your technical support representative.

CHASSISD_FHST_WRITE_REG_ERROR
System Log Message Description

Fchip: fhst_write() of value value failed at address address The high-speed transmitter (HST) write routine could not record the indicated value at the indicated address on an F-chip register. Error: An error occurred error

Type Severity

CHASSISD_FILE_OPEN
System Log Message Description

File open: filename, error: error-code -- error-message The chassis process (chassisd) could not open the indicated file for the indicated reason. Error: An error occurred critical

Type Severity

CHASSISD_FILE_STAT
System Log Message Description

File stat: filename, error: error-code -- error-message The chassis process (chassisd) could not open the indicated file because it could not obtain its status. Error: An error occurred error

Type Severity

CHASSISD_FM_BAD_STATE
System Log Message Description

function-name: unexpected state statetype for SIB#sib-slot The indicated function failed because it encountered the indicated type of unexpected internal state with respect to the indicated Switch Interface Board (SIB). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FHST_READ_REG_ERROR

151

JUNOS 10.1 System Log Messages Reference

CHASSISD_FM_ERROR
System Log Message

function-name: error-message (SIB#sib-slot, Packet Forwarding Engine pfe on FPC fpc-slot) During execution of the indicated fabric management routine, the indicated error occurred between the indicated Switch Interface Board (SIB) and the indicated Packet Forwarding Engine on the indicated Flexible PIC Concentrator (FPC). Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_FM_ERROR_CLOS_F13_HSR
System Log Message

FM: error-message errors occurred on link from F2-f2-sib_SFfrom-fchip_s-port to F13SIBto-sfc-sib_SF3_to-fchip_d-port on plane sib-plane 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). 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. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_FM_ERROR_CLOS_F13_HST
System Log Message

FM: error-message errors occurred on link from F13SIBfrom-sfc-sib_SF1_from-fchip_s-port to F2-f2-sib_SFto-fchip_d-port on plane sib-plane 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). The chassis process (chassisd) on the SFC routing node detected an error in the transmit electrical path between the indicated port on the indicated F13SIB and F2SIB on the indicated plane. Error: An error occurred

Description

Type

152

CHASSISD_FM_ERROR

Chapter 17: CHASSISD System Log Messages

Severity Action

error Contact your technical support representative.

CHASSISD_FM_ERROR_CLOS_F2_HSR
System Log Message

FM: error-message errors occurred on link from F13SIBfrom-sfc-sib_SF1_from-fchip_s-port to f2-sib_SFto-fchip_d-port on plane sib-plane 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). 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. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_FM_ERROR_CLOS_F2_HST
System Log Message

FM: error-message errors occurred on link from f2-sib_SFfrom-fchip_s-port to F13SIBto-sfc-sib_SF1_to-fchip_d-port on plane sib-plane 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). The chassis process (chassisd) on the SFC routing node detected an error in the transmit electrical path between the indicated port on the indicated F2SIB and F13SIB on the indicated plane. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_FM_ERROR_F13_FB_HSR_TXP
System Log Message

error-message errors on LCClcc_FPCfpc-slot_pfe link via ST_SIB_Lfrom-lcc-sib_FBfiber-bundle to F13SIBto-sfc-sib 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). The chassis process (chassisd) on the routing node that houses the indicated

Description

CHASSISD_FM_ERROR_CLOS_F13_HST

153

JUNOS 10.1 System Log Messages Reference

F13SIB detected an error in the electrical path between the indicated ports on the F13SIB and the indicated ST-SIB-L on the indicated LCC.
Type Severity Action

Error: An error occurred error Contact your technical support representative.

CHASSISD_FM_ERROR_F13_FB_RX_VC
System Log Message

error-message on F13SIBfrom-sfc-sib_FBfiber-bundle VCSEL vcsel Channel vcsel-channel connected from LCC lcc SIB_L to-lcc-sib 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). The chassis process (chassisd) on the routing node that houses the indicated F13SIB detected the indicated error as packets that were traveling in the in the optical media from the indicated ST-SIB-L on the indicated LCC. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_FM_ERROR_F13_FB_TXP
System Log Message Description

F13SIBsib-slot_FB_fiber-bundle LCC lcc ST_SIB_Lto-lcc-sib is error-message In a Tx-Plus routing matrix, the fiber-optic cable between each Switch Interface Board in a T1600 routing node (called a ST-SIB-L) must connect to a specific SIB port on the TX-Plus Matrix platform (called a F13SIB). The cable connected at the indicated F13SIB had the indicated error. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FM_ERROR_F13_FB_TX_VC
System Log Message

error-message on F13SIBfrom-sfc-sib_FBfiber-bundle VCSEL vcsel Channel vcsel-channel connected to LCC lcc SIB_L to-lcc-sib

154

CHASSISD_FM_ERROR_F13_FB_HSR_TXP

Chapter 17: CHASSISD System Log Messages

Description

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). The chassis process (chassisd) on the routing node that houses the indicated F13SIB detected the indicated error as packets that were traveling in the indicated direction were translated between electrical and optical media. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FM_ERROR_F13_VC_PWR
System Log Message

FM: High power difference at F13SIBfrom-sfc-sib_FBfiber-bundle VCSEL vcsel Channel vcsel-channel connected to LCC lcc SIB_Lsib-slot 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). 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. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_FM_ERROR_SIB_L_FB_HSR
System Log Message

FM: HSR error occurred on link from SIB-S port F(s-row,s-port) to SIB-L#sib-slot port F(l-row,l-port) In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the T640 routing nodes (called SIB-Ls) and the SIBs in the TX Matrix platform (called SIB-Ss). The chassis process (chassisd) on the routing node that houses the indicated SIB-L detected an error in the electrical path between the indicated ports on the SIB-L and the corresponding SIB-S. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_FM_ERROR_F13_FB_TX_VC

155

JUNOS 10.1 System Log Messages Reference

CHASSISD_FM_ERROR_SIB_L_FB_RX_VC
System Log Message

error-message on LCC lcc SIB_Lfrom-lcc-sib_FBfiber-bundle VCSEL vcsel Channel vcsel-channel connected to F13SIBto-sfc-sib 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). The chassis process (chassisd) on the routing node that houses the indicated ST-SIB-L detected the indicated error as packets that were traveling in the optical media. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_FM_ERROR_SIB_L_FB_SMF
System Log Message Description

FM: error-message error occurred on link to-from-sib SIB-L#sib-slot to-from-scc SCC In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the TX Matrix platform (the switch-card chassis, or SCC) and the SIBs in the T640 routing nodes (called SIB-Ls). The chassis process (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. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FM_ERROR_SIB_L_FB_TXP
System Log Message Description

LCC lcc ST-SIB-L:sib-slot Fiber-bundle:fiber-bundle is error-message In a Tx-Plus routing matrix, the fiber-optic cable between each Switch Interface Board in a T1600 routing node (called a ST-SIB-L) must connect to a specific SIB port on the TX-Plus Matrix platform (called a F13SIB). The cable connected at the indicated ST-SIB-L had the indicated error. Error: An error occurred error

Type Severity

156

CHASSISD_FM_ERROR_SIB_L_FB_RX_VC

Chapter 17: CHASSISD System Log Messages

Action

Contact your technical support representative.

CHASSISD_FM_ERROR_SIB_L_FB_TX_VC
System Log Message

error-message on LCC lcc SIB_Lfrom-lcc-sib_FBfiber-bundle VCSEL vcsel Channel vcsel-channel connected to F13SIBto-sfc-sib 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). The chassis process (chassisd) on the routing node that houses the indicated ST-SIB-L detected the indicated error as packets that were traveling in the indicated direction were translated between electrical and optical media. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_FM_ERROR_SIB_L_HSR_PFE
System Log Message Description

FM: error-message on LCC:lcc FPCfpc-slot_pfe link to ST-SIB-Lto-lcc-sib_fchip-id 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). 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. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FM_ERROR_SIB_L_HSR_TXP
System Log Message

FM: error-message on LCC:lcc FPCfpc-slot_pfe link connected by ST-SIB-Lfrom-lcc-sib_fchip-id_s-port_FBfiber-bundle to F13SIBto-sfc-sib 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). 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 ports on the SIB-L and the corresponding F13SIB.

Description

CHASSISD_FM_ERROR_SIB_L_FB_TXP

157

JUNOS 10.1 System Log Messages Reference

Type Severity Action

Error: An error occurred error Contact your technical support representative.

CHASSISD_FM_ERROR_SIB_L_MISMATCH
System Log Message Description

FM: fiber cable from SIB-L#sib-slot possibly connected to wrong SIB-S In a routing matrix, the fiber-optic cable between each Switch Interface Board in a T640 routing node (called a SIB-L) must connect to a specific SIB port on the TX Matrix platform (called a SIB-S). The cable originating at the indicated SIB-L was possibly plugged into the wrong SIB-S port or wrong SIB-S. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FM_ERROR_SIB_L_VC_PWR
System Log Message

FM: High power difference at LCC lcc SIB_Lsib-slot_FBfiber-bundle VCSEL vcsel Channel vcsel-channel connected to F13SIBfrom-sfc-sib 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). 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. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_FM_ERROR_SIB_S_FB_HSR
System Log Message

FM: HSR error occurred on link from LCClcc SIB-L port F(l-row,l-port) to SIB-S#sib-slot port F(s-row,s-port) In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the TX Matrix platform (called SIB-Ss) and the SIBs in the T640 routing nodes (called SIB-Ls). The chassis process (chassisd) on the TX Matrix platform detected an error in the electrical path between the

Description

158

CHASSISD_FM_ERROR_SIB_L_HSR_TXP

Chapter 17: CHASSISD System Log Messages

indicated port on the indicated SIB-S and the indicated port on a SIB-L installed in the indicated routing node (line-card chassis, or LCC).
Type Severity Action

Error: An error occurred error Contact your technical support representative.

CHASSISD_FM_ERROR_SIB_S_FB_SMF
System Log Message Description

FM: error-message error occurred on link to-from-sib-s SIB-S#sib-slot to-from-lcc LCClcc In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the TX Matrix platform (called SIB-Ss) and the SIBs in the T640 routing nodes (line-card chassis, or LCCs). The chassis process (chassisd) on the TX Matrix platform detected the indicated error as packets that were traveling to or from the indicated LCC were translated between electrical and optical media. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FM_MEMORY_ERROR
System Log Message Description Type Severity Action

function-name: unable to allocate memory; error-message The chassis process (chassisd) could not allocate memory for a fabric operation. Error: An error occurred warning Contact your technical support representative.

CHASSISD_FM_SIB_ERROR
System Log Message Description

Fabric management error for SIB sib-slot: error-message The chassis process (chassisd) detected the indicated type of error on the indicated Switch Interface Board (SIB) and performed the indicated action. Error: An error occurred error

Type Severity

CHASSISD_FM_ERROR_SIB_S_FB_HSR

159

JUNOS 10.1 System Log Messages Reference

Action

Contact your technical support representative.

CHASSISD_FM_SIB_FPC_TYPE_ERROR
System Log Message Description

SIB sib-slot does not support features required for FPC Type 4 The indicated Switch Interface Board (SIB) does not support features required by the Flexible PIC Concentrator (FPC) Type 4. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FPC_NOT_FOUND
System Log Message Description

function-name: unable to find FPC for PIC attachment operation The chassis process (chassisd) attempted to bring a Physical Interface Card (PIC) online, but could not find the Flexible PIC Concentrator (FPC) that houses it. Error: An error occurred warning Contact your technical support representative.

Type Severity Action

CHASSISD_FPC_PIC_DETECT_TIMEOUT
System Log Message Description

function-name: PIC detection on FPC fpc-slot timed out The chassis process (chassisd) expects to receive notification within a timeout period that each Flexible PIC Concentrator (FPC) has attached the Physical Interface Cards (PICs) that it houses. It did not receive notification from the indicated FPC. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FPC_TYPE_SIB_TYPE_ERROR
System Log Message

Installed SIB type (SIB-I8-F16) does not support features required by FPC fpc-slot

160

CHASSISD_FM_SIB_ERROR

Chapter 17: CHASSISD System Log Messages

Description

The indicated Flexible PIC Concentrator (FPC) is Type 4, which is not supported by Switch Interface Board (SIB) type SIB-I8-F16. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FRU_ALREADY_OFFLINE
System Log Message Description

fru-name fru-slot already offline The chassis process (chassisd) received a request to take the indicated component (field-replaceable unit, or FRU) offline, but the FRU was already offline. Event: This message reports an event, not an error error

Type Severity

CHASSISD_FRU_ALREADY_ONLINE
System Log Message Description

Received request to bring fru-name fru-slot online; it was already online The chassis process (chassisd) received a request to bring the indicated component (field-replaceable unit, or FRU) online, but the FRU was already online. Event: This message reports an event, not an error warning

Type Severity

CHASSISD_FRU_EVENT
System Log Message Description

function-name: state fru-name fru-slot The state of the indicated component (field-replaceable unit, or FRU) changed as indicated. Event: This message reports an event, not an error notice

Type Severity

CHASSISD_FRU_INVALID_SLOT
System Log Message

FRU fru-name is not supported in current slot

CHASSISD_FPC_TYPE_SIB_TYPE_ERROR

161

JUNOS 10.1 System Log Messages Reference

Description

The chassis process (chassisd) detected that the indicated hardware component (field-replaceable unit, or FRU) was inserted in a slot that is not valid for that component type. Error: An error occurred critical Contact your technical support representative.

Type Severity Action

CHASSISD_FRU_IO_ERROR
System Log Message Description

function-name: fru-name operation error: reason (error-message) The chassis process (chassisd) could not perform the indicated I/O operation on the indicated component (field-replaceable unit, or FRU). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FRU_IO_OFFSET_ERROR
System Log Message Description

function-name: fru-name operation error: reason 0xoffset (error-message) The chassis process (chassisd) could not perform the indicated I/O operation at the indicated byte offset. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_FRU_IPC_WRITE_ERROR
System Log Message Description

function-name: FRU fru-name, errno error-code, error-message The chassis process (chassisd) could not send an interprocess communication (IPC) message to the indicated component (field-replaceable unit, or FRU) because of the indicated error. Error: An error occurred warning

Type Severity

162

CHASSISD_FRU_INVALID_SLOT

Chapter 17: CHASSISD System Log Messages

CHASSISD_FRU_OFFLINE_FAILED
System Log Message Description

Unable to take fru-name fru-slot offline because FRU sequencer is active: reason The chassis process (chassisd) could not take the indicated component (field-replaceable unit, or FRU) offline for the indicated reason. Event: This message reports an event, not an error notice

Type Severity

CHASSISD_FRU_OFFLINE_NOTICE
System Log Message Description

Taking fru-name fru-slot offline: reason The chassis process (chassisd) took the indicated component (field-replaceable unit, or FRU) offline for the indicated reason. Event: This message reports an event, not an error notice

Type Severity

CHASSISD_FRU_OFFLINE_TIMEOUT
System Log Message Description

Offline request timed out; fru-name fru-slot restarted The indicated component (field-replaceable unit, or FRU) did not go offline within the time period that is normally sufficient for synchronized shutdown. After generating this message, the chassis process (chassisd) tried several times to take the FRU offline and powered it down if all attempts failed. Event: This message reports an event, not an error warning

Type Severity

CHASSISD_FRU_ONLINE_TIMEOUT
System Log Message Description

function-name: attempt to bring fru-name fru-slot online timed out The indicated component (field-replaceable unit, or FRU) did not come online within the time that is normally sufficient. After generating this message, the chassis process (chassisd) tried to bring the FRU online several more times. If all attempts failed, the chassisd process raised an alarm and left the FRU offline. Event: This message reports an event, not an error error

Type Severity

CHASSISD_FRU_OFFLINE_FAILED

163

JUNOS 10.1 System Log Messages Reference

CHASSISD_FRU_STEP_ERROR
System Log Message Description

fru-name fru-slot at step step-number The power-on sequence for the indicated component (field-replaceable unit, or FRU) failed at the indicated point. Error: An error occurred error

Type Severity

CHASSISD_FRU_UNRESPONSIVE
System Log Message Description

Error for fru-name fru-slot: error-message; action The chassis process (chassisd) tried to bring the indicated component (field-replaceable unit, or FRU) online, but the attempt failed in the indicated way. As a result, the chassisd process performed the indicated action. Event: This message reports an event, not an error error

Type Severity

CHASSISD_FRU_UNRESPONSIVE_RETRY
System Log Message Description

Attempt count to power on fru-name fru-slot timed out; restarted it The chassis process (chassisd) tried the indicated number of times to bring the indicated component (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. Event: This message reports an event, not an error error

Type Severity

CHASSISD_FRU_UNSUPPORTED
System Log Message Description

chassisd invalidated support for fru-name fru-slot The chassis process (chassisd) invalidated support for the indicated component (field-replaceable unit, or FRU) during initialization. Error: An error occurred warning

Type Severity

164

CHASSISD_FRU_STEP_ERROR

Chapter 17: CHASSISD System Log Messages

CHASSISD_FRU_VERSION_MISMATCH
System Log Message Description

component version mismatch for fru-name -- expected expected-value, got received-value The chassis process (chassisd) verifies that it supports the revision level or version of a component (field-replaceable unit, or FRU). The revision level for the indicated FRU was unsupported or otherwise invalid. Event: This message reports an event, not an error error Upgrade the FRU.

Type Severity Action

CHASSISD_GASIC_ID_ERROR
System Log Message Description

Fchip: invalid SIB slot A routine tried to determine the identifier for an application-specific integrated circuit (ASIC) on a Switch Interface Board (SIB). The attempt failed, because the supplied SIB slot number was invalid. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_GBUS_NOT_READY
System Log Message Description

function-name: fru-name not ready for power up (RTIME_PWR_COND = 0xvalue) The GBUS was not ready when the chassis process (chassisd) first tried to power it on, and the power-up operation timed out. Error: An error occurred error The probable cause is hardware error. Contact your technical support representative.

Type Severity Cause Action

CHASSISD_FRU_VERSION_MISMATCH

165

JUNOS 10.1 System Log Messages Reference

CHASSISD_GBUS_READBACK_ERROR
System Log Message

Readback error from GBUS for fru-name fru-slot ([0xgbus-address, 0xgbus-registers] -> 0xreturn-value) There was an error when the chassis process (chassisd) tried to read back information from the GBUS on the indicated component (field-replaceable unit, or FRU). Error: An error occurred error The probable cause is hardware error. Contact your technical support representative.

Description

Type Severity Cause Action

CHASSISD_GBUS_RESET_EVENT
System Log Message Description

fru-name#fru-slot - command The chassis process (chassisd) reset the GBUS for the indicated component (field-replaceable unit, or FRU). This is a normal part of startup. Event: This message reports an event, not an error warning

Type Severity

CHASSISD_GBUS_SANITY_ERROR
System Log Message Description

function-name: fru-name fru-slot -- management bus failed sanity test The chassis process (chassisd) checks its management GBUS with a set of test operations when it is started. The tests failed. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_GENERIC_ERROR
System Log Message Description

function-name: error-message The chassis process (chassisd) detected the indicated error.

166

CHASSISD_GBUS_READBACK_ERROR

Chapter 17: CHASSISD System Log Messages

Type Severity Action

Error: An error occurred error Perform any corrective actions mentioned in the error message.

CHASSISD_GENERIC_WARNING
System Log Message Description Type Severity

function-name: error-message The chassis process (chassisd) generated the indicated warning message. Error: An error occurred notice

CHASSISD_GETTIMEOFDAY
System Log Message Description

Unexpected error from gettimeofday: error-code -- error-message The chassis process (chassisd) could not obtain the time of day because of the indicated error. Error: An error occurred warning

Type Severity

CHASSISD_GRES_UNSUPP_PIC
System Log Message Description

Unable to enable graceful Routing Engine switchover; PIC does not support it The chassis process (chassisd) could not enable graceful Routing Engine switchover because an installed Physical Interface Card (PIC) does not support it. Error: An error occurred error

Type Severity

CHASSISD_HIGH_TEMP_CONDITION
System Log Message Description

Chassis temperature over temperature degrees C (message) The temperature of one or more components (field-replaceable units, or FRUs) exceeded the indicated temperature, which is the lower of two thresholds. 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. Event: This message reports an event, not an error

Type

CHASSISD_GENERIC_ERROR

167

JUNOS 10.1 System Log Messages Reference

Severity Action

warning Increase cooling in the area around the chassis.

CHASSISD_HOST_TEMP_READ
System Log Message Description

Error reading host temperature sensor The chassis process (chassisd) could not read the temperature sensors on the routing platform. Error: An error occurred notice

Type Severity

CHASSISD_HSR_CONFIG_READ_ERROR
System Log Message Description

function-name: unable to read configuration for HSR identifier The indicated function could not read the configuration for the indicated high-speed receiver (HSR). Error: An error occurred error

Type Severity

CHASSISD_HSR_CONFIG_WRITE_ERROR
System Log Message Description

function-name: unable to write configuration for HSR identifier The indicated routine could not write to the configuration for the indicated high-speed receiver (HSR). Error: An error occurred error

Type Severity

CHASSISD_HSR_ELEMENTS_ERROR
System Log Message Description

Provided number of HSR elements (count) was invalid The indicated routine for processing a certain number of high-speed receiver (HSR) elements failed, because the supplied number of elements was invalid. Error: An error occurred error

Type Severity

168

CHASSISD_HIGH_TEMP_CONDITION

Chapter 17: CHASSISD System Log Messages

CHASSISD_HSR_FIFO_ERROR
System Log Message Description

function-name: FIFO read failed for HSR identifier A first in, first out (FIFO) read error occurred during execution of the indicated routine on the indicated high-speed receiver (HSR). Error: An error occurred error

Type Severity

CHASSISD_I2CS_READBACK_ERROR
System Log Message

Readback error from I2C slave for fru-name fru-slot ([0xi2cs-address, 0xoffset] -> 0xerror-code) The chassis process (chassisd) could not read back information from the I2C slave (I2CS) about the indicated component (field-replaceable unit, or FRU). Error: An error occurred error The probable cause is hardware error. Contact your technical support representative.

Description

Type Severity Cause Action

CHASSISD_I2C_BAD_IDEEPROM_FORMAT
System Log Message Description

Invalid IDEEPROM format for fru-name The chassis process (chassisd) determined that the ID EEPROM format specified for the indicated type of hardware component (field-replaceable unit, or FRU) is not valid for it. Error: An error occurred critical Contact your technical support representative.

Type Severity Action

CHASSISD_I2C_FIC_PRESENCE_READ
System Log Message

function-name: fru-name unable to get presence masks (error-message)

CHASSISD_HSR_FIFO_ERROR

169

JUNOS 10.1 System Log Messages Reference

Description

The chassis process (chassisd) could not read I2C data with presence information about the indicated component (field-replaceable unit, or FRU). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_I2C_GENERIC_ERROR
System Log Message Description Type Severity Action

function-name: error-message The indicated error occurred during an I2C access library operation. Error: An error occurred error Contact your technical support representative.

CHASSISD_I2C_INVALID_ASSEMBLY_ID
System Log Message Description

'0xassembly-id' is invalid value for fru-name assembly ID The assembly ID for the indicated component (field-replaceable unit, or FRU) was not valid for its type. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_I2C_IOCTL_FAILURE
System Log Message

function-name: operation ioctl failure for group group-id at address 0xaddress (errno error-code) The chassis process (chassisd) could not perform the indicated ioctl() operation on the I2C data for the indicated component (field-replaceable unit, or FRU). Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

170

CHASSISD_I2C_FIC_PRESENCE_READ

Chapter 17: CHASSISD System Log Messages

CHASSISD_I2C_IO_FAILURE
System Log Message Description

function-name: fru-name operation failed for group group-id at address 0xaddress The chassis process (chassisd) could not perform the indicated I/O operation on the I2C data for the indicated component (field-replaceable unit, or FRU). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_I2C_MIDPLANE_CORRUPT
System Log Message

Corruption on midplane ID EEPROM (ID: 0xassembly-id, MAC address: 0xmac-address, 0xversion) The chassis process (chassisd) found corrupted information when it tried to verify the parameters of the midplane's I2C ID EEPROM. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_I2C_RANGE_ERROR
System Log Message

function-name: requested offset was out of range (offset offset + nbytes count > 256) The indicated offset, which is greater than 256, was specified in a read request for an I2C device. Error: An error occurred error No I2C device uses or has storage above an offset of 256. Contact your technical support representative.

Description

Type Severity Cause Action

CHASSISD_I2C_READ_ERROR
System Log Message

function-name: read error for group group-id at address 0xaddress, offset offset

CHASSISD_I2C_IO_FAILURE

171

JUNOS 10.1 System Log Messages Reference

Description Type Severity Action

The chassis process (chassisd) could not read I2C data from the indicated device. Error: An error occurred error Contact your technical support representative.

CHASSISD_I2C_WRITE_ERROR
System Log Message Description Type Severity Action

function-name: write error for group group-id at address 0xaddress, offset offset The chassis process (chassisd) could not write I2C data to the indicated device. Error: An error occurred error Contact your technical support representative.

CHASSISD_IDEEPROM_READ_ERROR
System Log Message Description

Unable to read fru-name ID EEPROM The chassis process (chassisd) could not read the I2C ID EEPROM of the indicated component (field-replaceable unit, or FRU). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_IFDEV_CREATE_FAILURE
System Log Message Description

function-name: unable to create interface device for interface-name (error-message) The chassis process (chassisd) creates initial interface devices for newly installed Physical Interface Cards (PICs) and pseudodevices. It could not create a device for the indicated PIC or pseudodevice. Error: An error occurred error Necessary resources might have been unavailable.

Type Severity Cause

172

CHASSISD_I2C_READ_ERROR

Chapter 17: CHASSISD System Log Messages

Action

Contact your technical support representative.

CHASSISD_IFDEV_CREATE_NOTICE
System Log Message Description

function-name: created device-name for interface-name The chassis process (chassisd) created the initial interface device for the indicated newly installed Physical Interface Card (PIC) or pseudodevice. Event: This message reports an event, not an error notice

Type Severity

CHASSISD_IFDEV_DETACH_ALL_PSEUDO
System Log Message Description Type Severity

ifdev_detach(pseudo devices: all) The chassis process (chassisd) detached the interface devices for all pseudodevices. Event: This message reports an event, not an error notice

CHASSISD_IFDEV_DETACH_FPC
System Log Message Description

ifdev_detach_fpc(fpc-slot) The chassis process (chassisd) detached the interface devices for all Physical Interface Cards (PICs) installed in the indicated Flexible PIC Concentrator (FPC). Event: This message reports an event, not an error notice

Type Severity

CHASSISD_IFDEV_DETACH_PIC
System Log Message Description

ifdev_detach_pic(fpc-slot/pic-slot) The chassis process (chassisd) detached the interface devices for the indicated Physical Interface Card (PIC). Event: This message reports an event, not an error notice

Type Severity

CHASSISD_IFDEV_CREATE_FAILURE

173

JUNOS 10.1 System Log Messages Reference

CHASSISD_IFDEV_DETACH_PSEUDO
System Log Message

ifdev_detach(pseudo devices: porttype port-type, sdev=sdev-number, edev=edev-number) The chassis process (chassisd) detached the interface devices for the indicated pseudodevices. Event: This message reports an event, not an error notice

Description

Type Severity

CHASSISD_IFDEV_DETACH_TLV_ERROR
System Log Message

ifdev_detach: rtslib_ifdm_change_tlvs failed for slot fpc-slot dev idx device-id error-message The chassis process (chassisd) asked the kernel to remove the indicated interface from the kernel interface table. The request failed. Error: An error occurred error

Description

Type Severity

CHASSISD_IFDEV_GETBYNAME_NOTICE
System Log Message

function-name: ifdm get_by_name failed for interface-type interface device interface-name (error-message) The chassis process (chassisd) failed to find the indicated interface device, even though it just created it. Event: This message reports an event, not an error warning There was a problem with interface state creation. Contact your technical support representative.

Description

Type Severity Cause Action

CHASSISD_IFDEV_GET_BY_INDEX_FAIL
System Log Message Description

function-name: rtslib_ifdm_get_by_index failed: error-code - error-message The chassis process (chassisd) could not obtain information about an interface device.

174

CHASSISD_IFDEV_DETACH_PSEUDO

Chapter 17: CHASSISD System Log Messages

Type Severity

Error: An error occurred error

CHASSISD_IFDEV_GET_BY_NAME_FAIL
System Log Message Description

Unable to retrieve information for interface device interface-name: error-message The chassis process (chassisd) could not obtain information about the indicated interface device. Error: An error occurred error

Type Severity

CHASSISD_IFDEV_NO_MEMORY
System Log Message Description

function-name: unable to allocate memory for interface-type interface The chassis process (chassisd) could not allocate memory when creating an interface device for the indicated interface type. Error: An error occurred error Resources on the system are extremely limited. Eliminate the resource limitations and restart the Physical Interface Card (PIC) that houses the interface for which the interface device could not be created.

Type Severity Cause Action

CHASSISD_IFDEV_RETRY_NOTICE
System Log Message

function-name: attempt count to add interface device interface-name failed (error-message) The chassis process (chassisd) tried the indicated number of times to create the indicated interface device, but the attempts failed. After generating this message, the chassisd process waited a while for resources to free up and tried again. Event: This message reports an event, not an error warning Necessary resources might have been unavailable. They should become available soon.

Description

Type Severity Cause

CHASSISD_IFDEV_GET_BY_INDEX_FAIL

175

JUNOS 10.1 System Log Messages Reference

CHASSISD_IFDEV_RTSLIB_FAILURE
System Log Message Description

function-name: library-function-name failed (error-message) The chassis process (chassisd) could not create an interface device because an error occurred during the indicated call to the routing socket library. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_IOCTL_FAILURE
System Log Message Description

function-name: reason for fru-name (error-message) The chassis process (chassisd) could not perform the indicated ioctl() operation on the indicated component (field-replaceable unit, or FRU). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_IPC_ANNOUNCE_TIMEOUT
System Log Message

function-name: no ack received from fru-type for fru-name fru-slot state change (0xsent-mask, acks 0xack-mask) The chassis process (chassisd) notified the indicated components (field-replaceable units, or FRUs) that the component in the indicated slot was changing state. It did not receive the expected acknowledgment. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_IPC_CONNECTION_DROPPED
System Log Message

Dropped IPC connection for fru-name fru-slot

176

CHASSISD_IFDEV_RTSLIB_FAILURE

Chapter 17: CHASSISD System Log Messages

Description

The chassis process (chassisd) dropped its interprocess communication (IPC) connection to the indicated component (field-replaceable unit, or FRU). Event: This message reports an event, not an error warning

Type Severity

CHASSISD_IPC_DAEMON_WRITE_ERROR
System Log Message Description

pipe_write failure for connection-id; connection error: error-message (errno error-code) The chassis process (chassisd) could not write to a socket, because of the indicated error. The socket is for a connection to another process that runs on the Routing Engine and helps manage the chassis. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_IPC_ERROR
System Log Message Description

function-name: error-message An error occurred when the chassis process (chassisd) received an interprocess communication (IPC) message. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_IPC_FLUSH_ERROR
System Log Message Description

function-name: flush operation failed for fru-name fru-slot The chassis process (chassisd) could not write to a socket that it was using to communicate with the indicated component (field-replaceable unit, or FRU). Error: An error occurred warning Contact your technical support representative.

Type Severity Action

CHASSISD_IPC_CONNECTION_DROPPED

177

JUNOS 10.1 System Log Messages Reference

CHASSISD_IPC_MSG_DROPPED
System Log Message

Dropping message from connection queue: type = message-type, subtype = message-subtype The chassis process (chassisd) dropped an interprocess communication (IPC) message because the message queue had already reached maximum capacity. Error: An error occurred error 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. Contact your technical support representative.

Description

Type Severity Cause

Action

CHASSISD_IPC_MSG_ERROR
System Log Message

function-name: error code error-code, type message-type, subtype message-subtype, opcode message-opcode The chassis process (chassisd) detected an error in an interprocess communication (IPC) message with the indicated characteristics. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_IPC_MSG_FRU_NOT_FOUND
System Log Message

function-name: unable to locate FRU for message with type message-type, subtype message-subtype, opcode message-opcode The chassis process (chassisd) could not locate a component (field-replaceable unit, or FRU) to handle the interprocess communication (IPC) message with the indicated characteristics that it received. The message was ignored. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

178

CHASSISD_IPC_MSG_DROPPED

Chapter 17: CHASSISD System Log Messages

CHASSISD_IPC_MSG_QFULL_ERROR
System Log Message

Dropping message from connection queue: type = message-type, subtype = message-subtype The chassis process (chassisd) had to discard a message because the queue of messages waiting for a connection was already full. Error: An error occurred error

Description

Type Severity

CHASSISD_IPC_MSG_UNHANDLED
System Log Message

function-name: unable to handle fru-name message with type message-type, subtype message-subtype, length length, opcode message-opcode, error error-code 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. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_IPC_UNEXPECTED_MSG
System Log Message

function-name: invalid message received: message (message type message-type, subtype message-subtype) The chassis process (chassisd) received a unexpected message with the indicated characteristics. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_IPC_UNEXPECTED_RECV
System Log Message

Received unexpected message from connection-id: type = message-type, subtype = message-subtype

CHASSISD_IPC_MSG_QFULL_ERROR

179

JUNOS 10.1 System Log Messages Reference

Description

The chassis process (chassisd) received an unexpected message from a peer connection. Error: An error occurred error

Type Severity

CHASSISD_IPC_WRITE_ERROR
System Log Message

function-name: pipe_write failure for SCC connection with error error-code (error-message) A line-card chassis in a routing matrix attempted to send data to the TX Matrix platform (switch-card chassis, or SCC) over a pipe. The attempt failed with the indicated error. Error: An error occurred warning

Description

Type Severity

CHASSISD_IPC_WRITE_ERR_NO_PIPE
System Log Message Description

FRU has no connection pipe function-name fru-name 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. Error: An error occurred warning

Type Severity

CHASSISD_IPC_WRITE_ERR_NULL_ARGS
System Log Message Description

FRU has no connection arguments function-name fru-name The chassis process (chassisd) could not send a message to the indicated component (field-replaceable unit, or FRU) because one or more required parameters had a null value. Error: An error occurred warning

Type Severity

CHASSISD_ISSU_BLOB_ERROR
System Log Message

fru-name: error-message

180

CHASSISD_IPC_UNEXPECTED_RECV

Chapter 17: CHASSISD System Log Messages

Description

The chassisd process (chassisd) detected the indicated error while handling blobs (opaque information) for the indicated field replaceable unit (fru). The blobs are used by the fru to store state information across in service software upgrade(issu) reboot. Error: An error occurred notice

Type Severity

CHASSISD_ISSU_DAEMON_ERROR
System Log Message Description

Daemon [process-name] state:<state> error:<error-message> The chassisd process (chassisd) encountered the indicated error in the indicated in service software upgrade (issu) state for the indicated daemon. Error: An error occurred notice

Type Severity

CHASSISD_ISSU_ERROR
System Log Message Description

action error-code(error-message) The chassisd process (chassisd) encountered the indicated error for the indicated in service software upgrade process (issu) action. Error: An error occurred notice

Type Severity

CHASSISD_ISSU_FRU_ERROR
System Log Message Description

fru-name: state:[state] error-message The chassisd process (chassisd) encoutered the indicated error during the in service software upgrade for the indicated field replaceable unit (fru). Error: An error occurred notice

Type Severity

CHASSISD_ISSU_FRU_IPC_ERROR
System Log Message Description

fru-name: state:[state] error:[message] reason:[error-message] The chassisd process (chassisd) detected the indicated error for the indicated field replaceable unit (fru) during in service software upgrade (issu).

CHASSISD_ISSU_BLOB_ERROR

181

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred notice

CHASSISD_JTREE_ERROR
System Log Message Description

jtree terminate operation returned error-code The chassis process (chassisd) received the indicated error when executing the JUNOS system call that terminates the jtree. Event: This message reports an event, not an error warning

Type Severity

CHASSISD_LCC_RELEASE_MASTERSHIP
System Log Message

Backup Routing Engine became master, because JUNOS version of former master did not match SCC master The chassis process (chassisd) running on the master Routing Engine on a T640 routing node (line-card chassis, or LCC, in a routing matrix) relinquished mastership to the backup Routing Engine in the LCC. Event: This message reports an event, not an error notice The version of the JUNOS software 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.

Description

Type Severity Cause

CHASSISD_LOST_MASTERSHIP
System Log Message Description

Routing Engine lost mastership; exiting The chassis process (chassisd) running on the master Routing Engine exited, because mastership switched to the other Routing Engine. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_MAC_ADDRESS_AE_ERROR
System Log Message

chassisd MAC address allocation error for aedevice-id

182

CHASSISD_ISSU_FRU_IPC_ERROR

Chapter 17: CHASSISD System Log Messages

Description

The chassis process (chassisd) could not obtain a media access control (MAC) address for the indicated aggregated Ethernet interface because of an internal error. Error: An error occurred error

Type Severity

CHASSISD_MAC_ADDRESS_CBP_ERROR
System Log Message Description

chassisd MAC address allocation error for CBP The chassis process (chassisd) could not obtain a media access control (MAC) address for a customer backbone port because of an internal error. Error: An error occurred error

Type Severity

CHASSISD_MAC_ADDRESS_ERROR
System Log Message Description

chassisd MAC address allocation exceed error for FPC fpc-slot, PIC pic-slot, port port The chassis process (chassisd) could not obtain a media access control (MAC) address for the indicated interface because of an internal error. Error: An error occurred error

Type Severity

CHASSISD_MAC_ADDRESS_FABRIC_ERR
System Log Message Description

Unable to allocate MAC address for fabric interface device-id The chassis process (chassisd) could not obtain a media access control (MAC) address for the indicated fabric interface because of an internal error. Error: An error occurred error

Type Severity

CHASSISD_MAC_ADDRESS_IRB_ERROR
System Log Message Description

chassisd MAC address allocation error for IRB The chassis process (chassisd) could not obtain a media access control (MAC) address for an integrated routing and bridging interface because of an internal error. Error: An error occurred

Type

CHASSISD_MAC_ADDRESS_AE_ERROR

183

JUNOS 10.1 System Log Messages Reference

Severity

error

CHASSISD_MAC_ADDRESS_PIP_ERROR
System Log Message Description

chassisd MAC address allocation error for PIP The chassis process (chassisd) could not obtain a media access control (MAC) address for a provider instance port because of an internal error. Error: An error occurred error

Type Severity

CHASSISD_MAC_ADDRESS_VLAN_ERROR
System Log Message Description

chassisd MAC address allocation error for VLAN The chassis process (chassisd) could not obtain a media access control (MAC) address for a vlan interface because of an internal error. Error: An error occurred error

Type Severity

CHASSISD_MAC_DEFAULT
System Log Message Description

Using default MAC address base The chassis process (chassisd) used the default base media access control (MAC) address. Event: This message reports an event, not an error info

Type Severity

CHASSISD_MALLOC_FAILURE
System Log Message Description

function-name: chassisd malloc failed, aborting The chassis process (chassisd) could not allocate memory. The chassisd process tried to continue functioning, but the lack of memory usually causes the process to fail. An administrator needs to restart it at some point. Error: An error occurred error Contact your technical support representative.

Type Severity Action

184

CHASSISD_MAC_ADDRESS_IRB_ERROR

Chapter 17: CHASSISD System Log Messages

CHASSISD_MASTER_PCG_REMOVED
System Log Message

Master PCG (slot pcg-slot) removed; powering down Packet Forwarding Engine complex The master Packet Forwarding Engine Clock Generator (PCG) was removed. The PCG provides the system clock for all application-specific integrated circuits (ASICs) in the routing platform, so packet forwarding halts until the Packet Forwarding Engine is restarted and a PCG is functioning as master. Error: An error occurred critical

Description

Type Severity

CHASSISD_MASTER_SCG_REMOVED
System Log Message Description

Master SCG (slot fru-slot) removed; powering it down The master SONET Clock Generator (SCG) was removed. The SCG provides the clock for SONET/SDH interface timing, so those interfaces might drop packets and experience other errors until a new clock source is established. Error: An error occurred critical

Type Severity

CHASSISD_MBUS_ERROR
System Log Message Description Type Severity Action

fru-name fru-slot: management bus failed sanity test Startup tests on the indicated FRU's management bus failed. Error: An error occurred error Contact your technical support representative.

CHASSISD_MCHASSIS_SWITCH_WARNING
System Log Message

CB settings on chassis-type old-index changed: switch is now 'value', chassis index is now 0xnew-index A toggle switch on the back of the Control Board on each platform in a routing matrix is set to 'M' (multichassis) on the T640 routing nodes and to 'S' (single-chassis) on the TX Matrix platform. On a T640 routing node, the adjacent dial is set to the node's index number in the routing matrix (0 through 3); on the TX Matrix platform it is set

Description

CHASSISD_MASTER_PCG_REMOVED

185

JUNOS 10.1 System Log Messages Reference

to 0. The setting of the toggle switch, the dial, or both, changed to the indicated values on the indicated platform. The new settings take effect when the routing matrix next reboots.
Type Severity Action

Event: This message reports an event, not an error warning If the changes were accidental, return the toggle and dial to the correct settings before the next reboot. If the changes were intended, disconnect and move the cables on the TX Matrix platform Switch Interface Board (SIB) to the row that corresponds to the T640 routing node's new index number.

CHASSISD_MCS_INTR_ERROR
System Log Message Description

Received SIGUSR2 without any interrupts pending The chassis process (chassisd) received the indicated interrupt signal. The signal normally indicates that an event on the Miscellaneous Control Subsystem (MCS) requires servicing. However, the chassisd process did not find such an event pending. This error does not usually cause component failure. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_MGR_CONNECT
System Log Message Description

function-name evSelectFD: initial pipe create aborted (errno error-code) The chassis process (chassisd) could not to open a pipe for interprocess communication (IPC) to a component (field-replaceable unit, or FRU). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_MIC_OFFLINE_NOTICE
System Log Message Description Type

Taking MIC mic-slot in FPC fpc-slot offline: reason The chassis process (chassisd) took the indicated MIC offline, for the indicated reason. Event: This message reports an event, not an error

186

CHASSISD_MCHASSIS_SWITCH_WARNING

Chapter 17: CHASSISD System Log Messages

Severity

notice

CHASSISD_MULTILINK_BUNDLES_ERROR
System Log Message Description

Unable to set multilink Frame Relay UNI NNI bundles for PIC pic-slot in FPC fpc-slot The chassis process (chassisd) could not create multilink Frame Relay user-to-network interface and network-to-network interface (MLFR UNI NNI [FRF.16]) bundles for the indicated Physical Interface Card (PIC). Error: An error occurred warning Contact your technical support representative.

Type Severity Action

CHASSISD_NO_PCGS
System Log Message Description

No PCG status The chassis process (chassisd) could not find an operational Packet Forwarding Engine Clock Generator (PCG). Packet forwarding is halted until a PCG becomes operational. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_NO_SCGS
System Log Message Description

No SCG state 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. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_OFFLINE_NOTICE
System Log Message

Routing Engine offline: message

CHASSISD_MIC_OFFLINE_NOTICE

187

JUNOS 10.1 System Log Messages Reference

Description Type Severity

The chassis process (chassisd) took the Routing Engine offline. Event: This message reports an event, not an error critical

CHASSISD_OID_GEN_FAILED
System Log Message Description

Unable to generate OID: oid (error-message) The chassis process (chassisd) could not generate an object identifier (OID) for the indicated object. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_OVER_TEMP_CONDITION
System Log Message

Chassis temperature over temperature degrees C (message); routing platform will shutdown in duration seconds if condition persists The temperature of one or more components (field-replaceable units, or FRUs) exceeded the indicated temperature, which is the upper of two thresholds. The fans (and impellers, if applicable) were in the indicated state. If the temperature does not go below the threshold within four minutes after the chassis process (chassisd) detects this condition, the chassisd process shuts down the routing platform. When this message was logged, the indicated number of seconds remained before shutdown. Error: An error occurred error Increase cooling in the area around the chassis.

Description

Type Severity Action

CHASSISD_OVER_TEMP_SHUTDOWN_TIME
System Log Message

Chassis temperature above temperature degrees C description (> duration seconds); powering down all FRUs The chassis process (chassisd) shut down the routing platform because the temperature of one or more components exceeded the indicated threshold temperature for the indicated amount of time. Continued operation at the excessive temperature could damage the routing platform. Error: An error occurred

Description

Type

188

CHASSISD_OFFLINE_NOTICE

Chapter 17: CHASSISD System Log Messages

Severity Action

critical Increase cooling in the area around the chassis.

CHASSISD_PARSE_COMPLETE
System Log Message Description Type Severity

Using new configuration The chassis process (chassisd) successfully parsed its configuration file. Event: This message reports an event, not an error info

CHASSISD_PCI_ERROR
System Log Message Description

function-name: error-message While performing an operation on the PCI bus, the chassis process (chassisd) encountered the indicated error. Error: An error occurred error A software or a hardware problem occurred. Contact your technical support representative.

Type Severity Cause Action

CHASSISD_PEER_UNCONNECTED
System Log Message Description

function-name: peer not connected The chassis process (chassisd) processed a packet for a peer with an invalid or missing connection. Event: This message reports an event, not an error error In most cases, this error is caused by peers transitioning up and down unexpectedly. The error is usually transient and nonfatal.

Type Severity Cause

CHASSISD_PEM_BREAKER_TRIP
System Log Message

Circuit breaker tripped for power supply pem-slot

CHASSISD_OVER_TEMP_SHUTDOWN_TIME

189

JUNOS 10.1 System Log Messages Reference

Description Type Severity Action

The circuit breaker was tripped for the indicated power entry module (PEM). Event: This message reports an event, not an error warning Turn on the affected PEM manually.

CHASSISD_PEM_IMPROPER
System Log Message Description Type Severity Action

Power supply pem-slot improper for platform Old PEM is not supported in this platform. Error: An error occurred error Replace old PEM with proper newer PEM

CHASSISD_PEM_INPUT_BAD
System Log Message

error-message for power supply pem-slot (status bits: 0xstatus-code); check circuit breaker The chassis process (chassisd) detected the indicated error condition for the indicated power entry module (PEM). Event: This message reports an event, not an error warning Check the status of the circuit breaker and the input connections.

Description

Type Severity Action

CHASSISD_PEM_NOT_SUFFICIENT
System Log Message

Unable to power up FPC fpc-slot, because no three-input 240-A power supply is installed On the T1600 router, the T1600-FPC4 ES Flexible PIC Concentrator (FPC) requires that at least one three-input 240-A power supply be installed. The chassis process (chassisd) did not power on the T1600-FPC4 ES in the indicated slot because the required power supply is not installed. Error: An error occurred error

Description

Type Severity

190

CHASSISD_PEM_BREAKER_TRIP

Chapter 17: CHASSISD System Log Messages

Action

Install at least one three-input 240-A power supply.

CHASSISD_PEM_OVERLOAD
System Log Message Description

Overload condition for power supply pem-slot (status bits: 0xstatus-code); The indicated power entry module (PEM) reported an output voltage overload condition. Event: This message reports an event, not an error warning There might have been excessive load on the PEM.

Type Severity Cause

CHASSISD_PEM_TEMPERATURE
System Log Message Description

Temperature check bit set for power supply pem-slot; airflow might be inadequate The chassis process (chassisd) detected that the 'temperature check bit' was set in the status bit mask for the indicated power entry module (PEM). Event: This message reports an event, not an error warning The PEM might have exceeded its temperature threshold, possibly because the airflow through it was inadequate.

Type Severity Cause

CHASSISD_PEM_VOLTAGE
System Log Message Description Type Severity Cause

Power supply pem-slot reports problem; check output voltage The indicated power entry module (PEM) reported a problem with its output voltage. Event: This message reports an event, not an error warning There might have been excessive load on the PEM.

CHASSISD_PIC_CMD_GIVEUP
System Log Message

function-name: attempt fpc-slot to bring PIC pic-slot in FPC count online timed out; stopped trying

CHASSISD_PEM_NOT_SUFFICIENT

191

JUNOS 10.1 System Log Messages Reference

Description

The chassis process (chassisd) tried the indicated number of times to bring the indicated Physical Interface Card (PIC) online, but stopped trying after all attempts failed. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_PIC_CMD_TIMEOUT
System Log Message Description

function-name: attempt to bring PIC pic-slot in FPC fpc-slot online timed out The chassis process (chassisd) tried to bring the indicated Physical Interface Card (PIC) online. The attempt took longer than the standard time allotted for that operation. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_PIC_CONFIG_ERROR
System Log Message

Unable to create interface devices during attachment of PIC pic-slot in FPC fpc-slot: graceful switchover not supported The chassis process (chassisd) did not create an interface device for the indicated Physical Interface Card (PIC), because graceful switchover was enabled but is not supported in combination with that PIC type. A PIC must have an interface device to come online, so it remained offline. Error: An error occurred error Remove the PIC or upgrade the JUNOS software.

Description

Type Severity Action

CHASSISD_PIC_HWERROR
System Log Message Description

PIC pic-slot in FPC fpc-slot (PIC type pic-type, version version) had hardware error The indicated Physical Interface Card (PIC) experienced a hardware error. The chassis process (chassisd) did not bring the PIC online. Event: This message reports an event, not an error

Type

192

CHASSISD_PIC_CMD_GIVEUP

Chapter 17: CHASSISD System Log Messages

Severity Action

warning Contact your technical support representative.

CHASSISD_PIC_OFFLINE_NOTICE
System Log Message Description

Taking PIC pic-slot in FPC fpc-slot offline: reason The chassis process (chassisd) took the indicated Physical Interface Card (PIC) offline, for the indicated reason. Event: This message reports an event, not an error notice

Type Severity

CHASSISD_PIC_OID_GEN_FAILED
System Log Message Description

Unable to generate OID for PIC: pic-name (error-message) The chassis process (chassisd) could not generate an object identifier (OID) for the indicated Physical Interface Card (PIC). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_PIC_OID_UNKNOWN
System Log Message Description

Unable to find OID for PIC: i2c-id The chassis process (chassisd) could not determine the object identifier (OID) for the Physical Interface Card (PIC) with the indicated identifier. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_PIC_RESET_ON_SWITCHOVER
System Log Message Description

PIC pic-slot in FPC fpc-slot (type pic-type, version version) will be reset on switchover The chassis process (chassisd) noted that the Physical Interface Card (PIC) with the indicated characteristics needs to be reset when a graceful switchover occurs.

CHASSISD_PIC_HWERROR

193

JUNOS 10.1 System Log Messages Reference

Type Severity

Event: This message reports an event, not an error warning

CHASSISD_PIC_SPEED_INVALID
System Log Message

Set speed for so-fpc-slot/pic-slot/port to default-value because configured value current-value is invalid The chassis process (chassisd) set the speed for the indicated Physical Interface Card (PIC) to the indicated value, because the configured value is either higher than the maximum valid value or lower than the minimum valid value. Error: An error occurred error Reconfigure the PIC with a valid speed.

Description

Type Severity Action

CHASSISD_PIC_VERSION_ERROR
System Log Message

Hardware version (pic-slot) of PIC fpc-slot in FPC pic-type (PIC type version) is not supported The chassis process (chassisd) did not bring the indicated Physical Interface Card (PIC) online, because its hardware version is not supported. Error: An error occurred warning The PIC requires a hardware upgrade. Contact your technical support representative.

Description

Type Severity Cause Action

CHASSISD_PIDFILE_OPEN
System Log Message Description

Unable to open PID file 'filename': errno error-code The chassis process (chassisd) could not open the file where it stores its process ID (PID). Error: An error occurred error

Type Severity

194

CHASSISD_PIC_RESET_ON_SWITCHOVER

Chapter 17: CHASSISD System Log Messages

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.

CHASSISD_PIPE_WRITE_ERROR
System Log Message Description Type Severity Cause

Pipe write error: error-message The chassis process (chassisd) experienced a fatal error while writing to a pipe. Error: An error occurred error There was no reader for the pipe.

CHASSISD_POWER_CHECK
System Log Message Description

fru-name fru-slot not powering up The chassis process (chassisd) could not power up the indicated component (field-replaceable unit, or FRU), because the FRU did not respond. Error: An error occurred error

Type Severity

CHASSISD_POWER_EVENT
System Log Message

Unable to turn off power to fru-name fru-slot; a stand-alone test jumper might be installed The chassis process (chassisd) could not turn off power to the indicated component (field-replaceable unit, or FRU). Event: This message reports an event, not an error warning A common reason is that a standalone test jumper is installed.

Description

Type Severity Cause

CHASSISD_POWER_RATINGS_EXCEEDED
System Log Message Description

PIM/module in slot fru-slot left offline to avoid exceeding chassis power ratings The chassis process (chassisd) did not bring online the component (field-replaceable unit, or FRU) in the indicated slot, because doing so causes the total power demand

CHASSISD_PIDFILE_OPEN

195

JUNOS 10.1 System Log Messages Reference

of components in the chassis to exceed the chassis' power ratings. On a J-series Services Router, the component is a Physical Interface Module (PIM) or other module that installs in a PIM slot.
Type Severity

Error: An error occurred error

CHASSISD_PSD_RELEASE_MASTERSHIP
System Log Message

Backup Routing Engine became master, because JUNOS version of former master did not match RSD master The chassis process (chassisd) running on the master Routing Engine on a System-Domain routing node relinquished mastership to the backup Routing Engine in the PSD. Event: This message reports an event, not an error notice The version of the JUNOS software on the master Routing Engine did not match the version on the RSD platform's master Routing Engine. The version on the backup Routing Engine did match the RSD platform.

Description

Type Severity Cause

CHASSISD_PSU_ERROR
System Log Message Description

error-message power supply pem-slot (status bits: 0xstatus-code); status failure The chassis process (chassisd) detected the indicated error condition for the indicated power supply unit (PSU). Event: This message reports an event, not an error warning

Type Severity

CHASSISD_PSU_FAN_FAIL
System Log Message Description Type Severity

Fan Fail for power supply pem-slot PSU Fan fail bit is set in the status for the indicated power supply unit (PSU) Error: An error occurred warning

196

CHASSISD_POWER_RATINGS_EXCEEDED

Chapter 17: CHASSISD System Log Messages

CHASSISD_PSU_INPUT_BAD
System Log Message Description

error-message power supply pem-slot (status bits: 0xstatus-code); Input failure The chassis process (chassisd) detected the input voltage/warning fault condition for the indicated power supply unit (PSU). Event: This message reports an event, not an error warning Check the status of the input connections.

Type Severity Action

CHASSISD_PSU_OVERLOAD
System Log Message Description Type Severity Cause

Overload condition for power supply pem-slot (status bits: 0xstatus-code); The indicated power supply unit (PSU) reported an output voltage overload condition. Event: This message reports an event, not an error warning There might have been excessive load on the PSU.

CHASSISD_PSU_TEMPERATURE
System Log Message Description

Temperature check bit set for power supply pem-slot; airflow might be inadequate The chassis process (chassisd) detected that the 'temperature check bit' was set in the status bit mask for the indicated power supply unit (PSU). Event: This message reports an event, not an error warning The PSU might have exceeded its temperature threshold, possibly because the airflow through it was inadequate.

Type Severity Cause

CHASSISD_PSU_VOLTAGE
System Log Message Description Type

Power supply pem-slot reports problem; check output voltage The indicated power supply unit (PSU) reported a problem with its output voltage. Event: This message reports an event, not an error

CHASSISD_PSU_INPUT_BAD

197

JUNOS 10.1 System Log Messages Reference

Severity Cause

warning There might have been excessive load on the PSU.

CHASSISD_RANGE_CHECK
System Log Message Description Type Severity Action

function-name: '0xvalue' is invalid value for object-name (out of range) The indicated value was outside the valid range of values for the indicated object. Error: An error occurred error Contact your technical support representative.

CHASSISD_RECONNECT_SUCCESSFUL
System Log Message Description

Successfully reconnected on soft restart The chassis process (chassisd) successfully reconnected with each Packet Forwarding Engine after a soft restart. Event: This message reports an event, not an error notice

Type Severity

CHASSISD_RELEASE_MASTERSHIP
System Log Message Description

Release mastership notification The chassis process (chassisd) running on the master Routing Engine received a request to release mastership. Event: This message reports an event, not an error info The Routing Engine was probably rebooting and graceful Routing Engine switchover is configured.

Type Severity Cause

CHASSISD_RE_INIT_INVALID_RE_SLOT
System Log Message Description

re_init: re routing-engine-slot, out of range The chassis process (chassisd) could not initialize a Routing Engine because the slot number specified for it was invalid.

198

CHASSISD_PSU_VOLTAGE

Chapter 17: CHASSISD System Log Messages

Type Severity

Error: An error occurred error

CHASSISD_RE_OVER_TEMP_CONDITION
System Log Message

Routing Engine routing-engine-slot temperature (temperature C) over threshold degrees C The temperature of the indicated Routing Engine exceeded the indicated temperature, which is the upper of two thresholds. Error: An error occurred error Increase cooling in the area around the chassis.

Description

Type Severity Action

CHASSISD_RE_OVER_TEMP_SHUTDOWN
System Log Message

Routing Engine routing-engine-slot temperature above threshold degrees C for too long; action The chassis process (chassisd) performed the indicated action because the temperature of the indicated Routing Engine exceeded the maximum threshold for more than four minutes. Continued operation at the excessive temperature could damage routing platform components. Error: An error occurred critical Increase cooling in the area around the chassis.

Description

Type Severity Action

CHASSISD_RE_OVER_TEMP_WARNING
System Log Message

Routing Engine routing-engine-slot temperature (temperature C) over threshold degrees C, component will shutdown in duration seconds if condition persists The temperature of the indicated Routing Engine exceeded the indicated temperature, which is the upper of two thresholds. If the temperature does not go below the threshold within four minutes after the chassis process (chassisd) detects this condition, the chassisd process shuts down the indicated component. When this message was logged, the indicated number of seconds remained before shutdown. Error: An error occurred error

Description

Type Severity

CHASSISD_RE_INIT_INVALID_RE_SLOT

199

JUNOS 10.1 System Log Messages Reference

Action

Increase cooling in the area around the chassis.

CHASSISD_RE_WARM_TEMP_CONDITION
System Log Message

Routing Engine routing-engine-slot temperature (temperature C) is above warm temperature limit (threshold C) The temperature of the indicated Routing Engine exceeded the indicated temperature, which is the lower of two thresholds. Event: This message reports an event, not an error error Increase cooling in the area around the chassis.

Description

Type Severity Action

CHASSISD_ROOT_MOUNT_ERROR
System Log Message Description

Unable to determine the mount point for root directory: error-message The chassis process (chassisd) could not determine the mount point for the root file system. Error: An error occurred error

Type Severity

CHASSISD_RTS_SEQ_ERROR
System Log Message Description Type Severity Cause

ifmsg sequence gap expected-value - received-value The chassis process (chassisd) received a routing socket message out of order. Event: This message reports an event, not an error warning A routing socket message was lost because of excessive load or lack of memory.

CHASSISD_SBOARD_VERSION_MISMATCH
System Log Message

Version mismatch: chassisd message version expected-value fru-name message version received-value local IPC version local-ipc-version remote IPC version remote-ipc-version The chassis process (chassisd) verifies that it supports the revision level or version of a component (field-replaceable unit, or FRU). The revision level for the indicated FRU was unsupported or otherwise invalid.

Description

200

CHASSISD_RE_OVER_TEMP_WARNING

Chapter 17: CHASSISD System Log Messages

Type Severity Cause

Error: An error occurred error Either a previous software upgrade did not complete successfully, or the chassisd process or FRU did not restart after a successful software upgrade. Upgrade the software and reboot the routing platform.

Action

CHASSISD_SENSOR_RANGE_NOTICE
System Log Message

fru-name fru-slot temperature is temperature degrees C, which is outside operating range The temperature sensor on the indicated component (field-replaceable unit, or FRU) reported the indicated temperature, which is outside the acceptable operating range. Event: This message reports an event, not an error warning Some sensors generate erroneous readings when a FRU starts up. When this happens, the chassis process (chassisd) rereads the sensor at a later time.

Description

Type Severity Cause

CHASSISD_SERIAL_ID
System Log Message Description

Serial ID read error: error-code -- error-message The chassis process (chassisd) could not obtain the Routing Engine's serial number from the kernel because of the indicated error. Error: An error occurred warning

Type Severity

CHASSISD_SFM_MODE_ERROR
System Log Message Description

function-name: error-message The chassis process could not configure a requested operational mode for a Switching and Forwarding Module (SFM), for the indicated reason. Error: An error occurred info Possible reasons include (a) the requested mode is available only with certain versions of an application-specific integrated circuit (ASIC) (b) not all SFMs are online as

Type Severity Cause

CHASSISD_SBOARD_VERSION_MISMATCH

201

JUNOS 10.1 System Log Messages Reference

required by the requested mode (c) cross-connect mode cannot be configured if an OC-192c Physical Interface Card (PIC) is installed.

CHASSISD_SFM_NOT_ONLINE
System Log Message Description Type Severity Action

function-name: SFM sfm-slot not online The indicated Switching and Forwarding Module (SFM) was offline. Error: An error occurred error Contact your technical support representative.

CHASSISD_SHUTDOWN_NOTICE
System Log Message Description

Shutdown reason: reason Although the chassis process (chassisd) normally does not exit or shut down except when the Routing Engine reboots, it shut down for the indicated reason. Event: This message reports an event, not an error warning

Type Severity

CHASSISD_SIB_INVALID_SLOT
System Log Message Description

fru-name in invalid slot slot The chassis process (chassisd) detected the presence of the switch interface board (SIB) in an invalid slot. The SIB remains offline. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_SIGPIPE
System Log Message Description

SIGPIPE received The chassis process (chassisd) received a signal indicating that its attempt to write to a pipe failed because the reader (which could be another process or thread) did not exist.

202

CHASSISD_SFM_MODE_ERROR

Chapter 17: CHASSISD System Log Messages

Type Severity Cause

Event: This message reports an event, not an error error The entity at the other end of the pipe exited or closed the connection.

CHASSISD_SMB_ERROR
System Log Message Description

smb_read: fpga download not complete: val return-value, action 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. Error: An error occurred error

Type Severity

CHASSISD_SMB_INVALID_PS
System Log Message Description

function-name: invalid power supply status code (0xstatus-code) The chassis process (chassisd) could not set the status (enabled or disabled) for a power supply, because it received the indicated power supply status code, which is invalid. Error: An error occurred critical Contact your technical support representative.

Type Severity Action

CHASSISD_SMB_IOCTL_FAILURE
System Log Message

function-name: 'operation' ioctl failed on system management bus (address 0xmemory-address, cmd 0xcommand) The indicated ioctl() operation failed at the indicated address on the system management bus (SMB). Error: An error occurred critical Contact your technical support representative.

Description

Type Severity Action

CHASSISD_SIGPIPE

203

JUNOS 10.1 System Log Messages Reference

CHASSISD_SMB_READ_FAILURE
System Log Message Description

function-name: read() failed on system management bus (address 0xmemory-address) A read() operation failed at the indicated address on the system management bus (SMB). Error: An error occurred critical Contact your technical support representative.

Type Severity Action

CHASSISD_SNMP_TRAP1
System Log Message Description

SNMP trap generated: trap (argument1 value1) The chassisd process (chassisd) generated the indicated simple network management protocol (snmp) trap with the indicated value. Event: This message reports an event, not an error notice

Type Severity

CHASSISD_SNMP_TRAP10
System Log Message

SNMP trap generated: trap (argument1 value1, argument2 value2, argument3 value3, argument4 value4, argument5 value5, argument6 value6, argument7 value7, argument8 value8, argument9 value9, argument10 value10) The chassis process (chassisd) generated a Simple Network Management Protocol (SNMP) trap with the ten indicated argument-value pairs. Event: This message reports an event, not an error notice

Description

Type Severity

CHASSISD_SNMP_TRAP6
System Log Message

SNMP trap generated: trap (argument1 value1, argument2 value2, argument3 value3, argument4 value4, argument5 value5, argument6 value6) The chassis process (chassisd) generated a Simple Network Management Protocol (SNMP) trap with the six indicated argument-value pairs. Event: This message reports an event, not an error

Description

Type

204

CHASSISD_SMB_READ_FAILURE

Chapter 17: CHASSISD System Log Messages

Severity

notice

CHASSISD_SNMP_TRAP7
System Log Message

SNMP trap generated: trap (argument1 value1, argument2 value2, argument3 value3, argument4 value4, argument5 value5, argument6 value6, argument7 value7) The chassis process (chassisd) generated a Simple Network Management Protocol (SNMP) trap with the seven indicated argument-value pairs. Event: This message reports an event, not an error notice

Description

Type Severity

CHASSISD_SPMB_RESTART
System Log Message Description Type Severity

SPMB slot restarted The indicated Switch Processor Mezzanine Board (SPMB) restarted. Event: This message reports an event, not an error info

CHASSISD_SPMB_RESTART_TIMEOUT
System Log Message Description

Attempt count to restart SPMB slot timed out; action The chassis process (chassisd) tried the indicated number of times to bring the indicated Switch Processor Mezzanine Board (SPMB) online. The chassisd process performed the indicated action as a result of the failure. Event: This message reports an event, not an error error

Type Severity

CHASSISD_SSB_FAILOVERS
System Log Message Description

fru-name failover occurred count times The indicated packet-switching component or control board failed over to a redundant neighbor the indicated number of times, which exceeds the maximum limit. Event: This message reports an event, not an error warning There is probably a system error.

Type Severity Cause

CHASSISD_SNMP_TRAP6

205

JUNOS 10.1 System Log Messages Reference

Action

Contact your technical support representative.

CHASSISD_STANDALONE_FPC_NOTICE
System Log Message Description

chassisd running in standalone FPC mode mode 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. Event: This message reports an event, not an error warning

Type Severity

CHASSISD_SYSCTL_ERROR
System Log Message

function-name: sysctl-error error from sysctl-function-name: error-message (errno error-code) The chassis process (chassisd) received the indicated error from the indicated sysctl() operation. Error: An error occurred error

Description

Type Severity

CHASSISD_TEMP_HOT_NOTICE
System Log Message Description

fru-name temperature of temperature degrees C is above limit (threshold degrees) The temperature of the chassis, or of the indicated component (field-replaceable unit, or FRU), exceeded the lower of two thresholds. The chassis process (chassisd) increased the speed of all functioning fans (and impellers, if applicable) to full speed. If the temperature did not decrease below the threshold within 4 minutes after this message was logged, the chassisd process shut down the routing platform. Event: This message reports an event, not an error error Increase cooling in the area around the chassis.

Type Severity Action

CHASSISD_TEMP_SENSOR_FAILURE
System Log Message

function-name: unable to read temperature sensor for fru-name

206

CHASSISD_SSB_FAILOVERS

Chapter 17: CHASSISD System Log Messages

Description

The temperature sensor for the indicated component (field-replaceable unit, or FRU) either did not respond to a request from the chassis process (chassisd) for a temperature reading or sent a value that is outside the normal operating range. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_TERM_SIGNAL
System Log Message Description

Received SIGTERM request, shutting down The chassis process (chassisd) received the SIGTERM signal, indicating that it should terminate. It began the procedure for clean shutdown and exit, but possibly restarted automatically after exiting. Event: This message reports an event, not an error info

Type Severity

CHASSISD_TIMER_CLR_ERR
System Log Message Description

function-name: message The chassis process (chassisd) could not clear the state of the timer it had set to track the timeout period for an event. Error: An error occurred error

Type Severity

CHASSISD_TIMER_ERR
System Log Message Description

Unable to schedule timeout for description The chassis process (chassisd) could not start a timer to track the timeout period for the indicated event. The seriousness of this error depends on the event. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_TEMP_SENSOR_FAILURE

207

JUNOS 10.1 System Log Messages Reference

CHASSISD_TIMER_VAL_ERR
System Log Message Description

Null timer ID The chassis process (chassisd) started a timer to track the timeout period for an event. The timer returned a null identifier, so the chassisd process could not clear the timer. Error: An error occurred error

Type Severity

CHASSISD_UNEXPECTED_EXIT
System Log Message Description Type Severity

evMainLoop returned return-value (errno error-code) The chassis process (chassisd) exited unexpectedly and reported the indicated error. Error: An error occurred error

CHASSISD_UNEXPECTED_VALUE
System Log Message Description

function-name: 'value' is invalid value for object-name The indicated value was specified for the indicated object in a message received by the chassis process (chassisd). The value is invalid for that type of object. Error: An error occurred warning Contact your technical support representative.

Type Severity Action

CHASSISD_UNSUPPORTED_FPC
System Log Message Description

FPC with I2C ID of 0xi2c-id is not supported A Flexible PIC Concentrator (FPC) of the indicated type was installed in the routing platform. The software does not support that FPC type on this platform. Error: An error occurred error Contact your technical support representative.

Type Severity Action

208

CHASSISD_TIMER_VAL_ERR

Chapter 17: CHASSISD System Log Messages

CHASSISD_UNSUPPORTED_MODEL
System Log Message Description

Model model unsupported with this version of chassisd The version of the chassis process (chassisd) software that is installed on the routing platform does not support this type of chassis. Error: An error occurred warning Contact your technical support representative.

Type Severity Action

CHASSISD_UNSUPPORTED_PIC
System Log Message Description

PIC pic-slot in FPC fpc-slot (type pic-type, version version) is not supported The indicated Physical Interface Card (PIC) is either not supported on this routing platform or is not supported by the installed version of the chassis process (chassisd) software. The chassisd process did not bring the PIC online. Error: An error occurred warning Contact your technical support representative.

Type Severity Action

CHASSISD_UNSUPPORTED_PIC_MODE
System Log Message Description

Application mode mode is not supported for PIC pic-slot in FPC fpc-slot The indicated Physical Interface Card (PIC) does not support the indicated application mode configured for it. Event: This message reports an event, not an error warning Check which application modes are supported for the PIC.

Type Severity Action

CHASSISD_UNSUPPORTED_SIB
System Log Message

SIB with assembly ID assembly-id is not supported

CHASSISD_UNSUPPORTED_MODEL

209

JUNOS 10.1 System Log Messages Reference

Description

The chassis process (chassisd) detected the presence of a new Switch Interface Board (SIB) with the indicated assembly ID. The SIB remains offline, because it is not a supported type. Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_VERSION_MISMATCH
System Log Message

Version mismatch: chassisd message version expected-value fru-name fru-slot message version received-value local IPC version local-ipc-version remote IPC version remote-ipc-version 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. Error: An error occurred error Either a previous software upgrade did not complete successfully, or the chassisd process or FRU did not restart after a successful software upgrade. Upgrade the software and reboot the routing platform.

Description

Type Severity Cause

Action

CHASSISD_VOLTAGE_READ_FAILED
System Log Message

Unable to read voltage from fru-name (group group-id, address address, channel voltage-channel) The chassis process (chassisd) could not read voltage data from the indicated component (field-replaceable unit, or FRU). Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

CHASSISD_VOLTAGE_SENSOR_INIT
System Log Message

Unable to initialize voltage sensor for fru-name (group group-id, address address)

210

CHASSISD_UNSUPPORTED_SIB

Chapter 17: CHASSISD System Log Messages

Description

The chassis process (chassisd) could not initialize the voltage sensor for the indicated component (field-replaceable unit, for FRU). Error: An error occurred error Contact your technical support representative.

Type Severity Action

CHASSISD_VOLTAGE_SENSOR_INIT

211

JUNOS 10.1 System Log Messages Reference

212

CHASSISD_VOLTAGE_SENSOR_INIT

Chapter 18

CONNECTION System Log Messages

This chapter describes messages with the CONNECTION prefix. They are generated whenever the alarm process is unable to connect to another process.

CONNECTION_CHASSISD_FAIL
System Log Message Description Type Severity

after count attempts chassisd connect returned error: error-message The alarm process (alarmd) was unable to connect to the chassis process (chassisd). Error: An error occurred error

CONNECTION_CRAFTD_FAIL
System Log Message Description Type Severity

after count attempts craftd connect returned error: error-message The alarm process (alarmd) was unable to connect to the craft process (craftd). Error: An error occurred error

CONNECTION_RTLOGD_FAIL
System Log Message Description

after count attempts rtlogd connect returned error: error-message The alarm process (alarmd) was unable to connect to the JUNOS J Series Services Router (JSR) log process (rtlogd). Error: An error occurred error

Type Severity

CONNECTION_CHASSISD_FAIL

213

JUNOS 10.1 System Log Messages Reference

CONNECTION_SEND_ERROR
System Log Message Description Type Severity

alarmd_send_msg: ipc_msg_write failed: error-message. The alarm process (alarmd) received an error while it was trying to send a message. Error: An error occurred error

214

CONNECTION_SEND_ERROR

Chapter 19

CONTENT System Log Messages

This chapter describes messages with the CONTENT prefix. They are generated by the content filtering process (contentd) which filters certain types of traffic based on the type, file extension, and protocol command. The content filter controls file transfers across the gateway by checking traffic against configured filter lists.

CONTENT_FILTERING_BLOCKED
System Log Message Description Type Severity Cause Action

Content Filtering: argument (profile-name) from source-address is action due to reason The transaction is blocked due to content filtering setting Event: This message reports an event, not an error info The transaction is in content filtering's block list Check the transaction to make sure it is not a false positive

CONTENT_FILTERING_BLOCKED_MT
System Log Message Description Type Severity Cause Action

Content Filtering: argument (profile-name) from source-address is action due to reason The transaction is blocked due to content filtering setting Event: This message reports an event, not an error info The transaction is in content filtering's block list Check the transaction to make sure it is not a false positive

CONTENT_FILTERING_BLOCKED

215

JUNOS 10.1 System Log Messages Reference

216

CONTENT_FILTERING_BLOCKED_MT

Chapter 20

COSD System Log Messages

This chapter describes messages with the COSD prefix. They are generated by the class-of-service (CoS) process (cosd), which enables the routing platform to provide different levels of service to applications based on packet classifications.

COSD_AGGR_CONFIG_INVALID
System Log Message Description

Error: Cannot have config error-message interface-name The class-of-service (CoS) process (cosd) did not apply the config on this interface because it was not valid in this case Error: An error occurred error One possible cause is if any Class-of-Service is configured on an interface which is a part of an aggregated interface Remove/change the config from/on the interface.

Type Severity Cause

Action

COSD_CHASSIS_SCHED_MAP_INVALID
System Log Message Description

Chassis scheduler map incorrectly applied to interface interface-name: error-message The class-of-service (CoS) process (cosd) did not apply a chassis scheduler map to the indicated interface, because the configuration used to apply the scheduler map was invalid. Error: An error occurred error One possible cause is that the chassis scheduler map is applied to a specific interface. For most interface types, a scheduler map must be applied to all interfaces on the Physical Interface Card (PIC); therefore, a wildcard must be used to specify the interfaces. One exception to this rule is the Gigabit Ethernet IQ PIC.

Type Severity Cause

COSD_AGGR_CONFIG_INVALID

217

JUNOS 10.1 System Log Messages Reference

Action

Correct the configuration used to apply the chassis scheduler map to the interface.

COSD_CLASSIFIER_NO_SUPPORT_LSI
System Log Message Description

Cannot support classifier type classifier-type on lsi interface interface-name The Differentiated Services code point (DSCP) classifier and the 802.1p classifier are only supported on I-Chip based Flexible PIC Concentrators (FPCs). Error: An error occurred error Remove the DSCP or the 802.1p classifier configuration from the routing-instance

Type Severity Action

COSD_CONF_OPEN_FAILURE
System Log Message

Unable to open: filename, using default CoS forwarding classes, do 'commit full' in cli to avoid this message The class-of-service (CoS) process (cosd) could not read configuration data. Error: An error occurred error All of the following:mgd -I fails after upgrade (cosd.conf does not exist and is not created because of the mgd -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') Do a 'commit full'

Description Type Severity Cause

Action

COSD_DB_OPEN_FAILED
System Log Message Description

Unable to open configuration database: error-message The class-of-service (CoS) process (cosd) could not read configuration data for the indicated reason. Error: An error occurred error An internal software failure occurred.

Type Severity Cause

218

COSD_CHASSIS_SCHED_MAP_INVALID

Chapter 20: COSD System Log Messages

Action

Contact your technical support representative.

COSD_EXACT_RATE_UNSUPP_INTERFACE
System Log Message

Unable to apply scheduler map scheduler-map to interface interface-name because it does not support exact-rate transmission The class-of-service (CoS) process (cosd) did not apply the indicated scheduler map to the indicated interface, because a scheduler named in the scheduler map specifies exact transmission rate. The interface is housed on a type of Physical Interface Card (PIC) that does not support exact transmission rate, such as an IQ2 PIC. In terms of configuration, the 'exact' statement is included in the scheduler definition at the [edit class-of-service schedulers <scheduler-name> transmit-rate (<rate> | percent <percentage>)] hierarchy level. The scheduler is included in the scheduler map that is applied to the interface. Error: An error occurred error Remove the 'exact' statement from the scheduler in the scheduler map applied to the interface.

Description

Type Severity Action

COSD_EXACT_RATE_UNSUPP_SESSION
System Log Message

Unable to apply CoS to L2TP session session-id, because scheduler map scheduler-map specifies exact rate transmission The class-of-service (CoS) process (cosd) did not apply CoS settings to the indicated Layer 2 Tunneling Protocol (L2TP) session, because the scheduler map specified by the RADIUS server for the session is configured for exact transmission rate. Exact transmission rate is not supported for L2TP sessions on the type of Physical Interface Card (PIC) that houses the interface, such as an IQ2 PIC. In terms of configuration, the 'exact' statement is included in a scheduler definition at the [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 by an attribute in the RADIUS server's configuration file, which makes the profile apply to the session. Error: An error occurred error Remove the 'exact' statement from the scheduler in the scheduler map applied to the session.

Description

Type Severity Action

COSD_DB_OPEN_FAILED

219

JUNOS 10.1 System Log Messages Reference

COSD_FRAGMENTATION_MAP_CONFLICT
System Log Message

Interface compression-device matches wildcard wildcard-interface-name, but fragmentation map fragmentation-map was not applied because interface is compression device for link interface link-interface-name The indicated fragmentation map is normally applied to interfaces that match the indicated wildcard. 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 interface is acting as a compression device for the indicated link interface. Error: An error occurred warning Correct the configuration of the fragmentation map.

Description

Type Severity Action

COSD_HIGH_PRIO_QUEUES_INTERFACE
System Log Message

Unable to apply scheduler map scheduler-map to interface interface-name, because multiple schedulers in map have "high,""medium-high," or "strict-high" priority The class-of-service (CoS) process (cosd) did not apply the indicated scheduler map to the indicated interface, because the map includes more than one scheduler that has high, medium-high, or strict-high priority. For interfaces that are housed by certain Physical Interface Cards (PICs), such as an IQ2 PIC, the scheduler map can include only one scheduler that specifies one of those three priority levels. In terms of configuration, the 'priority' statement at the [edit class-of-service schedulers <scheduler-name>] hierarchy level has the value 'high, ' 'medium-high, ' or 'strict-high' for more than one of the schedulers in the map. Error: An error occurred error Correct the configuration so that the scheduler map includes only one scheduler with high, medium-high, or strict-high priority.

Description

Type Severity Action

COSD_HIGH_PRIO_QUEUES_SESSION
System Log Message

Unable to apply CoS to L2TP session session-id, because multiple schedulers in scheduler map scheduler-map have "high,""medium-high," or "strict-high" priority The class-of-service (CoS) process (cosd) did not apply CoS settings to the indicated Layer 2 Tunneling Protocol (L2TP) session, because the scheduler map specified by the RADIUS server for the session includes more than one scheduler that has high, medium-high, or strict-high priority. For interfaces that are housed by certain Physical Interface Cards (PICs), such as an IQ2 PIC, the scheduler map can include only one

Description

220

COSD_FRAGMENTATION_MAP_CONFLICT

Chapter 20: COSD System Log Messages

scheduler that specifies one of those three priority levels. In terms of configuration, the 'priority' statement at the [edit class-of-service schedulers <scheduler-name>] hierarchy level has the value 'high, ' 'medium-high, ' or 'strict-high' for more than one of the schedulers in the map. The map is associated with a traffic control profile that is named by an attribute in the RADIUS server's configuration file, which makes the profile apply to the session.
Type Severity Action

Error: An error occurred error Correct the configuration so that the scheduler map includes only one scheduler with high, medium-high, or strict-high priority.

COSD_HWDB_OPEN_FAILED
System Log Message Description

Unable to open chassis hardware database: error-message The class-of-service (CoS) process (cosd) encountered the indicated error while opening the chassis hardware database. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

COSD_IFD_OUTPUT_SHAPING_RATE_ERR
System Log Message Description

Traffic shaping not supported on interface device interface-name The class-of-service (CoS) process (cosd) did not apply the shaping rate that is configured for the indicated interface. Error: An error occurred error Shaping rate is valid only for interfaces housed by IQ and IQ2 Physical Interface Cards (PICs), and the interface is on a different type of PIC. Remove the shaping rate configuration from the interface.

Type Severity Cause

Action

COSD_HIGH_PRIO_QUEUES_SESSION

221

JUNOS 10.1 System Log Messages Reference

COSD_IFD_SHAPER_ERR
System Log Message Description

port shaper not allowed on interface interface-name The non-queuing dense port concentrators (DPCs) did not support the specified shaping rate. Error: An error occurred error The port shaper was not supported on the non-queuing DPCs. Remove the shaping rate configuration from the interface.

Type Severity Cause Action

COSD_INTERFACE_NO_MEDIA
System Log Message Description

Unable to obtain media information for interface interface-name The message sent by the kernel for the indicated interface did not include required media information. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

COSD_L2TP_COS_NOT_CONFIGURED
System Log Message

Unable to apply CoS to L2TP session session-id because session-aware CoS is not enabled for interface interface-name The class-of-service (CoS) process (cosd) did not apply CoS settings to the indicated Layer 2 Tunneling Protocol (L2TP) session on the indicated interface, because the interface is not configured to support session-aware 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. Error: An error occurred error Include the 'per-session-scheduler' statement in the configuration for the interface.

Description

Type Severity Action

222

COSD_IFD_SHAPER_ERR

Chapter 20: COSD System Log Messages

COSD_L2TP_COS_NOT_SUPPORTED
System Log Message

Unable to apply CoS to L2TP session session-id on interface interface-name: it does not support CoS The class-of-service (CoS) process (cosd) did not apply CoS settings to the indicated Layer 2 Tunneling Protocol (L2TP) session on the indicated interface. The interface is configured to support session-aware CoS for L2TP, but is not on a Physical Interface Card (PIC) that supports that feature, such as an IQ2 PIC. In terms of configuration, the 'per-session-scheduler' statement is included at the [edit interfaces <interface-name> unit <logical-unit-number>] hierarchy level. Error: An error occurred error Determine whether the interface is on an PIC that supports session-aware CoS; if not, remove the 'per-session-scheduler' statement.

Description

Type Severity Action

COSD_L2TP_SHAPING_NOT_CONFIGURED
System Log Message

Unable to apply CoS to L2TP session session-id because session-aware shaping is not enabled for interface interface-name The class-of-service (CoS) process (cosd) did not apply CoS settings to the indicated Layer 2 Tunneling Protocol (L2TP) session on the indicated interface, because session-aware traffic shaping for L2TP is not configured on the Physical Interface Card (PIC) that houses the interface. In terms of configuration, the 'session-shaping' statement is not included at the [edit chassis fpc <slot-number> pic <pic-number> traffic-manager mode] hierarchy level. Error: An error occurred error Include the 'session-shaping' statement in the configuration for the PIC.

Description

Type Severity Action

COSD_LARGE_DELAY_BUFFER_INVALID
System Log Message Description

Error for interface interface-name error-message The class-of-service (CoS) process (cosd) did not apply the large delay buffer setting that is configured for the indicated interface. Error: An error occurred error

Type Severity

COSD_L2TP_COS_NOT_SUPPORTED

223

JUNOS 10.1 System Log Messages Reference

Cause

The interface is not housed on one of the Physical Interface Card (PIC) types that supports large delay buffer. Remove the large delay buffer configuration from the interface.

Action

COSD_MALLOC_FAILED
System Log Message Description

malloc failed: error-message The class-of-service (CoS) process (cosd) could not dynamically allocate memory, for the indicated reason. Error: An error occurred error A software bug caused a memory leak, or the Routing Engine did not have sufficient memory. Contact your technical support representative.

Type Severity Cause

Action

COSD_MPLS_DSCP_CLASS_NO_SUPPORT
System Log Message Description

Cannot support MPLS DSCP classifier on ifl interface-name The MPLS Differentiated Services code point (DSCP) classifier is only supported on I-Chip based Flexible PIC Concentrators (FPCs). It is not supported on Q2 PICs. Error: An error occurred error Remove the MPLS DSCP classifier configuration from the logical interface.

Type Severity Action

COSD_MULTILINK_CLASS_CONFLICT
System Log Message

Fragmentation map fragmentation-map for wildcard wildcard-interface-name specified multilink class class-name for queue queue-number on interface interface-name, which exceeds configured limit of limit The indicated fragmentation map is normally applied to interfaces that match the indicated wildcard, and specifies the indicated multilink class setting for queues on those interfaces. 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.

Description

224

COSD_LARGE_DELAY_BUFFER_INVALID

Chapter 20: COSD System Log Messages

Type Severity Action

Error: An error occurred warning Correct the configuration so that the multilink class setting in the fragmentation map does not exceed the class limit for the interface.

COSD_NULL_INPUT_ARGUMENT
System Log Message Description Type Severity Action

NULL input argument : error-message The pointer that was passed to this function was NULL. Error: An error occurred error Contact your technical support representative.

COSD_RATE_LIMIT_INVALID
System Log Message

Unable to apply scheduler map scheduler-map to interface interface-name because it does not support either configured number of rate limiting queues or rate limited queue priority or rate limited queues and buffer size The class-of-service (CoS) process (cosd) did not apply the indicated scheduler map to the indicated interface, because the number of rate limited queues in the scheduler map exceeded the limit supported by this interface or the priority is not supported. The interface is housed in a type of Physical Interface Card (PIC) that does not support the number of configured rate limited queues or the priority is not supported. In terms of configuration, the 'rate-limit' statement is included in the scheduler definition at the [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. Error: An error occurred error Either limit the number of rate-limited schedulers in this scheduler map to the allowed maximum for this PIC and interface type or check the allowed priority for rate-limited queues

Description

Type Severity Action

COSD_RATE_LIMIT_NOT_SUPPORTED
System Log Message

Unable to apply scheduler map scheduler-map to interface interface-name because it does not support rate limiting

COSD_MULTILINK_CLASS_CONFLICT

225

JUNOS 10.1 System Log Messages Reference

Description

The class-of-service (CoS) process (cosd) did not apply the indicated scheduler map to the indicated interface, because a scheduler named in the scheduler map is configured for rate limiting. The interface is housed in a type of Physical Interface Card (PIC) that does not support rate limiting. In terms of configuration, the 'rate-limit' statement is included in the scheduler definition at the [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. Error: An error occurred error Remove the 'rate-limit' statement from the scheduler in the scheduler map applied to the interface.

Type Severity Action

COSD_REWRITE_RULE_LIMIT_EXCEEDED
System Log Message

Number of rewrite rules applied to interface interface-name exceeds limit (maximum-value) The class-of-service (CoS) process (cosd) determined that the number of rewrite rules applied to the indicated interface exceeds the indicated limit for the interface. In terms of configuration, too many rewrite rules are included at the [edit class-of-service interfaces <interface-name> unit <logical-unit-number> rewrite-rules] hierarchy level. Error: An error occurred error Remove rewrite rules from the configuration for the interface.

Description

Type Severity Action

COSD_SCHEDULER_MAP_CONFLICT
System Log Message

Forwarding classes "first-forwarding-class" and "second-forwarding-class" in scheduler map scheduler-map both map to queue queue-number Both of the indicated forwarding classes, which are defined in the indicated scheduler map, map to the same indicated queue. The double mapping is invalid. Error: An error occurred error Map only one forwarding class to the queue.

Description

Type Severity Action

226

COSD_RATE_LIMIT_NOT_SUPPORTED

Chapter 20: COSD System Log Messages

COSD_STREAM_IFD_CREATE_FAILURE
System Log Message Description

Unable to create special master interface device for interface-name The class-of-service (CoS) process (cosd) could not create the indicated internal interface device, which it needs for application of a chassis scheduler map. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

COSD_TIMER_ERROR
System Log Message Description

Unable to set retry timer for rtsock write operation: error-message The class-of-service (CoS) process (cosd) used a routine from the rtsock library to write to the kernel, but the kernel did not accept the request. The cosd process could not set the retry timer for the request, for the indicated reason. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

COSD_TRICOLOR_NOT_SUPPORTED
System Log Message

Unable to apply scheduler scheduler-map to interface interface-name, because it does not support tricolor marking The class-of-service (CoS) process (cosd) did not apply the indicated scheduler map to the indicated interface, because a scheduler included in the map specifies a packet loss priority (PLP) that is supported only with tricolor marking (TCM). The interface does not support TCM, either because TCM is not enabled or the interface is on a router that does not support TCM. In terms of configuration, the value 'medium-high' or 'medium-low' is specified for the 'loss-priority' statement in a scheduler definition at the [edit class-of-service schedulers <scheduler-name> drop-profile-map] hierarchy level. The scheduler is included in the scheduler map applied to the interface, but the 'tri-color' statement is either not included at the [edit class-of-service] hierarchy level, or is not supported.

Description

COSD_STREAM_IFD_CREATE_FAILURE

227

JUNOS 10.1 System Log Messages Reference

Type Severity Action

Error: An error occurred error Change the value of the 'loss-priority' statement in the scheduler or include the 'tri-color' statement to enable TCM on the router.

COSD_TX_QUEUE_RATES_TOO_HIGH
System Log Message

Unable to apply scheduler map scheduler-map to interface interface-name: sum of scheduler transmission rates exceeds interface shaping or transmission rate The class-of-service (CoS) process (cosd) did not apply the indicated scheduler map to the indicated interface, because the sum of the queue transmission rates defined in the schedulers in the scheduler map exceeds the shaping or transmission rate for the interface. In terms of configuration, the 'transmit-rate' statement is specified for each scheduler at the [edit class-of-service schedulers <scheduler-name>] hierarchy level. The sum of the configured transmission rates exceeds the transmission or shaping rate of the interface. Error: An error occurred error Decrease the value of one or more 'transmit-rate' statements so that the sum is less than the interface transmission or shaping rate.

Description

Type Severity Action

COSD_UNKNOWN_CLASSIFIER
System Log Message Description

classifier type classifier-type is invalid The class-of-service (CoS) process (cosd) did not recognize the indicated classifier type from the rtsock library. Error: An error occurred warning An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

COSD_UNKNOWN_REWRITE
System Log Message Description

rtsock rewrite type type is invalid The class-of-service (CoS) process (cosd) did not recognize the indicated rewrite type from the rtsock library.

228

COSD_TRICOLOR_NOT_SUPPORTED

Chapter 20: COSD System Log Messages

Type Severity Cause Action

Error: An error occurred warning An internal software failure occurred. Contact your technical support representative.

COSD_UNKNOWN_TRANSLATION_TABLE
System Log Message Description

rtsock translation table type translation-table-type is invalid The class-of-service (CoS) process (cosd) did not recognize the indicated translation table type from the rtsock library. Error: An error occurred warning An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

COSD_UNKNOWN_REWRITE

229

JUNOS 10.1 System Log Messages Reference

230

COSD_UNKNOWN_TRANSLATION_TABLE

Chapter 21

DCD System Log Messages

This chapter describes messages with the DCD prefix. They are generated by the interface process (dcd), which controls the physical interface devices and logical interfaces in the routing platform.

DCD_GRE_CONFIG_INVALID
System Log Message

Either tunnel key or clear-dont-fragment-bit must be configured for this GRE tunnel (interface-name), to enable post fragmentation You must configure either the tunnel key or the clear-don't-fragment bit (along with the allow-fragmentation bit) for this interface. Error: An error occurred error Configure either the tunnel key or the clear-dont-fragment-bit for this tunnel

Description

Type Severity Action

DCD_MALLOC_FAILED_INIT
System Log Message Description

Memory allocation failed during initialization for configuration load The interface process (dcd) could not dynamically allocate memory in preparation for loading a configuration. Error: An error occurred error A software bug caused a memory leak, or the routing platform had insufficient memory. Contact your technical support representative.

Type Severity Cause

Action

DCD_GRE_CONFIG_INVALID

231

JUNOS 10.1 System Log Messages Reference

DCD_PARSE_EMERGENCY
System Log Message Description

dcd_config: errors while parsing configuration file The interface process (dcd) encountered an unhandled internal state while parsing the configuration database. Error: An error occurred error There might be a bug in the dcd process' parser. Contact your technical support representative.

Type Severity Cause Action

DCD_PARSE_ERROR_CLOCK
System Log Message Description

PIC housing interface interface-name does not support clocking as configured The 'clocking' statement is included at the [edit interfaces] hierarchy level for the indicated interface, but is not supported by the 10-Gigabit Ethernet IQ2 Physical Interface Card (PIC). Error: An error occurred warning Remove the 'clocking' statement from the configuration for the interface.

Type Severity Action

DCD_PARSE_ERROR_HIER_SCHEDULER
System Log Message

interface-name: PIC or encapsulation type does not support 'hierarchical-scheduler' statement 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. Error: An error occurred warning Remove the 'hierarchical-scheduler' statement from the configuration for the interface.

Description

Type Severity Action

232

DCD_PARSE_EMERGENCY

Chapter 21: DCD System Log Messages

DCD_PARSE_ERROR_IFLSET
System Log Message Description

Interface interface-name does not support 'interface-set' statement The 'interface-set' statement is included at the [edit interfaces] hierarchy level for the indicated interface, but is not supported by the interface. Error: An error occurred warning Remove the 'interface-set' statement from the configuration for the interface.

Type Severity Action

DCD_PARSE_ERROR_MAX_HIER_LEVELS
System Log Message

interface-name: PIC or encapsulation type does not support 'maximum-hierarchy-levels' statement Neither the PIC nor the configured type of encapsulation supports the hierarchial-scheduler maximum-hierarchy-levels statement at the [edit interfaces] hierarchy level. Error: An error occurred warning Remove the 'hierarchical-scheduler maximum-hierarchy-levels' statement from the configuration for the interface.

Description

Type Severity Action

DCD_PARSE_ERROR_SCHEDULER
System Log Message

interface-name: PIC or encapsulation type does not support 'per-unit-scheduler' or 'shared-scheduler' statement The 'per-unit-scheduler' or 'shared-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. Error: An error occurred warning Remove the 'per-unit-scheduler' or 'shared-scheduler' statement from the configuration for the interface.

Description

Type Severity Action

DCD_PARSE_ERROR_IFLSET

233

JUNOS 10.1 System Log Messages Reference

DCD_PARSE_ERROR_SCHEDULER_LIMIT
System Log Message

interface-name: exceeds the allowed limit (maximum-value) of 'per-unit-scheduler' interface statement for PIC=pic-slot on FPC=fpc-slot The 'per-unit-scheduler' statement is enabled on more interfaces than what this PIC would suppport. Error: An error occurred warning Remove the 'per-unit-scheduler' statement from the configuration for the interface.

Description

Type Severity Action

DCD_PARSE_ERROR_VLAN_TAGGING
System Log Message Description

interface-name: PIC type does not support flexible-vlan-tagging statement The 'flexible-vlan-tagging' statement is included at the [edit interfaces] hierarchy level for the indicated interface, but is not supported by the Physical Interface Card (PIC) that houses the interface. Error: An error occurred warning Remove the 'flexible-vlan-tagging' statement from the configuration for the interface.

Type Severity Action

DCD_PARSE_ERR_INCOMPATIBLE_CFG
System Log Message Description

Incompatible configuration detected warning-message The interface process (dcd) found a configuration that will no longer be supported in future releases. Error: An error occurred warning This is a warning that this configuration will not be supported in future releases. Contact your technical support representative.

Type Severity Cause Action

DCD_PARSE_MINI_EMERGENCY
System Log Message

dcd_mini_config: errors while parsing configuration overlay

234

DCD_PARSE_ERROR_SCHEDULER_LIMIT

Chapter 21: DCD System Log Messages

Description

The interface process (dcd) encountered an unhandled internal state during interface parsing. Error: An error occurred error There might be a bug in the dcd process' parser. Contact your technical support representative.

Type Severity Cause Action

DCD_PARSE_STATE_EMERGENCY
System Log Message Description

An unhandled state was encountered during interface parsing The interface process (dcd) encountered an unhandled internal state during interface parsing. Error: An error occurred emergency There might be a bug in the dcd process' parser. Contact your technical support representative.

Type Severity Cause Action

DCD_PARSE_MINI_EMERGENCY

235

JUNOS 10.1 System Log Messages Reference

236

DCD_PARSE_STATE_EMERGENCY

Chapter 22

DFCD System Log Messages

This chapter describes messages with the DFCD prefix. They are generated by the dynamic flow control process (dfcd), which monitors packet flows using dynamically alterable filtering criteria.

DFCD_FTAP_PIC_UNSUPPORTED
System Log Message Description

PIC housing interface interface-name does not support flow-tap service The Physical Interface Card (PIC) that houses the indicated interface does not support flow-tap service. Error: An error occurred error

Type Severity

DFCD_GENCFG_MALLOC_FAILED
System Log Message Description

GENCFG mem alloc failed !!! The dynamic flow capture process (dfcd) could not allocate memory for gencfg message. Error: An error occurred error

Type Severity

DFCD_GENCFG_WRITE_FAILED
System Log Message Description

GENCFG write failed for Reason: error-message (error-code) The dynamic flow capture process (dfcd) could not send gencfg message, for the indicated reason. Error: An error occurred error

Type Severity

DFCD_FTAP_PIC_UNSUPPORTED

237

JUNOS 10.1 System Log Messages Reference

DFCD_LINH_MALLOC_FAILED
System Log Message Description Type Severity

GENCFG mem alloc failed !!! The dynamic flow capture process (dfcd) could not allocate memory for linh message. Error: An error occurred error

DFCD_LI_NEXT_HOP_ADD_FAILED
System Log Message Description

Unable to add li next hop for subscriber interface: error-message (error-code) The dynamic flow capture process (dfcd) could not add a subscriber li next hop, for the indicated reason. Error: An error occurred error

Type Severity

DFCD_NEXT_HOP_ADD_FAILED
System Log Message Description

Unable to add service next hop: error-message (error-code) The dynamic flow capture process (dfcd) could not add a service next hop, for the indicated reason. Error: An error occurred error

Type Severity

DFCD_NEXT_HOP_DELETE_FAILED
System Log Message Description

Unable to delete service next hop: error-message (error-code) The dynamic flow capture process (dfcd) could not delete a service next hop, for the indicated reason. Error: An error occurred error

Type Severity

DFCD_SAMPLE_CLASS_ADD_FAILED
System Log Message

Unable to add sample class: error-message (error-code)

238

DFCD_LINH_MALLOC_FAILED

Chapter 22: DFCD System Log Messages

Description

The dynamic flow capture process (dfcd) could not add a sample class, for the indicated reason. Error: An error occurred error

Type Severity

DFCD_SAMPLE_CLASS_DELETE_FAILED
System Log Message Description

Unable to delete sample class: error-message (error-code) The dynamic flow capture process (dfcd) could not delete a sample class, for the indicated reason. Error: An error occurred error

Type Severity

DFCD_SAMPLE_CLASS_ADD_FAILED

239

JUNOS 10.1 System Log Messages Reference

240

DFCD_SAMPLE_CLASS_DELETE_FAILED

Chapter 23

DFWD System Log Messages

This chapter describes messages with the DFWD prefix. They are generated by the firewall process (dfwd), which manages compilation and downloading of JUNOS firewall filters.

DFWD_MALLOC_FAILED_INIT
System Log Message Description

Memory allocation failed during initialization for configuration load The firewall process (dfwd) could not dynamically allocate memory in preparation for loading a configuration. Error: An error occurred error A software bug caused a memory leak, or the routing platform had insufficient memory. Contact your technical support representative.

Type Severity Cause

Action

DFWD_PARSE_FILTER_EMERGENCY
System Log Message Description

dfwd encountered errors while parsing filter index file The firewall process (dfwd) encountered an unhandled internal state while parsing a filter index file. Error: An error occurred error There might be a bug in the parser. Contact your technical support representative.

Type Severity Cause Action

DFWD_MALLOC_FAILED_INIT

241

JUNOS 10.1 System Log Messages Reference

DFWD_PARSE_STATE_EMERGENCY
System Log Message Description

dfwd encountered unhandled state while parsing interface The firewall process (dfwd) encountered an unhandled internal state while parsing an interface. Error: An error occurred emergency There might be a bug in the parser. Contact your technical support representative.

Type Severity Cause Action

DFWD_POLICER_LIMIT_EXCEEDED
System Log Message Description

Number of interface policers configured is exceeding maximum allowed total-count. The firewall process (dfwd) detected that number of interface policers configured is exceeding maximum allowed. Error: An error occurred error Reduce the number of interface policers to within allowed limit.

Type Severity Action

242

DFWD_PARSE_STATE_EMERGENCY

Chapter 24

DHCPD System Log Messages

This chapter describes messages with the DHCPD prefix. They are generated by the Dynamic Host Configuration Protocol (DHCP) server process (dhcpd) for J Series Services Routers, which automatically allocates network IP addresses and delivers configuration settings to client hosts in a Transmission Control Protocol (TCP)/IP network.

DHCPD_BIND_FAILURE
System Log Message Description

bind() to port port failed: error-message The Dynamic Host Configuration Protocol server process (dhcpd) received the indicated error when it tried to bind a socket to the indicated local port. Error: An error occurred error Contact your technical support representative.

Type Severity Action

DHCPD_DEGRADED_MODE
System Log Message Description

Running in degraded mode because of reason: error-message The Dynamic Host Configuration Protocol server process (dhcpd) began running in degraded mode because the indicated unrecoverable error occurred. Error: An error occurred error There might be a problem with the lease cache directory used to store persistent lease information. Contact your technical support representative.

Type Severity Cause

Action

DHCPD_BIND_FAILURE

243

JUNOS 10.1 System Log Messages Reference

DHCPD_MEMORY_ALLOCATION_FAILURE
System Log Message Description

Unable to allocate memory for object-name: error-message The Dynamic Host Configuration Protocol server process (dhcpd) could not allocate memory from the heap for the indicated object. Error: An error occurred error Contact your technical support representative.

Type Severity Action

DHCPD_OVERLAY_CONFIG_FAILURE
System Log Message Description

Unable to open overlay configuration: error-message The Dynamic Host Configuration Protocol server process (dhcpd) could not open an overlay configuration file for parsing. Error: An error occurred error Contact your technical support representative.

Type Severity Action

DHCPD_OVERLAY_PARSE_FAILURE
System Log Message Description

Unable to parse overlay configuration because of count syntax errors The Dynamic Host Configuration Protocol server process (dhcpd) could not parse its overlay configuration because the configuration contained the indicated number of syntax errors. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

DHCPD_RECVMSG_FAILURE
System Log Message

Exiting due to too many recvmsg() failures

244

DHCPD_MEMORY_ALLOCATION_FAILURE

Chapter 24: DHCPD System Log Messages

Description

The Dynamic Host Configuration Protocol server process (dhcpd) could not receive data from the network, which it needs to do during normal operation. Error: An error occurred error Contact your technical support representative.

Type Severity Action

DHCPD_RTSOCK_FAILURE
System Log Message Description

Error with rtsock: error-message The Dynamic Host Configuration Protocol server process (dhcpd) experienced the indicated error with a routing socket. Error: An error occurred info An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

DHCPD_SENDMSG_FAILURE
System Log Message

sendmsg() from source-address to port destination-port at destination-address via interface interface-name and routing instance routing-instance failed: error-message The Dynamic Host Configuration Protocol server process (dhcpd) could not send data from the indicated source (address, interface, and routing instance) to the indicated destination (port and address), which it needs to do during normal operation. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

DHCPD_SENDMSG_NOINT_FAILURE
System Log Message

sendmsg() from source-address to port destination-port at destination-address via routing instance routing-instance failed: error-message The Dynamic Host Configuration Protocol server process (dhcpd) could not send data from the indicated source (address and routing instance) to the indicated destination (port and address), which it needs to do during normal operation.

Description

DHCPD_RECVMSG_FAILURE

245

JUNOS 10.1 System Log Messages Reference

Type Severity Action

Error: An error occurred error Contact your technical support representative.

DHCPD_SETSOCKOPT_FAILURE
System Log Message Description

setsockopt(socket-option) failed: error-message The Dynamic Host Configuration Protocol server process (dhcpd) could not set the indicated socket option. Error: An error occurred error Contact your technical support representative.

Type Severity Action

DHCPD_SOCKET_FAILURE
System Log Message Description

socket(arguments) failed: error-message The Dynamic Host Configuration Protocol server process (dhcpd) could not create a socket. Error: An error occurred error Contact your technical support representative.

Type Severity Action

246

DHCPD_SENDMSG_NOINT_FAILURE

Chapter 25

DYNAMIC System Log Messages

This chapter describes messages with the DYNAMIC prefix. They are generated by the Access Manager client which is used in the dynamic VPN feature. The dynamic VPN feature further simplifies remote access by enabling users to establish Internet Protocol Security (IPsec) VPN tunnels without having to manually configure VPN settings on their PCs or laptops. Instead, authenticated users can simply download the Access Manager Web client to their computers. This Layer 3 remote access client uses client-side configuration settings that it receives from the server to create and manage a secure end-to-site VPN tunnel to the server.

DYNAMIC_VPN_AUTH_CONNECT_FAIL
System Log Message Description

Unable to connect to fwauthd on socket file-descriptor: error-message The connection manager authentication process could not connect to fwauthd daemon on the indicated socket. Event: This message reports an event, not an error error

Type Severity

DYNAMIC_VPN_AUTH_FAIL
System Log Message Description

Username/password and token are username The connection manager authentication process was unable to authenticate the indicated user/token Event: This message reports an event, not an error error

Type Severity

DYNAMIC_VPN_AUTH_INVALID
System Log Message Description

type username is invalid The connection manager authentication failed due to invalid user/token

DYNAMIC_VPN_AUTH_CONNECT_FAIL

247

JUNOS 10.1 System Log Messages Reference

Type Severity

Event: This message reports an event, not an error error

DYNAMIC_VPN_AUTH_NO_CONFIG
System Log Message Description

Authentication failed for type username due to unavailable client config The connection manager authentication process was unable to obtain client config for the indicated user/token Event: This message reports an event, not an error error

Type Severity

DYNAMIC_VPN_AUTH_NO_LICENSE
System Log Message Description

Authentication failed for type username due to unavailable license The connection manager authentication process was unable to obtain license for the indicated user/token Event: This message reports an event, not an error error

Type Severity

DYNAMIC_VPN_AUTH_OK
System Log Message Description

type username with client-name client-id authenticated successfully. The connection manager authentication process was able to authenticate the indicated user/token successfully Event: This message reports an event, not an error notice

Type Severity

DYNAMIC_VPN_CLIENT_CONFIG_WRITE
System Log Message Description Type Severity

Client VPN config is saved in file filename for user username Connection manager writes client VPN config to file before sending to client. Event: This message reports an event, not an error notice

248

DYNAMIC_VPN_AUTH_INVALID

Chapter 25: DYNAMIC System Log Messages

DYNAMIC_VPN_CONN_DEL_NOTIFY
System Log Message Description Type Severity

Connection manager receives SA deleted notification for ike-id gateway-id Connection manager receives SA deleted notification from IKED. Event: This message reports an event, not an error notice

DYNAMIC_VPN_CONN_DEL_REQUEST
System Log Message Description Type Severity

Connection manager receives delete request from the client for ike-id gateway-id Connection manager receives connection delete request from the client. Event: This message reports an event, not an error notice

DYNAMIC_VPN_CONN_EST_NOTIFY
System Log Message Description Type Severity

Connection manager receives SA established notification for ike-id gateway-id Connection manager receives SA established notification from IKED. Event: This message reports an event, not an error notice

DYNAMIC_VPN_INIT_SUCCESSFUL
System Log Message Description Type Severity

Connection manager initialization succeeded. Connection manager is initialized successfully. Event: This message reports an event, not an error notice

DYNAMIC_VPN_LICENSE_ASSIGNED
System Log Message

Dynamic VPN license granted, license limit free, count overdrafted, current-value used

DYNAMIC_VPN_CONN_DEL_NOTIFY

249

JUNOS 10.1 System Log Messages Reference

Description

The Access Manager client has successfully acquired a license and is permitted to connect to the device. Event: This message reports an event, not an error info

Type Severity

DYNAMIC_VPN_LICENSE_CHECK_FAILED
System Log Message Description Type Severity

Dynamic VPN license check failed for user username No Access Manager license is available at the moment. Error: An error occurred error

DYNAMIC_VPN_LICENSE_CHECK_OK
System Log Message Description Type Severity

Dynamic VPN license check succeed for user username Preliminary check on Access Manager license is successful for the given user. Event: This message reports an event, not an error notice

DYNAMIC_VPN_LICENSE_EXHAUSTED
System Log Message Description

Dynamic VPN license denied, no available license The device is out of Access Manager licenses. Connection request from the Access Manager client is denied. Error: An error occurred error

Type Severity

DYNAMIC_VPN_LICENSE_FREED
System Log Message

Dynamic VPN license returned, license limit free, count overdrafted, current-value used The Access Manager client has disconnected and returned its license. Event: This message reports an event, not an error info

Description Type Severity

250

DYNAMIC_VPN_LICENSE_ASSIGNED

Chapter 25: DYNAMIC System Log Messages

DYNAMIC_VPN_LICENSE_FREE_FAILED
System Log Message Description Type Severity

Server failed to free an Access Manager for username The Access Manager client attempt to return a license has failed. Event: This message reports an event, not an error error

DYNAMIC_VPN_LICENSE_FREE_OK
System Log Message Description Type Severity

Server successfully freed an Access Manager license for username The Access Manager client successfully returned a license. Event: This message reports an event, not an error notice

DYNAMIC_VPN_LICENSE_GET_FAILED
System Log Message Description Type Severity

Server failed to get an Access Manager license for username No Access Manager license is available at the moment. Event: This message reports an event, not an error error

DYNAMIC_VPN_LICENSE_GET_OK
System Log Message Description Type Severity

Server successfully got an Access Manager license for username The Access Manager client successfully obtained a license. Event: This message reports an event, not an error notice

DYNAMIC_VPN_LICENSE_INSTALLED
System Log Message Description

Dynamic VPN license name installed, license limit total, count free An Access Manager license was installed successfully on this device.

DYNAMIC_VPN_LICENSE_FREE_FAILED

251

JUNOS 10.1 System Log Messages Reference

Type Severity

Event: This message reports an event, not an error info

DYNAMIC_VPN_LICENSE_REQUIRED
System Log Message Description Type Severity

Dynamic VPN license denied, no license installed Requested operation requires an Access Manager license to be installed on this device. Error: An error occurred error

DYNAMIC_VPN_LICENSE_UNINSTALLED
System Log Message Description Type Severity

Dynamic VPN license name deleted, license limit total, count free An Access Manager license is removed from this device. Event: This message reports an event, not an error info

252

DYNAMIC_VPN_LICENSE_INSTALLED

Chapter 26

ESWD System Log Messages

This chapter describes messages with the ESWD prefix. They are generated by the ethernet bridging process (eswd).

ESWD_BPDU_BLOCK_ERROR_DISABLED
System Log Message Description Type Severity

interface-name: bpdu-block disabled port This condition occurs when bpdu-block error condition is detected. Error: An error occurred alert

ESWD_BPDU_BLOCK_ERROR_ENABLED
System Log Message Description Type Severity

interface-name: bpdu-block enabled port This condition occurs when bpdu-block error condition is cleared. Error: An error occurred alert

ESWD_DAI_FAILED
System Log Message

count type received, interface interface-name[index interface-device-index], vlan vlan-name[index vlan-id], sender ip/mac sender-address/mac1, receiver ip/mac destination-address/mac2 The ARP request/response receieved on this port cannot be linked to any of the IPs assigned by DHCP. Error: An error occurred alert

Description

Type Severity

ESWD_BPDU_BLOCK_ERROR_DISABLED

253

JUNOS 10.1 System Log Messages Reference

ESWD_DHCP_UNTRUSTED
System Log Message

count untrusted type received, interface interface-name[index interface-device-index], vlan vlan-name[index vlan-id], server ip/mac source-address/mac1, offer ip/client mac client-address/mac2 DHCP server packets are being received on a port which was not meant to receive server traffic. Error: An error occurred alert

Description

Type Severity

ESWD_INVALID_MAC_ADDRESS
System Log Message Description

Invalid MAC address mac-addresse received on interface-name Received a MAC address that is not in the configured valid MAC addresses for this interface. Error: An error occurred alert MAC address recieved is not configured as a valid MAC address for this interface.

Type Severity Cause

ESWD_MAC_LIMIT_BLOCK
System Log Message Description

MAC limit (limit) exceeded at interface-name: shutting down the interface Interface was blocked because the number of MAC addresses learned on an interface has exceeded the user configured limit. Error: An error occurred alert More learning requests were received by the system than the user configured.

Type Severity Cause

ESWD_MAC_LIMIT_DROP
System Log Message Description

MAC limit (limit) exceeded at interface-name: dropping the packet Learning request was dropped because the number of MAC addresses learned on an interface has reached the user configured limit.

254

ESWD_DHCP_UNTRUSTED

Chapter 26: ESWD System Log Messages

Type Severity Cause

Error: An error occurred alert More learning requests were received by the system than the user configured.

ESWD_MAC_LIMIT_EXCEEDED
System Log Message Description

MAC limit (limit) exceeded at interface-name Number of MAC addresses learned on an interface has exceeded the user configured limit. Error: An error occurred alert More learning requests were received by the system than the user configured.

Type Severity Cause

ESWD_MAC_MOVE_LIMIT_BLOCK
System Log Message

MAC move limit (limit) exceeded at vlan-name for MAC address mac-addresse; shutting down interface interface-name Data traffic on interface was halted because the number of times that a MAC addresses moved to a different interface exceeded the user-configured limit. Error: An error occurred alert A MAC address moved to a different interface more times per second than the user configured.

Description

Type Severity Cause

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 Learning request was dropped because the number of times a MAC address moved to a different interface exceeded the user-configured limit. Error: An error occurred alert A MAC address moved to a different interface more times per second than the user configured.

Description

Type Severity Cause

ESWD_MAC_LIMIT_DROP

255

JUNOS 10.1 System Log Messages Reference

ESWD_MAC_MOVE_LIMIT_EXCEEDED
System Log Message

MAC move limit (limit) exceeded at vlan-name for MAC address mac-addresse on interface interface-name The number of times that a MAC address moved to a different interface within a VLAN exceeded the user-configured limit. Error: An error occurred alert A MAC address moved to a different interface more times per second than the user configured.

Description

Type Severity Cause

ESWD_MIRROR_ERROR
System Log Message Description

Mirror version on other Routing Engine is incompatible: error-message The indicated error occurred when the layer2 control protocol process (l2cpd) tried to establish the nonstop routing mirror connection between the master and standby Routing Engines. Error: An error occurred warning The master and standby Routing Engines are running incompatable versions of the JUNOS software. Update the JUNOS software on the master Routing Engine, standby Routing Engine, or both, so that they are running compatible versions.

Type Severity Cause

Action

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 While trying to establish the nonstop routing mirror connection between the master and standby Routing Engines, the layer2 control protocol process (l2cpd) determined that the version of the nonstop routing mirror software on the Routing Engines did not match. Error: An error occurred warning

Description

Type Severity

256

ESWD_MAC_MOVE_LIMIT_EXCEEDED

Chapter 26: ESWD System Log Messages

Cause

The master and standby Routing Engines are running incompatable versions of the JUNOS software. Update the JUNOS software on the master Routing Engine, standby Routing Engine, or both, so that they are running compatible versions.

Action

ESWD_MODULE_SHUTDOWN_FAILURE
System Log Message Description Type Severity

ESWD: error-message Module shutdown failed While deleting the instance of logical-switch, RST/MST Module shutdown failed. Error: An error occurred error

ESWD_PPM_READ_ERROR
System Log Message Description

Read error on pipe from ppmd: reason (error-message) The ethernet bridging process (eswd) could not read a message available on the read pipe from the periodic packet management process (ppmd). Error: An error occurred error Contact your technical support representative.

Type Severity Action

ESWD_PPM_WRITE_ERROR
System Log Message Description

function-name: write error on pipe to ppmd (error-message) The ethernet bridging process (eswd) could not write a message on the pipe to the periodic packet management process (ppmd). Error: An error occurred error Contact your technical support representative.

Type Severity Action

ESWD_STP_BASE_MAC_ERROR
System Log Message Description

Failed to get error-message. All modules will remain disabled. This condition occurs when STP cannot derive the base MAC address of the system.

ESWD_MIRROR_VERSION_MISMATCH

257

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred alert

ESWD_STP_LOOP_PROTECT_CLEARED
System Log Message Description Type Severity

interface-name: loop protect cleared for instance instance-id This condition occurs when STP loop protect condition is cleared. Error: An error occurred alert

ESWD_STP_LOOP_PROTECT_IN_EFFECT
System Log Message Description Type Severity

interface-name: loop protect in effect for instance instance-id This condition occurs when STP loop protect condition occurs. Error: An error occurred alert

ESWD_STP_ROOT_PROTECT_CLEARED
System Log Message Description Type Severity

interface-name: root protect cleared for instance instance-id This condition occurs when STP root protect condition is cleared. Error: An error occurred alert

ESWD_STP_ROOT_PROTECT_IN_EFFECT
System Log Message Description Type Severity

interface-name: root protect in effect for instance instance-id This condition occurs when STP root protect condition occurs. Error: An error occurred alert

258

ESWD_STP_BASE_MAC_ERROR

Chapter 26: ESWD System Log Messages

ESWD_ST_CTL_BW_INFO
System Log Message

interface-name: configured storm control speed level is greater than interface speed bandwidth. Storm control will be set to the latter Log message to alert the user to the bandwidth setting limits. Error: An error occurred alert

Description Type Severity

ESWD_ST_CTL_ERROR_DISABLED
System Log Message Description Type Severity

interface-name: storm control disabled port This condition occurs when storm control error condition is detected. Error: An error occurred alert

ESWD_ST_CTL_ERROR_ENABLED
System Log Message Description Type Severity

interface-name: storm control enabled port This condition occurs when storm-control error condition is cleared. Error: An error occurred alert

ESWD_ST_CTL_INFO
System Log Message Description Type Severity

interface-name: storm control will default to 80 percent of link speed Log message to alert the user to the storm control setting. Error: An error occurred alert

ESWD_SYSTEM_CALL_FAILED
System Log Message Description

reason: error-message A system call made by enterprise switching process (eswd) failed.

ESWD_ST_CTL_BW_INFO

259

JUNOS 10.1 System Log Messages Reference

Type Severity Cause

Error: An error occurred error It is possible that the kernel lacked the resources to fulfill the request.

260

ESWD_SYSTEM_CALL_FAILED

Chapter 27

EVENTD System Log Messages

This chapter describes messages with the EVENTD prefix. They are generated by the event policy process (eventd), which performs configured actions in response to events on a routing platform that trigger system log messages.

EVENTD_ACK_FAILED
System Log Message Description

Unable to send acknowledgment: error-message JUNOS processes can request that the event processing process (eventd) notify them when a specific event occurs. The eventd process could not send an acknowledgment for a registration request, for the indicated reason. Error: An error occurred error

Type Severity

EVENTD_ALARM_CLEAR
System Log Message Description Type Severity

User username cleared alarm: "timestamp: message" An administrator has acknowledged and cleared a security alarm. Event: This message reports an event, not an error notice

EVENTD_COMMAND_SUBSTITUTE_ERROR
System Log Message Description

Variable substitution failed for command 'command' The event processing process (eventd) can be configured to execute a JUNOS command-line interface (CLI) command when a specified event occurs. The command can include one or more variables (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. Error: An error occurred

Type

EVENTD_ACK_FAILED

261

JUNOS 10.1 System Log Messages Reference

Severity Cause

error An internal software failure occurred.

EVENTD_ESCRIPT_EXECUTION
System Log Message Description

Trying to execute the script 'filename' from 'directory-name' The event process (eventd) executing the configured event script from the specified location. Event: This message reports an event, not an error info

Type Severity

EVENTD_EVENT_SEND_FAILED
System Log Message Description

Unable to send event notification: error-message JUNOS processes can request that the event processing process (eventd) notify them when a specific event occurs. The eventd process could not send an event notification for the indicated reason. Error: An error occurred error

Type Severity

EVENTD_FORK_ERR
System Log Message Description

Unable to fork: error-message The event processing process (eventd) could not create a child process for executing policies. Error: An error occurred error

Type Severity

EVENTD_PIPE_CREATION_FAILED
System Log Message Description

Unable to create pipe: error-message The event processing process (eventd) could not create a pipe for interprocess communication. Error: An error occurred error

Type Severity

262

EVENTD_COMMAND_SUBSTITUTE_ERROR

Chapter 27: EVENTD System Log Messages

EVENTD_POLICY_ACTION_FAILED
System Log Message Description

Unable to execute 'action' action in policy policy-name The event processing process (eventd) could not perform the indicated action, which is specified by the indicated policy. Error: An error occurred error

Type Severity

EVENTD_POLICY_LIMIT_EXCEEDED
System Log Message

Unable to execute policy 'policy-name' because current number of policies (count) exceeds system limit (limit) The event processing process (eventd) could not execute the indicated policy, because the indicated number of currently executing policies exceeded the indicated maximum defined by the system. Event: This message reports an event, not an error warning

Description

Type Severity

EVENTD_POLICY_UPLOAD_FAILED
System Log Message

Unable to upload file 'filename' to destination 'destination-name' for policy 'policy-name' The event processing process (eventd) could not upload the indicated file to the indicated destination. Error: An error occurred error

Description

Type Severity

EVENTD_POPEN_FAIL
System Log Message Description

Error error-code in invoking command 'command' A call to the popen() function failed when the event processing process (eventd) invoked the indicated command. Error: An error occurred error

Type Severity

EVENTD_POLICY_ACTION_FAILED

263

JUNOS 10.1 System Log Messages Reference

EVENTD_READ_ERROR
System Log Message Description

recvmsg() failed: error-message The event processing process (eventd) could not read an event sent to it, for the indicated reason. Error: An error occurred error

Type Severity

EVENTD_REGEXP_INVALID
System Log Message Description

Invalid regular expression 'regular-expression' provided for attribute value The event processing process (eventd) received a request that included the indicated regular expression as the value for an attribute. The regular expression is not valid. Error: An error occurred error

Type Severity

EVENTD_REG_VERSION_MISMATCH
System Log Message Description

Registration version expected-value did not match expected version (received-value) The event processing process (eventd) received a registration request with the indicated version indicator, which does not match the indicated version expected by the eventd process. Error: An error occurred error

Type Severity

EVENTD_ROTATE_COMMAND_FAILED
System Log Message Description

Command 'command' failed during rotation of file 'filename': error-message The event processing process (eventd) invoked the indicated command while attempting to rotate the indicated file. The command failed. Error: An error occurred error

Type Severity

264

EVENTD_READ_ERROR

Chapter 27: EVENTD System Log Messages

EVENTD_ROTATE_FORK_EXCEEDED
System Log Message Description

Unable to fork: too many child processes The event processing process (eventd) could not create a child process for rotating files because adding another child would have made the number of children exceed the limit. Error: An error occurred error

Type Severity

EVENTD_ROTATE_FORK_FAILED
System Log Message Description

Unable to fork: error-message The event processing process (eventd) could not create a child process for rotating files, for the indicated reason. Error: An error occurred error

Type Severity

EVENTD_SCRIPT_CHECKSUM_MISMATCH
System Log Message Description

checksum checksum value does not match for script filename Current checksum value of the script does not match with the checksum configured under [event-options event-script] hierarchy. As a result any event-policy configured inside the script will not be read Error: An error occurred error

Type Severity

EVENTD_SET_PROCESS_PRIV_FAILED
System Log Message Description

Unable to set process privilege level to that of user 'username': error-message In preparation for executing an action defined in a policy, the event processing process (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. Error: An error occurred

Type

EVENTD_ROTATE_FORK_EXCEEDED

265

JUNOS 10.1 System Log Messages Reference

Severity

error

EVENTD_SET_TIMER_FAILED
System Log Message Description

evSetTimer failed: error-message The event processing process (eventd) starts a timer whenever an internal event needs to be generated. It could not activate the timer for the indicated reason. Error: An error occurred error

Type Severity

EVENTD_SYSLOG_FWD_FAILED
System Log Message Description

Unable to forward syslog message to PSD (psd-id), errorno: error-code The event processing process (eventd) encountered a system error when forwarding a syslog message to indicated protected system domain (PSD). Error: An error occurred error

Type Severity

EVENTD_TEST_ALARM
System Log Message Description Type Severity

This is test alarm argument1 of argument2 This is an alarm test for the eventd alarm infrastructure. Event: This message reports an event, not an error notice

EVENTD_TRANSFER_COMMAND_FAILED
System Log Message Description

Command 'error-code' failed during transfer of file 'command': filename The event processing process (eventd) invoked the indicated command while attempting to transfer the indicated file. The command failed. Error: An error occurred error

Type Severity

266

EVENTD_SET_PROCESS_PRIV_FAILED

Chapter 27: EVENTD System Log Messages

EVENTD_TRANSFER_FORK_EXCEEDED
System Log Message Description

Unable to fork: too many child processes The event processing process (eventd) could not create a child process for transferring files, because adding another child would have made the number of children exceed the limit. Error: An error occurred error

Type Severity

EVENTD_TRANSFER_FORK_FAILED
System Log Message Description

Unable to fork: error-message The event processing process (eventd) could not create a child process for transferring files, for the indicated reason. Error: An error occurred error

Type Severity

EVENTD_VERSION_MISMATCH
System Log Message Description

Event version expected-value did not match expected version (received-value) The event processing process (eventd) received an event with the indicated version indicator, which does not match the indicated version expected by the eventd process. Error: An error occurred error

Type Severity

EVENTD_XML_FILENAME_INVALID
System Log Message Description

XML syntax of output filename was invalid An event script created an output file and wrote the filename to standard output (stdout) with 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. Error: An error occurred error

Type Severity

EVENTD_TRANSFER_FORK_EXCEEDED

267

JUNOS 10.1 System Log Messages Reference

268

EVENTD_XML_FILENAME_INVALID

Chapter 28

FCD System Log Messages

This chapter describes messages with the FCD prefix. They are generated by the Fibre Channel process (fcd) which connects servers to disks and tape devices in a storage area network.

FCD_SYS_CALL_FAILED
System Log Message Description Type Severity Cause

reason: error-message A system call made by the fibre channel process (fcd) failed. Error: An error occurred error It is possible that the kernel did not have enough resources to fulfill the request.

FCD_SYS_CALL_FAILED

269

JUNOS 10.1 System Log Messages Reference

270

FCD_SYS_CALL_FAILED

Chapter 29

FLOW System Log Messages

This chapter describes messages with the FLOW prefix. They are generated by the process that handles flows on routers running the JUNOS Software with enhanced services.

FLOW_HIGH_WATERMARK_TRIGGERED
System Log Message

Number of sessions current-flows exceeded the high watermark limit. Early aging triggered. 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 out sessions. This message notifies you that the session high watermark has been exceeded and aggressive aging of sessions has begun. Event: This message reports an event, not an error info

Description

Type Severity

FLOW_IP_ACTION
System Log Message

Flow IP action detected attack attempt: source-address/source-port --> destination-address/destination-port from interface interface-nameaction. Flow IP action detected attack attempt. Event: This message reports an event, not an error info

Description Type Severity

FLOW_LOW_WATERMARK_TRIGGERED
System Log Message

Number of sessions current-flows dropped below the low watermark limit. Early aging stopped. 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

Description

FLOW_HIGH_WATERMARK_TRIGGERED

271

JUNOS 10.1 System Log Messages Reference

aggressively aging out sessions. 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 Severity

Event: This message reports an event, not an error info

FLOW_SESSION_CLOSE
System Log Message

session closed reason: source-address/source-port->destination-address/destination-port,protocol-id: policy-name, inbound-packets, inbound-bytes,outbound-bytes elapsed-time A security session was closed. Event: This message reports an event, not an error info

Description Type Severity

FLOW_SESSION_CREATE
System Log Message

session created source-address/source-port->destination-address/destination-port,protocol-id: policy-name A security session was created. Event: This message reports an event, not an error info

Description Type Severity

FLOW_SESSION_DENY
System Log Message

session denied source-address/source-port->destination-address/destination-port,protocol-id(icmp-type): policy-name A security session was not permitted by policy. Event: This message reports an event, not an error info

Description Type Severity

272

FLOW_LOW_WATERMARK_TRIGGERED

Chapter 30

FPCLOGIN System Log Messages

This chapter describes messages with the FPCLOGIN prefix. They are generated by the Flexible PIC Concentrator (FPC) login process (pimlogin), which provides direct login access to Physical Interface Modules (PIMs).

FPCLOGIN_ADDRESS_GET_FAILED
System Log Message Description

Unable to determine IP address of TGM in slot slot A user tried to log in to the Physical Interface Module (PIM) in the indicated slot on a Flexible PIC Concentrator (FPC). In response, the FPC login process (pimlogin) tried to determine the PIM's IP address. It could not do so, and the login attempt failed. Error: An error occurred error

Type Severity

FPCLOGIN_IPC_RECEIVE_FAILED
System Log Message Description

Unable to receive IPC message from process-name The Flexible PIC Concentrator (FPC) login process (pimlogin) could not process an interprocess communication (IPC) message from the indicated other process. The 'wxd' process is the WX Physical Interface Module process. Error: An error occurred error

Type Severity

FPCLOGIN_IPC_SEND_FAILED
System Log Message Description

Unable to send IPC message to process-name 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). Error: An error occurred

Type

FPCLOGIN_ADDRESS_GET_FAILED

273

JUNOS 10.1 System Log Messages Reference

Severity

error

FPCLOGIN_LOGIN_FAILED
System Log Message Description

fpclogin failed: error-message A user tried to log in to a Physical Interface Module (PIM). The attempt failed for the indicated reason. Error: An error occurred error

Type Severity

FPCLOGIN_MESSAGE_INVALID
System Log Message Description

Message from process-name error-message The message that the Flexible PIC Concentrator (FPC) login process (pimlogin) received from the indicated other process was invalid in the indicated way. The 'wxd' process is the WX Physical Interface Module process (wxd). Error: An error occurred error

Type Severity

FPCLOGIN_SOCKET_OPERATION_FAILED
System Log Message Description

Unable to complete 'error-message' operation The Flexible PIC Concentrator (FPC) login process (pimlogin) could not perform the indicated operation on a routing socket. Error: An error occurred error

Type Severity

274

FPCLOGIN_IPC_SEND_FAILED

Chapter 31

FSAD System Log Messages

This chapter describes messages with the FSAD prefix. They are generated by the File System Access process (fsad), which provides Trivial FTP (TFTP) support for file transfer between services Physical Interface Cards (PICs) and other routing platform components.

FSAD_CONFIG_ERROR
System Log Message Description

Reason: reason The configuration file for the File System Access process (fsad) might contain an error. Error: An error occurred error

Type Severity

FSAD_CONNTIMEDOUT
System Log Message

Connection timed out to the client (connection-type, ip-address) having request type port The File System Access process (fsad) flushed all state information about the timed-out connection. Event: This message reports an event, not an error error

Description

Type Severity

FSAD_DIR_CREATE
System Log Message Description Type Severity

Failed to create directory directory-name: error-message The File System Access process (fsad) could not create the indicated directory. Error: An error occurred error

FSAD_CONFIG_ERROR

275

JUNOS 10.1 System Log Messages Reference

FSAD_DIR_STAT
System Log Message Description

function-name: stat() failed for pathname pathname: reason The File System Access process (fsad) received a request for a nonexistent file or directory. Error: An error occurred error The path does not exist. Make sure the path specified in the request is valid.

Type Severity Cause Action

FSAD_FAILED
System Log Message Description Type Severity Cause Action

In enclosing-function-name: function-name() returned: reason An internal error occurred inside a function in the File System Access process (fsad). Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

FSAD_FILE_FAILED
System Log Message

enclosing-function-name: function-name failed for file 'filename' with error message reason An internal error occurred while the File System Access process (fsad) was performing a file operation. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Description

Type Severity Cause Action

276

FSAD_DIR_STAT

Chapter 31: FSAD System Log Messages

FSAD_FILE_REMOVE
System Log Message Description

Unable to remove file 'filename': reason The File System Access process (fsad) could not remove the indicated file for the indicated reason. Error: An error occurred error The file to be removed does not exist or its permissions do not allow the operation. Make sure that the file exists and that its permissions allow it to be deleted.

Type Severity Cause Action

FSAD_FILE_RENAME
System Log Message Description

Unable to rename file 'source-filename' to 'destination-filename': reason The File System Access process (fsad) could not rename the indicated file for the indicated reason. Error: An error occurred error Either the source file does not exist, or one or both of the source and destination pathnames are incorrect. Make sure the source and destination paths exist and that the rename operation is allowed.

Type Severity Cause

Action

FSAD_FILE_STAT
System Log Message Description Type Severity Cause Action

function-name: stat() failed for file pathname pathname: reason The File System Access process (fsad) received a request for a nonexistent file. Error: An error occurred error The file path does not exist. Make sure the path specified in the request is valid.

FSAD_FILE_REMOVE

277

JUNOS 10.1 System Log Messages Reference

FSAD_FILE_SYNC
System Log Message Description

Unable to sync file 'filename': reason When closing a file, the File System Access process (fsad) executes the sync() system call to ensure that any changes to the file are committed to disk. This operation failed for the indicated file. Error: An error occurred error

Type Severity

FSAD_FLOWC_IPC_PAYLOAD_SIZE
System Log Message

Received flowc IPC message with incorrect length: message type message-type, subtype message-subtype, opcode operation-code, length length (expected length expected-value) The File System Access process (fsad) received a flow collector IPC message in which the payload length was incorrect. Error: An error occurred error

Description

Type Severity

FSAD_FLOWC_IPC_SUBTYPE
System Log Message

Received flowc IPC message with incorrect subtype: message type message-type, subtype message-subtype, opcode operation-code, length length The File System Access process (fsad) received a flow collector IPC message in which the subtype field was incorrect. Error: An error occurred error

Description

Type Severity

FSAD_FLOWC_IPC_TYPE
System Log Message

Received flowc IPC message with incorrect type: message type message-type, subtype message-subtype, opcode operation-code, length length The File System Access process (fsad) received a flow collector IPC message in which the type field was incorrect. Error: An error occurred

Description

Type

278

FSAD_FILE_SYNC

Chapter 31: FSAD System Log Messages

Severity

error

FSAD_FLOWC_IPC_VERSION
System Log Message

Received flowc IPC message with incorrect version received-value (expected version expected-value) The File System Access process (fsad) received a flow collector IPC message in which the version field was incorrect. Error: An error occurred error

Description

Type Severity

FSAD_FLOWC_SERVICE_INACTIVE
System Log Message Description

reason The File System Access process (fsad) received a request for the Flow Collector Transfer Log Archive service, which is not currently active. Error: An error occurred error

Type Severity

FSAD_FREE_SPACE_LOG
System Log Message

Unable to move temporary file temporary-filename (size file-size KB) to log file log-filename because free disk space (count KB) is insufficient The File System Access process (fsad) could not move the CDR temporary file of the indicated size to the log file, because it is larger than the amount of free disk space. Error: An error occurred error

Description

Type Severity

FSAD_FREE_SPACE_TMP
System Log Message

Unable to write CDR batch output to file temporary-filename because free disk space (count KB) is insufficient The File System Access process (fsad) could not write CDR batch output to the indicated temporary file, because the amount of free disk space was insufficient. Error: An error occurred error

Description

Type Severity

FSAD_FLOWC_IPC_TYPE

279

JUNOS 10.1 System Log Messages Reference

FSAD_FS_STAT
System Log Message Description

statfs() failed for pathname pathname: reason The File System Access process (fsad) encountered an error in getting filesystem statistics. Error: An error occurred error

Type Severity

FSAD_GEN_IPC_PAYLOAD_SIZE
System Log Message

Received IPC message with incorrect length: message type message-type, subtype message-subtype, opcode operation-code, length length (expected length expected-value) The File System Access process (fsad) received an IPC message in which the payload length was incorrect. Error: An error occurred error

Description

Type Severity

FSAD_GEN_IPC_SUBTYPE
System Log Message

Received IPC message with incorrect subtype: message type message-type, subtype message-subtype, opcode operation-code, length length The File System Access process (fsad) received an IPC message in which the subtype field was incorrect. Error: An error occurred error

Description

Type Severity

FSAD_GEN_IPC_TYPE
System Log Message

Received IPC message with incorrect type: message type message-type, subtype message-subtype, opcode operation-code, length length The File System Access process (fsad) received an IPC message in which the type field was incorrect. Error: An error occurred error

Description

Type Severity

280

FSAD_FS_STAT

Chapter 31: FSAD System Log Messages

FSAD_GEN_IPC_VERSION
System Log Message

Received generic IPC message with incorrect version received-value (expected version expected-value) The File System Access process (fsad) received an IPC message in which the version field was incorrect. Error: An error occurred error

Description

Type Severity

FSAD_GEN_SERVICE_INACTIVE
System Log Message Description

Received IPC message for inactive service service-name The File System Access process (fsad) received an IPC message for a service that is currently not active. Error: An error occurred error

Type Severity

FSAD_GEN_SERVICE_INIT_FAILED
System Log Message Description Type Severity

Failed to initialize service service-name The File System Access process (fsad) could not initialize the indicated service. Error: An error occurred error

FSAD_MAXCONN
System Log Message Description

Upper limit reached in fsad for handling connections The File System Access process (fsad) stopped accepting new connections because it reached an internal limit for handling connections. Event: This message reports an event, not an error error

Type Severity

FSAD_GEN_IPC_VERSION

281

JUNOS 10.1 System Log Messages Reference

FSAD_MEMORYALLOC_FAILED
System Log Message Description

allocation-function-name failed in the function function-name (line-number) The File System Access process (fsad) could not allocate memory. The system might be running low on memory. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

FSAD_NOT_ROOT
System Log Message Description

Must be run as root The user who attempted to start the File System Access process (fsad) was not the root user. Error: An error occurred error

Type Severity

FSAD_PARENT_DIRECTORY
System Log Message Description Type Severity Action

directory-name: invalid directory: message The parent directory specified in the request for a file was not valid. Error: An error occurred error Make sure the path specified in the request is valid.

FSAD_PATH_IS_DIRECTORY
System Log Message Description

File path cannot be a directory (pathname) The File System Access process (fsad) received a request on a directory instead of a regular file. Error: An error occurred

Type

282

FSAD_MEMORYALLOC_FAILED

Chapter 31: FSAD System Log Messages

Severity Cause Action

error The file path points to a directory. Make sure the path points to a regular file.

FSAD_PATH_IS_NOT_DIRECTORY
System Log Message Description

invalid path 'pathname' : not a directory : action The File System Access process (fsad) received a request for a pathname that was not a directory. Error: An error occurred error

Type Severity

FSAD_PATH_IS_SPECIAL
System Log Message Description

Not a regular file (pathname) The File System Access process (fsad) received a request for a pathname that points to a nonregular file. Error: An error occurred error Make sure the path points to a regular file.

Type Severity Action

FSAD_RECVERROR
System Log Message

fsad received error message from client having request type connection-type at (ip-address, port) The File System Access process (fsad) received a packet with the indicated error message from the other end of a connection. Error: An error occurred error

Description

Type Severity

FSAD_RENAME
System Log Message

function-name: failed to rename temporary file filename to new-filename: reason

FSAD_PATH_IS_DIRECTORY

283

JUNOS 10.1 System Log Messages Reference

Description

The File System Access process (fsad) could not rename the indicated temporary file for the indicated reason. Error: An error occurred error

Type Severity

FSAD_TERMINATED_CONNECTION
System Log Message Description

Open file 'filename' closed due to process shutdown The File System Access process (fsad) terminated a connection, stored the connection's (unwritten) data to disk, and purged it from its data structures. Event: This message reports an event, not an error notice

Type Severity

FSAD_TRACEOPEN_FAILED
System Log Message Description Type Severity

Open operation on trace file 'pathname' returned error error-message The File System Access process (fsad) failed to open the indicated trace file. Error: An error occurred error

FSAD_USAGE
System Log Message Description Type Severity Cause Action

Incorrect usage, message The File System Access process (fsad) displayed its usage statement. Event: This message reports an event, not an error error The fsad process was invoked with incorrect command-line arguments. Check the usage and invoke the fsad process with the correct command-line arguments.

284

FSAD_RENAME

Chapter 32

FUD System Log Messages

This chapter describes messages with the FUD prefix. They are generated by the UDP forwarding process (fud), which forwards UDP (User Datagram Protocol) packets from a network to a server for services that run over UDP.

FUD_ARGUMENT_FAILURE
System Log Message Description

Unknown option "option" One or more options provided on the 'fud' command line were invalid. The UDP forwarding process (fud) initialized but ignored the invalid options. Error: An error occurred error Reissue the 'fud' command with the correct options.

Type Severity Action

FUD_BAD_SERVER_ADDR_FAILURE
System Log Message Description

Destination address of destination-address is invalid One or more server addresses configured for the UDP forwarding process (fud) were invalid. Error: An error occurred error Reconfigure the fud process with valid server addresses.

Type Severity Action

FUD_BIND_FAILURE
System Log Message Description

bind(port port) failed: error-message The UDP forwarding process (fud) received the indicated error when it tried to bind a socket to a local address.

FUD_ARGUMENT_FAILURE

285

JUNOS 10.1 System Log Messages Reference

Type Severity Action

Error: An error occurred error Contact your technical support representative.

FUD_DAEMON_FAILURE
System Log Message Description

Unable to run in the background as daemon: error-message The UDP forwarding process (fud) could not create a version of itself to run in the background as a daemon. Error: An error occurred error Contact your technical support representative.

Type Severity Action

FUD_MEMORY_ALLOCATION_FAILURE
System Log Message Description

Unable to allocate count bytes of memory: error-message The UDP forwarding process (fud) could not allocate the indicated amount of memory from the heap. Error: An error occurred error Contact your technical support representative.

Type Severity Action

FUD_PERMISSION_FAILURE
System Log Message Description

program-name must be run as root The user who attempted to start the UDP forwarding process (fud) was not the root user, so the process did not start. Error: An error occurred error Become the root user before issuing the 'fud' command.

Type Severity Action

286

FUD_BIND_FAILURE

Chapter 32: FUD System Log Messages

FUD_PIDLOCK_FAILURE
System Log Message Description

Unable to lock PID file; another program-name was running The UDP Forwarding process (fud) attempted to lock the file that records its process ID (PID), which serves to prevent multiple instances of the fud process from running simultaneously. The attempt failed. Error: An error occurred error Another instance of the fud process is running. Check whether another fud process is running, and stop it if appropriate.

Type Severity Cause Action

FUD_PIDUPDATE_FAILURE
System Log Message Description

Unable to update PID file for program-name The UDP Forwarding process (fud) attempted to update the file that records its process ID (PID), which serves to prevent multiple instances of the fud process from running simultaneously. The attempt failed. Error: An error occurred error Another instance of the fud process is running. Check whether another fud process is running, and stop it if appropriate.

Type Severity Cause Action

FUD_RECVMSG_FAILURE
System Log Message Description

Exiting because of repeated recvmsg() failures The UDP Forwarding process (fud) could not receive data from the network, which it needs to do during normal operation. Error: An error occurred error Contact your technical support representative.

Type Severity Action

FUD_PIDLOCK_FAILURE

287

JUNOS 10.1 System Log Messages Reference

FUD_RTSOCK_WRITE_FAILURE
System Log Message Description

Unable to write to routing socket: error-message The UDP Forwarding process (fud) could not write to its routing socket for the indicated reason. Error: An error occurred error Contact your technical support representative.

Type Severity Action

FUD_SENDMSG_FAILURE
System Log Message

sendmsg() to destination-address port port on interface interface-name rt_inst routing-instance failed: error-message The UDP Forwarding process (fud) could not send data to the indicated destination port and address via the indicated interface and routing instance, which it needs to do during normal operation. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

FUD_SENDMSG_NOINT_FAILURE
System Log Message Description

sendmsg() to destination-address port port rt_inst routing-instance failed: error-message The UDP Forwarding process (fud) could not send data to the indicated destination port and address via the indicated routing instance, which it needs to do during normal operation. Error: An error occurred error Contact your technical support representative.

Type Severity Action

FUD_SETSOCKOPT_FAILURE
System Log Message

setsockopt(arguments) failed: error-message

288

FUD_RTSOCK_WRITE_FAILURE

Chapter 32: FUD System Log Messages

Description Type Severity Action

The UDP Forwarding process (fud) could not set the indicated socket option. Error: An error occurred error Contact your technical support representative.

FUD_SOCKET_FAILURE
System Log Message Description Type Severity Action

socket(arguments) failed: error-message The UDP Forwarding process (fud) could not create a socket. Error: An error occurred error Contact your technical support representative.

FUD_SETSOCKOPT_FAILURE

289

JUNOS 10.1 System Log Messages Reference

290

FUD_SOCKET_FAILURE

Chapter 33

FWAUTH System Log Messages

This chapter describes messages with the FWAUTH prefix. They are generated by the process that authenticates users when they initiate a connection across a firewall.

FWAUTH_FTP_LONG_PASSWORD
System Log Message Description Type Severity

Authentication for user username at client-address was denied (long password). The length of the password must not exceed 128 characters. Event: This message reports an event, not an error info

FWAUTH_FTP_LONG_USERNAME
System Log Message Description Type Severity

Authentication for user username at client-address was denied (long username). The length of the username must not exceed 64 characters. Event: This message reports an event, not an error info

FWAUTH_FTP_USER_AUTH_ACCEPTED
System Log Message Description Type Severity

User usernamegroup-name at client-address is accepted. The authenticated user can start accessing protected resources. Event: This message reports an event, not an error info

FWAUTH_FTP_USER_AUTH_FAIL
System Log Message

User username at client-address is rejected.

FWAUTH_FTP_LONG_PASSWORD

291

JUNOS 10.1 System Log Messages Reference

Description Type Severity

User authentication failed because the username or password was invalid. Event: This message reports an event, not an error notice

FWAUTH_HTTP_USER_AUTH_ACCEPTED
System Log Message Description Type Severity

User usernamegroup-name at client-address is accepted. The authenticated user can start accessing protected resources. Event: This message reports an event, not an error info

FWAUTH_HTTP_USER_AUTH_FAIL
System Log Message Description Type Severity

User username at client-address is rejected. User authentication failed because the username or password was invalid. Event: This message reports an event, not an error notice

FWAUTH_TELNET_LONG_PASSWORD
System Log Message Description Type Severity

Authentication for user username at client-address was denied (long password). The length of the password must not exceed 128 characters. Event: This message reports an event, not an error info

FWAUTH_TELNET_LONG_USERNAME
System Log Message Description Type Severity

Authentication for user username at client-address was denied (long username). The length of username must not exceed 64 characters. Event: This message reports an event, not an error info

292

FWAUTH_FTP_USER_AUTH_FAIL

Chapter 33: FWAUTH System Log Messages

FWAUTH_TELNET_USER_AUTH_ACCEPTED
System Log Message Description Type Severity

User usernamegroup-name at client-address is accepted. The authenticated user can start accessing protected resources Event: This message reports an event, not an error info

FWAUTH_TELNET_USER_AUTH_FAIL
System Log Message Description Type Severity

User username at client-address is rejected. User authentication failed because the username or password was invalid. Event: This message reports an event, not an error notice

FWAUTH_WEBAUTH_FAIL
System Log Message Description Type Severity

WebAuth user username at client-address is rejected/timed out. The provided user credentials are not valid. Event: This message reports an event, not an error info

FWAUTH_WEBAUTH_SUCCESS
System Log Message Description Type Severity

WebAuth user username at client-address is accepted. The authenticated user can start accessing protected resources. Event: This message reports an event, not an error info

FWAUTH_TELNET_USER_AUTH_ACCEPTED

293

JUNOS 10.1 System Log Messages Reference

294

FWAUTH_WEBAUTH_SUCCESS

Chapter 34

GPRSD System Log Messages

This chapter describes messages with the GPRSD prefix. They are generated by the general packet radio service process (gprsd) that integrates with existing GSM networks and offers mobile subscribers with packet switched data services access to corporate networks and the Internet.

GPRSD_MEMORY_ALLOC_FAILED
System Log Message Description

Unable to allocate count bytes of memory The general packet radio service daemon process (gprsd) could not allocate the indicated number of bytes of memory. Error: An error occurred error It is possible that system memory is exhausted. Increase the amount of RAM in the Routing Engine.

Type Severity Cause Action

GPRSD_RESTART_CCFG_READ_FAILED
System Log Message Description

Subcomponent could not read configuration database 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. Error: An error occurred error

Type Severity

GPRSD_MEMORY_ALLOC_FAILED

295

JUNOS 10.1 System Log Messages Reference

296

GPRSD_RESTART_CCFG_READ_FAILED

Chapter 35

HNCACHED System Log Messages

This chapter describes messages with the HNCACHED prefix. They are generated by the hostname-caching process (hncached) which stores hostnames in a temporary storage area in order to be able to retrieve them faster.

HNCACHED_HOST_ADDRESS_CHANGED
System Log Message Description

Detected change in IP addresses for host: hostname The hostname-caching process (hostname-cached) detected that the set of IP addresses for the specified hostname changed. Event: This message reports an event, not an error info

Type Severity

HNCACHED_NAME_RESOLUTION_FAILURE
System Log Message Description

Failed to resolve hostname: hostname (error-message) The hostname-caching process (hostname-cached) failed to resolve the specified hostname for the indicated reason. Error: An error occurred error (1) If the hostname used in config is incorrect, fix it. (2) Ensure that the configured name-server is reachable and working.

Type Severity Action

HNCACHED_HOST_ADDRESS_CHANGED

297

JUNOS 10.1 System Log Messages Reference

298

HNCACHED_NAME_RESOLUTION_FAILURE

Chapter 36

ICCPD System Log Messages

This chapter describes messages with the ICCPD prefix. They are generated by the interchassis communication process (iccpd).

ICCPD_ASSERT_SOFT
System Log Message

Soft assertion failed at line line-number in file 'source-filename' with error "message", but iccpd with PID pid continued running The source code for the interchassis communication process (iccpd) includes internal self-consistency checks. As the iccpd process with the indicated process ID (PID) executed the binary compiled from the indicated source file, a check failed at the indicated line number in the file. The iccpd process created a diagnostic core file for analysis by technical support personnel and continued to run. Error: An error occurred error An internal software failure occurred. Examine the messages that immediately follow this message in the system log for information about possible causes. Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core file, if requested.

Description

Type Severity Cause Action

ICCPD_OPEN_ERROR
System Log Message Description Type Severity Action

error-message: open error on pipe The interchassis communication process (iccpd) could not initialize. Error: An error occurred error Contact your technical support representative.

ICCPD_ASSERT_SOFT

299

JUNOS 10.1 System Log Messages Reference

ICCPD_READ_ERROR
System Log Message Description

Read error on pipe from client-name: reason (error-message) The interchassis communication process (iccpd) could not read a message on a pipe for the indicated client. Error: An error occurred info Contact your technical support representative.

Type Severity Action

ICCPD_WRITE_ERROR
System Log Message Description

write error on pipe to client-name: The interchassis communication process (iccpd) could not write a message on a pipe for the indicated client. Error: An error occurred error Contact your technical support representative.

Type Severity Action

300

ICCPD_READ_ERROR

Chapter 37

IDP System Log Messages

This chapter describes messages with the IDP prefix. They are generated by the Intrusion Detection and Prevention (IDP) process which enforces various attack detection and prevention techniques on network traffic.

IDP_APPDDOS_APP_ATTACK_EVENT
System Log Message

DDOS Attack at timestamp on ddos-application-name, < source-zone-name:source-interface-name:source-address:source-port>destination-zone-name:destination-interface-name:destination-address:destination-port > for protocol-name protocol and service service-name by rule rule-name of rulebase rulebase-name in policy policy-name. attack: repeats repeat-count action action severity severity, connection-hit-rate connection-hit-rate, context-name context-name, hit-rate context-hit-rate, value-hit-rate context-value-hit-rate time-scope time-scope time-count time-count time-period time-period secs, context value: context-value The application-level distributed denial-of-service (AppDDoS) attack occurred when the number of client transactions exceeded the user-configured connection, context and time binding thresholds Event: This message reports an event, not an error info

Description

Type Severity

IDP_APPDDOS_APP_STATE_EVENT
System Log Message

DDOS Application threshold crossed at timestamp on ddos-application-name, <destination-zone-name:destination-interface-name:destination-address:destination-port> for protocol-name protocol and service service-name in rule rule-name of rulebase rulebase-name in policy policy-name. repeats repeat-count message: message context-value: context-value 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 Event: This message reports an event, not an error info

Description

Type Severity

IDP_APPDDOS_APP_ATTACK_EVENT

301

JUNOS 10.1 System Log Messages Reference

IDP_ATTACK_LOG_EVENT
System Log Message

IDP: at timestamp, message-type Attack log <source-address:source-port->destination-address:destination-port> for protocol-name protocol and service service-name application application-name by rule rule-name of rulebase rulebase-name in policy policy-name. attack: repeat=repeat-count, action=action, severity=severity, name=attack-name, NAT <nat-source-address:nat-source-port->nat-destination-address:nat-destination-port>, time-elapsed=elapsed-time, inbytes=inbound-bytes, outbytes=outbound-bytes, inpackets=inbound-packets, outpackets=outbound-packets, intf:source-zone-name:source-interface-name->destination-zone-name:destination-interface-name, and misc-message message IDP Attack log generated for attack Event: This message reports an event, not an error info

Description Type Severity

IDP_DAEMON_INIT_FAILED
System Log Message Description

Aborting...A failure was encountered;error-message An attempt to start IDP policy daemon failed because an error was encountered during initialization. Error: An error occurred error

Type Severity

IDP_INTERNAL_ERROR
System Log Message Description Type Severity

Encountered an error(error-message) IDP daemon encountered an internal error Error: An error occurred error

IDP_POLICY_COMPILATION_FAILED
System Log Message Description

IDP compilation of policy[idp-policy] failed : [reason] IDP policy compiler encountered an error while compiling or packaging the policy.Device will continue running the existing IDP policy

302

IDP_ATTACK_LOG_EVENT

Chapter 37: IDP System Log Messages

Type Severity

Event: This message reports an event, not an error error

IDP_POLICY_LOAD_FAILED
System Log Message Description

IDP policy loading failed ;policy[idp-policy], detector[idp-detector] ,failure detail[reason] A compiled and optimized IDP policy could not be loaded into IDP engine. Device will continue running the existing IDP policy. Error: An error occurred error

Type Severity

IDP_POLICY_LOAD_SUCCEEDED
System Log Message Description

IDP policy[idp-policy] and detector[idp-detector] loaded successfully(message). A compiled and optimized IDP policy was loaded successfully into the IDP engine. All subsequent sessions will be processed as per this new IDP policy. Event: This message reports an event, not an error notice

Type Severity

IDP_POLICY_UNLOAD_FAILED
System Log Message Description

Failed to unload IDP policy. reason: reason. A running IDP policy could not be unloaded from IDP engine. Device will continue running the IDP policy. Error: An error occurred error

Type Severity

IDP_POLICY_UNLOAD_SUCCEEDED
System Log Message Description Type Severity

IDP policy unloaded successfully. A running IDP policy was unloaded successfully from the IDP engine. Event: This message reports an event, not an error notice

IDP_POLICY_COMPILATION_FAILED

303

JUNOS 10.1 System Log Messages Reference

IDP_SCHEDULEDUPDATE_START_FAILED
System Log Message Description

Failed to start scheduled update(error:error-message) The scheduled IDP security package update failed to start. Device will try it again at the next scheduled time Error: An error occurred error

Type Severity

IDP_SCHEDULED_UPDATE_STARTED
System Log Message Description Type Severity

Scheduled update has started(at timestamp) The scheduled IDP security package update has started. Event: This message reports an event, not an error notice

IDP_SECURITY_INSTALL_RESULT
System Log Message Description Type Severity

security package install result(status) IDP background process has returned the security package install result Event: This message reports an event, not an error notice

IDP_SESSION_LOG_EVENT
System Log Message Description Type Severity

IDP: at timestamp, event-name log generated IDP session threshold crossing event Event: This message reports an event, not an error info

IDP_SIGNATURE_LICENSE_EXPIRED
System Log Message

IDP Signagure update license(ID=feature-id) has expired

304

IDP_SCHEDULEDUPDATE_START_FAILED

Chapter 37: IDP System Log Messages

Description

IDP signature update license key has expired. Signature update may not work any more. Event: This message reports an event, not an error warning

Type Severity

IDP_SIGNATURE_LICENSE_EXPIRED

305

JUNOS 10.1 System Log Messages Reference

306

IDP_SIGNATURE_LICENSE_EXPIRED

Chapter 38

JADE System Log Messages

This chapter describes messages with the JADE prefix. They are generated by the JUNOScript authentication process (jade), which authenticates and checks authorization of client applications using the JUNOScript application programming interface (API).

JADE_ATTRIBUTES_TOO_LONG
System Log Message Description

Attribute number or length in client junoscript tag was too large The JUNOScript client passed too many attributes in the initial <junoscript> tag, or the attributes were too long. Error: An error occurred error

Type Severity

JADE_AUTH_FAILURE
System Log Message Description Type Severity

Authentication failed for user 'username' : error-message The username or password supplied by the client was incorrect. Error: An error occurred notice

JADE_AUTH_SUCCESS
System Log Message Description Type Severity

Authentication succeded for user 'username' The jade authentication process authenticated the indicated user. Event: This message reports an event, not an error notice

JADE_ATTRIBUTES_TOO_LONG

307

JUNOS 10.1 System Log Messages Reference

JADE_EXEC_ERROR
System Log Message Description

CLI xml-mode exec error: error-message The JUNOScript authentication process (jade) could not start because of an internal error. Error: An error occurred error

Type Severity

JADE_PAM_ERROR
System Log Message Description

PAM error: error-message The JUNOScript authentication process (jade) could not process the credentials supplied by the client. Error: An error occurred error

Type Severity

JADE_PAM_NO_LOCAL_USER
System Log Message Description

Unable to get local username from PAM: error-message The JUNOScript authentication process (jade) could not obtain a local username while processing the credentials supplied by the client. Error: An error occurred error

Type Severity

JADE_SOCKET_ERROR
System Log Message Description

Socket operation 'operation' failed: error-message The indicated socket operation, initiated by the JUNOScript authentication process (jade), failed for the indicated reason. Error: An error occurred error

Type Severity

308

JADE_EXEC_ERROR

Chapter 39

JCS System Log Messages

This chapter describes messages with the JCS prefix. They are generated by the Juniper Control System (jcsd) process which provides the user interface to the control processes for the management modules and switch modules in the JCS 1200 platform.

JCS_BBD_LOAD_FAILURE
System Log Message Description Type Severity

Blade slot load BBD falure: error-message The JCS process (jcsd) could not load blade bay data for the specified blade. Error: An error occurred error

JCS_BBD_LOCAL_MISMATCH
System Log Message Description

Blade slot BBD error-message mismatch (expected-value != received-value) The blade bay data retrieved for the specified blade does not match the data loaded during the reboot process. This error usually indicates that blade bay data in the JCS Management Module was changed since the last reboot. Error: An error occurred error

Type Severity

JCS_BBD_NOT_FOUND
System Log Message Description Type Severity

Blade slot bay data not found Blade bay data was not found for the specified blade. Error: An error occurred error

JCS_BBD_LOAD_FAILURE

309

JUNOS 10.1 System Log Messages Reference

JCS_BBD_NOT_VALID
System Log Message Description Type Severity

Blade slot BBD is invalid The blade bay data for the specified blade is invalid. Error: An error occurred error

JCS_BBD_PARSE_ERROR
System Log Message Description Type Severity

Blade slot bay data parse error - error-message The blade bay data for the specified blade did not parse correctly. Error: An error occurred error

JCS_BBD_PEER_MISMATCH
System Log Message Description

Peer blade slot BBD error-message mismatch (expected-value != received-value) The blade bay data retrieved for the specified peer blade does not match the data retrieved for the local blade. This error indicates that blade bay data in the JCS Management Module was not configured properly. Error: An error occurred error

Type Severity

JCS_BBD_SYSTEM_CONFLICT
System Log Message Description

Local BBD error-message (value) conflicts with blade slot The blade bay data retrieved for the local blade conflicts with another blade in the JCS. This error indicates that blade bay data in the JCS Management Module was not configured properly. Error: An error occurred error

Type Severity

310

JCS_BBD_NOT_VALID

Chapter 39: JCS System Log Messages

JCS_EXT_LINK_STATE
System Log Message Description

Switch slot EXT link state is state The JCS process (jcsd) detects a change of state for the external link of the indicated switch module. Event: This message reports an event, not an error info

Type Severity

JCS_INVALID_BANDWIDTH_ERROR
System Log Message Description

Invalid bandwidth percent (value) The specified switch bandwidth is invalid. The bandwidth is defined as a percentage between 1 and 100. Error: An error occurred error

Type Severity

JCS_KERNEL_RSD_LINK_DOWN
System Log Message Description

Kernel RSD link is DOWN (error-message) The JCS process (jcsd) has disabled kernel RSD communcation for the specified reason. Error: An error occurred error

Type Severity

JCS_KERNEL_RSD_LINK_ENABLED
System Log Message Description

Kernel RSD link is ENABLED (error-message) The JCS process (jcsd) has verified the blade bay data and enabled kernel RSD communication. Event: This message reports an event, not an error info

Type Severity

JCS_EXT_LINK_STATE

311

JUNOS 10.1 System Log Messages Reference

JCS_MM_COMMUNICATION_ERROR
System Log Message Description

MM communication error (error-message) The JCS process (jcsd) could not send an SNMP request to the Management Module because of the indicated error. Error: An error occurred error

Type Severity

JCS_MM_COMMUNICATION_OK
System Log Message Description

MM communication is OK The JCS process (jcsd) has established a communication link with the Management Module. Event: This message reports an event, not an error info

Type Severity

JCS_PEER_BLADE_STATE
System Log Message Description Type Severity

Peer blade slot is state The JCS process (jcsd) detects a change of state for the indicated blade. Event: This message reports an event, not an error info

JCS_READ_BANDWIDTH_ERROR
System Log Message Description Type Severity

Read bandwidth error (error-code) The indicated error occured when attempting to read the current switch bandwidth. Error: An error occurred error

JCS_READ_BBD_ERROR
System Log Message

Read blade bay data (error=error-code)

312

JCS_MM_COMMUNICATION_ERROR

Chapter 39: JCS System Log Messages

Description

The indicated error occured when attempting to read the current blade bay data via a sysctl call. Error: An error occurred error

Type Severity

JCS_RSD_LINK_STATE
System Log Message Description

Switch slot RSD link state is state The JCS process (jcsd) detects a change of state for the RSD link of the indicated switch module. Event: This message reports an event, not an error info

Type Severity

JCS_SWITCH_BANDWIDTH_CONFIG
System Log Message Description

Switch slot bandwidth value1 percent (value2 KBPS) The indicated JCS Switch Module has changed the bandwidth configuration to the specified value. Event: This message reports an event, not an error info

Type Severity

JCS_SWITCH_COMMUNICATION_ERROR
System Log Message Description

Switch slot communication error (error-message) The JCS process (jcsd) could not send an SNMP request to the indicated Switch Module because of the indicated error. Error: An error occurred error

Type Severity

JCS_SWITCH_COMMUNICATION_OK
System Log Message Description

Switch slot communication is OK The JCS process (jcsd) has established a communication link with the indicated Switch Module. Event: This message reports an event, not an error

Type

JCS_READ_BBD_ERROR

313

JUNOS 10.1 System Log Messages Reference

Severity

info

314

JCS_SWITCH_COMMUNICATION_OK

Chapter 40

JDIAMETERD System Log Messages

This chapter describes messages with the JDIAMETERD prefix. They are generated by the jdiameter process (jdiameterd). Jdiameter is an open source software implementation of the Diameter Base Protocol that is written in Java.

JDIAMETERD_FUNC_ACCEPT_FAIL
System Log Message Description

Accept failed: no socket The Diameter process (jdiameterd) failed to accept a connection from the process that implements the Diameter function. Error: An error occurred error

Type Severity

JDIAMETERD_FUNC_ACCEPT_NOT_FOUND
System Log Message Description

Path pathname does not match any application The Diameter process (jdiameterd) rejected a function-side connection because there was no matching Diameter function. Error: An error occurred error

Type Severity

JDIAMETERD_FUNC_OUT_OF_SYNC
System Log Message Description

Application diameter-function is out of sync, disconnecting The Diameter process (jdiameterd) was out of sync with the process that implements the Diameter function. The connection was closed so that a new connection with full resynchronization could be established. Error: An error occurred error

Type Severity

JDIAMETERD_FUNC_ACCEPT_FAIL

315

JUNOS 10.1 System Log Messages Reference

JDIAMETERD_FUNC_SOCK_BIND_FAIL
System Log Message Description

Unable to bind listening socket to pathname The Diameter process (jdiameterd) was unable to bind the listening socket for function-side connections. Error: An error occurred error

Type Severity

JDIAMETERD_FUNC_SOCK_CREATE_FAIL
System Log Message Description

Unable to create listening socket The Diameter process (jdiameterd) was unable to create a listening socket for function-side connections. Error: An error occurred error

Type Severity

JDIAMETERD_FUNC_SOCK_LISTEN_FAIL
System Log Message Description

Unable to listen on pathname The Diameter process (jdiameterd) was unable to listen on the socket for function-side connections. Error: An error occurred error

Type Severity

JDIAMETERD_MEMRLIM_REQUEST_FAIL
System Log Message Description

Unable to set memory limit The Diameter process (jdiameterd) was unable to set the required memory allocation limit. Error: An error occurred error

Type Severity

316

JDIAMETERD_FUNC_SOCK_BIND_FAIL

Chapter 41

JSRPD System Log Messages

This chapter describes messages with the JSRPD prefix. They are generated by the Juniper Services Redundancy Protocol (jsrpd) process, which controls chassis clustering.

JSRPD_DAEMONIZE_FAILED
System Log Message Description

Aborting, unable to run in the background as a daemon: error-message The jsrpd process (jsrpd) could not create a version of itself to run in the background as a daemon. Error: An error occurred emergency

Type Severity

JSRPD_DUPLICATE
System Log Message Description

Another copy of this program is running An attempt to start the jsrpd process (jsrpd) failed because an instance of the process was already running. Error: An error occurred error

Type Severity

JSRPD_NOT_ROOT
System Log Message Description Type Severity

Must be run as root The user who attempted to start the JSRP process (jsrpd) was not the root user. Error: An error occurred error

JSRPD_DAEMONIZE_FAILED

317

JUNOS 10.1 System Log Messages Reference

JSRPD_PID_FILE_LOCK
System Log Message Description

Unable to lock PID file: error-message The jsrpd process (jsrpd) attempted to lock the file that records its process ID (PID), which serves to prevent multiple instances of jsrpd from running simultaneously. The attempt failed. Error: An error occurred error

Type Severity

JSRPD_PID_FILE_UPDATE
System Log Message Description

Unable to update process PID file: error-message The jsrpd process (jsrpd) attempted to update the file that records its process ID (PID), which serves to prevent multiple instances of jsrpd from running simultaneously. The attempt failed. Error: An error occurred error

Type Severity

JSRPD_SOCKET_CREATION_FAILURE
System Log Message Description Type Severity

Socket creation (server) failed unexpectedly error-message. The jsrpd process (jsrpd) could not successfully create a socket. Error: An error occurred error

JSRPD_SOCKET_LISTEN_FAILURE
System Log Message Description Type Severity

Socket listen (server) failed unexpectedly. error-message The jsrpd process (jsrpd) could not successfully listen on a socket. Error: An error occurred error

318

JSRPD_PID_FILE_LOCK

Chapter 41: JSRPD System Log Messages

JSRPD_SOCKET_RECV_HB_FAILURE
System Log Message Description Type Severity

Socket reception of heartbeat from failed unexpectedly error-message. The jsrpd process (jsrpd) could not successfully receive on a socket. Error: An error occurred error

JSRPD_USAGE
System Log Message Description

Usage: jsrpd [-C] [-N] [-X] [-d debug-level] [-l] [-v] The jsrpd process (jsrpd) displayed the syntax statement for the 'jsrpd' command because the command was invoked incorrectly. Event: This message reports an event, not an error error

Type Severity

JSRPD_SOCKET_RECV_HB_FAILURE

319

JUNOS 10.1 System Log Messages Reference

320

JSRPD_USAGE

Chapter 42

KMD System Log Messages

This chapter describes messages with the KMD prefix. They are generated by the key management process (kmd), which provides IP Security (IPSec) authentication services for encryption Physical Interface Cards (PICs).

KMD_CFG_IF_ID_POOL_NOT_FOUND
System Log Message

Unable to allocate logical interface for IPSec interface from pool pool-name: pool not found 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 it could not access the indicated pool. Error: An error occurred error

Description

Type Severity

KMD_CFG_IF_ID_POOL_NO_ENTRY
System Log Message

Unable to return logical interface interface-name.interface-unit to pool pool-name: no entry in pool for interface The key management process (kmd) maintains pools of logical interfaces for assignment to IP Security (IPSec) interfaces. It could not return the indicated logical interface to the indicated pool, because there was no entry for the interface in the pool. Error: An error occurred error

Description

Type Severity

KMD_CFG_IF_ID_POOL_NO_INTERFACE
System Log Message

Unable to allocate logical interface for IPSec interface from pool pool-name: no interfaces available

KMD_CFG_IF_ID_POOL_NOT_FOUND

321

JUNOS 10.1 System Log Messages Reference

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. Error: An error occurred error

Type Severity

KMD_CFG_IF_ID_POOL_RETURN_FAILED
System Log Message Description

Unable to return logical interface to pool pool-name: pool not found The key management process (kmd) maintains pools of logical interfaces for assignment to IP Security (IPSec) interfaces. It could not return a logical interface to the indicated pool, because it could not access the pool. Error: An error occurred error

Type Severity

KMD_DPD_FAILOVER_MANUAL_TUNNEL
System Log Message Description

Tunnel tunnel-name did not fail over: it is manual type An IP Security (IPSec) tunnel normally fails over to its backup when the key management process (kmd) detects a dead peer. Failover was not attempted for the indicated tunnel, which is configured as a manual type and so does not support failover. Error: An error occurred error

Type Severity

KMD_DPD_FAILOVER_MAX_ATTEMPTS
System Log Message Description

Number of failover attempts exceeded limit count for tunnel tunnel-name An IP Security (IPSec) tunnel fails over to its backup when the key management process (kmd) detects a dead peer. The key management process (kmd) stopped making failover attempts for the indicated tunnel, because the number of attempts exceeded the indicated limit configured for Internet Key Exchange (IKE) Phase 1 negotiations. Error: An error occurred error Failover attempts can fail repeatedly if both the primary and backup peers are unreachable during the failover.

Type Severity Cause

322

KMD_CFG_IF_ID_POOL_NO_INTERFACE

Chapter 42: KMD System Log Messages

KMD_DPD_FAILOVER_NO_ACTIVE_PEER
System Log Message Description

Tunnel tunnel-name did not fail over: no active peer configured An IP Security (IPSec) tunnel normally fails over to its backup when the key management process (kmd) detects a dead peer. Failover was not attempted because the configuration for the indicated tunnel does not include information about an active peer. Error: An error occurred error

Type Severity

KMD_DPD_FAILOVER_NO_BACKUP_PEER
System Log Message Description

Tunnel tunnel-name did not fail over: no backup peer configured An IP Security (IPSec) tunnel normally fails over to its backup when the key management process (kmd) detects a dead peer. A failover attempt failed when the kmd process found that the configuration for the indicated tunnel does not include information about a backup peer. Error: An error occurred error

Type Severity

KMD_DPD_FAILOVER_NO_TUNNEL_CFG
System Log Message Description

Tunnel did not fail over: tunnel configuration not found An IP Security (IPSec) tunnel normally fails over to its backup when the key management process (kmd) detects a dead peer. Failover was not attempted because there was no configuration information for the tunnel. Error: An error occurred error

Type Severity

KMD_DPD_IKE_SERVER_NOT_FOUND
System Log Message

Unable to send DPD reply to remote peer remote-address:remote-port: no IKE server instance for local peer local-address:local-port The key management process (kmd) could not retrieve the Internet Key Exchange (IKE) server instance referenced by the indicated local peer (address and port), so it could not reply to the indicated remote peer (address and port) from the local peer.

Description

KMD_DPD_FAILOVER_NO_ACTIVE_PEER

323

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

KMD_DPD_INVALID_ADDRESS
System Log Message Description

Unable to send DPD reply: local peer local-address; remote peer remote-address One of the indicated peer addresses (local or remote) was invalid, so the key management process (kmd) could not send a dead peer detection (DPD) reply to the remote peer. Error: An error occurred error

Type Severity

KMD_DPD_INVALID_SEQUENCE_NUMBER
System Log Message

Unable to send DPD reply: remote peer remote-address:remote-port provided invalid zero sequence number to local peer local-address:local-port The indicated remote peer (address and port) provided a zero sequence number, which is invalid, to the indicated local peer (address and port). As a result, the key management process (kmd) could not send a dead peer detection (DPD) reply to the remote peer. Error: An error occurred error

Description

Type Severity

KMD_DPD_NO_LOCAL_ADDRESS
System Log Message

Unable to send DPD hello message from local peer local-address/local-port: address not found in instance service-set The indicated service set did not include an entry for the indicated local peer (address and port), so the key management process (kmd) could not send a dead peer detection (DPD) hello message from that peer. Error: An error occurred error

Description

Type Severity

KMD_DPD_REMOTE_ADDRESS_CHANGED
System Log Message Description

Remote peer address for tunnel tunnel-name changed from old-address to new-address The remote peer address in the configuration for the indicated tunnel changed to a new value as indicated.

324

KMD_DPD_IKE_SERVER_NOT_FOUND

Chapter 42: KMD System Log Messages

Type Severity

Event: This message reports an event, not an error notice

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 The Internet Key Exchange (IKE) server instance for the indicated service set did not include an entry for the indicated remote peer (address and port), so the key management process (kmd) could not send a dead peer detection (DPD) reply. Error: An error occurred error

Description

Type Severity

KMD_DPD_UNEXPECTED_IKE_STATUS
System Log Message

DPD reply to remote peer remote-address:remote-port failed with unexpected status status for IKE server instance ike-instance A dead peer detection (DPD) reply sent to the indicated remote peer (address and port) failed and returned the indicated Internet Key Exchange (IKE) status code for the indicated IKE instance. Error: An error occurred error

Description

Type Severity

KMD_PM_AUTH_ALGORITHM_INVALID
System Log Message

Invalid authentication algorithm auth-algorithm-id negotiated in transform transform-id for use by protocol-name in tunnel tunnel-name During Internet Key Exchange (IKE) Phase 2 negotiation of the indicated transform, the indicated authentication algorithm was chosen to be used by the indicated protocol (Authentication Header [AH] or Encapsulating Security Payload [ESP]) for the indicated tunnel. The algorithm is not a valid value, so the associated security association (SA) was not established. Error: An error occurred error

Description

Type Severity

KMD_PM_DUPLICATE_LIFE_DURATION
System Log Message

Duplicate SA life duration value given in Quick Mode notification from remote-address:remote-port

KMD_DPD_REMOTE_ADDRESS_CHANGED

325

JUNOS 10.1 System Log Messages Reference

Description

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. Error: An error occurred error

Type Severity

KMD_PM_DYNAMIC_SA_INSTALL_FAILED
System Log Message Description

Unable to install dynamic SA for tunnel tunnel-name Installation of a dynamic security association (SA) failed for the indicated tunnel during Internet Key Exchange (IKE) Phase 2. Error: An error occurred error

Type Severity

KMD_PM_ENCRYPTION_INVALID
System Log Message

Invalid encryption algorithm negotiated in transform transform-id for use by ESP in tunnel tunnel-name During Internet Key Exchange (IKE) Phase 2 negotiation of the indicated transform, an encryption algorithm was chosen to be used by the Encapsulating Security Payload (ESP) protocol for the indicated tunnel. The algorithm is not a valid value, so the associated security association (SA) was not installed to the data path. Error: An error occurred error

Description

Type Severity

KMD_PM_IKE_SERVER_LOOKUP_FAILED
System Log Message Description

No IKE server to connect Phase-1 to remote-peer The IKE Phase-1 negotiation with indicated remote gateway address failed because there is no corresponding IKE server running locally. Error: An error occurred error

Type Severity

KMD_PM_IKE_SERVER_NOT_FOUND
System Log Message

Failed to connect to remote-address:remote-port as there is no IKE server context available in instance service-set

326

KMD_PM_DUPLICATE_LIFE_DURATION

Chapter 42: KMD System Log Messages

Description

There is no local IKE server context in the indicated service set, hence failed to send the SPI delete notification request. Error: An error occurred error

Type Severity

KMD_PM_IKE_SRV_NOT_FOUND_CREATE
System Log Message

Local peer local-address:local-port could not inform remote peer remote-address:remote-port of SA creation failure: IKE server not found The key management process (kmd) could not connect to the indicated remote peer (address and port), because it could not locate a Internet Key Exchange (IKE) server for the indicated local peer (address and port). As a result, it could not notify the remote peer that a security association (SA) was not created. Error: An error occurred error

Description

Type Severity

KMD_PM_IKE_SRV_NOT_FOUND_DELETE
System Log Message

Unable to notify remote peer remote-address:remote-port that SPI was deleted: no IKE server for service set service-set The indicated service set did not have a local Internet Key Exchange (IKE) server context for the indicated remote peer (address and port). As a result, notification about deletion of a security parameter index (SPI) was not sent. Error: An error occurred error

Description

Type Severity

KMD_PM_ILLEGAL_REMOTE_GW_ID
System Log Message

Aborting Phase-1 negotiation. Cannot initiate negotiation with invalid Phase-1 remote remote-peer in instance: service-set The specified remote gateway identity is neither an IPv4 address nor an IPv6 address. Hence Phase-1 negotiation can not be started Error: An error occurred error

Description

Type Severity

KMD_PM_IKE_SERVER_NOT_FOUND

327

JUNOS 10.1 System Log Messages Reference

KMD_PM_INCONSISTENT_P2_IDS
System Log Message

Inconsistent phase-2 (IPsec) identities, local : initiator = local-initiator responder = local-responder remote : initiator = remote-initiator responder = remote-responder Initiator and responder identities at the local end are inconsistent with the remote peer's identities. Quick Mode negotiation is aborted. Error: An error occurred error

Description

Type Severity

KMD_PM_INVALID_LIFE_TYPE
System Log Message

Invalid life type units-type found in the Quick Mode notification from remote-address:remote-port The IKE Quick Mode notification message from the indicated remote gateway and remote port contains invalid life type. Second and Kilobytes are the only supported life types currently. Hence Quick Mode notification payload is dropped. Error: An error occurred error

Description

Type Severity

KMD_PM_KEY_NOT_SUPPORTED
System Log Message Description

Key type type not supported The key management process (kmd) retrieved a key of the indicated type during Internet Key Exchange (IKE) Phase 1. The key type is not one of the supported types, which are public/private and preshared. Error: An error occurred error

Type Severity

KMD_PM_LIFETIME_DUPLICATE
System Log Message

Phase 2 lifetime notification message from remote peer remote-address:remote-port specified duplicate duration During Internet Key Exchange (IKE) Phase 2 negotiation, the indicated remote peer (address and port) sent a lifetime notification message that specified a duplicate value for the security association (SA) lifetime duration. As a result, the key management process (kmd) discarded the notification message.

Description

328

KMD_PM_INCONSISTENT_P2_IDS

Chapter 42: KMD System Log Messages

Type Severity

Error: An error occurred error

KMD_PM_LIFETIME_LENGTH_UNEQUAL
System Log Message

Phase 2 lifetime notification message from remote peer remote-address:remote-port had unequal payload length 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. Error: An error occurred error

Description

Type Severity

KMD_PM_LIFETIME_NO_DURATION
System Log Message

Phase 2 lifetime notification message from remote peer remote-address:remote-port did not define duration During Internet Key Exchange (IKE) Phase 2 negotiation, the indicated remote peer (address and port) sent a lifetime notification message that did not specify a duration for the security association (SA) lifetime. As a result, the key management process (kmd) discarded the notification message. Error: An error occurred error

Description

Type Severity

KMD_PM_LIFETIME_TYPE_UNDEFINED
System Log Message

Phase 2 lifetime notification message from remote peer remote-address:remote-port did not specify life type During Internet Key Exchange (IKE) Phase 2 negotiation, the indicated remote peer (address and port) sent a lifetime notification message that did not specify a life type, making it impossible to determine the lifetime duration for the corresponding security association (SA). As a result, the key management process (kmd) discarded the notification message. Error: An error occurred error

Description

Type Severity

KMD_PM_LIFETIME_DUPLICATE

329

JUNOS 10.1 System Log Messages Reference

KMD_PM_LIFETIME_UNITS_INVALID
System Log Message

Phase 2 lifetime notification message from remote peer remote-address:remote-port specified invalid units type units-type During Internet Key Exchange (IKE) Phase 2 negotiation, the indicated remote peer (address and port) sent a lifetime notification message that specified the indicated type of units for the security association (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. Error: An error occurred error

Description

Type Severity

KMD_PM_NEW_GROUP_UNSUPPORTED
System Log Message Description

New Group mode not supported Internet Key Exchange (IKE) New Group mode is not supported, so an attempt to start New Group negotiation failed. Error: An error occurred error

Type Severity

KMD_PM_NO_LIFETIME
System Log Message

Duplicate life time payloads present in the notification from remote-address:remote-port. Dropping the notification. The IKE Quick Mode notification message from the indicated remote gateway and remote port contains two life type fields and there is no life duration field. Quick Mode notification is being dropped since it has insufficient information about life duration. Error: An error occurred error

Description

Type Severity

KMD_PM_NO_LIFE_TYPE
System Log Message

Quick mode notification from remote-address:remote-port contains lifetime duration without corresponding SA lifetime payload. The IKE Quick Mode notification message from the indicated remote gateway and remote port does not contain life type, hence existing life duration cannot be interpreted to be of a particular life type. Quick Mode notification payload is dropped.

Description

330

KMD_PM_LIFETIME_UNITS_INVALID

Chapter 42: KMD System Log Messages

Type Severity

Error: An error occurred error

KMD_PM_NO_PROPOSAL_FOR_PHASE1
System Log Message

Aborting Phase-1negotiation. No proposal found to initiatenegotiation between local:local-peer and remote remote-peer in instance:service-set It is not possible to start the Phase-1 negotiation to the indicated remote gateway because there is no proposal present. Error: An error occurred error

Description

Type Severity

KMD_PM_NO_SPD_PHASE1_FUNC_PTR
System Log Message Description Type Severity

Phase-1 SPD handler is not registered in instance:service-set Phase-1 negotiation can not be initiated as initialization function failed. Error: An error occurred error

KMD_PM_P1_POLICY_LOOKUP_FAILURE
System Log Message

Policy lookup for Phase-1 [negotiation-role] failed for p1_local=local-peer p1_remote=remote-peer The IKE Phase-1 negotiation with the indicated remote gateway address failed because there is no IKE policy configured for use against the indicated remote gateway. Error: An error occurred error

Description

Type Severity

KMD_PM_P2_POLICY_LOOKUP_FAILURE
System Log Message

Policy lookup for Phase-2 [negotiation-role] failed for p1_local=local-peer p1_remote=remote-peer p2_local=local-prefix p2_remote=remote-prefix The IKE Phase-2 negotiation with the indicated remote gateway address failed because the traffic selectors proposed by the remote gateway address do not match any of the policies configured for the indicated local gateway address. The proposed traffic selectors are indicated by the Phase-2 local and remote IP prefixes.

Description

KMD_PM_NO_LIFE_TYPE

331

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

KMD_PM_PHASE1_GROUP_UNREADABLE
System Log Message Description

Unable to read group attributes from IKE Phase 1 proposal 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. Error: An error occurred error

Type Severity

KMD_PM_PHASE1_GROUP_UNSPECIFIED
System Log Message Description

Used DH group 1 because Phase 1 proposal did not specify group The key management process (kmd) assigned Diffie-Hellman (DH) group 1 to an Internet Key Exchange (IKE) Phase 1 proposal because no group was specified. Event: This message reports an event, not an error error

Type Severity

KMD_PM_PHASE1_IKE_SRV_NOT_FOUND
System Log Message

Unable to perform Phase 1 negotiation with remote peer remote-peer: no local IKE server The key management process (kmd) could not locate an Internet Key Exchange (IKE) server for the local peer. As a result, IKE Phase 1 negotiation failed with the indicated remote peer. Error: An error occurred error

Description

Type Severity

KMD_PM_PHASE1_NO_IDENTITIES
System Log Message

Unable to begin Phase 1 negotiation for local peer service-set and remote peer local-peer in instance remote-peer Internet Key Exchange (IKE) Phase 1 negotiation did not begin, because either the local peer or remote peer was undefined for the indicated service set. Error: An error occurred

Description

Type

332

KMD_PM_P2_POLICY_LOOKUP_FAILURE

Chapter 42: KMD System Log Messages

Severity

error

KMD_PM_PHASE1_NO_SPD_HANDLER
System Log Message Description

No Phase 1 SPD handler registered for service set service-set 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. Error: An error occurred error

Type Severity

KMD_PM_PHASE1_POLICY_LOOKUP_FAIL
System Log Message

Unable to retrieve Phase 1 policy from negotiation-role (local peer local-peer, remote peer remote-peer) The key management process (kmd) could not retrieve a policy from the indicated participant to use during Internet Key Exchange (IKE) Phase 1 negotiation between the indicated local and remote peers. Error: An error occurred error

Description

Type Severity

KMD_PM_PHASE1_POLICY_NOT_FOUND
System Log Message

Unable to find policy for Phase 1 negotiation between local peer local-peer and remote peer remote-peer in service set service-set The key management process (kmd) could not retrieve a policy for Internet Key Exchange (IKE) Phase 1 negotiation between the indicated local and remote peers in the indicated service set. As a result, Phase 1 did not begin. Error: An error occurred error

Description

Type Severity

KMD_PM_PHASE1_POLICY_SEARCH_FAIL
System Log Message Description

No ike-policy found for ike-access-profile: access-profile, instance:service-set The key management process (kmd) could not retrieve the Phase 1 policy referenced by the indicated Internet Key Exchange (IKE) access profile for the indicated dynamic-endpoint service set. Error: An error occurred

Type

KMD_PM_PHASE1_NO_IDENTITIES

333

JUNOS 10.1 System Log Messages Reference

Severity

error

KMD_PM_PHASE1_PROTO_INVALID
System Log Message

Phase 1 transform specified invalid protocol received-value instead of SSH_IKE_PROTOCOL_ISAKMP (expected-value) The indicated protocol in a transform negotiated during Internet Key Exchange (IKE) 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. Error: An error occurred error

Description

Type Severity

KMD_PM_PHASE1_PROTO_NOT_ISAKMP
System Log Message Description

Protocol in IKE Phase 1 proposal was not ISAKMP as expected The protocol in an Internet Key Exchange (IKE) Phase 1 proposal was not the expected value, which is the Internet Security Association and Key Management Protocol (ISAKMP). Error: An error occurred error

Type Severity

KMD_PM_PHASE1_PROTO_TWICE
System Log Message Description

Phase 1 transform included protocol protocol-id twice A transform negotiated during Internet Key Exchange (IKE) Phase 1 specified the indicated protocol twice, which is invalid. The key management process (kmd) rejected the transform. Error: An error occurred error

Type Severity

KMD_PM_PHASE1_TXFORM_INCOMPLETE
System Log Message Description

Phase 1 transform was missing mandatory attributes A transform negotiated during Internet Key Exchange (IKE) Phase 1 did not include values for all attributes. One or more the following was missing: the authentication algorithm, encryption algorithm, or Diffie-Hellman group. The key management process (kmd) rejected the transform.

334

KMD_PM_PHASE1_POLICY_SEARCH_FAIL

Chapter 42: KMD System Log Messages

Type Severity

Error: An error occurred error

KMD_PM_PHASE1_TXFORM_INVALID
System Log Message

Phase 1 transform specified invalid transform ID received-value instead of expected-value 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. Error: An error occurred error

Description

Type Severity

KMD_PM_PHASE2_IDENTITY_MISMATCH
System Log Message

Phase 2 identities did not match: local initiator local-initiator, responder local-responder; remote initiator remote-initiator, responder remote-responder The indicated initiator and responder identities defined by the local peer did not match the indicated identities defined by the remote peer. The key management process (kmd) canceled Internet Key Exchange (IKE) Phase 2 negotiation. Error: An error occurred error

Description

Type Severity

KMD_PM_PHASE2_NOTIF_UNKNOWN
System Log Message

Unknown Phase 2 notification notification-name (type notification-type, size length bytes) from remote-address:remote-port for protocol protocol-id (SPI(size)=data) The indicated Internet Key Exchange (IKE) Phase 2 notification message from the indicated remote peer (address and port) is a type that the key management process (kmd) does not support. As a result, the kmd process discarded the message and Phase 2 negotiation failed. Error: An error occurred error

Description

Type Severity

KMD_PM_PHASE2_POLICY_LOOKUP_FAIL
System Log Message

Unable to retrieve policy for Phase 2 from negotiation-role (Phase 1 local peer local-peer, remote peer remote-peer; Phase 2 local peer local-prefix, remote peer remote-prefix)

KMD_PM_PHASE1_TXFORM_INCOMPLETE

335

JUNOS 10.1 System Log Messages Reference

Description

The key management process (kmd) could not retrieve a policy from the indicated participant to use during Internet Key Exchange (IKE) Phase 2 negotiation for the indicated local and remote peers. The traffic selectors proposed by the remote peer (represented by the indicated Phase 2 IP prefixes) do not match any local peer policies. Error: An error occurred error

Type Severity

KMD_PM_PHASE2_SELECTOR_UNDEFINED
System Log Message Description

Unable to start Phase 2: No traffic-selector addresses defined for SA sa-name 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. Error: An error occurred error

Type Severity

KMD_PM_PROPOSAL_NO_AUTH
System Log Message Description

AH proposal did not define authentication algorithm An Internet Key Exchange (IKE) Phase 2 proposal did not define the authentication algorithm for the Authentication Header (AH) protocol to use. The key management process (kmd) rejected the proposal. Error: An error occurred error

Type Severity

KMD_PM_PROPOSAL_NO_ENCRYPTION
System Log Message Description

ESP proposal did not define encryption algorithm An Internet Key Exchange (IKE) Phase 2 proposal did not define the encryption algorithm for the Encapsulating Security Payload (ESP) protocol to use. The key management process (kmd) rejected the proposal. Error: An error occurred error

Type Severity

336

KMD_PM_PHASE2_POLICY_LOOKUP_FAIL

Chapter 42: KMD System Log Messages

KMD_PM_PROPOSAL_NO_KEY_LENGTH
System Log Message Description

Phase 2 proposal did not specify length for variable key-length cipher cipher An Internet Key Exchange (IKE) Phase 2 proposal did not define the key length for the indicated variable-length cipher. As a result, the key management process (kmd) rejected the proposal. Error: An error occurred error

Type Severity

KMD_PM_PROPOSAL_NULL_ESP
System Log Message Description

ESP was negotiated with null encryption and authentication 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. Error: An error occurred error

Type Severity

KMD_PM_PROPOSAL_PROTOCOL_INVALID
System Log Message Description

Protocol protocol-id in Phase 2 proposal was invalid (was not AH or ESP) An Internet Key Exchange (IKE) Phase 2 proposal specified the indicated protocol, which is invalid. The acceptable protocols as Authentication Header (AH) and Encapsulating Security Payload (ESP). The key management process (kmd) rejected the proposal. Error: An error occurred error

Type Severity

KMD_PM_PROTO_INVALID
System Log Message Description

Invalid protocol protocol-id was negotiated for SA sa-name During Internet Key Exchange (IKE) Phase 2, the indicated protocol was chosen for the indicated security association (SA). It is not a valid value, so the SA was not established. Error: An error occurred

Type

KMD_PM_PROPOSAL_NO_KEY_LENGTH

337

JUNOS 10.1 System Log Messages Reference

Severity

error

KMD_PM_PROTO_IPCOMP_UNSUPPORTED
System Log Message Description

Unsupported IPComp protocol was negotiated for SA sa-name During Internet Key Exchange (IKE) Phase 2, the IP Payload Compression Protocol (IPComp) was chosen for the indicated security association (SA). IPComp is not supported, so the SA was not established. Error: An error occurred error

Type Severity

KMD_PM_PROTO_ISAKMP_RESV_UNSUPP
System Log Message Description

Unsupported protocol ISAKMP or RESERVED was negotiated for SA sa-name During Internet Key Exchange (IKE) Phase 2, either Internet Security Association and Key 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. Error: An error occurred error

Type Severity

KMD_PM_PROTO_NOT_NEGOTIATED
System Log Message Description

No protocol negotiated for SA sa-name While verifying the results of Internet Key Exchange (IKE) Phase 2, the key management process (kmd) determined that no protocol was negotiated for the indicated security association (SA). The SA was not established. Error: An error occurred error

Type Severity

KMD_PM_REMOTE_PEER_INVALID
System Log Message

Phase 1 negotiation failed: remote address remote-peer in instance service-set is invalid Internet Key Exchange (IKE) Phase 1 negotiation failed because the indicated remote peer address in the indicated service set is not a valid IP version 4 (IPv4) or IP version 6 (IPv6) address.

Description

338

KMD_PM_PROTO_INVALID

Chapter 42: KMD System Log Messages

Type Severity

Error: An error occurred error

KMD_PM_SA_CFG_NOT_FOUND
System Log Message Description

Unable to install negotiated Phase 2 values: SA sa-name configuration not found The key management process (kmd) could not retrieve configuration information for the indicated security association (SA), and so could not record the values that were negotiated for the SA during Internet Key Exchange (IKE) Phase 2. The SA was not established. Error: An error occurred error

Type Severity

KMD_PM_SA_DELETE_REJECT
System Log Message

Rejected SA deletion request for service set service-set: SPI size (size) is not 4 (local peer local-address:local-port, remote peer remote-address:remote-port) The key management process (kmd) discarded a message that requested deletion of a security association (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. Error: An error occurred error

Description

Type Severity

KMD_PM_SA_INDEX_GEN_FAILED
System Log Message Description

Unable to generate pair index for SA sa-name in service set service-set The key management process (kmd) could not generate a pair index for the indicated security association (SA) in the indicated service set. The kmd process canceled Internet Key Exchange (IKE) Phase 2 negotiation. Error: An error occurred error

Type Severity

KMD_PM_SA_PEER_ABSENT
System Log Message

No active peer found in tunnel configuration block sa-name

KMD_PM_REMOTE_PEER_INVALID

339

JUNOS 10.1 System Log Messages Reference

Description

Failed to find active peer information in the tunnel configuration block. Hence unable to send SA delete notifications to the peer. Error: An error occurred error

Type Severity

KMD_PM_SA_PEER_NOT_FOUND
System Log Message Description

Unable to find active peer for SA sa-name The key management process (kmd) could not retrieve information about an active peer from the configuration for the indicated security association (SA). As a result, it could not notify peers that an SA was deleted. Error: An error occurred error

Type Severity

KMD_PM_SPI_DELETE_REJECT
System Log Message

IKE Phase-2 delete:In instance service-set rejecting request to delete SPI size sizeu != 4 Local gateway local-address:local-port, Remote gateway remote-address:remote-port The SPI size in the delete notification is invalid. Hence delete request is rejected. Quick Mode notification payload is dropped. Error: An error occurred error

Description

Type Severity

KMD_PM_UNEQUAL_PAYLOAD_LENGTH
System Log Message

Inconsistent payload lengths in Quick Mode responder life time notification from remote-address:remote-port IKE Quick Mode notification is dropped because of unequal payload length received in the message. Error: An error occurred error

Description

Type Severity

KMD_PM_UNINITIALISE_ERROR
System Log Message

Invalid policy managerhandle to uninitialize service-set

340

KMD_PM_SA_PEER_ABSENT

Chapter 42: KMD System Log Messages

Description

Failed to uninitialize the Policy manager object while deleting the indicated service set. Error: An error occurred error

Type Severity

KMD_PM_UNINITIALIZE_FAILED
System Log Message Description

Unable to uninitialize service set service-set: invalid policy manager handle The key management process could not delete the indicated service set, because lack of a valid handle prevented the kmd process from uninitializing the policy manager object for the service set. Error: An error occurred error

Type Severity

KMD_PM_UNKNOWN_P1_IDENTITIES
System Log Message

Failed to initiate the Phase-1 negotiation for local:local-peer and remote:remote-peer in instance:service-set Phase-1 negotiation can not be started because either the local gateway identity or the remote gateway identity is unknown. Error: An error occurred error

Description

Type Severity

KMD_PM_UNKNOWN_PHASE2_ENTITIES
System Log Message Description

No Phase-2 entities present in tunnel configuration block sa-name Unable to initiate Phase-2 negotiation because of unknown local and remote traffic selectors in the indicated security association configuration block. For Adaptive Service PIC, the security association configuratin block refers to the tunnel configured under a service set with a given rule name and term name. Error: An error occurred error

Type Severity

KMD_PM_UNINITIALISE_ERROR

341

JUNOS 10.1 System Log Messages Reference

KMD_PM_UNKNOWN_QM_NOTIFICATION
System Log Message

Unknown Quick mode notification notification-name (notification-type) (size lengthubytes) from remote-address:remote-port for protocol=protocol-idd spi(sizeu)=data The notification message sent by the indicated remote gateway and remote port is not recognized. Hence Quick Mode notification payload is dropped. Error: An error occurred error

Description

Type Severity

KMD_PM_UNSUPPORTED_KEY
System Log Message Description

Key type = type, not supported The specified key type is unsupported. Public/Private and Pre-shared key are are the only types supported presently. Error: An error occurred error

Type Severity

KMD_PM_UNSUPPORTED_MODE
System Log Message Description

New group mode not supported currently The IKE New Group mode negotiations failed, because this is not a supported feature currently. Error: An error occurred error

Type Severity

KMD_SNMP_EXTRA_RESPONSE
System Log Message Description

PIC pic-slot sent additional response after reply to SNMP query: error-message The indicated Physical Interface Card (PIC) sent an additional unexpected message after it responded to a request from the key management process (kmd) for Simple Network Management Protocol (SNMP) statistics about IP Security (IPSec) security associations (SAs). As a result, the kmd process discarded the initial response. Error: An error occurred error

Type Severity

342

KMD_PM_UNKNOWN_QM_NOTIFICATION

Chapter 42: KMD System Log Messages

KMD_SNMP_FATAL_ERROR
System Log Message Description

Fatal SNMP error occurred: error-message The key management process (kmd) could not retrieve Simple Network Management Protocol (SNMP) statistics about IP Security (IPSec) security associations (SAs), because the indicated fatal SNMP error occurred. Error: An error occurred error

Type Severity

KMD_SNMP_IKE_SERVER_NOT_FOUND
System Log Message

Unable to fulfill SNMP request: could not fetch IKE server context for service set service-set The key management process (kmd) could not retrieve the Internet Key Exchange (IKE) server context for the indicated service set. As a result, it could not process a request for Simple Network Management Protocol (SNMP) statistics. Error: An error occurred error

Description

Type Severity

KMD_SNMP_MALLOC_FAILED
System Log Message Description

Unable to allocate memory for reply buffer; SNMP query to PIC pic-slot failed The key management process (kmd) could not allocate memory for the buffer it uses to store Simple Network Management Protocol (SNMP) statistics about IP Security (IPSec) security associations (SAs). As a result, it could not retrieve statistics from the indicated Physical Interface Card (PIC). Error: An error occurred error

Type Severity

KMD_SNMP_PIC_CONNECTION_FAILED
System Log Message Description

Unable to connect to PIC pic-slot; SNMP query failed The key management process (kmd) could not open a connection to the indicated Physical Interface Card (PIC). As a result, it could not retrieve Simple Network Management Protocol (SNMP) statistics about IP Security (IPSec) security associations (SAs).

KMD_SNMP_FATAL_ERROR

343

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

KMD_SNMP_PIC_NO_RESPONSE
System Log Message Description

PIC pic-slot did not respond to SNMP query: error-message The indicated Physical Interface Card (PIC) did not respond to a request from the key management process (kmd) for Simple Network Management Protocol (SNMP) statistics about IP Security (IPSec) security associations (SAs). Error: An error occurred error

Type Severity

KMD_SNMP_PIC_SLOT_NOT_FOUND
System Log Message Description

Unable to retrieve slot information for PIC pic-slot; SNMP query failed The key management process (kmd) could not retrieve information about the slot housing the indicated Physical Interface Card (PIC). As a result, it could not retrieve Simple Network Management Protocol (SNMP) statistics about IP Security (IPSec) security associations (SAs) from the PIC. Error: An error occurred error

Type Severity

KMD_VPN_DFBIT_STATUS_MSG
System Log Message Description Type Severity

The DF-BIT for VPN vpn-name has been set to argument. VPN DF bit status has been set. Event: This message reports an event, not an error info

KMD_VPN_DOWN_ALARM_USER
System Log Message Description Type Severity

VPN vpn-name from remote-address is down. Notifiication to user that VPN monitor detects IPSec SA is down. Event: This message reports an event, not an error info

344

KMD_SNMP_PIC_CONNECTION_FAILED

Chapter 42: KMD System Log Messages

KMD_VPN_UP_ALARM_USER
System Log Message Description Type Severity

VPN vpn-name from remote-address is up. Notifiication to user that VPN monitor detects IPSec SA is up. Event: This message reports an event, not an error info

KMD_VPN_UP_ALARM_USER

345

JUNOS 10.1 System Log Messages Reference

346

KMD_VPN_UP_ALARM_USER

Chapter 43

L2ALD System Log Messages

This chapter describes messages with the L2ALD prefix. They are generated by the Layer 2 address learning process (l2ald), which supports the dynamic acquisition of information about media access control (MAC) addresses in a Layer 2 bridge environment.

L2ALD_DUPLICATE_RBEB_MAC
System Log Message

Duplicate RBEB mac has been detected (mac-address). LE already exists with pbbn_id : pbbn-id. Rejecting LE create with pbbn_id :new-pbbn-id The l2 learning process (l2ald) already has this particular BEB MAC existing for a different PBBN ID. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

L2ALD_GENCFG_OP_FAILED
System Log Message

Unable to complete gencfg operation operation (major type, minor subtype): error-message The Layer 2 address learning process (l2ald) could not send Layer 2 forwarding-related information to the Packet Forwarding Engines, because the indicated operation failed during configuration generation. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

L2ALD_DUPLICATE_RBEB_MAC

347

JUNOS 10.1 System Log Messages Reference

L2ALD_IPC_MESSAGE_ERROR
System Log Message

Message (type message-type, subtype message-subtype, opcode message-opcode) received with error error-message The Layer 2 address learning process (l2ald) detected an error in an interprocess communication (IPC) message with the indicated characteristics. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

L2ALD_IPC_MESSAGE_INVALID
System Log Message

Invalid message received (message type message, subtype message-type): message-subtype The Layer 2 address learning process (l2ald) received a message with the indicated characteristics. The message was invalid for the indicated reason. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

L2ALD_IPC_MESSAGE_SEND_FAILED
System Log Message Description

Unable to send IPC message to peer-name identifier The Layer 2 address learning process (l2ald) could not send an interprocess communication (IPC) message to the indicated Layer 2 peer. Error: An error occurred warning Contact your technical support representative.

Type Severity Action

L2ALD_IPC_PIPE_WRITE_ERROR
System Log Message

Unable to write on pipe: error-message

348

L2ALD_IPC_MESSAGE_ERROR

Chapter 43: L2ALD System Log Messages

Description

The Layer 2 address learning process (l2ald) could not write to an interprocess communication (IPC) pipe for the indicated reason. Error: An error occurred error One possible reason is that there was no reader for the pipe. Contact your technical support representative.

Type Severity Cause Action

L2ALD_MAC_LIMIT_REACHED_BD
System Log Message

Limit on learned MAC addresses reached for routing instance 'routing-instance', domain 'bridge-domain:vlan-id'; current count is count The Layer 2 address learning process (l2ald) stopped adding addresses to the MAC address table that were learned by interfaces in the indicated bridging domain, because the indicated count of learned addresses exceeds the configured or default limit for the bridge-domain. Event: This message reports an event, not an error error Increase the limit on addresses learned by interfaces in the bridge domain, by increasing the value of the 'interface-mac-limit' statement at the [edit routing-instances <routing-instance-name> bridge-domains <bridge-domain-name> bridge-options] hierarchy level.

Description

Type Severity Action

L2ALD_MAC_LIMIT_REACHED_GLOBAL
System Log Message Description

Global limit on learned MAC addresses reached; current count is count The Layer 2 address learning process (l2ald) stopped adding addresses to the MAC address table, because the indicated count of learned addresses exceeds the limit for the router. Event: This message reports an event, not an error error Increase the limit on addresses learned by the interfaces on the router by increasing the value of the 'global-mac-limit' statement at the [edit protocols l2-learning] hierarchy level.

Type Severity Action

L2ALD_IPC_PIPE_WRITE_ERROR

349

JUNOS 10.1 System Log Messages Reference

L2ALD_MAC_LIMIT_REACHED_IF
System Log Message Description

Limit on learned MAC addresses reached for interface-name; current count is count The Layer 2 address learning process (l2ald) stopped adding addresses to the MAC address table that were learned by the indicated interface, because the indicated count of learned addresses exceeds the limit configured for the interface. Event: This message reports an event, not an error error Increase the limit on addresses learned by the interface by increasing the value of the 'interface-mac-limit' statement at the appropriate location under the [edit routing-instances <routing-instance-name> bridge-domains <bridge-domain-name> bridge-options] or the [edit routing-instances <routing-instance-name> protocols vpls] hierarchy level.

Type Severity Action

L2ALD_MAC_LIMIT_REACHED_IFBD
System Log Message Description

Limit on learned MAC addresses reached for interface-name; current count is count The Layer 2 address learning process (l2ald) stopped adding addresses to the MAC address table that were learned by the indicated interface:vlan-id, because the indicated count of learned addresses exceeds the limit configured for the interface:vlan-id. Event: This message reports an event, not an error error Increase the limit on addresses learned by the interface by increasing the value of the 'interface-mac-limit' statement at the appropriate location under the [edit routing-instances <routing-instance-name> bridge-domains <bridge-domain-name> bridge-options] or the [edit routing-instances <routing-instance-name> protocols vpls] hierarchy level.

Type Severity Action

L2ALD_MAC_LIMIT_REACHED_RTT
System Log Message

Limit on learned MAC addresses reached for routing instance 'routing-instance'; current count is count The Layer 2 address learning process (l2ald) stopped adding addresses to the MAC address table that were learned by interfaces in the indicated routing instance, because the indicated count of learned addresses exceeds the configured or default limit for the routing-instance. Event: This message reports an event, not an error

Description

Type

350

L2ALD_MAC_LIMIT_REACHED_IF

Chapter 43: L2ALD System Log Messages

Severity Action

error Increase the limit on addresses learned by interfaces in the routing-instance, by increasing the value of the '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 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 the indicated count of learned addresses no longer exceeds the limit configured for the domain. Event: This message reports an event, not an error error The probable reason that the count of addresses went below the limit is that addresses in the table reached the age limit and were removed.

Description

Type Severity Cause

L2ALD_MAC_LIMIT_RESET_GLOBAL
System Log Message Description

Resumed adding MAC addresses for router; current count is count The Layer 2 address learning process (l2ald) resumed adding addresses to the MAC address table, because the indicated count of learned addresses no longer exceeds the configured limit. Event: This message reports an event, not an error error The probable reason that the count of addresses went below the limit is that addresses in the table reached the age limit and were removed.

Type Severity Cause

L2ALD_MAC_LIMIT_RESET_IF
System Log Message Description

Resumed adding MAC addresses learned by interface-name; current count is count The Layer 2 address learning process (l2ald) resumed adding addresses to the MAC address table that were learned by the indicated interface, because the indicated count of learned addresses no longer exceeds the limit configured for the interface. Event: This message reports an event, not an error

Type

L2ALD_MAC_LIMIT_REACHED_RTT

351

JUNOS 10.1 System Log Messages Reference

Severity Cause

error The probable reason that the count of addresses went below the limit is that addresses in the table reached the age limit and were removed.

L2ALD_MAC_LIMIT_RESET_RTT
System Log Message

Resumed adding MAC addresses learned from routing instance 'routing-instance'; current count is count 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 the indicated count of learned addresses no longer exceeds the limit configured for the instance. Event: This message reports an event, not an error error The probable reason that the count of addresses went below the limit is that addresses in the table reached the age limit and were removed.

Description

Type Severity Cause

L2ALD_MAC_MOVE_NOTIFICATION
System Log Message Description

MAC Moves detected in the system When the same MAC address is learned on a different interface, or on the same interface but a different unit number, it is considered a MAC move. When this happens frequently for a specific time duration, a notification is sent Event: This message reports an event, not an error warning The probable reason for mac moves is the loops in the topology or some kind of misconfiguration.

Type Severity Cause

L2ALD_MALLOC_FAILED
System Log Message Description

Unable to allocate memory: error-message The Layer 2 address learning process (l2ald) could not allocate memory while creating a data structure. Error: An error occurred error

Type Severity

352

L2ALD_MAC_LIMIT_RESET_IF

Chapter 43: L2ALD System Log Messages

Action

Contact your technical support representative.

L2ALD_MANAGER_CONNECT
System Log Message Description

Unable to create pipe to Layer 2 address-learning manager: error-message The Layer 2 address learning process (l2ald) could not open a pipe for interprocess communication (IPC) with a Layer 2 address-learning manager process. Error: An error occurred error Contact your technical support representative.

Type Severity Action

L2ALD_NAME_LENGTH_IF_DEVICE
System Log Message Description

Unable to add interface device interface-name; name exceeds limit of length characters The Layer 2 address learning process (l2ald) did not add an entry for the indicated interface device to the interface table, because its name exceeds the indicated limit on the number of characters. Error: An error occurred error Contact your technical support representative.

Type Severity Action

L2ALD_NAME_LENGTH_IF_FAMILY
System Log Message Description

Unable to add interface family interface-family; name exceeds limit of length characters The Layer 2 address learning process (l2ald) did not add an entry for the indicated interface family to the interface table, because its name exceeds the indicated limit on the number of characters. Error: An error occurred error Contact your technical support representative.

Type Severity Action

L2ALD_NAME_LENGTH_IF_LOGICAL
System Log Message

Unable to add logical interface interface-name; name exceeds limit of length characters

L2ALD_MALLOC_FAILED

353

JUNOS 10.1 System Log Messages Reference

Description

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. Error: An error occurred error Contact your technical support representative.

Type Severity Action

L2ALD_PBBN_IFL_REVA
System Log Message

Unable to initialize Provider Backbone Bridging on interface interface-name. It is present on a Rev A card. The Layer 2 address learning process (l2ald) could not initialize the interface for the provider backbone bridging (PBB) feature because the interface is on a revision A card. Error: An error occurred warning Revision A cards do not support provider backbone bridging (PBB) features. Contact your technical support representative.

Description

Type Severity Cause Action

L2ALD_PBBN_REINSTATE_IFBDS
System Log Message

Hardware VCs are being restored for data packet.They were de-programmed because interface-name had an interface on a Rev A card. The Layer 2 address learning process (l2ald) reinstated certain hardware circuits to resume data traffic. The circuits were brought down because the provider backbone bridging (PBB) feature had discovered that one of the interfaces was on a revision A card. Error: An error occurred warning The interface is no longer present on the revision A card. Contact your technical support representative.

Description

Type Severity Cause Action

354

L2ALD_NAME_LENGTH_IF_LOGICAL

Chapter 43: L2ALD System Log Messages

L2ALD_PBBN_RETRACT_IFBDS
System Log Message

Provider Backbone Bridging feature detected on interface interface-name on a Rev A card. VCs are being de-programmed. The Layer 2 address learning process (l2ald) retracted certain hardware circuits to block data traffic. The circuits were brought down because the provider backbone bridging (PBB) feature had discovered that one of the interfaces was on a revision A card. Error: An error occurred warning An interface was discovered on the revision A card. Revision A cards do not support provider backbone bridging (PBB) features. Contact your technical support representative.

Description

Type Severity Cause

Action

L2ALD_PIP_IFD_READ_RETRY
System Log Message

Retry count exceeded trying to read pip-interface from the kernel. Retry count is retry-count The Layer 2 address learning process (l2ald) could not read the provide-in-provider interface (pip0) interface from the kernel. Error: An error occurred critical The chassis process may have been too slow in creating the interface. Contact your technical support representative.

Description

Type Severity Cause Action

L2ALD_PBBN_RETRACT_IFBDS

355

JUNOS 10.1 System Log Messages Reference

356

L2ALD_PIP_IFD_READ_RETRY

Chapter 44

L2CPD System Log Messages

This chapter describes messages with the L2CPD prefix. They are generated by the Layer 2 Control Protocol process (l2cpd), which supports the transmission of control messages for Layer 2 spanning tree protocols in a Layer 2 bridge environment.

L2CPD_ASSERT
System Log Message

Assertion failed for executable-name (PID pid) at line line-number in file 'source-filename': message The source code for the Layer 2 Control Protocol process (l2cpd) includes internal self-consistency tests. The l2cpd process with the indicated executable name and process ID (PID) terminated because the indicated test failed at the indicated line number in the indicated source file. The process created a diagnostic core file for analysis by technical support personnel. Error: An error occurred error Messages that immediately follow this message in the system log might provide information about possible causes. Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core file, if requested.

Description

Type Severity Cause

Action

L2CPD_ASSERT_SOFT
System Log Message

Assertion failed for executable-name (PID pid) at line line-number in file 'source-filename' (message); process continued running The source code for the Layer 2 Control Protocol process (l2cpd) includes internal self-consistency tests. The l2cpd process with the indicated executable name and process 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. Error: An error occurred

Description

Type

L2CPD_ASSERT

357

JUNOS 10.1 System Log Messages Reference

Severity Cause

error Messages that immediately follow this message in the system log might provide information about possible causes. Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core file, if requested.

Action

L2CPD_EXIT
System Log Message

l2cpd process with PID pid exited (was using executable executable-name, version version built by builder on date); caller was address The Layer 2 Control Protocol process (l2cpd) exited. The process had the indicated process ID (PID) and was using an executable with the indicated name, version, and other characteristics. Event: This message reports an event, not an error notice Either a system resource was unavailable, the l2cpd process could not interpret an error, or the indicated user (referred to as a 'caller') terminated the process.

Description

Type Severity Cause

L2CPD_KERNEL_VERSION
System Log Message

Kernel version (kernel-version) of routing sockets was not required version (l2cpd-version) The Layer 2 Control Protocol process (l2cpd) determined that the indicated version of routing sockets, which the kernel supports, is not the version that it requires. Error: An error occurred error Upgrade the kernel package.

Description

Type Severity Action

L2CPD_KERNEL_VERSION_OLD
System Log Message

Kernel version (kernel-version) of routing socket message type message-type is older than the required version (l2cpd-version) 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. Error: An error occurred

Description

Type

358

L2CPD_ASSERT_SOFT

Chapter 44: L2CPD System Log Messages

Severity Action

error Upgrade the kernel package.

L2CPD_KERNEL_VERSION_UNSUPP
System Log Message

Kernel version of routing socket message type 'message-type' was not required version (l2cpd-version) The Layer 2 Control Protocol process (l2cpd) determined that the kernel does not support the version of the indicated routing socket message type that it requires. Error: An error occurred error Upgrade the kernel package.

Description

Type Severity Action

L2CPD_MEMORY_EXCESSIVE
System Log Message Description

Using size KB of memory, percentage-value percent of available The Layer 2 Control Protocol process (l2cpd) was using the indicated amount and percentage of Routing Engine memory, which is considered excessive. Error: An error occurred error Either the l2cpd process is leaking memory or the use of system resources is excessive. Possible causes include misconfigured routing filters or a very complex configured network topology. Increase the amount of RAM in the Routing Engine.

Type Severity Cause

Action

L2CPD_MGMT_TIMEOUT
System Log Message Description

Peer peer-name timed out The Layer 2 Control Protocol process (l2cpd) did not receive input from the indicated management peer within the timeout period. Error: An error occurred warning Messages that immediately follow this message in the system log might provide information about possible causes.

Type Severity Cause

L2CPD_KERNEL_VERSION_OLD

359

JUNOS 10.1 System Log Messages Reference

L2CPD_MIRROR_ERROR
System Log Message Description

Unable to establish mirror connection between Routing Engines: error-message The Layer 2 Control Protocol process (l2cpd) could not establish the mirror connection (which supports nonstop routing) between the master and backup Routing Engines. Error: An error occurred warning The master and backup Routing Engines are running incompatible versions of the JUNOS Software. Update the JUNOS Software to compatible versions on the master and backup Routing Engines.

Type Severity Cause

Action

L2CPD_MIRROR_VERSION_MISMATCH
System Log Message

Mirror version (master-version) on master Routing Enginemaster-is-local is not compatible with version (standby-version) on backupstandby-is-local While trying to establish the mirror connection (which supports nonstop routing) between the master and backup Routing Engines, the Layer 2 Control Protocol process (l2cpd) determined that the versions of JUNOS Software on the Routing Engines were incompatible. Error: An error occurred warning Update the JUNOS Software to compatible versions on the master and backup Routing Engines.

Description

Type Severity Action

L2CPD_PPM_READ_ERROR
System Log Message Description

Read error on pipe from ppmd: reason (error-message) The Layer 2 Control Protocol process (l2cpd) could not read a message available on the read pipe from the periodic packet management process (ppmd). Error: An error occurred error Contact your technical support representative.

Type Severity Action

360

L2CPD_MIRROR_ERROR

Chapter 44: L2CPD System Log Messages

L2CPD_PPM_WRITE_ERROR
System Log Message Description

function-name: write error on pipe to ppmd (error-message) The Layer 2 Control Protocol process (l2cpd) could not write a message on the pipe to the periodic packet management process (ppmd). Error: An error occurred error Contact your technical support representative.

Type Severity Action

L2CPD_RUNTIME_MODULE
System Log Message Description

function-name: runtime was excessive (time) during action of module The indicated operation on the indicated submodule of the Layer 2 Control Protocol process (l2cpd) ran uninterrupted for the indicated period of time, which is considered excessive. Event: This message reports an event, not an error warning The message was logged because task accounting is enabled. The function might be implemented inefficiently.

Type Severity Cause

L2CPD_RUNTIME_OPERATION
System Log Message Description

function-name: runtime was excessive (time) during action of module The indicated operation on the indicated submodule of the Layer 2 Control Protocol process (l2cpd) ran uninterrupted for the indicated period of time, which is considered excessive. Event: This message reports an event, not an error warning The message was logged because task accounting is enabled. The function might be implemented inefficiently.

Type Severity Cause

L2CPD_PPM_WRITE_ERROR

361

JUNOS 10.1 System Log Messages Reference

L2CPD_RUNTIME_TASK
System Log Message

function-name: runtime was excessive (total-time [user-time user, system-time system]) doing action While performing the indicated operation, the indicated function in the Layer 2 Control Protocol process (l2cpd) ran uninterrupted for the indicated period of time (the sum of the indicated user and system times), which is considered excessive. Event: This message reports an event, not an error warning The message was logged because task accounting is enabled. The function might be implemented inefficiently.

Description

Type Severity Cause

L2CPD_RUNTIME_TOTAL
System Log Message

function-name: runtime was excessive (total of time in count callbacks) after action of module After the indicated operation on the indicated submodule of the Layer 2 Control Protocol process (l2cpd), several functions ran uninterrupted in the indicated number of callbacks for the indicated period of time, which is considered excessive. Event: This message reports an event, not an error warning The message was logged because task accounting is enabled. The function might be implemented inefficiently.

Description

Type Severity Cause

L2CPD_TASK_BEGIN
System Log Message Description

l2cpd process started (version l2cpd-version built on date by builder) The Layer 2 Control Protocol process (l2cpd) started. It was assigned the indicated process ID (PID) and was using an executable with the indicated name, version, and build date. Event: This message reports an event, not an error notice

Type Severity

L2CPD_TASK_CHILD_KILLED
System Log Message

Child process 'task-name' terminated by SIGsignal-name core-dump-status

362

L2CPD_RUNTIME_TASK

Chapter 44: L2CPD System Log Messages

Description

While a child process of the Layer 2 Control Protocol process (l2cpd) was performing the indicated operation, it terminated in response to the indicated signal. Event: This message reports an event, not an error error

Type Severity

L2CPD_TASK_CHILD_STOPPED
System Log Message Description

Child process 'task-name' stopped by SIGsignal-name 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. Event: This message reports an event, not an error error

Type Severity

L2CPD_TASK_FORK
System Log Message Description

Unable to fork task-name: error-message The Layer 2 Control Protocol process (l2cpd) could not create the indicated child process. Error: An error occurred error

Type Severity

L2CPD_TASK_GETWD
System Log Message Description

getwd() failed for error-message The Layer 2 Control Protocol process (l2cpd) invoked the getwd() system call, which failed. Error: An error occurred error It is possible that the kernel lacked the resources needed to fulfill the request. The l2cpd process continued operating.

Type Severity Cause

L2CPD_TASK_MASTERSHIP
System Log Message

Assumed mastership

L2CPD_TASK_CHILD_KILLED

363

JUNOS 10.1 System Log Messages Reference

Description

The Layer 2 Control Protocol process (l2cpd) became active when the Routing Engine on which it was running assumed mastership. Event: This message reports an event, not an error info

Type Severity

L2CPD_TASK_NO_REINIT
System Log Message Description

Unable to reinitialize The Layer 2 Control Protocol process (l2cpd) did not reinitialize as requested, because it was running in a state that did not allow reconfiguration. Error: An error occurred error

Type Severity

L2CPD_TASK_PID_CLOSE
System Log Message Description

Unable to close and remove PID file filename: error-message The Layer 2 Control Protocol process (l2cpd) could not close and remove the file that records its process ID (PID), which serves to prevent multiple instances of the l2cpd process from running simultaneously. Error: An error occurred error

Type Severity

L2CPD_TASK_PID_LOCK
System Log Message Description

flock(filename, LOCK_EX): error-message The Layer 2 Control Protocol process (l2cpd) could not lock the file that records its process ID (PID), which serves to prevent multiple instances of the l2cpd process from running simultaneously. Error: An error occurred error

Type Severity

L2CPD_TASK_PID_WRITE
System Log Message

Unable to write to PID file filename: error-message

364

L2CPD_TASK_MASTERSHIP

Chapter 44: L2CPD System Log Messages

Description

The Layer 2 Control Protocol process (l2cpd) could not write to the file that records its process ID (PID), which serves to prevent multiple instances of the l2cpd process from running simultaneously. Error: An error occurred error

Type Severity

L2CPD_TASK_REINIT
System Log Message Description Type Severity

Reinitialized The Layer 2 Control Protocol process (l2cpd) reinitialized. Event: This message reports an event, not an error info

L2CPD_TASK_SIGNAL_IGNORE
System Log Message Description

Unable to register SIGsignal-name to be ignored: error-message The Layer 2 Control Protocol process (l2cpd) informed the kernel that it wished to ignore the indicated signal, but the kernel did not process the request. Error: An error occurred error

Type Severity

L2CPD_TERMINATE_ACTIVE
System Log Message Description

Exited with active tasks: task-name After receiving multiple termination requests, the Layer 2 Control Protocol process (l2cpd) exited without performing the indicated cleanup tasks. Event: This message reports an event, not an error notice

Type Severity

L2CPD_TERMINATE_SIGNAL
System Log Message Description

Exited after receiving termination signal signal-name In response to the indicated termination request, the Layer 2 Control Protocol process (l2cpd) terminated adjacencies with neighbors and shut down. Event: This message reports an event, not an error

Type

L2CPD_TASK_PID_WRITE

365

JUNOS 10.1 System Log Messages Reference

Severity

notice

L2CPD_TRACE_FAILED
System Log Message Description

Unable to write to trace file filename The Layer 2 Control Protocol process (l2cpd) could not write to the indicated trace file, and stopped attempting to do so. The next commit of the configuration database will reenable tracing. Event: This message reports an event, not an error error

Type Severity

L2CPD_XSTP_SHUTDOWN_FAILED
System Log Message Description

Unable to shut down error-message module 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. Error: An error occurred error

Type Severity

366

L2CPD_TERMINATE_SIGNAL

Chapter 45

L2TPD System Log Messages

This chapter describes messages with the L2TPD prefix. They are generated by the Layer 2 Tunneling Protocol (L2TP) process (l2tpd), which provides services that enable tunneling of Point-to-Point Protocol (PPP) sessions across a Layer 3 IP network.

L2TPD_COS_PROFILE_ADD
System Log Message

Unable to add CoS profile profile-name (L2TP tunnel tunnel-id, session session-id): error-message The Layer 2 Tunneling Protocol process (l2tpd) could not add the indicated class-of-service (CoS) profile to the indicated session on the indicated tunnel, which is associated with a user. Error: An error occurred error Remove the CoS profile from the RADIUS database or contact your technical support representative.

Description

Type Severity Action

L2TPD_COS_PROFILE_DELETE
System Log Message Description

Unable to delete CoS profile (L2TP tunnel tunnel-id, session session-id): error-message The Layer 2 Tunneling Protocol process (l2tpd) could not delete a class-of-service (CoS) profile from the indicated session on the indicated tunnel, which is associated with a user. Error: An error occurred error Remove the CoS profile from the RADIUS database or contact your technical support representative.

Type Severity Action

L2TPD_COS_PROFILE_ADD

367

JUNOS 10.1 System Log Messages Reference

L2TPD_DB_ADD_FAILED
System Log Message Description

Unable to add node for node-name to internal database The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not add the indicated node to the in-memory database. Error: An error occurred error

Type Severity

L2TPD_DB_DELETE_FAILED
System Log Message Description

Unable to delete node for node-name from internal database The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not delete the indicated node to the in-memory database. Error: An error occurred error

Type Severity

L2TPD_DB_INIT_FAILED
System Log Message Description

Unable to initialize root node object-name in internal database: error-message The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not initialize the root node for the indicated object in the in-memory database. Error: An error occurred error

Type Severity

L2TPD_DB_TUN_GRP_ALLOC_FAILED
System Log Message Description

Unable to allocate memory for tunnel group The Layer 2 Tunneling Protocol process (l2tpd) could not allocate memory for the data structure used to record tunnel group information. Error: An error occurred error

Type Severity

368

L2TPD_DB_ADD_FAILED

Chapter 45: L2TPD System Log Messages

L2TPD_DEFAULT_PROTO_CREATE_FAIL
System Log Message Description Type Severity

Unable to create default L2TP module The Layer 2 Tunneling Protocol process (l2tpd) could not create a default L2TP module. Error: An error occurred error

L2TPD_EVLIB_CREATE_FAILED
System Log Message Description

Unable to create event context: error-message The Layer 2 Tunneling Protocol process (l2tpd) could not create a context for handling asynchronous events. Error: An error occurred emergency

Type Severity

L2TPD_EVLIB_FD_DEREGISTER_FAILED
System Log Message Description

Unable to deregister file descriptor: not registered The Layer 2 Tunneling Protocol process (l2tpd) could not deregister a file descriptor, because it did not exist. Error: An error occurred error

Type Severity

L2TPD_EVLIB_FD_DESELECT_FAILED
System Log Message Description Type Severity

Unable to deselect file descriptor: error-message The Layer 2 Tunneling Protocol process (l2tpd) could not deselect a file descriptor. Error: An error occurred error

L2TPD_EVLIB_FD_NOT_REGISTERED
System Log Message

No file descriptor registered

L2TPD_DEFAULT_PROTO_CREATE_FAIL

369

JUNOS 10.1 System Log Messages Reference

Description

The Layer 2 Tunneling Protocol process (l2tpd) could not find a registered file descriptor while attempting to set an event mask. Error: An error occurred error

Type Severity

L2TPD_EVLIB_FD_SELECT_FAILED
System Log Message Description

Unable to select file descriptor for events event-id: error-message The Layer 2 Tunneling Protocol process (l2tpd) could not select the file descriptor for the indicated events. Error: An error occurred error

Type Severity

L2TPD_EVLIB_TIMER_CLEAR_FAILED
System Log Message Description

Unable to clear event timer: error-message The Layer 2 Tunneling Protocol process (l2tpd) could not clear an event timer for the indicated reason. Error: An error occurred error

Type Severity

L2TPD_EVLIB_TIMER_SET_FAILED
System Log Message Description

Unable to set event timer: error-message The Layer 2 Tunneling Protocol process (l2tpd) could not set an event timer for the indicated reason. Error: An error occurred error

Type Severity

L2TPD_FILTER_FILE_OPEN_FAILED
System Log Message Description

Unable to open file filename The Layer 2 Tunneling Protocol process (l2tpd) could not open the indicated filter file. Error: An error occurred

Type

370

L2TPD_EVLIB_FD_NOT_REGISTERED

Chapter 45: L2TPD System Log Messages

Severity

error

L2TPD_GLOBAL_CFG_ADD_FAILED
System Log Message Description

Unable to add global configuration for PIC pic-slot (errno error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not add the global configuration for the indicated Physical Interface Card (PIC). Error: An error occurred error

Type Severity

L2TPD_GLOBAL_CFG_CHANGE_FAILED
System Log Message Description

Unable to change global configuration for PIC pic-slot (errno error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not change the global configuration for the indicated Physical Interface Card (PIC). Error: An error occurred error

Type Severity

L2TPD_GLOBAL_CFG_DELETE_FAILED
System Log Message Description

Unable to delete global configuration for PIC pic-slot (errno error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not delete the global configuration for the indicated Physical Interface Card (PIC). Error: An error occurred error

Type Severity

L2TPD_IFD_ADD_FAILED
System Log Message Description

function-name: unable to add interface device interface-name The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not add the indicated interface device to the in-memory database. Error: An error occurred error

Type Severity

L2TPD_FILTER_FILE_OPEN_FAILED

371

JUNOS 10.1 System Log Messages Reference

L2TPD_IFD_DELETE_FAILED
System Log Message Description

function-name: unable to delete interface device interface-name The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not delete the indicated interface device from the in-memory database. Error: An error occurred error

Type Severity

L2TPD_IFD_MSG_REGISTER_FAILED
System Log Message Description

Unable to register message handler for interface device: error-message The Layer 2 Tunneling Protocol process (l2tpd) could not register an interface device message handler. Error: An error occurred error

Type Severity

L2TPD_IFD_ROOT_ALLOC_FAILED
System Log Message Description

Unable to allocate memory for interface device root node: error-message The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not allocate memory in the in-memory database for the root node for an interface device. Error: An error occurred error

Type Severity

L2TPD_IFL_ADD_FAILED
System Log Message Description

function-name: unable to add interface interface-name The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not add the indicated logical interface to the in-memory database. Error: An error occurred error

Type Severity

372

L2TPD_IFD_DELETE_FAILED

Chapter 45: L2TPD System Log Messages

L2TPD_IFL_DELETE_FAILED
System Log Message Description

function-name: unable to delete interface interface-name The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not delete the indicated logical interface from the in-memory database. Error: An error occurred error

Type Severity

L2TPD_IFL_MSG_REGISTER_FAILED
System Log Message Description

Unable to register message handler for interface: error-message The Layer 2 Tunneling Protocol process (l2tpd) could not register a logical interface message handler. Error: An error occurred error

Type Severity

L2TPD_IFL_NOT_FOUND
System Log Message Description

Unable to find logical interface (L2TP tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) could not retrieve a logical interface in the indicated tunnel and session. Error: An error occurred error

Type Severity

L2TPD_IFL_ROOT_ALLOC_FAILED
System Log Message Description

Unable to allocate memory for interface root node: error-message The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not allocate memory in the in-memory database for the root node for a logical interface. Error: An error occurred error

Type Severity

L2TPD_IFL_DELETE_FAILED

373

JUNOS 10.1 System Log Messages Reference

L2TPD_INSTANCE_CREATE_FAILED
System Log Message Description

Unable to create L2TP instance tunnel-group The Layer 2 Tunneling Protocol process (l2tpd) could not create an L2TP instance for the indicated tunnel group. Error: An error occurred error

Type Severity

L2TPD_INSTANCE_RESTART_FAILED
System Log Message Description

Unable to trigger restart of L2TP instance tunnel-group The Layer 2 Tunneling Protocol process (l2tpd) could not restart the L2TP instance for the indicated tunnel group. Error: An error occurred error

Type Severity

L2TPD_INTERFACE_ID_NOT_FOUND
System Log Message Description

Unable to find interface ID interface-name The Layer 2 Tunneling Protocol process (l2tpd) could not find the indicated interface ID in the copy of the JUNOS configuration database that it maintains in memory. Error: An error occurred error

Type Severity

L2TPD_MESSAGE_REGISTER_FAILED
System Log Message Description

Unable to register L2TP message handler: error-message The Layer 2 Tunneling Protocol process (l2tpd) could not register an L2TP message handler. Error: An error occurred error

Type Severity

374

L2TPD_INSTANCE_CREATE_FAILED

Chapter 45: L2TPD System Log Messages

L2TPD_MLPPP_BUNDLE_ALLOC_FAILED
System Log Message Description

Unable to allocate MLPPP bundle The Layer 2 Tunneling Protocol process (l2tpd) could not allocate memory for a multilink Point-to-Point Protocol (MLPPP) bundle. Error: An error occurred error

Type Severity

L2TPD_MLPPP_BUNDLE_CREATE_FAILED
System Log Message Description

Unable to create MLPPP bundle (L2TP tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) could not create a multilink Point-to-Point Protocol (MLPPP) bundle in the indicated tunnel and session. Error: An error occurred error

Type Severity

L2TPD_MLPPP_BUNDLE_INVALID_ID
System Log Message Description

MLPPP bundle ID was invalid The identifier assigned to a multilink Point-to-Point Protocol (MLPPP) bundle was invalid. Error: An error occurred error

Type Severity

L2TPD_MLPPP_COPY_CFG_FAILED
System Log Message Description

Unable to copy MLPPP configuration (L2TP tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) could not copy the multilink Point-to-Point Protocol (MLPPP) configuration for the indicated tunnel and session. Error: An error occurred error

Type Severity

L2TPD_MLPPP_BUNDLE_ALLOC_FAILED

375

JUNOS 10.1 System Log Messages Reference

L2TPD_MLPPP_ID_ALLOC_FAILED
System Log Message Description

Unable to allocate MLPPP ID map The Layer 2 Tunneling Protocol process (l2tpd) could not allocate memory for a multilink Point-to-Point Protocol (MLPPP) identifier map data structure. Error: An error occurred error

Type Severity

L2TPD_MLPPP_ID_BITMAP_ALLOC_FAIL
System Log Message Description

Unable to allocate bitmap field for MLPPP ID map 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. Error: An error occurred error

Type Severity

L2TPD_MLPPP_ID_NODE_ADD_FAILED
System Log Message Description

Unable to add node for bundle bundle to MLPPP ID map The Layer 2 Tunneling Protocol process (l2tpd) could not add a node for the indicated multilink Point-to-Point Protocol (MLPPP) bundle to an MLPPP identifier map data structure. Error: An error occurred error

Type Severity

L2TPD_MLPPP_ID_ROOT_ALLOC_FAILED
System Log Message Description

Unable to allocate root node for MLPPP ID map The Layer 2 Tunneling Protocol process (l2tpd) could not allocate the root note for a multilink Point-to-Point Protocol (MLPPP) identifier map data structure. Error: An error occurred error

Type Severity

376

L2TPD_MLPPP_ID_ALLOC_FAILED

Chapter 45: L2TPD System Log Messages

L2TPD_MLPPP_LINK_CREATE_FAILED
System Log Message Description

Unable to create MLPPP bundle links (L2TP tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) could not create multilink Point-to-Point Protocol (MLPPP) bundle links for the indicated tunnel and session. Error: An error occurred error

Type Severity

L2TPD_MLPPP_LINK_MAX_EXCEEDED
System Log Message

Unable to add link: maximum number of sessions exceeded for MLPPP bundle bundle (L2TP tunnel tunnel-id, session session-id) 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. Error: An error occurred error

Description

Type Severity

L2TPD_MLPPP_POOL_ADDRESS_FAILED
System Log Message

Unable to assign pool address for MLPPP bundle bundle (L2TP tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) could not assign a pool address for the indicated multilink Point-to-Point Protocol (MLPPP) bundle in the indicated tunnel and session. Error: An error occurred error

Description

Type Severity

L2TPD_MLPPP_SESSION_CREATE_FAIL
System Log Message Description

Unable to create MLPPP session (L2TP tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) could not create a multilink Point-to-Point Protocol (MLPPP) session for the indicated tunnel and session. Error: An error occurred error

Type Severity

L2TPD_MLPPP_LINK_CREATE_FAILED

377

JUNOS 10.1 System Log Messages Reference

L2TPD_MLPPP_SESSION_DELETE_FAIL
System Log Message

Unable to delete session for MLPPP bundle bundle (L2TP tunnel tunnel-id, session session-id, errno error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not delete the session configuration for the indicated multilink Point-to-Point Protocol (MLPPP) bundle in the indicated tunnel and session. Error: An error occurred error

Description

Type Severity

L2TPD_MLPPP_SPEED_MISMATCH
System Log Message

Unable to add link: speed differs for bundle bundle (L2TP tunnel tunnel-id, session session-id) 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. Error: An error occurred error

Description

Type Severity

L2TPD_NH_DELETE_FAILED
System Log Message Description

Unable to delete next hop next-hop The Layer 2 Tunneling Protocol process (l2tpd) could not delete the indicated next hop. Error: An error occurred error

Type Severity

L2TPD_POLICER_ADD_FAILED
System Log Message

Unable to add policer filter-name (L2TP tunnel tunnel-id, session session-id): error-message The Layer 2 Tunneling Protocol process (l2tpd) could not add the indicated policer to the indicated session on the indicated tunnel, which is associated with a user. Error: An error occurred

Description

Type

378

L2TPD_MLPPP_SESSION_DELETE_FAIL

Chapter 45: L2TPD System Log Messages

Severity Action

error Remove the policer from the RADIUS database or contact your technical support representative.

L2TPD_POLICER_PROFILE_DEL_FAILED
System Log Message

Unable to delete policer profile (L2TP tunnel tunnel-id, session session-id): error-message The Layer 2 Tunneling Protocol process (l2tpd) could not delete a policer profile from the indicated session on the indicated tunnel, which is associated with a user. Error: An error occurred error Remove the policer profile from the RADIUS database or contact your technical support representative.

Description

Type Severity Action

L2TPD_POOL_ADDRESS_FAILED
System Log Message Description

Unable to assign pool address (L2TP tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) could not assign a pool address in the indicated tunnel and session. Error: An error occurred error

Type Severity

L2TPD_POOL_ASSIGN_ADDRESS_FAILED
System Log Message Description

Unable to assign L2TP pool address: pool pool-name is invalid or has no free addresses The Layer 2 Tunneling Protocol process (l2tpd) could not assign an address from the indicated address pool, either because the pool was invalid or had no free addresses. Error: An error occurred error

Type Severity

L2TPD_PPP_ROUTE_ADD_FAILED
System Log Message Description

Unable to add PPP peer route (L2TP tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not add information about a Point-to-Point

L2TPD_POLICER_ADD_FAILED

379

JUNOS 10.1 System Log Messages Reference

Protocol (PPP) peer route to the in-memory configuration for the indicated tunnel and session.
Type Severity

Error: An error occurred error

L2TPD_PPP_ROUTE_DELETE_FAILED
System Log Message Description

Unable to remove PPP peer route (L2TP tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not delete information about a Point-to-Point Protocol (PPP) peer route from the in-memory configuration for the indicated tunnel and session. Error: An error occurred error

Type Severity

L2TPD_PROFILE_NOT_FOUND
System Log Message Description

Profile profile-name not found The Layer 2 Tunneling Protocol process (l2tpd) could not locate an access profile from the configuration in order to find radius servers to authenticate. Error: An error occurred error

Type Severity

L2TPD_PROFILE_NO_RADIUS_SERVERS
System Log Message Description

Can't find radius servers for profile 'profile-name The Layer 2 Tunneling Protocol process (l2tpd) could not locate any radius servers for the configured access profile. Error: An error occurred error

Type Severity

L2TPD_RADIUS_ACCT_PORT_ZERO
System Log Message Description

RADIUS server accounting port is zero The Layer 2 Tunneling Protocol process (l2tpd) determined that the RADIUS server accounting port is zero, which is not a valid value.

380

L2TPD_PPP_ROUTE_ADD_FAILED

Chapter 45: L2TPD System Log Messages

Type Severity

Error: An error occurred error

L2TPD_RADIUS_GETHOSTNAME_FAILED
System Log Message Description

Unable to obtain hostname for outgoing RADIUS message: error-message The Layer 2 Tunneling Protocol process (l2tpd) could not obtain a hostname for an outgoing RADIUS message. Error: An error occurred error

Type Severity

L2TPD_RADIUS_RT_INST_ENOENT
System Log Message Description

Ignoring RADIUS server radius-server: routing instance routing-instance did not exist The Layer 2 Tunneling Protocol process (l2tpd) did not use the indicated RADIUS server because the indicated routing instance specified for the server did not exist. Error: An error occurred notice

Type Severity

L2TPD_RADIUS_RT_INST_NOT_FOUND
System Log Message

Ignoring RADIUS server radius-server: unable to retrieve routing instance routing-instance (error-message) The Layer 2 Tunneling Protocol process (l2tpd) did not use the indicated RADIUS server because it could not retrieve the indicated routing instance specified for the server. Error: An error occurred error

Description

Type Severity

L2TPD_RADIUS_SERVER_NOT_FOUND
System Log Message Description

Unable to find RADIUS server (tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) could not locate a RADIUS server during Point-to-Point Protocol (PPP) authentication of the indicated tunnel and session. Error: An error occurred

Type

L2TPD_RADIUS_ACCT_PORT_ZERO

381

JUNOS 10.1 System Log Messages Reference

Severity

error

L2TPD_RADIUS_SRC_ADDR_BIND_FAIL
System Log Message

Ignoring RADIUS server radius-server: unable to bind to source address source-address (error-message) The Layer 2 Tunneling Protocol process (l2tpd) did not use the indicated RADIUS server because it could not bind to the indicated source address. Error: An error occurred error

Description

Type Severity

L2TPD_RADIUS_SRC_ADDR_ENOENT
System Log Message Description

Ignoring RADIUS server radius-server: source address source-address did not exist The Layer 2 Tunneling Protocol process (l2tpd) did not use the indicated RADIUS server because the indicated source address did not exist in the routing instance for the server. Error: An error occurred notice

Type Severity

L2TPD_RPD_ASYNC_UNREG_FAILED
System Log Message Description

Unable to unregister with rpd (return-value) The Layer 2 Tunneling Protocol process (l2tpd) could not unregister asynchronously with the routing protocol process (rpd). Error: An error occurred error

Type Severity

L2TPD_RPD_ROUTE_ADD_CB_FAILED
System Log Message

Unable to add route address/prefix-length asynchronously (gateway gateway-id [gateway-name], L2TP tunnel tunnel-id, session session-id): error-code The Layer 2 Tunneling Protocol process (l2tpd) could not add a route on an asynchronous callback for the indicated address and prefix, gateway, tunnel, and session. Error: An error occurred

Description

Type

382

L2TPD_RADIUS_SERVER_NOT_FOUND

Chapter 45: L2TPD System Log Messages

Severity

error

L2TPD_RPD_ROUTE_ADD_FAILED
System Log Message

Unable to add route address/prefix-length (gateway gateway-id [gateway-name], L2TP tunnel tunnel-id, session session-id): error-message (error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not add a route for the indicated address and prefix, gateway, tunnel, and session. Error: An error occurred error

Description

Type Severity

L2TPD_RPD_ROUTE_DELETE_CB_FAILED
System Log Message

Unable to delete route address/prefix-length asynchronously (gateway gateway-id [gateway-name], L2TP tunnel tunnel-id, session session-id): error-code The Layer 2 Tunneling Protocol process (l2tpd) could not delete a route on an asynchronous callback for the indicated address and prefix, gateway, tunnel, and session. Error: An error occurred error

Description

Type Severity

L2TPD_RPD_ROUTE_DELETE_FAILED
System Log Message

Unable to delete route address/prefix-length (gateway gateway-id [gateway-name], L2TP tunnel tunnel-id, session session-id): error-message (error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not delete a route for the indicated address and prefix, gateway, tunnel, and session. Error: An error occurred error

Description

Type Severity

L2TPD_RPD_ROUTE_PREFIX_TOO_LONG
System Log Message

Unable to add route address/prefix-length: prefix too long (L2TP tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) could not add a route for the indicated address and prefix, tunnel, and session. Error: An error occurred

Description

Type

L2TPD_RPD_ROUTE_ADD_CB_FAILED

383

JUNOS 10.1 System Log Messages Reference

Severity

error

L2TPD_RPD_SESS_CREATE_FAILED
System Log Message Description

Unable to establish session with rpd (error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not establish a session with the routing protocol process (rpd). Error: An error occurred error

Type Severity

L2TPD_RPD_SESS_HANDLE_ALLOC_FAIL
System Log Message Description

Unable to allocate session handle for rpd connection: error-message (error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not allocate a session handle while attempting to initialize a connection to the routing protocol process (rpd). Error: An error occurred error

Type Severity

L2TPD_RPD_SOCKET_ALLOC_FAILED
System Log Message Description

Unable to allocate socket address for rpd connection The Layer 2 Tunneling Protocol process (l2tpd) could not allocate a socket address structure while attempting to initialize a connection to the routing protocol process (rpd). Error: An error occurred error

Type Severity

L2TPD_RPD_TBL_LOCATE_BY_NAME
System Log Message Description

Unable to locate rpd table by name: error-message (error-code) The Layer 2 Tunneling Protocol process (l2tpd) attempted to retrieve a routing protocol process table by providing the table name. The attempt failed. Error: An error occurred error

Type Severity

384

L2TPD_RPD_ROUTE_PREFIX_TOO_LONG

Chapter 45: L2TPD System Log Messages

L2TPD_RPD_TBL_LOCATE_FAILED
System Log Message Description

Unable to locate table table-name for identifier (return-value) The Layer 2 Tunneling Protocol process (l2tpd) could not retrieve the indicated routing protocol process table. Error: An error occurred error

Type Severity

L2TPD_RPD_VERSION_MISMATCH
System Log Message Description

Versions of rpd and librpd did not match; not retrying The Layer 2 Tunneling Protocol process (l2tpd) determined that the versions of the routing protocol process (rpd) and routing protocol library (librpd) were different. It halted its attempt to connect to the rpd process. Error: An error occurred error

Type Severity

L2TPD_RTSLIB_ASYNC_OPEN_FAILED
System Log Message Description

Unable to open asynchronous routing socket connection The Layer 2 Tunneling Protocol process (l2tpd) could not open a routing socket connection asynchronously. It uses the connection to communicate with the JUNOS operating system kernel. Error: An error occurred error

Type Severity

L2TPD_RTSLIB_OPEN_FAILED
System Log Message Description

Unable to open routing socket connection 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. Error: An error occurred error

Type Severity

L2TPD_RPD_TBL_LOCATE_FAILED

385

JUNOS 10.1 System Log Messages Reference

L2TPD_SERVER_START_FAILED
System Log Message Description Type Severity

Startup of L2TP server failed The Layer 2 Tunneling Protocol (L2TP) server did not start. Error: An error occurred error

L2TPD_SERVICE_NH_ADD_FAILED
System Log Message

Unable to add service next hop (L2TP tunnel tunnel-id, session session-id): error-message (error-code) The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not add information about a service next hop to the in-memory configuration for the indicated tunnel and session. Error: An error occurred error

Description

Type Severity

L2TPD_SERVICE_NH_DELETE_FAILED
System Log Message

Unable to remove service next hop next-hop (VRF vrf, L2TP tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not remove information about the indicated service next hop from the in-memory configuration for the indicated tunnel and session. Error: An error occurred error

Description

Type Severity

L2TPD_SESSION_CFG_ADD_ERROR
System Log Message

Unable to add L2TP tunnel tunnel-id, session session-id to PIC configuration (errno error-code) 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 Physical Interface Card (PIC).

Description

386

L2TPD_SERVER_START_FAILED

Chapter 45: L2TPD System Log Messages

Type Severity

Error: An error occurred error

L2TPD_SESSION_CFG_ADD_FAILED
System Log Message Description

Unable to add L2TP tunnel tunnel-id, session session-id to PIC configuration 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 Physical Interface Card (PIC). Error: An error occurred error

Type Severity

L2TPD_SESSION_CFG_DELETE_FAILED
System Log Message Description

Unable to remove L2TP tunnel tunnel-id, session session-id from PIC configuration The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not remove information about the indicated session and tunnel from the in-memory configuration for the Physical Interface Card (PIC). Error: An error occurred error

Type Severity

L2TPD_SESSION_DELETE_FAILED
System Log Message Description

Unable to delete session (L2TP tunnel tunnel-id, session session-id, errno error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not delete information about the indicated tunnel and session. Error: An error occurred error

Type Severity

L2TPD_SESSION_IFF_NOT_FOUND
System Log Message

Unable to find family structure for interface interface-name (L2TP tunnel tunnel-id, session session-id) 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.

Description

L2TPD_SESSION_CFG_ADD_ERROR

387

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

L2TPD_SESSION_IFL_ADD_FAILED
System Log Message Description

function-name: unable to assign session session-id to interface interface-name The Layer 2 Tunneling Protocol process (l2tpd) could not associate the indicated session with the indicated logical interface. Error: An error occurred error

Type Severity

L2TPD_SESSION_IFL_ALLOC_FAILED
System Log Message

function-name: unable to allocate memory for session session-id, interface interface-name The Layer 2 Tunneling Protocol process (l2tpd) could not allocate memory for the indicated session to be associated with the indicated logical interface. Error: An error occurred error

Description

Type Severity

L2TPD_SESSION_IFL_CLI_TREE_ALLOC
System Log Message Description

Unable to allocate memory for session tree for interface interface-name The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not allocate memory for a command-line interface (CLI)-specific session tree structure for the indicated logical interface. Error: An error occurred error

Type Severity

L2TPD_SESSION_IFL_DELETED
System Log Message Description

function-name: interface interface-name is deleted The Layer 2 Tunneling Protocol process (l2tpd) detected that the configuration information for the indicated logical interface was deleted for a session. Error: An error occurred

Type

388

L2TPD_SESSION_IFF_NOT_FOUND

Chapter 45: L2TPD System Log Messages

Severity

error

L2TPD_SESSION_IFL_DELETE_FAILED
System Log Message Description

function-name: unable to delete session identifier from interface interface-name The Layer 2 Tunneling Protocol process (l2tpd) could not delete information about a session from the configuration information for a logical interface. Error: An error occurred error

Type Severity

L2TPD_SESSION_IFL_GET_FAILED
System Log Message Description

function-name: unable to find interface interface-name The Layer 2 Tunneling Protocol process (l2tpd) could not retrieve configuration information about the indicated logical interface, to which it was going to add session information. Error: An error occurred error

Type Severity

L2TPD_SESSION_IFL_NOT_EQUAL
System Log Message Description

function-name: interface interface-name not equal The Layer 2 Tunneling Protocol process (l2tpd) could not add a session for the indicated logical interface. Error: An error occurred error

Type Severity

L2TPD_SESSION_IFL_NOT_FOUND
System Log Message Description

Unable to find interface interface-name (L2TP tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) could not find the indicated logical interface corresponding to the indicated tunnel and session. Error: An error occurred error

Type Severity

L2TPD_SESSION_IFL_DELETED

389

JUNOS 10.1 System Log Messages Reference

L2TPD_SESSION_IFL_OCCUPIED
System Log Message Description

function-name: interface interface-name already has associated session (value1/value2) The Layer 2 Tunneling Protocol process (l2tpd) determined that the indicated logical interface already had an associated session. Error: An error occurred error

Type Severity

L2TPD_SESSION_IFL_REMOVE_FAILED
System Log Message

Unable to remove L2TP tunnel tunnel-id, session session-id from logical interface (errno error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not remove information about the indicated tunnel and session from the record it maintains for a logical interface. Error: An error occurred error

Description

Type Severity

L2TPD_SESSION_INVALID_PEER_IP
System Log Message

Invalid peer address peer-address in IPCP UP (L2TP tunnel tunnel-id, session session-id); closing session The Layer 2 Tunneling Protocol process (l2tpd) received an IP Control Protocol (IPCP) 'UP' message for the indicated tunnel and session that included the indicated IP address for a peer. The address was invalid, and the l2tpd process started closing down the session. Error: An error occurred error

Description

Type Severity

L2TPD_SESSION_ROUTE_ADD_FAILED
System Log Message Description

Unable to add PPP route (L2TP tunnel tunnel-id, session session-id, errno error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not add a Point-to-Point Protocol (PPP) route for the indicated tunnel and session. Error: An error occurred error

Type Severity

390

L2TPD_SESSION_IFL_OCCUPIED

Chapter 45: L2TPD System Log Messages

L2TPD_SESSION_RT_TBL_NOT_FOUND
System Log Message

Unable to find route table table-id for interface interface-name (L2TP tunnel tunnel-id, session session-id) 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. Error: An error occurred error

Description

Type Severity

L2TPD_SESSION_TUNNEL_ID_MISMATCH
System Log Message

Tunnel ID tunnel-id in message does not match L2TP tunnel l2tp-tunnel-id, session session-id The Layer 2 Tunneling Protocol process (l2tpd) received a message with the indicated tunnel identifier, which did not match the identifier stored for the indicated tunnel and session. Error: An error occurred error

Description

Type Severity

L2TPD_SETSOCKOPT_FAILED
System Log Message Description

setsockopt() failed operation: error-message The Layer 2 Tunneling Protocol process (l2tpd) could not set socket options during the indicated operation. Error: An error occurred error

Type Severity

L2TPD_SET_ASYNC_CONTEXT
System Log Message Description

Unable to set asynchronous context (errno error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not set asynchronous context for a routing socket connection, which it uses to communicate with the JUNOS operating system kernel. Error: An error occurred error

Type Severity

L2TPD_SESSION_RT_TBL_NOT_FOUND

391

JUNOS 10.1 System Log Messages Reference

L2TPD_SHOW_MULTILINK
System Log Message Description

Detail level level is not supported by 'show services l2tp multilink' command 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. Error: An error occurred error

Type Severity

L2TPD_SHOW_SESSION
System Log Message Description

Detail level level is not supported by 'show services l2tp session' command The 'show services l2tp session' command was issued with the indicated option to specify the amount of information to return, but the command does not support that option. Error: An error occurred error

Type Severity

L2TPD_SHOW_TUNNEL
System Log Message Description

Detail level level is not supported by 'show services l2tp tunnel' command The 'show services l2tp tunnel' command was issued with the indicated option to specify the amount of information to return, but the command does not support that option. Error: An error occurred error

Type Severity

L2TPD_SOCKET_FAILED
System Log Message Description

socket() failed operation: error-message The Layer 2 Tunneling Protocol process (l2tpd) could not open socket during the indicated operation. Error: An error occurred error

Type Severity

392

L2TPD_SHOW_MULTILINK

Chapter 45: L2TPD System Log Messages

L2TPD_SUBUNIT_ROUTE_ALLOC_FAILED
System Log Message Description

Unable to allocate L2TP route (tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) could not allocate a subunit route record for the indicated tunnel and session. Error: An error occurred error

Type Severity

L2TPD_TRACE_FILE_OPEN_FAILED
System Log Message Description Type Severity

Unable to open trace file: error-message The Layer 2 Tunneling Protocol process (l2tpd) could not open its trace file. Error: An error occurred error

L2TPD_TUNNEL_CFG_ADD_FAILED
System Log Message Description

Unable to add L2TP tunnel tunnel-id to PIC configuration (errno error-code) 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 tunnel to the in-memory configuration for the Physical Interface Card (PIC). Error: An error occurred error

Type Severity

L2TPD_TUNNEL_CFG_ADD_INV_ADDR
System Log Message Description

Unable to add L2TP tunnel tunnel-id to PIC configuration: address invalid 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 tunnel to the in-memory configuration for the Physical Interface Card (PIC), because the local or remote address provided for the tunnel was invalid. Error: An error occurred error

Type Severity

L2TPD_SUBUNIT_ROUTE_ALLOC_FAILED

393

JUNOS 10.1 System Log Messages Reference

L2TPD_TUNNEL_CFG_DELETE_FAILED
System Log Message Description

Unable to remove L2TP tunnel tunnel-id from PIC configuration The Layer 2 Tunneling Protocol process (l2tpd) maintains a copy of the JUNOS configuration database in memory. It could not remove information about the indicated tunnel from the in-memory configuration for the Physical Interface Card (PIC). Error: An error occurred error

Type Severity

L2TPD_TUNNEL_DELETE_FAILED
System Log Message Description

Unable to delete L2TP tunnel tunnel-id (errno error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not delete information about the indicated tunnel. Error: An error occurred error

Type Severity

L2TPD_TUNNEL_DEST_IF_LOOKUP_FAIL
System Log Message

Unable to find destination interface for L2TP tunnel tunnel-id remote address: error-message The Layer 2 Tunneling Protocol process (l2tpd) tried to use route lookup to determine which local logical interface to use to reach the remote end of the indicated tunnel. The attempt failed. Error: An error occurred error

Description

Type Severity

L2TPD_TUNNEL_GROUP_ADD_FAILED
System Log Message Description Type Severity

Unable to create L2TP tunnel group The Layer 2 Tunneling Protocol process (l2tpd) could not create a tunnel group. Error: An error occurred error

394

L2TPD_TUNNEL_CFG_DELETE_FAILED

Chapter 45: L2TPD System Log Messages

L2TPD_TUNNEL_GROUP_CFG_ADD_FAIL
System Log Message

Unable to add tunnel group tunnel-group (service set service-set) to configuration for PIC pic-slot: error-message 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 tunnel group and service set to the in-memory configuration for the indicated Physical Interface Card (PIC). Error: An error occurred error

Description

Type Severity

L2TPD_TUNNEL_GROUP_CFG_DEL_FAIL
System Log Message Description

Unable to delete tunnel group tunnel-group (service set service-set): error-code The Layer 2 Tunneling Protocol process (l2tpd) could not delete information about the indicated tunnel group and service set. Error: An error occurred error

Type Severity

L2TPD_TUNNEL_GROUP_CREATE_FAILED
System Log Message Description

Unable to create L2TP module for tunnel group address The Layer 2 Tunneling Protocol process (l2tpd) could not create the indicated protocol tunnel group. Error: An error occurred error

Type Severity

L2TPD_TUNNEL_GROUP_DELETE_FAILED
System Log Message Description

Unable to delete L2TP tunnel group tunnel-group-id (errno error-code) The Layer 2 Tunneling Protocol process (l2tpd) could not delete information about the indicated tunnel group. Error: An error occurred error

Type Severity

L2TPD_TUNNEL_GROUP_CFG_ADD_FAIL

395

JUNOS 10.1 System Log Messages Reference

L2TPD_TUNNEL_GROUP_IDX_MISMATCH
System Log Message

Tunnel group index index1 in message does not match index index2 stored for L2TP tunnel tunnel-id The Layer 2 Tunneling Protocol process (l2tpd) received a message with the indicated tunnel group index, which did not match the indicated group tunnel index stored for the indicated tunnel. Error: An error occurred error

Description

Type Severity

L2TPD_TUNNEL_GROUP_RESTART_FAIL
System Log Message Description

Unable to restart L2TP module for tunnel group The Layer 2 Tunneling Protocol process (l2tpd) could not restart a protocol tunnel group. Error: An error occurred error

Type Severity

L2TPD_USER_AUTHN_NOT_FOUND
System Log Message Description

Unable to find user profile username during PPP authentication The Layer 2 Tunneling Protocol process (l2tpd) could not retrieve the user profile for the indicated username, which it needs for Point-to-Point Protocol (PPP) authentication of a session. Error: An error occurred error

Type Severity

L2TPD_USER_AUTHN_ORDER_UNKNOWN
System Log Message Description

Unknown authentication order authentication-order (tunnel tunnel-id, session session-id) The Layer 2 Tunneling Protocol process (l2tpd) did not recognize the indicated authentication order, which was specified for Point-to-Point (PPP) authentication of the indicated tunnel and session. Error: An error occurred error

Type Severity

396

L2TPD_TUNNEL_GROUP_IDX_MISMATCH

Chapter 45: L2TPD System Log Messages

L2TPD_USER_AUTHN_PWD_NOT_FOUND
System Log Message Description

Unable to retrieve password during PPP authentication of user username 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. Error: An error occurred error

Type Severity

L2TPD_USER_AUTHN_PWD_NOT_FOUND

397

JUNOS 10.1 System Log Messages Reference

398

L2TPD_USER_AUTHN_PWD_NOT_FOUND

Chapter 46

LACPD System Log Messages

This chapter describes messages with the LACPD prefix. They are generated by the Link Aggregation Control Protocol (LACPD) process (lacpd), which supports LACP functions for aggregated Ethernet interfaces.

LACPD_MEMORY_ALLOCATION_FAILED
System Log Message Description

Unable to allocate memory for interface interface-name The Link Aggregation Control Protocol process (lacpd) could not allocate memory for the indicated interface. Error: An error occurred error

Type Severity

LACPD_MEMORY_ALLOCATION_FAILED

399

JUNOS 10.1 System Log Messages Reference

400

LACPD_MEMORY_ALLOCATION_FAILED

Chapter 47

LFMD System Log Messages

This chapter describes messages with the LFMD prefix. They are generated by the link-fault management process (lfmd), which supports Operation, Administration, and Maintenance (OAM) functions that are defined in the Institute of Electrical and Electronics Engineers (IEEE) 802.3ah standard for Ethernet interfaces.

LFMD_RTSOCK_OPEN_FAILED
System Log Message Description

Unable to open synchronous routing socket: error-message The Ethernet Operation, Administration and Management link-fault management process (lfmd) could not open a routing socket to create a connection. Error: An error occurred error

Type Severity

LFMD_RTSOCK_OPEN_FAILED

401

JUNOS 10.1 System Log Messages Reference

402

LFMD_RTSOCK_OPEN_FAILED

Chapter 48

LIBESPTASK System Log Messages

This chapter describes messages with the LIBESPTASK prefix.

LIBESPTASK_SNMP_CONN_PROG
System Log Message Description

function-name: error-message The indicated error occurred while the process using libesptask was connecting to the Simple Network Management Protocol (SNMP) master agent. Error: An error occurred info

Type Severity

LIBESPTASK_SNMP_CONN_QUIT
System Log Message Description

function-name: unable to connect to SNMP agent (pathname): error-message The process using libesptask could not connect to the indicated Simple Network Management Protocol (SNMP) master agent. Error: An error occurred error

Type Severity

LIBESPTASK_SNMP_CONN_RETRY
System Log Message Description

function-name: reattempting connection to SNMP agent (pathname): error-message The process using libesptask tried again to connect to the indicated Simple Network Management Protocol (SNMP) master agent after a connection attempt failed. Error: An error occurred error

Type Severity

LIBESPTASK_SNMP_CONN_PROG

403

JUNOS 10.1 System Log Messages Reference

LIBESPTASK_SNMP_INVALID_SOCKET
System Log Message Description

function-name: socket file-descriptor is invalid The process using libesptask could not send a message to a Simple Network Management Protocol (SNMP) master agent because the indicated socket is invalid. Error: An error occurred error

Type Severity

LIBESPTASK_SNMP_SOCKOPT_BLOCK
System Log Message Description

function-name: unable to set nonblocking option The process using libesptask could not set a socket to nonblocking mode after connecting to the Simple Network Management Protocol (SNMP) master agent. Error: An error occurred error

Type Severity

LIBESPTASK_SNMP_SOCKOPT_RECVBUF
System Log Message Description

function-name: unable to set recvbuf option The process using libesptask could not set the size of the kernel receive buffer, which allows it to accept the largest possible packet from the Simple Network Management Protocol (SNMP) master agent. Error: An error occurred error

Type Severity

LIBESPTASK_SNMP_SOCKOPT_SENDBUF
System Log Message Description

function-name: unable to set sendbf option 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. Error: An error occurred error

Type Severity

404

LIBESPTASK_SNMP_INVALID_SOCKET

Chapter 49

LIBJNX System Log Messages

This chapter describes messages with the LIBJNX prefix. They are generated by processes that call routines in the libjuniper library, which includes routines for creating and managing child processes, parsing machine and interface addresses, tracing, file I/O, and other functions.

LIBJNX_AUDIT_ERROR
System Log Message Description

function-name: error-message A JUNOS process could not notify the audit process (auditd) about user activity related to system accounting, because of an interprocess communication (IPC) error. Error: An error occurred error Possible reasons include (a) auditd was not running (b) auditd was still initializing after a restart (c) there was a socket error. Contact your technical support representative.

Type Severity Cause

Action

LIBJNX_COMPRESS_EXEC_FAILED
System Log Message Description

Unable to compress file 'filename' using program-name: error-message 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. Error: An error occurred info An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

LIBJNX_AUDIT_ERROR

405

JUNOS 10.1 System Log Messages Reference

LIBJNX_DEFAULT_IP_ADDR_NOT_SET
System Log Message Description

Unable to retrieve system default IP address: not set in kernel (error-message) A JUNOS process could not retrieve the system default IP address from the kernel, because the address is not defined there. Error: An error occurred critical An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

LIBJNX_EVLIB_FAILURE
System Log Message Description

function-name: error-message A JUNOS process called the indicated function in the event library. The function failed for the indicated reason. Error: An error occurred emergency An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

LIBJNX_EXEC_EXITED
System Log Message

Command stopped: PID pid, signal='return-value'core-dump-status, command 'command' A JUNOS process created a child process to execute the indicated command for it. The child process stopped unexpectedly. Error: An error occurred notice An internal software failure occurred. Contact your technical support representative.

Description

Type Severity Cause Action

406

LIBJNX_DEFAULT_IP_ADDR_NOT_SET

Chapter 49: LIBJNX System Log Messages

LIBJNX_EXEC_FAILED
System Log Message Description

Child exec failed for command 'command': error-message A JUNOS process called the exec() system call while creating a child process to execute the indicated command for it. The system call failed. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

LIBJNX_EXEC_PIPE
System Log Message Description

Unable to create pipes for command 'command': error-message A JUNOS process created a child process to execute the indicated command for it. Its attempt to create pipes for communication with the child failed. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

LIBJNX_EXEC_SIGNALED
System Log Message

Command received signal: PID pid, signal signal-namecore-dump-status, command 'command' A JUNOS process created a child process to execute the indicated command for it. The child process received the indicated signal and exited. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Description

Type Severity Cause Action

LIBJNX_EXEC_FAILED

407

JUNOS 10.1 System Log Messages Reference

LIBJNX_EXEC_WEXIT
System Log Message Description

Command exited: PID pid, status return-valuecore-dump-status, command 'command' A JUNOS process created a child process to execute the indicated command for it. The child process exited abnormally with the indicated exit code. Error: An error occurred notice An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

LIBJNX_FILE_COPY_FAILED
System Log Message Description

Failed to copy from source-filename to destination-filename A JUNOS process could not copy the indicated source file to the indicated destination name or location. Error: An error occurred error

Type Severity

LIBJNX_FILE_SYSTEM_FAIL
System Log Message Description Type Severity

pathname: error-message A JUNOS process could not obtain status information for the indicated file system. Event: This message reports an event, not an error error

LIBJNX_FILE_SYSTEM_SPACE
System Log Message Description

Not enough space left on device pathname A JUNOS process found that the indicated file system did not have the free space needed for storing temporary files. Event: This message reports an event, not an error warning

Type Severity

408

LIBJNX_EXEC_WEXIT

Chapter 49: LIBJNX System Log Messages

LIBJNX_INVALID_CHASSIS_ID
System Log Message Description

function-name: invalid chassis ID chassis-id 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. Error: An error occurred error

Type Severity

LIBJNX_INVALID_RE_SLOT_ID
System Log Message Description

function-name: invalid Routing Engine slot ID routing-engine-slot A JUNOS process could not determine the hostname for a Routing Engine, because the indicated Routing Engine slot ID was invalid. Error: An error occurred error

Type Severity

LIBJNX_INVALID_XML_DATA
System Log Message Description

Invalid XML data '\\data' The XML parser closed its session with a client application because the indicated XML data sent by the client was invalid. Error: An error occurred error

Type Severity

LIBJNX_PRIV_LOWER_FAILED
System Log Message Description

Unable to lower privilege level: error-message A JUNOS process attempted to revert its effective user ID to the original user. The attempt failed. Error: An error occurred error An internal software failure occurred.

Type Severity Cause

LIBJNX_INVALID_CHASSIS_ID

409

JUNOS 10.1 System Log Messages Reference

Action

Contact your technical support representative.

LIBJNX_PRIV_RAISE_FAILED
System Log Message Description

Unable to raise privilege level: error-message A JUNOS process attempted to set its effective user ID to the root user. The attempt failed. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

LIBJNX_REPLICATE_RCP_ERROR
System Log Message Description Type Severity Cause Action

operation: operational-status The rcp command failed during replication. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJNX_REPLICATE_RCP_EXEC_FAILED
System Log Message Description

rcp failed: error-message A JUNOS process created a child process to copy a file to the other Routing Engine. The copy operation failed. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

410

LIBJNX_PRIV_LOWER_FAILED

Chapter 49: LIBJNX System Log Messages

LIBJNX_SNMP_ENGINE_FILE_FAILURE
System Log Message Description

function-name: operation: operation filename: error-message A JUNOS process could not perform the indicated operation on the indicated SNMP engine data file. Error: An error occurred critical An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

LIBJNX_SNMP_ENGINE_SCAN_FAILURE
System Log Message Description

function-name: fscanf : filename scanning: data Error: error-message A JUNOS process could not perform the scan operation on the indicated SNMP engine data file. Error: An error occurred critical An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

LIBJNX_SOCKET_FAILURE
System Log Message Description

operation: error-message Various system processes use Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Reliable Data Protocol (RDP) sockets. The indicated socket operation failed for the indicated reason. Error: An error occurred emergency An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

LIBJNX_SNMP_ENGINE_FILE_FAILURE

411

JUNOS 10.1 System Log Messages Reference

LIBJNX_XML_DECODE_FAILED
System Log Message Description

Invalid XML encoding 'data', skipping to ';' The XML parser ignored the indicated XML data sent by a client application, because the XML encoding of the data was invalid. The parser skipped ahead to the likely endpoint for the invalid data. Error: An error occurred error A possible cause is improper escaping of character constants in the data stream. Contact your technical support representative.

Type Severity Cause Action

412

LIBJNX_XML_DECODE_FAILED

Chapter 50

LIBJSNMP System Log Messages

This chapter describes messages with the LIBJSNMP prefix. They are generated by the libjsnmp process.

LIBJSNMP_CTX_FAILURE
System Log Message Description Type Severity Cause Action

snmp_ms_trap_api return argument Sub-agents SNMP context either too long or of zero size Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_IPC_ERROR
System Log Message Description Type Severity Cause Action

argument: sock:port (type:port-type) Error in SNMP related IPC messages size mismatch, corruption or memory failure Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_IPC_READ_ERROR
System Log Message Description

Unable to read inbound-bytes bytes: sock: port (type: port-type) Error in reading IPC messages during SNMP related messaging

LIBJSNMP_CTX_FAILURE

413

JUNOS 10.1 System Log Messages Reference

Type Severity Cause Action

Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_MTHD_API_UNKNOWN_TYPE
System Log Message Description Type Severity Cause Action

unknown oev type: tag-type Internal error - Unknown SNMP object indexing type Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_NS_LOG_CRIT
System Log Message Description Type Severity Cause Action

CRIT: argument Logs for SNMP critical message Error: An error occurred critical An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_NS_LOG_EMERG
System Log Message Description Type Severity Cause

EMERG: argument SNMP errors with LOG_EMERG as severity Error: An error occurred emergency An internal software failure occurred.

414

LIBJSNMP_IPC_READ_ERROR

Chapter 50: LIBJSNMP System Log Messages

Action

Contact your technical support representative.

LIBJSNMP_NS_LOG_ERR
System Log Message Description Type Severity Cause Action

ERR: argument SNMP errors with LOG_ERR as severity Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_OID_GEN_FAILED
System Log Message Description Type Severity Cause Action

Unable to generate OID: object-name (system-error-message) Unable to translate SNMP object string to OID Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_READ_LEN_ERR
System Log Message Description Type Severity Cause Action

error error-code reading routing socket Failure while reading rtsocket for SNMP related operation Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_NS_LOG_EMERG

415

JUNOS 10.1 System Log Messages Reference

LIBJSNMP_RTMSIZE_MISMATCH_ERR
System Log Message Description Type Severity Cause Action

routing socket msg size argument of argument1 (call buf = argument2) Error in message length while reading rtsocket for SNMP related operation Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_SMS_HDR_ERR
System Log Message Description Type Severity Cause Action

problem with hdr size (record-size) or msg size (size) Discrepancy in sub-agent message length and header size Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_SMS_MSG_ERR
System Log Message Description Type Severity Cause Action

received received-value bytes, expected expected-value bytes Various discrepancies in sub-agent message lengths. SNMP Message errors Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_SOCKET_OPEN_ERR
System Log Message

routing socket open error argument

416

LIBJSNMP_RTMSIZE_MISMATCH_ERR

Chapter 50: LIBJSNMP System Log Messages

Description Type Severity Cause Action

Failure in opening routing socket Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_SOCKET_VER_MISMATCH
System Log Message Description Type Severity Cause Action

routing socket version mismatch Routing socket version mismatch between kernel and application Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_TRAP_API_FAILURE
System Log Message Description Type Severity Cause Action

function-name: Trap API: argument argument1 Misc. error while creating SNMP traps Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

LIBJSNMP_TRAP_UTILS_ERR
System Log Message Description Type

unknown trap object: object-name Trying to send invalid object as varbind while creating SNMP traps Error: An error occurred

LIBJSNMP_SOCKET_OPEN_ERR

417

JUNOS 10.1 System Log Messages Reference

Severity Cause Action

error An internal software failure occurred. Contact your technical support representative.

418

LIBJSNMP_TRAP_UTILS_ERR

Chapter 51

LIBMSPRPC System Log Messages

This chapter describes messages with the LIBMSPRPC prefix. They are generated by the mspinfo process, which is responsible for RPC communication between the Routing Engine (RE) and the Multiservices PICs.

LIBMSPRPC_CLIENT_INIT_FAILED
System Log Message Description Type Severity Cause Action

Can't create msprpc client: error-message A JUNOS process (mspinfo) could not establish initialization of the RPC client. Error: An error occurred error Possible reasons: process is out of memory Contact your technical support representative.

LIBMSPRPC_CLIENT_KCOM_FAILED
System Log Message Description Type Severity Cause Action

Can't initialize kcom for msprpc client: error-message A JUNOS process (mspinfo) could not establish initialization of the kcom subsystem. Error: An error occurred error Possible reasons: can't initialize kcom services. Contact your technical support representative.

LIBMSPRPC_CLIENT_NO_CONNECTION
System Log Message

Failed connecting fpc=fpc-slot, pic=pic-slot

LIBMSPRPC_CLIENT_INIT_FAILED

419

JUNOS 10.1 System Log Messages Reference

Description

Remote execution of the command given from the RE to the PIC failed, can not connect to the PIC. Error: An error occurred notice Possible reasons: a)PIC appears online but is not responding b)msprpc server is not running on the PIC. Contact your technical support representative.

Type Severity Cause

Action

LIBMSPRPC_CLIENT_NO_REPLY
System Log Message Description

Error executing "command": no reply from the PIC Remote execution of the command given from the RE to the PIC failed, no reply from the PIC. Error: An error occurred notice Possible reasons: a)wrong command b)insufficient permissions c)wrong arguments d)PIC appears online but is not responding e)msprpc server is not running on the PIC. Contact your technical support representative.

Type Severity Cause

Action

LIBMSPRPC_CLIENT_PIC_DOWN
System Log Message Description

Interface interface-name is down Remote execution of the command given from the RE to the PIC failed, the PIC is down. Error: An error occurred error Possible reasons: the given PIC is not responding and/or is offline. Contact your technical support representative.

Type Severity Cause Action

LIBMSPRPC_CLIENT_WRONG_OUTPUT
System Log Message

Error executing "command": output length exceeds correct-length characters

420

LIBMSPRPC_CLIENT_NO_CONNECTION

Chapter 51: LIBMSPRPC System Log Messages

Description

Remote execution of the command given from the RE to the PIC failed, PIC returned unexpected output. Error: An error occurred notice Possible reasons: a)wrong command b)wrong arguments. Contact your technical support representative.

Type Severity Cause Action

LIBMSPRPC_CLIENT_WRONG_OUTPUT

421

JUNOS 10.1 System Log Messages Reference

422

LIBMSPRPC_CLIENT_WRONG_OUTPUT

Chapter 52

LICENSE System Log Messages

This chapter describes messages with the LICENSE prefix. They are generated by processes that call routines in the liblicense library, which provide software license management functions on a routing platform.

LICENSE_CONNECT_FAILURE
System Log Message Description

Connection could not be set up: error-message The indicated error occured because a connection to the license-check process was not established. Error: An error occurred error

Type Severity

LICENSE_CONN_TO_LI_CHECK_FAILURE
System Log Message Description

Process could not connect to license-check in maximum-value tries; giving up The indicated process failed to connect to the license-check process after the indicated maximum tries. Error: An error occurred error

Type Severity

LICENSE_CONN_TO_LI_CHECK_SUCCESS
System Log Message Description Type Severity

Connected to license-check The indicated process succesfully connected to the license-check process. Event: This message reports an event, not an error info

LICENSE_CONNECT_FAILURE

423

JUNOS 10.1 System Log Messages Reference

LICENSE_EXPIRED
System Log Message Description

License for feature feature-name(feature-id) expired The time-based license for the indicated feature expired. The feature remains inactive until a new license is installed. Event: This message reports an event, not an error alert

Type Severity

LICENSE_GRACE_PERIOD_APPROACHING
System Log Message Description

License grace period for feature feature-name(feature-id) will expire in time The indicated amount of time remained before the license grace period for the indicated feature would expire. If a new license was not installed within that time, the feature became inactive. Event: This message reports an event, not an error alert

Type Severity

LICENSE_GRACE_PERIOD_EXCEEDED
System Log Message

License grace period for feature feature-name(feature-id) will expire in time (limit = maximum-value) The grace period for a scale license is about to expire. Unless the scale license is upgraded, the license will scale back to the licensed limit once the grace period expires. Event: This message reports an event, not an error alert

Description

Type Severity

LICENSE_GRACE_PERIOD_EXPIRED
System Log Message Description

License grace period for feature feature-name(feature-id) has expired The grace period for a licensable feature has expired. Strict license enforcement will remain active until a new license is installed. Event: This message reports an event, not an error alert

Type Severity

424

LICENSE_EXPIRED

Chapter 52: LICENSE System Log Messages

LICENSE_LIST_MANAGEMENT
System Log Message

Error occurred for feature feature-name: error-message (system error: system-error-message) The management process (mgd) could not complete a license management command related to the indicated feature. If a system error is reported, it caused the problem. Error: An error occurred error

Description

Type Severity

LICENSE_NEARING_EXPIRY
System Log Message Description

License for feature feature-name(feature-id) expires in time At the time this message was logged, the indicated amount of time remained before the time-based license for the indicated feature would expire. If a new license was not installed within that time, the feature became inactive. Event: This message reports an event, not an error alert

Type Severity

LICENSE_READ_ERROR
System Log Message Description Type Severity

recvmsg() failed:error-message The indicated process failed to read an event sent to it, for the indicated reason. Error: An error occurred error

LICENSE_REG_ERROR
System Log Message Description

Registration request failed: current-value The license registration request failed. A request needs to be resent to the license-check process. Error: An error occurred error

Type Severity

LICENSE_LIST_MANAGEMENT

425

JUNOS 10.1 System Log Messages Reference

LICENSE_SIGNATURE_VERIFY_FAILED
System Log Message Description

Signature verification failed: error-message The management process (mgd) could not verify a license because the license's signature was invalid. Error: An error occurred error

Type Severity

LICENSE_UNKNOWN_RESPONSE_TYPE
System Log Message Description Type Severity

unknown message type received: current-value An unknown response type was received from the license-check process. Error: An error occurred error

LICENSE_VERIFICATION_FILE_ERROR
System Log Message

License verification failed for file 'error-message': filename (system error: system-error-message) The management process (mgd) could not verify the indicated license file because of the indicated internal file-handling error. Error: An error occurred error

Description

Type Severity

426

LICENSE_SIGNATURE_VERIFY_FAILED

Chapter 53

LLDPD System Log Messages

This chapter describes messages with the LLDPD prefix. They are generated by the link layer discovery protocol process (lldpd) which is used by EX-series switches to learn and distribute device information on network links. The information allows the switch to quickly identify a variety of devices, including IP telephones, resulting in a LAN that interoperates smoothly and efficiently.

LLDPD_SYSTEM
System Log Message Description Type Severity Cause

reason: error-message A system call made by the Link Layer Discovery Protocol process (LLDPD) failed. Error: An error occurred error It is possible that the kernel lacked the resources to fulfill the request. LLDPD will recover.

LLDPD_SYSTEM

427

JUNOS 10.1 System Log Messages Reference

428

LLDPD_SYSTEM

Chapter 54

LOGIN System Log Messages

This chapter describes messages with the LOGIN prefix. They are generated by the login process (login), which performs authentication for Telnet sessions.

LOGIN_ABORTED
System Log Message Description Type Severity

Client aborted login A login attempt was cancelled, either by the remote user or in response to a signal. Event: This message reports an event, not an error info

LOGIN_FAILED
System Log Message Description Type Severity

Login failed for user username from host hostname A login attempt failed for the indicated username. Event: This message reports an event, not an error notice

LOGIN_FAILED_SET_CONTEXT
System Log Message Description

Failed to set context for user username The login process (login) could not set login context properties for the indicated user and cancelled the authentication attempt. Error: An error occurred error

Type Severity

LOGIN_ABORTED

429

JUNOS 10.1 System Log Messages Reference

LOGIN_FAILED_SET_LOGIN
System Log Message Description

Failed to set login ID for user username: error-message The login process (login) could not assume the user ID of the indicated user and cancelled the authentication attempt. Error: An error occurred error

Type Severity

LOGIN_HOSTNAME_UNRESOLVED
System Log Message Description

Unable to resolve hostname hostname: error-message The login process (login) could not resolve the indicated remote hostname for the indicated reason. Error: An error occurred error An internal software failure occurred.

Type Severity Cause

LOGIN_INFORMATION
System Log Message Description

User username logged in from host hostname on device tty-name The indicated username was authenticated and logged into the shell specified for it in the password file. Event: This message reports an event, not an error info

Type Severity

LOGIN_LOCAL_PASSWORD
System Log Message Description

Requested local password from user username The PAM authentication attempt failed for the indicated user, who was prompted for the password recorded in the local password file. Event: This message reports an event, not an error info

Type Severity

430

LOGIN_FAILED_SET_LOGIN

Chapter 54: LOGIN System Log Messages

LOGIN_MALFORMED_USER
System Log Message Description Type Severity

Invalid username: username The indicated username was invalid. Event: This message reports an event, not an error info

LOGIN_PAM_AUTHENTICATION_ERROR
System Log Message Description Type Severity

PAM authentication error for user username The login process (login) could not authenticate the indicated user via PAM. Event: This message reports an event, not an error error

LOGIN_PAM_ERROR
System Log Message Description

Failure while authenticating user username: error-message The PAM authentication process failed for the indicated username, for the indicated reason. Error: An error occurred error

Type Severity

LOGIN_PAM_MAX_RETRIES
System Log Message Description

Too many retries while authenticating user username The number of failed PAM authentication attempts for the indicated user exceeded the maximum limit. Error: An error occurred error

Type Severity

LOGIN_PAM_STOP
System Log Message

Failed to end PAM session: error-message

LOGIN_MALFORMED_USER

431

JUNOS 10.1 System Log Messages Reference

Description

The login process (login) could not end the PAM authentication session, for the indicated reason. Error: An error occurred error

Type Severity

LOGIN_PAM_USER_UNKNOWN
System Log Message Description

Attempt to authenticate unknown user username The login process (login) failed to authenticate the indicated user via PAM because the username was unknown. Event: This message reports an event, not an error error

Type Severity

LOGIN_PASSWORD_EXPIRED
System Log Message Description

Forcing change of expired password for user username The password provided for the indicated username was expired and the user was prompted to set a new one. Event: This message reports an event, not an error info

Type Severity

LOGIN_REFUSED
System Log Message Description Type Severity

Login of user username from host hostname on device tty-name was refused: reason A login attempt for the indicated username was rejected for the indicated reason. Event: This message reports an event, not an error notice

LOGIN_ROOT
System Log Message Description

User username logged in as root from host hostname on device tty-name The indicated username was authenticated as a superuser and logged into the shell specified for the root user in the password file. Event: This message reports an event, not an error

Type

432

LOGIN_PAM_STOP

Chapter 54: LOGIN System Log Messages

Severity

info

LOGIN_TIMED_OUT
System Log Message Description Type Severity

Login attempt timed out after duration seconds A login attempt failed to complete in the maximum time allowed. Event: This message reports an event, not an error info

LOGIN_ROOT

433

JUNOS 10.1 System Log Messages Reference

434

LOGIN_TIMED_OUT

Chapter 55

LPDFD System Log Messages

This chapter describes messages with the LPDFD prefix. They are generated by the local policy decision function process (lpdfd). A policy decision function is a component in the IP multimedia subsystem that controls traffic entering the packet-switched network by allocating or denying IP bearer resources.

LPDFD_DYN_PDB_OPEN_FAILED
System Log Message Description Type Severity

Failed to open profile database: error-message The local policy decision function process (lpdfd) failed to open the profile database. Error: An error occurred error

LPDFD_DYN_REGISTER_FAILED
System Log Message Description

Dynamic config register failed: error-message The local policy decision function process (lpdfd) failed to register with the dynamic configuration subsystem. Error: An error occurred error

Type Severity

LPDFD_PCONN_SERVER
System Log Message Description Type Severity

argument: Cannot retrieve peer info for session. Error: error-message The local policy decision function process (lpdfd) pconn server failed to initialize Error: An error occurred error

LPDFD_DYN_PDB_OPEN_FAILED

435

JUNOS 10.1 System Log Messages Reference

436

LPDFD_PCONN_SERVER

Chapter 56

LRMUX System Log Messages

This chapter describes messages with the LRMUX prefix. They are generated by the logical router multiplexer process (lrmuxd), which manages the multiple instances of the routing protocols process (rpd) on a machine running logical routers.

LRMUX_FAILED_EXEC
System Log Message Description

Failed to exec command The Logical Router Multiplexer process (lrmuxd) issued the exec() system call to start a routing process (rpd) to check the validity of the configuration. The system call failed. Error: An error occurred error

Type Severity

LRMUX_LRPD_PID_LOCK
System Log Message Description

Lock not found on PID file filename The Logical Router Multiplexer process (lrmuxd) could not find a lock for a logical router. Error: An error occurred error A logical router process (rpd) died.

Type Severity Cause

LRMUX_LRPD_PID_OPEN
System Log Message Description

Unable to open PID file filename The Logical Router Multiplexer process (lrmuxd) could not open the indicated PID lock file for a logical router process (rpd). Error: An error occurred

Type

LRMUX_FAILED_EXEC

437

JUNOS 10.1 System Log Messages Reference

Severity

error

LRMUX_LRPD_SEND_HUP
System Log Message Description

Unable to send signal to PID pid The Logical Router Multiplexer process (lrmuxd) could not forward a SIGHUP signal to a logical router process (rpd). Error: An error occurred error

Type Severity

LRMUX_PID_LOCK
System Log Message Description

Unable to lock PID file 'filename' The Logical Router 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. Error: An error occurred error

Type Severity

438

LRMUX_LRPD_PID_OPEN

Chapter 57

MCSNOOPD System Log Messages

This chapter describes messages with the MCSNOOPD prefix. They are generated by the multicast snooping process (mcsnoopd), which enables a Layer 2 device to examine the content of Layer 3 packets to determine which actions to perform.

MCSNOOPD_MGMT_TIMEOUT
System Log Message Description

Connection to management peer process-name timed out waiting for input The connection between the snooping process (mcsnoopd) and the indicated management process (mgd) timed out before input arrived from the mgd process. Error: An error occurred warning Examine the messages that immediately follow this message in the system log for information about possible causes. An internal software failure occurred.

Type Severity Action

Cause

MCSNOOPD_MGMT_TIMEOUT

439

JUNOS 10.1 System Log Messages Reference

440

MCSNOOPD_MGMT_TIMEOUT

Chapter 58

MIB2D System Log Messages

This chapter describes messages with the MIB2D prefix. They are generated by the Management Information Base II (MIB II) process (mib2d), which services requests for information gathered and reported by the Simple Network Management Protocol (SNMP).

MIB2D_ATM_ERROR
System Log Message Description Type Severity Cause Action

function-name: error-message The MIB II process (mib2d) could not process ATM-related information. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

MIB2D_CONFIG_CHECK_FAILED
System Log Message Description

function-name: configuration database has errors The portion of the candidate configuration related to the MIB II process (mib2d) was checked for validity during a 'commit' operation. The check failed. Error: An error occurred error The configuration was invalid. Correct the invalid portion of the configuration as described in the error message on the console.

Type Severity Cause Action

MIB2D_ATM_ERROR

441

JUNOS 10.1 System Log Messages Reference

MIB2D_FILE_OPEN_FAILURE
System Log Message Description Type Severity Cause Action

Unable to open file 'filename': error-message The MIB II process (mib2d) could not open the indicated file. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

MIB2D_IFD_IFDINDEX_FAILURE
System Log Message

Ifd index assigned to interface-name changed from old-value to new-value, removing old interface There was a change to the ifd Index assigned to the indicated existing interface. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Description Type Severity Cause Action

MIB2D_IFD_IFINDEX_FAILURE
System Log Message Description Type Severity Cause Action

SNMP index assigned to interface-name changed from old-value to new-value There was a change to the SNMP ifIndex assigned to the indicated existing interface. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

442

MIB2D_FILE_OPEN_FAILURE

Chapter 58: MIB2D System Log Messages

MIB2D_IFL_IFINDEX_FAILURE
System Log Message

SNMP index assigned to interface-name.interface-unit changed from old-value to new-value There was a change to the SNMP ifIndex assigned to the indicated existing interface. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Description Type Severity Cause Action

MIB2D_IF_FLAPPING_MISSING
System Log Message

function-name: interface flapping missing: ifname(interface-name) old if_anydown_flaps(old-value) if_anydown_flaps(new-value) The MIB II process (mib2d) is blocked in the kernel for synchronous messages. If there is an interface flap (down and then back up again) when mib2d is blocked in the kernel, mib2d will miss asynchronous messages from the kernel about state changes. Event: This message reports an event, not an error notice

Description

Type Severity

MIB2D_KVM_FAILURE
System Log Message Description Type Severity Cause Action

function-name: reason: error-message A call to the indicated function in the kernel virtual memory library failed. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

MIB2D_PMON_OVERLOAD_CLEARED_TRAP
System Log Message

Overload name: overload-name, interface: interface-name

MIB2D_IFL_IFINDEX_FAILURE

443

JUNOS 10.1 System Log Messages Reference

Description

The MIB II process (mib2d) generated a jnxPMonOverloadCleared trap when it detected the clearing of an overload condition on the indicated monitoring services interface. Event: This message reports an event, not an error warning

Type Severity

MIB2D_PMON_OVERLOAD_SET_TRAP
System Log Message Description

Overload name: overload-name, interface: interface-name The MIB II process (mib2d) generated a jnxPMonOverloadSet trap when it detected an overload condition on the indicated monitoring services interface. Event: This message reports an event, not an error warning

Type Severity

MIB2D_RTSLIB_READ_FAILURE
System Log Message Description

function-name: failed in operation object-name: index (error-message) A call to the indicated function in the routing socket library failed during the indicated operation on the indicated object. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

MIB2D_RTSLIB_SEQ_MISMATCH
System Log Message Description

function-name: sequence mismatch (expected-value, received-value), resyncing The indicated function in the routing socket library detected a sequence number mismatch. The MIB II process (mib2d) will resynchronize its data with the JUNOS kernel. Event: This message reports an event, not an error info

Type Severity

444

MIB2D_PMON_OVERLOAD_CLEARED_TRAP

Chapter 58: MIB2D System Log Messages

MIB2D_SNMP_INDEX_ASSIGN
System Log Message

function-name: reason snmpid(snmp-interface-index) ifname(interface-name.interface-unit) MIB2D can not assign snmp index for each interface. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Description Type Severity Cause Action

MIB2D_SNMP_INDEX_DUPLICATE
System Log Message

function-name: duplicate snmpid(snmp-interface-index) old ifname(interface-name.interface-unit) new ifname(new-interface-name.kernel-interface-unit) The SNMP index for first interface name was assigned the same SNMP index as second interface name. Error: An error occurred emergency An internal software failure occurred. Contact your technical support representative.

Description

Type Severity Cause Action

MIB2D_SNMP_INDEX_UPDATE_STAT
System Log Message Description Type Severity Cause Action

function-name reason filename MIB2D can not get the status of SNMP index file Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

MIB2D_SNMP_INDEX_ASSIGN

445

JUNOS 10.1 System Log Messages Reference

MIB2D_SNMP_INDEX_WRITE
System Log Message Description Type Severity Cause Action

function-name: reason filename MIB2D can not write into a file containing all the indices Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

MIB2D_SYSCTL_FAILURE
System Log Message Description Type Severity Cause Action

function-name: sysctl type failed: error-message A request to the JUNOS kernel for system data failed. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

MIB2D_TRAP_HEADER_FAILURE
System Log Message Description Type Severity Cause Action

function-name: trap_request_header failed The MIB II process (mib2d) could not allocate a trap header. Error: An error occurred error The Routing Engine is low on memory. Contact your technical support representative.

MIB2D_TRAP_SEND_FAILURE
System Log Message

function-name: trap_request_send: error-message

446

MIB2D_SNMP_INDEX_WRITE

Chapter 58: MIB2D System Log Messages

Description Type Severity Cause Action

The MIB II process (mib2d) could not send a trap header. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

MIB2D_TRAP_SEND_FAILURE

447

JUNOS 10.1 System Log Messages Reference

448

MIB2D_TRAP_SEND_FAILURE

Chapter 59

MPLS_OAM System Log Messages

This chapter describes messages with the MPLS_OAM prefix. They are generated by the Multiprotocol Label Switching (MPLS) Operation, Administration, and Maintenance (OAM) process (mplsoamd), which supports traceroute operations for LDP label-switched paths (LSPs).

MPLS_OAM_FANOUT_LIMIT_REACHED
System Log Message Description Type Severity Action

fec-address: traceroute fanout limit was reached The traceroute fanout limit was reached. Error: An error occurred info Raise the traceroute fanout limit parameter.

MPLS_OAM_INVALID_SOURCE_ADDRESS
System Log Message Description Type Severity Action

fec-address: source address ip-address is invalid The traceroute utility is configured to use an invalid source address. Error: An error occurred error Configure traceroute to use a valid source address.

MPLS_OAM_PATH_LIMIT_REACHED
System Log Message Description Type

fec-address: traceroute path limit was reached The traceroute path limit was reached. Error: An error occurred

MPLS_OAM_FANOUT_LIMIT_REACHED

449

JUNOS 10.1 System Log Messages Reference

Severity Action

info Raise the traceroute path limit parameter.

MPLS_OAM_SEND_FAILED
System Log Message Description

fec-address: unable to send probe (error-message) The Multiprotocol Label Switching (MPLS) Operation, Administration, and Maintenance (OAM) process (mplsoamd) could not send a traceroute probe packet. Error: An error occurred error Contact your technical support representative.

Type Severity Action

MPLS_OAM_SOCKET_OPEN_FAILED
System Log Message Description

fec-address: unable to open socket (error-message) The Multiprotocol Label Switching (MPLS) Operation, Administration, and Maintenance (OAM) process (mplsoamd) could not open a socket to initiate a traceroute operation. Error: An error occurred error Contact your technical support representative.

Type Severity Action

MPLS_OAM_SOCKET_SELECT_FAILED
System Log Message Description

fec-address: unable to select socket (error-message) The Multiprotocol Label Switching (MPLS) Operation, Administration, and Maintenance (OAM) process (mplsoamd) could not select a socket to initiate a traceroute operation. Error: An error occurred error Contact your technical support representative.

Type Severity Action

MPLS_OAM_TRACEROUTE_INTERRUPTED
System Log Message

fec-address: topology update interrupted traceroute

450

MPLS_OAM_PATH_LIMIT_REACHED

Chapter 59: MPLS_OAM System Log Messages

Description Type Severity Action

A traceroute operation was interrupted by a topology change. Event: This message reports an event, not an error info Wait for the next scheduled traceroute operation.

MPLS_OAM_TTL_EXPIRED
System Log Message Description Type Severity Action

fec-address: traceroute TTL limit was reached The time-to-live (TTL) limit for the traceroute utility was reached. Error: An error occurred info Raise the traceroute TTL limit parameter.

MPLS_OAM_UNREACHABLE
System Log Message Description

fec-address: traceroute encountered unreachable node The traceroute utility encountered a node that does not have a computable destination address. The Multiprotocol Label Switching (MPLS) Operation, Administration, and Maintenance (OAM) process (mplsoamd) therefore could not send a probe to the node. Error: An error occurred info Contact your technical support representative.

Type Severity Action

MPLS_OAM_TRACEROUTE_INTERRUPTED

451

JUNOS 10.1 System Log Messages Reference

452

MPLS_OAM_UNREACHABLE

Chapter 60

NEXTHOP System Log Messages

This chapter describes messages with the NEXTHOP prefix. They are generated by the process that decides the next hop.

NEXTHOP_COMPONENTS_LIMIT_REACHED
System Log Message Description

Limit on components reached for flood next hop for routing instance 'routing-instance' 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. Event: This message reports an event, not an error error

Type Severity

NEXTHOP_COMPONENTS_LIMIT_REACHED

453

JUNOS 10.1 System Log Messages Reference

454

NEXTHOP_COMPONENTS_LIMIT_REACHED

Chapter 61

NSD System Log Messages

This chapter describes messages with the NSD prefix. They are generated by the network security process (nsd), which manages firewall configuration on routers running JUNOS Software with enhanced services.

NSD_MEMORY_ALLOC_FAILED
System Log Message Description

Unable to allocate count bytes of memory The network security process (nsd) could not allocate the indicated number of bytes of memory. Error: An error occurred error It is possible that system memory is exhausted. Increase the amount of RAM in the Routing Engine.

Type Severity Cause Action

NSD_RESTART_COMP_CFG_READ_FAILED
System Log Message Description

Subcomponent could not read configuration database As the network security process (nsd) restarted, one or more of its subcomponents could not read its configuration information from configuration database. The nsd process restarted anyway, and routing performance was not affected. Error: An error occurred error

Type Severity

NSD_SEC_NODE_COMP_SYNC_FAILED
System Log Message Description

One or more subcomponents could not sync their state on backup RE One or more subcomponents of the network security process (nsd) failed to synchronize their state when the nsd restarted on secondary mode.

NSD_MEMORY_ALLOC_FAILED

455

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

456

NSD_SEC_NODE_COMP_SYNC_FAILED

Chapter 62

NSTRACED System Log Messages

This chapter describes messages with the NSTRACED prefix. They are generated by the USP trace process (nstraced).

NSTRACED_MEMORY_ALLOC_FAILED
System Log Message Description

Unable to allocate count bytes of memory The USP trace process (nstraced) could not allocate the indicated number of bytes of memory. Error: An error occurred error System memory was exhausted. Increase the amount of RAM in the Routing Engine.

Type Severity Cause Action

NSTRACED_RESTART_CFG_READ_FAILED
System Log Message Description

Subcomponent could not read configuration database When the USP trace process (nstraced) restarted, it could not read its configuration information from the configuration database. Error: An error occurred error

Type Severity

NSTRACED_MEMORY_ALLOC_FAILED

457

JUNOS 10.1 System Log Messages Reference

458

NSTRACED_RESTART_CFG_READ_FAILED

Chapter 63

PFE System Log Messages

This chapter describes messages with the PFE prefix. They are generated by the Packet Forwarding Engine controller, which manages packet forwarding functions.

PFE_ANALYZER_CFG_FAILED
System Log Message Description

Error in Analyzer error-message for index = index error-code = error-code The configuration analyzer terminated because an error occured during the configuration. Error: An error occurred error

Type Severity

PFE_ANALYZER_SHIM_CFG_FAILED
System Log Message Description

Error in Analyzer error-message for index = index error-code = error-code The configuration analyzer terminated because an error occured while the chip was being programmed. Error: An error occurred error

Type Severity

PFE_ANALYZER_TABLE_WRITE_FAILED
System Log Message Description Type Severity

index Could not create analyzer error-message table The logical interfaces (ifl) index failed to configure the analyzer because of an error. Error: An error occurred error

PFE_ANALYZER_CFG_FAILED

459

JUNOS 10.1 System Log Messages Reference

PFE_ANALYZER_TASK_FAILED
System Log Message Description Type Severity

Following task failed : error-message The task analyzer terminated because an error occurred during the task. Error: An error occurred error

PFE_CBF_UNSUPPORTED
System Log Message Description

Internet Processor I does not support CoS-based forwarding The Internet Processor I application-specific integrated circuit (ASIC) does not support class-of-service (CoS)-based forwarding (CBF). Event: This message reports an event, not an error warning

Type Severity

PFE_COS_B2_ONE_CLASS
System Log Message

COSMAN: classifier classifier-id-new for ifl index replaces classifer classifier-id-old still used Only one classifier can be active on a B2-based FPC at any given time. Error: An error occurred error

Description Type Severity

PFE_COS_B2_UNSUPPORTED
System Log Message Description

COSMAN: B2 FPC cannot support classifier type classifier-type-name B2-based FPCs can only handle IP precedence classifiers. They do not support any other classifier. Error: An error occurred error

Type Severity

460

PFE_ANALYZER_TASK_FAILED

Chapter 63: PFE System Log Messages

PFE_FW_DELETE_MISMATCH_ERR
System Log Message

Instance mismatch for type (installed-firewall-name != deleted-firewall-name) ifl logical-interface-index family protocol-family Before a firewall is deleted, it is sanity checked against what is installed in the forwarding topology. A mismatch was detected between the firewall to be deleted and the forwarding topology, and the delete operation was canceled. Error: An error occurred error

Description

Type Severity

PFE_FW_IF_DIALER_ERR
System Log Message Description

DFW: output type (firewall-name) on ifl logical-interface-index rejected, invalid interface Firewalls that use the ipsec-sa action to forward traffic to an IP Security (IPSec) security association (SA) cannot be configured on the ES Physical Interface Card (PIC) that services the SA. That configuration creates traffic loops within the router and was probably unintended. The problematic filter was automatically removed from the indicated interface. Error: An error occurred error

Type Severity

PFE_FW_IF_INPUT_ERR
System Log Message Description

DFW: input type (firewall-name) on ifl logical-interface-index rejected, invalid interface Firewalls that use the ipsec-sa action to forward traffic to an IP Security (IPSec) security association (SA) cannot be configured on the ES Physical Interface Card (PIC) that services the SA. That configuration creates traffic loops within the router and was probably unintended. The problematic firewall was automatically removed from the indicated interface. Error: An error occurred error

Type Severity

PFE_FW_IF_OUTPUT_ERR
System Log Message Description

DFW: output type (firewall-name) on ifl logical-interface-index rejected, invalid interface Firewalls that use the ipsec-sa action to forward traffic to an IP Security (IPSec) security association (SA) cannot be configured on the ES Physical Interface Card (PIC) that services the SA. That configuration creates traffic loops within the router and

PFE_FW_DELETE_MISMATCH_ERR

461

JUNOS 10.1 System Log Messages Reference

was probably unintended. The problematic firewall was automatically removed from the indicated interface.
Type Severity

Error: An error occurred error

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 Before a postservice firewall is deleted, it is sanity checked against what is installed in the forwarding topology. A mismatch was detected between the firewall to be deleted and the forwarding topology, and the delete operation was canceled. Error: An error occurred error

Description

Type Severity

PFE_FW_SYSLOG_ETH
System Log Message

FW: interface-name action destination-address source-address protocol-name (count packets) An Ethernet frame matched against a stateless firewall filter with the indicated 'syslog' action (A = Accept, D = Discard, R = Reject). Event: This message reports an event, not an error info

Description

Type Severity

PFE_FW_SYSLOG_IP
System Log Message

FW: interface-name action protocol-name source-address destination-address source-port-or-type destination-port-or-code (count packets) An IP packet matched against a stateless firewall filter with the indicated 'syslog' action (A = Accept, D = Discard, R = Reject). Event: This message reports an event, not an error info

Description

Type Severity

PFE_FW_SYSLOG_IP6_GEN
System Log Message

FW: interface-name action protocol-name source-address destination-address (count packets)

462

PFE_FW_IF_OUTPUT_ERR

Chapter 63: PFE System Log Messages

Description

An IP version 6 (IPv6) packet matched against a stateless firewall filter with the indicated 'syslog' action (A = Accept, D = Discard, R = Reject). Event: This message reports an event, not an error info

Type Severity

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) An IP version 6 (IPv6) Internet Control Message Protocol (ICMP) packet matched against a stateless firewall filter with the indicated 'syslog' action (A = Accept, D = Discard, R = Reject). Event: This message reports an event, not an error info

Description

Type Severity

PFE_FW_SYSLOG_IP6_TCP_UDP
System Log Message

FW: interface-name action protocol-name source-address destination-address sport:source-port dport:destination-port (count packets) An IP version 6 (IPv6) Transmission Control Protocol/User Datagram Protocol (TCP/UDP) packet matched against a stateless firewall filter with the indicated 'syslog' action (A = Accept, D = Discard, R = Reject). Event: This message reports an event, not an error info

Description

Type Severity

PFE_MGCP_ADD_CA_PORT_FAIL
System Log Message Description Type Severity

Failed to add the MGCP Call Agent port to application definition table Failed to add the MGCP Call Agent port to the application definition table. Error: An error occurred error

PFE_MGCP_ADD_UA_PORT_FAIL
System Log Message Description

Failed to add the MGCP UA port to application definition table Failed to add the MGCP User Agent port to the application definition table.

PFE_FW_SYSLOG_IP6_GEN

463

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

PFE_MGCP_DEL_CA_PORT_FAIL
System Log Message Description Type Severity

Failed to delete the MGCP Call Agent port from application definition table Failed to remove the MGCP Call Agent port from the application definition table. Error: An error occurred error

PFE_MGCP_DEL_UA_PORT_FAIL
System Log Message Description Type Severity

Failed to delete the MGCP User Agent port from application definition table Failed to remove the MGCP User Agent port from the application definition table. Error: An error occurred error

PFE_MGCP_MEM_INIT_FAILED
System Log Message Description Type Severity

Failed to create memory pool for error-message Failed to initialize the MGCP memory pool. Error: An error occurred error

PFE_MGCP_REG_HDL_FAIL
System Log Message Description Type Severity

Failed to register object-name handle Failed to register the handler with the external module. Error: An error occurred error

PFE_NH_RESOLVE_THROTTLED
System Log Message

Next-hop resolution requests from interface logical-interface-index throttled

464

PFE_MGCP_ADD_UA_PORT_FAIL

Chapter 63: PFE System Log Messages

Description

The Packet Forwarding Engine throttled next-hop resolution requests from the indicated interface, because the high number of requests might constitute an attempted denial-of-service (DoS) attack. Examples of events that generate next-hop resolution requests include an attempt to forward a packet without an Address Resolution Protocol (ARP) entry and receiving a multicast data packet with no matching route. Normally, the Packet Forwarding Engine forwards the requests to the Routing Engine. Event: This message reports an event, not an error info

Type Severity

PFE_SCCP_ADD_PORT_FAIL
System Log Message Description Type Severity

Failed to add SCCP ALG port to application definition table Failed to add the SCCP port to the application definition table. Error: An error occurred error

PFE_SCCP_DEL_PORT_FAIL
System Log Message Description Type Severity

Failed to remove SCCP ALG port from application definition table Failed to delete the SCCP port from application definition table. Error: An error occurred error

PFE_SCCP_REG_NAT_VEC_FAIL
System Log Message Description Type Severity

Failed to add SCCP ALG vector to flow module Failed to register the SCCP vector with the flow module. Error: An error occurred error

PFE_SCCP_REG_RM_FAIL
System Log Message Description

Failed to register SCCP client to Resource Manager Failed to register the SCCP Resource Manager client.

PFE_NH_RESOLVE_THROTTLED

465

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

PFE_SCCP_REG_VSIP_FAIL
System Log Message Description Type Severity

Failed to register SCCP client to VoIP State IP port Failed to register the SCCP client to VoIP State IP port. Error: An error occurred error

PFE_SCCP_RM_CLIENTID_FAIL
System Log Message Description Type Severity

Failed to get SCCP Resource Manager client identifier Failed to get the SCCP Resource Manager client identifier. Error: An error occurred error

PFE_SCREEN_CFG_ERROR
System Log Message Description Type Severity

fail to operation the screen config due to error-message faile to change the configuration of screen module Error: An error occurred error

PFE_SCREEN_CFG_EVENT
System Log Message Description Type Severity

[operation]: screen name - context-name configuration of screen module is changed Event: This message reports an event, not an error info

PFE_SCREEN_MT_CFG_ERROR
System Log Message

failed to operation the screen config due to error-message

466

PFE_SCCP_REG_RM_FAIL

Chapter 63: PFE System Log Messages

Description Type Severity

failed to change the configuration of screen module Error: An error occurred error

PFE_SCREEN_MT_CFG_EVENT
System Log Message Description Type Severity

[operation]: screen name - context-name configuration of screen module is changed Event: This message reports an event, not an error info

PFE_SFLOW_CONFIGURATION_FAILED
System Log Message Description Type Severity

sflow configuration on hardware failed for ifl index = index The sflow configuration for the ifl index could not be programmed in the hardware Error: An error occurred error

PFE_SFLOW_HARDWARE_CFG_FAILED
System Log Message Description Type Severity

dev = device-id, port = destination-port, hardware error-code = error-code The sflow configuration for the port could not be programmed in the hardware Error: An error occurred error

PFE_SIP_ADD_PORT_FAIL
System Log Message Description Type Severity

Failed to add SIP ALG port to application definition table Failed to add the SIP port to the application definition table. Error: An error occurred error

PFE_SCREEN_MT_CFG_ERROR

467

JUNOS 10.1 System Log Messages Reference

PFE_SIP_DEL_PORT_FAIL
System Log Message Description Type Severity

Failed to delete SIP ALG port from application definition table Failed to remove the SIP port from the application definition table. Error: An error occurred error

PFE_SIP_MEM_INIT_FAILED
System Log Message Description Type Severity

Failed to create memory pool for object-name Failed to create a memory pool for SIP. Error: An error occurred error

PFE_SIP_REG_HDL_FAIL
System Log Message Description Type Severity

Failed to register object-name handle Failed to register the handler with the external module. Error: An error occurred error

PFE_USP_TRACE_BUFFER_CREATE
System Log Message Description

USP Trace buffer created for identifier. The USP Packet Forwarding Engine (PFE) created a trace buffer for the indicated identifier. Event: This message reports an event, not an error info

Type Severity

PFE_USP_TRACE_BUFFER_DELETE
System Log Message

Deleting USP trace buffer for identifier.

468

PFE_SIP_DEL_PORT_FAIL

Chapter 63: PFE System Log Messages

Description

The USP Packet Forwarding Engine (PFE) deleted a trace buffer for the indicated identifier. Event: This message reports an event, not an error info

Type Severity

PFE_USP_TRACE_BUFFER_LIMIT
System Log Message Description

Number of buffered records limited to requested-size for identifier. The USP Packet Forwarding Engine (PFE) trace buffers were limited to the indicated size for the indicated identifier. Event: This message reports an event, not an error info

Type Severity

PFE_USP_TRACE_BUFFER_MEM_FAIL
System Log Message Description

Cannot allocate buffer to hold requested-size records for identifier. The USP Packet Forwarding Engine (PFE) did not allocate buffers of the indicated size for the indicated identifier. Error: An error occurred error

Type Severity

PFE_USP_TRACE_BUFFER_MODIFY
System Log Message Description

USP Trace buffer modified for identifier. The USP Packet Forwarding Engine (PFE) modified trace buffers for the indicated identifier. Event: This message reports an event, not an error info

Type Severity

PFE_USP_TRACE_BUFFER_DELETE

469

JUNOS 10.1 System Log Messages Reference

470

PFE_USP_TRACE_BUFFER_MODIFY

Chapter 64

PFED System Log Messages

This chapter describes messages with the PFED prefix. They are generated by the Packet Forwarding Engine process, which gathers and reports Packet Forwarding Engine statistics.

PFED_NOTIFICATION_STATS_FAILED
System Log Message Description

Unable to retrieve notification statistics The Packet Forwarding Engine process (pfed) could not retrieve Packet Forwarding Engine notification statistics. Error: An error occurred warning

Type Severity

PFED_NOTIFICATION_STATS_FAILED

471

JUNOS 10.1 System Log Messages Reference

472

PFED_NOTIFICATION_STATS_FAILED

Chapter 65

PGCPD System Log Messages

This chapter describes messages with the PGCPD prefix. They are generated by the pgcpd process. This process decodes Packet Gateway Control Protocol (PGCP) messages that virtual packet gateways (VPG) receive from the packet gateway controller (PGC) and translates these messages to interprocess communication (IPC) messages.

PGCPD_SHUTDOWN
System Log Message Description Type Severity

The pgcpd process shut down The packet gateway control process (pgcpd) state was shut down. Event: This message reports an event, not an error notice

PGCPD_STARTUP
System Log Message Description Type Severity

The pgcpd process just started up The packet gateway control process (pgcpd) just started up Event: This message reports an event, not an error notice

PGCPD_SWITCH_OVER
System Log Message Description Type Severity

switch over Switch over from active to backup Routing Engine Event: This message reports an event, not an error warning

PGCPD_SHUTDOWN

473

JUNOS 10.1 System Log Messages Reference

474

PGCPD_SWITCH_OVER

Chapter 66

PING System Log Messages

This chapter describes messages with the PING prefix. They are generated by the ping command, which tests whether a remote machine is accessible across the network.

PING_EGRESS_JITTER_THRESH_EXCEED
System Log Message Description

pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name The jitter for the egress trip time exceeded the configured threshold during the indicated test conducted by the indicated user. Event: This message reports an event, not an error info

Type Severity

PING_EGRESS_STDDEV_THRESH_EXCEED
System Log Message Description

pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name The standard deviation of the egress trip time exceeded the configured threshold during the indicated test conducted by the indicated user. Event: This message reports an event, not an error info

Type Severity

PING_EGRESS_THRESHOLD_EXCEEDED
System Log Message Description

pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name The egress trip time measured for a probe exceeded the configured threshold during the indicated test conducted by the indicated user. Event: This message reports an event, not an error info

Type Severity

PING_EGRESS_JITTER_THRESH_EXCEED

475

JUNOS 10.1 System Log Messages Reference

PING_INGRESS_JTR_THRESH_EXCEED
System Log Message Description

pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name The jitter for the ingress trip time exceeded the configured threshold during the indicated test conducted by the indicated user. Event: This message reports an event, not an error info

Type Severity

PING_INGRESS_STDDV_THRESH_EXCEED
System Log Message Description

pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name The standard deviation of the ingress trip time exceeded the configured threshold during the indicated test conducted by the indicated user. Event: This message reports an event, not an error info

Type Severity

PING_INGRESS_THRESHOLD_EXCEEDED
System Log Message Description

pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name The ingress trip time measured for a probe exceeded the configured threshold during the indicated test conducted by the indicated user. Event: This message reports an event, not an error info

Type Severity

PING_PROBE_FAILED
System Log Message Description

pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name The number of successive probe failures exceeded the pingCtlTrapProbeFailureFilter threshold. Event: This message reports an event, not an error info

Type Severity

476

PING_INGRESS_JTR_THRESH_EXCEED

Chapter 66: PING System Log Messages

PING_RTT_JTR_THRESH_EXCEED
System Log Message Description

pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name The jitter for the round trip time exceeded the configured threshold during the indicated test conducted by the indicated user. Event: This message reports an event, not an error info

Type Severity

PING_RTT_STDDV_THRESH_EXCEED
System Log Message Description

pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name The standard deviation of the round trip time exceeded the configured threshold during the indicated test conducted by the indicated user. Event: This message reports an event, not an error info

Type Severity

PING_RTT_THRESHOLD_EXCEEDED
System Log Message Description

pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name The round trip time measured for a probe exceeded the configured threshold during the indicated test conducted by the indicated user. Event: This message reports an event, not an error info

Type Severity

PING_TEST_COMPLETED
System Log Message Description

pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name All probes were sent and the number of failed probes was less than the pingCtlTrapTestFailureFilter threshold. Event: This message reports an event, not an error info

Type Severity

PING_RTT_JTR_THRESH_EXCEED

477

JUNOS 10.1 System Log Messages Reference

PING_TEST_FAILED
System Log Message Description

pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name All probes were sent but the number of failed probes equaled or exceeded the pingCtlTrapTestFailureFilter threshold. Event: This message reports an event, not an error info

Type Severity

PING_UNKNOWN_THRESH_TYPE_EXCEED
System Log Message Description

pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name An unknown type of threshold event was reported during the indicated test conducted by the indicated user. Event: This message reports an event, not an error info

Type Severity

478

PING_TEST_FAILED

Chapter 67

PPMD System Log Messages

This chapter describes messages with the PPMD prefix. They are generated by the periodic packet management process (ppmd), which maintains routing protocol adjacencies for the routing protocol process (rpd).

PPMD_ASSERT_SOFT
System Log Message

Soft assertion failed at line line-number in file 'source-filename' with error "message", but ppmd with PID pid continued running The source code for the periodic package management process (ppmd) includes internal self-consistency checks. As the ppmd process with the indicated process ID (PID) executed the binary compiled from the indicated source file, a check failed at the indicated line number in the file. The ppmd process created a diagnostic core file for analysis by technical support personnel and continued to run. Error: An error occurred error An internal software failure occurred. Examine the messages that immediately follow this message in the system log for information about possible causes. Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core file, if requested.

Description

Type Severity Cause Action

PPMD_OPEN_ERROR
System Log Message Description

function-name: open error on pipe to protocol-name (error-message) The periodic packet management process (ppmd) could not initialize the indicated protocol. Error: An error occurred error Contact your technical support representative.

Type Severity Action

PPMD_ASSERT_SOFT

479

JUNOS 10.1 System Log Messages Reference

PPMD_READ_ERROR
System Log Message Description

Read error on pipe from protocol-name: reason (error-message) The periodic packet management process (ppmd) could not read a message on a pipe for the indicated protocol. Error: An error occurred info Contact your technical support representative.

Type Severity Action

PPMD_WRITE_ERROR
System Log Message Description

function-name: write error on pipe to protocol-name (error-message) The periodic packet management process (ppmd) could not write a message on a pipe for the indicated protocol. Error: An error occurred error Contact your technical support representative.

Type Severity Action

480

PPMD_READ_ERROR

Chapter 68

PPPD System Log Messages

This chapter describes messages with the PPPD prefix. They are generated by the Point-to-Point Protocol (PPP) process (pppd), which processes packets that use PPP.

PPPD_AUTH_CREATE_FAILED
System Log Message Description

Unable to allocate authentication handle: error-message The Point-to-Point Protocol process (pppd) could not allocate an authentication object, for the indicated reason. Error: An error occurred error

Type Severity

PPPD_CHAP_AUTH_IN_PROGRESS
System Log Message

Interface interface-name received response 'operation' with CHAP ID message-id, but was still authenticating previous response The Point-to-Point Protocol process (pppd) received another Challenge Handshake Authentication Protocol (CHAP) response from a peer while authenticating a previous CHAP response sent by that peer. The peer is resending CHAP responses faster than the pppd process can process them. Error: An error occurred error

Description

Type Severity

PPPD_CHAP_GETHOSTNAME_FAILED
System Log Message Description

interface-name: Unable to obtain hostname for outgoing CHAP message: error-message The Point-to-Point Protocol process (pppd) could not obtain the hostname needed to fill in the 'Name' field in an outgoing CHAP packet. Error: An error occurred

Type

PPPD_AUTH_CREATE_FAILED

481

JUNOS 10.1 System Log Messages Reference

Severity

error

PPPD_CHAP_INVALID_IDENTIFIER
System Log Message

Interface interface-name received 'operation' message with CHAP ID message-id instead of expected ID expected-value The Point-to-Point Protocol process (pppd) received a Challenge Handshake Authentication Protocol (CHAP) message from a peer that included the indicated message identifier, which did not match the indicated expected value. Error: An error occurred info

Description

Type Severity

PPPD_CHAP_INVALID_OPCODE
System Log Message

interface-name: received invalid operation code operation (type operation-code, CHAP ID message-id) The Point-to-Point Protocol process (pppd) received a Challenge Handshake Authentication Protocol (CHAP) message that included the indicated operation code, which is invalid. Error: An error occurred error

Description

Type Severity

PPPD_CHAP_LOCAL_NAME_UNAVAILABLE
System Log Message Description

Unable to determine value for 'Name' in outgoing CHAP packet The Point-to-Point Protocol process (pppd) could not determine the value needed to fill in the 'Name' field in an outgoing Challenge Handshake Authentication Protocol (CHAP) packet, because either the local name was not specified or pppd could not determine the hostname. Error: An error occurred error

Type Severity

PPPD_CHAP_OPERATION_UNEXPECTED
System Log Message Description

interface-name: unexpected operation type operation (CHAP ID message-id) The Challenge Handshake Authentication Protocol (CHAP) message with the indicated identifier had the indicated operation type, which the Point-to-Point Protocol process (pppd) did not expect.

482

PPPD_CHAP_GETHOSTNAME_FAILED

Chapter 68: PPPD System Log Messages

Type Severity

Error: An error occurred info

PPPD_CHAP_REPLAY_ATTACK_DETECTED
System Log Message

interface-name: received operation with CHAP ID message-id, which is identical to an outstanding challenge. Peer is trying to exhort response value. During an exchange of authentication messages, a peer responded to a challenge message from the Point-to-Point Protocol process (pppd) by returning the same message. The pppd process did not respond to the peer, because doing so would provide the answer to the original challenge. The peer must provide the answer on its own for authentication to succeed. Error: An error occurred error

Description

Type Severity

PPPD_EVLIB_CREATE_FAILURE
System Log Message Description

Unable to create event context: error-message The Point-to-Point Protocol process (pppd) could not create a context for handling asynchronous events, for the indicated reason. Error: An error occurred error

Type Severity

PPPD_LOCAL_CREATE_FAILED
System Log Message Description

Unable to allocate LOCAL module handle: error-message The Point-to-Point Protocol process (pppd) attempted to allocate a locally configured 'password' authentication module as part of its authentication sequence. The allocation failed. Error: An error occurred error

Type Severity

PPPD_MEMORY_ALLOCATION_FAILURE
System Log Message Description

Unable to allocate memory for object object-name: error-message The Point-to-Point Protocol process (pppd) could not allocate memory from the heap for the indicated object.

PPPD_CHAP_OPERATION_UNEXPECTED

483

JUNOS 10.1 System Log Messages Reference

Type Severity Action

Error: An error occurred error Contact your technical support representative.

PPPD_PAP_GETHOSTNAME_FAILED
System Log Message

Unable to obtain hostname for PAP message sent from interface interface-name: error-message The Point-to-Point Protocol process (pppd) could not obtain the hostname it needed to fill in the 'Name' field in an outgoing Password Authentication Protocol (PAP) packet sent from the indicated interface. Error: An error occurred error

Description

Type Severity

PPPD_PAP_INVALID_IDENTIFIER
System Log Message

Interface interface-name received 'operation' message with PAP ID message-id instead of expected ID expected-value The Point-to-Point Protocol process (pppd) received a Password Authentication Protocol (PAP) message from a peer that included the indicated identifier, which did not match the indicated expected value. Error: An error occurred info

Description

Type Severity

PPPD_PAP_INVALID_OPCODE
System Log Message

Interface interface-name received 'operation' message with PAP ID message-id and invalid operation code operation-code The Point-to-Point Protocol process (pppd) received a Password Authentication Protocol (PAP) message from a peer that included the indicated operation code, which is invalid. Error: An error occurred error

Description

Type Severity

PPPD_PAP_LOCAL_PASSWORD_UNAVAIL
System Log Message

Unable to determine value for 'Password' in outgoing PAP packet

484

PPPD_MEMORY_ALLOCATION_FAILURE

Chapter 68: PPPD System Log Messages

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. Error: An error occurred error The local password was not defined for the local hostname.

Type Severity Cause

PPPD_PAP_OPERATION_UNEXPECTED
System Log Message Description

interface-name: unexpected operation type operation (PAP ID message-id) The Point-to-Point Protocol process (pppd) received a Password Authentication Protocol (PAP) message with the indicated identifier and operation type. The operation type was not valid. Error: An error occurred info

Type Severity

PPPD_POOL_ADDRESSES_EXHAUSTED
System Log Message

No addresses available in pool "pool-name" to assign to remote peer on interface interface-name The Point-to-Point Protocol process (pppd) could not assign an address from the indicated address pool to the remote peer on the indicated interface, because there were no more addresses available in the pool. Error: An error occurred error Increase the number of addresses in the address pool.

Description

Type Severity Action

PPPD_RADIUS_ADD_SERVER_FAILED
System Log Message Description

Unable to add RADIUS server radius-server for profile access-profile: error-message The Point-to-Point Protocol process (pppd) could not add the indicated RADIUS server for the indicated access profile. Error: An error occurred error

Type Severity

PPPD_PAP_LOCAL_PASSWORD_UNAVAIL

485

JUNOS 10.1 System Log Messages Reference

PPPD_RADIUS_ALLOC_PASSWD_FAILED
System Log Message Description

Unable to allocate RADIUS password of size size: error-message The Point-to-Point Protocol process (pppd) could not allocate space for a temporary Challenge Handshake Authentication Protocol (CHAP) RADIUS password of the indicated size. Error: An error occurred error

Type Severity

PPPD_RADIUS_CREATE_FAILED
System Log Message Description

Unable to allocate RADIUS module handle: error-message The Point-to-Point Protocol process (pppd) attempted to allocate a RADIUS authentication module as part of its authentication sequence. The allocation failed. Error: An error occurred error

Type Severity

PPPD_RADIUS_CREATE_REQ_FAILED
System Log Message Description

Unable to create RADIUS access request message: error-message The Point-to-Point Protocol process (pppd) could not create an access request message to send to the RADIUS server. Error: An error occurred error

Type Severity

PPPD_RADIUS_GETHOSTNAME_FAILED
System Log Message Description

Unable to obtain hostname for outgoing RADIUS message: error-message The Point-to-Point Protocol process (pppd) could not obtain the hostname it needed to fill in the PPP_IDENTIFIER field in an outgoing RADIUS message. Error: An error occurred error

Type Severity

486

PPPD_RADIUS_ALLOC_PASSWD_FAILED

Chapter 68: PPPD System Log Messages

PPPD_RADIUS_MESSAGE_UNEXPECTED
System Log Message Description

Unknown response from RADIUS server: return-value The RADIUS authentication module for the Point-to-Point Protocol process (pppd) received a message from the RADIUS server that it could not process. Error: An error occurred error

Type Severity

PPPD_RADIUS_NO_VALID_SERVERS
System Log Message Description

Unable to find valid RADIUS server for profile access-profile The Point-to-Point Protocol process (pppd) could not access a valid RADIUS server to use for the indicated access profile. Error: An error occurred error

Type Severity

PPPD_RADIUS_OPEN_FAILED
System Log Message Description

rad_auth_open failed: error-message The Point-to-Point Protocol process (pppd) could not create a RADIUS object handle, which it uses to communicate with the RADIUS server. Error: An error occurred error

Type Severity

PPPD_RADIUS_ROUTE_INST_ENOENT
System Log Message

Ignored RADIUS server radius-server for profile access-profile because routing instance routing-instance did not exist The indicated routing instance, which the Point-to-Point Protocol process (pppd) uses for routing of RADIUS packets, was not defined. Event: This message reports an event, not an error notice The process of adding the required routing instance was still in progress when the message was logged.

Description

Type Severity Cause

PPPD_RADIUS_MESSAGE_UNEXPECTED

487

JUNOS 10.1 System Log Messages Reference

Action

None required. Authentication with the indicated RADIUS server is automatically reattempted, and can succeed when the interface exists.

488

PPPD_RADIUS_ROUTE_INST_ENOENT

Chapter 69

PROFILER System Log Messages

This chapter describes messages with the PROFILER prefix. They are generated by the profiler service process (profilerd) which captures accurate and granular detail of the traffic pattern over a specific time period. The profiler process provides details on the threats are encountered by the network as well as details about the mix of application traffic.

PROFILER_RECONFIGURE_SIGHUP
System Log Message Description

SIGHUP - re-reading configuration In response to a SIGHUP signal, the profiler service process (profilerd) read its configuration from the configuration database Event: This message reports an event, not an error info

Type Severity

PROFILER_RECONFIGURE_SIGHUP

489

JUNOS 10.1 System Log Messages Reference

490

PROFILER_RECONFIGURE_SIGHUP

Chapter 70

RDD System Log Messages

This chapter describes messages with the RDD prefix. They are generated by the redundant interfaces process (rdd), which manages redundant interfaces when they are configured on Adaptive Services Physical Interface Cards (PICs).

RDD_EVLIB_CREATE_FAILURE
System Log Message Description

evCreate failed (error-message) The redundant interfaces process (rdd) could not create a context used for handling all asynchronous events (such as timers and message availability). Error: An error occurred emergency

Type Severity

RDD_IFDEV_ADD_FAILURE
System Log Message Description

function-name: unable to add interface device interface-name (error-message) The redundant interfaces process (rdd) could not create an interface device because an error occurred during the indicated call to the routing socket library. Error: An error occurred error Contact your technical support representative.

Type Severity Action

RDD_IFDEV_DELETE_FAILURE
System Log Message

function-name: rtslib delete operation failed for interface device interface-name (error-message) The redundant interfaces process (rdd) could not delete an interface device because an error occurred during the indicated call to the routing socket library. Error: An error occurred

Description

Type

RDD_EVLIB_CREATE_FAILURE

491

JUNOS 10.1 System Log Messages Reference

Severity Action

error Contact your technical support representative.

RDD_IFDEV_GET_FAILURE
System Log Message

function-name: rtslib get operation failed for interface device interface-name (error-message) The redundant interfaces process (rdd) could not get an interface device because an error occurred during the indicated call to the routing socket library. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

RDD_IFDEV_INCOMPATIBLE_REVERT
System Log Message

function-name: did not revert rsp-interface-name back to primary interface primary-interface-name; PIC is incompatible with secondary The redundant interfaces process (rdd) tried to migrate service processing for the indicated redundant interface from the secondary interface back to the indicated primary interface. The attempt failed because the Adaptive Services (AS) Physical Interface Cards (PICs) that house the primary and secondary interfaces are not compatible. Error: An error occurred error

Description

Type Severity

RDD_IFDEV_INCOMPATIBLE_SWITCH
System Log Message

Unable to switch rsp-interface-name to secondary interface secondary-interface-name; PIC is incompatible with primary The redundant interfaces process (rdd) tried to migrate service processing for the indicated redundant interface from the primary interface to the indicated secondary interface. The attempt failed because the Adaptive Services (AS) Physical Interface Cards (PICs) that house the primary and secondary interfaces are not compatible. Error: An error occurred error

Description

Type Severity

492

RDD_IFDEV_DELETE_FAILURE

Chapter 70: RDD System Log Messages

RDD_IFDEV_RETRY_NOTICE
System Log Message

function-name: repeated attempt to add interface device interface-name failed (error-message) The redundant interfaces process (rdd) tried repeatedly to create the indicated interface device, but the attempts failed. After generating this message, rdd waited a while for resources to free up and tried again. Event: This message reports an event, not an error warning Necessary resources might have been unavailable. They should become available soon.

Description

Type Severity Cause

RDD_NEW_INTERFACE_STATE
System Log Message

Event event-name changed state of interface interface-name from 'old-state' to 'new-state' The indicated event on the indicated redundant interface changed the interface state as indicated. Event: This message reports an event, not an error info

Description

Type Severity

RDD_IFDEV_RETRY_NOTICE

493

JUNOS 10.1 System Log Messages Reference

494

RDD_NEW_INTERFACE_STATE

Chapter 71

RMOPD System Log Messages

This chapter describes messages with the RMOPD prefix. They are generated by the Simple Network Management Protocol (SNMP) remote operations process (rmopd), which services SNMP requests for execution of ping and traceroute operations.

RMOPD_ADDRESS_MULTICAST_INVALID
System Log Message Description

Multicast address is not allowed When a Simple Network Management Protocol (SNMP) client requests a remote operation, it can specify the addresses of the source and target hosts for the operation. A request failed because the client specified a multicast address for either or both the source and target hosts. Error: An error occurred error

Type Severity

RMOPD_ADDRESS_SOURCE_INVALID
System Log Message Description

Source address invalid: error-message When a Simple Network Management Protocol (SNMP) client requests a remote operation, it can specify the address to use as the source host for the operation, along with the corresponding address type (such as IP version 4 [IPv4]). Either the specified address was invalid because it did not match the specified address type, or the address could not be resolved. Error: An error occurred notice

Type Severity

RMOPD_ADDRESS_STRING_FAILURE
System Log Message Description

Unable to convert numeric address to string: error-message The remote Simple Network Management Protocol (SNMP) operations process (rmopd) could not convert a numeric host address to the corresponding hostname text string.

RMOPD_ADDRESS_MULTICAST_INVALID

495

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

RMOPD_ADDRESS_TARGET_INVALID
System Log Message Description

rmop_util_set_address status message: error-message When a Simple Network Management Protocol (SNMP) client requests a remote operation, it must specify the address of the target host along with the corresponding address type (such as IP version 4 [IPv4]). Either the specified address was invalid because it did not match the specified address type, or the address could not be resolved. Error: An error occurred error

Type Severity

RMOPD_ICMP_ADDR_TYPE_UNSUPPORTED
System Log Message Description

Only IPv4 source address is supported When a Simple Network Management Protocol (SNMP) client requests a remote operation, it can specify the address type (such as IP version 4 [IPv4]) of the source and target hosts for the operation. The client specified an unsupported address type. Error: An error occurred error

Type Severity

RMOPD_IFINDEX_NOT_ACTIVE
System Log Message Description

ifindex: snmp-interface-index 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 by either its numerical index or its name. The indicated index was invalid because it represents an inactive interface. Error: An error occurred error

Type Severity

RMOPD_IFINDEX_NO_INFO
System Log Message Description

No information for snmp-interface-index, message: error-message 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

496

RMOPD_ADDRESS_STRING_FAILURE

Chapter 71: RMOPD System Log Messages

it by either its numerical index or its name. The SNMP remote operations process (rmopd) could not find any information about the interface with the indicated index.
Type Severity

Error: An error occurred error

RMOPD_IFNAME_NOT_ACTIVE
System Log Message Description

ifname: interface-name 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 by either its numerical index or its name. The indicated name was invalid because it represents an inactive interface. Error: An error occurred error

Type Severity

RMOPD_IFNAME_NO_INFO
System Log Message Description

No information for interface-name, message: error-message 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 by either its numerical index or its name. The SNMP remote operations process (rmopd) could not find any information about the interface with the indicated name. Error: An error occurred error

Type Severity

RMOPD_ROUTING_INSTANCE_NO_INFO
System Log Message Description

No information for routing instance routing-instance: error-message The indicated routing instance does not exist, so the Simple Network Management Protocol (SNMP) remote operations process (rmopd) could not retrieve information about it. Error: An error occurred error

Type Severity

RMOPD_TRACEROUTE_ERROR
System Log Message

Message: error-message

RMOPD_IFINDEX_NO_INFO

497

JUNOS 10.1 System Log Messages Reference

Description

The traceroute application reported the indicated error message to the Simple Network Management Protocol (SNMP) remote operations process (rmopd). Error: An error occurred notice

Type Severity

498

RMOPD_TRACEROUTE_ERROR

Chapter 72

RPD System Log Messages

This chapter describes messages with the RPD prefix. They are generated by the routing protocol process (rpd) which controls the routing protocols that run on the router. This process starts all the configured routing protocols and handles all the routing messages. It maintains one or more routing tables, which consolidate the routing information learned from all routing protocols. From this routing information, the routing protocol process determines the active routes to network destinations and installs these routes into the Routing Engines forwarding table. Finally, it implements routing policy, which allows you to control the routing information that is transferred between the routing protocols and the routing table.

NOTE: When an interface goes down, individual RPD_IGMP_LEAVE and RPD_MLD_LEAVE messages are no longer generated per group or per host. Instead, a single message (such as RPD_IGMP_ALL_SUBSCRIBERS_DELETED) is generated for the interface.

RPD_ABORT
System Log Message Description Type Severity Action

abort executable-name[pid] version version built by builder on date: error-message The routing protocol process (rpd) terminated because of an internal error. Error: An error occurred error Examine the messages that immediately follow this message in the system log for information about possible causes. An internal software failure occurred.

Cause

RPD_ACTIVE_TERMINATE
System Log Message Description

Exiting with active tasks: task-name After receiving multiple termination requests, the routing protocol process (rpd) exited without performing the indicated cleanup tasks.

RPD_ABORT

499

JUNOS 10.1 System Log Messages Reference

Type Severity

Event: This message reports an event, not an error notice

RPD_ASSERT
System Log Message

Assertion failed executable-name[pid]: file "source-filename", line line-number: "message" The source code for the routing protocol process (rpd) includes internal self-consistency checks. A check failed at the indicated line number in the indicated source file, causing the instance of rpd that was using the indicated binary and had the indicated process ID (PID) to terminate. The process created a diagnostic core dump for analysis by technical support personnel. Error: An error occurred error An internal software failure occurred. Examine the messages that immediately follow this message in the system log for information about possible causes. Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core dump, if requested.

Description

Type Severity Cause Action

RPD_ASSERT_SOFT
System Log Message

Soft assertion failed executable-name[pid]: file "source-filename", line line-number: "message", daemon continued running The source code for the routing protocol process (rpd) includes internal self-consistency checks. A check failed at the indicated line number in the indicated source file, but the instance of rpd that was using the indicated binary and had the indicated process ID (PID) continued running. The process created a diagnostic core dump for analysis by technical support personnel. Error: An error occurred error An internal software failure occurred. Examine the messages that immediately follow this message in the system log for information about possible causes. Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core dump, if requested.

Description

Type Severity Cause Action

500

RPD_ACTIVE_TERMINATE

Chapter 72: RPD System Log Messages

RPD_BFD_READ_ERROR
System Log Message Description

Read error on pipe from bfdd: reason (error-message) The routing protocol process (rpd) could not read a message available on the read pipe from the Bidirectional Forwarding Detection process (bfdd). Error: An error occurred info Contact your technical support representative.

Type Severity Action

RPD_BFD_WRITE_ERROR
System Log Message Description

function-name: write error on pipe to bfdd (error-message) The routing protocol process (rpd) could not write a message on the pipe to the Bidirectional Forwarding Detection process (bfdd). Error: An error occurred error Contact your technical support representative.

Type Severity Action

RPD_BGP_NEIGHBOR_STATE_CHANGED
System Log Message Description

BGP peer peer-name changed state from old-state to new-state (event event-type) During BGP negotiation with the local router, the state of the indicated BGP neighbor (peer) changed as indicated. The ESTABLISHED state is the final state in the neighbor negotiation. Event: This message reports an event, not an error warning

Type Severity

RPD_DYN_CFG_BUSY_SIGNAL_FAILED
System Log Message Description

Dynamic config action busy signal failed: error-message The routing protocol process (rpd) failed to notify the dynamic configuration clients about its availability to process the dynamic configuration requests. Error: An error occurred

Type

RPD_BFD_READ_ERROR

501

JUNOS 10.1 System Log Messages Reference

Severity Action

error Contact your technical support representative.

RPD_DYN_CFG_GET_PROFILE_FAILED
System Log Message Description Type Severity

Get dynamic profiles failed: error-code The routing protocol process (rpd) tried to load a profile from the database and failed. Error: An error occurred error

RPD_DYN_CFG_GET_PROF_NAME_FAILED
System Log Message Description

Get profile name for session client-session-id failed: error-code The routing protocol process (rpd) tried to get the profile name from the session snapshot and failed. Error: An error occurred error Contact your technical support representative.

Type Severity Action

RPD_DYN_CFG_GET_SES_STATE_FAILED
System Log Message Description

Get session state for session client-session-id failed: error-code The routing protocol process (rpd) failed to get the session state from the session snapshot. Error: An error occurred error Contact your technical support representative.

Type Severity Action

RPD_DYN_CFG_GET_SES_TYPE_FAILED
System Log Message Description

Get session type for session client-session-id failed: error-code The routing protocol process (rpd) tried to get the session type from the session snapshot and failed.

502

RPD_DYN_CFG_BUSY_SIGNAL_FAILED

Chapter 72: RPD System Log Messages

Type Severity Action

Error: An error occurred error Contact your technical support representative.

RPD_DYN_CFG_GET_SNAPSHOT_FAILED
System Log Message Description

Get session id client-session-id snapshot failed: error-code The routing protocol process (rpd) tried to load client session data from the database and failed. Error: An error occurred error

Type Severity

RPD_DYN_CFG_PDB_CLOSE_FAILED
System Log Message Description Type Severity

Failed to close profile database: error-code The routing protocol process (rpd) tried to close the profile database and failed. Error: An error occurred error

RPD_DYN_CFG_PDB_OPEN_FAILED
System Log Message Description Type Severity

Failed to open profile database: error-code The routing protocol process (rpd) tried to open the profile database and failed. Error: An error occurred error

RPD_DYN_CFG_PROCESSING_FAILED
System Log Message Description Type Severity

Module module failed to process dynamic configuration The routing protocol process (rpd) tried to process dynamic configuration and failed. Error: An error occurred error

RPD_DYN_CFG_GET_SES_TYPE_FAILED

503

JUNOS 10.1 System Log Messages Reference

RPD_DYN_CFG_REGISTER_FAILED
System Log Message Description

Dynamic config registration failed: error-message The routing protocol process (rpd) tried to register with the dynamic configuration subsystem and failed. Error: An error occurred error

Type Severity

RPD_DYN_CFG_REQUEST_ACK_FAILED
System Log Message Description

Failed to ack request data-id: error-code The routing protocol process (rpd) tried to acknowledge a dynamic configuration request and failed. Error: An error occurred error

Type Severity

RPD_DYN_CFG_RESPONSE_SLOW
System Log Message Description Type Severity Action

Dynamic config response for session id client-session-id took system-seconds seconds The routing protocol process (rpd) is responding slowly to dynamic config requests. Error: An error occurred error Contact your technical support representative.

RPD_DYN_CFG_SCHEMA_OPEN_FAILED
System Log Message Description Type Severity

Could not open configuration schema: error-message The routing protocol process (rpd) tried to open the configuration schema and failed. Error: An error occurred error

504

RPD_DYN_CFG_REGISTER_FAILED

Chapter 72: RPD System Log Messages

RPD_DYN_CFG_SDB_CLOSE_FAILED
System Log Message Description Type Severity

Failed to close session database: error-code The routing protocol process (rpd) tried to close the session database and failed. Error: An error occurred error

RPD_DYN_CFG_SDB_OPEN_FAILED
System Log Message Description Type Severity

Failed to open session database: error-code The routing protocol process (rpd) tried to open the session database and failed. Error: An error occurred info

RPD_DYN_CFG_SES_RECOVERY_FAILED
System Log Message Description Type Severity Action

Recovery of session client-session-id failed The routing protcol process (rpd) tried to recover a session and failed. Error: An error occurred error Contact your technical support representative.

RPD_DYN_CFG_SET_CONTEXT_FAILED
System Log Message Description

Set dynamic config context for profile profile-name session client-session-id failed The routing protocol process (rpd) tried to set up the dynamic configuration context and failed. Error: An error occurred error

Type Severity

RPD_DYN_CFG_SDB_CLOSE_FAILED

505

JUNOS 10.1 System Log Messages Reference

RPD_ESIS_ADJDOWN
System Log Message

ES-IS lost adjacency-type adjacency to neighbor-nsap-netn on interface-name, reason: reason An ES-IS adjacency with the indicated neighboring router was terminated. The local router no longer exchanges routing information with, or directs traffic to, the neighboring router. Event: This message reports an event, not an error notice The communication path to the neighboring router was disrupted, a protocol error occurred, or the neighboring router was powered down.

Description

Type Severity Cause

RPD_ESIS_ADJUP
System Log Message Description

ES-IS new adjacency-type adjacency to neighbor-nsap-netn on interface-name An ES-IS adjacency was established with the indicated neighboring router. The local router can now exchange information with it. Event: This message reports an event, not an error info

Type Severity

RPD_EXIT
System Log Message Description

Exit executable-name[pid] version version built by builder on date, caller address The routing protocol process (rpd) exited, either in response to a user request or because of a system error. Event: This message reports an event, not an error notice A system resource was unavailable, rpd did not understand an error, or a user terminated the process. Examine the messages that immediately follow this message in the system log for information about possible causes.

Type Severity Cause

Action

506

RPD_ESIS_ADJDOWN

Chapter 72: RPD System Log Messages

RPD_IFD_INDEXCOLLISION
System Log Message

Physical interface collision -- same name, different index (new new-interface-name new-index old old-interface-name old-value) The routing protocol process (rpd) received a message from the kernel in which the numerical index associated with the indicated interface name differed from the index-to-name mapping maintained by rpd. Error: An error occurred error It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.

Description

Type Severity Cause

RPD_IFD_NAMECOLLISION
System Log Message

Physical interface collision -- different name, same index (new new-interface-name new-index, old old-interface-name old-value) The routing protocol process (rpd) received a message from the kernel in which the name associated with the indicated numerical interface index differed from the name-to-index mapping maintained by rpd. Error: An error occurred error It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.

Description

Type Severity Cause

RPD_IFL_INDEXCOLLISION
System Log Message

Logical interface collision -- same name, different index (new new-interface-name new-index old old-interface-name old-value) The routing protocol process (rpd) received a message from the kernel in which the numerical index associated with the indicated interface name differed from the index-to-name mapping maintained by rpd. Error: An error occurred error

Description

Type Severity

RPD_IFD_INDEXCOLLISION

507

JUNOS 10.1 System Log Messages Reference

Cause

It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.

RPD_IFL_NAMECOLLISION
System Log Message

Logical interface collision -- different name, same index (new new-interface-name new-index, old old-interface-name old-value) The routing protocol process (rpd) received a message from the kernel in which the name associated with the indicated numerical interface index differed from the name-to-index mapping maintained by rpd. Error: An error occurred error It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.

Description

Type Severity Cause

RPD_IGMP_ACCOUNTING_OFF
System Log Message Description

interface-name time Internet Group Management Protocol (IGMP) accounting for the indicated interface was disabled at the indicated time. Event: This message reports an event, not an error info

Type Severity

RPD_IGMP_ACCOUNTING_ON
System Log Message Description

interface-name time Internet Group Management Protocol (IGMP) accounting for the indicated interface was enabled at the indicated time. Event: This message reports an event, not an error info

Type Severity

RPD_IGMP_ALL_SUBSCRIBERS_DELETED
System Log Message

All IGMP subscribers on interface interface-name deleted at time because the interface is down

508

RPD_IFL_INDEXCOLLISION

Chapter 72: RPD System Log Messages

Description Type Severity

All IGMP subscribers have been deleted because the interface is down. Event: This message reports an event, not an error info

RPD_IGMP_CFG_CREATE_ENTRY_FAILED
System Log Message Description

Could not create entry for entry. Internet Group Management Protocol (IGMP) failed to create the indicated configuration entry. The configuration request failed. Error: An error occurred error Contact your technical support representative.

Type Severity Action

RPD_IGMP_CFG_GROUP_OUT_OF_RANGE
System Log Message

The combination of group-count count and group-increment ip-address causes some of the groups out of range. The configuration request failed because the indicated configuration object contained a group that is out of range. Error: An error occurred error Modify configuration statement to use a valid value.

Description

Type Severity Action

RPD_IGMP_CFG_INVALID_VALUE
System Log Message Description

The object-name configuration object identifier field has an invalid value of value The configuration request failed because the indicated configuration object contained the indicated invalid value. Error: An error occurred error Modify configuration statement to use a valid value.

Type Severity Action

RPD_IGMP_ALL_SUBSCRIBERS_DELETED

509

JUNOS 10.1 System Log Messages Reference

RPD_IGMP_CFG_SOURCE_OUT_OF_RANGE
System Log Message

The combination of source-count count and source-increment ip-address causes some of the sources out of range. The configuration request failed because the indicated configuration object contained a source that is out of range. Error: An error occurred error Modify configuration statement to use a valid value.

Description

Type Severity Action

RPD_IGMP_DYN_CFG_ALREADY_BOUND
System Log Message

Dynamic configuration session id client-session-id for interface interface-name is already bound to interface old-interface-name. The indicated dynamic configuration session id is already bound to another interface. The dynamic configuration instantiation request was rejected. Error: An error occurred error Unbind session id from existing interface.

Description

Type Severity Action

RPD_IGMP_DYN_CFG_INVALID_STMT
System Log Message Description

Invalid dynamic configuration statement: configuration-statement The indicated dynamic configuration statement was invalid. The dynamic configuration instantiation request was rejected. Error: An error occurred error Remove the unsupported configuration statement.

Type Severity Action

RPD_IGMP_DYN_CFG_SES_ID_ADD_FAIL
System Log Message

Failed to add dynamic configuration session id client-session-id to interface interface-name.

510

RPD_IGMP_CFG_SOURCE_OUT_OF_RANGE

Chapter 72: RPD System Log Messages

Description

Failed to associate the indicated dynamic configuration session id to specified interface. The dynamic configuration instantiation request was rejected. Error: An error occurred error Contact your technical support representative.

Type Severity Action

RPD_IGMP_DYN_CFG_SES_ID_MISMATCH
System Log Message

Dynamic configuration entry for interface interface-name with session id client-session-id found an existing entry with a different session id of client-session-id-1. The dynamic configuration instantiation request matched an existing dynamic configuration block that had a different session id. The dynamic configuration instantiation request was rejected. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

RPD_IGMP_JOIN
System Log Message

Listener source-address sent a join to destination-address for group group-address source sender-address on interface interface-name at time IGMP join event. Event: This message reports an event, not an error info

Description Type Severity

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 IGMP leave event. Event: This message reports an event, not an error info

Description Type Severity

RPD_IGMP_DYN_CFG_SES_ID_ADD_FAIL

511

JUNOS 10.1 System Log Messages Reference

RPD_IGMP_MEMBERSHIP_TIMEOUT
System Log Message

Membership timeout for listener source-address for group group-address source sender-address on interface interface-name at time IGMP group membership timeout. Event: This message reports an event, not an error info

Description Type Severity

RPD_IGMP_ROUTER_VERSION_MISMATCH
System Log Message

IGMP version mismatch on interface-name. Local version: local-version Remote version: remote-version The IGMP version running on the local router does not match the one received in the query Event: This message reports an event, not an error warning

Description

Type Severity

RPD_ISIS_ADJDOWN
System Log Message Description

IS-IS lost Lisis-level adjacency to neighbor-system-ids on interface-name, reason: reason An IS-IS adjacency with the indicated neighboring router was terminated. The local router no longer exchanges routing information with, or directs traffic to, the neighboring router. Event: This message reports an event, not an error notice The communication path to the neighboring router was disrupted, a protocol error occurred, or the neighboring router was powered down.

Type Severity Cause

RPD_ISIS_ADJUP
System Log Message Description

IS-IS new Lisis-level adjacency to neighbor-system-ids on interface-name An IS-IS adjacency was established with the indicated neighboring router. The local router can now exchange information with it. Event: This message reports an event, not an error

Type

512

RPD_IGMP_MEMBERSHIP_TIMEOUT

Chapter 72: RPD System Log Messages

Severity

info

RPD_ISIS_ADJUPNOIP
System Log Message

IS-IS new Lisis-level adjacency to neighbor-system-ids on interface-name without an address An IS-IS adjacency was established with the indicated neighboring router, which is not configured for IS-IS for IP. Event: This message reports an event, not an error notice The neighboring router is misconfigured: it is enabled for IS-IS but not for exchange of IP route information. Configure the neighboring router for IS-IS with IP, or remove it from the IS-IS mesh.

Description

Type Severity Cause

Action

RPD_ISIS_LDP_SYNC
System Log Message

IS-IS interface interface-name advertised with infinite metric for duration seconds already due to loss of synchronization with LDP The IS-IS protocol lost synchronization with the Label Distribution Protocol (LDP) on the indicated interface. As a consequence, it began advertising an infinite metric for the interface and has been doing so for the indicated number of seconds. Error: An error occurred warning Determine why LDP lost synchronization with IS-IS.

Description

Type Severity Action

RPD_ISIS_LSPCKSUM
System Log Message

IS-IS Lisis-level LSP checksum error, interface interface-name, LSP id lspl, sequence sequence-number, checksum checksum, lifetime duration The indicated IS-IS informational link-state PDU (LSP) failed an internal checksum validity test, implying that it was corrupted. Error: An error occurred warning The packet was corrupted in transit between the neighboring IS-IS router and this router, or memory on one of the routers was corrupted.

Description

Type Severity Cause

RPD_ISIS_ADJUP

513

JUNOS 10.1 System Log Messages Reference

Action

None, unless a large number of these messages appear in the system log file. The corrupted LSP is silently discarded.

RPD_ISIS_NO_ROUTERID
System Log Message Description Type Severity Cause

IS-IS instance does not have a valid router ID The IS-IS instance did not have a valid router ID. Error: An error occurred alert When a router ID is not explicitly configured for an instance, IPv4 addresses configured under the instance are considered in the selection of the router ID. In this case, the instance did not have a router ID configured and no IPv4 addresses were configured. Either configure a router ID by including the 'routing-instance' statement under the instance, or configure an IPv4 address by including the 'family inet' statement under one of the interfaces of the instance. You can also configure both.

Action

RPD_ISIS_OVERLOAD
System Log Message Description

IS-IS database overload The IS-IS link-state database is full and no additional memory can be allocated for it. Error: An error occurred alert No additional memory is available for storing IS-IS link-state information. Either system resources are exhausted or a software error occurred (such as a memory leak in the routing protocol process [rpd]). In the former case, IS-IS might be carrying too much information, or the router configuration includes too many features that use large amounts of system memory. Perform one or more of the following actions: (1) Check for unusually high memory usage by the IS-IS task or rpd, (2) Unconfigure features that use large amounts of memory, (3) Add more memory to the Routing Engine, (4) Carry fewer IS-IS routes.

Type Severity Cause

Action

RPD_KRT_CCC_IFL_MODIFY
System Log Message

error-code, error-message

514

RPD_ISIS_LSPCKSUM

Chapter 72: RPD System Log Messages

Description

The routing protocol process (rpd) attempted to modify the state for a logical interface that is related to circuit cross-connect (CCC), but the request failed. Event: This message reports an event, not an error info It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.

Type Severity Cause

RPD_KRT_DELETED_RTT
System Log Message

task-name: received deleted routing table from the kernel for family address-family-type table ID table-id The routing protocol process (rpd) received a message from the kernel that referred to a routing table that no longer exists. Error: An error occurred error

Description

Type Severity

RPD_KRT_IFA_GENERATION
System Log Message Description

ifa generation mismatch -- rpd rpd-generation kernel kernel-generation The routing protocol process (rpd) received a message from the kernel in which the interface address associated with the indicated numerical index differed from the address-to-index mapping maintained by rpd. Event: This message reports an event, not an error notice It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.

Type Severity Cause

RPD_KRT_IFDCHANGE
System Log Message

task-name CHANGE for ifd interface-device-index address/prefix-length failed, error "error-message" The routing protocol process (rpd) sent a request to the kernel to change the state of the indicated interface. The request failed. Error: An error occurred

Description

Type

RPD_KRT_CCC_IFL_MODIFY

515

JUNOS 10.1 System Log Messages Reference

Severity Cause

error It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.

RPD_KRT_IFDEST_GET
System Log Message Description

task-name IFDEST GET for ifd rpd-interface-name failed, error "error-message" The routing protocol process (rpd) requested state information about the indicated interface from the kernel. The request failed. Error: An error occurred error It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.

Type Severity Cause

RPD_KRT_IFDGET
System Log Message Description

task-name GET index for ifd interface-name failed, error "error-message" The routing protocol process (rpd) requested state information about the indicated interface from the kernel. The request failed. Error: An error occurred error It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.

Type Severity Cause

RPD_KRT_IFD_CELL_RELAY_INV_MODE
System Log Message

Invalid mode (mode) specified for interface device interface-name; defaulting to port mode The routing protocol process (rpd) received a message from the kernel that specified the cell-relay encapsulation for the indicated physical interface, but the specified cell-relay mode (port, or trunk user-to-network interface [UNI], or trunk network-to-network interface [NNI]) was invalid. Error: An error occurred notice

Description

Type Severity

516

RPD_KRT_IFDCHANGE

Chapter 72: RPD System Log Messages

RPD_KRT_IFD_CELL_RELAY_NO_MODE
System Log Message Description

No mode specified for interface device interface-name; defaulting to port mode The routing protocol process (rpd) received a message from the kernel that specified the cell-relay encapsulation for the indicated physical interface, but not the cell-relay mode. Error: An error occurred notice

Type Severity

RPD_KRT_IFD_GENERATION
System Log Message

ifd interface-device-index generation mismatch -- rpd rpd-generation kernel kernel-generation The routing protocol process (rpd) received a message from the kernel in which the physical interface associated with the indicated numerical index differed from the interface-to-index mapping maintained by rpd. Event: This message reports an event, not an error notice It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.

Description

Type Severity Cause

RPD_KRT_IFL_CELL_RELAY_INV_MODE
System Log Message

Invalid mode (mode) specified for logical interface interface-name; defaulting to port mode The routing protocol process (rpd) received a message from the kernel that specified the cell-relay encapsulation for the indicated logical interface, but the specified cell-relay mode (port, virtual-circuit, or virtual-path) was invalid. Error: An error occurred notice

Description

Type Severity

RPD_KRT_IFL_CELL_RELAY_NO_MODE
System Log Message

No mode specified for logical interface interface-name; defaulting to port mode

RPD_KRT_IFD_CELL_RELAY_NO_MODE

517

JUNOS 10.1 System Log Messages Reference

Description

The routing protocol process (rpd) received a message from the kernel that specified the cell-relay encapsulation for the indicated logical interface but not the cell-relay mode. Error: An error occurred notice

Type Severity

RPD_KRT_IFL_GENERATION
System Log Message

ifl logical-interface-index generation mismatch -- rpd rpd-interface-name rpd-generation kernel kernel-interface-name.kernel-interface-unit kernel-generation The routing protocol process (rpd) received a message from the kernel in which the logical interface associated with the indicated numerical index differed from the interface-to-index mapping maintained by rpd. Event: This message reports an event, not an error notice It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.

Description

Type Severity Cause

RPD_KRT_KERNEL_BAD_ROUTE
System Log Message Description

task-name: lost interface-hierarchy logical-interface-index for route route-prefix As it restarted, the routing protocol process (rpd) could not process a route obtained from the kernel because the route contained references to objects that are no longer valid. Event: This message reports an event, not an error warning rpd did not recognize some elements in the route message, such as the logical interface index or an address family. rpd can probably solve the problem, but check the entry for the indicated route prefix in the forwarding table. If the prefix's route and forwarding table entry are inconsistent, contact a technical support representative for instructions.

Type Severity Cause

Action

RPD_KRT_NEXTHOP_OVERFLOW
System Log Message

type route-prefix: number of next hops (count) exceeded the maximum allowed (maximum-value) -- truncating

518

RPD_KRT_IFL_CELL_RELAY_NO_MODE

Chapter 72: RPD System Log Messages

Description

The number of next hops for the indicated route exceeded the indicated limit for a single route add operation. Error: An error occurred error An indexed next hop can use multiple forwarding next hops per forwarding class. It is possible to have more next hops per route than can be carried in a single message. This requires that next hops be reused across forwarding classes, which is not recommended. Eliminate common next hops across forwarding classes, thereby reducing the total number of next hops that must be specified.

Type Severity Cause

Action

RPD_KRT_NOIFD
System Log Message Description

No device interface-device-index for interface logical-interface-index (interface-name) The routing protocol process (rpd) received a message from the kernel that associated the indicated physical interface device and logical interface. The rpd process has no record of the device. Error: An error occurred error It is possible that rpd discarded some interface messages from the kernel without processing them because it received more messages than it could handle. It will recover.

Type Severity Cause

RPD_KRT_VERSION
System Log Message

Routing socket version mismatch (kernel kernel-version != rpd rpd-version) -- kernel upgrade required The routing protocol process (rpd) discovered that the kernel does not support the version of routing sockets it requires. Error: An error occurred error The kernel version is older than the rpd version. Upgrade the kernel package.

Description

Type Severity Cause Action

RPD_KRT_NEXTHOP_OVERFLOW

519

JUNOS 10.1 System Log Messages Reference

RPD_KRT_VERSIONNONE
System Log Message

Routing socket message type message-type's version is not supported by kernel, expected rpd-version -- kernel upgrade required The routing protocol process (rpd) discovered that the kernel does not support the routing socket message types that it requires. Error: An error occurred error The kernel version is older than the rpd version. Upgrade the kernel package.

Description

Type Severity Cause Action

RPD_KRT_VERSIONOLD
System Log Message

Routing socket message type message-type's version is older than expected (kernel-version <rpd-version) -- consider upgrading the kernel The routing protocol process (rpd) discovered that the kernel uses an older version of routing socket message types than it does. Error: An error occurred error The kernel version is older than the rpd version. Upgrade the kernel package.

Description

Type Severity Cause Action

RPD_KRT_VPLS_IFL_MODIFY
System Log Message Description

Unable to modify VPLS-related state: error-code (errno error-message) The routing protocol process (rpd) attempted to modify the state for a logical interface that is related to virtual private LAN service (VPLS), but the request failed. Event: This message reports an event, not an error info It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.

Type Severity Cause

520

RPD_KRT_VERSIONNONE

Chapter 72: RPD System Log Messages

RPD_L2VPN_LABEL_ALLOC_FAILED
System Log Message Description

Unable to allocate label-type labels for site name with ID identifier in instance vpn-name The routing protocol process (rpd) could not allocate labels of the indicated type for the indicated site (name and ID) in the indicated virtual private network (VPN) virtual circuit (VC), because the resulting number of labels would have exceeded the limit. Error: An error occurred error

Type Severity

RPD_L2VPN_REMOTE_SITE_COLLISION
System Log Message

Two remote PEs (RDs route-discriminator and route-discriminator2) have the same site ID (identifier) in VPN vpn-name The routing protocol process (rpd) for the indicated virtual private network (VPN) received an advertisement from a remote provider edge (PE) router with the first indicated route discriminator, but the associated site ID also belongs to a remote site with the second route discriminator. Event: This message reports an event, not an error warning

Description

Type Severity

RPD_L2VPN_SITE_COLLISION
System Log Message

Same site ID identifier configured on remote PE (RD route-discriminator) and local PE in VPN vpn-name (non-multihomed site name) The routing protocol process (rpd) for the indicated virtual private network (VPN) received an advertisement from a remote provider edge (PE) router, but the associated site ID belongs to a local site. Event: This message reports an event, not an error error

Description

Type Severity

RPD_LAYER2_VC_BFD_DOWN
System Log Message Description

BFD session for Layer 2 VC vc-name went down The routing protocol process (rpd) determined that the Bidirectional Forwarding Detection (BFD) protocol session for the indicated Layer 2 virtual private network (VPN) virtual circuit (VC) terminated.

RPD_L2VPN_LABEL_ALLOC_FAILED

521

JUNOS 10.1 System Log Messages Reference

Type Severity

Event: This message reports an event, not an error notice

RPD_LAYER2_VC_BFD_UP
System Log Message Description

BFD session for Layer 2 VC vc-name came up 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. Event: This message reports an event, not an error notice

Type Severity

RPD_LAYER2_VC_DOWN
System Log Message Description

State of Layer 2 VC vc-name changed from UP to state The state of the indicated Layer 2 virtual private network (VPN) virtual circuit (VC) changed as indicated (to either down or deleted). Event: This message reports an event, not an error notice

Type Severity

RPD_LAYER2_VC_PING_DOWN
System Log Message Description

Ping failure for Layer 2 VC vc-name The routing protocol process (rpd) determined that the Ping for the indicated Layer 2 virtual private network (VPN) virtual circuit (VC) failed. Event: This message reports an event, not an error notice

Type Severity

RPD_LAYER2_VC_UP
System Log Message Description

State of Layer 2 VC vc-name changed to UP The state of the indicated Layer 2 virtual private network (VPN) virtual circuit (VC) changed to up. Event: This message reports an event, not an error info

Type Severity

522

RPD_LAYER2_VC_BFD_DOWN

Chapter 72: RPD System Log Messages

RPD_LDP_BFD_DOWN
System Log Message Description

LDP BFD session for FEC fec-address went down The routing protocol process (rpd) determined that the Label Distribution Protocol (LDP) Bidirectional Forwarding Detection (BFD) protocol session for the indicated forwarding equivalence class (FEC) terminated. Event: This message reports an event, not an error notice

Type Severity

RPD_LDP_BFD_DOWN_TRACEROUTE_FAIL
System Log Message Description

LDP BFD sessions for FEC fec-address going down due to traceroute failure The routing protocol process (rpd) determined that the Label Distribution Protocol (LDP) Bidirectional Forwarding Detection (BFD) protocol session for the indicated forwarding equivalence class (FEC) was terminated due to traceroute failure. Event: This message reports an event, not an error notice

Type Severity

RPD_LDP_BFD_UP
System Log Message Description

LDP BFD session for FEC fec-address came up The routing protocol process (rpd) determined that the Label Distribution Protocol (LDP) Bidirectional Forwarding Detection (BFD) protocol session for the indicated forwarding equivalence class (FEC) came up. Event: This message reports an event, not an error notice

Type Severity

RPD_LDP_INTF_BLOCKED
System Log Message

Duplicate session ID detected from neighbor-addressi, interface interface-name, blocking interface Label Distribution Protocol (LDP) operations were blocked on the indicated interface because the same session ID was detected across multiple interfaces but per-interface transport addresses are in use. Event: This message reports an event, not an error

Description

Type

RPD_LDP_BFD_DOWN

523

JUNOS 10.1 System Log Messages Reference

Severity

warning

RPD_LDP_INTF_UNBLOCKED
System Log Message Description

LDP interface interface-name is now unblocked The indicated interface returned to the normal Label Distribution Protocol (LDP) operational state. It was previously blocked because the routing protocol process (rpd) noticed that a duplicate session ID was being used. Event: This message reports an event, not an error warning

Type Severity

RPD_LDP_NBRDOWN
System Log Message Description

LDP neighbor neighbor-addressi (interface-name) is down A Label Distribution Protocol (LDP) adjacency was terminated because the indicated neighbor stopped communicating. If the adjacency was the only one with this neighbor, the routing protocol process (rpd) terminated the associated LDP session. Event: This message reports an event, not an error notice

Type Severity

RPD_LDP_NBRUP
System Log Message Description

LDP neighbor neighbor-addressi (interface-name) is up A Label Distribution Protocol (LDP) adjacency with the indicated neighbor became active. The routing protocol process (rpd) established an LDP session with the neighbor if one did not already exist. Event: This message reports an event, not an error info

Type Severity

RPD_LDP_PING_DOWN
System Log Message Description

LDP LSP ping failure for FEC fec-address The routing protocol process (rpd) determined that LSP ping returned error for the indicated forwarding equivalence class (FEC) of Label Distribution Protocol (LDP). Event: This message reports an event, not an error notice

Type Severity

524

RPD_LDP_INTF_BLOCKED

Chapter 72: RPD System Log Messages

RPD_LDP_SESSIONDOWN
System Log Message Description

LDP session neighbor-addressi is down, reason: reason The routing protocol process (rpd) terminated a Label Distribution Protocol (LDP) session with the indicated neighbor and deleted all labels exchanged during the session. Event: This message reports an event, not an error notice

Type Severity

RPD_LDP_SESSIONUP
System Log Message Description

LDP session neighbor-addressi is up The routing protocol process (rpd) established a Label Distribution Protocol (LDP) session with the indicated neighbor. The routers began exchanging labels. Event: This message reports an event, not an error info

Type Severity

RPD_LMP_ALLOC_ACK
System Log Message Description

Unknown context in ALLOC_ACK message The routing protocol process (rpd) received a label allocation acknowledgment that contained invalid context. Error: An error occurred error

Type Severity

RPD_LMP_ALLOC_REQUEST_TIMEOUT
System Log Message Description

Allocation request timeout for context 0xaddress, client request ID 0xrequest-id The label allocation request with the indicated client request ID and for the indicated context timed out before completion. Event: This message reports an event, not an error error

Type Severity

RPD_LDP_SESSIONDOWN

525

JUNOS 10.1 System Log Messages Reference

RPD_LMP_CONTROL_CHANNEL
System Log Message Description

operation operation failed: control channel logical-interface-index unknown The routing protocol process (rpd) received a message that specified the indicated type of operation on the indicated control channel. The channel does not exist. Error: An error occurred error

Type Severity

RPD_LMP_NO_CALLBACK
System Log Message Description

No function callback for label removed event The routing protocol process (rpd) could not notify a client that a label was removed, because there was no function callback for the removal event. Error: An error occurred error

Type Severity

RPD_LMP_NO_MEMORY
System Log Message Description Type Severity Cause

function-name: malloc() failed (error-message, errno error-code) The routing protocol process (rpd) could not allocate memory. Error: An error occurred error An internal software failure occurred.

RPD_LMP_NO_PEER
System Log Message Description

Peer peer-id not found for TE link link-name (index link-id) The routing protocol process (rpd) could not locate the indicated peer while processing a TE LINK message for the traffic-engineering link with the indicated name and index. Error: An error occurred error

Type Severity

526

RPD_LMP_CONTROL_CHANNEL

Chapter 72: RPD System Log Messages

RPD_LMP_PEER
System Log Message Description

operation operation failed: peer peer-name (index peer-id) reason The routing protocol process (rpd) could not perform the indicated operation for the peer with the indicated name and index, for the indicated reason. Error: An error occurred error

Type Severity

RPD_LMP_PEER_IFL
System Log Message

operation operation failed because reason for peer peer-name (index peer-id): error-message (errno error-code) The routing protocol process (rpd) could not perform the indicated operation for the peer with the indicated name and index, for the indicated reason. Error: An error occurred error

Description

Type Severity

RPD_LMP_PEER_INDEX
System Log Message Description Type Severity

No more peer indexes No more peer indexes were available for allocation. Event: This message reports an event, not an error error

RPD_LMP_RESOURCE
System Log Message Description

operation operation failed: resource resource (type type, index index) reason The routing protocol process (rpd) could not perform the indicated operation for the resource with the indicated name, type, and index, for the indicated reason. Error: An error occurred error

Type Severity

RPD_LMP_PEER

527

JUNOS 10.1 System Log Messages Reference

RPD_LMP_RESOURCE_NO_LINK
System Log Message Description

TE link link-id not found for resource resource (type type, index index) The routing protocol process (rpd) could not locate the indicated traffic-engineering link for the resource with the indicated name, type, and index. Error: An error occurred error

Type Severity

RPD_LMP_SEND
System Log Message Description

function-name: handling write exception (error-message, errno error-code) The routing protocol process (rpd) could not send a message to the Label Management Protocol (LMP) process (lmpd). Error: An error occurred error

Type Severity

RPD_LMP_SEND_ALLOCATION_MESSAGE
System Log Message Description Type Severity

Unable to send allocation message: error-message (error-code) The routing protocol process (rpd) could not send an allocation message. Error: An error occurred error

RPD_LMP_SYSFAIL
System Log Message Description

Unable to start type timer The routing protocol process (rpd) discovered that the Label Management Protocol (LMP) process (lmpd) was not running. The rpd process attempted to start the indicated type of timer for restarting the lmpd process or reestablishing a connection to it, but the attempt failed. Error: An error occurred error An internal software failure occurred.

Type Severity Cause

528

RPD_LMP_RESOURCE_NO_LINK

Chapter 72: RPD System Log Messages

Action

Examine the messages that immediately follow this message in the system log for information about possible reasons that lmpd failed.

RPD_LMP_TE_LINK
System Log Message Description

operation operation failed: TE link link-name (index index) reason The routing protocol process (rpd) could not perform the indicated operation for the traffic-engineering link with the indicated name and index, for the indicated reason. Error: An error occurred error

Type Severity

RPD_LMP_TE_LINK_INDEX
System Log Message Description Type Severity

No more TE-link indexes No more traffic-engineering link indexes were available for allocation. Event: This message reports an event, not an error error

RPD_LMP_UNEXPECTED_OPCODE
System Log Message Description

message-type message had unexpected operation code operation-code The routing protocol process (rpd) received the indicated type of message, which had the indicated invalid operation code. Error: An error occurred error

Type Severity

RPD_LOCK_FLOCKED
System Log Message Description

Unable to obtain a lock on filename, is another copy of rpd running? The routing protocol process (rpd) could not obtain the mutual exclusion lock that prevents more than one instance of rpd from running simultaneously. The system terminated the indicated process. Error: An error occurred error Another rpd process is running.

Type Severity Cause

RPD_LMP_SYSFAIL

529

JUNOS 10.1 System Log Messages Reference

Action

Use the 'show system process' command to verify that another rpd is running.

RPD_LOCK_LOCKED
System Log Message Description

Unable to obtain a lock on filename, program-name[pid] is still running The routing protocol process (rpd) could not obtain the mutual exclusion lock that prevents more than one instance of rpd from running simultaneously. The system terminated this instance of rpd. Error: An error occurred error Another rpd is running. Use the 'show system process' command to verify that another rpd is running.

Type Severity Cause Action

RPD_MC_CFG_CREATE_ENTRY_FAILED
System Log Message Description

Could not create entry for entry. The multicast configuration request failed because the routing protocol process (rpd) failed to create the specified configuration entry. Error: An error occurred error Contact your technical support representative.

Type Severity Action

RPD_MC_COSD_WRITE_ERROR
System Log Message Description

Unable to write to pipe to COS process: (error-message) The routing protocol process (rpd) could not write a message on the write pipe to the Class Of Service process (cosd). Error: An error occurred info Contact your technical support representative.

Type Severity Action

530

RPD_LOCK_FLOCKED

Chapter 72: RPD System Log Messages

RPD_MC_DESIGNATED_PE_CHANGE
System Log Message

Designated forwarder changed to ip-address for backup-pe-group group-name in routing-instance instance The routing protocol daemon (rpd) assigned the indicated Provider Edge (PE) as the new designated forwarder of the indicated routing instance for the indicated backup-pe-group. Event: This message reports an event, not an error notice

Description

Type Severity

RPD_MC_DYN_CFG_ALREADY_BOUND
System Log Message

Dynamic configuration session id client-session-id for interface interface-name is already bound to interface old-interface-name. The dynamic configuration instantiation request was rejected because the specified dynamic configuration sesssion ID was already bound to another interface. Error: An error occurred error Unbind the session ID from the existing interface.

Description

Type Severity Action

RPD_MC_DYN_CFG_SES_ID_ADD_FAIL
System Log Message

Failed to add dynamic configuration session id client-session-id to interface interface-name. The dynamic configuration instantiation request was rejected because the routing protocol process failed to associate the specified dynamic configuration session ID with the specified interface. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

RPD_MC_DYN_CFG_SES_ID_MISMATCH
System Log Message

Dynamic configuration entry for interface interface-name with session id client-session-id found an existing entry with a different session id of client-session-id-1.

RPD_MC_DESIGNATED_PE_CHANGE

531

JUNOS 10.1 System Log Messages Reference

Description

The dynamic configuration instantiation request was rejected because the request matched an existing dynamic configuration block that had a different session ID. Error: An error occurred error Contact your technical support representative.

Type Severity Action

RPD_MC_LOCAL_DESIGNATED_PE
System Log Message

Local PE is now the designated forwarder for backup-pe-group group-name in routing-instance instance The routing protocol daemon (rpd) selected the local Provider Edge (PE) as the designated forwarder of the indicated routing instance for the indicated backup-pe-group. Event: This message reports an event, not an error notice

Description

Type Severity

RPD_MC_OIF_REJECT
System Log Message Description

Interface interface-name is rejected due to lack of bw When multicast bandwidth admission control is applied, an interface may not be put into the downstream interface list for a forwarding cache if the interface does not have enough bandwidth for the flow, even when a multicast protocol determines that there are local/downstream receivers. Event: This message reports an event, not an error info

Type Severity

RPD_MC_OIF_RE_ADMIT
System Log Message Description

Interface interface-name is re-admitted with newly available bw The indicated downstream interface that was previously rejected was readmitted for the flow because there was newly availabe bandwidth on the interface. Event: This message reports an event, not an error info

Type Severity

532

RPD_MC_DYN_CFG_SES_ID_MISMATCH

Chapter 72: RPD System Log Messages

RPD_MGMT_TIMEOUT
System Log Message Description

Connection to management peer process-name timed out waiting for input The connection between the routing protocol process (rpd) and the indicated management process (mgd) timed out before input arrived from the mgd process. Error: An error occurred warning

Type Severity

RPD_MIRROR_ERROR
System Log Message Description

Unable to establish mirror connection between Routing Engines: error-message The routing protocol process (rpd) could not establish the mirror connection (which supports nonstop routing) between the master and backup Routing Engines. Error: An error occurred warning The master and backup Routing Engines are running incompatible versions of the JUNOS software. Update the JUNOS software to compatible versions on the master and backup Routing Engines.

Type Severity Cause

Action

RPD_MIRROR_VERSION_MISMATCH
System Log Message Description

Versions of mirror software on Routing Engines are incompatible: error-message While trying to establish the mirror connection between the master and backup Routing Engines (which supports nonstop routing), the routing protocol process (rpd) determined that the versions of JUNOS software on the Routing Engines were incompatible. Error: An error occurred warning Update the JUNOS software to compatible versions on the master and backup Routing Engines.

Type Severity Action

RPD_MGMT_TIMEOUT

533

JUNOS 10.1 System Log Messages Reference

RPD_MLD_ACCOUNTING_OFF
System Log Message Description

interface-name time The Multicast Listener Discovery (MLD) accounting for the indicated interface was disabled at the indicated time. Event: This message reports an event, not an error info

Type Severity

RPD_MLD_ACCOUNTING_ON
System Log Message Description

interface-name time The Multicast Listener Discovery (MLD) accounting for the indicated interface was enabled at the indicated time. Event: This message reports an event, not an error info

Type Severity

RPD_MLD_ALL_SUBSCRIBERS_DELETED
System Log Message

All MLD subscribers on interface interface-name deleted at time because the interface is down All MLD subscribers have been deleted because the interface is down. Event: This message reports an event, not an error info

Description Type Severity

RPD_MLD_CFG_CREATE_ENTRY_FAILED
System Log Message Description

Could not create entry for entry. MLD failed to create the indicated configuration entry. The configuration request failed. Error: An error occurred error Contact your technical support representative.

Type Severity Action

534

RPD_MLD_ACCOUNTING_OFF

Chapter 72: RPD System Log Messages

RPD_MLD_CFG_GROUP_OUT_OF_RANGE
System Log Message

The combination of group-count count and group-increment ip-address causes some of the groups out of range. The configuration request failed because the indicated configuration object contained a group that is out of range. Error: An error occurred error Modify configuration statement to use a valid value.

Description

Type Severity Action

RPD_MLD_CFG_INVALID_VALUE
System Log Message Description

The object-name configuration object identifier field has an invalid value of value The configuration request failed because the indicated configuration object contained the indicated invalid value. Error: An error occurred error Modify configuration statement to use a valid value.

Type Severity Action

RPD_MLD_CFG_SOURCE_OUT_OF_RANGE
System Log Message

The combination of source-count count and source-increment ip-address causes some of the sources out of range. The configuration request failed because the indicated configuration object contained a source that is out of range. Error: An error occurred error Modify configuration statement to use a valid value.

Description

Type Severity Action

RPD_MLD_DYN_CFG_ALREADY_BOUND
System Log Message

Dynamic configuration session id client-session-id for interface interface-name is already bound to interface old-interface-name.

RPD_MLD_CFG_GROUP_OUT_OF_RANGE

535

JUNOS 10.1 System Log Messages Reference

Description

The indicated dynamic configuration session id is already bound to another interface. The dynamic configuration instantiation request was rejected. Error: An error occurred error Unbind session id from existing interface.

Type Severity Action

RPD_MLD_DYN_CFG_INVALID_STMT
System Log Message Description

Invalid dynamic configuration statement: configuration-statement The indicated dynamic configuration statement was invalid. The dynamic configuration instantiation request was rejected. Error: An error occurred error Remove the unsupported configuration statement.

Type Severity Action

RPD_MLD_DYN_CFG_SES_ID_ADD_FAIL
System Log Message

Failed to add dynamic configuration session id client-session-id to interface interface-name. Failed to associate the indicated dynamic configuration session id to specified interface. The dynamic configuration instantiation request was rejected. Error: An error occurred error

Description

Type Severity

RPD_MLD_DYN_CFG_SES_ID_MISMATCH
System Log Message

Dynamic configuration entry for interface interface-name with session id client-session-id found an existing entry with a different session id of client-session-id-1. The dynamic configuration instantiation request matched an existing dynamic configuration block that had a different session id. The dynamic configuration instantiation request was rejected. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

536

RPD_MLD_DYN_CFG_ALREADY_BOUND

Chapter 72: RPD System Log Messages

RPD_MLD_JOIN
System Log Message

Listener source-address sent a join to destination-address for group group-address source sender-address on interface interface-name at time MLD join event. Event: This message reports an event, not an error info

Description Type Severity

RPD_MLD_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 MLD leave event. Event: This message reports an event, not an error info

Description Type Severity

RPD_MLD_MEMBERSHIP_TIMEOUT
System Log Message

Membership timeout for listener source-address for group group-address source sender-address on interface interface-name at time MLD group membership timeout. Event: This message reports an event, not an error info

Description Type Severity

RPD_MLD_ROUTER_VERSION_MISMATCH
System Log Message

MLD version mismatch on interface-name. Local version: local-version Remote version: remote-version The MLD version running on the local router does not match the one received in the query Event: This message reports an event, not an error warning

Description

Type Severity

RPD_MLD_JOIN

537

JUNOS 10.1 System Log Messages Reference

RPD_MPLS_INTERFACE_ROUTE_ERROR
System Log Message Description

Unable to add route in table table-name for label mpls-label pointing to interface-name There was a failure in adding a Multiprotocol Label Switching (MPLS) route pointing to an interface Event: This message reports an event, not an error notice

Type Severity

RPD_MPLS_INTF_MAX_LABELS_ERROR
System Log Message

Maximum labels exceeded - failed to stack additional label to nexthop on interface interface-name There was a failure in stacking additional label to a nexthop which already has maximum number of labels allowed for the interface Error: An error occurred error

Description

Type Severity

RPD_MPLS_LSP_AUTOBW_NOTICE
System Log Message Description

mpls LSP lsp-name Autobw already in progress, ignoring new trigger The auto-bandwidth adjustment for the indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) already in progress, ignoring new trigger. Event: This message reports an event, not an error notice

Type Severity

RPD_MPLS_LSP_BANDWIDTH_CHANGE
System Log Message Description

MPLS LSP lsp-name bandwidth changed, lsp bandwidth bandwidth bps The bandwidth associated with the indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) changed. Event: This message reports an event, not an error warning

Type Severity

538

RPD_MPLS_INTERFACE_ROUTE_ERROR

Chapter 72: RPD System Log Messages

RPD_MPLS_LSP_CHANGE
System Log Message

MPLS LSP lsp-name change on path-type(pathname) Route lsp-rro lsp bandwidth bandwidth bps The indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) was rerouted and its Record Route Object (RRO) changed. Event: This message reports an event, not an error warning

Description

Type Severity

RPD_MPLS_LSP_DOWN
System Log Message Description

MPLS LSP lsp-name down on path-type(pathname) The indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) went down and could not be used to send traffic. Event: This message reports an event, not an error warning

Type Severity

RPD_MPLS_LSP_SWITCH
System Log Message

MPLS LSP lsp-name switch from old-path-type(old-pathname) to new-path-type(new-pathname), Route lsp-rro: reason lsp bandwidth bandwidth bps The indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) switched from primary path to secondary path or vice versa. Event: This message reports an event, not an error warning

Description

Type Severity

RPD_MPLS_LSP_UP
System Log Message

MPLS LSP lsp-name up on path-type(pathname) Route lsp-rro lsp bandwidth bandwidth bps The indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) came up and could be used to send traffic. Event: This message reports an event, not an error warning

Description

Type Severity

RPD_MPLS_LSP_CHANGE

539

JUNOS 10.1 System Log Messages Reference

RPD_MPLS_OAM_LSP_PING_REPLY_ERR
System Log Message Description

Received ping reply with an error: error-code. Received a LSP ping reply with an error code, for the ping request sent. If any failure action is configured, the failure action will get executed Event: This message reports an event, not an error error

Type Severity

RPD_MPLS_OAM_PING_REPLY_TIMEOUT
System Log Message Description

LSP ping reply timed out LSP ping timed out waiting for a reply. If any failure action is configured, the failure action will get executed Event: This message reports an event, not an error error

Type Severity

RPD_MPLS_OAM_READ_ERROR
System Log Message Description

Unable to read from pipe to MPLS OAM process: reason (error-message) The routing protocol process (rpd) could not read a message available on the read pipe from the MPLS Operation, Administration, and Maintenance process (mplsoamd). Error: An error occurred info Contact your technical support representative.

Type Severity Action

RPD_MPLS_OAM_WRITE_ERROR
System Log Message Description

Unable to write to pipe to MPLS OAM process: (error-message) The routing protocol process (rpd) could not write a message on the write pipe to the MPLS Operation, Administration, and Maintenance process (mplsoamd). Error: An error occurred info Contact your technical support representative.

Type Severity Action

540

RPD_MPLS_OAM_LSP_PING_REPLY_ERR

Chapter 72: RPD System Log Messages

RPD_MPLS_PATH_BANDWIDTH_CHANGE
System Log Message

MPLS path pathname (lsp lsp-name) bandwidth changed, path bandwidth bandwidth bps The bandwidth associated with the indicated Multiprotocol Label Switching (MPLS) path changed. Event: This message reports an event, not an error warning

Description

Type Severity

RPD_MPLS_PATH_BFD_DOWN
System Log Message Description

BFD session for MPLS path pathname went down on LSP lsp-name The routing protocol process (rpd) determined that the Bidirectional Forwarding Detection (BFD) protocol session for the indicated Multiprotocol Label Switching (MPLS) path terminated on the indicated label-switched path (LSP). Event: This message reports an event, not an error notice

Type Severity

RPD_MPLS_PATH_BFD_UP
System Log Message Description

BFD session for MPLS path pathname came up on LSP lsp-name The routing protocol process (rpd) determined that the Bidirectional Forwarding Detection (BFD) protocol session for the the indicated Multiprotocol Label Switching (MPLS) path came up on the indicated label-switched path (LSP). Event: This message reports an event, not an error notice

Type Severity

RPD_MPLS_PATH_BW_NOT_AVAILABLE
System Log Message Description

Unable to satisfy bandwidth configured for MPLS path pathname on LSP lsp-name The bandwidth setting for the indicated Multiprotocol Label Switching (MPLS) path and label-switched path (LSP) was changed recently, but attempts to apply the new setting failed. The LSP continued to use the previous amount of bandwidth. Event: This message reports an event, not an error warning

Type Severity

RPD_MPLS_PATH_BANDWIDTH_CHANGE

541

JUNOS 10.1 System Log Messages Reference

Action

Determine the reason that the bandwidth could not change and make the necessary changes to the software configuration, hardware configuration, or both.

RPD_MPLS_PATH_DOWN
System Log Message Description

MPLS path pathname down on LSP lsp-name The indicated Multiprotocol Label Switching (MPLS) path went down on the indicated label-switched path (LSP). Event: This message reports an event, not an error warning

Type Severity

RPD_MPLS_PATH_PING_DOWN
System Log Message Description

LSP ping failure occured for MPLS path pathname on LSP lsp-name The routing protocol process (rpd) determined that the LSP ping returned error for the indicated Multiprotocol Label Switching (MPLS) path terminated on the indicated label-switched path (LSP). Event: This message reports an event, not an error notice

Type Severity

RPD_MPLS_PATH_UP
System Log Message Description

MPLS path pathname up on LSP lsp-name path bandwidth bandwidth bps The indicated Multiprotocol Label Switching (MPLS) path came up on the indicated label-switched path (LSP). Event: This message reports an event, not an error warning

Type Severity

RPD_MPLS_TABLE_ROUTE_ERROR
System Log Message Description

Unable to add route in table table-name for label mpls-label pointing to next-table-name There was a failure in adding a Multiprotocol Label Switching (MPLS) route pointing to another MPLS routing table Event: This message reports an event, not an error notice

Type Severity

542

RPD_MPLS_PATH_BW_NOT_AVAILABLE

Chapter 72: RPD System Log Messages

RPD_MSDP_PEER_DOWN
System Log Message Description

MSDP peer peer-address peer-group peer-group out of Established state The indicated MSDP peer left the Established state. The routing protocol process (rpd) deleted all active sources learned from the peer and will no longer send 'Source Active' messages to it. Event: This message reports an event, not an error notice

Type Severity

RPD_MSDP_PEER_UP
System Log Message Description Type Severity

MSDP peer peer-address peer-group peer-group into Established state The indicated MSDP peer entered the Established state. Event: This message reports an event, not an error info

RPD_MSDP_SRC_ACTIVE_OVER_LIMIT
System Log Message

Number of MSDP source-active messages about originator exceeded configured limit message The number of MSDP source-active messages received from the indicated instance, peer, or source exceeded the configured limit. All source-active messages are discarded until the limit is no longer exceeded. During periods when the event reported by this message occurs frequently, the routing protocol process (rpd) does not log every occurrence. In this case, the repetitions field in the message indicates how many times the event occurred since the rpd process previously logged this message. Event: This message reports an event, not an error notice

Description

Type Severity

RPD_MSDP_SRC_ACTIVE_OVER_THRESH
System Log Message

Number of MSDP source-active messages about originator exceeded configured threshold message The number of MSDP source-active messages received from the indicated instance, peer, or source exceeded the configured threshold. Until the threshold is no longer exceeded, a random early discard (RED) profile is applied to incoming messages so that only some of them are accepted. During periods when the event reported by

Description

RPD_MSDP_PEER_DOWN

543

JUNOS 10.1 System Log Messages Reference

this message occurs frequently, the routing protocol process (rpd) does not log every occurrence. In this case, the repetitions field in the message indicates how many times the event occurred since the rpd process previously logged this message.
Type Severity

Event: This message reports an event, not an error notice

RPD_MSDP_SRC_ACTIVE_UNDER_LIMIT
System Log Message

Number of MSDP source-active messages about originator no longer exceeded configured limit message The number of MSDP source-active messages received from the indicated instance, peer, or source no longer exceeded the configured limit. Active-source messages are no longer discarded automatically. During periods when the event reported by this message occurs frequently, the routing protocol process (rpd) does not log every occurrence. In this case, the repetitions field in the message indicates how many times the event occurred since the rpd process previously logged this message. Event: This message reports an event, not an error notice

Description

Type Severity

RPD_MSDP_SRC_ACTIVE_UNDER_THRESH
System Log Message

Number of MSDP source-active messages about originator no longer exceeded configured threshold message The number of MSDP source-active messages received from the indicated instance, peer, or source no longer exceeded the configured threshold. A random early discard (RED) profile is no longer applied to incoming messages. During periods when the event reported by this message occurs frequently, the routing protocol process (rpd) does not log every occurrence. In this case, the repetitions field in the message indicates how many times the event occurred since the rpd process previously logged this message. Event: This message reports an event, not an error notice

Description

Type Severity

RPD_OSPF_CFGNBR_P2P
System Log Message

Ignored configured neighbors on point-to-point realm realm-name interface interface-name area area-idi For point-to-point interfaces, OSPF neighbors are learned by using hello messages, so the implicit configuration of neighbors was ignored for the indicated point-to-point interface.

Description

544

RPD_MSDP_SRC_ACTIVE_OVER_THRESH

Chapter 72: RPD System Log Messages

Type Severity Action

Error: An error occurred warning Remove the neighbor configuration for the indicated interface.

RPD_OSPF_LDP_SYNC
System Log Message

OSPF realm realm-name interface interface-name area area-idi advertised with infinite metric for duration seconds already due to loss of synchronization with LDP The OSPF protocol lost synchronization with the Label Distribution Protocol (LDP) on the indicated interface. As a consequence, it began advertising an infinite metric for the interface and has been doing so for the indicated number of seconds. Error: An error occurred warning Determine why LDP lost synchronization with OSPF.

Description

Type Severity Action

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) An OSPF adjacency with the indicated neighboring router was terminated. The local router no longer exchanges routing information with, or directs traffic to, the neighboring router. Event: This message reports an event, not an error notice

Description

Type Severity

RPD_OSPF_NBRUP
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) An OSPF adjacency was established with the indicated neighboring router. The local router can now exchange information with it. Event: This message reports an event, not an error info

Description

Type Severity

RPD_OSPF_CFGNBR_P2P

545

JUNOS 10.1 System Log Messages Reference

RPD_OSPF_OVERLOAD
System Log Message

OSPF instance instance topology topology is going into overload state: number of export prefixes (count) exceeded maximum allowed (maximum-value) The indicated topology in the indicated OSPF instance became overloaded and will remain in that state until an administrator intervenes. Error: An error occurred warning The number of export prefixes exceeded the configured limit. Unconfigure or modify export policies that inject a large number of routes.

Description

Type Severity Cause Action

RPD_OS_MEMHIGH
System Log Message Description

Using size KB of memory, percentage-value percent of available The routing protocol process (rpd) is using the indicated amount and percentage of Routing Engine memory, which is considered excessive. Error: An error occurred error Either rpd is leaking memory or the use of system resources is excessive, perhaps because routing filters are misconfigured or the configured network topology is very complex. Increase the amount of RAM in the Routing Engine.

Type Severity Cause

Action

RPD_PARSE_BAD_LR_NAME
System Log Message Description

executable-name: logical system name "logical-system-name"exceeds count characters The indicated logical system name exceeds the indicated maximum number of characters. Error: An error occurred error Assign a shorter name.

Type Severity Action

546

RPD_OSPF_OVERLOAD

Chapter 72: RPD System Log Messages

RPD_PARSE_BAD_OPTION
System Log Message Description

executable-name: command-line option option is invalid The command line used to start the indicated process included the indicated option, which is invalid. The process did not start. Error: An error occurred error Reissue the command without the invalid option.

Type Severity Action

RPD_PARSE_CMD_ARG
System Log Message Description

executable-name: missing required argument for command-line option option The command line used to start the indicated process did not include the argument required by the indicated option. The process did not start. Error: An error occurred error Reissue the command and include the required argument.

Type Severity Action

RPD_PARSE_CMD_DUPLICATE
System Log Message Description

executable-name: command-line option option is a duplicate The command line used to start the indicated process included the indicated duplicate option. The process did not start. Error: An error occurred error Reissue the command without the duplicate option.

Type Severity Action

RPD_PARSE_CMD_EXTRA
System Log Message Description

executable-name: command-line option option is extraneous The command line used to start the indicated process included the indicated option, which is extraneous. The process did not start.

RPD_PARSE_BAD_OPTION

547

JUNOS 10.1 System Log Messages Reference

Type Severity Action

Error: An error occurred error Reissue the command and omit the extraneous option.

RPD_PIM_NBRDOWN
System Log Message Description Type Severity

PIM neighbor neighbor-address (interface-name) removed due to: reason The routing protocol process (rpd) declared the indicated PIM neighbor inactive. Event: This message reports an event, not an error notice

RPD_PIM_NBRUP
System Log Message Description

PIM new neighbor neighbor-address interface interface-name The routing protocol process (rpd) discovered the indicated new PIM neighbor on the indicated interface. Event: This message reports an event, not an error info

Type Severity

RPD_PPM_READ_ERROR
System Log Message Description

Read error on pipe from ppmd: reason (error-message) The routing protocol process (rpd) could not read a message available on the read pipe from the periodic packet management process (ppmd). Error: An error occurred info Contact your technical support representative.

Type Severity Action

RPD_PPM_WRITE_ERROR
System Log Message Description

function-name: write error on pipe to ppmd (error-message) The routing protocol process (rpd) could not write a message on the pipe to the periodic packet management process (ppmd).

548

RPD_PARSE_CMD_EXTRA

Chapter 72: RPD System Log Messages

Type Severity Action

Error: An error occurred error Contact your technical support representative.

RPD_RA_CFG_CREATE_ENTRY_FAILED
System Log Message Description

Could not create entry for entry. The configuration request failed because the IPv6 routing advertisements failed to create the indicate configuration entry. Error: An error occurred error Contact your technical support representative.

Type Severity Action

RPD_RA_CFG_INVALID_VALUE
System Log Message Description

The object-name configuration object identifier field has an invalid value of value The configuration request failed because the configuration object contained the indicated invalid value. Error: An error occurred error Change the value in the configuration statement to a valid one.

Type Severity Action

RPD_RA_DYN_CFG_ALREADY_BOUND
System Log Message

Dynamic configuration session id client-session-id for interface interface-name is already bound to interface old-interface-name. The dynamic configuration instantiation request was rejected because the indicated session ID was already bound to another interface. Error: An error occurred error Unbind session id from existing interface.

Description

Type Severity Action

RPD_PPM_WRITE_ERROR

549

JUNOS 10.1 System Log Messages Reference

RPD_RA_DYN_CFG_INVALID_STMT
System Log Message Description

Invalid dynamic configuration statement: configuration-statement The dynamic configuration instantiation request was rejected because the indicated dynamic configuration statement was invalid. Error: An error occurred error Remove the unsupported configuration statement.

Type Severity Action

RPD_RA_DYN_CFG_SES_ID_ADD_FAIL
System Log Message

Failed to add dynamic configuration session id client-session-id to interface interface-name. The dynamic configuration instantiation request was rejected because it failed to associate the indicated session ID with the specified interface. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

RPD_RA_DYN_CFG_SES_ID_MISMATCH
System Log Message

Dynamic configuration entry for interface interface-name with session id client-session-id found an existing entry with a different session id of client-session-id-1. The dynamic configuration instantiation request was rejected because it matched an existing dynamic configuration block that had a different session ID. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

RPD_RDISC_CKSUM
System Log Message

Bad checksum for router solicitation from source-address to destination-address

550

RPD_RA_DYN_CFG_INVALID_STMT

Chapter 72: RPD System Log Messages

Description

The routing protocol process (rpd) ignored a router discovery solicitation message from the indicated address because the checksum in the message's ICMP header was invalid. Event: This message reports an event, not an error warning The solicitation message was incorrectly generated or damaged in transit. Examine the host that generated the solicitation message.

Type Severity Cause Action

RPD_RDISC_NOMULTI
System Log Message Description

Ignoring interface interface-address on interface-name -- multicast not available The indicated interface was configured for router discovery, but does not support IP multicast operations as required. The routing protocol process (rpd) did not enable router discovery on the interface. Error: An error occurred warning Do not configure router discovery on the interface.

Type Severity Action

RPD_RDISC_NORECVIF
System Log Message

Unable to locate interface for router solicitation from source-address to destination-address The routing protocol process (rpd) ignored a router discovery solicitation message from the indicated router because the router's IP address does not share the IP prefix of the local router. The local router is not a candidate for the indicated router because they are not on the same network. Event: This message reports an event, not an error warning Although the indicated router seems to be locally attached, no interfaces on the local router are configured to handle its IP address. Either the indicated router is configured with the wrong IP address, or the local router is not correctly configured for the network that the indicated router is using. Ignore this message if it indicates the desired configuration, or reconfigure one or both routers to share a common network.

Description

Type Severity Cause

Action

RPD_RDISC_CKSUM

551

JUNOS 10.1 System Log Messages Reference

RPD_RDISC_SOLICITADDR
System Log Message

Expected multicast (expected-address) for router solicitation from source-address to destination-address A router discovery solicitation message received from the indicated address was not sent to the expected multicast address for all routers. Event: This message reports an event, not an error warning Examine the configuration of the router that generated the router discovery solicitation message.

Description

Type Severity Action

RPD_RDISC_SOLICITICMP
System Log Message

Nonzero ICMP code (value) for router solicitation from source-address to destination-address The routing protocol process (rpd) ignored a router discovery solicitation message from the indicated router because the ICMP code in the message header was nonzero. Event: This message reports an event, not an error warning The solicitation message was incorrectly generated. Examine the host that generated the solicitation message.

Description

Type Severity Cause Action

RPD_RDISC_SOLICITLEN
System Log Message

Insufficient length (length) for router solicitation from source-address to destination-address The routing protocol process (rpd) ignored a router discovery solicitation message from the indicated router, because the indicated message length is too short. Event: This message reports an event, not an error warning The solicitation message was incorrectly generated. Examine the host that generated the solicitation message.

Description

Type Severity Cause Action

552

RPD_RDISC_SOLICITADDR

Chapter 72: RPD System Log Messages

RPD_RIP_AUTH_REQUEST
System Log Message Description

Request with invalid authentication from source-address (interface-name) The routing protocol process (rpd) ignored an RIP request because the request authentication failed. Event: This message reports an event, not an error notice

Type Severity

RPD_RIP_AUTH_UPDATE
System Log Message Description

Update with invalid authentication from source-address (interface-name) The routing protocol process (rpd) ignored a RIP update because authentication of the update failed. Event: This message reports an event, not an error notice

Type Severity

RPD_RIP_JOIN_BROADCAST
System Log Message Description

Unable to get broadcast address on interface-name; using the all-ones address RIP cannot run on the indicated interface because the routing protocol process (rpd) could not obtain the broadcast address on the interface as required for running RIP version 1 or version 2 in compatibility mode. Error: An error occurred error

Type Severity

RPD_RIP_JOIN_MULTICAST
System Log Message Description

Unable to join multicast group on interface-name: error-message RIP cannot run on the indicated interface, because the routing protocol process (rpd) could not join the RIP multicast group as required for RIP version 2 multicast updates. Error: An error occurred error

Type Severity

RPD_RIP_AUTH_REQUEST

553

JUNOS 10.1 System Log Messages Reference

RPD_RSVP_BACKUP_DOWN
System Log Message Description

Backup for protecting LSP lsp-name down, using bypass bypass-lsp-namereason When link protection is enabled, a backup label-switched path (LSP) is needed to maintain a protected LSP's control-plane connectivity when topology failures are detected. The backup LSP for the indicated protected LSP failed. The failure can cause traffic loss because the protected LSP tears down when there is no backup. If the reason for the backup failure can be determined, it is reported in the message. Event: This message reports an event, not an error warning

Type Severity

RPD_RSVP_BYPASS_DOWN
System Log Message Description

RSVP bypass bypass-lsp-name for protecting interface interface-name went downreason The indicated RSVP link-protection bypass, which was protecting the indicated interface, was terminated. If the reason for the termination can be determined, it is reported in the message. Event: This message reports an event, not an error warning

Type Severity

RPD_RSVP_BYPASS_UP
System Log Message Description

RSVP bypass bypass-lsp-name for protecting interface interface-name came up The indicated RSVP link-protection bypass was established to protect the indicated interface. Event: This message reports an event, not an error warning

Type Severity

RPD_RSVP_LSP_SWITCH
System Log Message

RSVP LSP lsp-name switched to backup; using bypass LSP bypass-lsp-name, route lsp-rro RSVP detected a failure downstream for the indicated label-switched path (LSP) and switched it to a backup using the indicated bypass LSP. Event: This message reports an event, not an error

Description

Type

554

RPD_RSVP_BACKUP_DOWN

Chapter 72: RPD System Log Messages

Severity Cause

warning The downstream interface or router for the LSP went down.

RPD_RSVP_MAXIMUM_SESSIONS
System Log Message Description

RSVP maximum session limit of limit reached The routing protocol process (rpd) could not set up an RSVP session because the indicated limit on the number of sessions was reached. Event: This message reports an event, not an error warning

Type Severity

RPD_RSVP_NBRDOWN
System Log Message Description Type Severity Cause

RSVP neighbor neighbor-address down on interface interface-name, reason The RSVP neighbor to the indicated address was terminated. Event: This message reports an event, not an error warning The communication path to the neighboring router was disrupted, a protocol error occurred, or the neighboring router was powered down.

RPD_RSVP_NBRUP
System Log Message Description Type Severity

RSVP neighbor neighbor-address up on interface interface-name An RSVP neighbor was established to the indicated address. Event: This message reports an event, not an error warning

RPD_RT_CFG_BR_CONFLICT
System Log Message

static route: route-prefix is also configured as backup-router destination, turn on retain flag to ensure proper functionality A conflict occurred between the system backup router configuration and the indicated static route. Event: This message reports an event, not an error

Description

Type

RPD_RSVP_LSP_SWITCH

555

JUNOS 10.1 System Log Messages Reference

Severity Action

warning Add the retain flag to the static route

RPD_RT_CFG_CREATE_ENTRY_FAILED
System Log Message Description Type Severity Action

Could not create entry entry RT failed to create the indicated configuration entry. The configuration request failed. Error: An error occurred error Contact your technical support representative.

RPD_RT_CFG_INVALID_VALUE
System Log Message Description

The object-name configuration object identifier field has an invalid value of value The configuration request failed because the indicated configuration object contained the indicated invalid value. Error: An error occurred error Modify configuration statement to use a valid value.

Type Severity Action

RPD_RT_DUPLICATE_RD
System Log Message

routing-instance routing-instance has duplicate route-distinguisher route-discriminator as routing-instance existing-routing-instance The route-distinguisher assigned to this routing instance has already been assigned to another routing instance (as indicated). Error: An error occurred error

Description

Type Severity

RPD_RT_ERROR
System Log Message Description

rt_event_event-name: fatal state error A route in the routing table was found to be in an unrecoverable error state.

556

RPD_RT_CFG_BR_CONFLICT

Chapter 72: RPD System Log Messages

Type Severity

Error: An error occurred critical

RPD_RT_IFUP
System Log Message Description

UP route for interface interface-name index logical-interface-index address/prefix-length The interface route for the indicated interface and prefix changed state from down to up, becoming available for routing. Event: This message reports an event, not an error warning

Type Severity

RPD_RT_PATH_LIMIT_BELOW
System Log Message

Number of paths (count) in table table-name is now less than the configured maximum (limit) The number of paths in the indicated routing table previously equaled or exceeded the indicated limit, but went down to the indicated number, which is below the limit. Event: This message reports an event, not an error warning

Description

Type Severity

RPD_RT_PATH_LIMIT_REACHED
System Log Message Description

Number of paths (count) in table table-name status configured maximum (limit) The indicated total number of paths in the indicated routing table equaled or exceeded the indicated configured limit. Attempts to add some types of path to the table fail while this condition holds, but the path count can exceed the limit if paths are forcibly added (for example, for static routes). This message first appears in the log when the limit is reached and repeats periodically until the number of paths goes below the limit. Error: An error occurred error

Type Severity

RPD_RT_PATH_LIMIT_WARNING
System Log Message

Number of paths (count) in table table-name reached warning threshold (threshold percent of configured maximum limit)

RPD_RT_ERROR

557

JUNOS 10.1 System Log Messages Reference

Description

The indicated total number of paths in the indicated routing table reached the threshold for a warning. The threshold is the indicated percentage of the indicated configured limit on the number of paths. Event: This message reports an event, not an error warning

Type Severity

RPD_RT_PREFIX_LIMIT_BELOW
System Log Message

Number of prefixes (prefix-count) in table table-name is now less than the configured maximum (limit) The number of prefixes in the indicated routing table previously equaled or exceeded the indicated limit, but went down to the indicated number, which is below the limit. Event: This message reports an event, not an error warning

Description

Type Severity

RPD_RT_PREFIX_LIMIT_REACHED
System Log Message

Number of prefixes (prefix-count) in table table-name status configured maximum (limit) The indicated total number of prefixes in the indicated routing table equaled or exceeded the indicated configured limit. Attempts to add some types of prefix to the table fail while this condition holds, but the prefix count can exceed the limit if prefixes are forcibly added (for example, for static routes). This message first appears in the log when the limit is reached and repeats periodically until the number of prefixes goes below the limit. Error: An error occurred error

Description

Type Severity

RPD_RT_PREFIX_LIMIT_WARNING
System Log Message

Number of prefixes (prefix-count) in table table-name reached warning threshold (threshold percent of configured maximum limit) The indicated total number of prefixes in the indicated routing table reached the threshold for a warning. The threshold is the indicated percentage of the indicated configured limit on the number of prefixes. Event: This message reports an event, not an error warning

Description

Type Severity

558

RPD_RT_PATH_LIMIT_WARNING

Chapter 72: RPD System Log Messages

RPD_RT_SHOWMODE
System Log Message Description

invalid display mode (mode) The indicated display mode was specified in a 'show route' command and is unsupported. Error: An error occurred error

Type Severity

RPD_RT_TAG_ID_ALLOC_FAILED
System Log Message Description

Unable to allocate object-name for routing instance instance The routing protocol process (rpd) could not allocate either labels or subunits (as indicated) for the indicated routing instance, because the result number of objects would have exceeded the limit. Error: An error occurred error

Type Severity

RPD_SCHED_CALLBACK_LONGRUNTIME
System Log Message Description

function-name: excessive runtime time during action of module The indicated submodule of the routing protocol process (rpd) ran uninterrupted for the indicated period of time, which is considered excessive. Event: This message reports an event, not an error warning The duration was noted because task accounting is enabled. The function might be implemented inefficiently.

Type Severity Cause

RPD_SCHED_CUMULATIVE_LONGRUNTIME
System Log Message

function-name: excessive runtime (total of time in count callbacks) after action of module Several submodules of the routing protocol process (rpd) ran uninterrupted for the indicated period of time, which is considered excessive. Event: This message reports an event, not an error

Description

Type

RPD_RT_SHOWMODE

559

JUNOS 10.1 System Log Messages Reference

Severity Cause

warning The duration was noted because task accounting is enabled. The function might be implemented inefficiently.

RPD_SCHED_MODULE_LONGRUNTIME
System Log Message Description

function-name: excessive runtime time during action of module Several submodules of the routing protocol process (rpd) ran uninterrupted for the indicated period of time, which is considered excessive. Event: This message reports an event, not an error warning The duration was noted because task accounting is enabled. The function might be implemented inefficiently.

Type Severity Cause

RPD_SCHED_TASK_LONGRUNTIME
System Log Message Description

function-name ran for total-time (user-time user, system-time system) doing action A task callback within the routing protocol process (rpd) ran uninterrupted for the indicated period of time, which is considered excessive. Event: This message reports an event, not an error warning The duration was noted because task accounting is enabled. The function might be implemented inefficiently.

Type Severity Cause

RPD_SIGNAL_TERMINATE
System Log Message Description

signal-name termination signal received In response to the indicated termination request, the routing protocol process (rpd) terminated adjacencies with neighbors and shut down. Event: This message reports an event, not an error notice

Type Severity

RPD_SNMP_CONN_PROG
System Log Message

function-name: error-message

560

RPD_SCHED_CUMULATIVE_LONGRUNTIME

Chapter 72: RPD System Log Messages

Description

The indicated error occurred while the routing protocol process (rpd) was connecting to the Simple Network Management Protocol (SNMP) master agent. Error: An error occurred info

Type Severity

RPD_SNMP_CONN_QUIT
System Log Message Description

function-name: unable to connect to SNMP agent (pathname): error-message The routing protocol process (rpd) could not connect to the indicated Simple Network Management Protocol (SNMP) master agent. Error: An error occurred error

Type Severity

RPD_SNMP_CONN_RETRY
System Log Message Description

function-name: reattempting connection to SNMP agent (pathname): error-message The routing protocol process (rpd) tried again to connect to the indicated Simple Network Management Protocol (SNMP) master agent after a connection attempt failed. Error: An error occurred error

Type Severity

RPD_SNMP_INVALID_SOCKET
System Log Message Description

function-name: socket file-descriptor is invalid The routing protocol process (rpd) could not send a message to a Simple Network Management Protocol (SNMP) master agent because the indicated socket is invalid. Error: An error occurred error

Type Severity

RPD_SNMP_SOCKOPT_BLOCK
System Log Message Description

function-name: unable to set nonblocking option The routing protocol process (rpd) could not set a socket to nonblocking mode after connecting to the Simple Network Management Protocol (SNMP) master agent.

RPD_SNMP_CONN_PROG

561

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

RPD_SNMP_SOCKOPT_RECVBUF
System Log Message Description

function-name: unable to set recvbuf option The routing protocol process (rpd) could not set the size of the kernel receive buffer, which allows it to accept the largest possible packet from the Simple Network Management Protocol (SNMP) master agent. Error: An error occurred error

Type Severity

RPD_SNMP_SOCKOPT_SENDBUF
System Log Message Description

function-name: unable to set sendbf option The routing protocol process (rpd) could not set the size of the kernel send buffer, which allows it to send the largest possible packet to the Simple Network Management Protocol (SNMP) master agent. Error: An error occurred error

Type Severity

RPD_START
System Log Message Description Type Severity

Start executable-name[pid] version version built date The routing protocol process (rpd) started. Event: This message reports an event, not an error info

RPD_SYSTEM
System Log Message Description Type Severity

reason: error-message A system call made by the routing protocol process (rpd) failed. Error: An error occurred error

562

RPD_SNMP_SOCKOPT_BLOCK

Chapter 72: RPD System Log Messages

Cause

It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.

RPD_TASK_BEGIN
System Log Message Description Type Severity

Commencing routing updates, version rpd-version, built date by builder The routing protocol process (rpd) started. Event: This message reports an event, not an error notice

RPD_TASK_CHILDKILLED
System Log Message Description

task-name terminated by SIGsignal-namecore-dump-status While a child process of the routing protocol process (rpd) was performing the indicated operation, it terminated in response to the indicated signal. Event: This message reports an event, not an error error

Type Severity

RPD_TASK_CHILDSTOPPED
System Log Message Description

task-name stopped by SIGsignal-name While a child process of the routing protocol process (rpd) was performing the indicated operation, it stopped in response to the indicated signal. Event: This message reports an event, not an error error

Type Severity

RPD_TASK_DYN_REINIT
System Log Message Description Type Severity

Dynamic reconfiguration in process The routing protocol process (rpd) reinitialized. Event: This message reports an event, not an error info

RPD_SYSTEM

563

JUNOS 10.1 System Log Messages Reference

RPD_TASK_FORK
System Log Message Description Type Severity

Unable to fork task-name: error-message The routing protocol process failed to create the indicated child process. Error: An error occurred error

RPD_TASK_GETWD
System Log Message Description Type Severity Cause

getwd: error-message The getwd() system call made by the routing protocol process (rpd) failed. Error: An error occurred error It is possible that the kernel lacked the resources to fulfill the request. The rpd process will recover.

RPD_TASK_MASTERSHIP
System Log Message Description

Assuming mastership The routing protocol process (rpd) became active when the Routing Engine on which it was running assumed mastership. Event: This message reports an event, not an error info

Type Severity

RPD_TASK_NOREINIT
System Log Message Description

Reinitialization not possible The routing protocol process (rpd) failed to reinitialize as requested, because it was running in a state that did not allow reconfiguration. Error: An error occurred error

Type Severity

564

RPD_TASK_FORK

Chapter 72: RPD System Log Messages

RPD_TASK_PIDCLOSED
System Log Message Description

Unable to close and remove filename: error-message The routing protocol process (rpd) tried to close and remove the file that records its process ID (PID), which serves to prevent multiple instances of rpd from running simultaneously. The attempt failed. Error: An error occurred error

Type Severity

RPD_TASK_PIDFLOCK
System Log Message Description

flock(filename, LOCK_EX): error-message The routing protocol process (rpd) issued the flock() system call on the file that records its process ID (PID), which serves to prevent multiple instances of rpd from running simultaneously. The system call failed. Error: An error occurred error

Type Severity

RPD_TASK_PIDWRITE
System Log Message Description

Unable to write to fd filename: error-message The routing protocol process (rpd) tried to write to the file that records its process ID (PID), which serves to prevent multiple instances of rpd from running simultaneously. The attempt failed. Error: An error occurred error

Type Severity

RPD_TASK_REINIT
System Log Message Description Type Severity

Reinitializing The routing protocol process (rpd) reinitialized. Event: This message reports an event, not an error info

RPD_TASK_PIDCLOSED

565

JUNOS 10.1 System Log Messages Reference

RPD_TASK_SIGNALIGNORE
System Log Message Description

sigaction(SIGsignal-name): error-message The routing protocol process (rpd) informed the kernel that it wished to ignore the indicated signal, but the kernel failed to process the request. Error: An error occurred error

Type Severity

RPD_TRACE_FAILED
System Log Message Description

Unable to write to trace file filename The routing protocol process (rpd) could not write to the indicated trace file, and stopped attempting to do so. The next commit of the configuration database will reenable tracing. Event: This message reports an event, not an error error

Type Severity

566

RPD_TASK_SIGNALIGNORE

Chapter 73

RT System Log Messages

This chapter describes messages with the RT prefix. They are generated on routers running the JUNOS Software with enhanced services by the Packet Forwarding Engine as it processes packets for security control in real time.

RT_FLOW_SESSION_CLOSE
System Log Message

session closed reason: source-address/source-port->destination-address/destination-port service-name nat-source-address/nat-source-port->nat-destination-address/nat-destination-port src-nat-rule-name dst-nat-rule-name protocol-id policy-name source-zone-name destination-zone-name session-id-32 packets-from-client(bytes-from-client) packets-from-server(bytes-from-server) elapsed-time A security session was closed. Event: This message reports an event, not an error info

Description Type Severity

RT_FLOW_SESSION_CREATE
System Log Message

session created source-address/source-port->destination-address/destination-port service-name nat-source-address/nat-source-port->nat-destination-address/nat-destination-port src-nat-rule-name dst-nat-rule-name protocol-id policy-name source-zone-name destination-zone-name session-id-32 A security session was created. Event: This message reports an event, not an error info

Description Type Severity

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

RT_FLOW_SESSION_CLOSE

567

JUNOS 10.1 System Log Messages Reference

Description Type Severity

A security session was not permitted by policy. Event: This message reports an event, not an error info

RT_GTP_BAD_LICENSE
System Log Message Description

GTP invalid license (gtpP memory-address) The GPRS tunneling protocol (GTP) is not enabled. The user needs to enable GTP to solve this problem. Error: An error occurred error

Type Severity

RT_GTP_DEL_TUNNEL_V0
System Log Message

Delete tunnel for V0 gtp-array-index (tid gtp-mobile-id1gtp-mobile-id2), in gtp-tunnel-in-count out gtp-tunnel-out-count, duration: duration seconds A GPRS tunneling protocol (GTP) version 0 tunnel was deleted. Event: This message reports an event, not an error info

Description Type Severity

RT_GTP_DEL_TUNNEL_V1
System Log Message

Delete tunnel V1 gtp-array-index (SGSN teid gtp-teid), in gtp-tunnel-in-count out gtp-tunnel-out-count, duration: duration seconds A GPRS tunneling protocol (GTP) version 1 tunnel was deleted. Event: This message reports an event, not an error info

Description Type Severity

RT_GTP_PKT_APN_IE
System Log Message Description

APN IE: name Displays the contents of the Access Point Name (APN) information element carried in the GPRS tunneling protocol (GTP) message. Event: This message reports an event, not an error

Type

568

RT_FLOW_SESSION_DENY

Chapter 73: RT System Log Messages

Severity

info

RT_GTP_PKT_DESCRIPTION_CHARGING
System Log Message Description

GTP source-address -> destination-address charging vmajor-version Displays the GPRS tunneling protocol (GTP) packet description for a GTP charging message. The description includes the source and destination address and version. Event: This message reports an event, not an error info

Type Severity

RT_GTP_PKT_DESCRIPTION_V0
System Log Message

GTP source-address -> destination-address TID gtp-mobile-id1gtp-mobile-id2 (index gtp-array-index) Displays the GPRS tunneling protocol (GTP) packet description for a GTP version 0 message. The description includes the source and destination address, 64-bit tunnel ID, and index. Event: This message reports an event, not an error info

Description

Type Severity

RT_GTP_PKT_DESCRIPTION_V1
System Log Message Description

GTP source-address -> destination-address TeID xgtp-teid (index gtp-array-index) Displays the GPRS tunneling protocol (GTP) packet description for a GTP version 1 message. The description includes the source and destination address, tunnel endpoint ID, and index. Event: This message reports an event, not an error info

Type Severity

RT_GTP_PKT_ENDUSER_ADDR_IE_IPV4
System Log Message Description

EndUserAddr IE: ip-address 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. Event: This message reports an event, not an error

Type

RT_GTP_PKT_APN_IE

569

JUNOS 10.1 System Log Messages Reference

Severity

info

RT_GTP_PKT_GSNADDR_IE
System Log Message Description

GSNaddr IE: ip-address Displays the contents of the GPRS Support Node (GSN) Address information element carried in the GPRS tunneling protocol (GTP) message. The content includes the GSN IP address. Event: This message reports an event, not an error info

Type Severity

RT_GTP_PKT_IMSI_IE
System Log Message Description

IMSI IE: gtp-mobile-id1gtp-mobile-id2 Displays the contents of the International Mobile Subscriber Identity (IMSI) information element carried in the GPRS tunneling protocol (GTP) message. The content includes the lower and higher halves of the GTP mobile ID. Event: This message reports an event, not an error info

Type Severity

RT_GTP_PKT_MSISDN_IE
System Log Message Description

MSisdn IE: gtp-isdn-number Displays the contents of the MS International PSTN/ISDN Number (MSISDN) information element carried in the GPRS tunneling protocol (GTP) message. The content includes the ISDN number. Event: This message reports an event, not an error info

Type Severity

RT_GTP_PKT_RESULT
System Log Message Description

***message Displays the GPRS tunneling protocol (GTP) packet process result, providing information about whether the packet is passed or dropped. Event: This message reports an event, not an error info

Type Severity

570

RT_GTP_PKT_ENDUSER_ADDR_IE_IPV4

Chapter 73: RT System Log Messages

RT_GTP_SANITY_EXTENSION_HEADER
System Log Message Description

*** GTP-DROP message-type (sanity): wrong extension header The GPRS tunneling protocol (GTP) packet has an incorrect extension header and the packet will be dropped. Error: An error occurred error

Type Severity

RT_GTP_SYSTEM_ERROR
System Log Message Description

*** GTP-DROP message-type: bad system status (error-code) The GPRS tunneling protocol (GTP) packet was dropped due to a firewall system error, as indicated by the error code. Error: An error occurred error

Type Severity

RT_H323_CALL_LIMIT_EXCEED
System Log Message Description Type Severity

Failed to process the packet, active call limit exceeded maximum-value The maximum H.323 call limit has been exceeded. Error: An error occurred error

RT_H323_NAT_COOKIE_NOT_FOUND
System Log Message Description Type Severity

object-name cannot find cookie from session Failed to find the H.323 NAT cookie. Error: An error occurred error

RT_H323_RAS_REQ_FLOOD
System Log Message

RAS Request flood to gatekeeper destination-address detected, request threshold threshold

RT_GTP_SANITY_EXTENSION_HEADER

571

JUNOS 10.1 System Log Messages Reference

Description

H.323 Registration Authentication Status request messages have exceeded the configured threshold. Error: An error occurred error

Type Severity

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. Received IPSec packet with bad SPI Error: An error occurred error

Description Type Severity

RT_IPSEC_REPLAY
System Log Message

Replay packet detected on IPSec tunnel on interface-name with tunnel ID 0xtunnel-id! From source-address to destination-address/length, type, SPI 0xindex, SEQ 0xsequence-number. Received IPSec replay packet Error: An error occurred error

Description Type Severity

RT_MGCP_CALL_LIMIT_EXCEED
System Log Message Description Type Severity

Exceed maximum call max active call numbermaximum-value The maximum MGCP active call limit has been exceeded. Error: An error occurred error

RT_MGCP_DECODE_FAIL
System Log Message Description Type

Failed to decode MGCP packet Failed to decode MGCP message. Error: An error occurred

572

RT_H323_RAS_REQ_FLOOD

Chapter 73: RT System Log Messages

Severity

error

RT_MGCP_MEM_ALLOC_FAILED
System Log Message Description Type Severity

Failed to allocate memory for object-name Failed to allocate memory for the MGCP objects. Error: An error occurred error

RT_MGCP_REG_NAT_VEC_FAIL
System Log Message Description Type Severity

Failed to add MGCP object-name to flow module Failed to register the MGCP ALG vector with the flow module. Error: An error occurred error

RT_MGCP_REG_RM_FAIL
System Log Message Description Type Severity

Failed to register MGCP ALG with Resource Manager Failed to register the MGCP Resource Manager client. Error: An error occurred error

RT_MGCP_REM_NAT_VEC_FAIL
System Log Message Description Type Severity

Failed to remove MGCP object-name from flow module Failed to remove the MGCP ALG vector from the flow module. Error: An error occurred error

RT_MGCP_RM_CLIENTID_FAIL
System Log Message Description

MGCP ALG Resource Manager client registration failed Failed to obtain the MGCP Resource Manager client identifier.

RT_MGCP_DECODE_FAIL

573

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

RT_MGCP_UNREG_BY_RM
System Log Message Description Type Severity

MGCP ALG client has been unregistered by Resource Manager The Resource Manager has unregistered the MGCP Resource Manager client. Error: An error occurred error

RT_SCCP_CALL_LIMIT_EXCEED
System Log Message Description Type Severity

Failed to create SCCP ALG call, call limit maximum-value exceeded The maximum SCCP call limit has been exceeded. Error: An error occurred error

RT_SCCP_CALL_RATE_EXCEED
System Log Message Description Type Severity

The SCCP active call rate limit maximum-value has been exceeded The SCCP active call rate limit has been exceeded. Error: An error occurred error

RT_SCCP_DECODE_FAIL
System Log Message Description Type Severity

Failed to decode SCCP packet from source-address->destination-address Failed to decode SCCP packet. Error: An error occurred error

RT_SCCP_NAT_COOKIE_NOT_FOUND
System Log Message

Failed to find SCCP ALG cookie from session

574

RT_MGCP_RM_CLIENTID_FAIL

Chapter 73: RT System Log Messages

Description Type Severity

Failed to find SCCP NAT cookie. Error: An error occurred error

RT_SCCP_REM_NAT_VEC_FAIL
System Log Message Description Type Severity

Failed to remove SCCP ALG vector from flow module Failed to remove the SCCP ALG vector from the flow module. Error: An error occurred error

RT_SCCP_UNREG_RM_FAIL
System Log Message

Failed to unregister SCCP client from Resource Manager when the ALG was unregistered Failed to unregister SCCP client from Resource Manager when the ALG was unregistered. Error: An error occurred error

Description

Type Severity

RT_SCREEN_ICMP
System Log Message

attack-name source: source-address, destination: destination-address, zone name: source-zone-name, interface name: interface-name ICMP attack category Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_ICMP_FLOOD
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name ICMP flood attack Event: This message reports an event, not an error

Description Type

RT_SCCP_NAT_COOKIE_NOT_FOUND

575

JUNOS 10.1 System Log Messages Reference

Severity

error

RT_SCREEN_ICMP_FRAG
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name fragmented ICMP packet attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_ICMP_ID
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name ICMP zero ID attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_ICMP_LARGE
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name large ICMP packet attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_ICMP_PING_DEATH
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name ping of death attack Event: This message reports an event, not an error error

Description Type Severity

576

RT_SCREEN_ICMP_FLOOD

Chapter 73: RT System Log Messages

RT_SCREEN_IP
System Log Message

attack-name source: source-address, destination: destination-address, protocol-id: protocol-id, zone name: source-zone-name, interface name: interface-name IP attack category Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_IP_BAD_OPT
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name IP bad option attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_IP_FRAG
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name IP fragment attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_IP_LAND
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name IP land attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_IP

577

JUNOS 10.1 System Log Messages Reference

RT_SCREEN_IP_OPT_FILTER_ROUTE
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name IP source route option attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_IP_OPT_LSR
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name IP loose source route option attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_IP_OPT_RECORD
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name IP record route option attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_IP_OPT_SCHT
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name IP security option attack Event: This message reports an event, not an error error

Description Type Severity

578

RT_SCREEN_IP_OPT_FILTER_ROUTE

Chapter 73: RT System Log Messages

RT_SCREEN_IP_OPT_SSR
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name IP strict source route option attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_IP_OPT_STREAM
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name IP stream option attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_IP_OPT_TIMESTAMP
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name IP timestamp option attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_IP_SPOOFING
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name IP spoofing attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_IP_OPT_SSR

579

JUNOS 10.1 System Log Messages Reference

RT_SCREEN_IP_SWEEP
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name IP sweeping attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_IP_UNKNOWN_PROT
System Log Message

source: source-address, destination: destination-address, protocol-id: protocol-idzone name: filter-name, interface name: interface-name IP unknown protocol attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_MAL_URL
System Log Message

source: source-address-source-port, destination: destination-address-destination-port, protocol-id: protocol-idzone name: filter-name, interface name: interface-name malicious URL attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_OVER_SESSION_DST
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name session from the same destination address exceeds the threshold Event: This message reports an event, not an error error

Description Type Severity

580

RT_SCREEN_IP_SWEEP

Chapter 73: RT System Log Messages

RT_SCREEN_OVER_SESSION_SRC
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name session from the same source address exceeds the threshold Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_PORT_SCAN
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name port scan attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_SESSION_LIMIT
System Log Message

attack-name message: ip-address, zone name: source-zone-name, interface name: interface-name Session limit category Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_SYN_ACK_ACK
System Log Message

source: source-address-source-port, destination: destination-address-destination-port, zone name: filter-name, interface name: interface-name SYN-ACK-ACK attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_OVER_SESSION_SRC

581

JUNOS 10.1 System Log Messages Reference

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 TCP attack category Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_TCP_DST_IP
System Log Message

attack-name destination: destination-address, zone name: source-zone-name, interface name: interface-name TCP destination IP attack category Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_TCP_FIN_NO_ACK
System Log Message

source: source-address-source-port, destination: destination-address-destination-port, zone name: filter-name, interface name: interface-name TCP FIN without ACK flag attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_TCP_FRAG
System Log Message

source: source-address-source-port, destination: destination-address-destination-port, zone name: filter-name, interface name: interface-name TCP fragment attack Event: This message reports an event, not an error error

Description Type Severity

582

RT_SCREEN_TCP

Chapter 73: RT System Log Messages

RT_SCREEN_TCP_NO_FLAG
System Log Message

source: source-address-source-port, destination: destination-address-destination-port, zone name: filter-name, interface name: interface-name TCP no flag attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_TCP_SRC_IP
System Log Message

attack-name source: source-address, zone name: source-zone-name, interface name: interface-name TCP source IP attack category Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_TCP_SYN_FIN
System Log Message

source: source-address-source-port, destination: destination-address-destination-port, zone name: filter-name, interface name: interface-name TCP SYN-FIN flag attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_TCP_SYN_FLOOD
System Log Message

source: source-address-source-port, destination: destination-address-destination-port, zone name: filter-name, interface name: interface-name TCP SYN flood attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_TCP_NO_FLAG

583

JUNOS 10.1 System Log Messages Reference

RT_SCREEN_TEAR_DROP
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name tear drop attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_UDP
System Log Message

attack-name source: source-address:source-port, destination: destination-address:destination-port, zone name: source-zone-name, interface name: interface-name UDP attack category Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_UDP_FLOOD
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name UDP flood attack Event: This message reports an event, not an error error

Description Type Severity

RT_SCREEN_WINNUKE
System Log Message

source: source-address, destination: destination-address, zone name: filter-name, interface name: interface-name winnuke attack Event: This message reports an event, not an error error

Description Type Severity

584

RT_SCREEN_TEAR_DROP

Chapter 73: RT System Log Messages

RT_SIP_CALL_LIMIT_EXCEED
System Log Message Description Type Severity

Exceed maximum call The maximum SIP call limit has been exceeded. Error: An error occurred error

RT_SIP_DECODE_FAIL
System Log Message Description Type Severity

Failed to decode SIP packet error-message Failed to decode incoming SIP packet. Error: An error occurred error

RT_SIP_INIT_EP_FAIL
System Log Message Description Type Severity

The SIP stack failed to create an endpoint with the configuration Failed to initialize SIP endpoint. Error: An error occurred error

RT_SIP_INIT_LISTENER_FAIL
System Log Message Description Type Severity

The SIP stack failed endpoint failed to create a dummy listener Failed to initialize SIP transport listener. Error: An error occurred error

RT_SIP_MEM_ALLOC_FAILED
System Log Message Description

Failed to allocate memory for object-name Failed to allocate memory from the memory pool.

RT_SIP_CALL_LIMIT_EXCEED

585

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

RT_SIP_REG_NAT_VEC_FAIL
System Log Message Description Type Severity

Failed to add SIP ALG vector to flow module Failed to register SIP ALG vector with the flow module. Error: An error occurred error

RT_SIP_REG_RM_FAIL
System Log Message Description Type Severity

Failed to register SIP ALG with the Resource Manager Failed to register the SIP ALG Resource Manager client. Error: An error occurred error

RT_SIP_REM_NAT_VEC_FAIL
System Log Message Description Type Severity

Failed to remove SIP ALG vector from flow module Failed to remove the SIP ALG vector from the flow module. Error: An error occurred error

RT_SIP_UNREG_BY_RM
System Log Message Description Type Severity

SIP client has been unregistered by RM The Resource Manager has notified SIP that a client has been unregistered. Error: An error occurred error

RT_SOURCE_NAT_ALARM_CLEAR
System Log Message

Utilization of source nat pool 'nat-pool-name' hits clear threshold 'threshold%%'

586

RT_SIP_MEM_ALLOC_FAILED

Chapter 73: RT System Log Messages

Description Type Severity

Utilization of source NAT pool reaches the alarm clear threshold. Error: An error occurred error

RT_SOURCE_NAT_ALARM_RAISE
System Log Message Description Type Severity

Utilization of source nat pool 'nat-pool-name' hits raise threshold 'threshold%%' Utilization of source NAT pool reaches the alarm raise threshold. Error: An error occurred error

RT_SRC_NAT_ALARM_CLEAR
System Log Message Description Type Severity

Utilization of source nat pool 'nat-pool-name' hits clear threshold 'threshold%%' Utilization of source NAT pool reaches the alarm clear threshold. Error: An error occurred error

RT_SRC_NAT_ALARM_RAISE
System Log Message Description Type Severity

Utilization of source nat pool 'nat-pool-name' hits raise threshold 'threshold%%' Utilization of source NAT pool reaches the alarm raise threshold. Error: An error occurred error

RT_SOURCE_NAT_ALARM_CLEAR

587

JUNOS 10.1 System Log Messages Reference

588

RT_SRC_NAT_ALARM_RAISE

Chapter 74

RTLOG System Log Messages

This chapter describes messages with the RTLOG prefix. They are generated on routers running the JUNOS Software with enhanced services by the system log module of the Packet Forwarding Engine as it processes packets for security control in real time.

RTLOG_SOURCE_INIT
System Log Message Description Type Severity

Log source service-name attached at log ring buffer index Specified JSR log source is ready to export logs Event: This message reports an event, not an error info

RTLOG_UTP_TCP_SYN_FLOOD
System Log Message

source: source-address-source-port, destination: destination-address-destination-port, zone name: filter-name, interface name: interface-name Security LOG UTP fake TCP SYN flood attack. Event: This message reports an event, not an error error

Description Type Severity

RTLOG_SOURCE_INIT

589

JUNOS 10.1 System Log Messages Reference

590

RTLOG_UTP_TCP_SYN_FLOOD

Chapter 75

RTLOGD System Log Messages

This chapter describes messages with the RTLOGD prefix. They are generated by the system log utility for real-time processing of packets for security control (rtlogd) on routers running the JUNOS Software with enhanced services.

RTLOGD_LOG_BIND_ERROR
System Log Message Description

Failed to bind socket to PFE: error-message JUNOS JSR log daemon receives JSR log from a JSR log forwarder. The JSR log daemon failed to connect to the forwarder. Error: An error occurred error

Type Severity

RTLOGD_LOG_READ_ERROR
System Log Message Description

Failed to read from PFE: error-message 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. Error: An error occurred error

Type Severity

RTLOGD_LOG_BIND_ERROR

591

JUNOS 10.1 System Log Messages Reference

592

RTLOGD_LOG_READ_ERROR

Chapter 76

RTPERF System Log Messages

This chapter describes messages with the RTPERF prefix. They are related to performance logs for the data plane.

RTPERF_CPU_THRESHOLD_EXCEEDED
System Log Message Description Type Severity

PIC pic-slot CPU utilization exceeds threshold, current value=current-value PFE cpu threshold exceeded Event: This message reports an event, not an error critical

RTPERF_CPU_USAGE_OK
System Log Message Description Type Severity

PIC pic-slot CPU utilization returns to normal, current value=current-value PFE cpu usage okay Event: This message reports an event, not an error info

RTPERF_CPU_THRESHOLD_EXCEEDED

593

JUNOS 10.1 System Log Messages Reference

594

RTPERF_CPU_USAGE_OK

Chapter 77

SAVAL System Log Messages

This chapter describes messages with the SAVAL prefix. They are generated by the MAC SA Validate system (jsavald) process.

SAVAL_RTSOCK_FAILURE
System Log Message Description

Error with rtsock: error-message The MAC SA Validate system process (jsavald) experienced the indicated error with a routing socket. Error: An error occurred info An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SAVAL_RTSOCK_FAILURE

595

JUNOS 10.1 System Log Messages Reference

596

SAVAL_RTSOCK_FAILURE

Chapter 78

SDXD System Log Messages

This chapter describes messages with the SDX prefix. They are generated by the Session and Resource Control (SRC) process (sdxd), which provides a user interface for deploying Internet services.

SDXD_BEEP_FIN_FAIL
System Log Message Description

Graceful close of BEEP session failed The Session and Resource Control (SRC) process (sdxd) could not send a request to the SRC server to close a Blocks Extensible Exchange Protocol (BEEP) session. It sends this request when the session becomes unconfigured. Event: This message reports an event, not an error notice The usual cause is that the session was already partially or completely closed. None required. The sdxd process recovers automatically in this situation.

Type Severity Cause Action

SDXD_BEEP_INIT_FAIL
System Log Message Description

BEEP initialization failed The Session and Resource Control (SRC) process (sdxd) could not initialize the Blocks Extensible Exchange Protocol (BEEP), which it uses to connect to an SRC server. Error: An error occurred error An internal software failure might have occurred.

Type Severity Cause

SDXD_CHANNEL_START_FAIL
System Log Message

Notification channel could not be started (error-code): message

SDXD_BEEP_FIN_FAIL

597

JUNOS 10.1 System Log Messages Reference

Description

The indicated Blocks Extensible Exchange Protocol (BEEP) channel could not be started for the indicated reason. Event: This message reports an event, not an error error The usual cause is an abnormal operation, which might be described in the system log message.

Type Severity Cause

SDXD_CONNECT_FAIL
System Log Message Description

Connection to SDX server failed: message The Session and Resource Control (SRC) process (sdxd) could not connect to an SRC server for the indicated reason. Event: This message reports an event, not an error notice There was a network problem or the server was not running.

Type Severity Cause

SDXD_DAEMONIZE_FAIL
System Log Message Description

Aborting, unable to run in the background as a daemon: error-message The Service Deployment System process (sdxd) could not create a version of itself to run in the background as a daemon. Error: An error occurred emergency

Type Severity

SDXD_EVLIB_FAILURE
System Log Message Description

function-name: error-message The Service Deployment System process (sdxd) called the indicated function in the event library. The function failed with the indicated error. Error: An error occurred error An internal software failure occurred.

Type Severity Cause

598

SDXD_CHANNEL_START_FAIL

Chapter 78: SDXD System Log Messages

SDXD_KEEPALIVES_MISSED
System Log Message Description

No server keepalives received for three intervals The Session and Resource Control (SRC) process (sdxd) and SRC server exchange keepalive messages at regular intervals. The process did not receive a keepalive from the server for three consecutive keepalive intervals. In this case, it closes the session and tries to connect to another SRC server. Event: This message reports an event, not an error notice

Type Severity

SDXD_KEEPALIVE_SEND_FAIL
System Log Message Description

Unable to send keepalive The Session and Resource Control (SRC) process (sdxd) could not send a keepalive message to the SRC server, which it does periodically to maintain its connection to the server. Event: This message reports an event, not an error notice There might have been a network problem.

Type Severity Cause

SDXD_MGMT_SOCKET_IO
System Log Message Description

management daemon I/O failure: reason The Service Deployment System process (sdxd) could not read from or write to the management socket that it uses to communicate with the JUNOS management process (mgd). Error: An error occurred error The mgd process might have exited abnormally.

Type Severity Cause

SDXD_OUT_OF_MEMORY
System Log Message Description

Insufficient memory during operation The Service Deployment System (sdxd) attempted to allocate memory for an internal object during the indicated operation. The attempt failed.

SDXD_KEEPALIVES_MISSED

599

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

SDXD_PID_FILE_UPDATE
System Log Message Description

Unable to update process PID file: error-message The Service Deployment System process (sdxd) attempted to update the file that records its process ID (PID), which serves to prevent multiple instances of sdxd from running simultaneously. The attempt failed. Error: An error occurred error

Type Severity

SDXD_SOCKET_FAILURE
System Log Message Description

operation failed: error-message The Service Deployment System process (sdxd) uses Transmission Control Protocol (TCP) sockets for communication with the SRC server. The indicated operation, which might be for socket creation or binding to a local address, failed with the indicated error. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

600

SDXD_OUT_OF_MEMORY

Chapter 79

SMTPD System Log Messages

This chapter describes messages with the SMTPD prefix. They are generated by smtp client process (smtpd).

SMTPD_DROP_MAIL_PAYLOAD
System Log Message Description

Dropped mail to user:error-message. Send failed or queued reached max The smtp client process (smtpd) attempted to send the mail payload to the configured gateway mail server failed due to one of the following reasons: network connection failure, error in the payload, or sent failed after retries. The mail is dropped. Event: This message reports an event, not an error error

Type Severity

SMTPD_NO_CONFIGURED_SERVER
System Log Message Description

Unable to send mail to error-message. Configure server with relay The smtp client process (smtpd) is unable to send mail payload. A gateway server must be configured. This server must allow relaying. Event: This message reports an event, not an error error

Type Severity

SMTPD_DROP_MAIL_PAYLOAD

601

JUNOS 10.1 System Log Messages Reference

602

SMTPD_NO_CONFIGURED_SERVER

Chapter 80

SNMP System Log Messages

This chapter describes messages with the SNMP prefix. They are generated by two kinds of processes:

Processes that perform SNMP operations, such as the MIB II process (mib2d) and the SNMP agent process (snmpd). Those processes also generate messages with prefixes that match their names, as described in MIB2D System Log Messages on page 373 and SNMPD System Log Messages on page 513. Processes that are instrumented to generate system log messages when they send SNMP traps. The SNMP remote operations process (rmopd) is one such process. It also generates messages with the RMOPD_ prefix, which are described in RMOPD System Log Messages on page 419.

SNMP_GET_ERROR1
System Log Message Description

function-name operation failed for object-name: index1 index1 (error-message) An SNMP Get or GetNext request failed for the indicated object, which has the indicated index. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMP_GET_ERROR2
System Log Message

function-name operation failed for object-name: index1 index1 index2 index2 (error-message) An SNMP Get or GetNext request failed for the indicated object, which has the indicated indexes. Error: An error occurred

Description

Type

SNMP_GET_ERROR1

603

JUNOS 10.1 System Log Messages Reference

Severity Cause Action

error An internal software failure occurred. Contact your technical support representative.

SNMP_GET_ERROR3
System Log Message

function-name operation failed for object-name: index1 index1 index2 index2 index3 index3 (error-message) An SNMP Get or GetNext request failed for the indicated object, which has the indicated indexes. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Description

Type Severity Cause Action

SNMP_GET_ERROR4
System Log Message

function-name operation failed for object-name: index1 index1 index2 index2 index3 index3 index4 index4 (error-message) An SNMP Get or GetNext request failed for the indicated object, which has the indicated indexes. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Description

Type Severity Cause Action

SNMP_RTSLIB_FAILURE
System Log Message Description

function-name: reason: error-message A call to the indicated function in the routing socket library failed with the indicated error. Error: An error occurred

Type

604

SNMP_GET_ERROR2

Chapter 80: SNMP System Log Messages

Severity Cause Action

emergency An internal software failure occurred. Contact your technical support representative.

SNMP_TRAP_LINK_DOWN
System Log Message

ifIndex snmp-interface-index, ifAdminStatus admin-status, ifOperStatus operational-status, ifName interface-name The SNMP agent process (snmpd) generated a linkDown trap because the indicated interface changed state to 'down'. Event: This message reports an event, not an error warning

Description

Type Severity

SNMP_TRAP_LINK_UP
System Log Message

ifIndex snmp-interface-index, ifAdminStatus admin-status, ifOperStatus operational-status, ifName interface-name The SNMP agent process (snmpd) generated a linkUp trap because the indicated interface changed state to 'up'. Event: This message reports an event, not an error info

Description

Type Severity

SNMP_TRAP_TRACERT_PATH_CHANGE
System Log Message Description

traceRouteCtlOwnerIndex = test-owner, traceRouteCtlTestName = test-name The Simple Network Management Protocol (SNMP) remote operations process (rmopd) generated a traceRoutePathChange trap because two probes with the same time-to-live (TTL) value returned with different IP addresses. Event: This message reports an event, not an error info

Type Severity

SNMP_TRAP_TRACERT_TEST_COMPLETED
System Log Message

traceRouteCtlOwnerIndex = test-owner, traceRouteCtlTestName = test-name

SNMP_RTSLIB_FAILURE

605

JUNOS 10.1 System Log Messages Reference

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. Event: This message reports an event, not an error info

Type Severity

SNMP_TRAP_TRACERT_TEST_FAILED
System Log Message Description

traceRouteCtlOwnerIndex = test-owner, traceRouteCtlTestName = test-name 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. Event: This message reports an event, not an error info

Type Severity

606

SNMP_TRAP_TRACERT_TEST_COMPLETED

Chapter 81

SNMPD System Log Messages

This chapter describes messages with the SNMPD prefix. They are generated by the Simple Network Management Protocol (SNMP) agent process (snmpd), which responds to SNMP requests. As necessary, it passes the requests to subagent processes running on its machine and forwards the traps they generate to the SNMP manager.

SNMPD_AUTH_FAILURE
System Log Message Description

function-name: message from source-address to destination-address (index1) The indicated function failed because the authorization check failed for the interface, Simple Network Management Protocol (SNMP) community, or user making the request. Error: An error occurred notice An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_AUTH_PRIVILEGES_EXCEEDED
System Log Message Description

function-name: source-address: request exceeded community privileges The indicated function failed because the Simple Network Management Protocol (SNMP) community making the access request did not have the required privileges. Error: An error occurred notice An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_AUTH_FAILURE

607

JUNOS 10.1 System Log Messages Reference

SNMPD_AUTH_RESTRICTED_ADDRESS
System Log Message Description

function-name: request from address source-address not allowed The indicated function failed because access requests from the indicated source address are not allowed. Error: An error occurred notice An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_AUTH_WRONG_PDU_TYPE
System Log Message Description

function-name: source-address: unauthorized SNMP PDU type: pdu-type The indicated function failed because the indicated type of protocol data unit (PDU) is not supported. Error: An error occurred notice An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_BIND_INFO
System Log Message Description

Source address for trap socket was set to bind-address The source address for the indicated type of socket used by the Simple Network Management Protocol (SNMP) agent process (snmpd) was set to the indicated address. Event: This message reports an event, not an error info An administrator changed the JUNOS configuration for the process or for an interface. The online/offline state changed for a Physical Interface Card (PIC). This can also cause the address to become newly available or unavailable.

Type Severity Cause Cause

608

SNMPD_AUTH_RESTRICTED_ADDRESS

Chapter 81: SNMPD System Log Messages

SNMPD_CONFIG_ERROR
System Log Message Description

Configuration database has errors The Simple Network Management Protocol (SNMP) agent process (snmpd) detected an error in the SNMP configuration database. Error: An error occurred error

Type Severity

SNMPD_CONTEXT_ERROR
System Log Message Description

function-name: error in operation context context-name The indicated operation (addition or deletion) failed during configuration of the indicated Simple Network Management Protocol (SNMP) context. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_FILE_FAILURE
System Log Message Description

function-name: fopen filename: error-message The Simple Network Management Protocol (SNMP) agent process (snmpd) could not access the indicated file. Error: An error occurred emergency An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_GROUP_ERROR
System Log Message

function-name: error in operation group: 'group-id' user 'username' model 'model'

SNMPD_CONFIG_ERROR

609

JUNOS 10.1 System Log Messages Reference

Description

The indicated operation (creation, installation, or deletion) failed during configuration of the indicated group. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_HEALTH_MON_THRESH_CROSS
System Log Message Description

syslog-subtagdelimiterevent-name A system parameter monitored by the self-monitoring feature crossed a rising or falling threshold. Event: This message reports an event, not an error error System resources were being consumed.

Type Severity Cause

SNMPD_INIT_FAILED
System Log Message Description

snmpd initialization failure: error-message Initialization of the Simple Network Management Protocol (SNMP) agent process (snmpd) failed. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_LIBJUNIPER_FAILURE
System Log Message Description

function-name: system_default_inaddr: error-message 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).

610

SNMPD_GROUP_ERROR

Chapter 81: SNMPD System Log Messages

Type Severity Cause Action

Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

SNMPD_RADIX_FAILURE
System Log Message Description

function-name: radix_add failed: error-message The Simple Network Management Protocol (SNMP) agent process (snmpd) uses radix trees to store valid client prefixes, which are used to determine authorization for requests from users and communities. It could not create a new entry in a radix tree. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_RECEIVE_FAILURE
System Log Message Description

function-name: receive message failure: error-message The indicated error occurred while the Simple Network Management Protocol (SNMP) agent process (snmpd) was receiving either a protocol data unit (PDU) from the User Datagram Protocol (UDP) or a message from a subagent. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_RMONFILE_FAILURE
System Log Message Description Type

function-name: operation: operation filename: error-message The indicated operation failed on the indicated remote monitoring (RMON) data file. Error: An error occurred

SNMPD_LIBJUNIPER_FAILURE

611

JUNOS 10.1 System Log Messages Reference

Severity Cause Action

critical An internal software failure occurred. Contact your technical support representative.

SNMPD_RMON_COOKIE
System Log Message Description

function-name: Null cookie An invalid data pointer was returned when the remote monitoring (RMON) asynchronous completion handler performed an RMON alarm operation. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_RMON_EVENTLOG
System Log Message Description Type Severity

syslog-subtagdelimitermessage The indicated remote monitoring (RMON) event completed. Event: This message reports an event, not an error warning

SNMPD_RMON_MIBERROR
System Log Message

function-name: internal Get request error: description, alarm alarm-id, error error-message, variable: name (oid) A Get request for a monitored object instance failed during initialization of the indicated remote monitoring (RMON) alarm. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Description

Type Severity Cause Action

612

SNMPD_RMONFILE_FAILURE

Chapter 81: SNMPD System Log Messages

SNMPD_RTSLIB_ASYNC_EVENT
System Log Message Description

function-name: sequence mismatch (expected-value, received-value), resyncing A notification from the kernel to the Simple Network Management Protocol (SNMP) agent process (snmpd) was lost. Event: This message reports an event, not an error notice

Type Severity

SNMPD_SEND_FAILURE
System Log Message Description

function-name: send type (index1) failure: error-message The Simple Network Management Protocol (SNMP) agent process (snmpd) could not send either a protocol data unit (PDU) to the User Datagram Protocol (UDP) or a message to a subagent. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_SET_FAILED
System Log Message Description

Snmp set failed: error-message Configuration data was changed using an Simple Network Management Protocol (SNMP) Set request, but the SNMP agent process (snmpd) could not save the changes to the configuration database. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_SMOID_GEN_FAILURE
System Log Message

Unable to generate OID from product-name (error-message)

SNMPD_RTSLIB_ASYNC_EVENT

613

JUNOS 10.1 System Log Messages Reference

Description

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. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_SOCKET_FAILURE
System Log Message Description

function-name: socket failure: reason (error-message) The Simple Network Management Protocol (SNMP) agent process (snmpd) uses sockets for communication with subagents. A socket operation, such as creation or removal, failed. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_SOCKET_FATAL_FAILURE
System Log Message Description

function-name: socket failure: reason (error-message) The Simple Network Management Protocol (SNMP) agent process (snmpd) uses sockets for communication with subagents. The process exited after a socket operation, such as creation or removal, failed. Error: An error occurred emergency An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_SYSLIB_FAILURE
System Log Message

function-name: system function 'system-function-name' failed: error-message

614

SNMPD_SMOID_GEN_FAILURE

Chapter 81: SNMPD System Log Messages

Description

The indicated function from the Simple Network Management Protocol (SNMP) system library failed and returned the indicated error to the SNMP agent process (snmpd). Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_SYSOID_FAILURE
System Log Message Description

Unable to determine sysObjectID from internal model: model The Simple Network Management Protocol (SNMP) agent process (snmpd) could not determine the value of the sysObjectID object. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_SYSOID_GEN_FAILURE
System Log Message Description

Unable to generate OID for product product-name (error-message) The Simple Network Management Protocol (SNMP) agent process (snmpd) could not generate a value for the sysObjectID object for the indicated product. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_THROTTLE_QUEUE_DRAINED
System Log Message Description

function-name: cleared all throttled traps The queue of throttled traps was cleared.

SNMPD_SYSLIB_FAILURE

615

JUNOS 10.1 System Log Messages Reference

Type Severity

Event: This message reports an event, not an error info

SNMPD_TRAP_COLD_START
System Log Message Description

function-name: SNMP trap: cold start The Simple Network Management Protocol (SNMP) agent process (snmpd) generated a cold-start trap when the entire Routing Engine (including the snmpd process) initialized. Event: This message reports an event, not an error critical

Type Severity

SNMPD_TRAP_GEN_FAILURE
System Log Message Description

function-name: SNMP trap error: trap-message (error-message) The Simple Network Management Protocol (SNMP) agent process (snmpd) could not generate a trap. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

SNMPD_TRAP_INVALID_DATA
System Log Message Description

function-name: SNMP trap error: invalid message (value) received The Simple Network Management Protocol (SNMP) agent process (snmpd) received a trap message from a subagent that contained an invalid variable binding (varbind) type. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

616

SNMPD_THROTTLE_QUEUE_DRAINED

Chapter 81: SNMPD System Log Messages

SNMPD_TRAP_QUEUED
System Log Message Description Type Severity Cause

Adding trap to trap-destination to queue-name queue, size traps in queue A trap was queued for later transmission. Event: This message reports an event, not an error info Possible causes include the following: (a) the system is not completely initialized, (b) a route does not exist, or (c) traps are being throttled.

SNMPD_TRAP_QUEUE_DRAINED
System Log Message Description Type Severity

function-name: traps queued to trap-destination sent successfully The queued traps for the indicated destination were successfully sent. Event: This message reports an event, not an error info

SNMPD_TRAP_QUEUE_MAX_ATTEMPTS
System Log Message

function-name: after count attempts, deleting trap-count traps queued to trap-destination The number of attempts to send traps to the indicated destination exceeded the configured maximum. The traps still waiting to be sent were discarded. Error: An error occurred error Contact your technical support representative.

Description

Type Severity Action

SNMPD_TRAP_QUEUE_MAX_SIZE
System Log Message

function-name: maximum queue size exceeded (size), discarding trap to trap-destination from queue-name queue The number of traps in the trap queue exceeded the configured maximum. The traps still waiting to be sent were discarded. Event: This message reports an event, not an error

Description

Type

SNMPD_TRAP_QUEUED

617

JUNOS 10.1 System Log Messages Reference

Severity

info

SNMPD_TRAP_THROTTLED
System Log Message Description

function-name: traps throttled after count traps The number of traps waiting for transmission exceeded the configured maximum, so the remaining traps were throttled. Event: This message reports an event, not an error info

Type Severity

SNMPD_TRAP_WARM_START
System Log Message Description

function-name: SNMP trap: warm start The Simple Network Management Protocol (SNMP) agent process (snmpd) generated a warm-start trap when it initialized (other Routing Engine processes were already active). Event: This message reports an event, not an error error

Type Severity

SNMPD_USER_ERROR
System Log Message

function-name: error in action user 'username' auth 'authentication-type' priv 'privilege-type' The indicated operation (creation, installation, or deletion) failed during configuration of the indicated user. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Description

Type Severity Cause Action

618

SNMPD_TRAP_QUEUE_MAX_SIZE

Chapter 82

SPD System Log Messages

This chapter describes messages with the SPD prefix. They are generated by the adaptive services process (spd), which provides the user interface for management and configuration of Adaptive Services Physical Interface Cards (PICs).

SPD_CONFIGURATION_COMPILE
System Log Message Description

Compilation of configuration rule rule-name term index failed: reason The adaptive services process (spd) could not compile a configured object, such as a rule or rule term. Error: An error occurred error

Type Severity

SPD_CONN_FATAL_FAILURE
System Log Message Description

Connection attempt failed with fatal error: error-message The adaptive services process (spd) attempted to open a connection to an Adaptive Services Physical Interface Card (PIC), to gather information requested in a Simple Network Management Protocol (SNMP) query. The attempt failed with the indicated fatal error. Error: An error occurred error

Type Severity

SPD_CONN_NO_REPLY
System Log Message Description

function-name: no reply from interface-name (error-message) The adaptive services process (spd) did not receive a reply from the indicated interface on an Adaptive Services Physical Interface Card (PIC) for information requested in a Simple Network Management Protocol (SNMP) query. Error: An error occurred

Type

SPD_CONFIGURATION_COMPILE

619

JUNOS 10.1 System Log Messages Reference

Severity

error

SPD_CONN_OPEN_FAILURE
System Log Message Description

function-name: unable to open connection to interface-name (error-message) The adaptive services process (spd) attempted to open a connection to the indicated interface on an Adaptive Services Physical Interface Card (PIC), to gather information requested in a Simple Network Management Protocol (SNMP) query. The attempt failed for the indicated reason. Error: An error occurred error

Type Severity

SPD_CONN_SEND_FAILURE
System Log Message Description

function-name: unable to send query to interface-name (error-message) The adaptive services process (spd) attempted to send a request for information, needed for a Simple Network Management Protocol (SNMP) query, to the indicated interface on an Adaptive Services Physical Interface Card (PIC). The attempt failed for the indicated reason. Error: An error occurred error

Type Severity

SPD_CONN_UNEXPECTED_MSG
System Log Message Description

function-name: unexpected response received from interface-name (error-message) The adaptive services process (spd) sent a request for information, needed for a Simple Network Management Protocol (SNMP) query, to the indicated interface on an Adaptive Services Physical Interface Card (PIC). It received an unexpected response. Error: An error occurred error

Type Severity

SPD_DAEMONIZE_FAILED
System Log Message Description

Aborting, unable to run in the background as a daemon: error-message The adaptive services process (spd) could not create a version of itself to run in the background as a daemon. Error: An error occurred

Type

620

SPD_CONN_NO_REPLY

Chapter 82: SPD System Log Messages

Severity

emergency

SPD_DB_IF_ADD_FAILURE
System Log Message Description

Unable to add database entry for interface-name: error-message 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 add an entry to the database for the indicated interface on an Adaptive Services Physical Interface Card (PIC). Error: An error occurred error

Type Severity

SPD_DB_IF_ALLOC_FAILURE
System Log Message Description

Unable to allocate database entry for interface-name: error-message 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 interface on an Adaptive Services Physical Interface Card (PIC). Error: An error occurred error

Type Severity

SPD_DB_SVC_SET_ADD_FAILURE
System Log Message Description

Unable to add database entry for service-set: error-message 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 add an entry to the database for the indicated service set. Error: An error occurred error

Type Severity

SPD_DB_SVC_SET_ALLOC_FAILURE
System Log Message Description

Unable to allocate database entry for service-set: error-message 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.

SPD_DAEMONIZE_FAILED

621

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

SPD_DUPLICATE
System Log Message Description

Another copy of this program is running An attempt to start the adaptive services process (spd) failed because an instance of the process was already running. Error: An error occurred error

Type Severity

SPD_EVLIB_CREATE_FAILURE
System Log Message Description

evCreate failed with: error-message The adaptive services process (spd) could not create a context used for handling all asynchronous events (such as timers and message availability). Error: An error occurred emergency

Type Severity

SPD_EVLIB_EXIT_FAILURE
System Log Message Description

evMainLoop return value: return-value, error: error-message The adaptive services process (spd) returned from an event loop, which it should never do. Error: An error occurred error

Type Severity

SPD_NOT_ROOT
System Log Message Description

Must be run as root The user who attempted to start the adaptive services process (spd) was not the root user. Error: An error occurred error

Type Severity

622

SPD_DB_SVC_SET_ALLOC_FAILURE

Chapter 82: SPD System Log Messages

SPD_OUT_OF_MEMORY
System Log Message Description

Insufficient memory for operation operation The adaptive services process (spd) attempted to allocate memory for an internal object. The attempt failed. Error: An error occurred error

Type Severity

SPD_PID_FILE_LOCK
System Log Message Description

Unable to lock PID file: error-message The adaptive services process (spd) attempted to lock the file that records its process ID (PID), which serves to prevent multiple instances of spd from running simultaneously. The attempt failed. Error: An error occurred error

Type Severity

SPD_PID_FILE_UPDATE
System Log Message Description

Unable to update process PID file: error-message The adaptive services process (spd) attempted to update the file that records its process ID (PID), which serves to prevent multiple instances of spd from running simultaneously. The attempt failed. Error: An error occurred error

Type Severity

SPD_SERVICE_NEXT_HOP_ADD_FAILED
System Log Message Description

Unable to add service next hop: error-message (error-code) The adaptive services process (spd) could not add a service next hop for the indicated reason. Error: An error occurred error

Type Severity

SPD_OUT_OF_MEMORY

623

JUNOS 10.1 System Log Messages Reference

SPD_SERVICE_NEXT_HOP_DEL_FAILED
System Log Message Description

Unable to delete service next hop: error-message (error-code) The adaptive services process (spd) could not delete a service next hop for the indicated reason. Error: An error occurred error

Type Severity

SPD_TRAP_OID_GEN_FAILED
System Log Message Description

Unable to generate OID for identifier (error-message) The adaptive services process (spd) could not generate the indicated object identifier (OID) for a Simple Network Management Protocol (SNMP) trap notification. Error: An error occurred error

Type Severity

SPD_TRAP_REQUEST_FAILURE
System Log Message Description

function-name: type request failed: error-message The adaptive services process (spd) made the indicated type of request to the application programming interface (API) for generating Simple Network Management Protocol (SNMP) traps, but did not receive the expected result. Error: An error occurred error

Type Severity

SPD_USAGE
System Log Message Description

Usage: spd [-N] [-v] [-d debug-level] The adaptive services process (spd) displayed the syntax statement for the 'spd' command because the command was invoked incorrectly. Event: This message reports an event, not an error error

Type Severity

624

SPD_SERVICE_NEXT_HOP_DEL_FAILED

Chapter 83

TASK System Log Messages

This chapter describes messages with the TASK prefix.

TASK_ABORT
System Log Message Description Type Severity Action

abort executable-name[pid] version version built by builder on date: error-message The control protocol process terminated because of an internal error. Error: An error occurred error Examine the messages that immediately follow this message in the system log for information about possible causes. An internal software failure occurred.

Cause

TASK_ACTIVE_TERMINATE
System Log Message Description

Exiting with active tasks: task-name After receiving multiple termination requests, the control protocol process exited without performing the indicated cleanup tasks. Event: This message reports an event, not an error notice

Type Severity

TASK_ASSERT
System Log Message

Assertion failed executable-name[pid]: file "source-filename", line line-number: "message" The source code for this process includes internal self-consistency checks. The process terminated because a check failed, creating a diagnostic core dump for analysis by technical support personnel and noting the number of the line in the source file where the check failed.

Description

TASK_ABORT

625

JUNOS 10.1 System Log Messages Reference

Type Severity Cause Action

Error: An error occurred error An internal software failure occurred. Examine the messages that immediately follow this message in the system log for information about possible causes. Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core dump, if requested.

TASK_ASSERT_SOFT
System Log Message

Soft assertion failed executable-name[pid]: file "source-filename", line line-number: "message", daemon continued running The source code for the process includes internal self-consistency checks. A check failed but the process continued running. It created a diagnostic core dump for analysis by technical support personnel and noted the number of the line in the source file where the check failed. Error: An error occurred error An internal software failure occurred. Examine the messages that immediately follow this message in the system log for information about possible causes. Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core dump, if requested.

Description

Type Severity Cause Action

TASK_EXIT
System Log Message Description Type Severity Cause

Exit executable-name[pid] version version built by builder on date, caller address The process exited, either in response to a user request or because of a system error. Event: This message reports an event, not an error notice A system resource was unavailable, an unexpected error occurred, or a user terminated the process. Examine the messages that immediately follow this message in the system log for information about possible causes.

Action

626

TASK_ASSERT

Chapter 83: TASK System Log Messages

TASK_LOCK_FLOCKED
System Log Message Description

Unable to obtain a lock on filename, is another copy of the process running? The process could not obtain the mutual exclusion lock that prevents more than one instance from running simultaneously. The system terminated the indicated process. Error: An error occurred error Another process is running. Use the 'show system process' command to verify that another process is running.

Type Severity Cause Action

TASK_LOCK_LOCKED
System Log Message Description

Unable to obtain a lock on filename, program-name[pid] is still running The process could not obtain the mutual exclusion lock that prevents more than one instance from running simultaneously. The system terminated this instance. Error: An error occurred error Another process is running. Use the 'show system process' command to verify that another process is running.

Type Severity Cause Action

TASK_MGMT_TIMEOUT
System Log Message Description Type Severity Action

peer peer-name timed out waiting for input Daemon timed out waiting for management input. Error: An error occurred warning Examine the messages that immediately follow this message in the system log for information about possible causes. An internal software failure occurred.

Cause

TASK_LOCK_FLOCKED

627

JUNOS 10.1 System Log Messages Reference

TASK_OS_MEMHIGH
System Log Message Description

Using size KB of memory, percentage-value percent of available The process is using the indicated amount and percentage of Routing Engine memory, which is considered excessive. Error: An error occurred error Either the process is leaking memory or the use of system resources is excessive. Increase the amount of RAM in the Routing Engine.

Type Severity Cause Action

TASK_SCHED_CALLBACK_LONGRUNTIME
System Log Message Description

function-name: excessive runtime time during action of module The indicated submodule of this process ran uninterrupted for the indicated period of time, which is considered excessive. Event: This message reports an event, not an error warning The duration was noted because task accounting is enabled. The function might be implemented inefficiently.

Type Severity Cause

TASK_SCHED_CUMULATIVE_RUNTIME
System Log Message

function-name: excessive runtime (total of time in count callbacks) after action of module Several submodules of this process ran uninterrupted for the indicated period of time, which is considered excessive. Event: This message reports an event, not an error warning The duration was noted because task accounting is enabled. The function might be implemented inefficiently.

Description

Type Severity Cause

628

TASK_OS_MEMHIGH

Chapter 83: TASK System Log Messages

TASK_SCHED_MODULE_LONGRUNTIME
System Log Message Description

function-name: excessive runtime time during action of module Several submodules of this process ran uninterrupted for the indicated period of time, which is considered excessive. Event: This message reports an event, not an error warning The duration was noted because task accounting is enabled. The function might be implemented inefficiently.

Type Severity Cause

TASK_SCHED_TASK_LONGRUNTIME
System Log Message Description

function-name ran for total-time (user-time user, system-time system) doing action A task callback within this process ran uninterrupted for the indicated period of time, which is considered excessive. Event: This message reports an event, not an error warning The duration was noted because task accounting is enabled. The function might be implemented inefficiently.

Type Severity Cause

TASK_SIGNAL_TERMINATE
System Log Message Description

signal-name termination signal received In response to the indicated termination request, the process terminated and shut down. Event: This message reports an event, not an error notice

Type Severity

TASK_START
System Log Message Description Type

Start executable-name[pid] version version built date Process started. Event: This message reports an event, not an error

TASK_SCHED_MODULE_LONGRUNTIME

629

JUNOS 10.1 System Log Messages Reference

Severity

info

TASK_SYSTEM
System Log Message Description Type Severity Cause

reason: error-message A system call made by this process failed. Error: An error occurred error It is possible that the kernel lacked the resources to fulfill the request.

TASK_TASK_BEGIN
System Log Message

Commencing virtual chassis control daemon, version process-version, built date by builder The process started. Event: This message reports an event, not an error notice

Description Type Severity

TASK_TASK_CHILDKILLED
System Log Message Description

task-name terminated by SIGsignal-namecore-dump-status While a child process was performing the indicated operation, it terminated in response to the indicated signal. Event: This message reports an event, not an error error

Type Severity

TASK_TASK_CHILDSTOPPED
System Log Message Description

task-name stopped by SIGsignal-name While a child process was performing the indicated operation, it stopped in response to the indicated signal. Event: This message reports an event, not an error error

Type Severity

630

TASK_START

Chapter 83: TASK System Log Messages

TASK_TASK_FORK
System Log Message Description Type Severity

Unable to fork task-name: error-message This process failed to create the indicated child process. Error: An error occurred error

TASK_TASK_GETWD
System Log Message Description Type Severity Cause

getwd: error-message The getwd() system call failed. Error: An error occurred error It is possible that the kernel lacked the resources to fulfill the request.

TASK_TASK_NOREINIT
System Log Message Description

Reinitialization not possible This process (VCCPD) failed to reinitialize as requested, because it was running in a state that did not allow reconfiguration. Error: An error occurred error

Type Severity

TASK_TASK_PIDCLOSED
System Log Message Description

Unable to close and remove filename: error-message This process tried to close and remove the file that records its process ID (PID), which serves to prevent multiple instances from running simultaneously. The attempt failed. Error: An error occurred error

Type Severity

TASK_TASK_FORK

631

JUNOS 10.1 System Log Messages Reference

TASK_TASK_PIDFLOCK
System Log Message Description

flock(filename, LOCK_EX): error-message This process issued the flock() system call on the file that records its process ID (PID), which serves to prevent multiple instances from running simultaneously. The system call failed. Error: An error occurred error

Type Severity

TASK_TASK_PIDWRITE
System Log Message Description

Unable to write filename: error-message 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. Error: An error occurred error

Type Severity

TASK_TASK_REINIT
System Log Message Description Type Severity

Reinitializing This process reinitialized. Event: This message reports an event, not an error info

TASK_TASK_SIGNALIGNORE
System Log Message Description

sigaction(SIGsignal-name): error-message This process informed the kernel that it wished to ignore the indicated signal, but the kernel failed to process the request. Error: An error occurred error

Type Severity

632

TASK_TASK_PIDFLOCK

Chapter 83: TASK System Log Messages

TASK_TRACE_FAILED
System Log Message Description

Unable to write to trace file filename 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. Event: This message reports an event, not an error error

Type Severity

TASK_TRACE_FAILED

633

JUNOS 10.1 System Log Messages Reference

634

TASK_TRACE_FAILED

Chapter 84

TFTPD System Log Messages

This chapter describes messages with the TFTPD prefix. They are generated by the Trivial FTP (TFTP) process (tnp.tftpd), which services requests from hardware components for the configuration files that they use during initialization.

TFTPD_AF_ERR
System Log Message Description

Unexpected address family address-family-type As each hardware component on the routing platform initializes, it requests its configuration file from the TFTP process (tnp.tftpd). The tnp.tftpd process exited because an incoming packet had the indicated, unexpected value in its address family (sockaddr) field. Error: An error occurred error

Type Severity

TFTPD_BIND_ERR
System Log Message Description Type Severity

bind: error-message Binding of a socket to an address failed due to a system error. Error: An error occurred error

TFTPD_CONNECT_ERR
System Log Message Description Type Severity

connect: error-message Connection of a socket to an address failed due to a system error. Error: An error occurred error

TFTPD_AF_ERR

635

JUNOS 10.1 System Log Messages Reference

TFTPD_CONNECT_INFO
System Log Message Description

TFTP operation from address address port port file filename As each hardware component on the routing platform initializes, it requests its configuration file from the TFTP process (tnp.tftpd). The process established a connection with the indicated characteristics: kind of operation (read or write), address and port connected to, and name of file transferred. Event: This message reports an event, not an error info

Type Severity

TFTPD_CREATE_ERR
System Log Message Description Type Severity Cause

check_space error-message The TFTP process (tnp.tftpd) could not create a core dump file. Error: An error occurred error There is probably not enough free space in the file system where tnp.tftpd tried to create the file.

TFTPD_FIO_ERR
System Log Message Description Type Severity

ioctl(FIONBIO): error-message The TFTP process (tnp.tftpd) could not set the standard input to be nonblocking. Error: An error occurred error

TFTPD_FORK_ERR
System Log Message Description

fork: error-message As each hardware component on the routing platform initializes, it requests its configuration file from the 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. Error: An error occurred

Type

636

TFTPD_CONNECT_INFO

Chapter 84: TFTPD System Log Messages

Severity

error

TFTPD_NAK_ERR
System Log Message Description

nak error error-code, error-message The TFTP process (tnp.tftpd) sent a negative acknowledgment to a client because of the indicated error condition. Error: An error occurred warning

Type Severity

TFTPD_OPEN_ERR
System Log Message Description

Unable to open file 'filename', error: error-message The TFTP process (tnp.tftpd) could not open the indicated file because of the indicated error. Error: An error occurred warning

Type Severity

TFTPD_RECVCOMPLETE_INFO
System Log Message Description

Received count blocks of block-size size for file 'filename' The TFTP process (tnp.tftpd) received the last portion of a transmitted file. This message records the number of blocks received, the block size used, and the name of the file to which the data was written. Event: This message reports an event, not an error info

Type Severity

TFTPD_RECVFROM_ERR
System Log Message Description

recvfrom: error-message The TFTP process (tnp.tftpd) issued the recvfrom() system call when attempting to receive data from the network. The system call failed. Error: An error occurred error

Type Severity

TFTPD_FORK_ERR

637

JUNOS 10.1 System Log Messages Reference

TFTPD_RECV_ERR
System Log Message Description Type Severity

recv: error-message The TFTP process (tnp.tftpd) could not receive data from the network. Error: An error occurred error

TFTPD_SENDCOMPLETE_INFO
System Log Message Description

Sent count blocks of block-size and 1 block of size for file 'filename' The TFTP process (tnp.tftpd) successfully sent a file. This message records the number of blocks sent, the block size used, the size of the last block, and the name of the source file. Event: This message reports an event, not an error info

Type Severity

TFTPD_SEND_ERR
System Log Message Description Type Severity

send: error-message The TFTP process (tnp.tftpd) could not send data. Error: An error occurred error

TFTPD_SOCKET_ERR
System Log Message Description

socket: error-message The TFTP process (tnp.tftpd) could not open a socket for data transmission or reception. Error: An error occurred error

Type Severity

TFTPD_STATFS_ERR
System Log Message

statfs filename, error: error-message

638

TFTPD_RECV_ERR

Chapter 84: TFTPD System Log Messages

Description

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. Error: An error occurred error

Type Severity

TFTPD_STATFS_ERR

639

JUNOS 10.1 System Log Messages Reference

640

TFTPD_STATFS_ERR

Chapter 85

UI System Log Messages

This chapter describes messages with the UI prefix. They are generated by the JUNOS command-line interface (CLI) and management process (mgd), which together form the JUNOS user interface that accepts and processes input from users and client applications.

UI_AUTH_EVENT
System Log Message Description Type Severity

Authenticated user 'username' at permission level 'authentication-level' The management process (mgd) authenticated the indicated user. Event: This message reports an event, not an error info

UI_AUTH_INVALID_CHALLENGE
System Log Message Description

Received invalid authentication challenge for user 'username': response When a user logs onto the routing platform and attempts to authenticate, the CLI and management process (mgd) use a challenge-and-response system to limit the exposure of sensitive information such as passwords and keys. The format of the challenge generated by mgd was incorrect. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

UI_BOOTTIME_FAILED
System Log Message

Unable to fetch boot time: error-message

UI_AUTH_EVENT

641

JUNOS 10.1 System Log Messages Reference

Description

The management process (mgd) could not retrieve the system boot time from the kernel. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

UI_CFG_AUDIT_NEW
System Log Message Description

User 'username' action: pathname new-name The indicated user created a new configuration object by copying or renaming an existing object as indicated. Event: This message reports an event, not an error info

Type Severity

UI_CFG_AUDIT_OTHER
System Log Message Description

User 'username' action: pathname delimitervalue The indicated user deleted, activated, or deactivated a configuration object, as indicated. The JUNOS configuration log facility logged the change. Event: This message reports an event, not an error info

Type Severity

UI_CFG_AUDIT_SET
System Log Message Description Type Severity

User 'username' action: pathname delimiterdata -> "value" The indicated user set a value for a configuration object, as indicated. Event: This message reports an event, not an error info

UI_CFG_AUDIT_SET_SECRET
System Log Message

User 'username' action: pathname

642

UI_BOOTTIME_FAILED

Chapter 85: UI System Log Messages

Description

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. Event: This message reports an event, not an error info

Type Severity

UI_CHILD_ARGS_EXCEEDED
System Log Message Description

Too many arguments for child process 'command' The management process (mgd) invokes some commands on behalf of users. It supplied more arguments than the command's syntax statement specifies. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

UI_CHILD_CHANGE_USER
System Log Message Description

Unable to switch to local user: username The management process (mgd) invokes some commands on behalf of users. Its attempt to adopt the UID of the indicated user failed. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

UI_CHILD_EXEC
System Log Message Description

Child exec failed for command 'command': error-message 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. Error: An error occurred

Type

UI_CFG_AUDIT_SET_SECRET

643

JUNOS 10.1 System Log Messages Reference

Severity Cause Action

error An internal software failure occurred. Contact your technical support representative.

UI_CHILD_EXITED
System Log Message Description

Child exited: PID pid, status return-valuecore-dump-status, command 'command' The management process (mgd) created a child process to execute the indicated command for it. The child process exited unexpectedly with the indicated status code. Error: An error occurred notice An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

UI_CHILD_FOPEN
System Log Message Description

Unable to append to log 'filename': error-message The management process (mgd) attempted to save the output from a command in the indicated log file, but could not open the file. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

UI_CHILD_PIPE_FAILED
System Log Message Description

Unable to create pipe for command 'command': error-message The management process (mgd) created a child process to execute the indicated command for it. Its attempt to create pipes for communication with the child process failed. Error: An error occurred

Type

644

UI_CHILD_EXEC

Chapter 85: UI System Log Messages

Severity Cause Action

error An internal software failure occurred. Contact your technical support representative.

UI_CHILD_STOPPED
System Log Message Description

Child stopped: PID pid, signal=signal-namecore-dump-status, command='command') The management process (mgd) created a child process to execute the indicated command for it. The child process received the indicated signal and stopped. Error: An error occurred notice An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

UI_CHILD_WAITPID
System Log Message Description

waitpid failed: PID pid, rc return-value, status status-code: error-message The management process (mgd) created a child process to execute a command for it. It could not wait for the child process to finish. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

UI_CMDLINE_READ_LINE
System Log Message Description

User 'username', command 'command' 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). Event: This message reports an event, not an error info

Type Severity

UI_CHILD_PIPE_FAILED

645

JUNOS 10.1 System Log Messages Reference

UI_CMD_AUTH_REGEX_INVALID
System Log Message

Invalid 'allow-deny' command authorization regular expression 'regular-expression': error-message An operation that attempted to set command or configuration authorization included the indicated regular expression. The operation failed because the expression syntax was invalid. Error: An error occurred error Correct any errors in the regular expression.

Description

Type Severity Action

UI_COMMIT
System Log Message Description

User 'username' requested 'command' operation (comment: message) The indicated user requested the indicated type of commit operation on the candidate configuration and added the indicated comment. The 'commit' operation applies to the local Routing Engine and the 'commit synchronize' operation to both Routing Engines. Event: This message reports an event, not an error notice

Type Severity

UI_COMMIT_AT_ABORT
System Log Message Description

reason, will try again An attempt to complete a pending commit operation was cancelled for the indicated reason. Error: An error occurred error

Type Severity

UI_COMMIT_AT_COMPLETED
System Log Message Description

'commit at' was successful Changes to the candidate configuration were activated at the time scheduled by a 'commit at' operation. Event: This message reports an event, not an error

Type

646

UI_CMD_AUTH_REGEX_INVALID

Chapter 85: UI System Log Messages

Severity

notice

UI_COMMIT_AT_FAILED
System Log Message Description Type Severity

reason, scheduled commit cleared A 'commit at' operation did not complete, for the indicated reason. Error: An error occurred error

UI_COMMIT_COMPRESS_FAILED
System Log Message Description

Unable to compress file 'filename' As part of committing a new configuration, the management process (mgd) compresses and saves a copy of the configuration. mgd saved the configuration file in regular format because it could not compress it. Error: An error occurred error The Routing Engine is low on resources. An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Cause Action

UI_COMMIT_CONFIRMED_REMINDER
System Log Message Description

'commit confirmed' must be confirmed within duration minutes A 'commit confirmed' operation has activated the candidate configuration temporarily. If the commit is not confirmed within the indicated number of minutes (for example, by the command-line interface (CLI) 'commit' command), the management process (mgd) will roll back to the previous configuration. Event: This message reports an event, not an error notice

Type Severity

UI_COMMIT_EMPTY_CONTAINER
System Log Message

Skipped empty object 'node-name'

UI_COMMIT_AT_COMPLETED

647

JUNOS 10.1 System Log Messages Reference

Description

Some container objects are marked for automatic removal from the configuration hierarchy if they are empty when the user who created them changes to the top ([edit]) level of the hierarchy or exits configuration mode. While committing the candidate configuration, the management process (mgd) encountered such an object that was empty but not removed. Event: This message reports an event, not an error info 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. Populate or remove the empty object before committing the configuration. The user who created the object can remove it by exiting configuration mode or issuing the 'top' command to move to the top level of the hierarchy.

Type Severity Cause

Action

UI_COMMIT_NOT_CONFIRMED
System Log Message Description

Commit was not confirmed; message The 'commit confirmed' operation commits a configuration but requires confirmation within a defined number of minutes for the commit to become permanent. If the commit is not confirmed (by the 'commit' command, for example), the management process (mgd) automatically rolls back to the previously committed configuration. The automatic rollback restores management access to the routing platform in case an error in the configuration blocks access. Event: This message reports an event, not an error notice

Type Severity

UI_COMMIT_PROGRESS
System Log Message Description

Commit operation in progress: message As it performed a commit operation, the management process (mgd) recorded its execution of the indicated step. Event: This message reports an event, not an error info

Type Severity

UI_COMMIT_ROLLBACK_FAILED
System Log Message

Automatic rollback failed

648

UI_COMMIT_EMPTY_CONTAINER

Chapter 85: UI System Log Messages

Description

The 'commit confirmed' operation commits a configuration but requires confirmation within a defined number of minutes for the commit to become permanent. If the commit is not confirmed (by the 'commit' command, for example), the management process (mgd) automatically rolls back to the previously committed configuration. The 'commit confirmed' operation was not confirmed, but mgd could not roll back the configuration. The configuration might be in an indeterminate state. Error: An error occurred error The cause of the problem might be recorded in messages that precede this message in the system log.

Type Severity Cause

UI_COMMIT_SYNC_FORCE
System Log Message

All logins to local configuration database were terminated because forced 'commit synchronize' operation was invoked on other Routing Engine The 'commit synchronize force' command was issued on the other Routing Engine on the router. All login sessions in the local configuration database were terminated and the configuration from the other Routing Engine was committed on the local Routing Engine. Event: This message reports an event, not an error notice

Description

Type Severity

UI_CONFIGURATION_ERROR
System Log Message

Process: process-name, path: pathname, statement: configuration-statement, error-message The indicated process found a problem in its configuration. Error: An error occurred error

Description Type Severity

UI_CONFIGURATION_WARNING
System Log Message

Process: process-name, path: pathname, statement: configuration-statement, warning-message The indicated process found a problem in its configuration. Error: An error occurred warning

Description Type Severity

UI_COMMIT_ROLLBACK_FAILED

649

JUNOS 10.1 System Log Messages Reference

UI_DAEMON_ACCEPT_FAILED
System Log Message Description Type Severity Cause Action

connection-type socket connection accept failed: error-message The management process (mgd) did not accept an incoming connection request. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

UI_DAEMON_FORK_FAILED
System Log Message Description

Unable to create session child: error-message The management process (mgd) invokes the fork() system call to create a copy of itself for each CLI session. The system call failed. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

UI_DAEMON_SELECT_FAILED
System Log Message Description

select failed: error-message The management process (mgd) uses the select() system call to listen for incoming connection requests on a socket. The system call failed. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

650

UI_DAEMON_ACCEPT_FAILED

Chapter 85: UI System Log Messages

UI_DAEMON_SOCKET_FAILED
System Log Message Description

connection-type socket create failed: error-message The management process (mgd) uses sockets to communicate with other JUNOS Software processes running on the routing platform. It could not allocate a socket. Error: An error occurred error System resources are exhausted. Contact your technical support representative.

Type Severity Cause Action

UI_DBASE_ACCESS_FAILED
System Log Message

Unable to reaccess configuration database file 'filename', address address, size size: reason To increase the size of the configuration database, the management process (mgd) must unmap the database from its address space, change the database size, and remap the database. The remapping operation failed. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Description

Type Severity Cause Action

UI_DBASE_CHECKOUT_FAILED
System Log Message Description

Database 'filename' is out of data and needs to be rebuilt When the routing platform boots, the management process (mgd) checks the configuration database for internal consistency. It found one or more inconsistencies. Event: This message reports an event, not an error alert mgd restarted after new JUNOS Software was installed. None; mgd will rebuild the database.

Type Severity Cause Action

UI_DAEMON_SOCKET_FAILED

651

JUNOS 10.1 System Log Messages Reference

UI_DBASE_EXTEND_FAILED
System Log Message Description

Unable to extend configuration database file 'filename' to size requested-size: reason The management process (mgd) could not increase the configuration database to the indicated size. Error: An error occurred error The hard disk is defective or is not installed in the routing platform. Repair or replace the hard disk. There is insufficient disk space on the /var partition on the hard disk. Delete user files from the /var/homes directory to increase the available disk space.

Type Severity Cause Action Cause Action

UI_DBASE_LOGIN_EVENT
System Log Message Description

User 'username' entering configuration mode The indicated user entered configuration mode (logged into the configuration database). Event: This message reports an event, not an error notice

Type Severity

UI_DBASE_LOGOUT_EVENT
System Log Message Description

User 'username' exiting configuration mode The indicated user exited configuration mode (logged out of the configuration database). Event: This message reports an event, not an error notice

Type Severity

UI_DBASE_MISMATCH_EXTENT
System Log Message

Database header extent mismatch for file 'filename': expecting expected-value, got received-value

652

UI_DBASE_EXTEND_FAILED

Chapter 85: UI System Log Messages

Description

The header in the configuration database records the highest address allocated in the database. The management process (mgd) discovered that the highest address actually allocated in the database does not match the header value. Error: An error occurred error The database file is corrupted. Contact your technical support representative.

Type Severity Cause Action

UI_DBASE_MISMATCH_MAJOR
System Log Message

Database header major version number mismatch for file 'filename': expecting expected-value, got received-value 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 management process (mgd) discovered that the major parts (for example, '5' in '5.x') of the version numbers do not match. Error: An error occurred error A recent software upgrade did not complete successfully. Issue the 'show version' command to check the JUNOS version. If necessary, issue the 'request system reboot' command to reboot the routing platform and complete the software installation. The database file is corrupted. Contact your technical support representative.

Description

Type Severity Cause Action

Cause Action

UI_DBASE_MISMATCH_MINOR
System Log Message

Database header minor version number mismatch for file 'filename': expecting expected-value, got received-value 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 management process (mgd) discovered that the minor parts (for example, '2' in 'x.2') of the version numbers do not match. Error: An error occurred

Description

Type

UI_DBASE_MISMATCH_EXTENT

653

JUNOS 10.1 System Log Messages Reference

Severity Cause Action

error A recent software upgrade did not complete successfully. Issue the 'show version' command to check the JUNOS version. If necessary, issue the 'request system reboot' command to reboot the routing platform and complete the software installation. The database file is corrupted. Contact your technical support representative.

Cause Action

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. The header of the configuration database records the version number of the configuration schema (possible set of statements) used when the database was created. To prevent corruption, all JUNOS processes that access the database must use the same schema. The management process (mgd) discovered that the version number for the JUNOS Software installed on the routing platform does not match the header value. Error: An error occurred warning A recent software upgrade did not complete successfully. Issue the 'show version' command to check the JUNOS version. If necessary, issue the 'request system reboot' command to reboot the routing platform and complete the software installation. The database file is corrupted. Contact your technical support representative.

Description

Type Severity Cause Action

Cause Action

UI_DBASE_MISMATCH_SIZE
System Log Message

Database header size mismatch for file 'filename': expecting expected-value, got received-value The header of the configuration database records the database size. The management process (mgd) discovered that the size of the actual database file does not match the header value.

Description

654

UI_DBASE_MISMATCH_MINOR

Chapter 85: UI System Log Messages

Type Severity Cause Action

Error: An error occurred error The database file is corrupted. Contact your technical support representative.

UI_DBASE_OPEN_FAILED
System Log Message Description

Database open failed for file 'filename': reason The management process (mgd) could not open the indicated configuration database file. Error: An error occurred error The database file does not exist. Select a different filename or create a new configuration. The /config directory does not have sufficient space for a new database. Remove files from the /config directory to make more space available.

Type Severity Cause Action Cause Action

UI_DBASE_REBUILD_FAILED
System Log Message Description Type Severity Cause Action

modeusername rebuild of the database 'filename' failed The management process (mgd) could not rebuild the configuration database file. Error: An error occurred alert An internal software failure occurred. Contact your technical support representative.

UI_DBASE_REBUILD_SCHEMA_FAILED
System Log Message

Automatic rebuild of the database failed

UI_DBASE_MISMATCH_SIZE

655

JUNOS 10.1 System Log Messages Reference

Description

The management process (mgd) could not rebuild the schema for the configuration database. Error: An error occurred alert An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

UI_DBASE_REBUILD_STARTED
System Log Message Description

modeusername rebuild/rollback of the database 'filename' started 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. Event: This message reports an event, not an error alert

Type Severity

UI_DBASE_RECREATE
System Log Message Description

User 'username' attempting database re-creation The management process (mgd) discovered that the version of JUNOS Software running on the routing platform does not match the version of the current configuration database. In response to a prompt from mgd, the indicated user initiated a rebuilding of the database. Event: This message reports an event, not an error notice

Type Severity

UI_DBASE_REOPEN_FAILED
System Log Message Description

Reopen of the database failed After rebuilding the schema file for the configuration database, the management process (mgd) closes the file and reopens it in read-only mode to prevent corruption. It could not reopen the file. Error: An error occurred alert An internal software failure occurred.

Type Severity Cause

656

UI_DBASE_REBUILD_SCHEMA_FAILED

Chapter 85: UI System Log Messages

Action

Contact your technical support representative.

UI_DUPLICATE_UID
System Log Message Description

Users username1 and username2 have the same UID uid The JUNOS Software allows multiple user login accounts to share the same UID. This message was logged in case site policy dictates that users should not share UIDs. Event: This message reports an event, not an error notice Assign different UIDs to the affected users.

Type Severity Action

UI_FACTORY_OPERATION
System Log Message

Committing factory default configuration because CONFIG button was pressed and held 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. Event: This message reports an event, not an error notice

Description

Type Severity

UI_INITIALSETUP_OPERATION
System Log Message Description

Committing EZsetup configuration as EZsetup option is chosen The management process (mgd) began a commit operation to activate the pre initial setup configuration, because the initial-setup option was selected from the LCD Menu. Event: This message reports an event, not an error notice

Type Severity

UI_INVALID_REMOTE_PERMISSION
System Log Message Description

invalid permissions from authorization server: permission-name 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.

UI_DBASE_REOPEN_FAILED

657

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred error

UI_JUNOSCRIPT_CMD
System Log Message Description

User 'username' used JUNOScript client to run command 'command' The indicated user ran the indicated command using the JUNOScript application programming interface (API). Event: This message reports an event, not an error info

Type Severity

UI_JUNOSCRIPT_ERROR
System Log Message Description

JUNOScript error: error-message The management process (mgd) normally sends an error message to the JUNOS CLI or JUNOScript API client in an <xnm:error> tag. It could not send the tag, so it sent the indicated error message in an XML comment instead. Error: An error occurred warning

Type Severity

UI_LCC_NO_MASTER
System Log Message Description

No master Routing Engine defined for LCClcc By default, the JUNOS Software installed on the TX Matrix platform in a routing matrix is automatically copied to and installed on all T640 routing nodes in the routing matrix. The software was not installed on the indicated T640 routing node (line-card chassis, or LCC), because the management process (mgd) on the TX Matrix platform could not determine which Routing Engine on the LCC was the master. Error: An error occurred error Resolve the mastership situation on the T640 routing node and install the software on its Routing Engines.

Type Severity Action

UI_LOAD_EVENT
System Log Message

User 'username' is performing a 'operation'

658

UI_INVALID_REMOTE_PERMISSION

Chapter 85: UI System Log Messages

Description

The indicated user requested the indicated operation ('rollback, ' or 'load' or one of its variants) on the configuration database. The existing configuration database was deleted and a new database was created based on a text file. Event: This message reports an event, not an error notice

Type Severity

UI_LOAD_JUNOS_DEFAULT_FILE_EVENT
System Log Message Description Type Severity

Loading the default config from pathname The system is loading junos default configuration from file. Event: This message reports an event, not an error info

UI_LOGIN_EVENT
System Log Message Description Type Severity

User 'username' login, class 'class-name' local-peer[pid] The indicated user started a JUNOS CLI session. Event: This message reports an event, not an error info

UI_LOGOUT_EVENT
System Log Message Description Type Severity

User 'username' logout The indicated user exited from a JUNOS CLI session. Event: This message reports an event, not an error info

UI_LOST_CONN
System Log Message Description

Lost connection to daemon 'process-name' The management process (mgd) uses sockets to communicate with other JUNOS Software processes. The socket it was using for the indicated process closed prematurely. Error: An error occurred

Type

UI_LOAD_EVENT

659

JUNOS 10.1 System Log Messages Reference

Severity Cause Action

error An internal software failure occurred. Contact your technical support representative.

UI_MASTERSHIP_EVENT
System Log Message Description

mastership-event card-name mastership by 'username' Some redundant routing platform components use a master/standby system in which the master component is active and the standby is inactive but ready to assume mastership. The indicated user performed the indicated operation to modify component mastership. Event: This message reports an event, not an error warning

Type Severity

UI_MOTD_PROPAGATE_ERROR
System Log Message Description

Unable to propagate login announcement (motd) to pathname 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. Error: An error occurred error

Type Severity

UI_NETCONF_CMD
System Log Message Description

User 'username' used NETCONF client to run command 'command' The indicated user ran the indicated command using the NETCONF application programming interface (API). Event: This message reports an event, not an error info

Type Severity

UI_NETCONF_ERROR
System Log Message

NETCONF error: error-message

660

UI_LOST_CONN

Chapter 85: UI System Log Messages

Description

The management process (mgd) normally sends error messages to the NETCONF client in the <rpc-error> tag element. It could not send that tag element, and instead sent the indicated error message in an XML comment. Error: An error occurred warning

Type Severity

UI_PARSE_JUNOSCRIPT_ATTRIBUTES
System Log Message Description

Error parsing attributes in client junoscript tag The management process (mgd) encountered an error and exited while attempting to parse the XML attributes in the <junoscript> tag submitted by a client application. Error: An error occurred error

Type Severity

UI_READ_FAILED
System Log Message Description

read failed for peer peer-name: error-message 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. Error: An error occurred error An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

UI_READ_TIMEOUT
System Log Message Description

Timeout on read of peer 'peer-name' When communicating with other JUNOS processes running on the routing platform (referred to as peers), the management process (mgd) waits only a defined period for responses to arrive. The timeout period passed for the indicated process. Event: This message reports an event, not an error notice

Type Severity

UI_NETCONF_ERROR

661

JUNOS 10.1 System Log Messages Reference

UI_REBOOT_EVENT
System Log Message Description Type Severity

System halt-reboot by 'username' The indicated software process restarted as requested by the indicated user. Event: This message reports an event, not an error warning

UI_RESCUE_OPERATION
System Log Message Description

Committing rescue configuration because CONFIG button was pressed The management process (mgd) began a commit operation to activate the rescue configuration, because the CONFIG button on the chassis was pressed. Event: This message reports an event, not an error notice

Type Severity

UI_RESTART_EVENT
System Log Message Description Type Severity

User 'username' restarting daemon 'process-name'description The indicated software process restarted as requested by the indicated user. Event: This message reports an event, not an error warning

UI_SCHEMA_CHECKOUT_FAILED
System Log Message Description

Schema is out of date and needs to be rebuilt The JUNOS user interface schema file records all CLI commands and configuration statements available in the JUNOS Software. While initializing, the new management process (mgd) determined that the schema's sequence number means that the schema is incompatible with the JUNOS Software installed on the routing platform. Error: An error occurred alert The schema is out of date. None; mgd will rebuild the schema based on the current JUNOS version.

Type Severity Cause Action

662

UI_REBOOT_EVENT

Chapter 85: UI System Log Messages

UI_SCHEMA_MISMATCH_MAJOR
System Log Message

Schema major version mismatch for package package-name (expected-value vs. received-value) The JUNOS user interface schema file records all CLI commands and configuration statements available in the JUNOS Software. While initializing, the management process (mgd) discovered that the major part (for example, '5' in '5.x') of the schema version number does not match the major version number of the JUNOS Software installed on the routing platform. The mismatch could lead to corruption of the configuration database. Error: An error occurred error The schema is incompatible with the installed JUNOS Software. None; mgd will rebuild the schema based on the current JUNOS version. An internal software failure occurred. Contact your technical support representative.

Description

Type Severity Cause Action Cause Action

UI_SCHEMA_MISMATCH_SEQUENCE
System Log Message Description

Schema header sequence numbers mismatch for package package-name 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 the database understands the data. The value in the database file did not match the expected value. Error: An error occurred error The JUNOS Software installation did not succeed, possibly because of an internal software error. Contact your technical support representative.

Type Severity Cause

Action

UI_SCHEMA_SEQUENCE_ERROR
System Log Message

Schema sequence number mismatch

UI_SCHEMA_MISMATCH_MAJOR

663

JUNOS 10.1 System Log Messages Reference

Description

The JUNOS user interface schema file records all CLI commands and configuration statements available in the JUNOS Software. The management process (mgd) rebuilds the schema as necessary to be compatible with the JUNOS Software installed on the routing platform. A sequence number in the schema acts as a checksum that represents its content and format. A JUNOS process attempted to access the schema but determined that the schema's sequence number means that it is incompatible with the process. Error: An error occurred alert An internal software failure occurred. Contact your technical support representative.

Type Severity Cause Action

UI_TACPLUS_ERROR
System Log Message Description Type Severity

TACACS+ failure: error-message The management process (mgd) failed to send a record to TACACS+. Error: An error occurred notice

UI_VERSION_FAILED
System Log Message Description

Unable to fetch system version: error-message The management process (mgd) could not retrieve version information from the kernel. Error: An error occurred error Contact your technical support representative.

Type Severity Action

UI_WRITE_RECONNECT
System Log Message Description

Re-establishing connection to peer 'peer-name' The management process (mgd) reconnected to the indicated JUNOS process running on the routing platform. Event: This message reports an event, not an error

Type

664

UI_SCHEMA_SEQUENCE_ERROR

Chapter 85: UI System Log Messages

Severity

notice

UI_WRITE_RECONNECT

665

JUNOS 10.1 System Log Messages Reference

666

UI_WRITE_RECONNECT

Chapter 86

UTMD System Log Messages

This chapter describes messages with the UTMD prefix. They are generated by the unified threat management process (utmd) which protects the network from all types of attack.

UTMD_MALLOC_FAILURE
System Log Message Description

Out of memory. Unable to malloc error-message bytes The example process (utmd) could not allocate memory for a resource possibly due to lack of memory Error: An error occurred error

Type Severity

UTMD_SSAMLIB_FAILURE
System Log Message Description

ssamlib call returned error : error-message The example process (utmd) encoutered an error while calling a function or from a callback of the ssamlib library. Error: An error occurred error

Type Severity

UTMD_MALLOC_FAILURE

667

JUNOS 10.1 System Log Messages Reference

668

UTMD_SSAMLIB_FAILURE

Chapter 87

VCCPD System Log Messages

This chapter describes messages with the VCCPD prefix. They are generated by the virtual chassis control protocol (vccpd) process which exchanges link-state advertisement based discovery messages between all the packet forwarding engines (PFE) through the virtual chassis ports (VCP).

VCCPD_KNL_VERSION
System Log Message

Routing socket version mismatch (kernel kernel-version != vccpd version) -- kernel upgrade required The virtual chassis control protocol process (VCCPD) discovered that the kernel does not support the version of routing sockets it requires. Error: An error occurred error The kernel version is older than the VCCPD version. Upgrade the kernel package.

Description

Type Severity Cause Action

VCCPD_KNL_VERSIONNONE
System Log Message

Routing socket message type message-type's version is not supported by kernel, expected version -- kernel upgrade required The virtual chassis control protocol process (VCCPD) discovered that the kernel does not support the routing socket message types that it requires. Error: An error occurred error The kernel version is older than the VCCPD version. Upgrade the kernel package.

Description

Type Severity Cause Action

VCCPD_KNL_VERSION

669

JUNOS 10.1 System Log Messages Reference

VCCPD_KNL_VERSIONOLD
System Log Message

Routing socket message type message-type's version is older than expected (kernel-version <version) -- consider upgrading the kernel The virtual chassis control protocol process (VCCPD) discovered that the kernel uses an older version of routing socket message types than it does. Error: An error occurred error The kernel version is older than the VCCPD version. Upgrade the kernel package.

Description

Type Severity Cause Action

VCCPD_PROTOCOL_ADJDOWN
System Log Message Description

Lost adjacency to neighbor-system-ids on interface-name, A virtual chassis adjacency with the indicated neighboring switch was terminated. The local switch no longer exchanges information with the neighboring switch. Event: This message reports an event, not an error notice The communication path to the neighboring switch was disrupted, a protocol error occurred, or the neighboring switch was powered down.

Type Severity Cause

VCCPD_PROTOCOL_ADJUP
System Log Message Description

New adjacency to neighbor-system-ids on interface-name A virtual chassis adjacency was established with the indicated neighboring switch. The local switch can now exchange information with it. Event: This message reports an event, not an error info

Type Severity

VCCPD_PROTOCOL_LSPCKSUM
System Log Message

LSP checksum error, interface interface-name, LSP id lspl, sequence sequence-number, checksum checksum, lifetime duration

670

VCCPD_KNL_VERSIONOLD

Chapter 87: VCCPD System Log Messages

Description

The indicated vccpd link-state PDU (LSP) failed an internal checksum validity test, implying that it was corrupted. Error: An error occurred warning The packet was corrupted in transit between the neighboring switch and this switch, or memory on one of the switches was corrupted. None, unless a large number of these messages appear in the system log file. The corrupted LSP is purged from the virtual chassis and sent again by the originator.

Type Severity Cause

Action

VCCPD_PROTOCOL_OVERLOAD
System Log Message Description

vccpd database overload The vccpd link-state database is full and no additional memory can be allocated for it. Error: An error occurred alert No additional memory is available for storing vccpd link-state information. Either system resources are exhausted or a software error occurred (such as a memory leak). Perform one or more of the following actions: (1) Check for unusually high memory usage by vccpd, (2) Add more memory to the switch.

Type Severity Cause

Action

VCCPD_SYSTEM
System Log Message Description Type Severity Cause

reason: error-message A system call made by this process failed. Error: An error occurred error It is possible that the kernel lacked the resources to fulfill the request.

VCCPD_PROTOCOL_LSPCKSUM

671

JUNOS 10.1 System Log Messages Reference

672

VCCPD_SYSTEM

Chapter 88

VRRPD System Log Messages

This chapter describes messages with the VRRPD prefix. They are generated by the Virtual Router Redundancy Protocol (VVRP) process (vrrpd), which provides the user interface for management of VRRP groups.

VRRPD_ADVERT_TIME_MISMATCH
System Log Message

Packet received by interface-name for VRRP group vrrp-group-id had advertisement time received-value ms instead of required expected-value ms A Virtual Routing Redundancy Protocol (VRRP) advertisement packet received by the indicated interface for the indicated VRRP group specified an advertisement-timer value different from the value configured for the interface and group. The advertisement interval must be the same on all routing platforms in the VRRP group. For VRRP with IPv4, the value is set by the 'advertise-interval <seconds>' or 'fast-interval <milliseconds>' statement at the [edit interfaces <interface-name> unit <logical-unit-number> family inet address <address> vrrp-group <group-number>] hierarchy level. For VRRP with IPv6, the value is set by the 'inet6-advertise-interval <seconds>' or 'fast-interval <milliseconds>' statement at the [edit interfaces <interface-name> unit <logical-unit-number> family inet6 address <address> vrrp-inet6-group <group-number>] hierarchy level. Error: An error occurred error

Description

Type Severity

VRRPD_AUTH_INFO_INVALID
System Log Message

VRRP ad packet from ip-address received by interface interface-name.interface-unit for group vrrp-group-id was invalid: error-message The Virtual Routing Redundancy Protocol (VRRP) advertisement packet sent from the indicated IP address and received by the VRRP process (vrrpd) for the indicated group at the indicated address contained invalid authentication information. The message 'invalid-authentication-type' means that the packet specifies an authentication type that is not defined in 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 'authentication-key-mismatch' means that the authentication key in the packet is incorrect.

Description

VRRPD_ADVERT_TIME_MISMATCH

673

JUNOS 10.1 System Log Messages Reference

Type Severity

Error: An error occurred warning

VRRPD_GET_TRAP_HEADER_FAILED
System Log Message Description

Request for trap signature header failed The Virtual Routing Redundancy Protocol (VRRP) process requested the signature header for an SNMP trap. The request failed. Error: An error occurred error An internal software failure occurred.

Type Severity Cause

VRRPD_LINK_LOCAL_ADD_MISMATCH
System Log Message Description

Link-Local Address Mismatch: received-value expected-value The indicated interface received a Virtual Routing Redundancy protocol (VRRP) packet for the indicated VRRP group in which the link-local address was different from the one configured for the group and interface Error: An error occurred error

Type Severity

VRRPD_MISSING_VIP
System Log Message

Packet received by interface-name for VRRP group vrrp-group-id did not include required virtual IP address ip-address The indicated interface received a Virtual Routing Redundancy protocol (VRRP) packet for the indicated VRRP group in which the list of virtual IP addresses did not include the indicated address. For VRRP with IPv4, the list is defined by the 'virtual-address [ <addresses> ]' statement at the [edit interfaces <interface-name> unit <logical-unit-number> family inet address <address> vrrp-group <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. Error: An error occurred error

Description

Type Severity

674

VRRPD_AUTH_INFO_INVALID

Chapter 88: VRRPD System Log Messages

VRRPD_NEW_BACKUP
System Log Message

Interface interface-name.interface-unit (local address interface-address) became VRRP backup for group vrrp-group-id The indicated interface became the Virtual Routing Redundancy Protocol (VRRP) backup for the indicated VRRP group. The VRRP process (vrrpd) stopped sending VRRP advertisements for the virtual IP address on the interface that corresponds to the group. Event: This message reports an event, not an error warning

Description

Type Severity

VRRPD_NEW_MASTER
System Log Message

Interface interface-name.interface-unit (local address interface-address) became VRRP master for group vrrp-group-id The indicated interface became the Virtual Routing Redundancy Protocol (VRRP) master for the indicated VRRP group. The VRRP process (vrrpd) started sending VRRP advertisements for the virtual IP address on the interface that corresponds to the group. Event: This message reports an event, not an error warning

Description

Type Severity

VRRPD_VIP_COUNT_MISMATCH
System Log Message

Packet received by interface-name for VRRP group vrrp-group-id had received-value virtual IP addresses instead of required expected-value The indicated interface received a Virtual Routing Redundancy Protocol (VRRP) packet for the indicated VRRP group in which the number of virtual IP addresses was different from the number of addresses configured for the group and interface. The list of addresses must be the same on all routing platforms in a VRRP group. For VRRP with IPv4, the list is defined by the 'virtual-address [ <addresses> ]' statement at the [edit interfaces <interface-name> unit <logical-unit-number> family inet address <address> vrrp-group <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. Error: An error occurred error

Description

Type Severity

VRRPD_NEW_BACKUP

675

JUNOS 10.1 System Log Messages Reference

676

VRRPD_VIP_COUNT_MISMATCH

Chapter 89

VSYSD System Log Messages

This chapter describes messages with the VSYSD prefix. They are generated by the virtual system process (vsysd) process which controls virtual systems.

VSYSD_INIT_FAILED
System Log Message Description

Unable to find root virtual system The virtual system process (vsysd) did not initialize, because it could not find the root virtual system. Error: An error occurred error

Type Severity

VSYSD_INIT_FAILED

677

JUNOS 10.1 System Log Messages Reference

678

VSYSD_INIT_FAILED

Chapter 90

WEB System Log Messages

This chapter describes messages with the WEB prefix. They are generated by the Hypertext Transfer Protocol process (httpd), which provides a graphical user interface (GUI) for monitoring and configuring J Series Services Routers.

WEB_AUTH_FAIL
System Log Message Description Type Severity

Unable to authenticate httpd client (username username) The checklogin authentication process could not authenticate the indicated user. Event: This message reports an event, not an error notice

WEB_AUTH_SUCCESS
System Log Message Description Type Severity

Authenticated httpd client (username username) The checklogin authentication process authenticated the indicated user. Event: This message reports an event, not an error notice

WEB_AUTH_TIME_EXCEEDED
System Log Message Description

Login attempt exceeded maximum processing time The checklogin process halted a login attempt because it took longer than the maximum processing time allowed. Error: An error occurred error

Type Severity

WEB_AUTH_FAIL

679

JUNOS 10.1 System Log Messages Reference

WEB_CERT_FILE_NOT_FOUND
System Log Message Description Type Severity

Could not find certificate file 'filename', disabling HTTPS http-gk could not open the configured HTTPS certificate for reading. Error: An error occurred error

WEB_CHILD_STATE
System Log Message Description

Unable to retrieve child state: error-message The Web management process (httpd) could not retrieve state information for a child process that had exited, for the indicated reason. Error: An error occurred error

Type Severity

WEB_CONFIG_OPEN_ERROR
System Log Message Description Type Severity

Could not open 'filename' for writing httpd-gk could not open the web server configuration file for writing. Error: An error occurred error

WEB_CONFIG_WRITE_ERROR
System Log Message Description Type Severity

Could not write 'filename' configuration. Disk full? httpd-gk could not write the web server configuration file to disk. Error: An error occurred error

WEB_COULDNT_START_HTTPD
System Log Message

Could not fork httpd process!

680

WEB_CERT_FILE_NOT_FOUND

Chapter 90: WEB System Log Messages

Description

The Web management gatekeeper process (httpd-gk) could not start the web management process (httpd). Error: An error occurred error

Type Severity

WEB_EVENTLIB_INIT
System Log Message Description

Unable to initialize event library: error-message The Web management gatekeeper process (httpd-gk) attempted to initialize the event library during startup. The attempt failed for the indicated reason. Error: An error occurred error

Type Severity

WEB_KEYPAIR_FILE_NOT_FOUND
System Log Message Description Type Severity

Could not find key pair file 'filename', disabling HTTPS http-gk could not open the configured HTTPS key pair file for reading. Error: An error occurred error

WEB_MGD_BIND_ERROR
System Log Message Description Type Severity

Could not bind mgd listener socket: error-message The web management process could not open the MGD listening socket. Error: An error occurred error

WEB_MGD_CHMOD_ERROR
System Log Message Description

Could not chmod mgd listener socket The web management process could not change the MGD listening socket to proper file permissions. Error: An error occurred error

Type Severity

WEB_COULDNT_START_HTTPD

681

JUNOS 10.1 System Log Messages Reference

WEB_MGD_CONNECT_ERROR
System Log Message Description Type Severity

Could not connect to mgd management socket The web management process could not connect to the MGD management socket. Error: An error occurred error

WEB_MGD_FCNTL_ERROR
System Log Message Description Type Severity

Could not set incoming mgd request to nonblocking The web management process could not set the MGD listening socket to nonblocking. Error: An error occurred error

WEB_MGD_LISTEN_ERROR
System Log Message Description Type Severity

Could not listen mgd listener socket: error-message The web management process could not open the MGD listening socket. Error: An error occurred error

WEB_MGD_RECVMSG_PEEK_ERROR
System Log Message Description Type Severity

Could not peek recvmsg() mgd connection The web management process could not peek the incoming MGD request. Error: An error occurred error

WEB_MGD_SOCKET_ERROR
System Log Message Description

Could not create mgd listener socket The web management process could not open the MGD listening socket.

682

WEB_MGD_CONNECT_ERROR

Chapter 90: WEB System Log Messages

Type Severity

Error: An error occurred error

WEB_PIDFILE_LOCK
System Log Message Description

Unable to lock PID file pathname: error-message 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. Error: An error occurred error

Type Severity

WEB_PIDFILE_UPDATE
System Log Message Description

Unable to update PID file pathname: error-message The Web management gatekeeper process (httpd-gk) attempted to update the indicated file, which records the process ID (PID) of the running httpd-gk process. The file serves to prevent multiple instances of httpd-gk from running simultaneously. The attempt failed for the indicated reason. Error: An error occurred error The most common reason is that another httpd-gk process was already running.

Type Severity Cause

WEB_UNAME_FAILED
System Log Message Description

Unable to retrieve system hostname: error-message The Web management gatekeeper process (httpd-gk) attempted to retrieve and store the local hostname, which it shares with its remote clients. The attempt failed for the indicated reason. Error: An error occurred error

Type Severity

WEB_WEBAUTH_AUTH_FAIL
System Log Message

Web-authentication of user username with fwauthd failed

WEB_MGD_SOCKET_ERROR

683

JUNOS 10.1 System Log Messages Reference

Description

The web-authentication authentication process was unable to authenticate the indicated user Event: This message reports an event, not an error notice

Type Severity

WEB_WEBAUTH_AUTH_OK
System Log Message Description

Web-authentication of user username with fwauthd successful The web-authentication authentication process was able to authenticate the indicated user successfully Event: This message reports an event, not an error notice

Type Severity

WEB_WEBAUTH_CONNECT_FAIL
System Log Message Description

Unable to connect to fwauthd on socket file-descriptor: error-message The web-authentication authentication process could not connect to fwauthd daemon on the indicated socket Event: This message reports an event, not an error error

Type Severity

684

WEB_WEBAUTH_AUTH_FAIL

Chapter 91

WEBFILTER System Log Messages

This chapter describes messages with the WEBFILTER prefix. They are generated by the web filtering process (webfilter) which allows you to manage Internet usage by preventing access to inappropriate web content.

WEBFILTER_CACHE_NOT_ENABLED
System Log Message Description Type Severity Cause Action

Failed to enable the web-filtering category cache Failed to enable the category cache for web-filtering Event: This message reports an event, not an error error Temporarily out of system memory No recommended action

WEBFILTER_INTERNAL_ERROR
System Log Message Description Type Severity Cause Action

Error encountered: error-message An error is encountered in a periodical task or during a server update Event: This message reports an event, not an error error An error is encountered in a periodical task or during a server update No recommended action

WEBFILTER_REQUEST_NOT_CHECKED
System Log Message

Error encountered: server down, failed to check request error-message

WEBFILTER_CACHE_NOT_ENABLED

685

JUNOS 10.1 System Log Messages Reference

Description Type Severity Cause Action

Web-filtering failed to check a web request, Event: This message reports an event, not an error error Failed to talk to web server, temporary out of system memory or internal error No recommended action

WEBFILTER_SERVER_CONNECTED
System Log Message Description Type Severity Cause Action

Successfully connected to webfilter server name Client successfully connected to web server Event: This message reports an event, not an error notice Successfully connected to web server No recommended action

WEBFILTER_SERVER_DISCONNECTED
System Log Message Description Type Severity Cause Action

Webfilter: server name disconnected A socket error is encountered upon connecting to a web server Event: This message reports an event, not an error notice A socket error is encountered upon connecting to a web server No recommended action

WEBFILTER_SERVER_ERROR
System Log Message Description Type

WebFilter: An error is received from server name (0xstatus-code): error-message An error status is received from web server Event: This message reports an event, not an error

686

WEBFILTER_REQUEST_NOT_CHECKED

Chapter 91: WEBFILTER System Log Messages

Severity Cause

notice An error status is received from web server

WEBFILTER_URL_BLOCKED
System Log Message

WebFilter: ACTION="URL Blocked" source-address(source-port)->destination-address(destination-port) CATEGORY="name" REASON="error-message" PROFILE="profile-name" URL=object-name OBJ=pathname A web request is blocked Event: This message reports an event, not an error warning A web request is blocked No recommended action

Description Type Severity Cause Action

WEBFILTER_URL_PERMITTED
System Log Message

WebFilter: ACTION="URL Permitted" source-address(source-port)->destination-address(destination-port) CATEGORY="name" REASON="error-message" PROFILE="profile-name" URL=object-name OBJ=pathname A web request is permitted Event: This message reports an event, not an error info A web request is permitted No recommended action

Description Type Severity Cause Action

WEBFILTER_SERVER_ERROR

687

JUNOS 10.1 System Log Messages Reference

688

WEBFILTER_URL_PERMITTED

Part 3

Index

Index on page 691

Index

689

JUNOS 10.1 System Log Messages Reference

690

Index

Index
Symbols
! regular expression operator system logging...............................................24 #, comments in configuration statements....................lxi $ regular expression operator system logging...............................................24 () regular expression operator system logging...............................................24 ( ), in syntax descriptions.............................................lxi * regular expression operator system logging...............................................24 + regular expression operator system logging...............................................24 . regular expression operator system logging...............................................24 < >, in syntax descriptions........................................lxi ? regular expression operator system logging...............................................24 [] regular expression operator system logging...............................................24 [ ], in configuration statements....................................lxi ^ regular expression operator system logging...............................................24 { }, in configuration statements..................................lxii | regular expression operator system logging...............................................24 | (pipe), in syntax descriptions.....................................lxi ANCPD system log messages.......................................63 ANTISPAM system log messages..................................65 any (system logging facility)...........................................9 any (system logging severity level)...............................10 APPIDD system log messages......................................67 APPPXY system log messages......................................69 archive statement usage guidelines....................................................18 ASP system log messages............................................71 AUDITD system log messages....................................101 AUTHD system log messages.....................................105 authorization (system logging facility) Facilities for the facility-override Statement............9 AUTOCONFD system log messages............................107 AV system log messages............................................111

B
BFDD system log messages........................................119 BOOTPD system log messages...................................121 braces, in configuration statements.............................lxii brackets angle, in syntax descriptions.................................lxi square, in configuration statements......................lxi brief statement system logging usage guidelines............................................12

C
CFMD system log messages.......................................127 change-log (system logging facility)................................9 CHASSISD system log messages................................131 comments, in configuration statements.......................lxi Common Criteria system logging........................................................7 conflict-log (system logging facility)................................9 CONNECTION system log messages..........................213 console statement system logging usage guidelines............................................13 CONTENT system log messages.................................215 conventions text and syntax.....................................................lxi COSD system log messages.......................................217 critical (system logging severity level 2).......................21

A
ACCT system log messages..........................................57 ALARMD system log messages.....................................61 alert (system logging severity level 1)...........................21 alert (system logging severity level)..............................10

Index

691

JUNOS 10.1 System Log Messages Reference

critical (system logging severity level)..........................10 curly braces, in configuration statements....................lxii customer support........................................................lxii contacting JTAC....................................................lxii

FWAUTH system log messages..................................291

G
GPRSD system log messages......................................295

D
daemon (system logging facility)....................................9 option to facility-override statement.....................16 DCD system log messages.........................................231 debug (system logging severity level 7)........................21 dfc (system logging facility)............................................9 DFCD system log messages.......................................237 DFWD system log messages......................................241 DHCPD system log messages.....................................243 documentation comments on.......................................................lxii DYNAMIC system log messages.................................247

H
help syslog command usage guidelines....................................................49 HNCACHED system log messages..............................297 host statement system logging usage guidelines for routing matrix................34 usage guidelines for single-chassis system.......................................................13

I E
emergency (system logging severity level 0)................21 emergency (system logging severity level)...................10 error (system logging severity level 3)..........................21 error (system logging severity level).............................10 ESWD system log messages.......................................253 EVENTD system log messages...................................261 explicit-priority statement usage guidelines routing matrix...............................................33 single-chassis system.....................................19 ICCPD system log messages.......................................299 icons defined, notice.....................................................lx IDP system log messages...........................................301 info (system logging severity level 6)............................21 info (system logging severity level)...............................10 interactive-commands (system logging facility)..............9

J
JADE system log messages.........................................307 JCS system log messages............................................309 JDIAMETERD system log messages............................315 JSRPD system log messages.......................................317 JUNOS-FIPS system logging........................................................7

F
facilities (system logging) alternative for remote machine.............................16 default for remote machine..................................14 for local machine....................................................9 mapping of codes to names..................................20 facility-override statement system logging usage guidelines............................................14 FCD system log messages..........................................269 file statement system logging usage guidelines......................................11, 18 files system log messages, archiving............................18 firewall (system logging facility).....................................9 FLOW system log messages.......................................271 font conventions..........................................................lxi FPCLOGIN system log messages................................273 FSAD system log messages........................................275 ftp (system logging facility)............................................9 option to facility-override statement.....................16 FUD system log messages..........................................285

K
kernel (system logging facility).......................................9 option to facility-override statement.....................16

L
L2ALD system log messages......................................347 L2CPD system log messages......................................357 L2TPD system log messages......................................367 LACPD system log messages......................................399 LFMD system log messages.......................................401 LIBESPTASK system log messages.............................403 LIBJNX system log messages......................................405 LIBJSNMP system log messages.................................413 LIBMSPRPC system log messages..............................419 LICENSE system log messages...................................423 LLDPD system log messages......................................427 local[0-7] (options to facility-override statement).........16

692

Index

Index

log-prefix statement system logging usage guidelines............................................17 LOGIN system log messages......................................429 LPDFD system log messages......................................435 LRMUX system log messages.....................................437

R
RDD system log messages.........................................491 regular expression operators system logging......................................................24 RMOPD system log messages....................................495 routing matrix system logging......................................................28 RPD system log messages..........................................499 RT system log messages............................................567 RTLOG system log messages......................................589 RTLOGD system log messages...................................591

M
manuals comments on.......................................................lxii match statement usage guidelines....................................................23 MCSNOOPD system log messages.............................439 MIB2D system log messages......................................441 MPLS_OAM system log messages..............................449

S
SAVAL system log messages......................................595 scc-master option to host statement usage guidelines....................................................29 SDXD system log messages.......................................597 severity levels for system logging.................................21 size statement system logging usage guidelines............................................18 SMTPD system log messages.....................................601 SNMP system log messages.......................................603 SNMPD system log messages.....................................607 source-address statement system logging usage guidelines for routing matrix................34 usage guidelines for single-chassis system.......................................................14 SPD system log messages..........................................619 structured-data statement usage guidelines....................................................12 support, technical See technical support syntax conventions......................................................lxi system logging Common Criteria....................................................7 configuration statements........................................4 defaults...................................................................4 different on each node in routing matrix..............35 disabling...............................................................25 examples..............................................................25 facilities alternative for remote machine.....................16 default for remote machine...........................14 for local machine.............................................9 facilties mapping of codes to names...........................20 files, archiving.......................................................18 forwarding messages in routing matrix.................29 JUNOS-FIPS.............................................................7 message descriptions displaying......................................................49 fields in..........................................................49

N
NEXTHOP system log messages.................................453 no-world-readable statement system logging usage guidelines............................................18 none (system logging severity level).............................10 notice (system logging severity level 5)........................21 notice (system logging severity level)...........................10 notice icons defined......................................................lx NSD system log messages..........................................455 NSTRACED system log messages...............................457

O
operators, regular expression system logging......................................................24 other-routing-engine option to host statement usage guidelines routing matrix...............................................34 single-chassis system.....................................13

P
parentheses, in syntax descriptions..............................lxi pfe (system logging facility)............................................9 PFE system log messages...........................................459 PFED system log messages........................................471 PGCPD system log messages......................................473 PING system log messages.........................................475 PPMD system log messages.......................................479 PPPD system log messages........................................481 priorities system logging, including in log message for routing matrix..........................................33 for single-chassis system...............................19 PROFILER system log messages.................................489

Index

693

JUNOS 10.1 System Log Messages Reference

messages, displaying generated by JUNOS process.........................43 generated by service on PIC..........................44 structured-data format...................................38 regular expression filtering...................................23 regular expression operators.................................24 routing matrix.......................................................28 severity levels.......................................................21 single-chassis system..............................................7 timestamp, modifying...........................................22 system processes usage guidelines......................................................4

T
TASK system log messages........................................625 technical support contacting JTAC....................................................lxii TFTPD system log messages......................................635 time-format statement usage guidelines....................................................22 TX Matrix platform system logging......................................................28

U
UI system log messages.............................................641 user (system logging facility)..........................................9 option to facility-override statement.....................16 user statement system logging usage guidelines............................................12 UTMD system log messages.......................................667

V
VCCPD system log messages.....................................669 VRRPD system log messages.....................................673 VSYSD system log messages......................................677

W
warning (system logging severity level 4).....................21 warning (system logging severity level)........................10 WEB system log messages.........................................679 WEBFILTER system log messages..............................685 world-readable statement system logging usage guidelines............................................18

694

Index