Syslog Messages

Junos OS
System Log Messages Reference
Release
15.1
Modified: 2015-05-26
Copyright 2015, Juniper Networks, Inc.

Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks 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.

Junos OS System Log Messages Reference
Release 15.1
Copyright 2015, Juniper Networks, Inc.
All rights reserved.
Revision History
May 2015R1 Junos OS 15.1
The information in this document is current as of the date on the title page.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the
year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks
software. Use of such software is subject to the terms and conditions of the End User License Agreement (EULA) posted at
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of
that EULA.
ii Copyright 2015, Juniper Networks, Inc.

Abbreviated Table of Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxv
Part 1 Overview
Chapter 1 Configuring System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Part 2 System Log Messages

Chapter 2 AAA System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Chapter 3 ACCT System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Chapter 4 ALARMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Chapter 5 AMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Chapter 6 ANALYZER System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Chapter 7 ANTISPAM System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Chapter 8 APPID System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Chapter 9 APPIDD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Chapter 10 APPPXY System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Chapter 11 APPTRACK System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Chapter 12 ASP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Chapter 13 AUDITD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Chapter 14 AUTHD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Chapter 15 AUTOCONFD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Chapter 16 AUTOD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Chapter 17 AV System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Chapter 18 BBE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Chapter 19 BFDD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Chapter 20 BGP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Chapter 21 BOOTPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Chapter 22 CFMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Chapter 23 CHASSISD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Chapter 24 CHASSISM System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Chapter 25 CLKSYNCD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Chapter 26 COSD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Chapter 27 DCBX System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Chapter 28 DCD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Copyright 2015, Juniper Networks, Inc. iii

Chapter 29 DDOS System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Chapter 30 DFCD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Chapter 31 DFWD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Chapter 32 DHCPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Chapter 33 DIAM System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Chapter 34 DOT1XD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Chapter 35 DYNAMIC System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Chapter 36 ESWD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Chapter 37 EVENTD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Chapter 38 FABOAMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Chapter 39 FC System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Chapter 40 FCOE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Chapter 41 FIP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Chapter 42 FIPS System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Chapter 43 FLOW System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Chapter 44 FPCLOGIN System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Chapter 45 FSAD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Chapter 46 FUD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Chapter 47 FWAUTH System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Chapter 48 GPRSD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Chapter 49 HNCACHED System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Chapter 50 ICCPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Chapter 51 IDP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Chapter 52 JADE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Chapter 53 JCS System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Chapter 54 JDIAMETERD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Chapter 55 JIVED System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Chapter 56 JNUD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Chapter 57 JPTSPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Chapter 58 JSERVICES System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Chapter 59 JSRPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Chapter 60 JTASK System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Chapter 61 JTRACE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Chapter 62 KMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Chapter 63 L2ALD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Chapter 64 L2CPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Chapter 65 L2TPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Chapter 66 LACP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
iv Copyright 2015, Juniper Networks, Inc.

Abbreviated Table of Contents
Chapter 67 LACPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539

Chapter 68 LFMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Chapter 69 LIBJNX System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Chapter 70 LIBJSNMP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Chapter 71 LIBMSPRPC System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Chapter 72 LICENSE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Chapter 73 LLDP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Chapter 74 LOGIN System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
Chapter 75 LPDFD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Chapter 76 LRMUX System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
Chapter 77 LSYSD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Chapter 78 MBG System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
Chapter 79 MCSN System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Chapter 80 MIB2D System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Chapter 81 MPLS System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
Chapter 82 NEXTHOP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
Chapter 83 NSD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Chapter 84 NSTRACED System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Chapter 85 NTPDATE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
Chapter 86 NTPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Chapter 87 PARSE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Chapter 88 PFE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
Chapter 89 PFED System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Chapter 90 PGCPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Chapter 91 PING System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
Chapter 92 PKID System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Chapter 93 PPMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Chapter 94 PPPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
Chapter 95 PROFILER System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Chapter 96 RDD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
Chapter 97 RMOPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Chapter 98 RPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Chapter 99 RT System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Chapter 100 RTLOG System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
Chapter 101 RTLOGD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
Chapter 102 RTPERF System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
Chapter 103 SAVAL System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
Chapter 104 SDK System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
Copyright 2015, Juniper Networks, Inc. v

Chapter 105 SDXD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771

Chapter 106 SM System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
Chapter 107 SMTPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
Chapter 108 SNMP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
Chapter 109 SNMPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
Chapter 110 SPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
Chapter 111 SSH System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Chapter 112 SSHD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Chapter 113 SSL System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
Chapter 114 SYSTEM System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Chapter 115 TFTPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
Chapter 116 TRANSPORTD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
Chapter 117 UFDD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
Chapter 118 UI System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
Chapter 119 UTMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
Chapter 120 VCCPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
Chapter 121 VM System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
Chapter 122 VRRPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
Chapter 123 WEB System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Chapter 124 WEBFILTER System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
Part 3 Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881
vi Copyright 2015, Juniper Networks, Inc.

Table of Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxv
Junos OS Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . lxv
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxvi
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxvi
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxvi
Using the Examples in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxvii
Merging a Full Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxvii
Merging a Snippet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxviii
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxviii
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxx
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxxi
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . lxxi
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lxxi
Part 1 Overview
Chapter 1 Configuring System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Junos OS System Log Configuration Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Minimum and Default System Logging Configuration . . . . . . . . . . . . . . . . . . . . . . . 4
Junos OS Minimum System Logging Configuration . . . . . . . . . . . . . . . . . . . . . . 4
Junos OS Default System Log Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Junos OS Platform-Specific Default System Log Messages . . . . . . . . . . . . . . . 6
Configuring System Logging for a Single-Chassis System . . . . . . . . . . . . . . . . . . . . 7
Specifying the Facility and Severity of Messages to Include in the Log . . . . . . 9
Directing System Log Messages to a Log File . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Logging Messages in Structured-Data Format . . . . . . . . . . . . . . . . . . . . . . . . . 12
Directing System Log Messages to a User Terminal . . . . . . . . . . . . . . . . . . . . . 13
Directing System Log 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
Directed to a Remote Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Changing the Alternative Facility Name for System Log Messages
Directed to a Remote Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Default Facilities for System Log Messages Directed to a Remote
Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Alternate Facilities for System Log Messages Directed to a Remote
Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Examples: Assigning an Alternative Facility to System Log Messages
Directed to a Remote Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Copyright 2015, Juniper Networks, Inc. vii

Adding a Text String to System Log Messages Directed to a Remote

Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Adding a String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Specifying Log File Size, Number, and Archiving Properties . . . . . . . . . . . . . . 20
Including Priority Information in System Log Messages . . . . . . . . . . . . . . . . . 22
System Log Facility Codes and Numerical Codes Reported in Priority
Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Including the Year or Millisecond in Timestamps . . . . . . . . . . . . . . . . . . . . . . 25
Using Regular Expressions to Refine the Set of Logged Messages . . . . . . . . . 25
Junos System Log Regular Expression Operators for the match
Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Disabling the System Logging of a Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Examples: Configuring System Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Configuring System Logging for a TX Matrix Router . . . . . . . . . . . . . . . . . . . . . . . . 31
Configuring Message Forwarding in the Routing Matrix . . . . . . . . . . . . . . . . . 33
Impact of Different Local and Forwarded Severity Levels on System
Log Messages on a TX Matrix Router . . . . . . . . . . . . . . . . . . . . . . . . . 34
Configuring Optional Features for Forwarded Messages . . . . . . . . . . . . . . . . 36
Including Priority Information in Forwarded Messages . . . . . . . . . . . . . . 36
Adding a Text String to Forwarded Messages . . . . . . . . . . . . . . . . . . . . . . 37
Using Regular Expressions to Refine the Set of Forwarded
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Directing Messages to a Remote Destination from the Routing Matrix Based
on the TX Matrix Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Configuring System Logging Differently on Each T640 Router in a Routing
Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Configuring System Logging for a TX Matrix Plus Router . . . . . . . . . . . . . . . . 40
Configuring Message Forwarding to the TX Matrix Plus Router . . . . . . . . . . . 42
Impact of Different Local and Forwarded Severity Levels on System Log
Messages on a TX Matrix Plus Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Messages Logged When the Local and Forwarded Severity Levels Are
the Same . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Messages Logged When the Local Severity Level Is Lower . . . . . . . . . . . 43
Messages Logged When the Local Severity Level Is Higher . . . . . . . . . . . 44
Configuring Optional Features for Forwarded Messages on a TX Matrix Plus
Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Including Priority Information in Forwarded Messages . . . . . . . . . . . . . . 45
Adding a Text String to Forwarded Messages . . . . . . . . . . . . . . . . . . . . . 46
Using Regular Expressions to Refine the Set of Forwarded
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Directing Messages to a Remote Destination from the Routing Matrix Based
on a TX Matrix Plus Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Configuring System Logging Differently on Each T1600 or T4000 Router in
a Routing Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
viii Copyright 2015, Juniper Networks, Inc.

Table of Contents
Displaying and Interpreting System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . 49

Displaying a Log File from a Single-Chassis System . . . . . . . . . . . . . . . . . . . . 49
Displaying a Log File from a Routing Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Interpreting System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Interpreting Messages Generated in Structured-Data Format . . . . . . . . . 51
Interpreting Messages Generated in Standard Format by a Junos OS
Process or Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Interpreting Messages Generated in Standard Format by Services on a
PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Format of the message-source Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
The message-source Field on a Single-Chassis System . . . . . . . . . . . . . 57
The message-source Field on a TX Matrix Platform . . . . . . . . . . . . . . . . 58
Examples: Displaying a Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Getting Help About System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Displaying and Interpreting System Log Message Descriptions . . . . . . . . . . . 60
Examples: Displaying System Log Message Descriptions . . . . . . . . . . . . . . . . 62
Part 2 System Log Messages

Chapter 2 AAA System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
AAA_RADIUS_SERVER_STATE_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Chapter 3 ACCT System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
ACCT_ACCOUNTING_FERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
ACCT_ACCOUNTING_FOPEN_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
ACCT_ACCOUNTING_SMALL_FILE_SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
ACCT_BAD_RECORD_FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
ACCT_CU_RTSLIB_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
ACCT_FORK_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
ACCT_FORK_LIMIT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
ACCT_GETHOSTNAME_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
ACCT_MALLOC_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
ACCT_THREAD_CREATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
ACCT_UNDEFINED_COUNTER_NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
ACCT_XFER_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
ACCT_XFER_POPEN_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
ACCT_XFER_TIMEDOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Chapter 4 ALARMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
ALARMD_CONFIG_ACCESS_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
ALARMD_CONFIG_CLOSE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
ALARMD_CONFIG_PARSE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
ALARMD_CONFIG_RECONFIG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
ALARMD_CONNECTION_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
ALARMD_DECODE_ALARM_OBJECT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
ALARMD_EXISTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
ALARMD_EXISTS_TERM_OTHER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
ALARMD_IFDALARM_TYPE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
ALARMD_IFDEV_RTSLIB_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
ALARMD_IPC_MSG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Copyright 2015, Juniper Networks, Inc. ix

ALARMD_IPC_MSG_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
ALARMD_IPC_UNEXPECTED_MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
ALARMD_MEM_ALLOC_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
ALARMD_MGR_CONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
ALARMD_MULTIPLE_ALARM_BIT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
ALARMD_PIDFILE_OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
ALARMD_PIPE_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
ALARMD_SOCKET_CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
ALARMD_UNEXPECTED_EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Chapter 5 AMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
AMD_CONFIG_CHECK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
AMD_FILE_OPEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Chapter 6 ANALYZER System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
ANALYZER_INPUT_INTERFACES_LIMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Chapter 7 ANTISPAM System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
ANTISPAM_SPAM_DETECTED_MT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Chapter 8 APPID System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
APPID_SIGNATURE_LICENSE_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Chapter 9 APPIDD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
APPIDD_APPPACK_DOWNLOAD_RESULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
APPIDD_APPPACK_INSTALL_RESULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
APPIDD_APPPACK_UNINSTALL_RESULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
APPIDD_DAEMON_INIT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
APPIDD_INTERNAL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
APPIDD_SCHEDULED_UPDATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Chapter 10 APPPXY System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
APPPXY_SESSION_ABORT_MT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Chapter 11 APPTRACK System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
APPTRACK_SESSION_APP_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
APPTRACK_SESSION_APP_UPDATE_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
APPTRACK_SESSION_CLOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
APPTRACK_SESSION_CLOSE_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
APPTRACK_SESSION_CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
APPTRACK_SESSION_CREATE_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
APPTRACK_SESSION_VOL_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
APPTRACK_SESSION_VOL_UPDATE_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Chapter 12 ASP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
ASP_COS_RULE_MATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
ASP_IDS_HOST_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
ASP_IDS_HOST_RATE_APP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
ASP_IDS_INV_CLEAR_QUERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
ASP_IDS_INV_CLEAR_QUERY_VER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
ASP_IDS_INV_SHOW_QUERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
ASP_IDS_INV_SHOW_QUERY_VER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
x Copyright 2015, Juniper Networks, Inc.

Table of Contents
ASP_IDS_LIMIT_FLOW_RATE_BY_DEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
ASP_IDS_LIMIT_FLOW_RATE_BY_PAIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
ASP_IDS_LIMIT_FLOW_RATE_BY_SRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
ASP_IDS_LIMIT_OPEN_FLOWS_BY_DEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
ASP_IDS_LIMIT_OPEN_FLOWS_BY_PAIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
ASP_IDS_LIMIT_OPEN_FLOWS_BY_SRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
ASP_IDS_LIMIT_PKT_RATE_BY_DEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
ASP_IDS_LIMIT_PKT_RATE_BY_PAIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
ASP_IDS_LIMIT_PKT_RATE_BY_SRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
ASP_IDS_NO_MEM_SHOW_CMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
ASP_IDS_NULL_CLEAR_QUERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
ASP_IDS_NULL_SHOW_QUERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
ASP_IDS_RULE_MATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
ASP_IDS_SYN_COOKIE_OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
ASP_IDS_SYN_COOKIE_ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
ASP_IDS_TCP_SYN_ATTACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
ASP_L2TP_MESSAGE_INCOMPLETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
ASP_L2TP_NO_MEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
ASP_L2TP_OBJ_CAC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
ASP_L2TP_STATS_BULK_QUERY_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
ASP_L2TP_STATS_VERSION_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
ASP_L2TP_TUN_GRP_ADD_FAIL_ALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
ASP_L2TP_TUN_GRP_ADD_FAIL_EXISTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
ASP_L2TP_TUN_GRP_CHG_FAIL_ALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
ASP_L2TP_TUN_GRP_CHG_FAIL_INVLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
ASP_L2TP_TUN_GRP_DEL_FAIL_INVLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
ASP_NAT_OUTOF_ADDRESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
ASP_NAT_OUTOF_PORTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
ASP_NAT_POOL_RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
ASP_NAT_PORT_BLOCK_ACTIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
ASP_NAT_PORT_BLOCK_ALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
ASP_NAT_PORT_BLOCK_RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
ASP_NAT_RULE_MATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
ASP_PCP_NAT_MAP_CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
ASP_PCP_NAT_MAP_DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
ASP_PCP_TPC_ALLOC_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
ASP_PCP_TPC_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
ASP_PGCP_IPC_MSG_WRITE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
ASP_PGCP_IPC_PIPE_WRITE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
ASP_SFW_ALG_LEVEL_ADJUSTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
ASP_SFW_ALG_PROMOTION_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
ASP_SFW_APP_MSG_TOO_LONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
ASP_SFW_CHANGE_INACTIVITY_TIMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
ASP_SFW_CREATE_ACCEPT_FLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
ASP_SFW_CREATE_DISCARD_FLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
ASP_SFW_CREATE_REJECT_FLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
ASP_SFW_DELETE_FLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
ASP_SFW_DROP_FLOW_DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
ASP_SFW_FTP_ACTIVE_ACCEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Copyright 2015, Juniper Networks, Inc. xi

ASP_SFW_FTP_PASSIVE_ACCEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
ASP_SFW_ICMP_ERROR_DROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
ASP_SFW_ICMP_HEADER_LEN_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
ASP_SFW_ICMP_PACKET_ERROR_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
ASP_SFW_IP_FRAG_ASSEMBLY_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
ASP_SFW_IP_FRAG_OVERLAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
ASP_SFW_IP_OPTION_DROP_PACKET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
ASP_SFW_IP_PACKET_CHECKSUM_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
ASP_SFW_IP_PACKET_DST_BAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
ASP_SFW_IP_PACKET_FRAG_LEN_INV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
ASP_SFW_IP_PACKET_INCORRECT_LEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
ASP_SFW_IP_PACKET_LAND_ATTACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
ASP_SFW_IP_PACKET_NOT_VERSION_4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
ASP_SFW_IP_PACKET_PROTOCOL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
ASP_SFW_IP_PACKET_SRC_BAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
ASP_SFW_IP_PACKET_TOO_LONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
ASP_SFW_IP_PACKET_TOO_SHORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
ASP_SFW_IP_PACKET_TTL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
ASP_SFW_NEW_POLICY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
ASP_SFW_NO_IP_PACKET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
ASP_SFW_NO_POLICY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
ASP_SFW_NO_RULE_DROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
ASP_SFW_PING_DUPLICATED_SEQNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
ASP_SFW_PING_MISMATCHED_SEQNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
ASP_SFW_PING_OUTOF_SEQNO_CACHE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
ASP_SFW_POLICY_REJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
ASP_SFW_RULE_ACCEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
ASP_SFW_RULE_DISCARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
ASP_SFW_RULE_REJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
ASP_SFW_SYN_DEFENSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
ASP_SFW_TCP_BAD_SYN_COOKIE_RESP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
ASP_SFW_TCP_FLAGS_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
ASP_SFW_TCP_HEADER_LEN_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
ASP_SFW_TCP_NON_SYN_FIRST_PACKET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
ASP_SFW_TCP_PORT_ZERO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
ASP_SFW_TCP_RECONSTRUCT_DROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
ASP_SFW_TCP_SCAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
ASP_SFW_TCP_SEQNO_AND_FLAGS_ZERO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
ASP_SFW_TCP_SEQNO_ZERO_FLAGS_SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
ASP_SFW_UDP_HEADER_LEN_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
ASP_SFW_UDP_PORT_ZERO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
ASP_SFW_UDP_SCAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
ASP_SFW_VERY_BAD_PACKET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
ASP_SVC_SET_MAX_FLOWS_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Chapter 13 AUDITD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
AUDITD_RADIUS_AV_AUTH_TYPE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
AUDITD_RADIUS_AV_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
AUDITD_RADIUS_AV_PORT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
xii Copyright 2015, Juniper Networks, Inc.

Table of Contents
AUDITD_RADIUS_OPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
AUDITD_RADIUS_REQ_CREATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
AUDITD_RADIUS_REQ_DROPPED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
AUDITD_RADIUS_REQ_SEND_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
AUDITD_RADIUS_REQ_TIMED_OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
AUDITD_RADIUS_SERVER_ADD_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
AUDITD_SOCKET_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
AUDITD_TACPLUS_SHM_CREATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Chapter 14 AUTHD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
AUTHD_ACCOUNTING_STATE_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
AUTHD_ACCT_ON_ACK_NOT_RECEIVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
AUTHD_AUTH_CREATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
AUTHD_AUTH_SERVER_STATUS_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
AUTHD_RADIUS_GETHOSTNAME_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
AUTHD_SERVER_INIT_BIND_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
AUTHD_SERVER_INIT_LISTEN_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Chapter 15 AUTOCONFD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
AUTOCONFD_AUTHENTICATE_LICENSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Chapter 16 AUTOD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
AUTOD_BIND_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
AUTOD_HOSTNAME_EXPANSION_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
AUTOD_RECV_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
AUTOD_RES_MKQUERY_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
AUTOD_SEND_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
AUTOD_SOCKET_CREATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Chapter 17 AV System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
AV_PATTERN_GET_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
AV_PATTERN_KEY_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
AV_PATTERN_KL_CHECK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
AV_PATTERN_TOO_BIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
AV_PATTERN_UPDATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
AV_PATTERN_WRITE_FS_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
AV_SCANNER_READY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
AV_VIRUS_DETECTED_MT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Chapter 18 BBE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
BBE_MIBD_TRAP_HEADER_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
BBE_MIBD_TRAP_SEND_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Chapter 19 BFDD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
BFDD_MIRROR_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
BFDD_MIRROR_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
BFDD_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
BFDD_TRAP_MHOP_STATE_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
BFDD_TRAP_MHOP_STATE_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
BFDD_TRAP_SHOP_STATE_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
BFDD_TRAP_SHOP_STATE_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Copyright 2015, Juniper Networks, Inc. xiii

BFDD_TRAP_STATE_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
BFDD_TRAP_STATE_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
BFDD_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Chapter 20 BGP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
BGP_ADDR_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
BGP_ALLOC_BUFFER_ALREADY_EXISTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
BGP_BIND_FAILED_ADDR_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
BGP_CEASE_PREFIX_LIMIT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
BGP_CFG_PATH_ATTRIBUTE_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
BGP_CONNECT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
BGP_CONNECT_GET_SOCK_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
BGP_CONNECT_SOCK_SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
BGP_COPY_BUFFER_ALREADY_EXISTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
BGP_ERROR_SENDING_KEEPALIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
BGP_ERROR_UNEXPECTED_LOCAL_PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
BGP_FLUSH_FAILED_AFTER_RETRYING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
BGP_FREE_NONEXISTENT_BUFFER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
BGP_GATHER_FLUSH_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
BGP_IGNORING_INVALID_PREFIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
BGP_NLRI_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
BGP_NO_ADDRESS_BOUND_TO_SOCKET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
BGP_NO_INCOMING_INTERFACE_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
BGP_OPEN_INTERNAL_VERSION_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
BGP_ORF_BAD_MSG_HEADER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
BGP_ORF_LEN_EXCEEDS_MAX_PFXLEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
BGP_ORF_MAXLEN_EXCEEDS_MAX_PFXLEN . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
BGP_ORF_MAXLEN_LESS_THAN_MINLEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
BGP_ORF_MAX_PFXLEN_LESS_THAN_LEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
BGP_ORF_MINLEN_EXCEEDS_MAX_PFXLEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
BGP_ORF_MINLEN_LESS_THAN_LEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
BGP_ORF_PREFIX_BAD_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
BGP_ORF_PREFIX_INVALID_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
BGP_ORF_PREFIX_LESS_THAN_MINLEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
BGP_ORF_PREFIX_LIMIT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
BGP_PREFIX_LIMIT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
BGP_PREFIX_THRESH_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
BGP_REFRESH_FOR_UNNEGOTIATED_NLRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
BGP_RESET_PENDING_CONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
BGP_SET_INTERFACE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
BGP_SOCK_ADDR_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
BGP_SPOOL_FLUSH_CONNECTION_CLOSED . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
BGP_SPOOL_FLUSH_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
BGP_UNEXPECTED_MESSAGE_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
BGP_UNUSABLE_ASPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
BGP_UNUSABLE_NEXTHOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
BGP_UPDATE_CONTAINS_GARBAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
BGP_UPDATE_MISSING_PREFIXES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
BGP_WRITE_CONNECTION_CLOSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
xiv Copyright 2015, Juniper Networks, Inc.

Table of Contents
BGP_WRITE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
BGP_WRITE_FAILED_AFTER_RETRYING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
BGP_WRITE_WOULD_BLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Chapter 21 BOOTPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
BOOTPD_ARG_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
BOOTPD_BAD_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
BOOTPD_BOOTSTRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
BOOTPD_CONFIG_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
BOOTPD_CONF_OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
BOOTPD_DUP_PIC_SLOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
BOOTPD_DUP_REV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
BOOTPD_DUP_SLOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
BOOTPD_HWDB_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
BOOTPD_MODEL_CHK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
BOOTPD_NEW_CONF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
BOOTPD_NO_BOOTSTRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
BOOTPD_NO_CONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
BOOTPD_PARSE_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
BOOTPD_REPARSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
BOOTPD_SELECT_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
BOOTPD_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Chapter 22 CFMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
CFMD_CCM_DEFECT_AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
CFMD_CCM_DEFECT_CROSS_CONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
CFMD_CCM_DEFECT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
CFMD_CCM_DEFECT_MAC_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
CFMD_CCM_DEFECT_NONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
CFMD_CCM_DEFECT_RDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
CFMD_CCM_DEFECT_RMEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
CFMD_CCM_DEFECT_UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
CFMD_PPM_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
CFMD_PPM_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Chapter 23 CHASSISD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
CHASSISD_ACQUIRE_MASTERSHIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
CHASSISD_ANTICF_PIM_CHECK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
CHASSISD_ANTICF_RE_CHECK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
CHASSISD_ANTICF_RE_ROM_READ_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
CHASSISD_ANTICF_RE_SHA_READ_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
CHASSISD_ANTICF_ROM_READ_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
CHASSISD_ANTICF_SHA_READ_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
CHASSISD_ARGUMENT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
CHASSISD_BLOWERS_SPEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
CHASSISD_BLOWERS_SPEED_FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
CHASSISD_BLOWERS_SPEED_MEDIUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
CHASSISD_BUS_DEVICE_OPEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
CHASSISD_CB_CLOCK_CHECKSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
CHASSISD_CB_MASTER_BP_IGNORED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Copyright 2015, Juniper Networks, Inc. xv

CHASSISD_CB_READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
CHASSISD_CB_RE_ONLINE_BP_IGNORED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
CHASSISD_CFEB_POWER_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
CHASSISD_CLEAR_CONFIG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
CHASSISD_CLOCK_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
CHASSISD_CLOCK_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
CHASSISD_CLOCK_RESET_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
CHASSISD_CMB_READBACK_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
CHASSISD_COMMAND_ACK_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
CHASSISD_COMMAND_ACK_SFM_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
CHASSISD_CONCAT_MODE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
CHASSISD_CONFIG_ACCESS_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
CHASSISD_CONFIG_CHANGE_IFDEV_DEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
CHASSISD_CONFIG_INIT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
CHASSISD_CONFIG_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
CHASSISD_DEVICE_OPEN_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
CHASSISD_EXEC_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
CHASSISD_EXISTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
CHASSISD_EXISTS_TERM_OTHER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
CHASSISD_FAN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
CHASSISD_FASIC_CONFIG_COMPLETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
CHASSISD_FASIC_FTOKEN_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
CHASSISD_FASIC_FTOKEN_INIT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
CHASSISD_FASIC_HSL_CONFIG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
CHASSISD_FASIC_HSL_LINK_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
CHASSISD_FASIC_INIT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
CHASSISD_FASIC_INPUT_DROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
CHASSISD_FASIC_OUTPUT_DROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
CHASSISD_FASIC_PIO_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
CHASSISD_FASIC_PIO_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
CHASSISD_FASIC_PLL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
CHASSISD_FASIC_RESET_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
CHASSISD_FASIC_SRAM_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
CHASSISD_FASIC_VERSION_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
CHASSISD_FCHIP_CONFIG_COMPLETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
CHASSISD_FCHIP_CONFIG_MD_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
CHASSISD_FCHIP_CONFIG_RATE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
CHASSISD_FCHIP_CONFIG_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
CHASSISD_FCHIP_FTOKEN_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
CHASSISD_FCHIP_FTOKEN_INIT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
CHASSISD_FCHIP_HSR_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
CHASSISD_FCHIP_HSR_INIT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
CHASSISD_FCHIP_HSR_INIT_LINK_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
CHASSISD_FCHIP_HSR_RESET_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
CHASSISD_FCHIP_HST_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
CHASSISD_FCHIP_HST_INIT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
CHASSISD_FCHIP_HST_INIT_LINK_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
CHASSISD_FCHIP_HST_RESET_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
CHASSISD_FCHIP_INIT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
xvi Copyright 2015, Juniper Networks, Inc.

Table of Contents
CHASSISD_FCHIP_LINK_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
CHASSISD_FCHIP_MONITOR_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
CHASSISD_FCHIP_PIO_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
CHASSISD_FCHIP_PIO_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
CHASSISD_FCHIP_POLL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
CHASSISD_FCHIP_RATE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
CHASSISD_FCHIP_SIB_NOT_STARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
CHASSISD_FCHIP_VERSION_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
CHASSISD_FEB_REVERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
CHASSISD_FEB_SWITCHOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
CHASSISD_FHSR_READ_REG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
CHASSISD_FHSR_WRITE_REG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
CHASSISD_FHST_READ_REG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
CHASSISD_FHST_WRITE_REG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
CHASSISD_FILE_OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
CHASSISD_FILE_STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
CHASSISD_FM_ACTION_FPC_OFFLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
CHASSISD_FM_ACTION_FPC_ONLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
CHASSISD_FM_ACTION_FPC_POWER_OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
CHASSISD_FM_ACTION_FPC_RECOVERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
CHASSISD_FM_ACTION_FPC_RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
CHASSISD_FM_ACTION_PLANE_OFFLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
CHASSISD_FM_ACTION_PLANE_ONLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
CHASSISD_FM_BAD_STATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
CHASSISD_FM_DETECT_FPC_FABRIC_DEGRADED . . . . . . . . . . . . . . . . . . . . . . . 198
CHASSISD_FM_DETECT_PLANES_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
CHASSISD_FM_DETECT_UNREACHABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
CHASSISD_FM_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
CHASSISD_FM_ERROR_CLOS_F13_HSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
CHASSISD_FM_ERROR_CLOS_F13_HST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
CHASSISD_FM_ERROR_CLOS_F2_HSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
CHASSISD_FM_ERROR_CLOS_F2_HST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
CHASSISD_FM_ERROR_F13_FB_HSR_TXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
CHASSISD_FM_ERROR_F13_FB_RX_VC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
CHASSISD_FM_ERROR_F13_FB_TXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
CHASSISD_FM_ERROR_F13_FB_TX_VC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
CHASSISD_FM_ERROR_F13_VC_PWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
CHASSISD_FM_ERROR_LCC_SIB_CBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
CHASSISD_FM_ERROR_LCC_SIB_HSR_PFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
CHASSISD_FM_ERROR_LCC_SIB_HSR_XC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
CHASSISD_FM_ERROR_LCC_SIB_OPTICS_FAULT . . . . . . . . . . . . . . . . . . . . . . . . 204
CHASSISD_FM_ERROR_LCC_SIB_RX_OPTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
CHASSISD_FM_ERROR_LCC_SIB_TX_OPTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
CHASSISD_FM_ERROR_SC_CLOS_F13_HSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
CHASSISD_FM_ERROR_SC_CLOS_F13_HST . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
CHASSISD_FM_ERROR_SC_CLOS_F2_HSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
CHASSISD_FM_ERROR_SC_CLOS_F2_HST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
CHASSISD_FM_ERROR_SC_SIB_CBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
CHASSISD_FM_ERROR_SC_SIB_HSR_XC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Copyright 2015, Juniper Networks, Inc. xvii

CHASSISD_FM_ERROR_SC_SIB_OPTICS_FAULT . . . . . . . . . . . . . . . . . . . . . . . . . 207
CHASSISD_FM_ERROR_SC_SIB_RX_OPTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
CHASSISD_FM_ERROR_SC_SIB_TX_OPTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
CHASSISD_FM_ERROR_SIB_L_FB_HSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
CHASSISD_FM_ERROR_SIB_L_FB_RX_VC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
CHASSISD_FM_ERROR_SIB_L_FB_SMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
CHASSISD_FM_ERROR_SIB_L_FB_TXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
CHASSISD_FM_ERROR_SIB_L_FB_TX_VC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
CHASSISD_FM_ERROR_SIB_L_HSR_PFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
CHASSISD_FM_ERROR_SIB_L_HSR_TXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
CHASSISD_FM_ERROR_SIB_L_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
CHASSISD_FM_ERROR_SIB_L_VC_PWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
CHASSISD_FM_ERROR_SIB_S_FB_HSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
CHASSISD_FM_ERROR_SIB_S_FB_SMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
CHASSISD_FM_FABRIC_DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
CHASSISD_FM_FPC_FABRIC_DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
CHASSISD_FM_MEMORY_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
CHASSISD_FM_SIB_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
CHASSISD_FM_SIB_FPC_TYPE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
CHASSISD_FPC_JAM_HSL2_PARAMS_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . 214
CHASSISD_FPC_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
CHASSISD_FPC_OPTICS_HOT_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
CHASSISD_FPC_PIC_DETECT_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
CHASSISD_FPC_TYPE_SIB_TYPE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
CHASSISD_FRU_ALREADY_OFFLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
CHASSISD_FRU_ALREADY_ONLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
CHASSISD_FRU_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
CHASSISD_FRU_FIRE_TEMP_CONDITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
CHASSISD_FRU_HIGH_TEMP_CONDITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
CHASSISD_FRU_INVALID_SLOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
CHASSISD_FRU_IO_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
CHASSISD_FRU_IO_OFFSET_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
CHASSISD_FRU_IPC_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
CHASSISD_FRU_OFFLINE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
CHASSISD_FRU_OFFLINE_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
CHASSISD_FRU_OFFLINE_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
CHASSISD_FRU_ONLINE_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
CHASSISD_FRU_OVER_TEMP_CONDITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
CHASSISD_FRU_STEP_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
CHASSISD_FRU_UNRESPONSIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
CHASSISD_FRU_UNRESPONSIVE_RETRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
CHASSISD_FRU_UNSUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
CHASSISD_FRU_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
CHASSISD_GASIC_ID_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
CHASSISD_GBUS_NOT_READY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
CHASSISD_GBUS_READBACK_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
CHASSISD_GBUS_RESET_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
CHASSISD_GBUS_SANITY_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
CHASSISD_GENERIC_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
xviii Copyright 2015, Juniper Networks, Inc.

Table of Contents
CHASSISD_GENERIC_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
CHASSISD_GETTIMEOFDAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
CHASSISD_GRES_UNSUPP_PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
CHASSISD_HIGH_TEMP_CONDITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
CHASSISD_HOST_TEMP_READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
CHASSISD_HSR_CONFIG_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
CHASSISD_HSR_CONFIG_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
CHASSISD_HSR_ELEMENTS_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
CHASSISD_HSR_FIFO_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
CHASSISD_I2CS_READBACK_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
CHASSISD_I2C_BAD_IDEEPROM_FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
CHASSISD_I2C_FIC_PRESENCE_READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
CHASSISD_I2C_GENERIC_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
CHASSISD_I2C_INVALID_ASSEMBLY_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
CHASSISD_I2C_IOCTL_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
CHASSISD_I2C_IO_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
CHASSISD_I2C_MIDPLANE_CORRUPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
CHASSISD_I2C_RANGE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
CHASSISD_I2C_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
CHASSISD_I2C_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
CHASSISD_IDEEPROM_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
CHASSISD_IFDEV_CREATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
CHASSISD_IFDEV_CREATE_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
CHASSISD_IFDEV_DETACH_ALL_PSEUDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
CHASSISD_IFDEV_DETACH_FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
CHASSISD_IFDEV_DETACH_PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
CHASSISD_IFDEV_DETACH_PSEUDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
CHASSISD_IFDEV_DETACH_TLV_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
CHASSISD_IFDEV_GETBYNAME_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
CHASSISD_IFDEV_GET_BY_INDEX_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
CHASSISD_IFDEV_GET_BY_NAME_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
CHASSISD_IFDEV_NO_MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
CHASSISD_IFDEV_RETRY_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
CHASSISD_IFDEV_RTSLIB_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
CHASSISD_IFILTER_INSTALL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
CHASSISD_IOCTL_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
CHASSISD_IPC_ANNOUNCE_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
CHASSISD_IPC_CONNECTION_DROPPED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
CHASSISD_IPC_DAEMON_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
CHASSISD_IPC_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
CHASSISD_IPC_FLUSH_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
CHASSISD_IPC_MSG_DROPPED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
CHASSISD_IPC_MSG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
CHASSISD_IPC_MSG_FRU_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
CHASSISD_IPC_MSG_QFULL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
CHASSISD_IPC_MSG_UNHANDLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
CHASSISD_IPC_UNEXPECTED_MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
CHASSISD_IPC_UNEXPECTED_RECV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
CHASSISD_IPC_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Copyright 2015, Juniper Networks, Inc. xix

CHASSISD_IPC_WRITE_ERR_NO_PIPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
CHASSISD_IPC_WRITE_ERR_NULL_ARGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
CHASSISD_ISSU_BLOB_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
CHASSISD_ISSU_DAEMON_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
CHASSISD_ISSU_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
CHASSISD_ISSU_FRU_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
CHASSISD_ISSU_FRU_IPC_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
CHASSISD_JTREE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
CHASSISD_LCC_RELEASE_MASTERSHIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
CHASSISD_LOST_MASTERSHIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
CHASSISD_MAC_ADDRESS_AE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
CHASSISD_MAC_ADDRESS_ATS_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
CHASSISD_MAC_ADDRESS_CBP_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
CHASSISD_MAC_ADDRESS_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
CHASSISD_MAC_ADDRESS_FABRIC_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
CHASSISD_MAC_ADDRESS_IRB_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
CHASSISD_MAC_ADDRESS_PIP_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
CHASSISD_MAC_ADDRESS_PLT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
CHASSISD_MAC_ADDRESS_SWFAB_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
CHASSISD_MAC_ADDRESS_VIRB_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
CHASSISD_MAC_ADDRESS_VLAN_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
CHASSISD_MAC_ADDRESS_VTEP_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
CHASSISD_MAC_DEFAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
CHASSISD_MAIN_THREAD_STALLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
CHASSISD_MALLOC_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
CHASSISD_MASTER_CG_REMOVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
CHASSISD_MASTER_PCG_REMOVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
CHASSISD_MASTER_SCG_REMOVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
CHASSISD_MBUS_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
CHASSISD_MCHASSIS_SWITCH_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
CHASSISD_MCS_INTR_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
CHASSISD_MGR_CONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
CHASSISD_MIC_OFFLINE_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
CHASSISD_MULTILINK_BUNDLES_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
CHASSISD_MXC_LINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
CHASSISD_NO_CGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
CHASSISD_NO_PCGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
CHASSISD_NO_SCGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
CHASSISD_OFFLINE_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
CHASSISD_OID_GEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
CHASSISD_OVER_TEMP_CONDITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
CHASSISD_OVER_TEMP_SHUTDOWN_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
CHASSISD_PARSE_COMPLETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
CHASSISD_PCI_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
CHASSISD_PDU_BREAKER_TRIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
CHASSISD_PDU_NOT_OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
CHASSISD_PEER_UNCONNECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
CHASSISD_PEM_BREAKER_TRIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
CHASSISD_PEM_IMPROPER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
xx Copyright 2015, Juniper Networks, Inc.

Table of Contents
CHASSISD_PEM_INPUT_BAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
CHASSISD_PEM_NOT_SUFFICIENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
CHASSISD_PEM_OVERLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
CHASSISD_PEM_TEMPERATURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
CHASSISD_PEM_VOLTAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
CHASSISD_PFE_LAUNCH_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
CHASSISD_PIC_CMD_GIVEUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
CHASSISD_PIC_CMD_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
CHASSISD_PIC_CONFIG_CONFLICT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
CHASSISD_PIC_CONFIG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
CHASSISD_PIC_HWERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
CHASSISD_PIC_OFFLINE_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
CHASSISD_PIC_OID_GEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
CHASSISD_PIC_OID_UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
CHASSISD_PIC_PORT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
CHASSISD_PIC_RESET_ON_SWITCHOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
CHASSISD_PIC_SPEED_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
CHASSISD_PIC_VERSION_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
CHASSISD_PIDFILE_OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
CHASSISD_POWER_CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
CHASSISD_POWER_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
CHASSISD_POWER_ON_CHECK_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
CHASSISD_POWER_RATINGS_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
CHASSISD_PSD_RELEASE_MASTERSHIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
CHASSISD_PSM_NOT_OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
CHASSISD_PSM_NOT_OK_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
CHASSISD_PSM_TRIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
CHASSISD_PSU_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
CHASSISD_PSU_FAN_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
CHASSISD_PSU_INPUT_BAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
CHASSISD_PSU_OVERLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
CHASSISD_PSU_TEMPERATURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
CHASSISD_PSU_VOLTAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
CHASSISD_RANGE_CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
CHASSISD_RECONNECT_SUCCESSFUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
CHASSISD_RELEASE_MASTERSHIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
CHASSISD_RE_CONSOLE_FE_STORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
CHASSISD_RE_CONSOLE_ME_STORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
CHASSISD_RE_INIT_INVALID_RE_SLOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
CHASSISD_RE_OVER_TEMP_CONDITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
CHASSISD_RE_OVER_TEMP_SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
CHASSISD_RE_OVER_TEMP_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
CHASSISD_RE_WARM_TEMP_CONDITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
CHASSISD_ROOT_MOUNT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
CHASSISD_RTS_SEQ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
CHASSISD_SBOARD_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
CHASSISD_SENSOR_RANGE_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
CHASSISD_SERIAL_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
CHASSISD_SFC_FPM_CHCFG_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Copyright 2015, Juniper Networks, Inc. xxi

CHASSISD_SFM_MODE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
CHASSISD_SFM_NOT_ONLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
CHASSISD_SHUTDOWN_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
CHASSISD_SIB_INVALID_SLOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
CHASSISD_SIGPIPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
CHASSISD_SMB_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
CHASSISD_SMB_INVALID_PS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
CHASSISD_SMB_IOCTL_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
CHASSISD_SMB_READ_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
CHASSISD_SNMP_TRAP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
CHASSISD_SNMP_TRAP10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
CHASSISD_SNMP_TRAP6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
CHASSISD_SPI_IOCTL_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
CHASSISD_SPMB_RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
CHASSISD_SPMB_RESTART_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
CHASSISD_SSB_FAILOVERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
CHASSISD_STANDALONE_FPC_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
CHASSISD_SYSCTL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
CHASSISD_TEMP_HOT_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
CHASSISD_TEMP_SENSOR_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
CHASSISD_TERM_SIGNAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
CHASSISD_TIMER_CLR_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
CHASSISD_TIMER_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
CHASSISD_TIMER_VAL_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
CHASSISD_UNEXPECTED_EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
CHASSISD_UNEXPECTED_VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
CHASSISD_UNSUPPORTED_FPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
CHASSISD_UNSUPPORTED_MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
CHASSISD_UNSUPPORTED_PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
CHASSISD_UNSUPPORTED_PIC_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
CHASSISD_UNSUPPORTED_SIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
CHASSISD_VCHASSIS_CONVERT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
CHASSISD_VCHASSIS_LICENSE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
CHASSISD_VCHASSIS_MEMBER_LIST_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . 271
CHASSISD_VCHASSIS_MEMBER_OP_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
CHASSISD_VCHASSIS_MEMBER_UPDATE_NOTICE . . . . . . . . . . . . . . . . . . . . . . 272
CHASSISD_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
CHASSISD_VOLTAGE_READ_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
CHASSISD_VOLTAGE_SENSOR_INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
CHASSISD_VSERIES_LICENSE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
CHASSISD_ZONE_BLOWERS_SPEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
CHASSISD_ZONE_BLOWERS_SPEED_FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
CHASSISD_ZONE_BLOWERS_SPEED_OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Chapter 24 CHASSISM System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
CHASSISM_SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
xxii Copyright 2015, Juniper Networks, Inc.

Table of Contents
Chapter 25 CLKSYNCD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

CLKSYNCD_EVENT_BITS_DPLL_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
CLKSYNCD_EVENT_DPLL_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
CLKSYNCD_EVENT_LED_STATE_CHANGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
CLKSYNCD_EVENT_PRI_REF_CHANGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
CLKSYNCD_EVENT_PRI_SRC_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
CLKSYNCD_EVENT_PTP_CLOCK_ACCU_CHG . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
CLKSYNCD_EVENT_PTP_CLOCK_CLASS_CHG . . . . . . . . . . . . . . . . . . . . . . . . . . 278
CLKSYNCD_EVENT_PTP_GM_CHG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
CLKSYNCD_EVENT_PTP_HYBRID_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
CLKSYNCD_EVENT_PTP_SERVO_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
CLKSYNCD_EVENT_RX_QL_CHANGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
CLKSYNCD_EVENT_SEC_REF_CHANGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
CLKSYNCD_EVENT_SEC_SRC_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
CLKSYNCD_EVENT_SQUELCH_CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
CLKSYNCD_EVENT_SQUELCH_SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
CLKSYNCD_EVENT_SYNCE_DPLL_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
CLKSYNCD_EVENT_TX_QL_CHANGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
CLKSYNCD_FAULT_ACBC_NOT_COMPATIBLE . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
CLKSYNCD_FAULT_CPLD_NOT_COMPATIBLE . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
CLKSYNCD_FAULT_EFD_CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
CLKSYNCD_FAULT_EFD_SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
CLKSYNCD_FAULT_LOS_CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
CLKSYNCD_FAULT_LOS_SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
CLKSYNCD_FAULT_LO_ESMC_CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
CLKSYNCD_FAULT_LO_ESMC_SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
CLKSYNCD_FAULT_LTI_CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
CLKSYNCD_FAULT_LTI_SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
CLKSYNCD_FAULT_PRI_SRC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
CLKSYNCD_FAULT_PTP_UNI_NEG_RATE_REJ_CLEAR . . . . . . . . . . . . . . . . . . . . 284
CLKSYNCD_FAULT_PTP_UNI_NEG_RATE_REJ_SET . . . . . . . . . . . . . . . . . . . . . . . 284
CLKSYNCD_FAULT_QL_FAIL_CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
CLKSYNCD_FAULT_QL_FAIL_SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
CLKSYNCD_FAULT_SEC_SRC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Chapter 26 COSD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
COSD_AGGR_CONFIG_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
COSD_CHASSIS_SCHED_MAP_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
COSD_CLASSIFIER_NO_SUPPORT_LSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
COSD_CLASS_8021P_UNSUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
COSD_CLASS_NO_SUPPORT_IFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
COSD_CLASS_NO_SUPPORT_L3_IFL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
COSD_CONF_OPEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
COSD_DB_OPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
COSD_EXACT_RATE_UNSUPP_INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
COSD_EXACT_RATE_UNSUPP_SESSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
COSD_EXP_RW_L2_IFL_NOT_SUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
COSD_FABRIC_QUEUE_OVERFLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
COSD_FRAGMENTATION_MAP_CONFLICT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Copyright 2015, Juniper Networks, Inc. xxiii

COSD_HIGH_PRIO_QUEUES_INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
COSD_HIGH_PRIO_QUEUES_SESSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
COSD_IFD_OUTPUT_SHAPING_RATE_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
COSD_IFD_SHAPER_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
COSD_INTERFACE_NO_MEDIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
COSD_L2TP_COS_NOT_CONFIGURED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
COSD_L2TP_COS_NOT_SUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
COSD_L2TP_SHAPING_NOT_CONFIGURED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
COSD_LARGE_DELAY_BUFFER_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
COSD_MALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
COSD_MAX_FORWARDING_CLASSES_ABC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
COSD_MPLS_DSCP_CLASS_NO_SUPPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
COSD_MULTILINK_CLASS_CONFLICT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
COSD_NULL_INPUT_ARGUMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
COSD_OUT_OF_DEDICATED_QUEUES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
COSD_RATE_LIMIT_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
COSD_RATE_LIMIT_NOT_SUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
COSD_REWRITE_RULE_LIMIT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
COSD_RL_IFL_NEEDS_SHAPING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
COSD_SCHEDULER_MAP_CONFLICT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
COSD_SCHED_AVG_CONST_UNSUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . 298
COSD_SCHED_MAP_GROUP_CONFLICT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
COSD_SHAPER_GROUP_CONFLICT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
COSD_STREAM_IFD_CREATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
COSD_TIMER_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
COSD_TRICOLOR_ALWAYS_ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
COSD_TRICOLOR_NOT_SUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
COSD_TX_QUEUE_RATES_TOO_HIGH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
COSD_UNKNOWN_CLASSIFIER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
COSD_UNKNOWN_REWRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
COSD_UNKNOWN_TRAFFIC_CLASS_MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
COSD_UNKNOWN_TRANSLATION_TABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
COSD_WAN_QUEUE_OVERFLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Chapter 27 DCBX System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
DCBX_PFC_DISABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
DCBX_PFC_ENABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
DCBX_VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Chapter 28 DCD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
DCD_AE_CONFIG_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
DCD_FWD_CLASS_ACC_NOT_SUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
DCD_FWD_CLASS_ACC_NOT_SUPPORTED_IFL . . . . . . . . . . . . . . . . . . . . . . . . . 305
DCD_GRE_CONFIG_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
DCD_GRE_CONFIG_NOT_SUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
DCD_MALLOC_FAILED_INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
DCD_PARSE_CFG_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
DCD_PARSE_EMERGENCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
DCD_PARSE_ERROR_CLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
DCD_PARSE_ERROR_HIER_SCHEDULER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
xxiv Copyright 2015, Juniper Networks, Inc.

Table of Contents
DCD_PARSE_ERROR_IFLSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
DCD_PARSE_ERROR_MAX_HIER_LEVELS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
DCD_PARSE_ERROR_MAX_HIER_LEVELS_2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
DCD_PARSE_ERROR_SCHEDULER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
DCD_PARSE_ERROR_SCHEDULER_LIMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
DCD_PARSE_ERROR_VLAN_TAGGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
DCD_PARSE_MINI_EMERGENCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
DCD_PARSE_STATE_EMERGENCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
DCD_PARSE_WARN_INCOMPATIBLE_CFG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
DCD_RLT_CONFIG_UNSUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Chapter 29 DDOS System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
DDOS_PROTOCOL_VIOLATION_CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
DDOS_PROTOCOL_VIOLATION_SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
DDOS_RTSOCK_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
DDOS_SCFD_FLOW_AGGREGATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
DDOS_SCFD_FLOW_CLEARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
DDOS_SCFD_FLOW_DEAGGREGATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
DDOS_SCFD_FLOW_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
DDOS_SCFD_FLOW_RETURN_NORMAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
DDOS_SCFD_FLOW_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Chapter 30 DFCD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
DFCD_FTAP_PIC_UNSUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
DFCD_GENCFG_MALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
DFCD_GENCFG_WRITE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
DFCD_LINH_MALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
DFCD_LI_NEXT_HOP_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
DFCD_NEXT_HOP_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
DFCD_NEXT_HOP_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
DFCD_SAMPLE_CLASS_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
DFCD_SAMPLE_CLASS_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Chapter 31 DFWD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
DFWD_MALLOC_FAILED_INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
DFWD_PARSE_FILTER_EMERGENCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
DFWD_PARSE_STATE_EMERGENCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
DFWD_POLICER_LIMIT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Chapter 32 DHCPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
DHCPD_BIND_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
DHCPD_DEGRADED_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
DHCPD_MEMORY_ALLOCATION_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
DHCPD_OPTION_HOST_NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
DHCPD_OPTION_LOG_SERVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
DHCPD_OPTION_NTP_SERVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
DHCPD_OVERLAY_CONFIG_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
DHCPD_OVERLAY_PARSE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
DHCPD_RECVMSG_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
DHCPD_RTSOCK_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Copyright 2015, Juniper Networks, Inc. xxv

DHCPD_SENDMSG_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
DHCPD_SENDMSG_NOINT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
DHCPD_SETSOCKOPT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
DHCPD_SOCKET_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Chapter 33 DIAM System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
DIAM_PEER_CONN_STATE_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
DIAM_PEER_OUTQ_HIGH_WATERMARK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
DIAM_PEER_OUTQ_LOW_WATERMARK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
DIAM_PROFILE_STATE_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
DIAM_SPIC_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
DIAM_TARGET_STATE_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Chapter 34 DOT1XD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
DOT1XD_AUTH_SESSION_DELETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
DOT1XD_MKA_FAIL_ACTION_USER_ALLOWED . . . . . . . . . . . . . . . . . . . . . . . . . . 331
DOT1XD_MKA_FAIL_ACTION_USER_PROHIBITED . . . . . . . . . . . . . . . . . . . . . . . . 331
DOT1XD_MKA_SECURE_CHANNEL_CREATED . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
DOT1XD_MKA_SECURE_CHANNEL_DELETED . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
DOT1XD_RCVD_EAPLOGOF_ATHNTCTNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
DOT1XD_RCVD_EAPLOGOF_ATHNTICTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
DOT1XD_RCVD_EAPLOGOF_CONNECTNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
DOT1XD_USR_ACCESS_DENIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
DOT1XD_USR_ATHNTICTD_GST_VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
DOT1XD_USR_AUTHENTICATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
DOT1XD_USR_ON_SRVR_FAIL_VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
DOT1XD_USR_ON_SRVR_REJECT_VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
DOT1XD_USR_SESSION_DISCONNECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
DOT1XD_USR_SESSION_HELD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
DOT1XD_USR_UNATHNTCTD_CLI_CLRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Chapter 35 DYNAMIC System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
DYNAMIC_VPN_AUTH_CONNECT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
DYNAMIC_VPN_AUTH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
DYNAMIC_VPN_AUTH_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
DYNAMIC_VPN_AUTH_MUL_CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
DYNAMIC_VPN_AUTH_NO_CONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
DYNAMIC_VPN_AUTH_NO_LICENSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
DYNAMIC_VPN_AUTH_OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
DYNAMIC_VPN_CLIENT_CONFIG_WRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
DYNAMIC_VPN_CONN_DEL_NOTIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
DYNAMIC_VPN_CONN_DEL_REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
DYNAMIC_VPN_CONN_EST_NOTIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
DYNAMIC_VPN_INIT_SUCCESSFUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
DYNAMIC_VPN_LICENSE_ASSIGNED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
DYNAMIC_VPN_LICENSE_CHECK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
DYNAMIC_VPN_LICENSE_CHECK_OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
DYNAMIC_VPN_LICENSE_EXHAUSTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
DYNAMIC_VPN_LICENSE_FREED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
DYNAMIC_VPN_LICENSE_FREE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
xxvi Copyright 2015, Juniper Networks, Inc.

Table of Contents
DYNAMIC_VPN_LICENSE_FREE_OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
DYNAMIC_VPN_LICENSE_GET_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
DYNAMIC_VPN_LICENSE_GET_OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
DYNAMIC_VPN_LICENSE_INSTALLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
DYNAMIC_VPN_LICENSE_REQUIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
DYNAMIC_VPN_LICENSE_UNINSTALLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Chapter 36 ESWD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
ESWD_BPDU_BLOCK_ERROR_DISABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
ESWD_BPDU_BLOCK_ERROR_ENABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
ESWD_DAI_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
ESWD_DHCP_UNTRUSTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
ESWD_GLOBAL_MAC_LIMIT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
ESWD_INVALID_MAC_ADDRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
ESWD_LEARNT_FDB_MEMORY_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
ESWD_MAC_LIMIT_ALERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
ESWD_MAC_LIMIT_BLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
ESWD_MAC_LIMIT_DROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
ESWD_MAC_LIMIT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
ESWD_MAC_MOVE_LIMIT_BLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
ESWD_MAC_MOVE_LIMIT_DROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
ESWD_MAC_MOVE_LIMIT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
ESWD_MAC_SMAC_BRIDGE_MAC_IDENTICAL . . . . . . . . . . . . . . . . . . . . . . . . . . 345
ESWD_MIRROR_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
ESWD_MIRROR_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
ESWD_MODULE_SHUTDOWN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
ESWD_NDI_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
ESWD_OUT_OF_LOW_MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
ESWD_PPM_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
ESWD_PPM_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
ESWD_STATIC_FDB_MEMORY_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
ESWD_STP_BASE_MAC_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
ESWD_STP_LOOP_PROTECT_CLEARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
ESWD_STP_LOOP_PROTECT_IN_EFFECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
ESWD_STP_ROOT_PROTECT_CLEARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
ESWD_STP_ROOT_PROTECT_IN_EFFECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
ESWD_STP_STATE_CHANGE_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
ESWD_ST_CTL_BW_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
ESWD_ST_CTL_ERROR_DISABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
ESWD_ST_CTL_ERROR_ENABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
ESWD_ST_CTL_ERROR_IN_EFFECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
ESWD_ST_CTL_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
ESWD_VLAN_MAC_LIMIT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
ESWD_VMEMBER_MAC_LIMIT_DROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Chapter 37 EVENTD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
EVENTD_ACK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
EVENTD_ALARM_CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
EVENTD_ALARM_FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
EVENTD_AUDIT_DISABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Copyright 2015, Juniper Networks, Inc. xxvii

EVENTD_AUDIT_ENABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
EVENTD_AUDIT_SHOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
EVENTD_COMMAND_SUBSTITUTE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
EVENTD_CONFIG_CHANGE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
EVENTD_CONFIG_CHANGE_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
EVENTD_ESCRIPT_EXECUTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
EVENTD_ESCRIPT_NOT_CONFIGURED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
EVENTD_EVENT_SEND_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
EVENTD_FORK_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
EVENTD_JAIL_SOCKET_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
EVENTD_PARSE_CONTROL_INFO_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
EVENTD_PIPE_CREATION_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
EVENTD_POLICY_ACTION_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
EVENTD_POLICY_LIMIT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
EVENTD_POLICY_UPLOAD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
EVENTD_POPEN_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
EVENTD_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
EVENTD_REGEXP_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
EVENTD_REG_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
EVENTD_ROTATE_COMMAND_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
EVENTD_ROTATE_FORK_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
EVENTD_ROTATE_FORK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
EVENTD_SCRIPT_CHECKSUM_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
EVENTD_SECURITY_LOG_CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
EVENTD_SET_PROCESS_PRIV_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
EVENTD_SET_TIMER_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
EVENTD_SYSLOG_FWD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
EVENTD_TEST_ALARM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
EVENTD_TRANSFER_COMMAND_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
EVENTD_TRANSFER_FORK_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
EVENTD_TRANSFER_FORK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
EVENTD_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
EVENTD_XML_FILENAME_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Chapter 38 FABOAMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
FABOAMD_DEBUGGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Chapter 39 FC System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
FC_FABRIC_CREATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
FC_FABRIC_DELETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
FC_FABRIC_WWN_ASSIGNED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
FC_FABRIC_WWN_CLEARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
FC_FLOGI_VN_PORT_LOGIN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
FC_LOGICAL_INTERFACE_CREATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
FC_LOGICAL_INTERFACE_DELETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
FC_LOGICAL_INTERFACE_ISOLATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
FC_PROXY_NP_PORT_AVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
FC_PROXY_NP_PORT_LB_ADDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
FC_PROXY_NP_PORT_LB_REMOVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
FC_PROXY_NP_PORT_LOGIN_ABORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
xxviii Copyright 2015, Juniper Networks, Inc.

Table of Contents
FC_PROXY_NP_PORT_LOGIN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
FC_PROXY_NP_PORT_LOGOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
FC_PROXY_NP_PORT_NPIV_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
FC_PROXY_NP_PORT_OFFLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
FC_PROXY_NP_PORT_ONLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
FC_PROXY_NP_PORT_RESTORE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
FC_PROXY_NP_PORT_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
FC_PROXY_VN_PORT_LOGIN_ABORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
FC_PROXY_VN_PORT_LOGIN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Chapter 40 FCOE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
FCOE_LOGICAL_INTERFACE_CREATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
FCOE_LOGICAL_INTERFACE_DELETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
FCOE_LOGICAL_INTERFACE_ISOLATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Chapter 41 FIP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
FIP_ENODE_CLEARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
FIP_ENODE_FKA_TIMER_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
FIP_ENODE_LEARNED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
FIP_ENODE_TIMER_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
FIP_FCF_TIMER_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
FIP_MAX_FCOE_FILTERS_REACHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
FIP_MAX_SESSIONS_REACHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
FIP_PROTOCOL_STARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
FIP_PROTOCOL_STOPPED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
FIP_VN_PORT_FKA_TIMER_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
FIP_VN_PORT_LOGIN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
FIP_VN_PORT_SESSION_CLEARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
FIP_VN_PORT_SESSION_CREATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
FIP_VN_PORT_TIMER_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Chapter 42 FIPS System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
FIPS_KNOWN_ANSWER_TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Chapter 43 FLOW System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
FLOW_APP_POLICY_VIOLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
FLOW_DSTIP_POLICY_VIOLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
FLOW_HIGH_WATERMARK_TRIGGERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
FLOW_HIGH_WATERMARK_TRIGGERED_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
FLOW_IP_ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
FLOW_IP_ACTION_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
FLOW_LOW_WATERMARK_TRIGGERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
FLOW_LOW_WATERMARK_TRIGGERED_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
FLOW_POLICY_VIOLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
FLOW_REASSEMBLE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
FLOW_REASSEMBLE_SUCCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
FLOW_SRCIP_POLICY_VIOLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Chapter 44 FPCLOGIN System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
FPCLOGIN_ADDRESS_GET_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
FPCLOGIN_IPC_RECEIVE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Copyright 2015, Juniper Networks, Inc. xxix

FPCLOGIN_IPC_SEND_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
FPCLOGIN_LOGIN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
FPCLOGIN_MESSAGE_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
FPCLOGIN_SOCKET_OPERATION_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Chapter 45 FSAD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
FSAD_CONFIG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
FSAD_CONNTIMEDOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
FSAD_DIR_CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
FSAD_DIR_STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
FSAD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
FSAD_FILE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
FSAD_FILE_REMOVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
FSAD_FILE_RENAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
FSAD_FILE_STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
FSAD_FILE_SYNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
FSAD_FLOWC_IPC_PAYLOAD_SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
FSAD_FLOWC_IPC_SUBTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
FSAD_FLOWC_IPC_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
FSAD_FLOWC_IPC_VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
FSAD_FLOWC_SERVICE_INACTIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
FSAD_FREE_SPACE_LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
FSAD_FREE_SPACE_TMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
FSAD_FS_STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
FSAD_GEN_IPC_PAYLOAD_SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
FSAD_GEN_IPC_SUBTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
FSAD_GEN_IPC_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
FSAD_GEN_IPC_VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
FSAD_GEN_SERVICE_INACTIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
FSAD_GEN_SERVICE_INIT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
FSAD_MAXCONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
FSAD_MEMORYALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
FSAD_NOT_ROOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
FSAD_PARENT_DIRECTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
FSAD_PATH_IS_DIRECTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
FSAD_PATH_IS_NOT_DIRECTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
FSAD_PATH_IS_SPECIAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
FSAD_RECVERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
FSAD_RENAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
FSAD_TERMINATED_CONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
FSAD_TRACEOPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
FSAD_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Chapter 46 FUD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
FUD_ARGUMENT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
FUD_BAD_SERVER_ADDR_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
FUD_BIND_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
FUD_DAEMON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
FUD_MEMORY_ALLOCATION_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
FUD_PERMISSION_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
xxx Copyright 2015, Juniper Networks, Inc.

Table of Contents
FUD_PIDLOCK_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
FUD_PIDUPDATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
FUD_RECVMSG_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
FUD_RTSOCK_WRITE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
FUD_SENDMSG_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
FUD_SENDMSG_NOINT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
FUD_SETSOCKOPT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
FUD_SOCKET_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Chapter 47 FWAUTH System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
FWAUTH_FTP_LONG_PASSWORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
FWAUTH_FTP_LONG_PASSWORD_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
FWAUTH_FTP_LONG_USERNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
FWAUTH_FTP_LONG_USERNAME_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
FWAUTH_FTP_USER_AUTH_ACCEPTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
FWAUTH_FTP_USER_AUTH_ACCEPTED_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
FWAUTH_FTP_USER_AUTH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
FWAUTH_FTP_USER_AUTH_FAIL_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
FWAUTH_HTTP_USER_AUTH_ACCEPTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
FWAUTH_HTTP_USER_AUTH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
FWAUTH_HTTP_USER_AUTH_FAIL_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
FWAUTH_HTTP_USER_AUTH_OK_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
FWAUTH_TELNET_LONG_PASSWORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
FWAUTH_TELNET_LONG_PASSWORD_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
FWAUTH_TELNET_LONG_USERNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
FWAUTH_TELNET_LONG_USERNAME_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
FWAUTH_TELNET_USER_AUTH_ACCEPTED . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
FWAUTH_TELNET_USER_AUTH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
FWAUTH_TELNET_USER_AUTH_FAIL_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
FWAUTH_TELNET_USER_AUTH_OK_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
FWAUTH_WEBAUTH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
FWAUTH_WEBAUTH_FAIL_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
FWAUTH_WEBAUTH_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
FWAUTH_WEBAUTH_SUCCESS_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Chapter 48 GPRSD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
GPRSD_MEMORY_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
GPRSD_RESTART_CCFG_READ_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Chapter 49 HNCACHED System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
HNCACHED_HOST_ADDRESS_CHANGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
HNCACHED_NAME_RESOLUTION_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Chapter 50 ICCPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
ICCPD_ASSERT_SOFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
ICCPD_OPEN_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
ICCPD_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
ICCPD_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Copyright 2015, Juniper Networks, Inc. xxxi

Chapter 51 IDP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

IDP_APPDDOS_APP_ATTACK_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
IDP_APPDDOS_APP_ATTACK_EVENT_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
IDP_APPDDOS_APP_STATE_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
IDP_APPDDOS_APP_STATE_EVENT_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
IDP_ATTACK_LOG_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
IDP_ATTACK_LOG_EVENT_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
IDP_COMMIT_COMPLETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
IDP_COMMIT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
IDP_DAEMON_INIT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
IDP_IGNORED_IPV6_ADDRESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
IDP_INTERNAL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
IDP_POLICY_COMPILATION_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
IDP_POLICY_LOAD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
IDP_POLICY_LOAD_SUCCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
IDP_POLICY_UNLOAD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
IDP_POLICY_UNLOAD_SUCCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
IDP_SCHEDULEDUPDATE_START_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
IDP_SCHEDULED_UPDATE_STARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
IDP_SECURITY_INSTALL_RESULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
IDP_SESSION_LOG_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
IDP_SESSION_LOG_EVENT_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
IDP_SIGNATURE_LICENSE_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Chapter 52 JADE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
JADE_ATTRIBUTES_TOO_LONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
JADE_AUTH_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
JADE_AUTH_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
JADE_EXEC_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
JADE_IRI_AUTH_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
JADE_PAM_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
JADE_PAM_NO_LOCAL_USER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
JADE_SOCKET_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Chapter 53 JCS System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
JCS_BBD_LOAD_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
JCS_BBD_LOCAL_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
JCS_BBD_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
JCS_BBD_NOT_VALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
JCS_BBD_PARSE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
JCS_BBD_PEER_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
JCS_BBD_SYSTEM_CONFLICT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
JCS_INVALID_BANDWIDTH_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
JCS_KERNEL_RSD_LINK_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
JCS_KERNEL_RSD_LINK_ENABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
JCS_MM_COMMUNICATION_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
JCS_MM_COMMUNICATION_OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
JCS_PEER_BLADE_STATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
JCS_READ_BANDWIDTH_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
xxxii Copyright 2015, Juniper Networks, Inc.

Table of Contents
JCS_READ_BBD_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
JCS_SWITCH_BANDWIDTH_CONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
JCS_SWITCH_COMMUNICATION_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Chapter 54 JDIAMETERD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
JDIAMETERD_FUNC_HSHAKE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
JDIAMETERD_FUNC_LOCACCEPT_NFOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
JDIAMETERD_FUNC_NSCK_LISTEN_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
JDIAMETERD_FUNC_OUT_OF_SYNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
JDIAMETERD_FUNC_PICACCEPT_NFOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
JDIAMETERD_FUNC_TOO_MANY_BADE2ES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
JDIAMETERD_FUNC_USCK_LISTEN_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Chapter 55 JIVED System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
JIVED_ALREADY_RUNNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
JIVED_EVLIB_FUNC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
JIVED_INITIATE_CONN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
JIVED_INIT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
JIVED_NOT_ROOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
JIVED_PIDFILE_LOCK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
JIVED_PIDFILE_UPDATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
JIVED_SNMP_SEND_TRAP_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Chapter 56 JNUD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
JNUD_CONFIG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
JNUD_INIT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Chapter 57 JPTSPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
JPTSPD_INIT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
JPTSPD_OUT_OF_MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
JPTSPD_PIC_CONNECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
JPTSPD_PIC_DISCONNECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
JPTSPD_SRC_FAST_SYNC_ABORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
JPTSPD_SRC_FAST_SYNC_DONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
JPTSPD_SRC_FAST_SYNC_START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
JPTSPD_SRC_FULL_SYNC_ABORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
JPTSPD_SRC_FULL_SYNC_DONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
JPTSPD_SRC_FULL_SYNC_START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Chapter 58 JSERVICES System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
JSERVICES_NAT_OUTOF_ADDRESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
JSERVICES_NAT_OUTOF_PORTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
JSERVICES_NAT_POOL_RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
JSERVICES_NAT_PORT_BLOCK_ACTIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
JSERVICES_NAT_PORT_BLOCK_ALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
JSERVICES_NAT_PORT_BLOCK_RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
JSERVICES_NAT_RULE_MATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
JSERVICES_SESSION_CLOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
JSERVICES_SESSION_OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
JSERVICES_SFW_RULE_ACCEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
JSERVICES_SFW_RULE_DISCARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Copyright 2015, Juniper Networks, Inc. xxxiii

JSERVICES_SFW_RULE_REJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Chapter 59 JSRPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
JSRPD_DAEMONIZE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
JSRPD_DUPLICATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
JSRPD_NODE_STATE_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
JSRPD_NOT_ROOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
JSRPD_PID_FILE_LOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
JSRPD_PID_FILE_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
JSRPD_REDUNDANCY_MODE_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
JSRPD_REDUNDANCY_MODE_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
JSRPD_RG_STATE_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
JSRPD_SET_CS_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
JSRPD_SET_HW_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
JSRPD_SET_INTF_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
JSRPD_SET_IP_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
JSRPD_SET_LOOPBACK_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
JSRPD_SET_MBUF_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
JSRPD_SET_NEXTHOP_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
JSRPD_SET_NPC_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
JSRPD_SET_OTHER_INTF_MON_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
JSRPD_SET_SPU_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
JSRPD_SOCKET_CREATION_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
JSRPD_SOCKET_LISTEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
JSRPD_SOCKET_RECV_HB_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
JSRPD_UNSET_CS_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
JSRPD_UNSET_HW_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
JSRPD_UNSET_INTF_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
JSRPD_UNSET_IP_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
JSRPD_UNSET_LOOPBACK_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
JSRPD_UNSET_MBUF_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
JSRPD_UNSET_NEXTHOP_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
JSRPD_UNSET_NPC_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
JSRPD_UNSET_OTHER_INTF_MON_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
JSRPD_UNSET_SPU_MON_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
JSRPD_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
Chapter 60 JTASK System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
JTASK_ABORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
JTASK_ACTIVE_TERMINATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
JTASK_ASSERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
JTASK_ASSERT_SOFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
JTASK_BFD_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
JTASK_BFD_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
JTASK_CFG_CALLBACK_LONGRUNTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
JTASK_CFG_SCHED_CUMU_LONGRUNTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
JTASK_EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
JTASK_LOCK_FLOCKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
JTASK_LOCK_LOCKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
JTASK_MGMT_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
xxxiv Copyright 2015, Juniper Networks, Inc.

Table of Contents
JTASK_MODE_SWITCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
JTASK_MODE_SWITCH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
JTASK_OS_MEMHIGH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
JTASK_PARSE_BAD_COMMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
JTASK_PARSE_BAD_FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
JTASK_PARSE_BAD_LR_NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
JTASK_PARSE_BAD_OPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
JTASK_PARSE_CMD_ARG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
JTASK_PARSE_CMD_DUPLICATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
JTASK_PARSE_CMD_EXTRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
JTASK_PTHREAD_CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
JTASK_SCHED_CUMU_LONGRUNTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
JTASK_SCHED_MODULE_LONGRUNTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
JTASK_SCHED_TASK_LONGRUNTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
JTASK_SIGNAL_TERMINATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
JTASK_SNMP_CONN_EINPROGRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
JTASK_SNMP_CONN_QUIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
JTASK_SNMP_CONN_RETRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
JTASK_SNMP_INVALID_SOCKET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
JTASK_SNMP_SOCKOPT_BLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
JTASK_SNMP_SOCKOPT_RECVBUF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
JTASK_SNMP_SOCKOPT_SENDBUF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
JTASK_START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
JTASK_SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
JTASK_TASK_BEGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
JTASK_TASK_CHILDKILLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
JTASK_TASK_CHILDSTOPPED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
JTASK_TASK_DYN_REINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
JTASK_TASK_FORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
JTASK_TASK_GETWD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
JTASK_TASK_MASTERSHIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
JTASK_TASK_NOREINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
JTASK_TASK_PIDCLOSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
JTASK_TASK_PIDFLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
JTASK_TASK_PIDWRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
JTASK_TASK_REINIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
JTASK_TASK_SIGNALIGNORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
JTASK_TERMINATE_DISK_SPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Chapter 61 JTRACE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
JTRACE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Chapter 62 KMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
KMD_CFG_IF_ID_POOL_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
KMD_CFG_IF_ID_POOL_NO_ENTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
KMD_CFG_IF_ID_POOL_NO_INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
KMD_CFG_IF_ID_POOL_RETURN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
KMD_DPD_FAILOVER_MANUAL_TUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
KMD_DPD_FAILOVER_MAX_ATTEMPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
KMD_DPD_FAILOVER_NO_ACTIVE_PEER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Copyright 2015, Juniper Networks, Inc. xxxv

KMD_DPD_FAILOVER_NO_BACKUP_PEER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
KMD_DPD_FAILOVER_NO_TUNNEL_CFG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
KMD_DPD_REMOTE_ADDRESS_CHANGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
KMD_PM_DUPLICATE_LIFE_DURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
KMD_PM_IKE_SERVER_LOOKUP_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
KMD_PM_IKE_SERVER_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
KMD_PM_IKE_SRV_NOT_FOUND_DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
KMD_PM_ILLEGAL_REMOTE_GW_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
KMD_PM_INCONSISTENT_P2_IDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
KMD_PM_INVALID_LIFE_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
KMD_PM_LIFETIME_TO_SHORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
KMD_PM_NO_LIFETIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
KMD_PM_NO_LIFE_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
KMD_PM_NO_PROPOSAL_FOR_PHASE1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
KMD_PM_NO_SPD_PHASE1_FUNC_PTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
KMD_PM_P1_POLICY_LOOKUP_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
KMD_PM_P2_POLICY_LOOKUP_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
KMD_PM_PHASE1_GROUP_UNSPECIFIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
KMD_PM_PHASE1_POLICY_SEARCH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
KMD_PM_PHASE2_POLICY_LOOKUP_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
KMD_PM_PROTO_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
KMD_PM_PROTO_IPCOMP_UNSUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
KMD_PM_PROTO_ISAKMP_RESV_UNSUPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
KMD_PM_SA_CFG_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
KMD_PM_SA_ESTABLISHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
KMD_PM_SA_INDEX_GEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
KMD_PM_SA_PEER_ABSENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
KMD_PM_SA_PEER_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
KMD_PM_SPI_DELETE_REJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
KMD_PM_UNEQUAL_PAYLOAD_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
KMD_PM_UNINITIALISE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
KMD_PM_UNINITIALIZE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
KMD_PM_UNKNOWN_P1_IDENTITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
KMD_PM_UNKNOWN_PHASE2_ENTITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
KMD_PM_UNKNOWN_QM_NOTIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
KMD_PM_UNSUPPORTED_KEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
KMD_PM_UNSUPPORTED_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
KMD_SNMP_EXTRA_RESPONSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
KMD_SNMP_FATAL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
KMD_SNMP_MALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
KMD_SNMP_PIC_CONNECTION_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
KMD_SNMP_PIC_NO_RESPONSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
KMD_SNMP_PIC_SLOT_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
KMD_VPN_DFBIT_STATUS_MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
KMD_VPN_DOWN_ALARM_USER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
KMD_VPN_PV_LIFETIME_CHANGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
KMD_VPN_PV_PHASE1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
KMD_VPN_PV_PHASE2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
KMD_VPN_PV_PSK_CHANGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
xxxvi Copyright 2015, Juniper Networks, Inc.

Table of Contents
KMD_VPN_UP_ALARM_USER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Chapter 63 L2ALD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
L2ALD_BD_CREATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
L2ALD_BD_CREATE_RETRY_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
L2ALD_BD_NAME_RESTRICTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
L2ALD_DEFAULT_VLAN_DISABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
L2ALD_DUPLICATE_RBEB_MAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
L2ALD_FREE_MAC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
L2ALD_GENCFG_OP_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
L2ALD_IFBD_COUNT_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
L2ALD_IPC_MESSAGE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
L2ALD_IPC_MESSAGE_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
L2ALD_IPC_MESSAGE_SEND_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
L2ALD_IPC_PIPE_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
L2ALD_MAC_LIMIT_EXCEEDED_BD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
L2ALD_MAC_LIMIT_EXCEEDED_BLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
L2ALD_MAC_LIMIT_EXCEEDED_IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
L2ALD_MAC_LIMIT_EXCEEDED_IFBD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
L2ALD_MAC_LIMIT_REACHED_BD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
L2ALD_MAC_LIMIT_REACHED_GLOBAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
L2ALD_MAC_LIMIT_REACHED_IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
L2ALD_MAC_LIMIT_REACHED_IFBD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
L2ALD_MAC_LIMIT_REACHED_RTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
L2ALD_MAC_LIMIT_RESET_BD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
L2ALD_MAC_LIMIT_RESET_GLOBAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
L2ALD_MAC_LIMIT_RESET_IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
L2ALD_MAC_LIMIT_RESET_RTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
L2ALD_MAC_MOVE_EXCEEDED_BD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
L2ALD_MAC_MOVE_EXCEEDED_BD_ACTION_NONE . . . . . . . . . . . . . . . . . . . . . 496
L2ALD_MAC_MOVE_NOTIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
L2ALD_MAC_MOVE_NOTIF_ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
L2ALD_MAC_MOVE_NOTIF_EXTENSIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
L2ALD_MAC_MOVE_SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
L2ALD_MALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
L2ALD_MANAGER_CONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
L2ALD_NAME_LENGTH_IF_DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
L2ALD_NAME_LENGTH_IF_FAMILY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
L2ALD_NAME_LENGTH_IF_LOGICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
L2ALD_PBBN_IFL_REVA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
L2ALD_PBBN_REINSTATE_IFBDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
L2ALD_PBBN_RETRACT_IFBDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
L2ALD_PIP_IFD_READ_RETRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
L2ALD_RPD_LR_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
L2ALD_RPD_SESS_CREATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
L2ALD_RPD_SESS_HANDLE_ALLOC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
L2ALD_RPD_SOCKET_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
L2ALD_RPD_STATE_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
L2ALD_RPD_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Copyright 2015, Juniper Networks, Inc. xxxvii

L2ALD_ST_CTL_DISABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
L2ALD_ST_CTL_ENABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
L2ALD_ST_CTL_IN_EFFECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
Chapter 64 L2CPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
L2CPD_KERNEL_VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
L2CPD_KERNEL_VERSION_OLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
L2CPD_KERNEL_VERSION_UNSUPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
L2CPD_MIRROR_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
L2CPD_MIRROR_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
L2CPD_PPM_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
L2CPD_PPM_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
L2CPD_XSTP_SHUTDOWN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Chapter 65 L2TPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
L2TPD_COS_PROFILE_ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
L2TPD_COS_PROFILE_DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
L2TPD_DB_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
L2TPD_DB_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
L2TPD_DB_INIT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
L2TPD_DB_TUN_GRP_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
L2TPD_DEFAULT_PROTO_CREATE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
L2TPD_EVLIB_CREATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
L2TPD_EVLIB_FD_DEREGISTER_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
L2TPD_EVLIB_FD_DESELECT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
L2TPD_EVLIB_FD_NOT_REGISTERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
L2TPD_EVLIB_FD_SELECT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
L2TPD_EVLIB_TIMER_CLEAR_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
L2TPD_EVLIB_TIMER_SET_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
L2TPD_FILTER_FILE_OPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
L2TPD_GLOBAL_CFG_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
L2TPD_GLOBAL_CFG_CHANGE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
L2TPD_GLOBAL_CFG_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
L2TPD_IFD_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
L2TPD_IFD_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
L2TPD_IFD_MSG_REGISTER_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
L2TPD_IFD_ROOT_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
L2TPD_IFL_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
L2TPD_IFL_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
L2TPD_IFL_MSG_REGISTER_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
L2TPD_IFL_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
L2TPD_IFL_ROOT_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
L2TPD_INSTANCE_CREATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
L2TPD_INSTANCE_RESTART_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
L2TPD_INTERFACE_ID_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
L2TPD_MESSAGE_REGISTER_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
L2TPD_MLPPP_BUNDLE_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
L2TPD_MLPPP_BUNDLE_CREATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
L2TPD_MLPPP_BUNDLE_INVALID_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
L2TPD_MLPPP_COPY_CFG_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
xxxviii Copyright 2015, Juniper Networks, Inc.

Table of Contents
L2TPD_MLPPP_ID_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
L2TPD_MLPPP_ID_BITMAP_ALLOC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
L2TPD_MLPPP_ID_NODE_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
L2TPD_MLPPP_ID_ROOT_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
L2TPD_MLPPP_LINK_CREATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
L2TPD_MLPPP_LINK_MAX_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
L2TPD_MLPPP_POOL_ADDRESS_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
L2TPD_MLPPP_SESSION_CREATE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
L2TPD_MLPPP_SESSION_DELETE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
L2TPD_MLPPP_SPEED_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
L2TPD_NH_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
L2TPD_POLICER_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
L2TPD_POLICER_PROFILE_DEL_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
L2TPD_POOL_ADDRESS_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
L2TPD_POOL_ASSIGN_ADDRESS_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
L2TPD_PPP_ROUTE_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
L2TPD_PPP_ROUTE_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
L2TPD_PROFILE_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
L2TPD_PROFILE_NO_RADIUS_SERVERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
L2TPD_RADIUS_ACCT_PORT_ZERO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
L2TPD_RADIUS_GETHOSTNAME_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
L2TPD_RADIUS_RT_INST_ENOENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
L2TPD_RADIUS_RT_INST_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
L2TPD_RADIUS_SERVER_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
L2TPD_RADIUS_SRC_ADDR_BIND_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
L2TPD_RADIUS_SRC_ADDR_ENOENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
L2TPD_RPD_ASYNC_UNREG_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
L2TPD_RPD_ROUTE_ADD_CB_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
L2TPD_RPD_ROUTE_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
L2TPD_RPD_ROUTE_DELETE_CB_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
L2TPD_RPD_ROUTE_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
L2TPD_RPD_ROUTE_PREFIX_TOO_LONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
L2TPD_RPD_SESS_CREATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
L2TPD_RPD_SESS_HANDLE_ALLOC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
L2TPD_RPD_SOCKET_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
L2TPD_RPD_TBL_LOCATE_BY_NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
L2TPD_RPD_TBL_LOCATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
L2TPD_RPD_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
L2TPD_RTSLIB_ASYNC_OPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
L2TPD_RTSLIB_OPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
L2TPD_SERVER_START_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
L2TPD_SERVICE_NH_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
L2TPD_SERVICE_NH_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
L2TPD_SESSION_CFG_ADD_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
L2TPD_SESSION_CFG_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
L2TPD_SESSION_CFG_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
L2TPD_SESSION_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
L2TPD_SESSION_IFF_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
L2TPD_SESSION_IFL_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Copyright 2015, Juniper Networks, Inc. xxxix

L2TPD_SESSION_IFL_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
L2TPD_SESSION_IFL_CLI_TREE_ALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
L2TPD_SESSION_IFL_DELETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
L2TPD_SESSION_IFL_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
L2TPD_SESSION_IFL_GET_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
L2TPD_SESSION_IFL_NOT_EQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
L2TPD_SESSION_IFL_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
L2TPD_SESSION_IFL_OCCUPIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
L2TPD_SESSION_IFL_REMOVE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
L2TPD_SESSION_INVALID_PEER_IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
L2TPD_SESSION_IP_DUPLICATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
L2TPD_SESSION_ROUTE_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
L2TPD_SESSION_RT_TBL_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
L2TPD_SESSION_TUNNEL_ID_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
L2TPD_SETSOCKOPT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
L2TPD_SET_ASYNC_CONTEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
L2TPD_SHOW_MULTILINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
L2TPD_SHOW_SESSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
L2TPD_SHOW_TUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
L2TPD_SOCKET_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
L2TPD_SUBUNIT_ROUTE_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
L2TPD_TRACE_FILE_OPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
L2TPD_TUNNEL_CFG_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
L2TPD_TUNNEL_CFG_ADD_INV_ADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
L2TPD_TUNNEL_CFG_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
L2TPD_TUNNEL_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
L2TPD_TUNNEL_DEST_IF_LOOKUP_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
L2TPD_TUNNEL_GROUP_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
L2TPD_TUNNEL_GROUP_CFG_ADD_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
L2TPD_TUNNEL_GROUP_CFG_DEL_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
L2TPD_TUNNEL_GROUP_CREATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
L2TPD_TUNNEL_GROUP_DELETE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
L2TPD_TUNNEL_GROUP_IDX_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
L2TPD_TUNNEL_GROUP_RESTART_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
L2TPD_USER_AUTHN_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
L2TPD_USER_AUTHN_ORDER_UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
L2TPD_USER_AUTHN_PWD_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Chapter 66 LACP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
LACP_INTF_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Chapter 67 LACPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
LACPD_ISSU_ACK_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
LACPD_MEMORY_ALLOCATION_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
LACPD_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Chapter 68 LFMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
LFMD_3AH_LINKDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
LFMD_3AH_LINKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
LFMD_3AH_LOCAL_LB_CHANGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
xl Copyright 2015, Juniper Networks, Inc.

Table of Contents
LFMD_3AH_LT_LOOP_CLEARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
LFMD_3AH_LT_LOOP_DETECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
LFMD_3AH_REQ_REMOTE_LB_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
LFMD_RTSOCK_OPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Chapter 69 LIBJNX System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
LIBJNX_AUDIT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
LIBJNX_AUDIT_TACPLUS_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
LIBJNX_COMPRESS_EXEC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
LIBJNX_DEFAULT_IP_ADDR_NOT_SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
LIBJNX_EVLIB_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
LIBJNX_EXEC_EXITED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
LIBJNX_EXEC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
LIBJNX_EXEC_PIPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
LIBJNX_EXEC_SIGNALED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
LIBJNX_EXEC_WEXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
LIBJNX_FILE_COPY_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
LIBJNX_FILE_SYSTEM_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
LIBJNX_FILE_SYSTEM_SPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
LIBJNX_INVALID_XML_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
LIBJNX_LOGIN_ACCOUNTS_NOT_LOCKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
LIBJNX_LOGIN_ACCOUNT_LOCKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
LIBJNX_LOGIN_ACCOUNT_NOT_LOCKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
LIBJNX_LOGIN_ACCOUNT_UNLOCKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
LIBJNX_LOGIN_ACCT_NOT_UNLOCKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
LIBJNX_PRIV_LOWER_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
LIBJNX_PRIV_RAISE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
LIBJNX_REPLICATE_RCP_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
LIBJNX_REPLICATE_RCP_EXEC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
LIBJNX_SNMP_ENGINE_FILE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
LIBJNX_SNMP_ENGINE_SCAN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
LIBJNX_SOCKET_BUFF_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
LIBJNX_SOCKET_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
LIBJNX_SOCKET_FLUSH_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
LIBJNX_XML_DECODE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Chapter 70 LIBJSNMP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
LIBJSNMP_CTX_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
LIBJSNMP_IPC_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
LIBJSNMP_IPC_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
LIBJSNMP_MTHD_API_UNKNOWN_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
LIBJSNMP_NS_LOG_CRIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
LIBJSNMP_NS_LOG_EMERG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
LIBJSNMP_NS_LOG_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
LIBJSNMP_OID_GEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
LIBJSNMP_READ_LEN_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
LIBJSNMP_RTMSIZE_MISMATCH_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
LIBJSNMP_SMS_HDR_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
LIBJSNMP_SMS_MSG_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
LIBJSNMP_SNMP_PH_INIT_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Copyright 2015, Juniper Networks, Inc. xli

LIBJSNMP_SOCKET_OPEN_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
LIBJSNMP_SOCKET_VER_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
LIBJSNMP_TRAP_API_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
LIBJSNMP_TRAP_UTILS_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
Chapter 71 LIBMSPRPC System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
LIBMSPRPC_CLIENT_INIT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
LIBMSPRPC_CLIENT_KCOM_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
LIBMSPRPC_CLIENT_KCOM_NO_IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
LIBMSPRPC_CLIENT_NO_CONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
LIBMSPRPC_CLIENT_NO_REPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
LIBMSPRPC_CLIENT_PIC_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
LIBMSPRPC_CLIENT_WRONG_OUTPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Chapter 72 LICENSE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
LICENSE_CONNECT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
LICENSE_CONN_TO_LI_CHECK_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
LICENSE_CONN_TO_LI_CHECK_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
LICENSE_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
LICENSE_EXPIRED_KEY_DELETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
LICENSE_GRACE_PERIOD_APPROACHING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
LICENSE_GRACE_PERIOD_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
LICENSE_GRACE_PERIOD_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
LICENSE_INCORRECT_USAGE_API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
LICENSE_INVALIDE_FEATURE_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
LICENSE_JVERSION_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
LICENSE_LIST_MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
LICENSE_NEARING_EXPIRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
LICENSE_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
LICENSE_REG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
LICENSE_REVOKE_DB_CREATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
LICENSE_REVOKE_DB_OPEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
LICENSE_SHM_ATTACH_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
LICENSE_SHM_CREATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
LICENSE_SHM_DETACH_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
LICENSE_SHM_DIR_OPEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
LICENSE_SHM_FILE_OPEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
LICENSE_SHM_KEY_CREATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
LICENSE_SHM_SCALE_READ_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
LICENSE_SHM_SCALE_UPDATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
LICENSE_SHM_USAGE_READ_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
LICENSE_SHM_USAGE_WRITE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
LICENSE_SIGNATURE_VERIFY_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
LICENSE_UNKNOWN_RESPONSE_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
LICENSE_VERIFICATION_FILE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Chapter 73 LLDP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
LLDP_NEIGHBOR_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
LLDP_NEIGHBOR_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
xlii Copyright 2015, Juniper Networks, Inc.

Table of Contents
Chapter 74 LOGIN System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573

LOGIN_ABORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
LOGIN_ATTEMPTS_THRESHOLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
LOGIN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
LOGIN_FAILED_LIMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
LOGIN_FAILED_SET_CONTEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
LOGIN_FAILED_SET_LOGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
LOGIN_HOSTNAME_UNRESOLVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
LOGIN_INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
LOGIN_MALFORMED_USER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
LOGIN_PAM_AUTHENTICATION_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
LOGIN_PAM_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
LOGIN_PAM_MAX_RETRIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
LOGIN_PAM_STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
LOGIN_PAM_USER_UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
LOGIN_PASSWORD_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
LOGIN_REFUSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
LOGIN_ROOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
LOGIN_TIMED_OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Chapter 75 LPDFD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
LPDFD_DYN_PDB_OPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
LPDFD_DYN_REGISTER_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
LPDFD_PCONN_SERVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Chapter 76 LRMUX System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
LRMUX_FAILED_EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
LRMUX_LRPD_PID_LOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
LRMUX_LRPD_PID_OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
LRMUX_LRPD_SEND_HUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Chapter 77 LSYSD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
LRMUX_FAILED_EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
LRMUX_LRPD_PID_LOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
LRMUX_LRPD_PID_OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
LRMUX_LRPD_SEND_HUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Chapter 78 MBG System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
MBG_ADDR_ALLOC_ALLOCATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
MBG_ADDR_ALLOC_MM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
MBG_ADDR_ALLOC_NO_ADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
MBG_ADDR_ALLOC_NO_POOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
MBG_ADDR_ALLOC_NO_VRF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
MBG_ADDR_ALLOC_UNDEFINED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
MBG_ADDR_APFE_DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
MBG_ADDR_APFE_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
MBG_ADDR_INIT_OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
MBG_ADDR_MM_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
MBG_ADDR_MM_ENABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
MBG_ADDR_NO_MEMORY_HEAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Copyright 2015, Juniper Networks, Inc. xliii

MBG_ADDR_NO_MEMORY_OC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
MBG_ADDR_PRIMARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
MBG_ADDR_SECONDARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
MBG_ADDR_STANDALONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
MBG_CFG_COMMIT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
MBG_CFG_DB_OPEN_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
MBG_CG_CONF_SERVER_REGIST_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
MBG_CG_CP_MM_STATE_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
MBG_CG_EVENT_SERVER_REGIST_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
MBG_CG_TSP_MM_STATE_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
MBG_CG_UI_SERVER_REGIST_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
MBG_CMD_ATTACH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
MBG_CMD_CDR_DEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
MBG_CMD_CDR_ENCODING_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
MBG_CMD_CONF_CLIENT_INIT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
MBG_CMD_EVE_CLIENT_INIT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
MBG_CMD_GTPP_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
MBG_CMD_GTPP_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
MBG_CMD_GTPP_VER_MIS_MATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
MBG_CMD_GW_SER_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
MBG_CMD_HA_CHARGED_CONNEC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
MBG_CMD_HMEM_THRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
MBG_CMD_IRI_EXTRACT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
MBG_CMD_LMEM_THRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
MBG_CMD_MMEM_THRES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
MBG_CMD_PMNGR_IPC_REGISTER_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
MBG_CMD_PMNGR_SERVER_CONNEC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
MBG_CMD_RE_DISK_FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
MBG_CMD_RE_DISK_FULL_RESOLVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
MBG_CMD_RE_DISK_OFFLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
MBG_CMD_RE_DISK_ONLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
MBG_CMD_TIMER_START_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
MBG_CMD_TIMER_STOP_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
MBG_CMD_TSP_LOOK_UP_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
MBG_CMD_UI_CLIENT_INIT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
MBG_CMD_WFA_FULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
MBG_CONF_SERVER_INIT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
MBG_EVENT_SERVER_INIT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
MBG_GW_TASK_CREATION_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
MBG_IF_TASK_CREATION_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
MBG_INIT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
MBG_MM_TASK_CREATE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
MBG_PKG_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
MBG_PLATFORM_NOT_SUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
MBG_ROUTING_SOCKET_INIT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
MBG_TIMER_CREATE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
MBG_UI_SERVER_INIT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
xliv Copyright 2015, Juniper Networks, Inc.

Table of Contents
Chapter 79 MCSN System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601

MCSN_SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Chapter 80 MIB2D System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
MIB2D_ATM_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
MIB2D_CONFIG_CHECK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
MIB2D_COUNTER_DECREASING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
MIB2D_FILE_OPEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
MIB2D_IFD_IFDINDEX_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
MIB2D_IFD_IFINDEX_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
MIB2D_IFL_IFINDEX_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
MIB2D_IF_FLAPPING_MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
MIB2D_KVM_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
MIB2D_MASTERSHIP_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
MIB2D_PMON_OVERLOAD_CLEARED_TRAP . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
MIB2D_PMON_OVERLOAD_SET_TRAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
MIB2D_RTSLIB_READ_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
MIB2D_RTSLIB_SEQ_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
MIB2D_SNMP_INDEX_ASSIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
MIB2D_SNMP_INDEX_DUPLICATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
MIB2D_SNMP_INDEX_UPDATE_STAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
MIB2D_SNMP_INDEX_WRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
MIB2D_SYSCTL_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
MIB2D_TRAP_HEADER_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
MIB2D_TRAP_SEND_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Chapter 81 MPLS System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
MPLS_OAM_FANOUT_LIMIT_REACHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
MPLS_OAM_INVALID_SOURCE_ADDRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
MPLS_OAM_PATH_LIMIT_REACHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
MPLS_OAM_SEND_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
MPLS_OAM_SOCKET_OPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
MPLS_OAM_SOCKET_SELECT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
MPLS_OAM_TRACEROUTE_INTERRUPTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
MPLS_OAM_TTL_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
MPLS_OAM_UNREACHABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Chapter 82 NEXTHOP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
NEXTHOP_COMPONENTS_LIMIT_REACHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
Chapter 83 NSD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
NSD_MEMORY_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
NSD_RESTART_COMP_CFG_READ_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
NSD_SEC_NODE_COMP_SYNC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Chapter 84 NSTRACED System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
NSTRACED_MEMORY_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
NSTRACED_RESTART_CFG_READ_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Chapter 85 NTPDATE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
NTPDATE_TIME_CHANGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
Copyright 2015, Juniper Networks, Inc. xlv

Chapter 86 NTPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623

NTPD_CHANGED_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Chapter 87 PARSE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
PARSE_WARN_DUPLICATE_ROUTER_AD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
PARSE_WARN_NO_LS_ROUTER_AD_CFG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
PARSE_WARN_NO_ROUTER_AD_CFG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
PARSE_WARN_PROXY_ARP_CFG_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Chapter 88 PFE System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
PFE_ANALYZER_CFG_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
PFE_ANALYZER_SHIM_CFG_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
PFE_ANALYZER_TABLE_WRITE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
PFE_ANALYZER_TASK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
PFE_CBF_UNSUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
PFE_COS_B2_ONE_CLASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
PFE_COS_B2_UNSUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
PFE_FW_DELETE_MISMATCH_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
PFE_FW_IF_DIALER_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
PFE_FW_IF_INPUT_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
PFE_FW_IF_OUTPUT_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
PFE_FW_PSF_DELETE_MISMATCH_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
PFE_FW_SYSLOG_ETH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
PFE_FW_SYSLOG_IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
PFE_FW_SYSLOG_IP6_GEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
PFE_FW_SYSLOG_IP6_ICMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
PFE_FW_SYSLOG_IP6_TCP_UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
PFE_MGCP_MEM_INIT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
PFE_MGCP_REG_HDL_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
PFE_NH_RESOLVE_THROTTLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
PFE_SCCP_ADD_PORT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
PFE_SCCP_DEL_PORT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
PFE_SCCP_REG_NAT_VEC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
PFE_SCCP_REG_RM_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
PFE_SCCP_REG_VSIP_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
PFE_SCCP_RM_CLIENTID_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
PFE_SCREEN_MT_CFG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
PFE_SCREEN_MT_CFG_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
PFE_SCREEN_MT_ZONE_BINDING_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
PFE_SIP_MEM_INIT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
PFE_SIP_REG_HDL_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
Chapter 89 PFED System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
PFED_NOTIFICATION_STATS_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Chapter 90 PGCPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
PGCPD_SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
PGCPD_STARTUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
PGCPD_SWITCH_OVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
xlvi Copyright 2015, Juniper Networks, Inc.

Table of Contents
Chapter 91 PING System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639

PING_EGRESS_JITTER_THRESH_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
PING_EGRESS_STDDEV_THRESH_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
PING_EGRESS_THRESHOLD_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
PING_INGRESS_JTR_THRESH_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
PING_INGRESS_STDDV_THRESH_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
PING_INGRESS_THRESHOLD_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
PING_PROBE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
PING_RTT_JTR_THRESH_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
PING_RTT_STDDV_THRESH_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
PING_RTT_THRESHOLD_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
PING_TEST_COMPLETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
PING_TEST_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
PING_UNKNOWN_THRESH_TYPE_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Chapter 92 PKID System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
PKID_AFTER_KEY_GEN_SELF_TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
PKID_CERT_BASIC_CNSTRS_INV_CA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
PKID_CERT_BASIC_CNSTRS_MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
PKID_CERT_ID_LOOKUP_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
PKID_CERT_NOT_AFTER_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
PKID_CERT_NOT_BEFORE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
PKID_CERT_SIGN_VERIFY_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
PKID_CORRUPT_CERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
PKID_CRL_CERTIFICATE_REVOKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
PKID_CRL_CHECK_SKIPPED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
PKID_CRL_DOWNLOAD_FAIL_LF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
PKID_CRL_DOWNLOAD_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
PKID_CRL_LOCAL_CERT_REVOKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
PKID_CRL_SIGNATURE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
PKID_FIPS_DSA_NOT_ALLOWED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
PKID_FIPS_KAT_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
PKID_FIPS_RSA_TOO_WEAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
PKID_NO_CA_CERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
PKID_NO_KEYPAIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
PKID_NO_LOCAL_CERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
PKID_OCSP_CA_CERT_MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
PKID_OCSP_CONNECTION_FAILOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
PKID_OCSP_FALLBACK_TO_CRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
PKID_OCSP_NONCE_CHECK_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
PKID_OCSP_RESPONSE_INT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
PKID_OCSP_RESPONSE_MALFORMED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
PKID_OCSP_RESPONSE_SIGN_REQUIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
PKID_OCSP_RESPONSE_TRY_LATER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
PKID_OCSP_RESPONSE_UNAUTHORIZED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
PKID_OCSP_RESP_CA_CERT_MISSING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
PKID_OCSP_RESP_CERT_REVOKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
PKID_OCSP_RESP_CERT_VERIFY_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
PKID_OCSP_SIGN_VERIFY_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Copyright 2015, Juniper Networks, Inc. xlvii

PKID_OCSP_SKIP_REVOCATION_CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
PKID_PV_ASYM_KEYGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
PKID_PV_CERT_DEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
PKID_PV_CERT_LOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
PKID_PV_KEYPAIR_DEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
PKID_PV_KEYPAIR_GEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
PKID_PV_OBJECT_READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
PKID_SCEP_INV_DIGEST_ALG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
PKID_SCEP_INV_ENCRYPT_ALG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
PKID_UNABLE_TO_GET_CRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Chapter 93 PPMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
PPMD_ASSERT_SOFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
PPMD_MIRROR_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
PPMD_OPEN_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
PPMD_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
PPMD_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Chapter 94 PPPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
PPPD_AUTH_CREATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
PPPD_CHAP_AUTH_IN_PROGRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
PPPD_CHAP_GETHOSTNAME_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
PPPD_CHAP_INVALID_IDENTIFIER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
PPPD_CHAP_INVALID_OPCODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
PPPD_CHAP_LOCAL_NAME_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
PPPD_CHAP_OPERATION_UNEXPECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
PPPD_CHAP_REPLAY_ATTACK_DETECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
PPPD_EVLIB_CREATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
PPPD_LOCAL_CREATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
PPPD_MEMORY_ALLOCATION_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
PPPD_PAP_GETHOSTNAME_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
PPPD_PAP_INVALID_IDENTIFIER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
PPPD_PAP_INVALID_OPCODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
PPPD_PAP_LOCAL_PASSWORD_UNAVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
PPPD_PAP_OPERATION_UNEXPECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
PPPD_POOL_ADDRESSES_EXHAUSTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
PPPD_RADIUS_ADD_SERVER_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
PPPD_RADIUS_ALLOC_PASSWD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
PPPD_RADIUS_CREATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
PPPD_RADIUS_CREATE_REQ_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
PPPD_RADIUS_GETADDRINFO_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
PPPD_RADIUS_GETHOSTNAME_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
PPPD_RADIUS_MESSAGE_UNEXPECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
PPPD_RADIUS_NO_VALID_SERVERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
PPPD_RADIUS_OPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
PPPD_RADIUS_ROUTE_INST_ENOENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
Chapter 95 PROFILER System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
PROFILER_RECONFIGURE_SIGHUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
xlviii Copyright 2015, Juniper Networks, Inc.

Table of Contents
Chapter 96 RDD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665

RDD_EVLIB_CREATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
RDD_IFDEV_ADD_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
RDD_IFDEV_DELETE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
RDD_IFDEV_GET_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
RDD_IFDEV_INCOMPATIBLE_REVERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
RDD_IFDEV_INCOMPATIBLE_SWITCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
RDD_IFDEV_RETRY_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
RDD_NEW_INTERFACE_STATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
Chapter 97 RMOPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
RMOPD_ADDRESS_MULTICAST_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
RMOPD_ADDRESS_SOURCE_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
RMOPD_ADDRESS_STRING_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
RMOPD_ADDRESS_TARGET_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
RMOPD_ICMP_ADDR_TYPE_UNSUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
RMOPD_IFINDEX_NOT_ACTIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
RMOPD_IFINDEX_NO_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
RMOPD_IFNAME_NOT_ACTIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
RMOPD_IFNAME_NO_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
RMOPD_ROUTING_INSTANCE_NO_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
RMOPD_TRACEROUTE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Chapter 98 RPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
RPD_AMT_CFG_ADDR_FMLY_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
RPD_AMT_CFG_ANYCAST_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
RPD_AMT_CFG_ANYCAST_MCAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
RPD_AMT_CFG_LOC_ADDR_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
RPD_AMT_CFG_LOC_ADDR_MCAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
RPD_AMT_CFG_PREFIX_LEN_SHORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
RPD_AMT_CFG_RELAY_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
RPD_AMT_RELAY_DISCOVERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
RPD_AMT_TUNNEL_CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
RPD_AMT_TUNNEL_DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
RPD_AMT_UCAST_STRM_LMT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
RPD_BGP_CFG_ADDR_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
RPD_BGP_CFG_LOCAL_ASNUM_WARN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
RPD_BGP_NEIGHBOR_LLST_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
RPD_BGP_NEIGHBOR_STATE_CHANGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
RPD_DYN_CFG_BUSY_SIGNAL_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
RPD_DYN_CFG_GET_PROFILE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
RPD_DYN_CFG_GET_PROF_NAME_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
RPD_DYN_CFG_GET_SES_STATE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
RPD_DYN_CFG_GET_SES_TYPE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
RPD_DYN_CFG_GET_SNAPSHOT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
RPD_DYN_CFG_PDB_CLOSE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
RPD_DYN_CFG_PDB_OPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
RPD_DYN_CFG_REGISTER_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
RPD_DYN_CFG_REQUEST_ACK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Copyright 2015, Juniper Networks, Inc. xlix

RPD_DYN_CFG_RESPONSE_SLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
RPD_DYN_CFG_SCHEMA_OPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
RPD_DYN_CFG_SES_RECOVERY_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
RPD_DYN_CFG_SET_CONTEXT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
RPD_DYN_CFG_SMID_RECOVERY_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
RPD_DYN_CFG_SMID_REG_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
RPD_DYN_CFG_SMID_UNREG_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
RPD_ESIS_ADJDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
RPD_ESIS_ADJUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
RPD_FEC129_AII_COLLISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
RPD_FEC129_AII_COLLISION_CLEARED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
RPD_FEC129_REMOTE_AII_COLLISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
RPD_IFD_INDEXCOLLISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
RPD_IFD_NAMECOLLISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
RPD_IFL_INDEXCOLLISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
RPD_IFL_NAMECOLLISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
RPD_IGMP_ACCOUNTING_OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
RPD_IGMP_ACCOUNTING_ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
RPD_IGMP_ALL_SUBSCRIBERS_DELETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
RPD_IGMP_CFG_CREATE_ENTRY_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
RPD_IGMP_CFG_GROUP_OUT_OF_RANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
RPD_IGMP_CFG_INVALID_VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
RPD_IGMP_CFG_SOURCE_OUT_OF_RANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
RPD_IGMP_DYN_CFG_ALREADY_BOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
RPD_IGMP_DYN_CFG_INVALID_STMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
RPD_IGMP_DYN_CFG_SES_ID_ADD_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
RPD_IGMP_DYN_CFG_SES_ID_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
RPD_IGMP_GROUP_LIMIT_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
RPD_IGMP_GROUP_THRESHOLD_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
RPD_IGMP_GRP_THRESH_LIMIT_BELOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
RPD_IGMP_JOIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
RPD_IGMP_LEAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
RPD_IGMP_MEMBERSHIP_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
RPD_IGMP_ROUTER_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
RPD_ISIS_ADJDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
RPD_ISIS_ADJUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
RPD_ISIS_ADJUPNOIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
RPD_ISIS_LDP_SYNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
RPD_ISIS_LSPCKSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
RPD_ISIS_NO_ROUTERID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
RPD_ISIS_OVERLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
RPD_KRT_CCC_IFL_MODIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
RPD_KRT_DELETED_RTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
RPD_KRT_IFA_GENERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
RPD_KRT_IFDCHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
RPD_KRT_IFDEST_GET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
RPD_KRT_IFDGET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
RPD_KRT_IFD_CELL_RELAY_INV_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
RPD_KRT_IFD_CELL_RELAY_NO_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
l Copyright 2015, Juniper Networks, Inc.

Table of Contents
RPD_KRT_IFD_GENERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
RPD_KRT_IFL_CELL_RELAY_INV_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
RPD_KRT_IFL_CELL_RELAY_NO_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
RPD_KRT_IFL_GENERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
RPD_KRT_KERNEL_BAD_ROUTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
RPD_KRT_NEXTHOP_OVERFLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
RPD_KRT_NOIFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
RPD_KRT_VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
RPD_KRT_VERSIONNONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
RPD_KRT_VERSIONOLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
RPD_KRT_VPLS_IFL_MODIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
RPD_L2VPN_INSTANCE_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
RPD_L2VPN_LABEL_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
RPD_L2VPN_REMOTE_SITE_COLLISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
RPD_L2VPN_SITE_COLLISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
RPD_LAYER2_VC_BFD_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
RPD_LAYER2_VC_BFD_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
RPD_LAYER2_VC_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
RPD_LAYER2_VC_PING_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
RPD_LAYER2_VC_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
RPD_LDP_BFD_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
RPD_LDP_BFD_DOWN_TRACEROUTE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
RPD_LDP_BFD_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
RPD_LDP_GR_CFG_IGNORED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
RPD_LDP_INTF_BLOCKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
RPD_LDP_INTF_UNBLOCKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
RPD_LDP_NBRDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
RPD_LDP_NBRUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
RPD_LDP_PING_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
RPD_LDP_SESSIONDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
RPD_LDP_SESSIONUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
RPD_LMP_ALLOC_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
RPD_LMP_ALLOC_REQUEST_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
RPD_LMP_CONTROL_CHANNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
RPD_LMP_NO_CALLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
RPD_LMP_NO_MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
RPD_LMP_NO_PEER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
RPD_LMP_PEER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
RPD_LMP_PEER_IFL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
RPD_LMP_PEER_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
RPD_LMP_RESOURCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
RPD_LMP_RESOURCE_NO_LINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
RPD_LMP_SEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
RPD_LMP_SEND_ALLOCATION_MESSAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
RPD_LMP_SYSFAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
RPD_LMP_TE_LINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
RPD_LMP_TE_LINK_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
RPD_LMP_UNEXPECTED_OPCODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
RPD_MC_CFG_CREATE_ENTRY_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
Copyright 2015, Juniper Networks, Inc. li

RPD_MC_CFG_FWDCACHE_CONFLICT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
RPD_MC_CFG_PREFIX_LEN_SHORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
RPD_MC_COSD_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
RPD_MC_DESIGNATED_PE_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
RPD_MC_DYN_CFG_ALREADY_BOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
RPD_MC_DYN_CFG_SES_ID_ADD_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
RPD_MC_DYN_CFG_SES_ID_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
RPD_MC_FWD_CACHE_SUPPRESSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
RPD_MC_FWD_CACHE_THRESH_BELOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
RPD_MC_FWD_CACHE_THRESH_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
RPD_MC_FWD_CACHE_UNSUPPRESSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
RPD_MC_LOCAL_DESIGNATED_PE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
RPD_MC_OIF_REJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
RPD_MC_OIF_RE_ADMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
RPD_MIRROR_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
RPD_MIRROR_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
RPD_MLD_ACCOUNTING_OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
RPD_MLD_ACCOUNTING_ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
RPD_MLD_ALL_SUBSCRIBERS_DELETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
RPD_MLD_CFG_CREATE_ENTRY_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
RPD_MLD_CFG_GROUP_OUT_OF_RANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
RPD_MLD_CFG_INVALID_VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
RPD_MLD_CFG_SOURCE_OUT_OF_RANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
RPD_MLD_DYN_CFG_ALREADY_BOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
RPD_MLD_DYN_CFG_INVALID_STMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
RPD_MLD_DYN_CFG_SES_ID_ADD_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
RPD_MLD_DYN_CFG_SES_ID_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
RPD_MLD_GROUP_LIMIT_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
RPD_MLD_GROUP_THRESHOLD_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
RPD_MLD_GRP_THRESH_LIMIT_BELOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
RPD_MLD_JOIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
RPD_MLD_LEAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
RPD_MLD_MEMBERSHIP_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
RPD_MLD_ROUTER_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
RPD_MPLS_DYNAMIC_POOL_EXHAUSTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
RPD_MPLS_INTERFACE_ROUTE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
RPD_MPLS_INTF_MAX_LABELS_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
RPD_MPLS_LABEL_LIMIT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
RPD_MPLS_LABEL_THRESHOLD_LIMIT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . 716
RPD_MPLS_LOSS_DELAY_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
RPD_MPLS_LSP_AUTOBW_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
RPD_MPLS_LSP_BANDWIDTH_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
RPD_MPLS_LSP_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
RPD_MPLS_LSP_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
RPD_MPLS_LSP_SWITCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
RPD_MPLS_LSP_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
RPD_MPLS_OAM_LSP_PING_REPLY_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
RPD_MPLS_OAM_PING_REPLY_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
RPD_MPLS_OAM_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
lii Copyright 2015, Juniper Networks, Inc.

Table of Contents
RPD_MPLS_OAM_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
RPD_MPLS_PATH_BANDWIDTH_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
RPD_MPLS_PATH_BFD_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
RPD_MPLS_PATH_BFD_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
RPD_MPLS_PATH_BW_NOT_AVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
RPD_MPLS_PATH_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
RPD_MPLS_PATH_PING_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
RPD_MPLS_PATH_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
RPD_MPLS_REQ_BW_NOT_AVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
RPD_MPLS_TABLE_ROUTE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
RPD_MSDP_CFG_SA_LIMITS_CONFLICT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
RPD_MSDP_CFG_SRC_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
RPD_MSDP_PEER_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
RPD_MSDP_PEER_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
RPD_MSDP_SRC_ACTIVE_OVER_LIMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
RPD_MSDP_SRC_ACTIVE_OVER_LOGWARN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
RPD_MSDP_SRC_ACTIVE_OVER_THRESH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
RPD_MSDP_SRC_ACTIVE_UNDER_LIMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
RPD_MSDP_SRC_ACTIVE_UNDER_LOGWAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
RPD_MSDP_SRC_ACTIVE_UNDER_THRESH . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
RPD_MVPN_CFG_PREFIX_LEN_SHORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
RPD_MVPN_HOT_ROOT_STANDBY_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
RPD_MVPN_SENDER_BASED_RPF_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
RPD_OSPF_CFGNBR_P2P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
RPD_OSPF_IF_COST_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
RPD_OSPF_LDP_SYNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
RPD_OSPF_LSA_MAXIMUM_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
RPD_OSPF_LSA_WARNING_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
RPD_OSPF_NBRDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
RPD_OSPF_NBRUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
RPD_OSPF_OVERLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
RPD_OSPF_TOPO_IF_COST_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
RPD_PIM_BSR_DROP_PKT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
RPD_PIM_BSR_SEND_Q_THRESHOLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
RPD_PIM_FOUND_NON_BIDIR_NBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
RPD_PIM_GRP_RP_MAP_LIMIT_BELOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
RPD_PIM_GRP_RP_MAP_LIMIT_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
RPD_PIM_GRP_RP_MAP_THRES_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
RPD_PIM_JP_INFINITE_HOLDTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
RPD_PIM_NBRDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
RPD_PIM_NBRUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
RPD_PIM_NON_BIDIR_RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
RPD_PIM_REGISTER_LIMIT_BELOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
RPD_PIM_REGISTER_LIMIT_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
RPD_PIM_REG_THRESH_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
RPD_PIM_SG_LIMIT_BELOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
RPD_PIM_SG_LIMIT_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
RPD_PIM_SG_THRESHOLD_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
RPD_PLCY_CFG_COMMUNITY_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
Copyright 2015, Juniper Networks, Inc. liii

RPD_PLCY_CFG_FWDCLASS_OVERRIDDEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
RPD_PLCY_CFG_IFALL_NOMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
RPD_PLCY_CFG_PARSE_GEN_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
RPD_PLCY_CFG_PREFIX_LEN_SHORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
RPD_PPM_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
RPD_PPM_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
RPD_RA_CFG_CREATE_ENTRY_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
RPD_RA_CFG_INVALID_VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
RPD_RA_DYN_CFG_ALREADY_BOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
RPD_RA_DYN_CFG_INVALID_STMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
RPD_RA_DYN_CFG_SES_ID_ADD_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
RPD_RA_DYN_CFG_SES_ID_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
RPD_RDISC_CKSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
RPD_RDISC_NOMULTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
RPD_RDISC_NORECVIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
RPD_RDISC_SOLICITADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
RPD_RDISC_SOLICITICMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
RPD_RDISC_SOLICITLEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
RPD_RIP_AUTH_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
RPD_RIP_AUTH_REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
RPD_RIP_AUTH_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
RPD_RIP_JOIN_BROADCAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
RPD_RIP_JOIN_MULTICAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
RPD_RSVP_BACKUP_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
RPD_RSVP_BYPASS_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
RPD_RSVP_BYPASS_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
RPD_RSVP_COS_CFG_WARN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
RPD_RSVP_INCORRECT_FLOWSPEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
RPD_RSVP_LSP_SWITCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
RPD_RSVP_MAXIMUM_SESSIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
RPD_RSVP_NBRDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
RPD_RSVP_NBRUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
RPD_RT_CFG_BR_CONFLICT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
RPD_RT_CFG_CREATE_ENTRY_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
RPD_RT_CFG_INVALID_VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
RPD_RT_CFG_TABLE_NON_MATCHING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
RPD_RT_DUPLICATE_RD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
RPD_RT_DYN_CFG_INST_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
RPD_RT_DYN_CFG_TABLE_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
RPD_RT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
RPD_RT_IFUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
RPD_RT_INST_CFG_RESERVED_NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
RPD_RT_INST_IMPORT_PLCY_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
RPD_RT_PATH_LIMIT_BELOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
RPD_RT_PATH_LIMIT_REACHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
RPD_RT_PATH_LIMIT_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
RPD_RT_PREFIX_LIMIT_BELOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
RPD_RT_PREFIX_LIMIT_REACHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
RPD_RT_PREFIX_LIMIT_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
liv Copyright 2015, Juniper Networks, Inc.

Table of Contents
RPD_RT_SHOWMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
RPD_RT_TAG_ID_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
RPD_RV_SESSIONDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
RPD_START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
RPD_SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
RPD_VPLS_CW_NOT_SUPPORTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
RPD_VPLS_INTF_NOT_IN_SITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Chapter 99 RT System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
RT_ALG_ERR_GATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
RT_ALG_ERR_INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
RT_ALG_ERR_MEM_ALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
RT_ALG_ERR_NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
RT_ALG_ERR_RES_ALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
RT_ALG_NTC_FSM_DROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
RT_ALG_NTC_PARSE_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
RT_ALG_NTC_PKT_MALFORMED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
RT_ALG_WRN_CAPACITY_LMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
RT_ALG_WRN_CFG_NEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
RT_FLOW_SESSION_CLOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
RT_FLOW_SESSION_CLOSE_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
RT_FLOW_SESSION_CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
RT_FLOW_SESSION_CREATE_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
RT_FLOW_SESSION_DENY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
RT_FLOW_SESSION_DENY_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
RT_H323_NAT_COOKIE_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
RT_IPSEC_AUTH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
RT_IPSEC_BAD_SPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
RT_IPSEC_DECRYPT_BAD_PAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
RT_IPSEC_PV_DECRYPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
RT_IPSEC_PV_ENCRYPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
RT_IPSEC_PV_REPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
RT_IPSEC_PV_SYM_KEYGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
RT_IPSEC_REPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
RT_MGCP_CALL_LIMIT_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
RT_MGCP_DECODE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
RT_MGCP_MEM_ALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
RT_MGCP_REM_NAT_VEC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
RT_MGCP_RM_CLIENTID_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
RT_MGCP_UNREG_BY_RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
RT_SCCP_CALL_LIMIT_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
RT_SCCP_CALL_RATE_EXCEED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
RT_SCCP_DECODE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
RT_SCCP_NAT_COOKIE_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
RT_SCCP_REM_NAT_VEC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
RT_SCCP_UNREG_RM_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
RT_SCREEN_ICMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
RT_SCREEN_ICMP_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
RT_SCREEN_IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
Copyright 2015, Juniper Networks, Inc. lv

RT_SCREEN_IP_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
RT_SCREEN_SESSION_LIMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
RT_SCREEN_SESSION_LIMIT_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
RT_SCREEN_TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
RT_SCREEN_TCP_DST_IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
RT_SCREEN_TCP_DST_IP_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
RT_SCREEN_TCP_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
RT_SCREEN_TCP_SRC_IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
RT_SCREEN_TCP_SRC_IP_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
RT_SCREEN_UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
RT_SCREEN_UDP_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
RT_SCREEN_WHITE_LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
RT_SCREEN_WHITE_LIST_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
RT_SCTP_LOG_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
RT_SCTP_PKT_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
Chapter 100 RTLOG System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
RTLOG_JLOG_TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
RTLOG_UTP_TCP_SYN_FLOOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
RTLOG_UTP_TCP_SYN_FLOOD_LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
Chapter 101 RTLOGD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
RTLOGD_LOG_BIND_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
RTLOGD_LOG_READ_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
Chapter 102 RTPERF System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
RTPERF_CPU_THRESHOLD_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
RTPERF_CPU_USAGE_OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
Chapter 103 SAVAL System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
SAVAL_RTSOCK_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
Chapter 104 SDK System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
SDK_VMMD_COMMAND_OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
SDK_VMMD_MOD_LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
Chapter 105 SDXD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
SDXD_BEEP_FIN_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
SDXD_BEEP_INIT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
SDXD_CHANNEL_START_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
SDXD_CONNECT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
SDXD_DAEMONIZE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
SDXD_EVLIB_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
SDXD_KEEPALIVES_MISSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
SDXD_KEEPALIVE_SEND_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
SDXD_MGMT_SOCKET_IO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
SDXD_OUT_OF_MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
SDXD_PID_FILE_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
SDXD_SOCKET_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
lvi Copyright 2015, Juniper Networks, Inc.

Table of Contents
Chapter 106 SM System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775

SM_IPPOOL_MM_STATE_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
SM_IPPOOL_POOL_THRESH_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
Chapter 107 SMTPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
SMTPD_DROP_MAIL_PAYLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
SMTPD_NO_CONFIGURED_SERVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
Chapter 108 SNMP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
SNMP_GET_ERROR1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
SNMP_GET_ERROR2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
SNMP_GET_ERROR3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
SNMP_GET_ERROR4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
SNMP_RTSLIB_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
SNMP_TRAP_LINK_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
SNMP_TRAP_LINK_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
SNMP_TRAP_TRACERT_PATH_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
SNMP_TRAP_TRACERT_TEST_COMPLETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
SNMP_TRAP_TRACERT_TEST_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
Chapter 109 SNMPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
SNMPD_AUTH_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
SNMPD_AUTH_PRIVILEGES_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
SNMPD_AUTH_RESTRICTED_ADDRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
SNMPD_AUTH_WRONG_PDU_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
SNMPD_BIND_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
SNMPD_CONFIG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
SNMPD_CONTEXT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
SNMPD_ENGINE_ID_CHANGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
SNMPD_FILE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
SNMPD_GROUP_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
SNMPD_HEALTH_MON_THRESH_CROSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
SNMPD_INIT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
SNMPD_LIBJUNIPER_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
SNMPD_MISSING_REGISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
SNMPD_RADIX_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
SNMPD_RECEIVE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
SNMPD_RMONFILE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
SNMPD_RMON_COOKIE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
SNMPD_RMON_EVENTLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
SNMPD_RMON_MIBERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
SNMPD_RTSLIB_ASYNC_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
SNMPD_SCRIPT_OID_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
SNMPD_SCRIPT_REGISTERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
SNMPD_SEND_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
SNMPD_SET_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
SNMPD_SMOID_GEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
SNMPD_SOCKET_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
SNMPD_SOCKET_FATAL_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
SNMPD_SYSLIB_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
Copyright 2015, Juniper Networks, Inc. lvii

SNMPD_SYSOID_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
SNMPD_SYSOID_GEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
SNMPD_THROTTLE_QUEUE_DRAINED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
SNMPD_TRAP_COLD_START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
SNMPD_TRAP_GEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
SNMPD_TRAP_INVALID_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
SNMPD_TRAP_QUEUED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
SNMPD_TRAP_QUEUE_DRAINED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
SNMPD_TRAP_QUEUE_MAX_ATTEMPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
SNMPD_TRAP_QUEUE_MAX_SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
SNMPD_TRAP_TARGET_ADD_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
SNMPD_TRAP_TARGET_DELETE_NOTICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
SNMPD_TRAP_THROTTLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
SNMPD_TRAP_WARM_START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
SNMPD_USER_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
Chapter 110 SPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
SPD_CONFIGURATION_COMPILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
SPD_CONN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
SPD_CONN_NO_REPLY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
SPD_CONN_OPEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
SPD_CONN_SEND_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
SPD_CONN_UNEXPECTED_MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
SPD_DAEMONIZE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
SPD_DB_IF_ADD_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
SPD_DB_IF_ALLOC_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
SPD_DB_SVC_SET_ADD_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
SPD_DB_SVC_SET_ALLOC_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
SPD_DUPLICATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
SPD_EVLIB_CREATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
SPD_EVLIB_EXIT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
SPD_GEN_NUM_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
SPD_NOT_ROOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
SPD_OUT_OF_MEMORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
SPD_PID_FILE_LOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
SPD_PID_FILE_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
SPD_SERVICE_NEXT_HOP_ADD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
SPD_SERVICE_NEXT_HOP_DEL_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
SPD_TRAP_OID_GEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
SPD_TRAP_REQUEST_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
SPD_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Chapter 111 SSH System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
SSH_MSG_REPLAY_DETECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
SSH_MSG_REPLAY_LIMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
SSH_RELAY_CONNECT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
SSH_RELAY_SERVER_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
SSH_RELAY_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
lviii Copyright 2015, Juniper Networks, Inc.

Table of Contents
Chapter 112 SSHD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807

SSHD_LOGIN_ATTEMPTS_THRESHOLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
SSHD_LOGIN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
SSHD_LOGIN_FAILED_LIMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Chapter 113 SSL System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
SSL_PROXY_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
SSL_PROXY_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
SSL_PROXY_SESSION_IGNORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
SSL_PROXY_SESSION_WHITELIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
SSL_PROXY_SSL_SESSION_ALLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
SSL_PROXY_SSL_SESSION_DROP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
SSL_PROXY_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Chapter 114 SYSTEM System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
SYSTEM_ABNORMAL_SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
SYSTEM_OPERATIONAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
SYSTEM_SHUTDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Chapter 115 TFTPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
TFTPD_AF_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
TFTPD_BIND_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
TFTPD_CONNECT_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
TFTPD_CONNECT_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
TFTPD_CREATE_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
TFTPD_FIO_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
TFTPD_FORK_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
TFTPD_NAK_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
TFTPD_OPEN_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
TFTPD_RECVCOMPLETE_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
TFTPD_RECVFROM_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
TFTPD_RECV_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
TFTPD_SENDCOMPLETE_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
TFTPD_SEND_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
TFTPD_SOCKET_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
TFTPD_STATFS_ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
Chapter 116 TRANSPORTD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
TRANSPORTD_IPC_MSG_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
TRANSPORTD_IPC_MSG_UNHANDLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
TRANSPORTD_IPC_UNEXPECTED_MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
TRANSPORTD_IPC_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
TRANSPORTD_IPC_WRITE_ERR_NO_PIPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
TRANSPORTD_MGR_CONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
TRANSPORTD_PIPE_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
TRANSPORTD_SYSCALL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
Chapter 117 UFDD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
UFDD_GROUP_ACTION_COMPLETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
UFDD_LINK_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
Copyright 2015, Juniper Networks, Inc. lix

Chapter 118 UI System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825

UI_AUTH_BAD_LOCATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
UI_AUTH_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
UI_AUTH_INVALID_CHALLENGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825
UI_BOOTTIME_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
UI_CFG_AUDIT_NEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
UI_CFG_AUDIT_OTHER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
UI_CFG_AUDIT_SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
UI_CFG_AUDIT_SET_SECRET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
UI_CHILD_ARGS_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
UI_CHILD_CHANGE_USER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
UI_CHILD_EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
UI_CHILD_EXITED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
UI_CHILD_FOPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
UI_CHILD_OUTPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
UI_CHILD_PIPE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
UI_CHILD_STOPPED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
UI_CHILD_WAITPID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
UI_CLASS_MODIFIED_USERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
UI_CLI_IDLE_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
UI_CMDLINE_READ_LINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
UI_CMD_AUTH_REGEX_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
UI_COMMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
UI_COMMIT_AT_ABORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
UI_COMMIT_AT_COMPLETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
UI_COMMIT_AT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
UI_COMMIT_COMPLETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
UI_COMMIT_COMPRESS_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
UI_COMMIT_CONFIRMED_REMINDER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
UI_COMMIT_EMPTY_CONTAINER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
UI_COMMIT_NOT_CONFIRMED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
UI_COMMIT_PREV_CNF_SAVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
UI_COMMIT_PROGRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
UI_COMMIT_ROLLBACK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
UI_COMMIT_SYNC_FORCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
UI_COND_GROUPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
UI_COND_GROUPS_COMMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
UI_COND_GROUPS_COMMIT_ABORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
UI_CONFIGURATION_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
UI_CONFIGURATION_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
UI_CONNECT_COMMITD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
UI_DAEMON_ACCEPT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
UI_DAEMON_FORK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
UI_DAEMON_SELECT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
UI_DAEMON_SOCKET_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
UI_DBASE_ACCESS_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
UI_DBASE_CHECKOUT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
UI_DBASE_EXTEND_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
UI_DBASE_LOGIN_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
lx Copyright 2015, Juniper Networks, Inc.

Table of Contents
UI_DBASE_LOGOUT_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
UI_DBASE_MISMATCH_EXTENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
UI_DBASE_MISMATCH_MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
UI_DBASE_MISMATCH_MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
UI_DBASE_MISMATCH_SEQUENCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
UI_DBASE_MISMATCH_SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
UI_DBASE_OPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
UI_DBASE_REBUILD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
UI_DBASE_REBUILD_SCHEMA_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
UI_DBASE_REBUILD_STARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
UI_DBASE_RECREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
UI_DBASE_REOPEN_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
UI_DELTA_CONSTRAINT_CHECK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
UI_DELTA_CONSTRAINT_CHECK_FORK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . 843
UI_DELTA_CONSTRAINT_CHECK_NOT_RUNNING . . . . . . . . . . . . . . . . . . . . . . . 843
UI_DELTA_CONSTRAINT_CHECK_VERSION_MISMATCH . . . . . . . . . . . . . . . . . . 843
UI_DELTA_EXPORTER_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
UI_DELTA_EXPORTER_INIT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
UI_DUPLICATE_UID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
UI_EPHEMERAL_COMMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
UI_EPHEMERAL_COMMIT_COMPLETED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
UI_EPHEMERAL_DB_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
UI_FACTORY_OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
UI_INITIALSETUP_OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
UI_INVALID_REMOTE_PERMISSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
UI_JUNOSCRIPT_CMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
UI_JUNOSCRIPT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
UI_LCC_NO_MASTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
UI_LOAD_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
UI_LOAD_JUNOS_DEFAULT_FILE_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
UI_LOCK_AUTHENTICATION_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
UI_LOCK_AUTHENTICATION_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
UI_LOGIN_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
UI_LOGOUT_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
UI_LOST_CONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
UI_MASTERSHIP_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
UI_MOTD_PROPAGATE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
UI_NETCONF_CMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
UI_NETCONF_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
UI_PARSE_JUNOSCRIPT_ATTRIBUTES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
UI_READ_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
UI_READ_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
UI_REBOOT_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
UI_RESCUE_OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
UI_RESTART_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
UI_RESTART_FAILED_EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
UI_SCHEMA_CHECKOUT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
UI_SCHEMA_MISMATCH_MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
UI_SCHEMA_MISMATCH_SEQUENCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
Copyright 2015, Juniper Networks, Inc. lxi

UI_SCHEMA_SEQUENCE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852
UI_SCRIPTS_COPY_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852
UI_SOCK_WARNING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852
UI_VERSION_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
UI_WRITE_RECONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
UI_XPATH_CONSTRAINT_CHECK_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
UI_XPATH_CONSTRAINT_DA_INIT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
UI_XPATH_CONSTRAINT_DOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
Chapter 119 UTMD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
UTMD_MAILNOTIFIER_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
UTMD_MALLOC_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
UTMD_SSAMLIB_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
Chapter 120 VCCPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
VCCPD_FABRIC_LSDB_LOOKUP_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
VCCPD_FABRIC_MALLOC_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
VCCPD_FABRIC_PROCESS_OIR_MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
VCCPD_FABRIC_SYSCTL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
VCCPD_FABRIC_SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
VCCPD_FABRIC_UNSUPPORTED_RE_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
VCCPD_FABRIC_UNSUPPORTED_SKU_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
VCCPD_KNL_VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
VCCPD_KNL_VERSIONNONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
VCCPD_KNL_VERSIONOLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
VCCPD_PROTOCOL_ADJDOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
VCCPD_PROTOCOL_ADJUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
VCCPD_PROTOCOL_LSPCKSUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
VCCPD_PROTOCOL_OVERLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
VCCPD_SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
Chapter 121 VM System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
VM_DCF_PB_COMMUNICATION_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
VM_DCF_PB_INVALID_IMAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
VM_DCF_PB_INVALID_UUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
VM_DCF_PB_RESOURCE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
Chapter 122 VRRPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
VRRPD_ADVERT_TIME_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
VRRPD_AUTH_INFO_INVALID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
VRRPD_GET_TRAP_HEADER_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
VRRPD_LINK_LOCAL_ADD_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
VRRPD_MISSING_VIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
VRRPD_NEW_BACKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
VRRPD_NEW_MASTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
VRRPD_V3_PROTO_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
VRRPD_VIP_COUNT_MISMATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
Chapter 123 WEB System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
WEB_AUTH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
WEB_AUTH_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
lxii Copyright 2015, Juniper Networks, Inc.

Table of Contents
WEB_AUTH_TIME_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
WEB_CERT_FILE_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
WEB_CERT_FILE_NOT_FOUND_RETRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
WEB_CHILD_STATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
WEB_CONFIG_OPEN_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
WEB_CONFIG_WRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
WEB_COULDNT_START_HTTPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
WEB_EVENTLIB_INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
WEB_KEYPAIR_FILE_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
WEB_MGD_BIND_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
WEB_MGD_CHMOD_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
WEB_MGD_CONNECT_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
WEB_MGD_FCNTL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
WEB_MGD_LISTEN_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
WEB_MGD_RECVMSG_PEEK_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
WEB_MGD_SOCKET_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
WEB_PIDFILE_LOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
WEB_PIDFILE_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
WEB_UNAME_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
WEB_WEBAUTH_AUTH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
WEB_WEBAUTH_AUTH_OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
WEB_WEBAUTH_CONNECT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
Chapter 124 WEBFILTER System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
WEBFILTER_CACHE_NOT_ENABLED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
WEBFILTER_INTERNAL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
WEBFILTER_REQUEST_NOT_CHECKED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
WEBFILTER_SERVER_CONNECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
WEBFILTER_SERVER_DISCONNECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
WEBFILTER_SERVER_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
Part 3 Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881
Copyright 2015, Juniper Networks, Inc. lxiii

lxiv Copyright 2015, Juniper Networks, Inc.

About This Guide

This preface provides the following guidelines for using the Junos OS System Log
Messages Reference:
Junos OS Documentation and Release Notes on page lxv

Objectives on page lxvi
Audience on page lxvi
Supported Platforms on page lxvi
Using the Examples in This Manual on page lxvii
Documentation Conventions on page lxviii
Documentation Feedback on page lxx
Requesting Technical Support on page lxxi
Junos OS Documentation and Release Notes
For a list of related Junos OS 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 OS 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 the Junos operating system (Junos
OS) 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 OS 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.
Copyright 2015, Juniper Networks, Inc. lxv

Objectives
This reference describes system log messages generated by the Junos OS. Use the
information to interpret system log messages and determine the appropriate corrective
action for error conditions
NOTE: For additional information about the Junos OSeither 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, the Junos OS currently supports the following
platforms:
M Series
MX Series
lxvi Copyright 2015, Juniper Networks, Inc.

About This Guide
QFabric
QFX Series
SRX 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:
Copyright 2015, Juniper Networks, Inc. lxvii

[edit]
user@host# load merge /var/tmp/ex-script.conf
load complete
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.confload complete
For more information about the load command, see the Junos OS CLI User Guide
Documentation Conventions
Table 1 on page lxix defines notice icons used in this guide.
lxviii Copyright 2015, Juniper Networks, Inc.

About This Guide
Table 1: Notice Icons

Icon Meaning Description
Informational note 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.
Tip Indicates helpful information.
Best practice Alerts you to a recommended use or implementation.
Table 2 on page lxix defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions

Convention Description Examples
Bold text like this Represents text that you type. To enter configuration mode, type the
configure command:
user@host> configure
Fixed-width text like this Represents output that appears on the user@host> show chassis alarms
terminal screen.
No alarms currently active
Italic text like this Introduces or emphasizes important A policy term is a named structure
new terms. that defines match conditions and
Identifies guide names. actions.
Junos OS CLI User Guide
Identifies RFC and Internet draft titles.
RFC 1997, BGP Communities Attribute
Italic text like this Represents variables (options for which Configure the machines domain name:
you substitute a value) in commands or
configuration statements. [edit]
root@# set system domain-name
domain-name
Copyright 2015, Juniper Networks, Inc. lxix

Table 2: Text and Syntax Conventions (continued)

Convention Description Examples
Text like this Represents names of configuration To configure a stub area, include the
statements, commands, files, and stub statement at the [edit protocols
directories; configuration hierarchy levels; ospf area area-id] hierarchy level.
or labels on routing platform The console port is labeled CONSOLE.
components.
< > (angle brackets) Encloses optional keywords or variables. stub <default-metric metric>;
| (pipe symbol) Indicates a choice between the mutually broadcast | multicast

exclusive keywords or variables on either
side of the symbol. The set of choices is (string1 | string2 | string3)
often enclosed in parentheses for clarity.
# (pound sign) Indicates a comment specified on the rsvp { # Required for dynamic MPLS only
same line as the configuration statement
to which it applies.
[ ] (square brackets) Encloses a variable for which you can community name members [
substitute one or more values. community-ids ]
Indention and braces ( { } ) Identifies a level in the configuration [edit]

hierarchy. routing-options {
static {
route default {
; (semicolon) Identifies a leaf statement at a
nexthop address;
configuration hierarchy level.
retain;
}
}
}
GUI Conventions
Bold text like this Represents graphical user interface (GUI) In the Logical Interfaces box, select
items you click or select. All Interfaces.
To cancel the configuration, click
Cancel.
> (bold right angle bracket) Separates levels in a hierarchy of menu In the configuration editor hierarchy,
selections. select Protocols>Ospf.
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can

improve the documentation. You can provide feedback by using either of the following
methods:
Online feedback rating systemOn any page at the Juniper Networks Technical
Documentation site at http://www.juniper.net/techpubs/index.html, simply click the
stars to rate the content, and use the pop-up form to provide us with information about
your experience. Alternately, you can use the online feedback form at
https://www.juniper.net/cgi-bin/docbugreport/.
lxx Copyright 2015, Juniper Networks, Inc.

About This Guide
E-mailSend your comments to techpubs-comments@juniper.net. Include the document

or topic name, URL or page number, and software 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/us/en/local/pdf/resource-guides/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.
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/
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:

http://kb.juniper.net/InfoCenter/
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).
Copyright 2015, Juniper Networks, Inc. lxxi

For international or direct-dial options in countries without toll-free numbers, visit us at

http://www.juniper.net/support/requesting-support.html
lxxii Copyright 2015, Juniper Networks, Inc.

PART 1
Overview
Configuring System Log Messages on page 3
Copyright 2015, Juniper Networks, Inc. 1

2 Copyright 2015, Juniper Networks, Inc.

CHAPTER 1
Configuring System Log Messages
Junos OS generates system log messages (also called syslog messages) to record events
that occur on the router, 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 router power-down due to excessive

temperature
Each system log message identifies the Junos OS process that generated the message
and briefly describes the operation or error that occurred.
NOTE: This topic describes system log messages for Junos OS processes
and libraries and not the system logging services on a PIC such as the Adaptive
Services PIC. For information about configuring system logging for PIC
services, see Junos OS Services Interfaces Library for Routing Devices.
This chapter discusses the following topics:
Junos OS System Log Configuration Hierarchy on page 3

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 TX Matrix Router on page 31
Displaying and Interpreting System Log Messages on page 49
Getting Help About System Log Messages on page 60
Junos OS System Log Configuration Hierarchy
To configure the router 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;
archive <archive-sites {ftp-url <password password>}> <files number> <size size>
<start-time "YYYY-MM-DD.hh:mm"> <transfer-interval minutes> <world-readable |
no-world-readable>;
explicit-priority;
match "regular-expression";
structured-data {
brief;
}
}
host (hostname | other-routing-engine | scc-master) {
facility severity;
explicit-priority;
facility-override facility;
log-prefix string
source-address source-address;
structured-data {
brief;
}
}
time-format (year | millisecond | year millisecond);
user (username | *) {
facility severity;
}
}
Related Junos OS System Log Overview

Documentation
Minimum and Default System Logging Configuration
For information about the minimum and default system log settings on routing platforms
that run Junos OS, see the following sections:
Junos OS Minimum System Logging Configuration on page 4

Junos OS Default System Log Settings on page 5
Junos OS Platform-Specific Default System Log Messages on page 6
Junos OS 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 Single-Chassis System Logging Configuration Overview.

Chapter 1: Configuring System Log Messages
Table 3: Minimum Configuration Statements for System Logging

Destination Minimum Configuration Statements
File [edit system syslog]

file filename {
facility severity;
}
Terminal session of one, several, or all [edit system syslog]

users user (username | *) {
facility severity;
}
Router or switch console [edit system syslog]

console {
facility severity;
}
Remote machine or the other Routing [edit system syslog]

Engine on the router or switch host (hostname | other-routing-engine) {
facility severity;
}

Documentation
Junos OS Default System Log Settings

Table 4 on page 5 summarizes the default system log settings that apply to all routers
that run Junos OS, and specifies which statement to include in the configuration to
override the default value.
Table 4: Default System Logging Settings

Setting Default Overriding Statement Instructions
Alternative facility For change-log: local6 [edit system syslog] Changing the Alternative Facility
for message host hostname { Name for System Log Messages
forwarded to a For conflict-log: local5 facility-override facility; Directed to a Remote Destination on
remote machine } page 15
For dfc: local1
For firewall: local3
For interactive-commands: local7
For pfe: local4
Format of Standard Junos format, based [edit system syslog] Logging Messages in
messages logged on UNIX format file filename { Structured-Data Format on page 12
to a file structured-data;
}

Table 4: Default System Logging Settings (continued)

Setting Default Overriding Statement Instructions
Maximum number 10 [edit system syslog] Specifying Log File Size, Number,
of files in the archive { and Archiving Properties on page 20
archived set files number;
}
file filename {
archive {
files number;
}
}
Maximum size of M Series, MX Series, and T [edit system syslog] Specifying Log File Size, Number,
the log file Series: 1 megabyte (MB) archive { and Archiving Properties on page 20
size size;
TX Matrix: 10 MB }
file filename {
archive {
size size;
}
}
Timestamp format Month, date, hour, minute, [edit system syslog] Including the Year or Millisecond in
second time-format format; Timestamps on page 25
For example: Aug 21 12:36:30
Users who can read root user and users with the [edit system syslog] Specifying Log File Size, Number,
log files Junos maintenance permission archive { and Archiving Properties on page 20
world-readable;
}
file filename {
archive {
world-readable;
}
}
Junos OS System Log Overview
Junos OS Platform-Specific Default System Log Messages on page 6
Junos OS Platform-Specific Default System Log Messages

The following messages are generated by default on specific routers. To view any of
these types of messages, you must configure at least one destination for messages as
described in Junos OS Minimum System Logging Configuration on page 4.
To log the kernel process message on an M Series, MX Series, or T Series router, include
the kernel info statement at the appropriate hierarchy level:
[edit system syslog]

(console | file filename | host destination | user username) {
kernel info;
}

On a routing matrix composed of a TX Matrix router and T640 routers, the master
Routing Engine on each T640 router forwards all messages with a severity of info and
higher to the master Routing Engine on the TX Matrix router. This is equivalent to the
following configuration statement included on the TX Matrix router:

host scc-master {
any info;
}
Likewise, on a routing matrix composed of a TX Matrix Plus router with connected

T1600 or T4000 routers, the master Routing Engine on each T1600 or T4000 LCC
forwards to the master Routing Engine on the TX Matrix Plus router all messages with
a severity of info and higher. This is equivalent to the following configuration statement
included on the TX Matrix Plus router:
NOTE: From the perspective of the user interface, the routing matrix
appears as a single router. The TX Matrix Plus router controls all the T1600
or T4000 routers connected to it in the routing matrix.

host sfc0-master {
any info;
}

Documentation
Junos OS Default System Log Settings on page 5
Routing Matrix with a TX Matrix Plus Router Solutions Page
Configuring System Logging for a Single-Chassis System
The Junos OS 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 Junos
OS.
System logging configuration for Junos-FIPS software and for Juniper Networks routing
platforms in a Common Criteria environment is the same as for Junos OS. For more
information, see the Secure Configuration Guide for Common Criteria and Junos-FIPS.
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.

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 Logging
Messages in Structured-Data Format on page 12.
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 System Log
Messages to a User Terminal on page 13.
To the routing platform console, by including the console statement. See Directing
System Log 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 Destination from the Routing Matrix Based on the TX Matrix Router on
page 37.
By default, messages are logged in a standard format, which is based on a UNIX system
log format; for detailed information, see Interpreting Messages Generated in Standard
Format by a Junos OS Process or Library on page 55, Interpreting Messages Generated
in Standard Format by Services on a PIC on page 56, and Interpreting Messages
Generated in Structured-Data Format on page 51. 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 22.
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 25.
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
Destination from the Routing Matrix Based on the TX Matrix Router on page 37.
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 25.
For a statement summary for the statements discussed in this chapter, see the Junos
System Basics Configuration Guide.
Specifying the Facility and Severity of Messages to Include in the Log on page 9
Directing System Log Messages to a Log File on page 11
Logging Messages in Structured-Data Format on page 12
Directing System Log Messages to a User Terminal on page 13
Directing System Log Messages to the Console on page 13
Directing Messages to a Remote Machine or the Other Routing Engine on page 13
Specifying Log File Size, Number, and Archiving Properties on page 20
Including Priority Information in System Log Messages on page 22
System Log Facility Codes and Numerical Codes Reported in Priority
Information on page 23
Including the Year or Millisecond in Timestamps on page 25
Using Regular Expressions to Refine the Set of Logged Messages on page 25
Junos System Log Regular Expression Operators for the match Statement on page 27
Disabling the System Logging of a Facility on page 28
Examples: Configuring System Logging on page 29
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 and higher are logged
to the following destination:

(console | file filename | host destination | user username) {
facility severity ;
}
For more information about the destinations, see Directing System Log Messages to a
User Terminal on page 13, and, Directing System Log Messages to the Console 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 10 lists the Junos OS system logging facilities that you can specify in
configuration statements at the [edit system syslog] hierarchy level.
Table 5: Junos OS System Logging Facilities

Facility Type of Event or Error
any All (messages from all facilities)
authorization Authentication and authorization attempts
change-log Changes to the Junos OS configuration
conflict-log Specified configuration is invalid on the router type
daemon Actions performed or errors encountered by system processes
dfc Events related to dynamic flow capture
firewall Packet filtering actions performed by a firewall filter
ftp Actions performed or errors encountered by the FTP process
interactive-commands Commands issued at the Junos OS command-line interface (CLI) prompt

or by a client application such as a Junos XML protocol or NETCONF XML
client
kernel Actions performed or errors encountered by the Junos OS kernel
pfe Actions performed or errors encountered by the Packet Forwarding Engine
user Actions performed or errors encountered by user-space processes
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 the System Logging of a Facility on page 28.
Table 6: System Log Message Severity Levels

Severity Level Description
any Includes all severity levels
none Disables logging of the associated facility to a destination
emergency System panic or other condition that causes the router to stop functioning

Table 6: System Log Message Severity Levels (continued)

Severity Level Description
alert Conditions that require immediate correction, such as a corrupted system

database
critical Critical conditions, such as hard errors
error Error conditions that generally have less serious consequences than errors at
the emergency, alert, and critical levels
warning Conditions that warrant monitoring
notice Conditions that are not errors but might warrant special handling
info Events or nonerror conditions of interest
Related Junos OS System Logging Facilities and Message Severity Levels

Documentation
Single-Chassis System Logging Configuration Overview
Directing System Log 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:

file filename {
facility severity;
archive <archive-sites (ftp-url <password password>)> <files number> <size size>
no-world-readable>;
explicit-priority;
structured-data {
brief;
}
}
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 OS 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, either for all log files or for a certain log file. For more information, see Specifying
Log File Size, Number, and Archiving Properties on page 20.

For information about the following statements, see the indicated sections:
explicit-prioritySee Including Priority Information in System Log Messages on page 22
matchSee Using Regular Expressions to Refine the Set of Logged Messages on

page 25
structured-dataSee Logging Messages in Structured-Data Format on page 12
Related Single-Chassis System Logging Configuration Overview

Documentation
Logging Messages in Structured-Data Format

You can log messages to a file in structured-data format instead of the standard Junos
OS 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-23,

The syslog Protocol, which is at http://tools.ietf.org/html/draft-ietf-syslog-protocol-23.
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.
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 OS system log format, not to
structured-data format.

Documentation

Directing System Log 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:

user (username | *) {
facility severity;
}
Specify one or more Junos OS 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 logging 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 statement,
see Using Regular Expressions to Refine the Set of Logged Messages on page 25.

Documentation
Directing System Log 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:

console {
facility severity;
}
For the list of logging facilities and severity levels, see Specifying the Facility and Severity
of Messages to Include in the Log on page 9.

Documentation
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:

host (hostname | other-routing-engine) {
facility severity;
explicit-priority;
log-prefix string;

}
To direct system log messages to a remote machine, include the host hostname statement
to specify the remote machines IPv4 address, 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 22.
For information about the match statement, see Using Regular Expressions to Refine
the Set of Logged Messages on page 25.
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 Directed to a

Remote Destination on page 15
Changing the Alternative Facility Name for System Log Messages Directed to a Remote
Destination on page 15
Default Facilities for System Log Messages Directed to a Remote Destination on page 17
Alternate Facilities for System Log Messages Directed to a Remote
Examples: Assigning an Alternative Facility to System Log Messages Directed to a
Adding a Text String to System Log Messages Directed to a Remote
Adding a String on page 20

Specifying an Alternative Source Address for System Log Messages Directed to

a Remote Destination
To specify the source router to be reported in system log messages when the messages
are directed to a remote machine, include the source-address statement at the
[edit system syslog] hierarchy level:

source-address is a valid IPv4 or IPv6 address configured on one of the router 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.

Documentation
Changing the Alternative Facility Name for System Log Messages Directed to a
Remote Destination
Some facilities assigned to messages logged on the local router or switch have Junos
OS-specific names (see Junos OS System Logging Facilities and Message Severity Levels).
In the recommended configuration, a remote machine designated at the [edit system
syslog host hostname] hierarchy level is not a Juniper Networks router or switch, so its
syslogd utility cannot interpret the Junos OS-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 OS-specific
facility name.
Table 7 on page 17 lists the default alternative facility name next to the Junos OS-specific
facility name it is used for.
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 router
or switch or the remote machine itself). For example, the following statements in the
configuration of the router called local-router direct messages from the authorization
facility to the remote machine monitor.mycompany.com:

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, then the file contains 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;
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 17 lists the facilities that you can specify in the facility-override statement.
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 OS
system logging utility can interpret the Junos OS-specific names.
The following example shows how to log all messages generated on the local router at
the error level or higher to the local0 facility on the remote machine called
monitor.mycompany.com:

any error;
facility-override local0;
}
The following example shows how to configure routers located in California and routers
located in New York to send messages to a single remote machine called
central-logger.mycompany.com. The messages from California are assigned to alternative
facility local0 and the messages from New York are assigned to alternative facility local2.
Configure California routers to aggregate messages in the local0 facility:

host central-logger.mycompany.com {
change-log info;
}
Configure New York routers to aggregate messages in the local2 facility:

change-log info;
}

On central-logger, you can then configure the system logging utility to write messages
from the local0 facility to the file change-log and the messages from the local2 facility
to the file new-york-config.
Related Table 7 on page 17

Documentation
Alternate Facilities for System Log Messages Directed to a Remote Destination on
page 17

Default Facilities for System Log Messages Directed to a Remote Destination
Table 7 on page 17 lists the default alternative facility name next to the Junos OS-specific
facility name for which it is used. 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

Junos OSSpecific Local
Facility Default Facility When Directed to Remote Destination
change-log local6
conflict-log local5
dfc local1
firewall local3
interactive-commands local7
pfe local4

Documentation
Alternate Facilities for System Log Messages Directed to a Remote Destination
Table 8 on page 17 lists the facilities that you can specify in the facility-override statement.
Table 8: Facilities for the facility-override Statement

Facility Description
authorization Authentication and authorization attempts
daemon Actions performed or errors encountered by system processes
ftp Actions performed or errors encountered by the FTP process

Table 8: Facilities for the facility-override Statement (continued)

Facility Description
kernel Actions performed or errors encountered by the Junos OS kernel
local0 Local facility number 0
user 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 OS
system logging utility can interpret the Junos OS-specific names.
Related Examples: Assigning an Alternative Facility to System Log Messages Directed to a

Documentation Remote Destination on page 18
Single-Chassis System Logging Configuration Overview
Examples: Assigning an Alternative Facility to System Log Messages Directed to

a Remote Destination
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:

any error;
}
Configure routing platforms located in California 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:


change-log info;
}
Configure New York routing platforms to aggregate messages in the local2 facility:

change-log info;
}
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.
Related Alternate Facilities for System Log Messages Directed to a Remote Destination on
Documentation page 17
Adding a Text String to System Log Messages Directed to a Remote Destination
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 OS system logging utility automatically appends a colon and a space to the
specified string when the system log messages are written to the log. The string is inserted
after the identifier for the Routing Engine that generated the message.
The following example shows how to 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:

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


Documentation
Specifying Log File Size, Number, and Archiving Properties on page 20
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:

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
Specifying Log File Size, Number, and Archiving Properties

To prevent log files from growing too large, by default the Junos OS system logging utility
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 EX Series switches
1 megabyte (MB) for M Series, MX Series, and T Series routers
10 MB for TX Matrix or TX Matrix Plus routers
1 MB for the QFX Series
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. This process is also known
as file rotation. 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 and when the size of the active file reaches
the configured maximum size, the contents of the last archived file are overwritten by
the current active file. The logging utility by default also limits the users who can read
log files to the root user and users who have Junos OS maintenance permission.
Junos OS provides a configuration statement log-rotate-frequency that configures the

system log file rotation frequency by configuring the time interval for checking the log
file size. The frequency can be set to a value of 1 minute through 59 minutes. The default
frequency is 15 minutes.
To configure the log rotation frequency, include the log-rotate-frequency statement at

the [edit system syslog] hierarchy level.

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:
archive <files number> <size size> <world-readable | no-world-readable>;
To configure values that apply to a specific log file, include the archive statement at the
[edit system syslog file filename] hierarchy level:
archive <archive-sites (ftp-url <password password>)> <files number> <size size>

no-world-readable> ;
archive-sites site-name specifies a list of archive sites that you want to use for storing
files. The site-name value is any valid FTP URL to a destination. If more than one site
name is configured, a list of archive sites for the system log files is created. When a file
is archived, the router or switch attempts to transfer the file to the first URL in the list,
moving to the next site only if the transfer does not succeed. The log file is stored at the
archive site with the specified log filename. For information about how to specify valid
FTP URLs, see Format for Specifying Filenames and URLs in Junos OS CLI Commands.
binary-data Mark file as containing binary data. This allows proper archiving of binary
files, such as WTMP files (login records for UNIX based systems). To restore the default
setting, include the no-binary-data statement.
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.
start-time "YYYY-MM-DD.hh:mm" defines the date and time in the local time zone for a
one-time transfer of the active log file to the first reachable site in the list of sites specified
by the archive-sites statement.
transfer-interval interval defines the amount of time the current log file remains open
(even if it has not reached the maximum possible size) and receives new statistics before
it is closed and transferred to an archive site. This interval value can be from 5 through
2880 minutes.
world-readable enables all users to read log files. To restore the default permissions,
include the no-world-readable statement.

Documentation

Including Priority Information in System Log Messages

The facility and severity level of a message are together referred to as its priority. By
default, messages logged in the standard Junos OS 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. 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.
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;
NOTE: The other-routing-engine option does not apply to the QFX Series.
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 OS system logging utility still uses the alternative facility name for the messages
themselves when directing them to the remote destination. For more information, see
Changing the Alternative Facility Name for System Log Messages Directed to a Remote
Destination on page 15.
When the explicit-priority statement is included, the Junos OS 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 OS system log messages.)
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

Documentation
System Log Facility Codes and Numerical Codes Reported in Priority Information
Table 9 on page 23 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 23 does not include the Junos
OS facility name for a code, the facility cannot be included in a statement at
the [edit system syslog] hierarchy level. Junos OS might use the facilities in
Table 9 on page 23and others that are not listedwhen reporting on internal
operations.
Table 9: Facility Codes Reported in Priority Information

Junos Facility
Code Name Type of Event or Error
AUTH authorization Authentication and authorization attempts
AUTHPRIV Authentication and authorization attempts that can be viewed

by superusers only
CHANGE change-log Changes to Junos OS configuration
CONFLICT conflict-log Specified configuration is invalid on the router type
CONSOLE Messages written to /dev/console by the kernel console

output r
CRON Actions performed or errors encountered by the cron process
DAEMON daemon Actions performed or errors encountered by system processes
DFC dfc Actions performed or errors encountered by the dynamic flow

capture process
FIREWALL firewall Packet filtering actions performed by a firewall filter
FTP ftp Actions performed or errors encountered by the FTP process

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

Junos Facility
Code Name Type of Event or Error
INTERACT interactive-commands Commands issued at the Junos OS CLI prompt or invoked by

a client application such as a Junos XML protocol or NETCONF
client
KERN kernel Actions performed or errors encountered by the Junos kernel
NTP Actions performed or errors encountered by the Network Time

Protocol (NTP)
PFE pfe Actions performed or errors encountered by the Packet

Forwarding Engine
SYSLOG Actions performed or errors encountered by the Junos system

logging utility
USER user Actions performed or errors encountered by user-space

processes
Table 10 on page 24 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 Severity
Code Level Description
0 emergency System panic or other condition that causes the router to stop
functioning
1 alert Conditions that require immediate correction, such as a corrupted

system database
2 critical Critical conditions, such as hard errors
3 error Error conditions that generally have less serious consequences than
errors in the emergency, alert, and critical levels
4 warning Conditions that warrant monitoring
5 notice Conditions that are not errors but might warrant special handling
6 info Events or nonerror conditions of interest
7 debug Software debugging messages (these appear only if a technical support

representative has instructed you to configure this severity level)


Documentation
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:

However, the timestamp for traceoption messages is specified in milliseconds by default,

and is independent of the [edit system syslog time-format] statement.
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.
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 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 contents
of a structured-data message, see the Junos OS System Log Messages
Reference.

Documentation
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:
You can include this statement at the following hierarchy levels:
[edit system syslog file filename] (for a file)
[edit system syslog user (username | *)] (for a specific user session or for all user sessions
on a terminal)
[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 26 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.
Table 11: Regular Expression Operators for the match Statement
Operator Matches
. (period) One instance of any character except the space.
* (asterisk) Zero or more instances of the immediately preceding term.
+ (plus sign) One or more instances of the immediately preceding term.
? (question mark) Zero or one instance of the immediately preceding term.
| (pipe) One of the terms that appears on either side of the pipe operator.
! (exclamation point) 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 OS-specific.
^ (caret) 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.
$ (dollar sign) End of a line.

Table 11: Regular Expression Operators for the match

Statement (continued)
Operator Matches
[ ] (paired square One instance of one of the enclosed alphanumeric characters. To
brackets) 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.
( ) (paired parentheses) One instance of the evaluated value of the enclosed term.
Parentheses are used to indicate the order of evaluation in the regular
expression.
Using Regular Filter messages that belong to the interactive-commands facility, directing those that
Expressions include the string configure to the terminal of the root user:

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 a severity of 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:

file process-errors {
daemon error;
match !(.*snmpd.*);
}
file snmpd-errors {
daemon error;
match .*snmpd.*;
}

Documentation
Junos System Log Regular Expression Operators for the match Statement
Table 12: Regular Expression Operators for the match Statement

Operator Matches
. (period) One instance of any character except the space.
* (asterisk) Zero or more instances of the immediately preceding term.

Table 12: Regular Expression Operators for the match

Statement (continued)
Operator Matches
+ (plus sign) One or more instances of the immediately preceding term.
? (question Zero or one instance of the immediately preceding term.

mark)
| (pipe) One of the terms that appear on either side of the pipe operator.
! (exclamation Any string except the one specified by the expression, when the exclamation
point) point appears at the start of the expression. Use of the exclamation point is
Junos OSspecific.
^ (caret) The 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.
$ (dollar sign) The end of a line.
[ ] (paired square One instance of one of the enclosed alphanumeric characters. To indicate a
brackets) 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.
( ) (paired One instance of the evaluated value of the enclosed term. Parentheses are
parentheses) used to indicate the order of evaluation in the regular expression.

Documentation
Disabling the System 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:

console {
any error;
daemon none;
kernel none;
}
file internals {
daemon info;

kernel info;
}

Documentation
Examples: Configuring System Logging

The following example shows how to configure the logging of messages about all
commands entered by users at the CLI prompt or invoked by client applications such as
Junos OS XML protocol or NETCONF client applications, 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 * {
authorization info;
}
}
The following example shows how to configure the logging of all changes in the state of
alarms to the file /var/log/alarms:
[edit system]
syslog {
file alarms {
kernel warning;
}
}
The following example shows how to 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;
}
/* 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 */
daemon info;
any warning;
}
/* write all messages at level "error" and above to the system console */
console {
any error;
}
}
The following example shows how to configure the handling of messages generated
when users issue Junos OS 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 {
file user-actions {
}
user philip {
interactive-commands notice;
}
console {
interactive-commands warning;
}
}

Documentation

Configuring System Logging for a TX Matrix Router
To configure system logging for all routers in a routing matrix composed of a TX Matrix
router and T640 routers, include the syslog statement at the [edit system] hierarchy level
on the TX Matrix router. The syslog statement applies to every router in the routing matrix.
[edit system]
syslog {
console {
facility severity;
}
file filename {
facility severity;
no-world-readable>;
explicit-priority;
structured-data {
brief;
}
}
host (hostname | other-routing-engine | scc-master) {
facility severity;
explicit-priority;
log-prefix string;
port port number;
}
(username | *) {
facility severity;
}
}
When included in the configuration on the TX Matrix router, the following configuration
statements have the same effect as on a single-chassis system, except that they apply
to every router in the routing matrix:
archiveSets the size and number of log files on each platform in the routing matrix.
See Specifying Log File Size, Number, and Archiving Properties on page 20.
consoleDirects the specified messages to the console of each platform in the routing
matrix. See Directing System Log 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 System Log 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
The separate match statement at the [edit system syslog host scc-master] hierarchy
level applies to messages forwarded from the T640 routers to the TX Matrix router.
See Configuring Optional Features for Forwarded Messages on a TX Matrix Plus Router.
portSpecifies the port number of the remote syslog server.
source-addressSets the IP address of the router 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. On a routing matrix composed of a TX Matrix router and
T640 routers, the address is not reported by the T640 routers in messages directed
to the other Routing Engine on each router or to the TX Matrix router. See Specifying
an Alternative Source Address for System Log Messages Directed to a Remote
Destination on page 15.
structured-dataWrites messages to a file in structured-data format. See Logging

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 25.
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
System Log Messages to a User Terminal on page 13.
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 33

Configuring Optional Features for Forwarded Messages on page 36
Directing Messages to a Remote Destination from the Routing Matrix Based on the TX
Matrix Router on page 37
Configuring System Logging Differently on Each T640 Router in a Routing
Matrix on page 38
Configuring System Logging for a TX Matrix Plus Router on page 40
Configuring Message Forwarding to the TX Matrix Plus Router on page 42
Impact of Different Local and Forwarded Severity Levels on System Log Messages on
a TX Matrix Plus Router on page 43
Configuring Optional Features for Forwarded Messages on a TX Matrix Plus
Router on page 45
Directing Messages to a Remote Destination from the Routing Matrix Based on a TX
Matrix Plus Router on page 46
Configuring System Logging Differently on Each T1600 or T4000 Router in a Routing
Matrix on page 47

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 the host
scc-master statement at the [edit system syslog] hierarchy level on the TX Matrix platform:

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

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.
To the terminal session of one or more specific users (or all users), as described in
Directing System Log Messages to a User Terminal on page 13.
To the console, as described in Directing System Log 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 Based on the TX Matrix Router on page 37.
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.)
a TX Matrix Router on page 34

Impact of Different Local and Forwarded Severity Levels on System Log Messages
on a TX Matrix Router
This topic describes the impact of different local and forwarded severity levels configured
for system log messages on a TX Matrix router:
Messages Logged When the Local and Forwarded Severity Levels Are the
Same on page 34
Messages Logged When the Local Severity Level Is Lower on page 34
Messages Logged When the Local Severity Level Is Higher on page 35
Messages Logged When the Local and Forwarded Severity Levels Are the Same
When the severity level is the same for local and forwarded messages, the log on the TX
Matrix router contains all messages from the logs on the T640 routers. For example, you
can specify severity info for the /var/log/messages file, which is the default severity level
for messages forwarded by T640 routers:

file messages {
any info;
}
Table 13 on page 34 specifies which messages are included in the logs on the T640
routers and the TX Matrix router.
Table 13: Example: Local and Forwarded Severity Level Are Both info
Log Location Source of Messages Lowest Severity Included
T640 router Local info
TX Matrix router Local info
Forwarded from T640 routers info
Messages Logged When the Local Severity Level Is Lower
When the severity level is lower for local messages than for forwarded messages, the
log on the TX Matrix router 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, on a TX Matrix router, you can specify severity notice for the
/var/log/messages file and severity critical for forwarded messages:

file messages {
any notice;
}
host scc-master {
any critical;
}

Table 14 on page 35 specifies which messages in a routing matrix are included in the logs
on the T640 routers and the TX Matrix router. The T640 routers forward only those
messages with severity critical and higher, so the log on the TX Matrix router does not
include the messages with severity error, warning, or notice that the T640 routers log
locally.
Table 14: Example: Local Severity Is notice, Forwarded Severity Is critical

T640 router Local notice
TX Matrix router Local notice
Forwarded from T640 routers critical
Messages Logged When the Local Severity Level Is Higher
When the severity level is higher for local messages than for forwarded messages, the
log on the TX Matrix router 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:

file messages {
any critical;
}
host scc-master {
any notice;
}
routers and the TX Matrix router. Although the T640 routers forward messages with
severity notice and higher, the TX Matrix router 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 15: Example: Local Severity Is critical, Forwarded Severity Is notice

T640 router Local critical
TX Matrix router Local critical
Related Configuring System Logging for a TX Matrix Router

Documentation

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;
}
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 System Log
Messages Directed to a Remote Destination on page 15.
1. Including Priority Information in Forwarded Messages on page 36

2. Adding a Text String to Forwarded Messages on page 37
3. Using Regular Expressions to Refine the Set of Forwarded Messages on page 37
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 Based
on a TX Matrix Plus Router.
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 on
the TX Matrix platform also includes messages with those characteristics forwarded
from the T640 routing nodes.


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
Directed to a Remote Destination on page 19.
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 25.
Directing Messages to a Remote Destination from the Routing Matrix Based on the TX Matrix
Router
You can configure a routing matrix composed of a TX Matrix router and T640 routers to
direct system logging messages to a remote machine or the other Routing Engine on
each router, just as on a single-chassis system. Include the host statement at the [edit
system syslog] hierarchy level on the TX Matrix router:

facility severity;
explicit-priority;
log-prefix string;
}
The TX Matrix router 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 System Log Messages to a
Remote Machine or the Other Routing Engine.
For the TX Matrix router to include priority information when it directs messages that
originated on a T640 router 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 routers to the TX Matrix router. 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
router 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 router.
Because the configuration on the TX Matrix router applies to the T640 routers, any T640
router that has interfaces for direct access to the Internet also directs messages to the
remote machine. The consequences include the following:
If the T640 routers are configured to forward messages to the TX Matrix router (as in
the default configuration), the remote machine receives two copies of some messages:
one directly from the T640 router and the other from the TX Matrix router. 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 to the TX Matrix Router.
If the source-address statement is configured at the [edit system syslog] hierarchy

level, all routers in the routing matrix report the same source address in messages
directed to the remote machine. This is appropriate, because the routing matrix
functions as a single router.
If the log-prefix statement is included, the messages from all routers in the routing
matrix include the same text string. You cannot use the string to distinguish between
the routers in the routing matrix.

Documentation
Configuring System Logging Differently on Each T640 Router in a Routing Matrix

We recommend that all routers in a routing matrix composed of a TX Matrix router and
T640 routers use the same configuration, which implies that you include system logging
configuration statements on the TX Matrix router only. In rare circumstances, however,
you might choose to log different messages on different routers. For example, if one
router in the routing matrix is experiencing problems with authentication, a Juniper
Networks support representative might instruct you to log messages from the authorization
facility with severity debug on that router.
To configure routers separately, include configuration statements in the appropriate

groups at the [edit groups] hierarchy level on the TX Matrix router:
To configure settings that apply to the TX Matrix router but not the T640 routers,
include them in the re0 and re1 configuration groups.
To configure settings that apply to particular T640 routers, include them in the lccn-re0
and lccn-re1 configuration groups, where n is the line-card chassis (LCC) index number
of the router.
When you use configuration groups, do not issue CLI configuration-mode commands to
change statements at the [edit system syslog] hierarchy level on the TX Matrix router. If
you do, the resulting statements overwrite the statements defined in configuration groups

and apply to the T640 routers also. (We further recommend that you do not issue CLI
configuration-mode commands on the T640 routers at any time.)
The following example shows how to configure the /var/log/messages files on three
routers to include different sets of messages:
On the TX Matrix router, local messages with severity info and higher from all facilities.
The file does not include messages from the T640 routers, because the host scc-master
statement disables message forwarding.
On the T640 router designated LCC0, messages from the authorization facility with
severity info and higher.
On the T640 router 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;
}
}
}
}
lcc0-re1 {
}


Documentation
Configuring System Logging for a TX Matrix Plus Router

From the perspective of the user interface, the routing matrix appears as a single router.
The TX Matrix Plus router (also called the switch-fabric chassis SFC) controls all the
T1600 or T4000 routers (also called the line-card chassis LCC) in the routing matrix.
To configure system logging for all routers in a routing matrix composed of a TX Matrix
Plus router with connected T1600 or T4000 LCCs, include the syslog statement at the
[edit system] hierarchy level on the SFC. The syslog statement applies to every router in
the routing matrix.
[edit system]
syslog {
console {
facility severity;
}
file filename {
facility severity;
no-world-readable>;
explicit-priority;
structured-data {
brief;
}
}
host (hostname | other-routing-engine | sfc0-master) {
facility severity;
explicit-priority;
log-prefix string;
}
(username | *) {
facility severity;
}
}
When included in the configuration on the TX Matrix Plus router, the following
configuration statements have the same effect as on a single-chassis system, except
that they apply to every router in the routing matrix.
archiveSets the size and number of log files on each router in the routing matrix. See
Specifying Log File Size, Number, and Archiving Properties on page 20.
consoleDirects the specified messages to the console of each router in the routing
matrix. See Directing System Log Messages to the Console on page 13.

fileDirects the specified messages to a file of the same name on each router in the
routing matrix. See Directing System Log 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
The separate match statement at the [edit system syslog host sfc0-master] hierarchy
level applies to messages forwarded from the T1600 or T4000 LCCs to the SFC. See
Configuring Optional Features for Forwarded Messages on a TX Matrix Plus Router
on page 45.
source-addressSets the IP address of the router as the message source in system

log messages when the messages are directed to the remote machines specified in
all host hostname statements at the [edit system syslog] hierarchy level, for each router
in the routing matrix. On a routing matrix composed of a TX Matrix Plus router with
connected T1600 or T4000 LCCs, the address is not reported by the T1600 or T4000
routers in messages directed to the other Routing Engine on each router or to the TX
Matrix Plus router. See Specifying an Alternative Source Address for System Log
structured-dataWrites messages to a file in structured-data format. See Logging

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 25.
userDirects the specified messages to the terminal session of one or more specified
users on each router in the routing matrix that they are logged in to. See Directing
System Log Messages to a User Terminal on page 13.
The effect of the other statements differs somewhat for a routing matrix than for a
single-chassis system.
Related Configuring Message Forwarding to the TX Matrix Plus Router on page 42

Documentation
a TX Matrix Plus Router on page 43
Configuring Optional Features for Forwarded Messages on a TX Matrix Plus Router on

page 45

Matrix Plus Router on page 46
Configuring System Logging Differently on Each T1600 or T4000 Router in a Routing

Matrix on page 47

Configuring Message Forwarding to the TX Matrix Plus Router

By default, the master Routing Engine on each connected T1600 or T4000 LCC forwards
to the master Routing Engine on the SFC all messages from all facilities with severity
level of info and higher. To change the facility, the severity level, or both, include the host
sfc0-master statement at the [edit system syslog] hierarchy level on the SFC:

host sfc0-master {
facility severity;
}
To disable message forwarding, set the facility to any and the severity level to none:

host sfc0-master {
any none;
}
In either case, the setting applies to all connected LCCs in the routing matrix.
To capture the messages forwarded by the T1600 or T4000 LCCs (as well as messages
generated on the SFC itself), you must also configure system logging on the SFC. Direct
the messages to one or more destinations by including the appropriate statements at
the [edit system syslog] hierarchy level on the SFC:
To a file, as described in Directing System Log 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 System Log Messages to a User Terminal on page 13.
To the console, as described in Directing System Log 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 Based on a TX Matrix Plus Router on page 46.
As previously noted, the configuration statements included on the SFC also configure
the same destinations on each connected LCC.
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 sfc0-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.)

Related Configuring System Logging for a TX Matrix Plus Router on page 40

Documentation
Impact of Different Local and Forwarded Severity Levels on System Log Messages on a TX
Matrix Plus Router
This topic describes the impact of different local and forwarded severity levels configured
for the system log messages on a TX Matrix Plus router:
Messages Logged When the Local and Forwarded Severity Levels Are the
Same on page 43
Messages Logged When the Local Severity Level Is Lower on page 43
Messages Logged When the Local Severity Level Is Higher on page 44
Messages Logged When the Local and Forwarded Severity Levels Are the Same
When the severity level is the same for local and forwarded messages, the log on the TX
Matrix Plus router contains all messages from the logs on the T1600 routers in the routing
matrix. For example, you can specify severity info for the /var/log/messages file, which
is the default severity level for messages forwarded by T1600 routers:

file messages {
any info;
}
Table 16 on page 43 specifies which messages in a routing matrix based on a TX Matrix

Plus router are included in the logs on the T1600 routers and the TX Matrix Plus router:
Table 16: Example: Local and Forwarded Severity Level Are Both info
T1600 router Local info
TX Matrix Plus router Local info
Forwarded from T1600 routers info
Messages Logged When the Local Severity Level Is Lower
When the severity level is lower for local messages than for forwarded messages, the
log on the TX Matrix Plus router 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, on a TX Matrix Plus router, you can specify severity notice for the
/var/log/messages file and severity critical for forwarded messages:

file messages {

any notice;
}
host sfc0-master {
any critical;
}
Table 17 on page 44 specifies which messages in a routing matrix are included in the logs
on the T1600 routers and the TX Matrix Plus router. The T1600 routers forward only those
messages with severity critical and higher, so the log on the TX Matrix Plus router does
not include the messages with severity error, warning, or notice that the T1600 routers
log locally.
Table 17: Example: Local Severity Is notice, Forwarded Severity Is critical

T1600 router Local notice
TX Matrix Plus router Local notice
Messages Logged When the Local Severity Level Is Higher
When the severity level is higher for local messages than for forwarded messages, the
log on the TX Matrix Plus router 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:

file messages {
any critical;
}
host sfc0-master {
any notice;
}
routers and the TX Matrix Plus router. Although the T1600 routers forward messages
with severity notice and higher, the TX Matrix Plus router 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 18: Example: Local Severity Is critical, Forwarded Severity Is notice

T1600 router Local critical
TX Matrix Plus router Local critical


Documentation
Configuring Optional Features for Forwarded Messages on a TX Matrix Plus Router

To configure additional optional features when specifying how the connected T1600 or
T4000 LCCs forward messages to the SFC, include statements at the [edit system syslog
host sfc0-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.

host sfc0-master {
facility severity;
explicit-priority;
log-prefix string;
match "regular-expression;
}
You can also include the facility-override statement at the [edit system syslog host
sfc0-master] hierarchy level, but we do not recommend doing so. It is not necessary to
use alternative facilities for messages forwarded to the SFC, because it runs the Junos
system logging utility and can interpret the Junos OS-specific facilities. For more
information about alternative facilities, see Changing the Alternative Facility Name for
System Log Messages Directed to a Remote Destination on page 15.
1. Including Priority Information in Forwarded Messages on page 45

2. Adding a Text String to Forwarded Messages on page 46
3. Using Regular Expressions to Refine the Set of Forwarded Messages on page 46
Including Priority Information in Forwarded Messages
When you include the explicit-priority statement at the [edit system syslog host
sfc0-master] hierarchy level, messages forwarded to the TX Matrix Plus router (or the
SFC) include priority information. For the information to appear in a log file on the SFC,
you must also include the explicit-priority statement at the [edit system syslog file
filename] hierarchy level for the file on the SFC. 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 routers
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
Matrix Plus Router on page 46.

In the following example, the /var/log/messages file on all routers includes priority
information for messages with severity notice and higher from all facilities. The log on
the TX Matrix Plus router SFC also includes messages with those characteristics forwarded
from the connected T1600 or T4000 LCCs.

host sfc0-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 sfc0-master]
hierarchy level, the string that you define appears in every message forwarded to the TX
Matrix Plus router. For more information, see Adding a Text String to System Log
Using Regular Expressions to Refine the Set of Forwarded Messages
When you include the match statement at the [edit system syslog host sfc0-master]
hierarchy level, the regular expression that you specify controls which messages from
the connected T1600 or T4000 LCCs are forwarded to the TX Matrix Plus SFC. The
regular expression is not applied to messages from the connected LCCs that are directed
to destinations other than the SFC. For more information about regular expression
matching, see Using Regular Expressions to Refine the Set of Logged Messages on
page 25.
Directing Messages to a Remote Destination from the Routing Matrix Based on a TX Matrix
Plus Router
T1600 or T4000 routers also called the ine-card chassis LCC) in the routing matrix.
You can configure a routing matrix composed of a TX Matrix Plus router with connected
T1600 or T4000 LCCs to direct system logging messages to a remote machine or the
other Routing Engine on each routing router, just as on a single-chassis system. Include
the host statement at the [edit system syslog] hierarchy level on the SFC:

facility severity;
explicit-priority;
log-prefix string;
}

The TX Matrix Plus router 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 System
Log Messages to a Remote Machine or the Other Routing Engine.
For the TX Matrix Plus router to include priority information when it directs messages
that originated on a connected T1600 or T4000 LCC to the remote destination, you must
also include the explicit-priority statement at the [edit system syslog host sfc0-master]
hierarchy level.
The other-routing-engine statement does not interact with message forwarding from the
connected T1600 or T4000 LCCs to the SFC. For example, if you include the statement
in the configuration for the Routing Engine in slot 0 (re0), the re0 Routing Engine on each
connected T1600 or T4000 LCC sends messages to the re1 Routing Engine on its router
only. It does not also send messages directly to the re1 Routing Engine on the SFC.
Because the configuration on the SFC applies to the connected T1600 or T4000 LCCs,
any LCC that has interfaces for direct access to the Internet also directs messages to the
remote machine. The consequences include the following:
If the LCCs are configured to forward messages to the SFC (as in the default
configuration), the remote machine receives two copies of some messages: one directly
from the T1600 or T4000 LCC and the other from the SFC. 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 to
the TX Matrix Plus Router on page 42.
If the source-address statement is configured at the [edit system syslog] hierarchy

level, all routers in the routing matrix report the same source address in messages
directed to the remote machine. This is appropriate, because the routing matrix
functions as a single routing router.
If the log-prefix statement is included, the messages from all routers in the routing
matrix include the same text string. You cannot use the string to distinguish between
the routers in the routing matrix.

Documentation
Configuring System Logging Differently on Each T1600 or T4000 Router in a Routing Matrix
We recommend that all routers in a routing matrix composed of a TX Matrix Plus router
with T1600 or T4000 routers use the same configuration, which implies that you include
system logging configuration statements on the TX Matrix Plus router only. In rare
circumstances, however, you might choose to log different messages on different routers.
For example, if one router in the routing matrix is experiencing problems with
authentication, a Juniper Networks support representative might instruct you to log
messages from the authorization facility with severity debug on that router.

To configure routers separately, include configuration statements in the appropriate

groups at the [edit groups] hierarchy level on the TX Matrix Plus router:
To configure settings that apply to the TX Matrix Plus router but not the T1600 or
T4000 routers, include them in the re0 and re1 configuration groups.
To configure settings that apply to particular T1600 or T4000 routers, include them
in the lccn-re0 and lccn-re1 configuration groups, where n is the line-card chassis (LCC)
index number of the router.
When you use configuration groups, do not issue CLI configuration-mode commands to
change statements at the [edit system syslog] hierarchy level on the TX Matrix Plus
router. If you do, the resulting statements overwrite the statements defined in
configuration groups and apply to the T1600 or T4000 routers also. (We further
recommend that you do not issue CLI configuration-mode commands on the T1600 or
T4000 routers at any time.)
For more information about the configuration groups for a routing matrix, see the chapter
about configuration groups in the CLI User Guide.
The following example shows how to configure the /var/log/messages files on three
routers to include different sets of messages:
On the TX Matrix Plus router, local messages with severity info and higher from all
facilities. The file does not include messages from the T1600 or T4000 routers, because
the host sfc0-master statement disables message forwarding.
On the T1600 or T4000 router designated LCC0, messages from the authorization
facility with severity info and higher.
On the T1600 or T4000 router designated LCC1, messages with severity notice from
all facilities.
[edit groups]
re0 {
system {
syslog {
file messages {
any info;
}
host sfc0-master {
any none;
}
}
}
}
re1 {
... same statements as for re0 ...
}
lcc0-re0 {
system {
syslog {
file messages {
authorization info;
}

}
}
}
lcc0-re1 {
}
lcc1-re0 {
system {
syslog {
file messages {
any notice;
}
}
}
}
lcc0-re1 {
}

Documentation
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 CLI Explorer.
Displaying a Log File from a Single-Chassis System on page 49

Displaying a Log File from a Routing Matrix on page 50
Interpreting System Log Messages on page 50
Format of the message-source Field on page 57
Examples: Displaying a Log File on page 59
Displaying a Log File from a Single-Chassis System

To display a log file stored on a single-chassis system, enter Junos OS 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 Messages Generated
in Standard Format by a Junos OS Process or Library on page 55, Interpreting Messages
Generated in Standard Format by Services on a PIC on page 56, and Interpreting
Messages Generated in Structured-Data Format on page 51. For examples, see
Examples: Displaying a Log File on page 59.
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 OS 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 49.
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> show log lcc2:messages

user@host> show log lcc2-master:messages
user@host> show log lcc2-re0:messages
user@host> 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
a TX Matrix Router on page 34.
For information about the fields in a log message, see Interpreting Messages Generated
in Structured-Data Format on page 51, Interpreting Messages Generated in Standard
Format by Services on a PIC on page 56, and Interpreting Messages Generated in
Standard Format by a Junos OS Process or Library on page 55. For examples, see
Examples: Displaying a Log File on page 59.
Interpreting System Log Messages

The fields in a message written to the system log depend on whether the message was
generated by a Junos OS 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 51

Interpreting Messages Generated in Standard Format by a Junos OS Process or
Library on page 55
Interpreting Messages Generated in Standard Format by Services on a PIC on page 56
Interpreting Messages Generated in Structured-Data Format
Beginning in Junos OS Release 8.3, when the structured-data statement is included in

the configuration for a log file, Junos OS 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.
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 19 on page 51 describes the fields. If the system logging utility cannot determine
the value in a particular field, a hyphen ( - ) appears instead.
Table 19: Fields in Structured-Data Messages
Field Description Examples

<priority code> Number that indicates the messages <165> for a message from
facility and severity. It is calculated by the pfe facility
multiplying the facility number by 8 and (facility=20) with
then adding the numerical value of the severity notice
severity. For a mapping of the numerical (severity=5).
codes to facility and severity, see
Specifying the Facility and Severity of
Messages to Include in the Log on
page 9.
version Version of the Internet Engineering Task 1 for the initial version
Force (IETF) system logging protocol
specification.

Table 19: Fields in Structured-Data Messages (continued)
Field Description Examples

timestamp Time when the message was generated, 2007-02-15T09:17:15.719Z
in one of two representations: is 9:17 AM UTC on 15
February 2007.
YYYY-MM-DDTHH:MM:SS.MSZ is the 2007-02-15T01:17:15.719
year, month, day, hour, minute, -08:00 is the same
second and millisecond in Universal timestamp expressed as
Coordinated Time (UTC) Pacific Standard Time in
YYYY-MM-DDTHH:MM:SS.MS+/-HH:MM the United States.
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 router1

generated the message.
process Name of the Junos OS process that mgd

processID UNIX process ID (PID) of the Junos OS 3046

process that generated the message.
TAG Junos OS system log message tag, UI_DBASE_LOGOUT_EVENT

which uniquely identifies the message.
junos@2636.platform An identifier for the type of hardware junos@2636.1.1.1.2.18 for

platform that generated the message. the M120 router
The junos@2636 prefix indicates that
the platform runs Junos OS. It is
followed by a dot-separated numerical
identifier for the platform type. For a list
of the identifiers, see
Table 21 on page 54.
variable-value-pairs A variable-value pair for each element username="regress"

in the message-text string that varies
depending on the circumstances that
triggered the message. Each pair
appears in the format variable = "value".
message-text English-language description of the User 'regress' exiting

event or error (omitted if the brief configuration mode
statement is included at the [edit system
syslog file filename structured-data]
hierarchy level). For the text for each
message, see the chapters following
System Log Messages.
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 20 on page 53 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 20 on page 53
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.
Table 20: Facility and Severity Codes in the priority-code Field
Severity
Facility (number) emergency alert critical error warning notice info debug
kernel (0) 1 1 2 3 4 5 6 7
user (1) 8 9 10 11 12 13 14 15
mail (2) 16 17 18 19 20 21 22 23
daemon (3) 24 25 26 27 28 29 30 31
authorization (4) 32 33 34 35 36 37 38 39
syslog (5) 40 41 42 43 44 45 46 47
printer (6) 48 49 50 51 52 53 54 55
news (7) 56 57 58 59 60 61 62 63
uucp (8) 64 65 66 67 68 69 70 71
clock (9) 72 73 74 75 76 77 78 79
authorization-private 80 81 82 83 84 85 86 87
(10)
ftp (11) 88 89 90 91 92 93 94 95
ntp (12) 96 97 98 99 100 101 102 103
security (13) 104 105 106 107 108 109 110 111

Table 20: Facility and Severity Codes in the priority-code Field (continued)
Severity
Facility (number) emergency alert critical error warning notice info debug
console (14) 112 113 114 115 116 117 118 119
local0 (16) 128 129 130 131 132 133 134 135
dfc (17) 136 137 138 139 140 141 142 143
local2 (18) 144 145 146 147 148 149 150 151
firewall (19) 152 153 154 155 156 157 158 159
pfe (20) 160 161 162 163 164 165 166 167
conflict-log (21) 168 169 170 171 172 173 174 175
change-log (22) 176 177 178 179 180 181 182 183
interactive-commands 184 185 186 187 188 189 190 191

(23)
Table 21 on page 54 lists the numerical identifiers for routing platforms that appear in
the platform field. The identifier is derived from the platforms SNMP object identifier
(OID) as defined in the Juniper Networks routing platform MIB. For more information
about OIDs, see the Network Management Administration Guide for Routing Devices.
Table 21: Platform Identifiers in the platform Field
Identifier Platform Name

1.1.1.2.1 M40 router
1.1.1.2.2 M20 router
1.1.1.2.3 M160 router
1.1.1.2.4 M10 router
1.1.1.2.5 M5 router
1.1.1.2.6 T640 routing node
1.1.1.2.7 T320 router
1.1.1.2.8 M40e router
1.1.1.2.9 M320 router
1.1.1.2.10 M7i router

Table 21: Platform Identifiers in the platform Field (continued)
Identifier Platform Name

1.1.1.2.11 M10i router
1.1.1.2.17 TX Matrix platform
1.1.1.2.18 M120 router
1.1.1.2.27 T1600 router
1.1.1.2.37 TX Matrix Plus platform
1.1.1.2.83 T4000 router
Interpreting Messages Generated in Standard Format by a Junos OS Process or

Library
The syntax of a standard-format message generated by a Junos OS 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 22 on page 55 describes the message fields.
Table 22: Fields in Standard-Format Messages Generated by a Junos OS

process or Library
Field Description
timestamp Time at which the message was logged.
message-source 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 The
message-source Field on a TX Matrix Platform on page 58,The message-source
Field on a T640 Routing Node in a Routing Matrix, and The message-source
Field on a Single-Chassis System on page 57.
facility Code that specifies the facility to which the system log message belongs. For
a mapping of codes to facility names, see Table: Numerical Codes for Severity
Levels Reported in Priority Information in Including Priority Information in System
Log Messages on page 22.

Table 22: Fields in Standard-Format Messages Generated by a Junos OS

process or Library (continued)
Field Description
severity Numerical code that represents the severity level assigned to the system log
message. For a mapping of codes to severity names, see Table: Numerical
Codes for Severity Levels Reported in Priority Information in Including Priority
Information in System Log Messages on page 22.
TAG 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.
message-text Text of the message. For the text for each message, see the chapters following
System Log Messages.
Interpreting Messages Generated in Standard Format by Services on a PIC
Standard-format system log messages generated by services on a PIC, such as the

Adaptive Services (AS) PIC, have the following syntax:
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 23 on page 56 describes the message fields.
Table 23: Fields in Messages Generated by a PIC
Field Description
timestamp Time at which the message was logged.
fpc-slot Slot number of the Flexible PIC Concentrator (FPC) that houses the PIC that
pic-slot Number of the PIC slot on the FPC in which the PIC that generated the
message resides.
service-set Name of the service set that generated the message.

Table 23: Fields in Messages Generated by a PIC (continued)
Field Description
SERVICE Code representing the service that generated the message. The codes include
the following:
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.
TAG 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.
message-text Text of the message. For the text of each message, see System Log
Messages.
Format of the message-source Field

The message-source field discussed in Interpreting Messages Generated in Standard
Format by a Junos OS Process or Library on page 55 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 57

The message-source Field on a TX Matrix Platform on page 58
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 Impact of Different Local and Forwarded Severity Levels on System Log Messages
on a TX Matrix Router on page 34.
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 24 on page 58 specifies the format of the message-source field in the various cases.
Table 24: Format of message-source Field in Messages Logged on TX

Matrix Platform
Generating Process or
Generating Machine Routing Engine Component Format
TX Matrix platform Local Process hostname process[processID]
Component hostname scc-reX

process[processID]
Other Process hostname scc-reX

scc-componentZ process
Component hostname scc-reX

T640 routing node Local Process hostname

lccY-masterprocess[processID]
Component hostname lccY-master

Other Process hostname lccY-master lccY-reX

process[processID]
Component hostname lccY-master lccY-reX

lccY-componentZ process

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.
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).
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
%DAEMON-3-SNMPD_TRAP_WARM_START: trap_generate_warm: SNMP trap: warm
start
%DAEMON-2-SNMPD_TRAP_COLD_START: trap_generate_cold: SNMP trap: cold start
Getting Help About System Log Messages
System log message tag names begin with a prefix that indicates which Junos OS 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. For information about displaying and interpreting messages, see the following
sections:
Displaying and Interpreting System Log Message Descriptions on page 60

Examples: Displaying System Log Message Descriptions on page 62
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 Junos OS that is running on a routing
platform, enter the Junos OS 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 a Perl-based expression for the variable regex. The match is not case-sensitive.
For information about Perl-based regular expressions, consult a Perl reference manual
or website such as http://perldoc.perl.org.
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 25 on page 61 describes the fields in a system log message description in this
reference or in the CLI.
Table 25: Fields in System Log Message Descriptions
Field Name in Reference Field Name in CLI Description

Name The message tag in all capital
letters.
System Log Message Message 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.
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.
Description Description More detailed explanation of

the message.
Type Type Category to which the

message belongs:
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: System Log
Message Severity Levels in
Specifying the Facility and
Severity of Messages to
Include in the Log on page 9.

Table 25: Fields in System Log Message Descriptions (continued)
Field Name in Reference Field Name in CLI Description

Cause Cause (Optional) Possible cause for
message generation. There
can be more than one cause.
Action Action (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
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


PART 2
System Log Messages

AAA System Log Messages on page 69
ACCT System Log Messages on page 71
ALARMD System Log Messages on page 75
AMD System Log Messages on page 81
ANALYZER System Log Messages on page 83
ANTISPAM System Log Messages on page 85
APPID System Log Messages on page 87
APPIDD System Log Messages on page 89
APPPXY System Log Messages on page 91
APPTRACK System Log Messages on page 93
ASP System Log Messages on page 97
AUDITD System Log Messages on page 129
AUTHD System Log Messages on page 133
AUTOCONFD System Log Messages on page 137
AUTOD System Log Messages on page 139
AV System Log Messages on page 141
BBE System Log Messages on page 145
BFDD System Log Messages on page 147
BGP System Log Messages on page 151
BOOTPD System Log Messages on page 165
CFMD System Log Messages on page 171
CHASSISD System Log Messages on page 175
CHASSISM System Log Messages on page 275
CLKSYNCD System Log Messages on page 277
COSD System Log Messages on page 287
DCBX System Log Messages on page 303
DCD System Log Messages on page 305
DDOS System Log Messages on page 313
DFCD System Log Messages on page 317

DFWD System Log Messages on page 321

DHCPD System Log Messages on page 323
DIAM System Log Messages on page 329
DOT1XD System Log Messages on page 331
DYNAMIC System Log Messages on page 335
ESWD System Log Messages on page 341
EVENTD System Log Messages on page 351
FABOAMD System Log Messages on page 361
FC System Log Messages on page 363
FCOE System Log Messages on page 369
FIP System Log Messages on page 371
FIPS System Log Messages on page 375
FLOW System Log Messages on page 377
FPCLOGIN System Log Messages on page 381
FSAD System Log Messages on page 383
FUD System Log Messages on page 393
FWAUTH System Log Messages on page 399
GPRSD System Log Messages on page 405
HNCACHED System Log Messages on page 407
ICCPD System Log Messages on page 409
IDP System Log Messages on page 411
JADE System Log Messages on page 419
JCS System Log Messages on page 423
JDIAMETERD System Log Messages on page 429
JIVED System Log Messages on page 431
JNUD System Log Messages on page 435
JPTSPD System Log Messages on page 437
JSERVICES System Log Messages on page 441
JSRPD System Log Messages on page 445
JTASK System Log Messages on page 455
JTRACE System Log Messages on page 469
KMD System Log Messages on page 471
L2ALD System Log Messages on page 487
L2CPD System Log Messages on page 503
L2TPD System Log Messages on page 507
LACP System Log Messages on page 537
LACPD System Log Messages on page 539

Part 2: System Log Messages
LFMD System Log Messages on page 541

LIBJNX System Log Messages on page 543
LIBJSNMP System Log Messages on page 553
LIBMSPRPC System Log Messages on page 559
LICENSE System Log Messages on page 563
LLDP System Log Messages on page 571
LOGIN System Log Messages on page 573
LPDFD System Log Messages on page 579
LRMUX System Log Messages on page 581
LSYSD System Log Messages on page 583
MBG System Log Messages on page 585
MCSN System Log Messages on page 601
MIB2D System Log Messages on page 603
MPLS System Log Messages on page 611
NEXTHOP System Log Messages on page 615
NSD System Log Messages on page 617
NSTRACED System Log Messages on page 619
NTPDATE System Log Messages on page 621
NTPD System Log Messages on page 623
PARSE System Log Messages on page 625
PFE System Log Messages on page 627
PFED System Log Messages on page 635
PGCPD System Log Messages on page 637
PING System Log Messages on page 639
PKID System Log Messages on page 643
PPMD System Log Messages on page 653
PPPD System Log Messages on page 655
PROFILER System Log Messages on page 663
RDD System Log Messages on page 665
RMOPD System Log Messages on page 669
RPD System Log Messages on page 673
RT System Log Messages on page 747
RTLOG System Log Messages on page 761
RTLOGD System Log Messages on page 763
RTPERF System Log Messages on page 765
SAVAL System Log Messages on page 767
SDK System Log Messages on page 769

SDXD System Log Messages on page 771

SM System Log Messages on page 775
SMTPD System Log Messages on page 777
SNMP System Log Messages on page 779
SNMPD System Log Messages on page 783
SPD System Log Messages on page 797
SSH System Log Messages on page 805
SSHD System Log Messages on page 807
SSL System Log Messages on page 809
SYSTEM System Log Messages on page 813
TFTPD System Log Messages on page 815
TRANSPORTD System Log Messages on page 819
UFDD System Log Messages on page 823
UI System Log Messages on page 825
UTMD System Log Messages on page 855
VCCPD System Log Messages on page 857
VM System Log Messages on page 863
VRRPD System Log Messages on page 865
WEB System Log Messages on page 869
WEBFILTER System Log Messages on page 875

CHAPTER 2
AAA System Log Messages
This chapter describes messages with the AAA prefix.
AAA_RADIUS_SERVER_STATE_CHANGE
System Log Message Radius server radius-server-name state changed to new-radius-server-state on
interface-name
Description This notification signifies that the specified radius server has changed state from active
to dead or vice-versa
Type Event: This message reports an event, not an error
Severity info
Facility LOG_DAEMON


CHAPTER 3
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 Unexpected error error-code from file filename
Description An error prevented the accounting statistics process from processing the indicated file.
Type Error: An error occurred
Severity warning
Facility LOG_PFE
ACCT_ACCOUNTING_FOPEN_ERROR
System Log Message Failed to open file filename: error-code
Description The accounting statistics process could not open the indicated file.
Severity warning
Facility LOG_PFE
ACCT_ACCOUNTING_SMALL_FILE_SIZE
System Log Message File filename size (file-size) is smaller than record size (record-size)
Description The size limit configured for the indicated file is smaller than the record to be written to
it.
Severity warning
Facility LOG_PFE
ACCT_BAD_RECORD_FORMAT
System Log Message Invalid statistics record: entry

Description The number of columns in the indicated record does not match the number of columns
in the accounting profile.
Severity warning
Facility LOG_PFE
ACCT_CU_RTSLIB_ERROR
System Log Message Error getting class usage statistics for interface interface-name.unit-id: error-message
Description The accounting statistics process could not obtain current class usage statistics.
Severity error
Facility LOG_PFE
ACCT_FORK_ERR
System Log Message Unable to fork: error-message
Description The accounting statistics process could not create a child process for transferring files,
for the indicated reason.
Severity error
Facility LOG_PFE
ACCT_FORK_LIMIT_EXCEEDED
System Log Message Unable to fork: too many child processes
Description 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.
Severity error
Facility LOG_PFE
ACCT_GETHOSTNAME_ERROR
System Log Message Error error-code trying to get hostname
Description A call to the gethostname() function failed.
Severity error
Facility LOG_PFE

Chapter 3: ACCT System Log Messages
ACCT_MALLOC_FAILURE
System Log Message Memory allocation failed while reallocating filter profile interface list
Description The accounting statistics process could not allocate memory from the heap.
Severity error
Facility LOG_PFE
Cause An internal software failure occurred.
Action Contact your technical support representative. For more information, see
http://kb.juniper.net/InfoCenter/index?page=content&id=KB18749.
ACCT_THREAD_CREATE_FAILURE
System Log Message Unable to create file transfer timeout thread: error-message
Description The accounting statistics process could not create a thread to ensure that file transfers
complete within the configured accounting-options time interval.
Severity error
Facility LOG_PFE
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
Description The indicated filter profile referenced the indicated counter name, which is not defined
in a firewall filter that uses the filter profile.
Severity warning
Facility LOG_PFE
Action Change the filter profile counter name to match the name defined in the firewall
configuration.
ACCT_XFER_FAILED
System Log Message Error transferring filename
Description An attempt to transfer the indicated file failed.

Severity error
Facility LOG_PFE
ACCT_XFER_POPEN_FAIL
System Log Message Error error-code in invoking command command to transfer file filename
Description A call to the popen() function failed when the accounting statistics process invoked the
indicated command to transfer the indicated file.
Severity error
Facility LOG_PFE
Action For more information, see

ACCT_XFER_TIMEDOUT
System Log Message Aborted file transfer for: filename, time-period min. interval exceeded
Description The time required to transfer a file exceeded the time configured for accounting-options
interval.
Severity error
Facility LOG_PFE

CHAPTER 4
ALARMD System Log Messages
This chapter describes messages with the ALARMD prefix. They are generated by the
alarm process (alarmd).
ALARMD_CONFIG_ACCESS_ERROR
System Log Message function-name: error-message
Description The alarm process (alarmd) experienced the indicated problem while attempting to
parse the configuration database.
Severity error
Facility LOG_DAEMON
Action Contact your technical support representative.
ALARMD_CONFIG_CLOSE_ERROR
System Log Message Unable to close configuration database
Description The alarm process (alarmd) could not close the configuration database.
Severity error
Facility LOG_DAEMON
ALARMD_CONFIG_PARSE_ERROR
System Log Message Unable to parse configuration; using defaults
Description The alarm process (alarmd) could not parse the configuration and used default values
while initializing.
Severity error

Facility LOG_DAEMON
ALARMD_CONFIG_RECONFIG_ERROR
System Log Message Re-configuration failed, using previous values
Description The alarm process (alarmd) could not parse new configuration and used previous values.
Severity error
Facility LOG_DAEMON
ALARMD_CONNECTION_FAILURE
System Log Message after count attempts process-name connect returned error: error-message
Description The alarm process (alarmd) was unable to connect to the indicated process
Severity warning
Facility LOG_DAEMON
ALARMD_DECODE_ALARM_OBJECT_ERROR
System Log Message Cannot decode error test from object alarm-object, reason alarm-reason for if_name
interface-type
Description The alarm process (alarmd) encountered invalide alarm object.
Severity error
Facility LOG_DAEMON
ALARMD_EXISTS
System Log Message alarmd already running; exiting
Description The alarm process (alarmd) exited because it discovered that another alarmd process
is already running.
Severity error
Facility LOG_DAEMON

Chapter 4: ALARMD System Log Messages
ALARMD_EXISTS_TERM_OTHER
System Log Message Killing existing alarmd and exiting
Description The alarm process (alarmd) discovered that another alarmd process is already running.
It terminated the other process and exited.
Severity error
Facility LOG_DAEMON
ALARMD_IFDALARM_TYPE_ERROR
System Log Message Unknown interface alarm type: alarm-type
Description The alarm process (alarmd) could not recognize an interface type alarm due to it's
unknown alarm type.
Severity error
Facility LOG_DAEMON
ALARMD_IFDEV_RTSLIB_FAILURE
System Log Message function-name: library-function-name failed on error-message socket (socket-option)
Description The alarm process (alarmd) failed to access an interface device because an error occurred
during the indicated call to the routing socket library.
Severity error
Facility LOG_DAEMON
ALARMD_IPC_MSG_ERROR
System Log Message function-name: error code error-code, type message-type, subtype message-subtype,
opcode message-opcode
Description The alarm process (alarmd) detected an error in an interprocess communication (IPC)
message with the indicated characteristics.
Severity error
Facility LOG_DAEMON

ALARMD_IPC_MSG_WRITE_ERROR
System Log Message alarmd_send_msg: ipc_msg_write failed: error-message.
Description The alarm process (alarmd) is not able to write a new ipc message to the given ipc pipe.
Severity warning
Facility LOG_DAEMON
ALARMD_IPC_UNEXPECTED_MSG
System Log Message function-name: invalid message received: message (message type message-type, subtype
message-subtype)
Description The alarm process (alarmd) received an unexpected message with the indicated
characteristics.
Severity error
Facility LOG_DAEMON
ALARMD_MEM_ALLOC_FAILURE
System Log Message function-name: alarmd memory allocation failed
Description The alarm process (alarmd) could not allocate memory.
Severity error
Facility LOG_DAEMON
ALARMD_MGR_CONNECT
System Log Message function-name evSelectFD: initial pipe create aborted (errno error-code)
Description The alarm process (alarmd) could not open a pipe for interprocess communication (IPC).
Severity error
Facility LOG_DAEMON

Chapter 4: ALARMD System Log Messages
ALARMD_MULTIPLE_ALARM_BIT_ERROR
System Log Message Multiple alarm bits: 0xalarm-bit
Description The alarm process (alarmd) expected one alarm bit set for an interface alarm when it
received multiple.
Severity error
Facility LOG_DAEMON
ALARMD_PIDFILE_OPEN
System Log Message Unable to open PID file 'filename': errno error-code
Description The alarm process (alarmd) could not open the file where it stores its process ID (PID).
Severity error
Facility LOG_DAEMON
Cause The alarm process (alarmd)might have detected that another alarmd process was
running and tried to read the file so that it could use the PID recorded there when
terminating the other process.
ALARMD_PIPE_WRITE_ERROR
System Log Message Pipe write error: error-message
Description The alarm process (alarmd) experienced a fatal error while writing to a pipe.
Severity error
Facility LOG_DAEMON
Cause There was no reader for the pipe.
ALARMD_SOCKET_CREATE
System Log Message Unable to create socket for process-name connection: errno error-code
Description The alarm process (alarmd) could not create socket.
Severity error
Facility LOG_DAEMON

ALARMD_UNEXPECTED_EXIT
System Log Message evMainLoop returned return-value (errno error-code)
Description The alarm process (alarmd) exited unexpectedly and reported the indicated error.
Severity error
Facility LOG_DAEMON

CHAPTER 5
AMD System Log Messages
AMD_CONFIG_CHECK_FAILED
System Log Message function-name: configuration database has errors
Description The portion of the candidate configuration related to the ALARMMGMTD process
(alarm-mgmtd) was checked for validity during a 'commit' operation. The check failed.
Severity error
Facility LOG_DAEMON
Cause The configuration was invalid.
Action Correct the invalid portion of the configuration as described in the error message on the
console.
AMD_FILE_OPEN_FAILURE
System Log Message Unable to open file 'filename': error-message
Description The ALARMMGMTD process (alarm-mgmtd) could not open the indicated file.
Severity error
Facility LOG_DAEMON


CHAPTER 6
ANALYZER System Log Messages
This chapter describes messages with the ANALYZER prefix on the Juniper Networks EX
Series switches. They are generated by the sample process (sampled), which gathers
information on mirrored traffic analysis for EX Series switches.
ANALYZER_INPUT_INTERFACES_LIMIT
System Log Message Number of analyzer input interface is exceeding error-message
Description In an analyzer session, the number of input interfaces exceeded the platform limit.
Severity alert
Facility LOG_DAEMON


CHAPTER 7
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.
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_MT
System Log Message AntiSpam: SPAM detected: source-name (source-address) action reason: reason username
username roles roles
Description 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
Severity info
Facility LOG_PFE
Cause The email is detected as a spam
Action Verify the spam to make sure it is not a false positive


CHAPTER 8
APPID System Log Messages
This chapter describes messages with the APPID 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.
APPID_SIGNATURE_LICENSE_EXPIRED
System Log Message APPID signature update license(ID=feature-id) has expired
Description APPID signature update license key has expired. Signature update may not work any
more.
Severity warning
Facility LOG_DAEMON


CHAPTER 9
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_APPPACK_DOWNLOAD_RESULT
System Log Message Application package download result(status)
Description Application package download result
Severity notice
Facility LOG_DAEMON
APPIDD_APPPACK_INSTALL_RESULT
System Log Message Application package install result(status)
Description Application package install result
Severity notice
Facility LOG_DAEMON
APPIDD_APPPACK_UNINSTALL_RESULT
System Log Message Application package uninstall result(status)
Description Application package uninstall result
Severity notice
Facility LOG_DAEMON
APPIDD_DAEMON_INIT_FAILED
System Log Message Aborted. A failure was encountered error-message

Description An attempt to start AI policy daemon failed because an error was encountered during
initialization.
Severity error
Facility LOG_DAEMON
APPIDD_INTERNAL_ERROR
System Log Message Internal Error(error-message)
Description Application-Identification daemon encountered an internal error
Severity error
Facility LOG_DAEMON
APPIDD_SCHEDULED_UPDATE_FAILED
System Log Message Failed to update application packge error-message
Description The scheduled application-identification application package update failed to start.

Device will try it again at the next scheduled time
Severity error
Facility LOG_DAEMON

CHAPTER 10
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.
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_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)
Description Report application protocol (ftp/http/pop3/smtp/imap) session is aborted
Severity warning
Facility LOG_PFE


CHAPTER 11
APPTRACK System Log Messages
This chapter describes messages with the APPTRACK prefix. They are generated by the
application tracking process (apptrack).
APPTRACK_SESSION_APP_UPDATE
System Log Message AppTrack app update: source-address/source-port->destination-address/destination-port
service-name application nested-application
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 username roles encrypted
Description A log message was sent by AppTrack, an application tracking tool, when an application
identification service identified an application in the session.
Severity info
Facility ANY
APPTRACK_SESSION_APP_UPDATE_LS
System Log Message Lsys logical-system-name: AppTrack app update:
source-address/source-port->destination-address/destination-port service-name
application nested-application
Description A log message was sent by AppTrack, an application tracking tool, when an application
identification service identified an application in the session.
Severity info
Facility ANY

APPTRACK_SESSION_CLOSE
System Log Message AppTrack session closed reason:
Description A security session being tracked by AppTrack, an application tracking tool, was closed.
Severity info
Facility ANY
APPTRACK_SESSION_CLOSE_LS
System Log Message Lsys logical-system-name: AppTrack session closed reason:
Description A security session being tracked by AppTrack, an application tracking tool, was closed.
Severity info
Facility ANY
APPTRACK_SESSION_CREATE
System Log Message AppTrack session created
destination-zone-name session-id-32 username roles encrypted
Description A security session that will be monitored by AppTrack, an application tracking tool, was
created.
Severity info
Facility ANY

Chapter 11: APPTRACK System Log Messages
APPTRACK_SESSION_CREATE_LS
System Log Message Lsys logical-system-name: AppTrack session created
destination-zone-name session-id-32 username roles encrypted
Description A security session that will be monitored by AppTrack, an application tracking tool, was
created.
Severity info
Facility ANY
APPTRACK_SESSION_VOL_UPDATE
System Log Message AppTrack volume update:
Description Apptrack, an application tracking tool, sent periodic updates on the volume (byte and
packet count) for the session that it is monitoring. The update interval is determined by
the configuration.
Severity info
Facility ANY
APPTRACK_SESSION_VOL_UPDATE_LS
System Log Message Lsys logical-system-name: AppTrack volume update:
Description Apptrack, an application tracking tool, sent periodic updates on the volume (byte and
packet count) for the session that it is monitoring. The update interval is determined by
the configuration.

Severity info
Facility ANY

CHAPTER 12
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
Description 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).
Severity info
Facility LOG_PFE
ASP_IDS_HOST_RATE
System Log Message Host destination-address, event-type ... rate=rate events/sec
Description 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.
Severity error

Facility LOG_PFE
ASP_IDS_HOST_RATE_APP
System Log Message Host destination-address (application), event-type ... rate=rate events/sec
Description 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.
Severity error
Facility LOG_PFE
ASP_IDS_INV_CLEAR_QUERY
System Log Message CLEAR: Invalid query type received-value expecting expected-value
Description 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.
Severity critical
Facility LOG_PFE
ASP_IDS_INV_CLEAR_QUERY_VER
System Log Message CLEAR: Invalid query version received-value expecting expected-value
Description 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.
Severity critical
Facility LOG_PFE
ASP_IDS_INV_SHOW_QUERY
System Log Message SHOW: Invalid query type received-value expecting expected-value

Chapter 12: 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.
Severity critical
Facility LOG_PFE
ASP_IDS_INV_SHOW_QUERY_VER
System Log Message SHOW: Invalid query version received-value expecting expected-value
Description 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.
Severity critical
Facility LOG_PFE
ASP_IDS_LIMIT_FLOW_RATE_BY_DEST
System Log Message syslog-prefix error-code: proto protocol-id (protocol-name),
destination-addressdestination-port, event-type
Description The stateful firewall discarded the packet with the indicated characteristics and did not
create a new flow, because the flow rate at the firewall exceeded the intrusion detection
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).
Severity notice
Facility LOG_PFE
ASP_IDS_LIMIT_FLOW_RATE_BY_PAIR

<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
Severity notice
Facility LOG_PFE
ASP_IDS_LIMIT_FLOW_RATE_BY_SRC
<rule-name> term <term-name> then session-limit by-source] hierarchy level. The
Severity notice
Facility LOG_PFE
ASP_IDS_LIMIT_OPEN_FLOWS_BY_DEST
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
Severity notice
Facility LOG_PFE

ASP_IDS_LIMIT_OPEN_FLOWS_BY_PAIR
<rule-name> term <term-name> then session-limit by-pair] hierarchy level. The discarded
Severity notice
Facility LOG_PFE
ASP_IDS_LIMIT_OPEN_FLOWS_BY_SRC
<rule-name> term <term-name> then session-limit by-source] hierarchy level. The
Severity notice
Facility LOG_PFE
ASP_IDS_LIMIT_PKT_RATE_BY_DEST
Description 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).

Severity notice
Facility LOG_PFE
ASP_IDS_LIMIT_PKT_RATE_BY_PAIR
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).
Severity notice
Facility LOG_PFE
ASP_IDS_LIMIT_PKT_RATE_BY_SRC
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
Severity notice
Facility LOG_PFE
ASP_IDS_NO_MEM_SHOW_CMD
System Log Message Not enough memory for show command
Description Intrusion detection services (IDS) could not service a request to show information from
IDS tables, because not enough memory was available.
Severity critical

Facility LOG_PFE
ASP_IDS_NULL_CLEAR_QUERY
System Log Message Failure: NULL query for CLEAR command.
Description 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.
Severity critical
Facility LOG_PFE
ASP_IDS_NULL_SHOW_QUERY
System Log Message Failure: NULL query for SHOW command.
Description 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.
Severity critical
Facility LOG_PFE
ASP_IDS_RULE_MATCH
term: term-name
Description 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
name), application, source (logical interface name, IP address, and port number), and
Severity info
Facility LOG_PFE
ASP_IDS_SYN_COOKIE_OFF
System Log Message Host destination-address, SYN-COOKIE protection deactivated

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.
Severity error
Facility LOG_PFE
ASP_IDS_SYN_COOKIE_ON
System Log Message Host destination-address, SYN-COOKIE protection activated
Description 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.
Severity error
Facility LOG_PFE
ASP_IDS_TCP_SYN_ATTACK
Description 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
Severity error
Facility LOG_PFE

ASP_L2TP_MESSAGE_INCOMPLETE
System Log Message IPC message lacked variable portion
Description The Layer 2 Tunneling Protocol (L2TP) did not process an interprocess communication
(IPC) message because the variable portion of the message was missing.
Severity error
Facility LOG_PFE
ASP_L2TP_NO_MEM
System Log Message Unable to allocate memory for L2TP flow for tunnel tunnel-id, session session-id
Description The Layer 2 Tunneling Protocol (L2TP) could not allocate the memory it needed to create
a flow for the indicated tunnel and session.
Severity error
Facility LOG_PFE

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)
Description 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.
Severity error
Facility LOG_PFE

ASP_L2TP_STATS_BULK_QUERY_FAILED
System Log Message Number of queries (num-queries) in statistics request exceeded limit (max-queries)
Description 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.

Severity error
Facility LOG_PFE
ASP_L2TP_STATS_VERSION_INVALID
System Log Message Invalid version received-value on statistics request (expected expected-value)
Description The Layer 2 Tunneling Protocol process (l2tpd) received a request for statistics with the
indicated version, which is not the indicated, supported version.
Severity error
Facility LOG_PFE
ASP_L2TP_TUN_GRP_ADD_FAIL_ALLOC
System Log Message Unable to add tunnel group for service set service-set: could not allocate ID
Description 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.
Severity error
Facility LOG_PFE
ASP_L2TP_TUN_GRP_ADD_FAIL_EXISTS
System Log Message Unable to add tunnel group group-id: it already exists
Description The Layer 2 Tunneling Protocol (L2TP) could not add a tunnel group with the indicated
ID because it already existed.
Severity error
Facility LOG_PFE
ASP_L2TP_TUN_GRP_CHG_FAIL_ALLOC
System Log Message Unable to change tunnel group for service set service-set: could not allocate ID
Description 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.
Severity error
Facility LOG_PFE
ASP_L2TP_TUN_GRP_CHG_FAIL_INVLD
System Log Message Unable to change tunnel group group-id: ID is invalid

Description The Layer 2 Tunneling Protocol (L2TP) could not change the tunnel group with the
indicated internal ID, because the ID is invalid.
Severity error
Facility LOG_PFE
ASP_L2TP_TUN_GRP_DEL_FAIL_INVLD
System Log Message Unable to delete tunnel group group-id: ID is invalid
Description The Layer 2 Tunneling Protocol (L2TP) could not delete the tunnel group with the
indicated internal ID, because the ID is invalid.
Severity error
Facility LOG_PFE
ASP_NAT_OUTOF_ADDRESSES
System Log Message natpool nat-pool-name is out of addresses
Description Network Address Translation (NAT) services could not allocate an address from the
indicated NAT pool, because no addresses were available.
Severity warning
Facility LOG_PFE
ASP_NAT_OUTOF_PORTS
System Log Message natpool nat-pool-name is out of ports
Description Network Address Translation (NAT) services could not allocate a port from the indicated
NAT pool, because no ports were available.
Severity warning
Facility LOG_PFE
ASP_NAT_POOL_RELEASE
System Log Message natpool release address:port[count]
Description 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.
Severity info

Facility LOG_PFE
ASP_NAT_PORT_BLOCK_ACTIVE
System Log Message source-address ->
nat-source-address:nat-source-port-range-start-nat-source-port-range-end 0xvalue1
Description When interim port block logging is configured, an interim port block log is generated at
the configured interval which carries all the information logged in
ASP_NAT_PORT_BLOCK_ALLOC including the time stamp.
Severity info
Facility LOG_PFE
ASP_NAT_PORT_BLOCK_ALLOC
nat-source-address:nat-source-port-range-start-nat-source-port-range-end
Description When Port block allocation is configured, a port block will be allocated and assigned to
a private IP if it is a first connection from that private IP or if there are no ports available
in previously allocated port block for that private IP. This has the range of NAT ports and
NAT IP allocated for that private IP.
Severity info
Facility LOG_PFE
ASP_NAT_PORT_BLOCK_RELEASE
nat-source-address:nat-source-port-range-start-nat-source-port-range-end 0xvalue1
Description Allocated port block is released.
Severity info
Facility LOG_PFE
ASP_NAT_RULE_MATCH
term: term-name
Description 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

Severity info
Facility LOG_PFE
ASP_PCP_NAT_MAP_CREATE
System Log Message source-address subscriber-address:source-port -> pcp-server-address
nat-source-address:nat-source-port
Description Create the request mapping
Severity info
Facility LOG_PFE
ASP_PCP_NAT_MAP_DELETE
System Log Message source-address subscriber-address:source-port -> pcp-server-address
nat-source-address:nat-source-port
Description Delete the request mapping
Severity info
Facility LOG_PFE
ASP_PCP_TPC_ALLOC_ERR
System Log Message Memory allocation failed for Third party client: source-address
Description Allocation error for third party context
Severity info
Facility LOG_PFE
ASP_PCP_TPC_NOT_FOUND
System Log Message Third party context not found source-address
Description PCP third party context is not found
Severity info
Facility LOG_PFE

ASP_PGCP_IPC_MSG_WRITE_FAILED
System Log Message Unable to write IPC message (type message-type, subtype message-subtype): status
code status
Description The Packet Gateway Control Protocol (PGCP) client on the MultiServices PIC could not
write an interprocess communication (IPC) message to the end of its pipe.
Severity error
Facility LOG_PFE
Action For more inofrmation, see

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
Description The Packet Gateway Control Protocol (PGCP) client on the MultiServices PIC could not
write the contents of its interprocess communication (IPC) pipe to the socket layer.
Severity error
Facility LOG_PFE
Action For more inofrmation, see

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
Description 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.
Severity warning
Facility LOG_PFE

Action 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.
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
Description 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.
Severity critical
Facility LOG_PFE
Action 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.
ASP_SFW_APP_MSG_TOO_LONG
Description 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
Severity notice
Facility LOG_PFE
Action 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.
ASP_SFW_CHANGE_INACTIVITY_TIMER
System Log Message change global inactivity timer to value1, open timeout to value2, and close timeout to
value3

Description The global inactivity timer, the close timeout, and the open timeout were set to the
indicated values.
Severity critical
Facility LOG_PFE
ASP_SFW_CREATE_ACCEPT_FLOW
destination-addressdestination-port, event-type nat-information softwire-information
Description 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), and if relevant, Softwire source
and destination IP addresses
Severity info
Facility LOG_PFE
ASP_SFW_CREATE_DISCARD_FLOW
the 'discard' action, and the stateful firewall created a discard flow. The matching packet
Severity notice
Facility LOG_PFE
ASP_SFW_CREATE_REJECT_FLOW
the 'reject' action, and the stateful firewall created a reject flow. The matching packet

Severity notice
Facility LOG_PFE
ASP_SFW_DELETE_FLOW
Description The flow with the indicated characteristics was removed from the system. If the flow
required Network Address Translation (NAT) services, NAT information appears at the
end of the message. The flow indicated information about its protocol (numerical identifier
and name), application, source (logical interface name, IP address, and port number),
destination (IP address and port number), and if relevant, Softwire source and destination
IP addresses.
Severity info
Facility LOG_PFE
ASP_SFW_DROP_FLOW_DELETE
Description Drop flow is deleted.
Severity info
Facility LOG_PFE
ASP_SFW_FTP_ACTIVE_ACCEPT
destination-addressdestination-port, event-type nat-information
Description 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

Severity notice
Facility LOG_PFE
ASP_SFW_FTP_PASSIVE_ACCEPT
destination-addressdestination-port, event-type nat-information
Description 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
Severity notice
Facility LOG_PFE
ASP_SFW_ICMP_ERROR_DROP
Description 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
Severity notice
Facility LOG_PFE
ASP_SFW_ICMP_HEADER_LEN_ERROR
Description 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
source (logical interface name, IP address, and port number), and destination (IP address
and port number).
Severity notice
Facility LOG_PFE
ASP_SFW_ICMP_PACKET_ERROR_LENGTH
Description 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,
Severity notice
Facility LOG_PFE
ASP_SFW_IP_FRAG_ASSEMBLY_TIMEOUT
Description 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).
Severity notice
Facility LOG_PFE
ASP_SFW_IP_FRAG_OVERLAP
related IP fragments it had previously received, because the contents of two fragments

overlapped. The discarded packet contained the indicated information about its protocol
Severity notice
Facility LOG_PFE
ASP_SFW_IP_OPTION_DROP_PACKET
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).
Severity notice
Facility LOG_PFE
ASP_SFW_IP_PACKET_CHECKSUM_ERROR
the packet checksum was incorrect. The discarded packet contained the indicated
Severity notice
Facility LOG_PFE
ASP_SFW_IP_PACKET_DST_BAD
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

and port number).
Severity notice
Facility LOG_PFE
ASP_SFW_IP_PACKET_FRAG_LEN_INV
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
Severity notice
Facility LOG_PFE
ASP_SFW_IP_PACKET_INCORRECT_LEN
Description 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).
Severity notice
Facility LOG_PFE
ASP_SFW_IP_PACKET_LAND_ATTACK
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

Severity notice
Facility LOG_PFE
ASP_SFW_IP_PACKET_NOT_VERSION_4
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).
Severity notice
Facility LOG_PFE
ASP_SFW_IP_PACKET_PROTOCOL_ERROR
the packet used an invalid protocol. The discarded packet contained the indicated
Severity notice
Facility LOG_PFE
ASP_SFW_IP_PACKET_SRC_BAD
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

Severity notice
Facility LOG_PFE
ASP_SFW_IP_PACKET_TOO_LONG
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
Severity notice
Facility LOG_PFE
ASP_SFW_IP_PACKET_TOO_SHORT
the packet did not contain the minimum amount of data required. The discarded packet
and port number).
Severity notice
Facility LOG_PFE
ASP_SFW_IP_PACKET_TTL_ERROR
the packet had a time-to-live (TTL) value of 0 (zero). The discarded packet contained
port number).

Severity notice
Facility LOG_PFE
ASP_SFW_NEW_POLICY
System Log Message install new configuration
Description A new stateful firewall policy was installed.
Severity critical
Facility LOG_PFE
ASP_SFW_NO_IP_PACKET
Description 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
Severity notice
Facility LOG_PFE
ASP_SFW_NO_POLICY
System Log Message source-address -> destination-addressNo policy
Description The stateful firewall received packets with the indicated source and destination addresses.
There was no matching policy for the traffic.
Severity critical
Facility LOG_PFE
ASP_SFW_NO_RULE_DROP
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

Severity notice
Facility LOG_PFE
ASP_SFW_PING_DUPLICATED_SEQNO
Description 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
Severity notice
Facility LOG_PFE
ASP_SFW_PING_MISMATCHED_SEQNO
Description 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
port number).
Severity notice
Facility LOG_PFE
ASP_SFW_PING_OUTOF_SEQNO_CACHE
Description 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
and port number).

Severity notice
Facility LOG_PFE
ASP_SFW_POLICY_REJECT
System Log Message reject configuration because reason
Description A newly installed stateful firewall policy was rejected for the indicated reason.
Severity critical
Facility LOG_PFE
ASP_SFW_RULE_ACCEPT
term: term-name
Description 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
Severity info
Facility LOG_PFE
ASP_SFW_RULE_DISCARD
term: term-name
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
Severity notice

Facility LOG_PFE
ASP_SFW_RULE_REJECT
term: term-name
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
Severity notice
Facility LOG_PFE
ASP_SFW_SYN_DEFENSE
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
number).
Severity notice
Facility LOG_PFE
Cause 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.

ASP_SFW_TCP_BAD_SYN_COOKIE_RESP
Description 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
and port number).
Severity notice
Facility LOG_PFE
ASP_SFW_TCP_FLAGS_ERROR
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
Severity notice
Facility LOG_PFE
ASP_SFW_TCP_HEADER_LEN_ERROR
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
number).

Severity notice
Facility LOG_PFE
ASP_SFW_TCP_NON_SYN_FIRST_PACKET
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
Severity notice
Facility LOG_PFE
ASP_SFW_TCP_PORT_ZERO
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
Severity notice
Facility LOG_PFE
ASP_SFW_TCP_RECONSTRUCT_DROP
indicated characteristics, because the session to which the packet belongs violated TCP
standards. The discarded packet contained the indicated information about its protocol

Severity notice
Facility LOG_PFE
Cause 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
Description 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
port number).
Severity notice
Facility LOG_PFE
ASP_SFW_TCP_SEQNO_AND_FLAGS_ZERO
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
Severity notice
Facility LOG_PFE
ASP_SFW_TCP_SEQNO_ZERO_FLAGS_SET
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 contained the

number).
Severity notice
Facility LOG_PFE
ASP_SFW_UDP_HEADER_LEN_ERROR
Description 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
number).
Severity notice
Facility LOG_PFE
ASP_SFW_UDP_PORT_ZERO
Description 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
Severity notice
Facility LOG_PFE
ASP_SFW_UDP_SCAN
Description 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 about its protocol
Severity notice
Facility LOG_PFE
ASP_SFW_VERY_BAD_PACKET
the packet was malformed. The discarded packet contained the indicated information
about its protocol (numerical identifier and name), source (logical interface name, IP
Severity critical
Facility LOG_PFE
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
Description 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.
Severity notice
Facility LOG_PFE

CHAPTER 13
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_AUTH_TYPE_ERROR
System Log Message Unable to add authentication type to type record: error-message
Description The audit process (auditd) experienced the indicated error when building RADIUS
Authentication-type attribute-value (AV) pair for the login accounting request.
Severity error
Facility LOG_DAEMON
AUDITD_RADIUS_AV_ERROR
System Log Message Unable to create type record: error-message
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.
Severity error
Facility LOG_DAEMON
AUDITD_RADIUS_AV_PORT_ERROR
System Log Message Unable to add port number to type record: error-message
Remote-port attribute-value (AV) pair for the login accounting request.
Severity error

Facility LOG_DAEMON
AUDITD_RADIUS_OPEN_FAILED
System Log Message function-name: unable to create RADIUS object handle (error-message)
Description The audit process (auditd) could not create a RADIUS object handle, which it uses for
various RADIUS operations.
Severity emergency
Facility LOG_DAEMON

AUDITD_RADIUS_REQ_CREATE_FAILED
System Log Message Unable to create RADIUS request: error-message
Description The audit process (auditd) could not create a RADIUS accounting request for the indicated
reason.
Severity error
Facility LOG_DAEMON

AUDITD_RADIUS_REQ_DROPPED
System Log Message Discarded Accounting-Request message; no RADIUS server responded
Description 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.
Severity error
Facility LOG_DAEMON
Cause The RADIUS accounting servers are not correctly configured or are unreachable, or the
server applications are not responding.
AUDITD_RADIUS_REQ_SEND_ERROR

Chapter 13: AUDITD System Log Messages
Description The audit process (auditd) experienced the indicated error when it requested accounting
information from a RADIUS server.
Severity error
Facility LOG_DAEMON
AUDITD_RADIUS_REQ_TIMED_OUT
System Log Message Retransmitted request to RADIUS server radius-server
Description 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.
Severity error
Facility LOG_DAEMON
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 Unable to add RADIUS server radius-server: error-message
Description 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.
Severity error
Facility LOG_DAEMON
Action For more information, see KB18757.
AUDITD_SOCKET_FAILURE
System Log Message function-name: unable to operation socket (error-message)
Description 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.

Severity emergency
Facility LOG_DAEMON
AUDITD_TACPLUS_SHM_CREATE_FAILED
System Log Message auditd shm create failed. stopping auditd-tacplus
Description The audit process for tacplus failed to intialize shared memory for accounting records.
This can be a temporary issue with system free memory. Please try configuring tacplus
accounting again.
Severity error
Facility LOG_DAEMON

CHAPTER 14
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_ACCOUNTING_STATE_CHANGE
System Log Message New state (new-state)
Description CLI command suspends or resumes accounting or begins baseline. Baseline completes
when all volume and time counters have been baselined.
Severity warning
Facility LOG_AUTH
AUTHD_ACCT_ON_ACK_NOT_RECEIVED
System Log Message Acct-On-Response is not yet received for profile: profile-name, logical system:
logical-system-name, routing instance: routing-instance)
Description The generic authentication service process (authd) did not send any
authentication/accounting packet to the RADIUS server because it has not received
Acct-On-Ack from the RADIUS server.
Severity error
Facility LOG_AUTH
AUTHD_AUTH_CREATE_FAILED
System Log Message Unable to allocate authentication handle: error-message
Description The generic authentication service process (authd) could not allocate an authentication
object for the indicated reason.
Severity error

Facility LOG_AUTH
Action For more inofrmation see,

AUTHD_AUTH_SERVER_STATUS_CHANGE
System Log Message Status of authentication server destination-address:destination-port set to new-state
(profile profile-name)
Description Authentication server status is changed to DOWN if it is unavailable, and it is again set
to UP after revert interval timer expires
Severity warning
Facility LOG_AUTH
AUTHD_RADIUS_GETHOSTNAME_FAILED
System Log Message Unable to obtain hostname for outgoing RADIUS message: error-message
Description The generic authentication service process (authd) could not obtain a hostname for an
outgoing RADIUS message.
Severity error
Facility LOG_AUTH
Action For more inofrmation see, KB18760.
AUTHD_SERVER_INIT_BIND_FAIL
System Log Message Unable to bind to socket file-descriptor: error-message (errno error-code)
Description The generic authentication service process (authd) could not bind the server to the
address specified.
Severity error
Facility LOG_AUTH

AUTHD_SERVER_INIT_LISTEN_FAIL
System Log Message Unable to listen on socket file-descriptor: error-message (errno error-code)
Description The generic authentication service process (authd) could not initialize listening on the
server for the indicated socket.

Chapter 14: AUTHD System Log Messages
Severity error
Facility LOG_AUTH



CHAPTER 15
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 Authentication failed due to license error. Total license failures count
Description 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.
Severity alert
Facility LOG_DAEMON
Action Add or update the license for authentication


CHAPTER 16
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 Unable to bind address to socket: error-message
Description The autoinstallation process (autod) received the indicated error when it tried to bind a
socket to an address.
Severity error
Facility LOG_DAEMON
AUTOD_HOSTNAME_EXPANSION_FAILURE
System Log Message Unable to expand compressed DNS domain name: error-message
Description The autoinstallation process (autod) received the indicated error when it tried to expand
a compressed Domain Name System (DNS) domain name.
Severity error
Facility LOG_DAEMON
AUTOD_RECV_FAILURE
System Log Message Unable to receive on socket: error-message
Description The autoinstallation process (autod) received the indicated error when it tried to receive
data on a socket.

Severity error
Facility LOG_DAEMON
AUTOD_RES_MKQUERY_FAILURE
System Log Message DNS query failed: error-message
Description The autoinstallation process (autod) received the indicated error when it made a Domain
Name System (DNS) query.
Severity error
Facility LOG_DAEMON
Action Contact your technical support representative. For more information, see KB18766.
AUTOD_SEND_FAILURE
System Log Message Unable to send on socket: error-message
Description The autoinstallation process (autod) received the indicated error when it tried to send
data on a socket.
Severity error
Facility LOG_DAEMON
AUTOD_SOCKET_CREATE_FAILURE
System Log Message Unable to create socket: error-message
Description The autoinstallation process (autod) received the indicated error when it tried to create
a socket.
Severity error
Facility LOG_DAEMON

CHAPTER 17
AV System Log Messages
This chapter describes messages with the AV prefix. They are generated by the antivirus
scanning process (avd).
AV_PATTERN_GET_FAILED
System Log Message AntiVirus: cannot retrieve pattern error-message file due to error-code (status-code).
Description 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
Severity notice
Facility LOG_FIREWALL
Cause Unable to retrieve an antivirus pattern file from the server
Action Contact Juniper Networks technical support
AV_PATTERN_KEY_EXPIRED
System Log Message AntiVirus: Attempt to time failed due to date, please renew to receive updates.
Description The internal antivirus scanner was unsuccessful in downloading the antivirus pattern file,
because the AV license key has been expired
Severity notice
Cause Download the antivirus pattern file while antivirus license key has been expired
Action Renew the antivirus license key
AV_PATTERN_KL_CHECK_FAILED
System Log Message AntiVirus: db file signature mismatch: error-message.

Description The device is unable to use Kaspersky's pattern file. The error message provides
information you need to give Juniper Networks technical support
Severity critical
Cause The device is unable to use Kaspersky's pattern file
Action Contact Juniper Networks technical suppor. For more information, see
AV_PATTERN_TOO_BIG
System Log Message AntiVirus: The pattern file specified in server is too large(file-size bytes)
Description The pattern file size specified in the server initialization file (server.ini) exceeds the
maximum prescribed limit
Severity alert
Cause The pattern file size specified in the server initialization file exceeds the limit
Action Contact Juniper Networks technical suppor. For more information, see
AV_PATTERN_UPDATED
System Log Message AntiVirus: Pattern file updated. Version: version; size: file-size bytes
Description The internal antivirus scanner successfully updated the pattern file and may have changed
the size of the file in the process
Severity notice
Cause The internal antivirus scanner successfully updated the antivirus pattern file
Action No recommended action
AV_PATTERN_WRITE_FS_FAILED
System Log Message AntiVirus: db file save failed: error-code
Description The device is unable to save contents of an antivirus pattern file to the file system

Chapter 17: AV System Log Messages
Severity critical
Cause The device is unable to save contents of an antivirus pattern file to the file syste
Action Contact Juniper Networks technical support
AV_SCANNER_READY
System Log Message AntiVirus:The scan engine is ready.
Description The antivirus scan engine is ready to scan the traffic
Severity notice
Cause The antivirus scan engine is ready
AV_VIRUS_DETECTED_MT
System Log Message AntiVirus: Virus detected: from source-address:source-port to
destination-address:destination-port source-zone source-zone-name filename file
temporary-filename virus name URL:http://www.viruslist.com/en/search?VN=url
username username roles roles
Description The antivirus scanner has detected a virus; the log will show source and destination port
and IP, source zone, contaminated file, virus name and URL link with virus description
Severity warning
Facility LOG_PFE


CHAPTER 18
BBE System Log Messages
This chapter describes messages with the BBE prefix.
BBE_MIBD_TRAP_HEADER_FAILURE
System Log Message No memory for trap request header
Description The bbe-mibd process could not allocate a trap header.
Severity error
Facility LOG_DAEMON
Cause The Routing Engine is low on memory.
BBE_MIBD_TRAP_SEND_FAILURE
System Log Message Unable to send trap: error-message
Description The bbe-mibd process could not send a trap header.
Severity error
Facility LOG_DAEMON


CHAPTER 19
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 Unable to establish BFD mirror connection between Routing Engines: error-message
Description The Bidirectional Forwarding Detection process (bfdd) could not establish the mirror
connection (which supports nonstop routing) between the master and backup Routing
Engines.
Severity warning
Facility LOG_DAEMON
Cause The master and backup Routing Engines are running incompatible versions of the Junos
OS.
Action Update the Junos OS to compatible versions on the master and backup Routing Engines.
BFDD_MIRROR_VERSION_MISMATCH
System Log Message Versions of BFD mirror software on Routing Engines are incompatible: error-message
Description 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 OS on the Routing Engines were
incompatible.
Severity warning
Facility LOG_DAEMON

BFDD_READ_ERROR
System Log Message Read error on pipe-type pipe: reason (error-message)
Description The Bidirectional Forwarding Detection process (bfdd) could not read the message
available on the indicated type of pipe.
Severity info
Facility LOG_DAEMON
BFDD_TRAP_MHOP_STATE_DOWN
System Log Message local discriminator: session-id, new state: state, peer addr: pip-interface
Description The state changed to 'down' or 'admin down' for the indicated Bidirectional Forwarding
Detection process (bfdd) session.
Severity warning
Facility LOG_DAEMON
BFDD_TRAP_MHOP_STATE_UP
System Log Message local discriminator: session-id, new state: state, peer addr: pip-interface
Description The state changed to 'up' for the indicated Bidirectional Forwarding Detection process
(bfdd) session.
Severity info
Facility LOG_DAEMON
BFDD_TRAP_SHOP_STATE_DOWN
System Log Message local discriminator: session-id, new state: state, interface: pip-interface, peer addr:
remote-peer
Severity warning
Facility LOG_DAEMON

Chapter 19: BFDD System Log Messages
BFDD_TRAP_SHOP_STATE_UP
System Log Message local discriminator: session-id, new state: state, interface: pip-interface, peer addr:
remote-peer
(bfdd) session.
Severity info
Facility LOG_DAEMON
BFDD_TRAP_STATE_DOWN
System Log Message local discriminator: session-id, new state: state
Severity warning
Facility LOG_DAEMON
BFDD_TRAP_STATE_UP
System Log Message local discriminator: session-id, new state: state
(bfdd) session.
Severity info
Facility LOG_DAEMON
BFDD_WRITE_ERROR
System Log Message function-name: write error on pipe-type pipe (error-message)
Description The Bidirectional Forwarding Detection process (bfdd) could not write a message to the
indicated type of pipe.
Severity error
Facility LOG_DAEMON


CHAPTER 20
BGP System Log Messages
This chapter describes messages with the BGP prefix. They are generated by the Border
Gateway Routing Protocol.
BGP_ADDR_NOT_FOUND
System Log Message function-name: BGP peer peer-name local address local-address not found. Leaving peer
idled
Description The BGP speaker's local address was not found. The peer will be idled.
Severity warning
Facility LOG_DAEMON
Action None.
BGP_ALLOC_BUFFER_ALREADY_EXISTS
System Log Message function-name: buffer already allocated, something screwed up!!
Description BGP encountered an error while allocating the requested buffer. The buffer already exists
and won't be allocated.
Severity error
Facility LOG_DAEMON
Action None.
BGP_BIND_FAILED_ADDR_UNAVAILABLE
System Log Message function-name: peer peer-name local address local-address unavailable, connection
failed
Description BGP was not able to bind the local address to the socket since the address is unavailable.
The peer will be restarted.

Severity warning
Facility LOG_DAEMON
Action None.
BGP_CEASE_PREFIX_LIMIT_EXCEEDED
System Log Message peer-name: Shutting down peer due to exceeding configured message(limit) for nlri-type
nlri: prefix-count (instance instance)
Description The number of prefixes received/accepted on the BGP session exceeds the configured
maximum limit. The BGP session with the peer will be torn down.
Severity error
Facility LOG_DAEMON
Action BGP session will be restablished but may be torn down again if the local speaker
receives/accepts the same number of prefixes. You may want to modify the configuration
statement to use a higher value for the received/accepted number of prefixes.
BGP_CFG_PATH_ATTRIBUTE_WARNING
System Log Message An attribute is configured to be both dropped and ignored. Drop path attribute will take
precedence and the attribute will be dropped.
Description drop-path-attributes and ignore-path-attributes knob is configured for the same attribute.
drop-path-attributes will take precedence and attribute will be dropped.
Severity warning
Facility LOG_DAEMON
BGP_CONNECT_FAILED
System Log Message bgp_connect_start: connect peer-name: error-message
Description There was an error connecting the socket to the addresss.
Severity error
Facility LOG_DAEMON
Action None.
BGP_CONNECT_GET_SOCK_ERROR
System Log Message function-name: task_get_addr_local(local-address): error-message

Chapter 20: BGP System Log Messages
Description There was an error connecting the non-blocking socket to the address immediately
because BGP was not able to determine the local address bound to the socket file
descriptor.
Severity error
Facility LOG_DAEMON
Action None.
BGP_CONNECT_SOCK_SHUTDOWN
System Log Message bgp_peer_connected: Connection to local-address refused
Description There was an error connecting the non-blocking socket to the address immmediately
perhaps because the socket was shutdown (received a TCP RST) while BGP was trying
to connect with the peer.
Severity error
Facility LOG_DAEMON
Action None.
BGP_COPY_BUFFER_ALREADY_EXISTS
System Log Message function-name: destination already has buffer allocated!!
Description BGP encountered an error while copying the buffer to another structure. The destination
structure already has a buffer allocated. The buffer pointed by the destination structure
will be freed before copying the contents from the source.
Severity error
Facility LOG_DAEMON
Action None.
BGP_ERROR_SENDING_KEEPALIVE
System Log Message function-name: error sending KEEPALIVE to peer-name: error-message
Description BGP failed to send keepalive to this peer. The BGP peer will be closed.
Severity error
Facility LOG_DAEMON

Action None.
BGP_ERROR_UNEXPECTED_LOCAL_PREF
System Log Message bgp_recv_v4_update: external peer peer-name UPDATE included LOCALPREF attribute
Description The local speaker has received an update message with a local attribute from an external
peer.
Severity warning
Facility LOG_DAEMON
Action None.
BGP_FLUSH_FAILED_AFTER_RETRYING
System Log Message function-name: sending to peer-name (sent num-bytes-sent, num-bytes remainargument)
looping: error-message
Description The write call by BGP returned with soft error on multiple tries. The corresponding bgp
peer will be closed.
Severity error
Facility LOG_DAEMON
Action None.
BGP_FREE_NONEXISTENT_BUFFER
System Log Message function-name: buffer not present, something screwed up!!
Description BGP encountered an error while freeing the requeusted buffer. The buffer does not exist
and won't be freed.
Severity error
Facility LOG_DAEMON
Action None.
BGP_GATHER_FLUSH_FAILED
System Log Message bgp_gather_timeout: Writing num-bytes bytes to peer-name failed: errno error-code,
error-message
Description Write call by BGP returned with a hard error for this socket while attempting to flush the
gather buffer.

Severity error
Facility LOG_DAEMON
Action None.
BGP_IGNORING_INVALID_PREFIX
System Log Message function-name: peer peer-name UPDATE ignoring invalid unreachable route
route-prefix/prefix-length (num-bytes of num-bytes-sent)
Description The unreachable route received in the update message will be ignored as the prefix is
invalid.
Severity error
Facility LOG_DAEMON
Action None.
BGP_NLRI_MISMATCH
System Log Message function-name: mismatch NLRI with peer-name: peer: <peer-nlri-type>(peer-nlri) us:
<nlri-type>(nlri)
Description The peer has requested some NLRIs during capability negotiation that are not supported
by the local speaker. The session will settle for the common set among the one's
advertised by the peer and us.
Severity warning
Facility LOG_DAEMON
Action None.
BGP_NO_ADDRESS_BOUND_TO_SOCKET
System Log Message function-name: task_get_addr_local(): error-message
Description The local address to which the socket is bound could not be ascertained perhaps because
a TCP RST was received. Connection will not be accepted.
Severity error
Facility LOG_DAEMON
Action None.

BGP_NO_INCOMING_INTERFACE_FOUND
System Log Message function-name: Connection received from peer-address, no incoming interface
Description The connection request packet received on the TCP socket from the peer had no matching
interface. Conection will not be accepted.
Severity error
Facility LOG_DAEMON
Action None.
BGP_OPEN_INTERNAL_VERSION_ERROR
System Log Message function-name: internal error! peer peer-name, version version
Description BGP attempted to send an open message but encountered an internal error, viz.,
unsupported BGP version number configured. The routing process will now exit.
Severity error
Facility LOG_DAEMON
Action You may want to rectify the configuration to use a supported BGP version.
BGP_ORF_BAD_MSG_HEADER
System Log Message peer-name: ORF msg header too short (length)
Description ORF message length is less than minimum message length. The ORF message won't be
processed.
Severity error
Facility LOG_DAEMON
Action None.
BGP_ORF_LEN_EXCEEDS_MAX_PFXLEN
System Log Message peer-name: ORF type prefix-based invalid length - seqnum sequence-number (length
orf-pfx-len > max_plen max-pfx-len)
Description BGP orf entry's prefix has an invalid length. The length is greater than the maximum prefix
length of BGP orf entry's prefix.

Severity error
Facility LOG_DAEMON
Action None.
BGP_ORF_MAXLEN_EXCEEDS_MAX_PFXLEN
System Log Message peer-name: ORF type prefix-based invalid maxlen seqnum sequence-number (maxlen
orf-pfx-max-len > max_plen max-pfx-len)
Description BGP orf entry prefix has an invalid max length. The maxlen is less than the maximum
prefix length of BGP orf entry's prefix.
Severity error
Facility LOG_DAEMON
Action None.
BGP_ORF_MAXLEN_LESS_THAN_MINLEN
orf-pfx-max-len minlen <orf-pfx-min-len)
Description BGP orf entry prefix has an invalid max length. The maxlen is less than the min prefix
length.
Severity error
Facility LOG_DAEMON
Action None.
BGP_ORF_MAX_PFXLEN_LESS_THAN_LEN
orf-pfx-max-len length <orf-pfx-len)
Description BGP orf entry prefix has an invalid prefix max length. The max prefix length is less than
BGP orf entry's prefix length.
Severity error
Facility LOG_DAEMON
Action None.

BGP_ORF_MINLEN_EXCEEDS_MAX_PFXLEN
System Log Message peer-name: ORF type prefix-based invalid minlen seqnum sequence-number (minlen
orf-pfx-min-len > max_plen max-pfx-len)
Description BGP orf entry prefix has an invalid min length. The minlen is greater than the maximum
prefix length of BGP orf entry's prefix.
Severity error
Facility LOG_DAEMON
Action None.
BGP_ORF_MINLEN_LESS_THAN_LEN
System Log Message peer-name: ORF type prefix-based invalid minlen seqnum sequence-number (minlen
orf-pfx-min-len = length <orf-pfx-len)
Description BGP orf entry's prefix has an invalid min length. The minlen is less than or equal to BGP
orf entry's prefix length.
Severity error
Facility LOG_DAEMON
Action None.
BGP_ORF_PREFIX_BAD_LENGTH
System Log Message peer-name: ORF msg type orf-type, bad length (length)
Description ORF message read has an invalid length and won't be processed.
Severity error
Facility LOG_DAEMON
Action None.
BGP_ORF_PREFIX_INVALID_LENGTH
System Log Message peer-name: ORF type prefix-based invalid length - seqnum sequence-number (length
orf-pfx-len > len length)
Description Prefix-based ORF request can't be processed because prefix is invalid.

Severity error
Facility LOG_DAEMON
Action None.
BGP_ORF_PREFIX_LESS_THAN_MINLEN
System Log Message peer-name: ORF type prefix-based length length is too short
Description Prefix-based ORF request can't be processed because prefix length is less than the
minimum ORF prefix length.
Severity error
Facility LOG_DAEMON
Action None.
BGP_ORF_PREFIX_LIMIT_EXCEEDED
System Log Message peer-name: Ignore ADD prefix-based ORF nlri nlri-type with seq sequence-number as orf
count count reached max limit
Description Prefix-based ORF can't be added because prefix limit has been reached for this peer and
nlri.
Severity error
Facility LOG_DAEMON
Action None.
BGP_PREFIX_LIMIT_EXCEEDED
System Log Message peer-name: Configured message(limit) exceeded for nlri-type nlri: prefix-count (instance
instance)
Description The number of prefixes received/accepted on the BGP session exceeds the configured
maximum limit.
Severity warning
Facility LOG_DAEMON
Action You may want to modify the configuration statement to use a higher value for the
received/accepted number of prefixes.

BGP_PREFIX_THRESH_EXCEEDED
System Log Message peer-name: Configured message threshold(percentage-value) exceeded for nlri-type nlri:
prefix-count (instance instance)
Description The number of prefixes received on the BGP session exceeds the specified percentage
of the configured maximum limit.
Severity warning
Facility LOG_DAEMON
Action You may want to modify the configuration statement to use a higher percentage threshold
value for the received/accepted number of prefixes.
BGP_REFRESH_FOR_UNNEGOTIATED_NLRI
System Log Message peer-name: received refresh request for NLRI nlri-type (afi=afi, safi=safi) not negotiated
in this session
Description The peer has sent a BGP refresh message for an nlri that was not negotiated. Refresh
will not be scheduled for tables corresponding to this NLRI.
Severity warning
Facility LOG_DAEMON
Action None.
BGP_RESET_PENDING_CONNECTION
System Log Message peer-name: reseting pending active connection
Description The local BGP speaker received an open message in the connect state. The corresponding
peer will be restarted.
Severity warning
Facility LOG_DAEMON
Action None.
BGP_SET_INTERFACE_FAILED
System Log Message function-name: BGP peer peer-name interface not found. Leaving peer idled
Description The local BGP speaker needs a shared interface. The interface was not found and the
peer will be idled.

Severity warning
Facility LOG_DAEMON
Action None.
BGP_SOCK_ADDR_NOT_FOUND
System Log Message function-name: task_get_addr_local(peer-name): error-message
Description BGP was unable to ascertain the socket address that is bound to this socket file descriptor.
Severity error
Facility LOG_DAEMON
Action None.
BGP_SPOOL_FLUSH_CONNECTION_CLOSED
System Log Message function-name: sending num-bytes (sent num-bytes-sent) bytes to peer-name: connection
closed
Description Write call by BGP failed because the connection was closed.
Severity error
Facility LOG_DAEMON
Action None.
BGP_SPOOL_FLUSH_FAILED
System Log Message function-name: sending num-bytes (sent num-bytes-sent) bytes to peer-name failed:
error-message
Description Write call by BGP returned with a hard error for this socket. The corresponding bgp peer
will be closed.
Severity error
Facility LOG_DAEMON
Action None.

BGP_UNEXPECTED_MESSAGE_TYPE
System Log Message function-name: peer peer-name: message-type arrived, expected
expected-typeargumentexpected-type2
Description The message type received from the BGP peer is not the expected message type. The
BGP peer will be shutdown.
Severity warning
Facility LOG_DAEMON
Action None.
BGP_UNUSABLE_ASPATH
System Log Message function-name: peer peer-name AS peer-as received path with bad AS path
Description The local BGP speaker received an update with an AS path that is not usable. The
corresponding route will be rejected.
Severity error
Facility LOG_DAEMON
Action None.
BGP_UNUSABLE_NEXTHOP
System Log Message function-name: peer peer-name next hop next-hop-address reason, ignoring routes in this
update
Description The nexthop of the route is not usuable. BGP will ignore all the routes in this update.
Severity warning
Facility LOG_DAEMON
Action None.
BGP_UPDATE_CONTAINS_GARBAGE
System Log Message function-name: peer peer-name UPDATE zero attribute length followed by num-bytes
bytes of garbage
Description The update received from the peer has a zero path attribute length and contains garbage
beyond the attribute length field.

Severity warning
Facility LOG_DAEMON
Action None.
BGP_UPDATE_MISSING_PREFIXES
System Log Message function-name: peer peer-name UPDATE has path attributes but no reachable route
prefixes.
Description The local speaker has received an update message with path attributes but no reachable
route prefixes.
Severity warning
Facility LOG_DAEMON
Action None.
BGP_WRITE_CONNECTION_CLOSED
System Log Message bgp_send: sending num-bytes bytes to peer-name: connection closed
Description Write call by BGP failed because the connection was closed.
Severity error
Facility LOG_DAEMON
Action None.
BGP_WRITE_FAILED
System Log Message bgp_send: sending num-bytes bytes to peer-name failed: error-message
Description Write call by BGP returned with a hard error for this socket.
Severity error
Facility LOG_DAEMON
Action None.
BGP_WRITE_FAILED_AFTER_RETRYING
System Log Message bgp_send: sending to peer-name looping: error-message
Description BGP write failed because it encountered soft error on multiple tries.

Severity error
Facility LOG_DAEMON
Action None.
BGP_WRITE_WOULD_BLOCK
System Log Message bgp_send: sending num-bytes bytes to peer-name blocked (no spooling requested):
error-message
Description BGP write to a non-blocking file descriptor would block as there is no buffer space
available with the socket.
Severity error
Facility LOG_DAEMON
Action None.

CHAPTER 21
BOOTPD System Log Messages
This chapter describes messages with the BOOTPD prefix.
BOOTPD_ARG_ERR
System Log Message Ignoring unknown option -option
Description 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.
Severity warning
Facility ANY
Action Remove the invalid option from the 'tnp.bootpd' command line.
BOOTPD_BAD_ID
System Log Message Unexpected ID 0xassembly-id
Description 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.
Severity notice
Facility ANY
BOOTPD_BOOTSTRING
System Log Message Boot string: boot-string
from the boot parameter process (tnp.bootpd). tnp.bootpd responded with the indicated
boot string.

Severity info
Facility ANY
BOOTPD_CONFIG_ERR
System Log Message Problems with configuration file 'filename', using defaults
Description The boot parameter process (tnp.bootpd) could not read the indicated configuration
file, so it initialized using default settings defined at compile time.
Severity error
Facility ANY
Action Correct the configuration file.
BOOTPD_CONF_OPEN
System Log Message Unable to open configuration file 'filename'
Description The boot parameter process (tnp.bootpd) could not open the indicated configuration
Severity notice
Facility ANY
BOOTPD_DUP_PIC_SLOT
System Log Message Duplicate default value defined for PIC pic-slot in FPC fpc-slot
configuration file for tnp.bootpd. There was more than one definition in the file for the
indicated PIC slot in the indicated Flexible PIC Concentrator (FPC), so tnp.bootpd used
the first definition it found.
Severity notice
Facility ANY
Action Remove the extra definitions from the configuration file.
BOOTPD_DUP_REV
System Log Message Duplicate revision: major-version.minor-version

Chapter 21: BOOTPD System Log Messages
indicated revision of a component, so tnp.bootpd used the first definition it found.
Severity notice
Facility ANY
BOOTPD_DUP_SLOT
System Log Message Duplicate slot default: slot
indicated slot (combination of component assembly ID and revision), so tnp.bootpd
used the first definition it found.
Severity notice
Facility ANY
BOOTPD_HWDB_ERROR
System Log Message Operation in chassis hardware database failed: error-message
Description 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.
Severity error
Facility ANY
BOOTPD_MODEL_CHK
System Log Message Unexpected ID 0xidentifier for model model
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.

Severity warning
Facility ANY
BOOTPD_NEW_CONF
System Log Message New configuration installed
Description The boot parameter process (tnp.bootpd) loaded a new configuration file.
Severity info
Facility ANY
BOOTPD_NO_BOOTSTRING
System Log Message No boot string found for type board-type major-version.minor-version command-type
configuration file for tnp.bootpd. The file did not include a boot string for the hardware
component with the indicated characteristics.
Severity warning
Facility ANY
BOOTPD_NO_CONFIG
System Log Message No configuration file 'filename', using defaults
Description The boot parameter process (tnp.bootpd) could not open the indicated configuration
Severity notice
Facility ANY
BOOTPD_PARSE_ERR
System Log Message filename: return-value parse errors on SIGHUP
Description 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.

Chapter 21: BOOTPD System Log Messages
Severity error
Facility ANY
Action Correct the configuration file.
BOOTPD_REPARSE
System Log Message Reparsing configuration file 'filename'
Description The boot parameter process (tnp.bootpd) reparsed the indicated configuration file.
Severity info
Facility ANY
BOOTPD_SELECT_ERR
System Log Message select: error-message
Description The boot parameter process (tnp.bootpd) issued the select() system call, which returned
the indicated error message.
Severity warning
Facility ANY
BOOTPD_TIMEOUT
System Log Message Timeout duration unreasonable
Description 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.
Severity warning
Facility ANY
Action Provide an acceptable value for the -t argument; acceptable values are '1' (second) and
larger.


CHAPTER 22
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_AIS
System Log Message CFM defect: error-message
Description A connectivity-fault management (CFM) maintenance endpoint (MEP) received an alarm

indication signal (AIS) from the server level or a maintenance domain (MD) level lower
than that of the MEP.
Severity error
Facility LOG_DAEMON
Cause Adjacency loss or any other defect condition that brought down CFM.
Action Log the AIS message and suppress the alarms, for the received MD level, or propagate
the AIS message to higher levels.
CFMD_CCM_DEFECT_CROSS_CONNECT
Description 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.
Severity error
Facility ANY
Cause The configuration is invalid.

Action Check whether the configured MD name, format, and level, or the MA name or format,
is different from the remote endpoint.
CFMD_CCM_DEFECT_ERROR

continuity check message (CCM) with an incorrect transmission interval or MEP ID, which
indicates a configuration error.
Severity error
Facility ANY
Cause The configuration is invalid.
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

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.
Severity error
Facility ANY
CFMD_CCM_DEFECT_NONE
Description No defect was detected.
Severity error
Facility ANY
CFMD_CCM_DEFECT_RDI

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.

Chapter 22: CFMD System Log Messages
Severity error
Facility ANY
CFMD_CCM_DEFECT_RMEP
Description 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.
Severity error
Facility ANY
CFMD_CCM_DEFECT_UNKNOWN
Description An unknown defect was detected.
Severity error
Facility ANY
CFMD_PPM_READ_ERROR
System Log Message Read error on pipe from ppmd: reason (error-message)
Description The connectivity fault management process (cfmd) could not read a message available
on the read pipe from the periodic packet management process (ppmd).
Severity error
Facility ANY
CFMD_PPM_WRITE_ERROR
System Log Message function-name: write error on pipe to ppmd (error-message)
Description The connectivity fault management process (cfmd) could not write a message on the
pipe to the periodic packet management process (ppmd).
Severity error

Facility ANY

CHAPTER 23
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_ACQUIRE_MASTERSHIP
System Log Message Acquire mastership notification
Description The chassis process (chassisd) running on the master Routing Engine received a request
to acquire mastership.
Severity info
Facility LOG_DAEMON
Cause The Routing Engine was probably rebooting and graceful Routing Engine switchover is
configured.
CHASSISD_ANTICF_PIM_CHECK_FAILED
System Log Message PIM pim-slot failed anti-counterfeit check
Description The indicated Physical Interface Module (PIM) failed the anti-counterfeit check performed
by the chassis process (chassisd).
Severity error
Facility LOG_DAEMON
CHASSISD_ANTICF_RE_CHECK_FAILED
System Log Message Routing Engine failed anti-counterfeit check
Description The Routing Engine failed the anti-counterfeit check performed by the chassis process
(chassisd).
Severity error

Facility LOG_DAEMON
CHASSISD_ANTICF_RE_ROM_READ_FAIL
System Log Message Unable to read serial number from anti-counterfeit device for Routing Engine
Description The chassis process (chassisd) could not read the serial number recorded in the ROM
of the anti-counterfeit device for the Routing Engine.
Severity error
Facility LOG_DAEMON
CHASSISD_ANTICF_RE_SHA_READ_FAIL
System Log Message Unable to read SHA output from anti-counterfeit device for Routing Engine
Description The chassis process (chassisd) could not read Secure Hash Algorithm (SHA) information
from the anti-counterfeit device for the Routing Engine.
Severity error
Facility LOG_DAEMON
CHASSISD_ANTICF_ROM_READ_FAILED
System Log Message Unable to read serial number from anti-counterfeit device for PIM pim-slot
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_ANTICF_SHA_READ_FAILED
System Log Message Unable to read SHA output from anti-counterfeit device for PIM pim-slot
Description The chassis process (chassisd) could not read Secure Hash Algorithm (SHA) information
from the anti-counterfeit device for the indicated Physical Interface Module (PIM).

Chapter 23: CHASSISD System Log Messages
Severity error
Facility LOG_DAEMON
CHASSISD_ARGUMENT_ERROR
System Log Message Unknown option option
Description The indicated option, provided on the 'chassisd' command line, is invalid. The chassis
process (chassisd) initialized but ignored the invalid option.
Severity error
Facility LOG_DAEMON
CHASSISD_BLOWERS_SPEED
System Log Message Fans and impellers are now running at normal speed
Description The fans (and impellers, if applicable) were running at the normal speed.
Severity info
Facility LOG_DAEMON
CHASSISD_BLOWERS_SPEED_FULL
System Log Message Fans and impellers being set to full speed [reason]
Description For the indicated reason, the chassis process (chassisd) increased the speed of fans
(and impellers, if applicable) to the maximum.
Severity info
Facility LOG_DAEMON
CHASSISD_BLOWERS_SPEED_MEDIUM
System Log Message Fans and impellers being set to intermediate speed
Description 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.
Severity info

Facility LOG_DAEMON
CHASSISD_BUS_DEVICE_OPEN_FAILURE
System Log Message Unable to open 'bus-type' bus device, error error-message (error-code)
Description The chassis process (chassisd) could not open the indicated bus device for the indicated
reason.
Severity error
Facility LOG_DAEMON
CHASSISD_CB_CLOCK_CHECKSUM
System Log Message Clock module on M120 CB had configuration data checksum error
Description The chassis process (chassisd) detected a checksum error for the clock module on an
M120 Control Board (CB).
Severity error
Facility LOG_DAEMON
CHASSISD_CB_MASTER_BP_IGNORED
System Log Message Press of online/offline button ignored for master fru-name fru-slot
Description 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, T640,
MX240, MX480 and MX960 routers is the Control Board (CB).
Severity error
Facility LOG_DAEMON
Cause The control board was acting as master.
Action Switch mastership to the other control board before taking the control board offline.
CHASSISD_CB_READ
System Log Message Error reading midplane ID EEPROM, errno error-code
Description The chassis process (chassisd) could not read the EEPROM on the midplane.

Severity error
Facility LOG_DAEMON
CHASSISD_CB_RE_ONLINE_BP_IGNORED
System Log Message Unable to take fru-name fru-slot offline because paired Routing Engine is online
Description 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, T640,
MX240, MX480 and MX960 routers is the Control Board (CB).
Severity error
Facility LOG_DAEMON
Cause The Routing Engine paired with the indicated control board is still online.
Action Take the Routing Engine offline before taking the control board offline.
CHASSISD_CFEB_POWER_FAILURE
System Log Message function-name: unable to turn state power for CFEB cfeb-slot
Description The chassis process (chassisd) could not turn on or turn off the power to the indicated
Compact Forwarding Engine Board (CFEB).
Severity error
Facility LOG_DAEMON
CHASSISD_CLEAR_CONFIG_ERROR
System Log Message function-name: status
Description 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.
Severity error

Facility LOG_DAEMON
CHASSISD_CLOCK_FAILURE
System Log Message function-name: fru-name error-message
Description The chassis process (chassisd) determined that the indicated clock source failed in the
indicated way.
Severity error
Facility LOG_DAEMON
CHASSISD_CLOCK_NOTICE
System Log Message fru-name: message
Description The clock-synchronization status of the indicated component (field-replaceable unit, or

FRU) changed as indicated.
Severity notice
Facility LOG_DAEMON
CHASSISD_CLOCK_RESET_FAIL
System Log Message Zarlink module on Taz Base Board is not coming up after reset
Description The chassis process (chassisd) detected an error in the state of clock module.
Severity error
Facility LOG_DAEMON
CHASSISD_CMB_READBACK_ERROR
System Log Message Readback error from chassis management bus for fru-name fru-slot ([0xaddress, 0xoffset]
-> 0xerror-code)
Description The chassis process (chassisd) could not read back information from the Chassis
Management Bus (CMB) about the indicated component (field-replaceable unit, or FRU).

Severity error
Facility LOG_DAEMON
Cause The probable cause is hardware error.
CHASSISD_COMMAND_ACK_ERROR
System Log Message Error occurred when fru-name fru-slot reported its online status: error-message (error
code error-code)
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.
Severity error
Facility LOG_DAEMON
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)
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_CONCAT_MODE_ERROR
System Log Message Cannot set no-concatenated mode for FPC fpc-slot PIC pic-slot
Description 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.

Severity warning
Facility LOG_DAEMON
CHASSISD_CONFIG_ACCESS_ERROR
Description The chassis process (chassisd) experienced the indicated problem while attempting to
parse the configuration database.
Severity error
Facility LOG_DAEMON
CHASSISD_CONFIG_CHANGE_IFDEV_DEL
System Log Message Deleting argument1 interface-typesdev-numberargument2 due to configuration change
Description The chassis process (chassisd) deleted the indicated interface devices due to a change
in the configuration.
Severity warning
Facility LOG_DAEMON
CHASSISD_CONFIG_INIT_ERROR
System Log Message Unable to parse configuration; using defaults
Description The chassis process (chassisd) could not parse the configuration and used default values
while initializing.
Severity error
Facility LOG_DAEMON
CHASSISD_CONFIG_WARNING
System Log Message function-name: warning-message, FPC fpc-slot PIC pic-slot
Description The configuration that was specified for the indicated Physical Interface Card (PIC) is
invalid for that type of PIC.

Severity warning
Facility LOG_DAEMON
CHASSISD_DEVICE_OPEN_ERROR
System Log Message Unable to open device-name device file (errno error-code)
Description The chassis process (chassisd) could not open the device file for the indicated device.
Severity error
Facility LOG_DAEMON
CHASSISD_EXEC_ERROR
Description While trying to commit the rescue configuration, the chassis process (chassisd)
encountered an error.
Severity error
Facility LOG_DAEMON
CHASSISD_EXISTS
System Log Message chassisd already running; exiting
Description The chassis process (chassisd) exited because it discovered that another chassisd
process is already running.
Severity warning
Facility LOG_DAEMON
CHASSISD_EXISTS_TERM_OTHER
System Log Message Killing existing chassisd and exiting
Description The chassis process (chassisd) discovered that another chassisd process is already
running. It terminated the other process and exited.

Severity warning
Facility LOG_DAEMON
CHASSISD_FAN_FAILURE
System Log Message fru-name in slot fru-slot failed
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.
Severity error
Facility LOG_DAEMON
CHASSISD_FASIC_CONFIG_COMPLETE
System Log Message Fchip: configuration already completed
Description The chassis process (chassisd) detected an attempt to configure an F chip on a Control
Board (CB) when configuration was already complete.
Severity error
Facility LOG_DAEMON
CHASSISD_FASIC_FTOKEN_ERROR
System Log Message Fchip (CB control-board-slot, ID fchip-id): ftoken overflow/underflow set (data) at address
Description The chassis process (chassisd) detected an underflow or overflow error on the indicated
F chip on the indicated Control Board (CB).
Severity error
Facility LOG_DAEMON
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

Description 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).
Severity error
Facility LOG_DAEMON
CHASSISD_FASIC_HSL_CONFIG_ERROR
System Log Message Fchip (CB control-board-slot, ID fchip-id): HSL configuration failed (error error-message)
Description The chassis process (chassisd) could not configure high speed links (HSL) for the
indicated F chip on the indicated Control Board (CB).
Severity error
Facility LOG_DAEMON
CHASSISD_FASIC_HSL_LINK_ERROR
System Log Message Fchip (CB control-board-slot, ID fchip-id): link link-id failed because of error-message
Description 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).
Severity error
Facility LOG_DAEMON
CHASSISD_FASIC_INIT_ERROR
System Log Message Fchips were not configured yet
Description The chassis process (chassisd) detected that F chips were not yet initialized on the
Control Board (CB).
Severity error

Facility LOG_DAEMON
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
Description 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.
Severity error
Facility LOG_DAEMON
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
Description 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.
Severity error
Facility LOG_DAEMON
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
Description 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).

Severity error
Facility LOG_DAEMON
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
Description 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).
Severity error
Facility LOG_DAEMON
CHASSISD_FASIC_PLL_ERROR
System Log Message Fchip (CB control-board-slot, ID fchip-id): unable to lock PLL
Description The chassis process (chassisd) could not lock a phased-lock loop (PLL) for the indicated
F chip on the indicated Control Board (CB).
Severity error
Facility LOG_DAEMON
CHASSISD_FASIC_RESET_ERROR
System Log Message Fchip (CB control-board-slot, ID fchip-id): reset failed
Description The chassis process (chassisd) could not reset the indicated F chip on the indicated
Control Board (CB).
Severity error
Facility LOG_DAEMON

CHASSISD_FASIC_SRAM_ERROR
System Log Message Fchip (CB control-board-slot, ID fchip-id): SRAM fuse did not initialize
Description The chassis process (chassisd) detected that static RAM (SRAM) did not initialize properly
for the indicated F chip on the indicated Control Board (CB).
Severity error
Facility LOG_DAEMON

CHASSISD_FASIC_VERSION_ERROR
System Log Message Fchip (CB control-board-slot, ID fchip-id): part number part-number and version version
were invalid
Description The indicated part number and version detected for the indicated F chip on the indicated
Control Board (CB) were not valid values.
Severity error
Facility LOG_DAEMON
CHASSISD_FCHIP_CONFIG_COMPLETE
System Log Message Fchip: configuration already completed
Description The chassis process (chassisd) detected an attempt to configure an F chip when
configuration was already complete.
Severity error
Facility LOG_DAEMON
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
Description The chassis process (chassisd) detected an invalid number of Md chips for the indicated
F chip, Packet Forwarding Engine and Flexible PIC Concentrator (FPC).
Severity error
Facility LOG_DAEMON


CHASSISD_FCHIP_CONFIG_RATE_ERROR
System Log Message Fchip fchip-id: unable to set rate limit on port port
Description The chassis process (chassisd) could not set the rate limit for the indicated F chip and
port.
Severity error
Facility LOG_DAEMON
CHASSISD_FCHIP_CONFIG_READ_ERROR
System Log Message Fchip fchip-id: unable to read configuration register
Description The chassis process (chassisd) could not read a configuration register on the indicated
F chip.
Severity error
Facility LOG_DAEMON
CHASSISD_FCHIP_FTOKEN_ERROR
System Log Message Fchip fchip-id: Ftoken overflow/underflow set (data) at address
Description The chassis process (chassisd) detected an underflow or overflow error on the indicated
F chip.
Severity error
Facility LOG_DAEMON
CHASSISD_FCHIP_FTOKEN_INIT_ERROR
System Log Message Fchip fchip-id: fchip_ftoken_init() stuck in ftoken loop, addr=address, data=data
Description The chassis process (chassisd) encountered an error while initializing memory at the
indicated address for the indicated F chip.
Severity error
Facility LOG_DAEMON

CHASSISD_FCHIP_HSR_ERROR
System Log Message Fchip high-speed receiver (HSR) error: error-message
Description The chassis process (chassisd) detected an error in the high-speed receiver (HSR)
subsystem for the F chip with the indicated characteristics.
Severity error
Facility LOG_DAEMON

CHASSISD_FCHIP_HSR_INIT_ERROR
System Log Message HSR: No vectors supplied
Description The chassis process (chassisd) could not initialize the high-speed receiver (HSR)
subsystem for an F chip.
Severity error
Facility LOG_DAEMON
CHASSISD_FCHIP_HSR_INIT_LINK_ERR
System Log Message Fchip fchip-id: unable to initialize HSR link link-id
Description The chassis process (chassisd) could not initialize the indicated high-speed receiver
(HSR) link for the indicated F chip.
Severity error
Facility LOG_DAEMON
CHASSISD_FCHIP_HSR_RESET_ERROR
System Log Message Fchip fchip-id: hsr_reset error in fchip_init() on link link-id
Description A high-speed receiver (HSR) reset error occurred during initialization of the indicated F
chip and link.
Severity error
Facility LOG_DAEMON

CHASSISD_FCHIP_HST_ERROR
System Log Message Fchip high-speed transmitter (HST) error: error-message
Description The chassis process (chassisd) detected an error in the high-speed transmitter (HST)
subsystem for the F chip with the indicated characteristics.
Severity error
Facility LOG_DAEMON

CHASSISD_FCHIP_HST_INIT_ERROR
System Log Message HST: No vectors supplied
Description The chassis process (chassisd) could not initialize the high-speed transmitter (HST)
subsystem for an F chip.
Severity error
Facility LOG_DAEMON
CHASSISD_FCHIP_HST_INIT_LINK_ERR
System Log Message Fchip fchip-id: unable to initialize HST link link-id
Description The chassis process (chassisd) could not initialize the indicated high-speed transmitter
(HST) link for the indicated F chip.
Severity error
Facility LOG_DAEMON
CHASSISD_FCHIP_HST_RESET_ERROR
System Log Message Fchip fchip-id: hst_reset error in fchip_init() on link link-id
Description A high-speed transmitter (HST) reset error occurred during initialization of the indicated
F chip and link.
Severity error
Facility LOG_DAEMON

CHASSISD_FCHIP_INIT_ERROR
System Log Message Fchips were not configured yet
Description The chassis process (chassisd) detected that F chips were not yet initialized.
Severity error
Facility LOG_DAEMON
CHASSISD_FCHIP_LINK_ERROR
System Log Message SIBsib-slot_F0: link-type link link-id was bad
Description 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).
Severity error
Facility LOG_DAEMON
CHASSISD_FCHIP_MONITOR_ERROR
System Log Message F chip module was invalid
Description The chassis process (chassisd) detected an invalid F-chip module while enabling or
disabling the monitoring of F-chip functional blocks.
Severity error
Facility LOG_DAEMON
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
Description The indicated routine failed with a read error at the indicated address and register for
the indicated F chip and link.

Severity error
Facility LOG_DAEMON

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
Description The indicated routine failed with a write error at the indicated address and register for
the indicated F chip and link.
Severity error
Facility LOG_DAEMON

CHASSISD_FCHIP_POLL_ERROR
System Log Message Fchip fchip-id: link-type link-id poll returned error error-code
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_FCHIP_RATE_ERROR
System Log Message Fchip fchip-id: per-port rate limit was not enabled
Description 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.
Severity error
Facility LOG_DAEMON

CHASSISD_FCHIP_SIB_NOT_STARTED
System Log Message Unable to start fru-name fru-slot because F chips were not initialized
Description The indicated Switch Interface Board (SIB) did not start because the F chips on it were
not initialized.
Severity error
Facility LOG_DAEMON
CHASSISD_FCHIP_VERSION_ERROR
System Log Message F chip fchip-id: part number (part-number) and version (version) were invalid
Description The indicated part number and version detected for the indicated F chip were not valid
values.
Severity error
Facility LOG_DAEMON
CHASSISD_FEB_REVERSION
System Log Message Reversion from FEB fru-slot to FEB slot
Description The chassis daemon (chassisd) reverted to the indicated FEB from the specified FEB.
Severity error
Facility LOG_DAEMON
CHASSISD_FEB_SWITCHOVER
System Log Message Switchover from FEB fru-slot to FEB slot
Description The chassis daemon (chassisd) switched to the indicated FEB from the specified FEB.
Severity error
Facility LOG_DAEMON
CHASSISD_FHSR_READ_REG_ERROR
System Log Message Fchip: fhsr_read() failed at address address

Description The high-speed receiver (HSR) read routine failed at the indicated address on an F-chip
register.
Severity error
Facility LOG_DAEMON
CHASSISD_FHSR_WRITE_REG_ERROR
System Log Message Fchip: fhsr_write() of value value failed at address address
Description The high-speed receiver (HSR) write routine could not record the indicated value at the
indicated address on an F-chip register.
Severity error
Facility LOG_DAEMON

CHASSISD_FHST_READ_REG_ERROR
System Log Message Fchip: fhst_read() failed at address address
Description The high-speed transmitter (HST) read routine failed at the indicated address on an
F-chip register.
Severity error
Facility LOG_DAEMON
CHASSISD_FHST_WRITE_REG_ERROR
System Log Message Fchip: fhst_write() of value value failed at address address
Description The high-speed transmitter (HST) write routine could not record the indicated value at
the indicated address on an F-chip register.
Severity error

Facility LOG_DAEMON

CHASSISD_FILE_OPEN
System Log Message File open: filename, error: error-code -- error-message
Description The chassis process (chassisd) could not open the indicated file for the indicated reason.
Severity critical
Facility LOG_DAEMON

CHASSISD_FILE_STAT
System Log Message File stat: filename, error: error-code -- error-message
Description The chassis process (chassisd) could not open the indicated file because it could not
obtain its status.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ACTION_FPC_OFFLINE
System Log Message FPC fpc-slot offline initiated to attempt healing of the fabric down condition.
Description The chassis process took the indicated FPC offline in an attempt to heal a fabric down
condition, which caused the router to be incapable of carrying traffic.
Severity notice
Facility LOG_DAEMON
CHASSISD_FM_ACTION_FPC_ONLINE
System Log Message FPC fpc-slot online initiated to attempt healing of the fabric down condition.
Description The chassis process put the indicated FPC online in an attempt to heal a fabric down

Severity notice
Facility LOG_DAEMON
CHASSISD_FM_ACTION_FPC_POWER_OFF
System Log Message FPC fpc-slot power off initiated to take down interfaces since the FPC is incapable of
forwarding traffic due to the fabric down condition.
Description The chassis process powered off the indicated FPC to take down the FPC's interfaces
and signal neighboring routers that the router is incapable of carrying traffic on the
indicated FPC.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ACTION_FPC_RECOVERY
System Log Message FPC fpc-slot action initiated to attempt healing of the error-message condition.
Description The chassis process took the indicated FPC action in an attempt to heal a fabric
degradation/down condition which caused the router to be running in degraded
performance or incapable of carrying traffic.
Severity notice
Facility LOG_DAEMON
CHASSISD_FM_ACTION_FPC_RESTART
System Log Message FPC fpc-slot restart initiated to attempt healing of the fabric down condition.
Description The chassis process restarted the indicated FPC in an attempt to heal a fabric down
Severity notice
Facility LOG_DAEMON

CHASSISD_FM_ACTION_PLANE_OFFLINE
System Log Message Fabric plane sib-plane offline initiated to attempt healing of the fabric down condition.
Description The chassis process took the indicated fabric plane offline in an attempt to heal a fabric
down condition, which caused the router to be incapable of carrying traffic.
Severity notice
Facility LOG_DAEMON
CHASSISD_FM_ACTION_PLANE_ONLINE
System Log Message Fabric plane sib-plane online initiated to attempt healing of the fabric down condition.
Description The chassis process put the indicated fabric plane online in an attempt to heal a fabric
down condition, which caused the router to be incapable of carrying traffic.
Severity notice
Facility LOG_DAEMON
CHASSISD_FM_BAD_STATE
System Log Message function-name: unexpected state statetype for SIB#sib-slot
Description The indicated function failed because it encountered the indicated type of unexpected
internal state with respect to the indicated Switch Interface Board (SIB).
Severity error
Facility LOG_DAEMON
CHASSISD_FM_DETECT_FPC_FABRIC_DEGRADED
System Log Message Detected FPC fabric degradation exceeds threshold. If no fabric planes come online in
elapsed-time seconds actions will be taken to address the fabric error-message condition.
Description The chassis process detected that the fabric planes are functioning at a degraded capacity
and the router is running with degraded performance or not capable of carrying traffic
coming in through the interfaces.

Severity error
Facility LOG_DAEMON
CHASSISD_FM_DETECT_PLANES_DOWN
System Log Message All fabric planes in the system have gone down after interfaces have been created. If no
fabric planes come online in elapsed-time seconds, actions will be taken to address the
fabric down condition.
Description The chassis process detected all the fabric planes went down after interfaces were
created and the router is not capable of carrying traffic coming in through the interfaces.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_DETECT_UNREACHABLE
System Log Message Some fabric destinations PFEs in the system have become unreachable after interfaces
have been created. If the unreachable PFE destinations are not fixed in elapsed-time
seconds, actions will be taken to address the fabric down condition.
Description The chassis process detected that some Packet Forwarding Engine (PFE) destinations
had become unreachable after interfaces were created, and the router is not capable of
carrying traffic to the unreachable PFE destinations on the interfaces.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR
System Log Message function-name: error-message (SIB#sib-slot, Packet Forwarding Engine pfe on FPC
fpc-slot)
Description 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).
Severity error
Facility LOG_DAEMON

CHASSISD_FM_ERROR_CLOS_F13_HSR
System Log Message FM: error-message errors occurred on link from F2S-f2-sib_SFfrom-fchip_s-port to
F13SIBto-sfc-sib_SF3_to-fchip_d-port on plane sib-plane
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 SFC routing node detected an error in the electrical
path between the indicated port on the indicated F2SIB and F13SIB on the indicated
plane.
Severity error
Facility LOG_DAEMON
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 F2S-f2-sib_SFto-fchip_d-port on plane sib-plane
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.
Severity error
Facility LOG_DAEMON
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 F2S-f2-sib_SFto-fchip_d-port on plane sib-plane

plane.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_CLOS_F2_HST
System Log Message FM: error-message errors occurred on link from F2S-f2-sib_SFfrom-fchip_s-port to
F13SIBto-sfc-sib_SF1_to-fchip_d-port on plane sib-plane
indicated plane.
Severity error
Facility LOG_DAEMON
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
The chassis process (chassisd) on the routing node that houses the indicated 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.
Severity error
Facility LOG_DAEMON

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
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.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_F13_FB_TXP
System Log Message F13SIBsib-slot_FB_fiber-bundle LCC lcc ST_SIB_Lto-lcc-sib is error-message
Description 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.
Severity error
Facility LOG_DAEMON
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
detected the indicated error as packets that were traveling in the indicated direction were
translated between electrical and optical media.
Severity error
Facility LOG_DAEMON

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
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.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_LCC_SIB_CBL
System Log Message Cable running from SFCerror-message lcc, lcc-sib-name, to LCCcable-name sc is
sc-sib-name on plane sib-plane.
Description In a Multi-chassis routing matrix, the fiber-optic cable between each SIB in a LCC routing
node (called a LCC SIB) must connect to a specific SIB port on the Switch chassis
platform. The cable connected at the indicated line card chassis SIB had the indicated
error.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_LCC_SIB_HSR_PFE
System Log Message error-message errors on link from FPClcc PFElc-name to pfe
lcc-sib-name_asic-name,asic-port on LCCasic-chan and plane sib-plane
Description In a Multi-chassis routing matrix, packets traverse both electrical and optical media as
they travel between the Switch Interface Boards (SIBs) in the LCC routing nodes (called
LCC SIBs) and the SIBs in the Switch Chassis platform (called F13SIBs and/or F2S-SIBs).
The chassis process (chassisd) on the routing node that houses the indicated LCC SIB
detected an error in the electrical path between the indicated LCC SIB and the indicated
PFE on the FPC.

Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_LCC_SIB_HSR_XC
System Log Message error-message errors on link from SFCsc sc-sib-name to LCClcc lcc-sib-name
asic-name_asic-port,asic-chan on plane sib-plane
detected an error in the electrical path between the indicated ports on the LCC SIB and
the corresponding SIB on Switch chassis.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_LCC_SIB_OPTICS_FAULT
System Log Message Optics module on LCCerror-message lcc, lcc-sib-name, connected to SFCcable-name sc
is sc-sib-name on plane sib-plane.
Description In a Multi-chassis routing matrix, fiber-optic modules are used to inter-connect each SIB
in a LCC routing node (called a LCC SIB) to a specific SIB port on the Switch chassis
platform. The optics module connected at the indicated line card chassis SIB had the
indicated error.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_LCC_SIB_RX_OPTICS
System Log Message FM: error-message on optics channel in
LCClcc_lcc-sib-name_opt-dev-nameoptics,optics-channel
detected the indicated error in the optical media.

Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_LCC_SIB_TX_OPTICS
System Log Message error-message on optics channel in
LCClcc_lcc-sib-name_opt-dev-nameoptics,optics-channel
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_SC_CLOS_F13_HSR
System Log Message FM: error-message errors occurred on link from SFC sc,
sc-f2ssib-name_asic-name_asic-port,asic-chan to
sc-f13sib-name_dst-asic-name_dst-asic-port,dst-asic-chan on plane sib-plane
plane.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_SC_CLOS_F13_HST
sc-f13sib-name_asic-name_asic-port,asic-chan to
sc-f2ssib-name_dst-asic-name_dst-asic-port,dst-asic-chan on plane sib-plane

indicated plane.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_SC_CLOS_F2_HSR
sc-f13sib-name_asic-name_asic-port,asic-chan to
sc-f2ssib-name_dst-asic-name_dst-asic-port,dst-asic-chan on plane sib-plane
plane.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_SC_CLOS_F2_HST
sc-f2ssib-name_asic-name_asic-port,asic-chan to
sc-f13sib-name_dst-asic-name_dst-asic-port,dst-asic-chan on plane sib-plane
indicated plane.
Severity error
Facility LOG_DAEMON

CHASSISD_FM_ERROR_SC_SIB_CBL
System Log Message Cable running from LCCerror-message sc, sc-sib-name, to SFCcable-name lcc is
lcc-sib-name on plane sib-plane.
Description In a Multi-chassis routing matrix, the fiber-optic cable between each SIB in a LCC routing
node (called a LCC SIB) must connect to a specific SIB port on the Switch chassis
platform. The cable connected at the indicated switch chassis SIB had the indicated
error.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_SC_SIB_HSR_XC
System Log Message error-message errors on link from LCClcc lcc-sib-name to SFCsc sc-sib-name
asic-name_asic-port,asic-chan on plane sib-plane
The chassis process (chassisd) on the routing node that houses the indicated Switch
chassis SIB detected an error in the electrical path between indicated ports on the Switch
chassis SIB and the indicated LCC SIB on the indicated LCC.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_SC_SIB_OPTICS_FAULT
System Log Message Optics module on SFCerror-message sc, sc-sib-name, connected to LCCcable-name lcc
is lcc-sib-name on plane sib-plane.
Description In a Multi-chassis routing matrix, fiber-optic modules are used to inter-connect each SIB
in a LCC routing node (called a LCC SIB) to a specific SIB port on the Switch chassis
platform. The optics module connected at the indicated switch chassis SIB had the
indicated error.
Severity error

Facility LOG_DAEMON
CHASSISD_FM_ERROR_SC_SIB_RX_OPTICS
System Log Message FM: error-message on optics channel in
SFCsc_sc-sib-name_opt-dev-nameoptics,optics-channel
chassis SIB detected the indicated error as packets were traveling in the optical media
from the indicated LCC SIB on the indicated LCC.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_SC_SIB_TX_OPTICS
System Log Message error-message on optics channel in
SFCsc_sc-sib-name_opt-dev-nameoptics,optics-channel
chassis SIB detected the indicated error as packets that were traveling in the indicated
direction were translated between electrical and optical media.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_SIB_L_FB_HSR
System Log Message FM: HSR error error-code occurred on link from SIB-S port F(s-row,s-port) to SIB-L#sib-slot
port F(l-row,l-port)
Description 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.

Severity error
Facility LOG_DAEMON
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
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.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_SIB_L_FB_SMF
System Log Message FM: error-message error occurred on link to-from-sib SIB-L#sib-slot to-from-scc SCC
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.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_SIB_L_FB_TXP
System Log Message LCC lcc ST-SIB-L:sib-slot Fiber-bundle:fiber-bundle is error-message
Description 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.
Severity error
Facility LOG_DAEMON
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
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_SIB_L_HSR_PFE
System Log Message FM: error-message on LCC:lcc FPCfpc-slot_pfe link to ST-SIB-Lto-lcc-sib_fchip-id
detected an error in the electrical path between the indicated ST-SIB-L and the indicated
PFE on the FPC.
Severity error
Facility LOG_DAEMON
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

detected an error in the electrical path between the indicated ports on the SIB-L and the
corresponding F13SIB.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_SIB_L_MISMATCH
System Log Message FM: fiber cable from SIB-L#sib-slot possibly connected to wrong SIB-S
Description 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.
Severity error
Facility LOG_DAEMON
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
detected higher than configured receive power levels on the indicated fiber-bundles
connected to the indicated LCC ST-SIB-L.
Severity error
Facility LOG_DAEMON

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)
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 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).
Severity error
Facility LOG_DAEMON
CHASSISD_FM_ERROR_SIB_S_FB_SMF
System Log Message FM: error-message error occurred on link to-from-sib-s SIB-S#sib-slot to-from-lcc LCClcc
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.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_FABRIC_DEGRADED
System Log Message DPCs are seeing grant timeouts; System is blackholing Need to attempt fabric healing.
Action will be taken after elapsed-time seconds, to address the fabric down condition.
Description The chassis process detected that the fabric planes are functioning at a degraded capacity
and the router is not capable of carrying traffic coming in through the interfaces.
Severity error
Facility LOG_DAEMON

CHASSISD_FM_FPC_FABRIC_DEGRADED
System Log Message FPC fpc-slot running with error-message,no attempt of healing due to configuration.
Description The chassis process (chassisd) did not attempt healing due to user configuration or
insufficient online planes.
Severity error
Facility LOG_DAEMON
Action Change the configuration (chassis) that prevent the healing.
CHASSISD_FM_MEMORY_ERROR
System Log Message function-name: unable to allocate memory; error-message
Description The chassis process (chassisd) could not allocate memory for a fabric operation.
Severity warning
Facility LOG_DAEMON
CHASSISD_FM_SIB_ERROR
System Log Message Fabric management error for SIB sib-slot: error-message
Description The chassis process (chassisd) detected the indicated type of error on the indicated
Switch Interface Board (SIB) and performed the indicated action.
Severity error
Facility LOG_DAEMON
CHASSISD_FM_SIB_FPC_TYPE_ERROR
System Log Message SIB sib-slot does not support features required for FPC Type 4
Description The indicated Switch Interface Board (SIB) does not support features required by the
Flexible PIC Concentrator (FPC) Type 4.

Severity error
Facility LOG_DAEMON
CHASSISD_FPC_JAM_HSL2_PARAMS_TIMEOUT
System Log Message function-name: attempt to jam params for fru-name fru-slot timed out
Description The indicated component (field-replaceable unit, or FRU) did not transfer the parameters
within the time that is normally sufficient. If attempt failed, the chassisd process raised
an alarm and left the FRU offline.
Severity error
Facility LOG_DAEMON
CHASSISD_FPC_NOT_FOUND
System Log Message function-name: unable to find FPC for PIC attachment operation
Description 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.
Severity warning
Facility LOG_DAEMON
CHASSISD_FPC_OPTICS_HOT_NOTICE
System Log Message fru-name temperature over temperature degrees C; non-high-temperature tolerant optics
will be disabled in duration seconds if condition persists
Description The temperature of FPC exceeded the trigger point to disable non-high-temperature
tolerant optics. If the temperature did not decrease below the threshold within 10 minutes
after message was logged, the chassisd process disable those affected optics.
Severity error
Facility LOG_DAEMON
Action Increase cooling on FRU or replace optics with high-temperature tolerant optics
CHASSISD_FPC_PIC_DETECT_TIMEOUT
System Log Message function-name: PIC detection on FPC fpc-slot timed out

Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_FPC_TYPE_SIB_TYPE_ERROR
System Log Message Installed SIB type (SIB-I8-F16) does not support features required by FPC fpc-slot
Description The indicated Flexible PIC Concentrator (FPC) is Type 4, which is not supported by Switch
Interface Board (SIB) type SIB-I8-F16.
Severity error
Facility LOG_DAEMON
CHASSISD_FRU_ALREADY_OFFLINE
System Log Message fru-name fru-slot already offline
Description The chassis process (chassisd) received a request to take the indicated component
(field-replaceable unit, or FRU) offline, but the FRU was already offline.
Severity error
Facility LOG_DAEMON
CHASSISD_FRU_ALREADY_ONLINE
System Log Message Received request to bring fru-name fru-slot online; it was already online
Description The chassis process (chassisd) received a request to bring the indicated component
(field-replaceable unit, or FRU) online, but the FRU was already online.
Severity warning
Facility LOG_DAEMON

CHASSISD_FRU_EVENT
System Log Message function-name: state fru-name fru-slot
Description The state of the indicated component (field-replaceable unit, or FRU) changed as
indicated.
Severity notice
Facility LOG_DAEMON
CHASSISD_FRU_FIRE_TEMP_CONDITION
System Log Message fru-name fru-slot sensor temperature temperature over threshold degrees C (message);
routing platform will shut down in duration seconds if condition persists
Description The temperature of the specified component (field-replaceable unit, or FRU) exceeded
the indicated temperature, which is the upper of two thresholds. The fans (and impellers,
if applicable) that were cooling this FRU were in the indicated state. If the temperature
does not go below the threshold within four seconds 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.
Severity error
Facility LOG_DAEMON
Action Increase cooling in the area around the chassis.
CHASSISD_FRU_HIGH_TEMP_CONDITION
System Log Message fru-name fru-slot sensor temperature temperature over threshold degrees C (message)
the indicated temperature, which is the lower of two thresholds. The fans (and impellers,
if applicable) that were cooling this FRU were in the indicated state. The chassis process
(chassisd) increased the speed of all functioning fans (and impellers) that were cooling
this component to full speed.
Severity error
Facility LOG_DAEMON
CHASSISD_FRU_INVALID_SLOT
System Log Message FRU fru-name is not supported in current slot

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.
Severity critical
Facility LOG_DAEMON
CHASSISD_FRU_IO_ERROR
System Log Message function-name: fru-name operation error: reason (error-message)
Description The chassis process (chassisd) could not perform the indicated I/O operation on the
indicated component (field-replaceable unit, or FRU).
Severity error
Facility LOG_DAEMON
CHASSISD_FRU_IO_OFFSET_ERROR
System Log Message function-name: fru-name operation error: reason 0xoffset (error-message)
Description The chassis process (chassisd) could not perform the indicated I/O operation at the
indicated byte offset.
Severity error
Facility LOG_DAEMON
CHASSISD_FRU_IPC_WRITE_ERROR
System Log Message function-name: FRU fru-name, errno error-code, error-message
Description 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.
Severity warning

Facility LOG_DAEMON
CHASSISD_FRU_OFFLINE_FAILED
System Log Message Unable to take fru-name fru-slot offline because FRU sequencer is active: reason
Description The chassis process (chassisd) could not take the indicated component (field-replaceable
unit, or FRU) offline for the indicated reason.
Severity notice
Facility LOG_DAEMON
CHASSISD_FRU_OFFLINE_NOTICE
System Log Message Taking fru-name fru-slot offline: reason
Description The chassis process (chassisd) took the indicated component (field-replaceable unit,
or FRU) offline for the indicated reason.
Severity notice
Facility LOG_DAEMON
CHASSISD_FRU_OFFLINE_TIMEOUT
System Log Message Offline request timed out; fru-name fru-slot restarted
Description 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.
Severity warning
Facility LOG_DAEMON
CHASSISD_FRU_ONLINE_TIMEOUT
System Log Message function-name: attempt to bring fru-name fru-slot online timed out
Description 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.
Severity error
Facility LOG_DAEMON

CHASSISD_FRU_OVER_TEMP_CONDITION
System Log Message fru-name fru-slot sensor temperature temperature over threshold degrees C (message);
FRU will shut down in duration seconds if condition persists
if applicable) that were cooling this FRU 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 FRU or all FRUs in the same
cooling zone. When this message was logged, the indicated number of seconds remained
before shutdown.
Severity error
Facility LOG_DAEMON
CHASSISD_FRU_STEP_ERROR
System Log Message fru-name fru-slot at step step-number
Description The power-on sequence for the indicated component (field-replaceable unit, or FRU)
failed at the indicated point.
Severity error
Facility LOG_DAEMON
CHASSISD_FRU_UNRESPONSIVE
System Log Message Error for fru-name fru-slot: error-message; action
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_FRU_UNRESPONSIVE_RETRY
System Log Message Attempt count to power on fru-name fru-slot timed out; restarted it
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_FRU_UNSUPPORTED
System Log Message chassisd invalidated support for fru-name fru-slot
Description The chassis process (chassisd) invalidated support for the indicated component
(field-replaceable unit, or FRU) during initialization.
Severity warning
Facility LOG_DAEMON
CHASSISD_FRU_VERSION_MISMATCH
System Log Message component version mismatch for fru-name -- expected expected-value, got received-value
Description 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.
Severity error
Facility LOG_DAEMON
Action Upgrade the FRU.
CHASSISD_GASIC_ID_ERROR
System Log Message Fchip: invalid SIB slot
Description 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.
Severity error
Facility LOG_DAEMON

CHASSISD_GBUS_NOT_READY
System Log Message function-name: fru-name not ready for power up (RTIME_PWR_COND = 0xvalue)
Description The GBUS was not ready when the chassis process (chassisd) first tried to power it on,
and the power-up operation timed out.
Severity error
Facility LOG_DAEMON
CHASSISD_GBUS_READBACK_ERROR
System Log Message Readback error from GBUS for fru-name fru-slot ([0xgbus-address, 0xgbus-registers] ->
0xreturn-value)
Description 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).
Severity error
Facility LOG_DAEMON
CHASSISD_GBUS_RESET_EVENT
System Log Message fru-name#fru-slot - command
Description The chassis process (chassisd) reset the GBUS for the indicated component
(field-replaceable unit, or FRU). This is a normal part of startup.
Severity warning
Facility LOG_DAEMON
CHASSISD_GBUS_SANITY_ERROR
System Log Message function-name: fru-name fru-slot -- management bus failed sanity test

Description The chassis process (chassisd) checks its management GBUS with a set of test operations
when it is started. The tests failed.
Severity error
Facility LOG_DAEMON
CHASSISD_GENERIC_ERROR
Description The chassis process (chassisd) detected the indicated error.
Severity error
Facility LOG_DAEMON
Action Perform any corrective actions mentioned in the error message.
CHASSISD_GENERIC_WARNING
Description The chassis process (chassisd) generated the indicated warning message.
Severity notice
Facility LOG_DAEMON
CHASSISD_GETTIMEOFDAY
System Log Message Unexpected error from gettimeofday: error-code -- error-message
Description The chassis process (chassisd) could not obtain the time of day because of the indicated
error.
Severity warning
Facility LOG_DAEMON
CHASSISD_GRES_UNSUPP_PIC
System Log Message Unable to enable graceful Routing Engine switchover; PIC does not support it
Description The chassis process (chassisd) could not enable graceful Routing Engine switchover
because an installed PIC does not support it.

Severity error
Facility LOG_DAEMON
CHASSISD_HIGH_TEMP_CONDITION
System Log Message Chassis temperature over temperature degrees C (message)
Description 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.
Severity warning
Facility LOG_DAEMON
CHASSISD_HOST_TEMP_READ
System Log Message Error reading host temperature sensor
Description The chassis process (chassisd) could not read the temperature sensors on the routing
platform.
Severity notice
Facility LOG_DAEMON
CHASSISD_HSR_CONFIG_READ_ERROR
System Log Message function-name: unable to read configuration for HSR identifier
Description The indicated function could not read the configuration for the indicated high-speed
receiver (HSR).
Severity error
Facility LOG_DAEMON
CHASSISD_HSR_CONFIG_WRITE_ERROR
System Log Message function-name: unable to write configuration for HSR identifier
Description The indicated routine could not write to the configuration for the indicated high-speed
receiver (HSR).

Severity error
Facility LOG_DAEMON
CHASSISD_HSR_ELEMENTS_ERROR
System Log Message Provided number of HSR elements (count) was invalid
Description The indicated routine for processing a certain number of high-speed receiver (HSR)
elements failed, because the supplied number of elements was invalid.
Severity error
Facility LOG_DAEMON
CHASSISD_HSR_FIFO_ERROR
System Log Message function-name: FIFO read failed for HSR identifier
Description A first in, first out (FIFO) read error occurred during execution of the indicated routine on
the indicated high-speed receiver (HSR).
Severity error
Facility LOG_DAEMON

CHASSISD_I2CS_READBACK_ERROR
System Log Message Readback error from I2C slave for fru-name fru-slot ([0xi2cs-address, 0xoffset] ->
0xerror-code)
Description The chassis process (chassisd) could not read back information from the I2C slave (I2CS)
about the indicated component (field-replaceable unit, or FRU).
Severity error
Facility LOG_DAEMON
CHASSISD_I2C_BAD_IDEEPROM_FORMAT
System Log Message Invalid IDEEPROM format for fru-name

Description 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.
Severity critical
Facility LOG_DAEMON
CHASSISD_I2C_FIC_PRESENCE_READ
System Log Message function-name: fru-name unable to get presence masks (error-message)
Description The chassis process (chassisd) could not read I2C data with presence information about
the indicated component (field-replaceable unit, or FRU).
Severity error
Facility LOG_DAEMON
CHASSISD_I2C_GENERIC_ERROR
Description The indicated error occurred during an I2C access library operation.
Severity error
Facility LOG_DAEMON
CHASSISD_I2C_INVALID_ASSEMBLY_ID
System Log Message '0xassembly-id' is invalid value for fru-name assembly ID
Description The assembly ID for the indicated component (field-replaceable unit, or FRU) was not
valid for its type.
Severity error
Facility LOG_DAEMON

CHASSISD_I2C_IOCTL_FAILURE
System Log Message function-name: operation ioctl failure for group group-id at address 0xaddress (errno
error-code)
Description The chassis process (chassisd) could not perform the indicated ioctl() operation on the
I2C data for the indicated component (field-replaceable unit, or FRU).
Severity error
Facility LOG_DAEMON
CHASSISD_I2C_IO_FAILURE
System Log Message function-name: fru-name operation failed for group group-id at address 0xaddress
Description 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).
Severity error
Facility LOG_DAEMON
CHASSISD_I2C_MIDPLANE_CORRUPT
System Log Message Corruption on midplane ID EEPROM (ID: 0xassembly-id, MAC address: 0xmac-address,
0xversion)
Description The chassis process (chassisd) found corrupted information when it tried to verify the
parameters of the midplane's I2C ID EEPROM.
Severity error
Facility LOG_DAEMON
CHASSISD_I2C_RANGE_ERROR
System Log Message function-name: requested offset was out of range (offset offset + nbytes count > 256)
Description The indicated offset, which is greater than 256, was specified in a read request for an I2C
device.

Severity error
Facility LOG_DAEMON
Cause No I2C device uses or has storage above an offset of 256.
CHASSISD_I2C_READ_ERROR
System Log Message function-name: read error for group group-id at address 0xaddress, offset offset
Description The chassis process (chassisd) could not read I2C data from the indicated device.
Severity error
Facility LOG_DAEMON
CHASSISD_I2C_WRITE_ERROR
System Log Message function-name: write error for group group-id at address 0xaddress, offset offset
Description The chassis process (chassisd) could not write I2C data to the indicated device.
Severity error
Facility LOG_DAEMON
CHASSISD_IDEEPROM_READ_ERROR
System Log Message Unable to read fru-name ID EEPROM
Description The chassis process (chassisd) could not read the I2C ID EEPROM of the indicated
component (field-replaceable unit, or FRU).
Severity error
Facility LOG_DAEMON
CHASSISD_IFDEV_CREATE_FAILURE
System Log Message function-name: unable to create interface device for interface-name (error-message)

Description 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.
Severity error
Facility LOG_DAEMON
Cause Necessary resources might have been unavailable.
CHASSISD_IFDEV_CREATE_NOTICE
System Log Message function-name: created device-name for interface-name
Description The chassis process (chassisd) created the initial interface device for the indicated newly
installed Physical Interface Card (PIC) or pseudodevice.
Severity notice
Facility LOG_DAEMON
CHASSISD_IFDEV_DETACH_ALL_PSEUDO
System Log Message ifdev_detach(pseudo devices: all)
Description The chassis process (chassisd) detached the interface devices for all pseudodevices.
Severity notice
Facility LOG_DAEMON
CHASSISD_IFDEV_DETACH_FPC
System Log Message ifdev_detach_fpc(fpc-slot)
Description The chassis process (chassisd) detached the interface devices for all Physical Interface
Cards (PICs) installed in the indicated Flexible PIC Concentrator (FPC).
Severity notice
Facility LOG_DAEMON


CHASSISD_IFDEV_DETACH_PIC
System Log Message ifdev_detach_pic(fpc-slot/pic-slot)
Description The chassis process (chassisd) detached the interface devices for the indicated Physical
Interface Card (PIC).
Severity notice
Facility LOG_DAEMON

CHASSISD_IFDEV_DETACH_PSEUDO
System Log Message ifdev_detach(pseudo devices: porttype port-type, sdev=sdev-number, edev=edev-number)
Description The chassis process (chassisd) detached the interface devices for the indicated
pseudodevices.
Severity notice
Facility LOG_DAEMON
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
Description The chassis process (chassisd) asked the kernel to remove the indicated interface from
the kernel interface table. The request failed.
Severity error
Facility LOG_DAEMON
CHASSISD_IFDEV_GETBYNAME_NOTICE
System Log Message function-name: ifdm get_by_name failed for interface-type interface device interface-name
(error-message)
Description The chassis process (chassisd) failed to find the indicated interface device, even though
it just created it.
Severity warning
Facility LOG_DAEMON

Cause There was a problem with interface state creation.
CHASSISD_IFDEV_GET_BY_INDEX_FAIL
System Log Message function-name: rtslib_ifdm_get_by_index failed: error-code - error-message
Description The chassis process (chassisd) could not obtain information about an interface device.
Severity error
Facility LOG_DAEMON
CHASSISD_IFDEV_GET_BY_NAME_FAIL
System Log Message Unable to retrieve information for interface device interface-name: error-message
Description The chassis process (chassisd) could not obtain information about the indicated interface
device.
Severity error
Facility LOG_DAEMON
CHASSISD_IFDEV_NO_MEMORY
System Log Message function-name: unable to allocate memory for interface-type interface
Description The chassis process (chassisd) could not allocate memory when creating an interface
device for the indicated interface type.
Severity error
Facility LOG_DAEMON
Cause Resources on the system are extremely limited.
Action Eliminate the resource limitations and restart the PIC that houses the interface for which
the interface device could not be created.
CHASSISD_IFDEV_RETRY_NOTICE
System Log Message function-name: attempt count to add interface device interface-name failed
(error-message)
Description 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.

Severity warning
Facility LOG_DAEMON
Cause Necessary resources might have been unavailable. They should become available soon.
CHASSISD_IFDEV_RTSLIB_FAILURE
System Log Message function-name: library-function-name failed (error-message)
Description The chassis process (chassisd) could not create an interface device because an error
occurred during the indicated call to the routing socket library.
Severity error
Facility LOG_DAEMON
CHASSISD_IFILTER_INSTALL_ERROR
System Log Message function-name: RTSOCK Implicit Filter install failed. error=error-code
Description The chassis process (chassisd) could not install a global implciit rtsock filter most likely
due to a file operation error.
Severity error
Facility LOG_DAEMON
CHASSISD_IOCTL_FAILURE
System Log Message function-name: reason for fru-name (error-message)
indicated component (field-replaceable unit, or FRU).
Severity error
Facility LOG_DAEMON
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)

Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_IPC_CONNECTION_DROPPED
System Log Message Dropped IPC connection for fru-name fru-slot
Description The chassis process (chassisd) dropped its interprocess communication (IPC) connection
to the indicated component (field-replaceable unit, or FRU).
Severity warning
Facility LOG_DAEMON

CHASSISD_IPC_DAEMON_WRITE_ERROR
System Log Message pipe_write failure for connection-id; connection error: error-message (errno error-code)
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_IPC_ERROR
Description An error occurred when the chassis process (chassisd) received an interprocess
communication (IPC) message.
Severity error

Facility LOG_DAEMON
CHASSISD_IPC_FLUSH_ERROR
System Log Message function-name: flush operation failed for fru-name fru-slot
Description 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).
Severity warning
Facility LOG_DAEMON
CHASSISD_IPC_MSG_DROPPED
System Log Message Dropping message from connection queue: type = message-type, subtype =
message-subtype
Description The chassis process (chassisd) dropped an interprocess communication (IPC) message
because the message queue had already reached maximum capacity.
Severity error
Facility LOG_DAEMON
Cause 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.
http://kb.juniper.net/InfoCenter/index?page=content&idhttp://kb.juniper.net/InfoCenter/index?page=content&id==KB18825.
CHASSISD_IPC_MSG_ERROR
Description The chassis process (chassisd) detected an error in an interprocess communication (IPC)
message with the indicated characteristics.
Severity error
Facility LOG_DAEMON

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
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_IPC_MSG_QFULL_ERROR
System Log Message Dropping message from connection queue: type = message-type, subtype =
message-subtype
Description The chassis process (chassisd) had to discard a message because the queue of messages
waiting for a connection was already full.
Severity error
Facility LOG_DAEMON
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
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_IPC_UNEXPECTED_MSG
message-subtype)

Description The chassis process (chassisd) received a unexpected message with the indicated
characteristics.
Severity error
Facility LOG_DAEMON
CHASSISD_IPC_UNEXPECTED_RECV
System Log Message Received unexpected message from connection-id: type = message-type, subtype =
message-subtype
Description The chassis process (chassisd) received an unexpected message from a peer connection.
Severity error
Facility LOG_DAEMON
CHASSISD_IPC_WRITE_ERROR
System Log Message function-name: pipe_write failure for SCC connection with error error-code (error-message)
Description 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.
Severity warning
Facility LOG_DAEMON
CHASSISD_IPC_WRITE_ERR_NO_PIPE
System Log Message FRU has no connection pipe function-name fru-name
Description 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.
Severity warning
Facility LOG_DAEMON
CHASSISD_IPC_WRITE_ERR_NULL_ARGS
System Log Message FRU has no connection arguments function-name fru-name

Description 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.
Severity warning
Facility LOG_DAEMON

CHASSISD_ISSU_BLOB_ERROR
System Log Message fru-name: error-message
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.
Severity notice
Facility LOG_DAEMON
CHASSISD_ISSU_DAEMON_ERROR
System Log Message Daemon [process-name] state:<state> error:<error-message>
Description The chassisd process (chassisd) encountered the indicated error in the indicated in
service software upgrade (issu) state for the indicated daemon.
Severity notice
Facility LOG_DAEMON
CHASSISD_ISSU_ERROR
System Log Message action error-code(error-message)
Description The chassisd process (chassisd) encountered the indicated error for the indicated in
service software upgrade process (issu) action.
Severity notice
Facility LOG_DAEMON
CHASSISD_ISSU_FRU_ERROR
System Log Message fru-name: state:[state] error-message

Description The chassisd process (chassisd) encoutered the indicated error during the in service
software upgrade for the indicated field replaceable unit (fru).
Severity notice
Facility LOG_DAEMON
CHASSISD_ISSU_FRU_IPC_ERROR
System Log Message fru-name: state:[state] error:[message] reason:[error-message]
Description The chassisd process (chassisd) detected the indicated error for the indicated field
replaceable unit (fru) during in service software upgrade (issu).
Severity notice
Facility LOG_DAEMON
CHASSISD_JTREE_ERROR
System Log Message jtree terminate operation returned error-code
Description The chassis process (chassisd) received the indicated error when executing the JUNOS
system call that terminates the jtree.
Severity warning
Facility LOG_DAEMON
CHASSISD_LCC_RELEASE_MASTERSHIP
System Log Message Backup Routing Engine became master, because JUNOS version of former master did
not match SCC master
Description 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.
Severity notice
Facility LOG_DAEMON
Cause 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.
CHASSISD_LOST_MASTERSHIP
System Log Message Routing Engine lost mastership; exiting

Description The chassis process (chassisd) running on the master Routing Engine exited, because
mastership switched to the other Routing Engine.
Severity error
Facility LOG_DAEMON
CHASSISD_MAC_ADDRESS_AE_ERROR
System Log Message chassisd MAC address allocation error for aedevice-id
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.
Severity error
Facility LOG_DAEMON
CHASSISD_MAC_ADDRESS_ATS_ERROR
System Log Message chassisd MAC address allocation error for atsdevice-id
for the indicated ATS Ethernet interface because of an internal error.
Severity error
Facility LOG_DAEMON
CHASSISD_MAC_ADDRESS_CBP_ERROR
System Log Message chassisd MAC address allocation error for CBP
for a customer backbone port because of an internal error.
Severity error
Facility LOG_DAEMON
CHASSISD_MAC_ADDRESS_ERROR
System Log Message chassisd MAC address allocation exceed error for FPC fpc-slot, PIC pic-slot, port port
for the indicated interface because of an internal error.

Severity error
Facility LOG_DAEMON

CHASSISD_MAC_ADDRESS_FABRIC_ERR
System Log Message Unable to allocate MAC address for fabric interface device-id
for the indicated fabric interface because of an internal error.
Severity error
Facility LOG_DAEMON

CHASSISD_MAC_ADDRESS_IRB_ERROR
System Log Message chassisd MAC address allocation error for IRB
for an integrated routing and bridging interface because of an internal error.
Severity error
Facility LOG_DAEMON
CHASSISD_MAC_ADDRESS_PIP_ERROR
System Log Message chassisd MAC address allocation error for PIP
for a provider instance port because of an internal error.
Severity error
Facility LOG_DAEMON
CHASSISD_MAC_ADDRESS_PLT_ERROR
System Log Message chassisd MAC address allocation error for PLT
for the pseudo logical tunnel interface because of an internal error.

Severity error
Facility LOG_DAEMON
CHASSISD_MAC_ADDRESS_SWFAB_ERR
System Log Message Unable to allocate MAC address for swfabric interface device-id
for the indicated swfabric interface because of an internal error.
Severity error
Facility LOG_DAEMON
CHASSISD_MAC_ADDRESS_VIRB_ERROR
System Log Message chassisd MAC address allocation error for IRB
Severity error
Facility LOG_DAEMON
CHASSISD_MAC_ADDRESS_VLAN_ERROR
System Log Message chassisd MAC address allocation error for VLAN
for a vlan interface because of an internal error.
Severity error
Facility LOG_DAEMON
CHASSISD_MAC_ADDRESS_VTEP_ERROR
System Log Message chassisd MAC address allocation error for VTEP
Severity error
Facility LOG_DAEMON

CHASSISD_MAC_DEFAULT
System Log Message Using default MAC address base
Description The chassis process (chassisd) used the default base media access control (MAC)
address.
Severity info
Facility LOG_DAEMON
CHASSISD_MAIN_THREAD_STALLED
System Log Message main chassis-control thread stalled for duration sec -- exiting
Description Chassis control daemon main thread did not run for a long duration.
Severity error
Facility LOG_DAEMON
Action A core dump of chassis control daemon will be attempted.
CHASSISD_MALLOC_FAILURE
System Log Message function-name: chassisd malloc failed, aborting
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_MASTER_CG_REMOVED
System Log Message Master fru-name (slot fru-slot) removed; powering it down
Description The master Clock Generator (CG) was removed. The CG provides the clock for interfaces
timing, so those interfaces might drop packets and experience other errors until a new
clock source has been established.
Severity critical

Facility LOG_DAEMON
CHASSISD_MASTER_PCG_REMOVED
System Log Message Master PCG (slot pcg-slot) removed; powering down Packet Forwarding Engine complex
Description 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.
Severity critical
Facility LOG_DAEMON
CHASSISD_MASTER_SCG_REMOVED
System Log Message Master SCG (slot fru-slot) removed; powering it down
Description 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.
Severity critical
Facility LOG_DAEMON
CHASSISD_MBUS_ERROR
System Log Message fru-name fru-slot: management bus failed sanity test
Description Startup tests on the indicated FRU's management bus failed.
Severity error
Facility LOG_DAEMON
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
Description 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 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.

Severity warning
Facility LOG_DAEMON
Action 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 Received SIGUSR2 without any interrupts pending
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_MGR_CONNECT
Description The chassis process (chassisd) could not to open a pipe for interprocess communication
(IPC) to a component (field-replaceable unit, or FRU).
Severity error
Facility LOG_DAEMON
CHASSISD_MIC_OFFLINE_NOTICE
System Log Message Taking MIC mic-slot in FPC fpc-slot offline: reason
Description The chassis process (chassisd) took the indicated MIC offline, for the indicated reason.
Severity notice
Facility LOG_DAEMON

CHASSISD_MULTILINK_BUNDLES_ERROR
System Log Message Unable to set multilink Frame Relay UNI NNI bundles for PIC pic-slot in FPC fpc-slot
Description 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 PIC.
Severity warning
Facility LOG_DAEMON
CHASSISD_MXC_LINK
System Log Message MXC: operation: filename, error: error-code -- error-message
Description The chassis process (chassisd) could not link the specified package to the application
services (AS-MXC) PIC.
Severity critical
Facility LOG_DAEMON
CHASSISD_NO_CGS
System Log Message No fru-name status
Description The chassis process (chassisd) could not find an operational Clock Generator (CG). To
continue functioning properly, interfaces that use a CG as their clock source must find
another source.
Severity error
Facility LOG_DAEMON
CHASSISD_NO_PCGS
System Log Message No PCG status
Description The chassis process (chassisd) could not find an operational Packet Forwarding Engine
Clock Generator (PCG). Packet forwarding is halted until a PCG becomes operational.

Severity error
Facility LOG_DAEMON
CHASSISD_NO_SCGS
System Log Message No SCG state
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_OFFLINE_NOTICE
System Log Message Routing Engine offline: message
Description The chassis process (chassisd) took the Routing Engine offline.
Severity critical
Facility LOG_DAEMON
CHASSISD_OID_GEN_FAILED
System Log Message Unable to generate OID: oid (error-message)
Description The chassis process (chassisd) could not generate an object identifier (OID) for the
indicated object.
Severity error
Facility LOG_DAEMON
CHASSISD_OVER_TEMP_CONDITION
System Log Message Chassis temperature over temperature degrees C (message); routing platform will
shutdown in duration seconds if condition persists
Description The temperature of one or more components (field-replaceable units, or FRUs) exceeded

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.
Severity error
Facility LOG_DAEMON
Action Increase cooling in the area around the chassis. For more information, see
CHASSISD_OVER_TEMP_SHUTDOWN_TIME
System Log Message Chassis temperature above temperature degrees C description (> duration seconds);
powering down all FRUs
Description 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.
Severity critical
Facility LOG_DAEMON
http://kb.juniper.net/InfoCenter/index?page=content&id=KB18833
CHASSISD_PARSE_COMPLETE
System Log Message Using new configuration
Description The chassis process (chassisd) successfully parsed its configuration file.
Severity info
Facility LOG_DAEMON
CHASSISD_PCI_ERROR
Description While performing an operation on the PCI bus, the chassis process (chassisd) encountered
the indicated error.
Severity error

Facility LOG_DAEMON
Cause A software or a hardware problem occurred.
CHASSISD_PDU_BREAKER_TRIP
System Log Message Circuit breaker tripped for PDU pdu-slot
Description The circuit breaker was tripped for the indicated power distibution unit (PDU).
Severity warning
Facility LOG_DAEMON
Action Turn on the affected PDU manually.
CHASSISD_PDU_NOT_OK
System Log Message error-message for PDU pdu-slot (status bits: 0xstatus-code)
Description The chassis process (chassisd) detected the indicated error condition for the indicated
power distribution unit (PDU).
Severity warning
Facility LOG_DAEMON
CHASSISD_PEER_UNCONNECTED
System Log Message function-name: peer not connected
Description The chassis process (chassisd) processed a packet for a peer with an invalid or missing
connection.
Severity error
Facility LOG_DAEMON
Cause In most cases, this error is caused by peers transitioning up and down unexpectedly. The
error is usually transient and nonfatal.
CHASSISD_PEM_BREAKER_TRIP
System Log Message Circuit breaker tripped for power supply pem-slot

Description The circuit breaker was tripped for the indicated power entry module (PEM).
Severity warning
Facility LOG_DAEMON
Action Turn on the affected PEM manually.
CHASSISD_PEM_IMPROPER
System Log Message Power supply pem-slot improper for platform
Description Old PEM is not supported in this platform.
Severity error
Facility LOG_DAEMON
Action 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
power entry module (PEM).
Severity warning
Facility LOG_DAEMON
Action Check the status of the circuit breaker and the input connections.
CHASSISD_PEM_NOT_SUFFICIENT
System Log Message Unable to power up FPC fpc-slot, because no three-input 240-A power supply is installed
Description 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.
Severity error
Facility LOG_DAEMON
Action Install at least one three-input 240-A power supply.

CHASSISD_PEM_OVERLOAD
System Log Message Overload condition for power supply pem-slot (status bits: 0xstatus-code);
Description The indicated power entry module (PEM) reported an output voltage overload condition.
Severity warning
Facility LOG_DAEMON
Cause There might have been excessive load on the PEM.
CHASSISD_PEM_TEMPERATURE
System Log Message Temperature check bit set for power supply pem-slot; airflow might be inadequate
Description The chassis process (chassisd) detected that the 'temperature check bit' was set in the
status bit mask for the indicated power entry module (PEM).
Severity warning
Facility LOG_DAEMON
Cause The PEM might have exceeded its temperature threshold, possibly because the airflow
through it was inadequate.
CHASSISD_PEM_VOLTAGE
System Log Message Power supply pem-slot reports problem; check output voltage
Description The indicated power entry module (PEM) reported a problem with its output voltage.
Severity warning
Facility LOG_DAEMON
Cause There might have been excessive load on the PEM.
CHASSISD_PFE_LAUNCH_ERROR
System Log Message Failed to launch PFE: error-message

Description The chassis process (chassisd) failed to launch the PFE image.
Severity error
Facility LOG_DAEMON
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
PIC online, but stopped trying after all attempts failed.
Severity error
Facility LOG_DAEMON
CHASSISD_PIC_CMD_TIMEOUT
System Log Message function-name: attempt to bring PIC pic-slot in FPC fpc-slot online timed out
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_PIC_CONFIG_CONFLICT
System Log Message fpc pic-slot pic fpc-slot port mirror instance instance will be applied to both the PICs
Description The PIC configuration will be alpplied to all PICs on the FPC
Severity unknown
Facility LOG_DAEMON
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

Description The chassis process (chassisd) did not create an interface device for the indicated 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.
Severity error
Facility LOG_DAEMON
Action Remove the PIC or upgrade the Junos OS.
CHASSISD_PIC_HWERROR
System Log Message PIC pic-slot in FPC fpc-slot (PIC type pic-type, version version) had hardware error
Description The indicated PIC experienced a hardware error. The chassis process (chassisd) did not
bring the PIC online.
Severity warning
Facility LOG_DAEMON
CHASSISD_PIC_OFFLINE_NOTICE
System Log Message Taking PIC pic-slot in FPC fpc-slot offline: reason
Description The chassis process (chassisd) took the indicated Physical Interface Card (PIC) offline,
Severity notice
Facility LOG_DAEMON
CHASSISD_PIC_OID_GEN_FAILED
System Log Message Unable to generate OID for PIC: pic-name (error-message)
Description The chassis process (chassisd) could not generate an object identifier (OID) for the
indicated Physical Interface Card (PIC).
Severity error
Facility LOG_DAEMON

CHASSISD_PIC_OID_UNKNOWN
System Log Message Unable to find OID for PIC: i2c-id
Description The chassis process (chassisd) could not determine the object identifier (OID) for the
Physical Interface Card (PIC) with the indicated identifier.
Severity error
Facility LOG_DAEMON
CHASSISD_PIC_PORT_ERROR
System Log Message chassisd pic/port check and set error for FPC fpc-slot, PIC pic-slot, port port
Description The chassis process (chassisd) could not set the port attributes for the indicated interface
because of an internal error.
Severity error
Facility LOG_DAEMON
CHASSISD_PIC_RESET_ON_SWITCHOVER
System Log Message PIC pic-slot in FPC fpc-slot (type pic-type: pic-name, version version) does not support
GRES and will be reset on switchover
Description The chassis process (chassisd) noted that the Physical Interface Card (PIC) with the
indicated characteristics needs to be reset when a graceful switchover occurs.
Severity warning
Facility LOG_DAEMON
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
Description 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.
Severity error
Facility LOG_DAEMON

Action Reconfigure the PIC with a valid speed.
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
Description The chassis process (chassisd) did not bring the indicated Physical Interface Card (PIC)
online, because its hardware version is not supported.
Severity warning
Facility LOG_DAEMON
Cause The PIC requires a hardware upgrade.
CHASSISD_PIDFILE_OPEN
System Log Message Unable to open PID file 'filename': errno error-code
Description The chassis process (chassisd) could not open the file where it stores its process ID (PID).
Severity error
Facility LOG_DAEMON
Cause The chassisd process might have detected that another chassisd process was running
and tried to read the file so that it could use the PID recorded there when terminating the
other process.
CHASSISD_POWER_CHECK
System Log Message fru-name fru-slot not powering up
Description The chassis process (chassisd) could not power up the indicated component
(field-replaceable unit, or FRU), because the FRU did not respond.
Severity error
Facility LOG_DAEMON


CHASSISD_POWER_EVENT
System Log Message Unable to turn off power to fru-name fru-slot; a stand-alone test jumper might be installed
Description The chassis process (chassisd) could not turn off power to the indicated component
(field-replaceable unit, or FRU).
Severity warning
Facility LOG_DAEMON
Cause A common reason is that a standalone test jumper is installed.
CHASSISD_POWER_ON_CHECK_FAILURE
System Log Message fru-name-fru-slot is already powered on, no need to re-power
Description The chassis process (chassisd) is getting a power- not-on status for a FRU
(field-replaceable unit) that is already powered on.
Severity error
Facility LOG_DAEMON
Cause This could be due to bad hardware or communication failure between hardware and
software.
CHASSISD_POWER_RATINGS_EXCEEDED
System Log Message PIM/module in slot fru-slot left offline to avoid exceeding chassis power ratings
Description 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 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.
Severity error
Facility LOG_DAEMON
CHASSISD_PSD_RELEASE_MASTERSHIP
System Log Message Backup Routing Engine became master, because JUNOS version of former master did
not match RSD master
Description 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.

Severity notice
Facility LOG_DAEMON
Cause 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.
CHASSISD_PSM_NOT_OK
System Log Message error-message for PDU pdu-slot PSM psm-slot (status bits: 0xstatus-code)
power supply module (PSM).
Severity warning
Facility LOG_DAEMON
CHASSISD_PSM_NOT_OK_1
System Log Message error-message for PSM psm-slot (status bits: 0xstatus-code)
power supply module (PSM).
Severity warning
Facility LOG_DAEMON
CHASSISD_PSM_TRIP
System Log Message Power supply module psm-slot tripped
Description The indicated power supply module (PSM) was tripped.
Severity warning
Facility LOG_DAEMON
CHASSISD_PSU_ERROR
System Log Message error-message power supply pem-slot (status bits: 0xstatus-code); status failure

power supply unit (PSU).
Severity warning
Facility LOG_DAEMON

CHASSISD_PSU_FAN_FAIL
System Log Message Fan Fail for power supply pem-slot
Description PSU Fan fail bit is set in the status for the indicated power supply unit (PSU)
Severity warning
Facility LOG_DAEMON

CHASSISD_PSU_INPUT_BAD
System Log Message error-message power supply pem-slot (status bits: 0xstatus-code); Input failure
Description The chassis process (chassisd) detected the input voltage/warning fault condition for
the indicated power supply unit (PSU).
Severity warning
Facility LOG_DAEMON
Action Check the status of the input connections. For more information, see
CHASSISD_PSU_OVERLOAD
System Log Message Overload condition for power supply pem-slot (status bits: 0xstatus-code);
Description The indicated power supply unit (PSU) reported an output voltage overload condition.
Severity warning
Facility LOG_DAEMON
Cause There might have been excessive load on the PSU.


CHASSISD_PSU_TEMPERATURE
System Log Message Temperature check bit set for power supply pem-slot; airflow might be inadequate
Description The chassis process (chassisd) detected that the 'temperature check bit' was set in the
status bit mask for the indicated power supply unit (PSU).
Severity warning
Facility LOG_DAEMON
Cause The PSU might have exceeded its temperature threshold, possibly because the airflow
through it was inadequate.

CHASSISD_PSU_VOLTAGE
System Log Message Power supply pem-slot reports problem; check output voltage
Description The indicated power supply unit (PSU) reported a problem with its output voltage.
Severity warning
Facility LOG_DAEMON
Cause There might have been excessive load on the PSU.

CHASSISD_RANGE_CHECK
System Log Message function-name: '0xvalue' is invalid value for object-name (out of range)
Description The indicated value was outside the valid range of values for the indicated object.
Severity error
Facility LOG_DAEMON

CHASSISD_RECONNECT_SUCCESSFUL
System Log Message Successfully reconnected on soft restart
Description The chassis process (chassisd) successfully reconnected with each Packet Forwarding
Engine after a soft restart.
Severity notice
Facility LOG_DAEMON
CHASSISD_RELEASE_MASTERSHIP
System Log Message Release mastership notification
Description The chassis process (chassisd) running on the master Routing Engine received a request
to release mastership.
Severity info
Facility LOG_DAEMON
Cause The Routing Engine was probably rebooting and graceful Routing Engine switchover is
configured.
CHASSISD_RE_CONSOLE_FE_STORM
System Log Message Console device encountering framing error storm on Routing Engine routing-engine-slot
(possibly a bad console cable)
Description At least one console device on the Routing Engine has encounted excessive framing
errors. This can be indicative of a bad cable connected to the device (especially true in
the case of a serial console port.)
Severity error
Facility LOG_DAEMON
CHASSISD_RE_CONSOLE_ME_STORM
System Log Message Console device encountering modem error storm on Routing Engine routing-engine-slot
(possibly a bad console cable)
Description At least one console device on the Routing Engine has encountered excessive modem
errors. This can be indicative of a bad cable connected to the device (especially in the
case of a serial console port).
Severity error

Facility LOG_DAEMON
CHASSISD_RE_INIT_INVALID_RE_SLOT
System Log Message re_init: re routing-engine-slot, out of range
Description The chassis process (chassisd) could not initialize a Routing Engine because the slot
number specified for it was invalid.
Severity error
Facility LOG_DAEMON
CHASSISD_RE_OVER_TEMP_CONDITION
System Log Message Routing Engine routing-engine-slot temperature (temperature C) over threshold degrees
C
Description The temperature of the indicated Routing Engine exceeded the indicated temperature,
which is the upper of two thresholds.
Severity error
Facility LOG_DAEMON
CHASSISD_RE_OVER_TEMP_SHUTDOWN
System Log Message Routing Engine routing-engine-slot temperature above threshold degrees C for too long;
action
Description 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.
Severity critical
Facility LOG_DAEMON
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

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.
Severity error
Facility LOG_DAEMON
CHASSISD_RE_WARM_TEMP_CONDITION
System Log Message Routing Engine routing-engine-slot temperature (temperature C) is above warm
temperature limit (threshold C)
which is the lower of two thresholds.
Severity error
Facility LOG_DAEMON
CHASSISD_ROOT_MOUNT_ERROR
System Log Message Unable to determine the mount point for root directory: error-message
Description The chassis process (chassisd) could not determine the mount point for the root file
system.
Severity error
Facility LOG_DAEMON
CHASSISD_RTS_SEQ_ERROR
System Log Message ifmsg sequence gap expected-value - received-value
Description The chassis process (chassisd) received a routing socket message out of order.
Severity warning
Facility LOG_DAEMON

Cause 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
Description 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.
Severity error
Facility LOG_DAEMON
Cause Either a previous software upgrade did not complete successfully, or the chassisd process
or FRU did not restart after a successful software upgrade.
Action Upgrade the software and reboot the routing platform.
CHASSISD_SENSOR_RANGE_NOTICE
System Log Message fru-name fru-slot temperature is temperature degrees C, which is outside operating range
Description The temperature sensor on the indicated component (field-replaceable unit, or FRU)
reported the indicated temperature, which is outside the acceptable operating range.
Severity warning
Facility LOG_DAEMON
Cause Some sensors generate erroneous readings when a FRU starts up. When this happens,
the chassis process (chassisd) rereads the sensor at a later time.
CHASSISD_SERIAL_ID
System Log Message Serial ID read error: error-code -- error-message
Description The chassis process (chassisd) could not obtain the Routing Engine's serial number from
the kernel because of the indicated error.
Severity warning
Facility LOG_DAEMON
CHASSISD_SFC_FPM_CHCFG_WARNING
System Log Message SFC Front Panel craft interface setting is changed : Chassis Number 0xold-index ->
0xindex, Config Size 0xold-size -> 0xsize

Description SFC Front Panel Dial Switches Chassis Number and Config Size are changed. Chassis
Number setting change is ignored. Config Size setting change affects the SFC operation
mode on next reboot.
Severity warning
Facility LOG_DAEMON
Action If the changes were accidental, return the dial to the correct settings before the next
reboot. If the changes were intended, make sure the right hardware configuration is
present.
CHASSISD_SFM_MODE_ERROR
Description The chassis process could not configure a requested operational mode for a Switching
and Forwarding Module (SFM), for the indicated reason.
Severity info
Facility LOG_DAEMON
Cause 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 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 function-name: SFM sfm-slot not online
Description The indicated Switching and Forwarding Module (SFM) was offline.
Severity error
Facility LOG_DAEMON
CHASSISD_SHUTDOWN_NOTICE
System Log Message Shutdown reason: reason
Description 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.

Severity warning
Facility LOG_DAEMON
CHASSISD_SIB_INVALID_SLOT
System Log Message fru-name in invalid slot slot
Description The chassis process (chassisd) detected the presence of the switch interface board
(SIB) in an invalid slot. The SIB remains offline.
Severity error
Facility LOG_DAEMON
CHASSISD_SIGPIPE
System Log Message SIGPIPE received
Description 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.
Severity info
Facility LOG_DAEMON
Cause The entity at the other end of the pipe exited or closed the connection.
CHASSISD_SMB_ERROR
System Log Message smb_read: fpga download not complete: val return-value, action
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_SMB_INVALID_PS
System Log Message function-name: invalid power supply status code (0xstatus-code)
Description 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.

Severity critical
Facility LOG_DAEMON
CHASSISD_SMB_IOCTL_FAILURE
System Log Message function-name: 'operation' ioctl failed on system management bus (address
0xmemory-address, cmd 0xcommand)
Description The indicated ioctl() operation failed at the indicated address on the system management
bus (SMB).
Severity error
Facility LOG_DAEMON
CHASSISD_SMB_READ_FAILURE
System Log Message function-name: read() failed on system management bus (address 0xmemory-address)
Description A read() operation failed at the indicated address on the system management bus (SMB).
Severity error
Facility LOG_DAEMON
CHASSISD_SNMP_TRAP1
System Log Message SNMP trap generated: trap (argument1 value1)
Description The chassisd process (chassisd) generated the indicated simple network management
protocol (snmp) trap with the indicated value.
Severity notice
Facility LOG_DAEMON

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)
Description The chassis process (chassisd) generated a Simple Network Management Protocol
(SNMP) trap with the ten indicated argument-value pairs.
Severity notice
Facility LOG_DAEMON
CHASSISD_SNMP_TRAP3
System Log Message ENTITY trap generated: trap (argument1 value1, argument2 value2, argument3 value3)
Description The chassisd process (chassisd) generated the indicated simple network management
protocol (snmp) trap with the three indicated argument-value pairs.
Severity notice
Facility LOG_DAEMON
CHASSISD_SNMP_TRAP6
argument4 value4, argument5 value5, argument6 value6)
(SNMP) trap with the six indicated argument-value pairs.
Severity notice
Facility LOG_DAEMON
CHASSISD_SNMP_TRAP7
argument4 value4, argument5 value5, argument6 value6, argument7 value7)
(SNMP) trap with the seven indicated argument-value pairs.
Severity notice
Facility LOG_DAEMON

CHASSISD_SPI_IOCTL_FAILURE
System Log Message function-name: reason 0xaddress, error error-message
indicated register of the spi device.
Severity error
Facility LOG_DAEMON
CHASSISD_SPMB_RESTART
System Log Message SPMB slot restarted
Description The indicated Switch Processor Mezzanine Board (SPMB) restarted.
Severity info
Facility LOG_DAEMON
CHASSISD_SPMB_RESTART_TIMEOUT
System Log Message Attempt count to restart SPMB slot timed out; action
Switch Processor Mezzanine Board (SPMB) online. The chassisd process performed the
indicated action as a result of the failure.
Severity error
Facility LOG_DAEMON
CHASSISD_SSB_FAILOVERS
System Log Message fru-name failover occurred count times
Description The indicated packet-switching component or control board failed over to a redundant
neighbor the indicated number of times, which exceeds the maximum limit.
Severity warning
Facility LOG_DAEMON
Cause There is probably a system error.

CHASSISD_STANDALONE_FPC_NOTICE
System Log Message chassisd running in standalone FPC mode mode
Description 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.
Severity warning
Facility LOG_DAEMON
CHASSISD_SYSCTL_ERROR
System Log Message function-name: sysctl-error error from sysctl-function-name: error-message (errno
error-code)
Description The chassis process (chassisd) received the indicated error from the indicated sysctl()
operation.
Severity error
Facility LOG_DAEMON
CHASSISD_TEMP_HOT_NOTICE
System Log Message fru-name temperature of temperature degrees C is above limit (threshold degrees)
Description 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.
Severity error
Facility LOG_DAEMON
CHASSISD_TEMP_SENSOR_FAILURE
System Log Message function-name: unable to read temperature sensor for fru-name
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.

Severity error
Facility LOG_DAEMON
CHASSISD_TERM_SIGNAL
System Log Message Received SIGTERM request, shutting down
Description 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.
Severity info
Facility LOG_DAEMON
CHASSISD_TIMER_CLR_ERR
System Log Message function-name: message
Description The chassis process (chassisd) could not clear the state of the timer it had set to track
the timeout period for an event.
Severity error
Facility LOG_DAEMON
CHASSISD_TIMER_ERR
System Log Message Unable to schedule timeout for description
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.
Severity error
Facility LOG_DAEMON
CHASSISD_TIMER_VAL_ERR
System Log Message Null timer ID
Description 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.

Severity error
Facility LOG_DAEMON

CHASSISD_UNEXPECTED_EXIT
System Log Message evMainLoop returned return-value (errno error-code)
Description The chassis process (chassisd) exited unexpectedly and reported the indicated error.
Severity error
Facility LOG_DAEMON

CHASSISD_UNEXPECTED_VALUE
System Log Message function-name: 'value' is invalid value for object-name
Description 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.
Severity warning
Facility LOG_DAEMON
CHASSISD_UNSUPPORTED_FPC
System Log Message FPC with I2C ID of 0xi2c-id is not supported
Description 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.
Severity error
Facility LOG_DAEMON

CHASSISD_UNSUPPORTED_MODEL
System Log Message Model model unsupported with this version of chassisd
Description The version of the chassis process (chassisd) software that is installed on the routing
platform does not support this type of chassis.
Severity warning
Facility LOG_DAEMON
CHASSISD_UNSUPPORTED_PIC
System Log Message PIC pic-slot in FPC fpc-slot (type pic-type, version version) is not supported
Description 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.
Severity warning
Facility LOG_DAEMON
CHASSISD_UNSUPPORTED_PIC_MODE
System Log Message Application mode mode is not supported for PIC pic-slot in FPC fpc-slot
Description The indicated Physical Interface Card (PIC) does not support the indicated application
mode configured for it.
Severity warning
Facility LOG_DAEMON
Action Check which application modes are supported for the PIC.
CHASSISD_UNSUPPORTED_SIB
System Log Message SIB with assembly ID assembly-id is not supported reason
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.

Severity error
Facility LOG_DAEMON
CHASSISD_VCHASSIS_CONVERT_ERROR
System Log Message function-name: fpc-slot/pic-slot/port conversion timeout; type type-string
Description The chassis process (chassisd) timed out awaiting notification from an fpc that an
interface being converted to or from a vc-port was deleted.
Severity error
Facility LOG_DAEMON
CHASSISD_VCHASSIS_LICENSE_ERROR
System Log Message Virtual Chassis License not installed
Description A virtual-chassis operational mode command was executed without a valid virtual chassis
license being installed.
Severity error
Facility LOG_DAEMON
CHASSISD_VCHASSIS_MEMBER_LIST_NOTICE
System Log Message Members: member-list
Description List of virtual-chassis members
Severity notice
Facility LOG_DAEMON
CHASSISD_VCHASSIS_MEMBER_OP_NOTICE
System Log Message Member change: vc operation of member member-id
Description The change being made to the member
Severity notice
Facility LOG_DAEMON

CHASSISD_VCHASSIS_MEMBER_UPDATE_NOTICE
System Log Message Membership update: Member old-member-id->member-id, Mode
old-member-mode->member-mode, master-member-idM backup-member-idB, Master
master-change, Members members-change
Description A virtual-chassis membership change is being reported
Severity notice
Facility LOG_DAEMON
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
Description 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.
Severity error
Facility LOG_DAEMON
Cause Either a previous software upgrade did not complete successfully, or the chassisd process
or FRU did not restart after a successful software upgrade.
Action Upgrade the software and reboot the routing platform.
CHASSISD_VOLTAGE_READ_FAILED
System Log Message Unable to read voltage from fru-name (group group-id, address address, channel
voltage-channel)
Description The chassis process (chassisd) could not read voltage data from the indicated component
(field-replaceable unit, or FRU).
Severity error
Facility LOG_DAEMON

CHASSISD_VOLTAGE_SENSOR_INIT
System Log Message Unable to initialize voltage sensor for fru-name (group group-id, address address)
Description The chassis process (chassisd) could not initialize the voltage sensor for the indicated
component (field-replaceable unit, for FRU).
Severity error
Facility LOG_DAEMON
CHASSISD_VSERIES_LICENSE_ERROR
System Log Message CHASSISD_VSERIES_LICENSE_ERROR: error-message
Description A virtual Appliance Operational Command was executed without a valid virtual appliance
license being installed.
Severity error
Facility LOG_DAEMON
CHASSISD_ZONE_BLOWERS_SPEED
System Log Message Fans and impellers in zone zone are now running at normal speed
Description The fans (and impellers, if applicable) in zone were running at the normal speed.
Severity notice
Facility LOG_DAEMON
CHASSISD_ZONE_BLOWERS_SPEED_FULL
System Log Message Fans and impellers in zone zone being set to full speed [reason]
Description For the indicated reason, the chassis process (chassisd) increased the speed of fans
(and impellers, if applicable) in zone to the maximum.
Severity notice
Facility LOG_DAEMON
CHASSISD_ZONE_BLOWERS_SPEED_OFF
System Log Message Fans and impellers in zone zone being set to off [reason]

Description The fans (and impellers, if applicable) in zone were off.
Severity notice
Facility LOG_DAEMON

CHAPTER 24
CHASSISM System Log Messages
This chapter describes messages with the CHASSISM prefix. They are generated by the
chassis manager process (chassism), which controls hardware components on the
routing platform.
CHASSISM_SYSTEM
System Log Message reason: error-message
Description A system call made by this process failed.
Severity error
Facility LOG_DAEMON
Cause It is possible that the kernel lacked the resources to fulfill the request.


CHAPTER 25
CLKSYNCD System Log Messages
This chapter describes messages with the CLKSYNCD prefix.
CLKSYNCD_EVENT_BITS_DPLL_STATUS
System Log Message ifIndex: snmp-interface-index, ifName: interface-name, dpll_state: dpll-state
Description Signifies SyncE DPLL status changed(Unknown, LockAcq, Locked, Holdover, FreeRun).
Severity notice
Facility ANY
CLKSYNCD_EVENT_DPLL_STATUS
System Log Message dpll_state: dpll-state
Description Signifies DPLL status changed(Unknown, LockAck, Locked, Holdover, FreeRun).
Severity notice
Facility ANY
CLKSYNCD_EVENT_LED_STATE_CHANGED
System Log Message ifIndex: snmp-interface-index, ifName: interface-name, led-state: led-state
Description Signifies LED color changed.
Severity notice
Facility ANY

CLKSYNCD_EVENT_PRI_REF_CHANGED
System Log Message ifIndex: snmp-interface-index, ifName: interface-name
Description Signifies Primary reference changed.
Severity notice
Facility ANY
CLKSYNCD_EVENT_PRI_SRC_RECOVERED
Description Signifies Primary source recovered.
Severity notice
Facility ANY
CLKSYNCD_EVENT_PTP_CLOCK_ACCU_CHG
System Log Message gm_id: ptp-gm-id, clock_accuracy: clock-accuracy
Description Signifies PTP clock accuracy changed.
Severity notice
Facility ANY
CLKSYNCD_EVENT_PTP_CLOCK_CLASS_CHG
System Log Message gm_id: ptp-gm-id, clock_class: clock-class
Description Signifies PTP clock class changed.
Severity notice
Facility ANY

Chapter 25: CLKSYNCD System Log Messages
CLKSYNCD_EVENT_PTP_GM_CHG
System Log Message gm_id: ptp-gm-id
Description Signifies PTP Grand Master changed.
Severity notice
Facility ANY
CLKSYNCD_EVENT_PTP_HYBRID_STATUS
System Log Message hybrid_state: hybrid-state
Description Signifies Hybrid state changed (Init, FreqAcq, FreqLckPhaseAcq, FreqPhaseLck)
Severity notice
Facility ANY
CLKSYNCD_EVENT_PTP_SERVO_STATUS
System Log Message spll_state: servo-state
Description Signifies PTP servo state changed(Init, FreeRun, Holdover, Acquiring, FreqLock,
PhaseAlinged).
Severity notice
Facility ANY
CLKSYNCD_EVENT_RX_QL_CHANGED
System Log Message ifIndex: snmp-interface-index, ifName: interface-name, new_rx_ssm_ql: ql-code
Description Signifies RX quality level changed.
Severity notice
Facility ANY

CLKSYNCD_EVENT_SEC_REF_CHANGED
Description Signifies Secondary reference changed.
Severity notice
Facility ANY
CLKSYNCD_EVENT_SEC_SRC_RECOVERED
Description Signifies Secondary recovered failed. .
Severity notice
Facility ANY
CLKSYNCD_EVENT_SQUELCH_CLEAR
Description Interface activated.
Severity notice
Facility ANY
CLKSYNCD_EVENT_SQUELCH_SET
Description Interface squelched.
Severity notice
Facility ANY

CLKSYNCD_EVENT_SYNCE_DPLL_STATUS
System Log Message ifIndex: snmp-interface-index, ifName: interface-name, dpll_state: dpll-state
Description Signifies SyncE DPLL status changed(Unknown, LockAck, Locked, Holdover, FreeRun).
Severity notice
Facility ANY
CLKSYNCD_EVENT_TX_QL_CHANGED
System Log Message ifIndex: snmp-interface-index, ifName: interface-name, new_tx_ssm_ql: ql-code
Description Signifies TX quality level changed.
Severity notice
Facility ANY
CLKSYNCD_FAULT_ACBC_NOT_COMPATIBLE
System Log Message majorVer=snmp-interface-index, minorVer=interface-name
Description ACBC FPGA version is not compatible is SET.
Severity warning
Facility ANY
CLKSYNCD_FAULT_CPLD_NOT_COMPATIBLE
System Log Message majorVer=snmp-interface-index, minorVer=interface-name
Description Boot-cpld version is not compatible is SET.
Severity warning
Facility ANY

CLKSYNCD_FAULT_EFD_CLEAR
Description exceeded frequency deviation is CLEARed.
Severity notice
Facility ANY
CLKSYNCD_FAULT_EFD_SET
Description exceeded frequency deviation is SET.
Severity warning
Facility ANY
CLKSYNCD_FAULT_LOS_CLEAR
Description linkStatus is up.
Severity notice
Facility ANY
CLKSYNCD_FAULT_LOS_SET
Description linkStatus is down.
Severity warning
Facility ANY

CLKSYNCD_FAULT_LO_ESMC_CLEAR
Description loss of ESMC is CLEARed.
Severity notice
Facility ANY
CLKSYNCD_FAULT_LO_ESMC_SET
Description loss of ESMC is SET.
Severity warning
Facility ANY
CLKSYNCD_FAULT_LTI_CLEAR
Description loss of timing info is CLEARed.
Severity notice
Facility ANY
CLKSYNCD_FAULT_LTI_SET
Description loss of timing info is SET.
Severity warning
Facility ANY

CLKSYNCD_FAULT_PRI_SRC_FAILED
Description Signifies Primary source failed.
Severity warning
Facility ANY
CLKSYNCD_FAULT_PTP_UNI_NEG_RATE_REJ_CLEAR
System Log Message streamHandle: stream-handle, remoteIpAddr: remote-address
Description Signifies acceptance of grant duration for PTP Signalling messages.
Severity notice
Facility ANY
CLKSYNCD_FAULT_PTP_UNI_NEG_RATE_REJ_SET
System Log Message streamHandle: stream-handle, remoteIpAddr: remote-address
Description Signifies rejecting or receiving rejection for PTP Signalling messages.
Severity warning
Facility ANY
CLKSYNCD_FAULT_QL_FAIL_CLEAR
Description quality level failed is CLEARed.
Severity notice
Facility ANY

CLKSYNCD_FAULT_QL_FAIL_SET
Description quality level failed is SET.
Severity warning
Facility ANY
CLKSYNCD_FAULT_SEC_SRC_FAILED
Description Signifies Secondary source failed.
Severity warning
Facility ANY


CHAPTER 26
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 Error: Cannot have config error-message interface-name
Description The class-of-service (CoS) process (cosd) did not apply the config on this interface
because it was not valid in this case.
Severity error
Facility LOG_DAEMON
Cause One possible cause is if any Class-of-Service is configured on an interface which is a part
of an aggregated interface
Action Remove or change the config from/on the interface.
COSD_CHASSIS_SCHED_MAP_INVALID
System Log Message Chassis scheduler map incorrectly applied to interface interface-name: error-message
Description 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.
Severity error
Facility LOG_DAEMON
Cause 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 PIC;
therefore, a wildcard must be used to specify the interfaces. One exception to this rule
is the Gigabit Ethernet IQ PIC.

Action Correct the configuration used to apply the chassis scheduler map to the interface.
COSD_CLASSIFIER_NO_SUPPORT_LSI
System Log Message Cannot support classifier type classifier-type on lsi interface interface-name
Description The Differentiated Services code point (DSCP) classifier and the 802.1p classifier are
only supported on I-Chip based Flexible PIC Concentrators (FPCs).
Severity error
Facility LOG_DAEMON
Action Remove the DSCP or the 802.1p classifier configuration from the routing instance
COSD_CLASS_8021P_UNSUPPORTED
System Log Message ieee-802.1 classifier is not valid on interface interface-name
Description The IEEE 802.1p classifier is not supported on the indicated interface.
Severity warning
Facility LOG_DAEMON
Action Remove the 802.1p classifier configuration from the interface, or configure an interface
encapsulation type that supports 802.1p classifiers.
COSD_CLASS_NO_SUPPORT_IFD
System Log Message BA/Fixed Classifier or Rewrite on Physical Interface is not allowed when ethernet switching
family is configured: interace interface-name
Description The Rewrite is not supported on this interface when ethernet switching is enabled
Severity error
Facility LOG_DAEMON
Action Remove the classifier configuration from the interface, instead apply it on the logical
interface where ethernet switching family is enabled
Action Remove the Rewrite configuration from the interface, instead apply it on the logical
interface where ethernet switching family is enabled

Chapter 26: COSD System Log Messages
COSD_CLASS_NO_SUPPORT_L3_IFL
System Log Message BA/Fixed Classifier or Rewrite config is not allowed on logical interface (interface-name)
with inet/inet6 family
Description The Rewrite is not supported on this logical interface
Severity error
Facility LOG_DAEMON
Action Remove the classifier configuration from the logical interface, instead apply it on the
main interface if inet/inet6 is configured on one of its logical interfaces
Action Remove the Rewrite configuration from the logical interface, instead apply it on the main
interface if inet/inet6 is configured on one of its logical interfaces
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
Description The class-of-service (CoS) process (cosd) could not read configuration data.
Severity error
Facility ANY
Cause All of the following resons: mgd -I fails after upgrade-the file cosd.conf does not exist
and is not created because of the mgd -I failure The first commit is 'commit' and not
'commit full'-the file cosd.conf does not commit and is not created automatically
[class-of-service forwarding-classes] does not exist-the file cosd.conf does not get
exported with plain 'commit'
Action Do a 'commit full'
COSD_DB_OPEN_FAILED
System Log Message Unable to open configuration database: error-message(name)
Description The class-of-service (CoS) process (cosd) could not read configuration data for the
indicated reason.
Severity error
Facility LOG_DAEMON
Cause The specified database does not exist

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
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 specifies
exact transmission rate. The interface is housed on a type of 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.
Severity error
Facility LOG_DAEMON
Action Remove the 'exact' statement from the scheduler in the scheduler map applied to the
interface.
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
Description 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 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.
Severity error
Facility LOG_DAEMON
Action Remove the 'exact' statement from the scheduler in the scheduler map applied to the
session.
COSD_EXP_RW_L2_IFL_NOT_SUPPORTED
System Log Message EXP Rewrite on IFL is not allowed when ethernet switching family is configured: interace
interface-name

Description EXP rewrite is not supported on this logical interface.
Severity error
Facility LOG_DAEMON
Action Remove the exp rewrite configuration from the logical interface.
COSD_FABRIC_QUEUE_OVERFLOW
System Log Message Fabric Queue depth for fpc fpc-slot pfe pfe queue-name priority queue-index
queue-number exceeded threshold percentage-value percentage
Description The fabric queue is overflowing on the Flexible PIC Concentrator/Packet Forwarding
Engine.
Severity warning
Facility LOG_DAEMON
Action No action required
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
Description 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.
Severity warning
Facility LOG_DAEMON
Action Correct the configuration of the fragmentation map.
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
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 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.
Severity error
Facility LOG_DAEMON
Action Correct the configuration so that the scheduler map includes only one scheduler with
high, medium-high, or strict-high priority.
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
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
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.
Severity error
Facility LOG_DAEMON
Action Correct the configuration so that the scheduler map includes only one scheduler with
high, medium-high, or strict-high priority.
COSD_IFD_OUTPUT_SHAPING_RATE_ERR
System Log Message Traffic shaping not supported on interface device interface-name
Description The class-of-service (CoS) process (cosd) did not apply the shaping rate that is configured
for the indicated interface.
Severity error
Facility LOG_DAEMON
Cause Shaping rate is valid only for interfaces housed by IQ and IQ2 PICs, and the interface is
on a different type of PIC.

Action Remove the shaping rate configuration from the interface.
COSD_IFD_SHAPER_ERR
System Log Message port shaper not allowed on interface interface-name
Description The non-queuing dense port concentrators (DPCs) did not support the specified shaping
rate.
Severity error
Facility LOG_DAEMON
Cause The port shaper was not supported on the non-queuing DPCs.
Action Remove the shaping rate configuration from the interface.
COSD_INTERFACE_NO_MEDIA
System Log Message Unable to obtain media information for interface interface-name
Description The message sent by the kernel for the indicated interface did not include required media
information.
Severity error
Facility LOG_DAEMON
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
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.
Severity error
Facility LOG_DAEMON
Action Include the 'per-session-scheduler' statement in the configuration for the interface.

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
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 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.
Severity error
Facility LOG_DAEMON
Action Determine whether the interface is on an PIC that supports session-aware CoS; if not,
remove the 'per-session-scheduler' statement.
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
Layer 2 Tunneling Protocol (L2TP) session on the indicated interface, because
session-aware traffic shaping for L2TP is not configured on the 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.
Severity error
Facility LOG_DAEMON
Action Include the 'session-shaping' statement in the configuration for the PIC.
COSD_LARGE_DELAY_BUFFER_INVALID
System Log Message Error for interface interface-name error-message
Description The class-of-service (CoS) process (cosd) did not apply the large delay buffer setting
that is configured for the indicated interface.
Severity error
Facility LOG_DAEMON

Cause The interface is not housed on one of the PIC types that support large delay buffer.
Action Remove the large delay buffer configuration from the interface.
COSD_MALLOC_FAILED
System Log Message malloc failed: error-message
Description The class-of-service (CoS) process (cosd) could not dynamically allocate memory for
the indicated reason.
Severity error
Facility LOG_DAEMON
Cause A software bug caused a memory leak or the Routing Engine did not have sufficient
memory.
COSD_MAX_FORWARDING_CLASSES_ABC
System Log Message exceeding max 4 forwarding-class support.
Description User configuration exceeds the maximum number of forwarding class that is supported.
Severity warning
Facility LOG_DAEMON
Action Configure only four forwarding classes
COSD_MPLS_DSCP_CLASS_NO_SUPPORT
System Log Message Cannot support MPLS DSCP classifier on ifl interface-name
Description 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.
Severity error
Facility LOG_DAEMON
Action Remove the MPLS DSCP classifier configuration from the logical interface.

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
Description 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.
Severity warning
Facility LOG_DAEMON
Action 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 NULL input argument : error-message
Description The pointer that was passed to this function was NULL.
Severity error
Facility LOG_DAEMON
COSD_OUT_OF_DEDICATED_QUEUES
System Log Message Queue usage count for interface interface-name is at percentage-value percent
Description The class-of-service (CoS) process (cosd) is running out of dedicated queues.
Severity warning
Facility LOG_DAEMON
COSD_RATE_LIMIT_INVALID
System Log Message Unable to apply scheduler map scheduler-map to interface interface-name. description.
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 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.
Severity error
Facility LOG_DAEMON
Action 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
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
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 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.
Severity error
Facility LOG_DAEMON
Action Remove the 'rate-limit' statement from the scheduler in the scheduler map applied to
the interface.
COSD_REWRITE_RULE_LIMIT_EXCEEDED
System Log Message Number of rewrite rules applied to interface interface-name exceeds limit
(maximum-value)
Description 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.
Severity error
Facility LOG_DAEMON
Action Remove rewrite rules from the configuration for the interface.

COSD_RL_IFL_NEEDS_SHAPING
System Log Message "rate-limit" configured in scheduler-map, but ifl interface-name does not have output
shaper configured. It will use the ifd-shaping rate/ifd-transmit rate for implementation
of rate-limit.
Description The 'rate-limit' statement is configured in one or more schedulers that are part of the
indicated scheduler map. In order to apply this scheduler map to the indicated interface,
output shaping rate should be configured on the interface. Since no output shaping rate
is configured, the transmit rate or shaping rate of the parent interface will be used instead.
Severity warning
Facility LOG_DAEMON
Action Configure output shaping rate for the indicataed interface
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
Description 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.
Severity error
Facility LOG_DAEMON
Action Map only one forwarding class to the queue.
COSD_SCHED_AVG_CONST_UNSUPPORTED
System Log Message Averaging constant not supported on interface interface-name. Value set in scheduler-map
scheduler-map (scheduler name) will be ignored.
Description Configuring averaging constant is not supported on the indicated interface. Value set in
the indicated scheduler will be ignored.
Severity warning
Facility LOG_DAEMON
Action Remove the averaging-constant configuration from the indicated scheduler.

COSD_SCHED_MAP_GROUP_CONFLICT
System Log Message Interface interface-name cannot be bound to scheduler-map scheduler-map. It will be
bound to default scheduler-map
Description Interfaces belonging to a group cannot be bound to different scheduler maps. They will
be bound to the default scheduler map.
Severity error
Facility LOG_DAEMON
Action Map only one scheduler map to all the interfaces of a group.
COSD_SHAPER_GROUP_CONFLICT
System Log Message Interface interface-name cannot be bound to configured shaping-rate. It will be bound
to default rate
Description Interfaces belonging to a group cannot be bound to different shaping rates. They will be
bound to the default shaping rate.
Severity error
Facility LOG_DAEMON
Action Map only one shaping rate to all interfaces of a group.
COSD_STREAM_IFD_CREATE_FAILURE
System Log Message Unable to create special master interface device for interface-name
Description 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.
Severity error
Facility LOG_DAEMON
COSD_TIMER_ERROR
System Log Message Unable to set retry timer for rtsock write operation: error-message

Description 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.
Severity error
Facility LOG_DAEMON
COSD_TRICOLOR_ALWAYS_ON
System Log Message tri-color is always enabled in this platform. There is no need to explicitly set it.
Description Tri-color marking is always enabled on this platform. There is no need to explicitly set it.
Severity warning
Facility LOG_DAEMON
Action Remove the 'tri-color' configuration statement
COSD_TRICOLOR_NOT_SUPPORTED
System Log Message Unable to apply scheduler scheduler-map to interface interface-name, because it does
not support tricolor marking
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.
Severity error
Facility LOG_DAEMON
Action 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
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.
Severity error
Facility LOG_DAEMON
Action Decrease the value of one or more 'transmit-rate' statements so that the sum is less
than the interface transmission or shaping rate.
COSD_UNKNOWN_CLASSIFIER
System Log Message classifier type classifier-type is invalid
Description The class-of-service (CoS) process (cosd) did not recognize the indicated classifier type
from the rtsock library.
Severity warning
Facility LOG_DAEMON
COSD_UNKNOWN_REWRITE
System Log Message rtsock rewrite type type is invalid
Description The class-of-service (CoS) process (cosd) did not recognize the indicated rewrite type
from the rtsock library.
Severity warning
Facility LOG_DAEMON

COSD_UNKNOWN_TRAFFIC_CLASS_MAP
System Log Message traffic-class-map type traffic-class-map-type is invalid
Description The class-of-service (CoS) process (cosd) did not recognize the indicated
traffic-class-map type from the rtsock library.
Severity warning
Facility LOG_DAEMON
COSD_UNKNOWN_TRANSLATION_TABLE
System Log Message rtsock translation table type translation-table-type is invalid
Description The class-of-service (CoS) process (cosd) did not recognize the indicated translation
table type from the rtsock library.
Severity warning
Facility LOG_DAEMON

COSD_WAN_QUEUE_OVERFLOW
System Log Message Wan Queue depth for fpc fpc-slot Interface interface-name queue-index queue-number
exceeded threshold percentage-value
Description A queue from the WAN is overflowing on the Flexible PIC Concentrator.
Severity warning
Facility LOG_DAEMON
Action No action required

CHAPTER 27
DCBX System Log Messages
This chapter describes messages with the DCBX prefix. They are generated by the interface
process (lldpd), which is a discovery and capability exchange protocol to discover peers
and exchange information.
DCBX_PFC_DISABLED
System Log Message IF interface-name: PFC is getting disabled
Description PFC is getting disabled through DCBX.
Severity info
Facility LOG_DAEMON
Cause The DCBX PFC parameters negotiation is not successfull
DCBX_PFC_ENABLED
System Log Message IF interface-name: PFC is getting enabled
Description PFC is getting enabled through DCBX.
Severity info
Facility LOG_DAEMON
Cause The DCBX PFC parameters negotiation is successfull
DCBX_VERSION
System Log Message IF interface-name: DCBX TLV version 1.0 received
Description Ignoring received Data Center Bridging Protocol (DCBX) packet due to old version 1.0
Severity info
Facility LOG_DAEMON

Cause The software on the Host Bus Adapter (HBA) is not up-to-date

CHAPTER 28
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_AE_CONFIG_WARNING
System Log Message interface-name: AE is not supported in OSE mode for pic-type PIC type
Description Aggregated Ethernet cannot be configured on PD-5-10XGE-SFPP that is not explicitly

configured for linerate mode.
Severity warning
Facility LOG_DAEMON
Action Set this PIC to linerate mode, or remove the Aggregated Ethernet configuration for the
PD-5-10XGE-SFPP link.
DCD_FWD_CLASS_ACC_NOT_SUPPORTED
System Log Message interface-name: Forwarding-class accounting is supported only on MPCs
Description Forwarding-class accounting is supported only on LU based MPCs.
Severity error
Facility LOG_DAEMON
DCD_FWD_CLASS_ACC_NOT_SUPPORTED_IFL
System Log Message interface-name.interface-unit: Forwarding-class accounting is not supported on this MPC
Description Forwarding-class accounting on the logical interface is supported only on LU based

MPCs.
Severity error

Facility LOG_DAEMON
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
Description This interface needs either the tunnel key or the clear-dont-fragment-bit to be configured
along with allow-fragmentation
Severity error
Facility LOG_DAEMON
Action Configure either the tunnel key or clear-dont-fragment-bit for this tunnel
DCD_GRE_CONFIG_NOT_SUPPORTED
System Log Message The clear-dont-fragment-bit option is not supported on GRE tunnel (interface-name),
due to the FPC not supporting it
Description This interface is configured on a Flexible PIC Concentrator (FPC) that does not support
the clear- dont-fragment-bit statement at the [edit interfaces] hierarchy level.
Severity error
Facility LOG_DAEMON
Action Move the Physical Interface Card (PIC) to an FPC that is based on an I-Chip. For more
information, see KB25385.
DCD_MALLOC_FAILED_INIT
System Log Message Memory allocation failed during initialization for configuration load
Description The interface process (dcd) could not dynamically allocate memory in preparation for
loading a configuration.
Severity error
Facility LOG_DAEMON
Cause A software bug caused a memory leak, or the routing platform had insufficient memory.
DCD_PARSE_CFG_WARNING
System Log Message configuration-statement : warning-message

Chapter 28: DCD System Log Messages
Description The interface-control process (dcd) found a discrepant configuration
Severity warning
Facility LOG_DAEMON
Cause This is a warning message and the current configuration has a few discrepancies to be
addressed.
DCD_PARSE_EMERGENCY
System Log Message dcd_config: errors while parsing configuration file
Description The interface process (dcd) encountered an unhandled internal state while parsing the
configuration database.
Severity error
Facility LOG_DAEMON
Cause There might be a bug in the dcd process' parser.
DCD_PARSE_ERROR_CLOCK
System Log Message PIC housing interface interface-name does not support clocking as configured
Description 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 PIC.
Severity warning
Facility LOG_DAEMON
Action Remove the 'clocking' statement from the configuration for the interface.
DCD_PARSE_ERROR_HIER_SCHEDULER
System Log Message interface-name: hierarchical or shared scheduler is not valid on this interface
Description 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.

Severity warning
Facility LOG_DAEMON
Action Remove the 'hierarchical-scheduler' statement from the configuration for the interface.
DCD_PARSE_ERROR_IFLSET
System Log Message Interface interface-name does not support 'interface-set' statement
Description The 'interface-set' statement is included at the [edit interfaces] hierarchy level for the
indicated interface, but is not supported by the interface.
Severity warning
Facility LOG_DAEMON
Action Remove the 'interface-set' statement from the configuration for the interface.
DCD_PARSE_ERROR_MAX_HIER_LEVELS
System Log Message interface-name: PIC or encapsulation type does not support 'maximum-hierarchy-levels'
statement
Description The 'hierarchical-scheduler maximum-hierarchy-levels' 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.
Severity warning
Facility LOG_DAEMON
Action Remove the 'hierarchical-scheduler maximum-hierarchy-levels' statement from the

configuration for the interface.
DCD_PARSE_ERROR_MAX_HIER_LEVELS_2
System Log Message interface-name: PIC or encapsulation type does not support 3 levels of scheduler hierarchy
Description The PIC or encapsulation type configured on the indicated interface supports upto two
hierarchy levels and requires including the maximum-hierarchy-levels statement in the
hierarchial schedulers configuration.
Severity warning
Facility LOG_DAEMON
Action To configure two-level hierarchical scheduling, include the maximum-hierarchy-levels

statement at the [edit interfaces interface-name hierarchial-scheduler].

DCD_PARSE_ERROR_SCHEDULER
System Log Message interface-name: PIC or encapsulation type does not support 'per-unit-scheduler' or
'shared-scheduler' statement
Description 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.
Severity warning
Facility LOG_DAEMON
Action Remove the 'per-unit-scheduler' or 'shared-scheduler' statement from the configuration

for the interface.
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
Description The 'per-unit-scheduler' statement is enabled on more interfaces than what this PIC
would suppport.
Severity warning
Facility LOG_DAEMON
Action Remove the 'per-unit-scheduler' statement from the configuration for the interface.
DCD_PARSE_ERROR_VLAN_TAGGING
System Log Message interface-name: PIC type does not support flexible-vlan-tagging statement
Description The 'flexible-vlan-tagging' statement is included at the [edit interfaces] hierarchy level
for the indicated interface, but is not supported by the PIC that houses the interface.
Severity warning
Facility LOG_DAEMON
Action Remove the 'flexible-vlan-tagging' statement from the configuration for the interface.
DCD_PARSE_MINI_EMERGENCY
System Log Message dcd_mini_config: errors while parsing configuration overlay
Description The interface process (dcd) encountered an unhandled internal state during interface
parsing.

Severity error
Facility LOG_DAEMON
DCD_PARSE_STATE_EMERGENCY
System Log Message An unhandled state was encountered during interface parsing
Description The interface process (dcd) encountered an unhandled internal state during interface
parsing.
Severity emergency
Facility LOG_DAEMON
DCD_PARSE_WARN_INCOMPATIBLE_CFG
System Log Message configuration-statement : Incompatible configuration detected : warning-message
Description The interface process (dcd) found a configuration that will not be supported in future
releases.
Severity warning
Facility LOG_DAEMON
Cause This is a warning and the configuration will not be supported in future releases.
DCD_RLT_CONFIG_UNSUPPORTED
System Log Message IFD interface-name cannot be a member interface of rLT
Description All member interfaces of a redundant logical tunnel interface have to exist on Trio based
MPCs only.

Severity error
Facility LOG_DAEMON
Action Do not configure this interface as a member interface of redundant logical tunnel.


CHAPTER 29
DDOS System Log Messages
This chapter describes messages with the DDOS prefix. They are generated by the
distributed denial-of-service attack (DDoS), which is a denial-of-service (DoS) attack
originating from multiple source addresses.
DDOS_PROTOCOL_VIOLATION_CLEAR
System Log Message Protocol protocol-name has returned to normal. Violated at source-name for repeat-count
times, from time-first-detected to time-last-detected
Description The ddos system detected that the incoming traffic for a violated control protocol returned
to normal.
Severity warning
Facility LOG_DAEMON
Action Check the network configuration.
DDOS_PROTOCOL_VIOLATION_SET
System Log Message Protocol protocol-name is violated at source-name for repeat-count times, started at
time-first-detected
Description The ddos system detected that the incoming traffic for a control protocol exceeded the
configured bandwidth. This could be a ddos attack.
Severity warning
Facility LOG_DAEMON
Action Check the network configuration and shut down the problem source.
DDOS_RTSOCK_FAILURE
System Log Message Failed to action argument, error=error-code
Description The ddos system process (jddosd) experienced the indicated error with a routing socket.

Severity error
Facility LOG_DAEMON
DDOS_SCFD_FLOW_AGGREGATED
System Log Message Flows of protocol protocol-name on slot source-name are aggregated to level level(s)
Description The ddos system has aggregated flows to a coarse granularity.
Severity warning
Facility LOG_DAEMON
Action check network configuration
DDOS_SCFD_FLOW_CLEARED
System Log Message A flow of protocol protocol-name on source-name with source addr source-address is
cleared. Found at time-first-detected, last observed time-last-detected.
Description The ddos system cleared a monitored control flow. Its arriving rate may still be above its
bandwidth.
Severity warning
Facility LOG_DAEMON
Action check logs and the flow may be discovered again
DDOS_SCFD_FLOW_DEAGGREGATED
System Log Message Flows of protocol protocol-name on slot source-name are deaggregated to level level(s)
Description The ddos system has deaggregated flows to a finer granularity.
Severity warning
Facility LOG_DAEMON
Action check network configuration

Chapter 29: DDOS System Log Messages
DDOS_SCFD_FLOW_FOUND
System Log Message A new flow of protocol protocol-name on source-name with source addr source-address
is found at time-first-detected
Description The ddos system detected a control flow that exceeded its allowed bandwidth. It could
be a ddos attack flow.
Severity warning
Facility LOG_DAEMON
Action check network configuration and shut down problem source
DDOS_SCFD_FLOW_RETURN_NORMAL
System Log Message A flow of protocol protocol-name on source-name with source addr source-address
returned normal and is removed from monitoring. Found at time-first-detected, last
observed at time-last-detected
Description The ddos system detected that the incoming traffic for a violated flow returned to normal
and the flow was removed from monitoring.
Severity warning
Facility LOG_DAEMON
Action check network configurtaion
DDOS_SCFD_FLOW_TIMEOUT
System Log Message A flow of protocol protocol-name on source-name with source addr source-address is
timed out. Found at time-first-detected, last observed at time-last-detected
Description The ddos system timed out a monitored control flow. Its arriving rate may still be above
its bandwidth.
Severity warning
Facility LOG_DAEMON
Action check logs and the flow may be discovered again


CHAPTER 30
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 PIC housing interface interface-name does not support flow-tap service
Description The PIC that houses the indicated interface does not support flow-tap service.
Severity error
Facility LOG_DAEMON
DFCD_GENCFG_MALLOC_FAILED
System Log Message GENCFG mem alloc failed !!!
Description The dynamic flow capture process (dfcd) could not allocate memory for gencfg message.
Severity error
Facility LOG_DAEMON

DFCD_GENCFG_WRITE_FAILED
System Log Message GENCFG write failed for Reason: error-message (error-code)
Description The dynamic flow capture process (dfcd) could not send gencfg message, for the
indicated reason.
Severity error
Facility LOG_DAEMON


DFCD_LINH_MALLOC_FAILED
System Log Message GENCFG mem alloc failed !!!
Description The dynamic flow capture process (dfcd) could not allocate memory for linh message.
Severity error
Facility LOG_DAEMON

DFCD_LI_NEXT_HOP_ADD_FAILED
System Log Message Unable to add li next hop for subscriber interface: error-message (error-code)
Description The dynamic flow capture process (dfcd) could not add a subscriber li next hop, for the
indicated reason.
Severity error
Facility LOG_DAEMON
DFCD_NEXT_HOP_ADD_FAILED
System Log Message Unable to add service next hop: error-message (error-code)
Description The dynamic flow capture process (dfcd) could not add a service next hop, for the
indicated reason.
Severity error
Facility LOG_DAEMON
DFCD_NEXT_HOP_DELETE_FAILED
System Log Message Unable to delete service next hop: error-message (error-code)
Description The dynamic flow capture process (dfcd) could not delete a service next hop, for the
indicated reason.
Severity error
Facility LOG_DAEMON

Chapter 30: DFCD System Log Messages
DFCD_SAMPLE_CLASS_ADD_FAILED
System Log Message Unable to add sample class: error-message (error-code)
Description The dynamic flow capture process (dfcd) could not add a sample class, for the indicated
reason.
Severity error
Facility LOG_DAEMON
DFCD_SAMPLE_CLASS_DELETE_FAILED
System Log Message Unable to delete sample class: error-message (error-code)
Description The dynamic flow capture process (dfcd) could not delete a sample class, for the
indicated reason.
Severity error
Facility LOG_DAEMON


CHAPTER 31
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 Memory allocation failed during initialization for configuration load
Description The firewall process (dfwd) could not dynamically allocate memory in preparation for
loading a configuration.
Severity error
Facility LOG_DAEMON
Cause A software bug caused a memory leak, or the routing platform had insufficient memory.
DFWD_PARSE_FILTER_EMERGENCY
System Log Message dfwd encountered errors while parsing filter index file
Description The firewall process (dfwd) encountered an unhandled internal state while parsing a
filter index file.
Severity error
Facility LOG_DAEMON
Cause There might be a bug in the parser.
DFWD_PARSE_STATE_EMERGENCY
System Log Message dfwd encountered unhandled state while parsing interface

Description The firewall process (dfwd) encountered an unhandled internal state while parsing an
interface.
Severity emergency
Facility LOG_DAEMON
Cause There might be a bug in the parser.
DFWD_POLICER_LIMIT_EXCEEDED
System Log Message Number of interface policers configured is exceeding maximum allowed total-count.
Description The firewall process (dfwd) detected that number of interface policers configured is
exceeding maximum allowed.
Severity error
Facility LOG_DAEMON
Action Reduce the number of interface policers to within allowed limit.

CHAPTER 32
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 bind() to port port failed: error-message
Description The Dynamic Host Configuration Protocol server process (dhcpd) received the indicated
error when it tried to bind a socket to the indicated local port.
Severity error
Facility LOG_AUTH
DHCPD_DEGRADED_MODE
System Log Message Running in degraded mode because of reason: error-message
Description The Dynamic Host Configuration Protocol server process (dhcpd) began running in
degraded mode because the indicated unrecoverable error occurred.
Severity error
Facility LOG_AUTH
Cause There might be a problem with the lease cache directory used to store persistent lease
information.
DHCPD_MEMORY_ALLOCATION_FAILURE
System Log Message Unable to allocate memory for object-name: error-message

Description The Dynamic Host Configuration Protocol server process (dhcpd) could not allocate
memory from the heap for the indicated object.
Severity error
Facility LOG_AUTH
DHCPD_OPTION_HOST_NAME
System Log Message option value
Description The Dynamic Host Configuration Protocol server process (dhcpd) received a DHCPACK
packet with the Host Name option set.
Severity info
Facility LOG_AUTH
DHCPD_OPTION_LOG_SERVER
packet with the Log Server option set.
Severity info
Facility LOG_AUTH
DHCPD_OPTION_NTP_SERVER
packet with the NTP Server option set.
Severity info
Facility LOG_AUTH
DHCPD_OVERLAY_CONFIG_FAILURE
System Log Message Unable to open overlay configuration: error-message
Description The Dynamic Host Configuration Protocol server process (dhcpd) could not open an
overlay configuration file for parsing.

Chapter 32: DHCPD System Log Messages
Severity error
Facility LOG_AUTH
DHCPD_OVERLAY_PARSE_FAILURE
System Log Message Unable to parse overlay configuration because of count syntax errors
Description The Dynamic Host Configuration Protocol server process (dhcpd) could not parse its
overlay configuration because the configuration contained the indicated number of syntax
errors.
Severity error
Facility LOG_AUTH
DHCPD_RECVMSG_FAILURE
System Log Message Exiting due to too many recvmsg() failures
Description The Dynamic Host Configuration Protocol server process (dhcpd) could not receive data
from the network, which it needs to do during normal operation.
Severity error
Facility LOG_AUTH
DHCPD_RTSOCK_FAILURE
System Log Message Error with rtsock: error-message
Description The Dynamic Host Configuration Protocol server process (dhcpd) experienced the
indicated error with a routing socket.
Severity info
Facility LOG_AUTH

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
Description 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.
Severity error
Facility LOG_AUTH
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
Description 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.
Severity error
Facility LOG_AUTH
DHCPD_SETSOCKOPT_FAILURE
System Log Message setsockopt(socket-option) failed: error-message
Description The Dynamic Host Configuration Protocol server process (dhcpd) could not set the
indicated socket option.
Severity error
Facility LOG_AUTH
DHCPD_SOCKET_FAILURE
System Log Message socket(arguments) failed: error-message

Chapter 32: DHCPD System Log Messages
Description The Dynamic Host Configuration Protocol server process (dhcpd) could not create a
socket.
Severity error
Facility LOG_AUTH


CHAPTER 33
DIAM System Log Messages
This chapter describes messages with the DIAM prefix.
DIAM_PEER_CONN_STATE_CHANGE
System Log Message Diameter Peer diameter-peer diameter-peer-conn-state on SPIC spic-name
Description This notification signifies that the diameter connection state to specified diameter peer
on the specified Session PIC has changed from UP to DOWN/FAIL or vice-versa.
Severity info
Facility LOG_DAEMON
DIAM_PEER_OUTQ_HIGH_WATERMARK
System Log Message Diameter Peer [diameter-peer] Outgoing queue on SPIC [spic-name] hit HIGH water
mark percent of [diameter-peer-outq-high-wmark]
Description This notification signifies that the outgoing queue size of the specified diameter peer has
reached higher watermark on the specified Session PIC.
Severity info
Facility LOG_DAEMON
DIAM_PEER_OUTQ_LOW_WATERMARK
System Log Message Diameter Peer [diameter-peer] Outgoing queue on SPIC [spic-name] hit LOW water mark
percent of [diameter-peer-outq-low-wmark]
Description This notification signifies that the outgoing queue size of the specified diameter peer has
reached Lower watermark on the specified Session PIC.
Severity info
Facility LOG_DAEMON

DIAM_PROFILE_STATE_CHANGE
System Log Message Diameter Application Profile [diameter-app-profile] is [diameter-app-profile-state]
Description This notification signifies that the specified diameter profile has changed state from UP
to DOWN or vice-versa.
Severity info
Facility LOG_DAEMON
DIAM_SPIC_UNAVAILABLE
System Log Message SPIC [spic-name] which was assigned Diameter Netowrk Element
[diameter-network-element] is not available
Description This notification signifies that the specified Session pic which was assigned a Diameter
Netowork Element did not respond within 300 seconds.
Severity info
Facility LOG_DAEMON
DIAM_TARGET_STATE_CHANGE
System Log Message Diameter target [diameter-target] is [diameter-target-state]
Description This notification signifies that the specified diameter target has changed state from UP
to DOWN or vice-versa.
Severity info
Facility LOG_DAEMON

CHAPTER 34
DOT1XD System Log Messages
This chapter describes messages with the DOT1XD prefix. They are generated by the
authentication processes such as 802.1X, MAC RADIUS, or captive portal, which control
access to a network through a Juniper Networks EX Series Ethernet Switch.
DOT1XD_AUTH_SESSION_DELETED
System Log Message user-type User username session with MacAddress mac-addresse interface interface-name
vlan vlan-name deleted
Description Authenticated session has been deleted.
Severity info
Facility LOG_DAEMON
DOT1XD_MKA_FAIL_ACTION_USER_ALLOWED
System Log Message user-type User username MacAddress mac-addresse on macsec best effort interface
interface-name allowed without macsec
Description Dot1x user access is allowed as macsec is not must-secure, though we cannot establish
a macsec session with the authenticated user
Severity info
Facility LOG_DAEMON
DOT1XD_MKA_FAIL_ACTION_USER_PROHIBITED
System Log Message user-type User username MacAddress mac-addresse on macsec must interface
interface-name denied, cannot establish macsec session
Description Dot1x user access is denied as macsec is must-secure and we cannot establish a macsec
session with the authenticated user
Severity info

Facility LOG_DAEMON
DOT1XD_MKA_SECURE_CHANNEL_CREATED
System Log Message Macsec receive secure channel created for mac-addresse on interface interface-name
Description Macsec enabled secure channel is created for a receiver.
Severity info
Facility LOG_DAEMON
DOT1XD_MKA_SECURE_CHANNEL_DELETED
System Log Message Macsec receive secure channel deleted for mac-addresse on interface interface-name
Description Macsec enabled secure channel is deleted for a receiver.
Severity info
Facility LOG_DAEMON
DOT1XD_RCVD_EAPLOGOF_ATHNTCTNG
System Log Message user-type User username EAP Logoff received from MacAddress mac-addresse interface
interface-name vlan vlan-name while authenticating
Description EAP Log off received while authenticating.
Severity info
Facility LOG_DAEMON
DOT1XD_RCVD_EAPLOGOF_ATHNTICTD
System Log Message user-type User username EAP Logoff received or MKA timeout for MacAddress
mac-addresse interface interface-name vlan vlan-name while authenticated
Description EAP Log off received while authenticated.
Severity info
Facility LOG_DAEMON
DOT1XD_RCVD_EAPLOGOF_CONNECTNG
System Log Message user-type User username EAP Logoff received from MacAddress mac-addresse interface
interface-name vlan vlan-name while connecting
Description EAP Log off received while connecting.

Chapter 34: DOT1XD System Log Messages
Severity info
Facility LOG_DAEMON
DOT1XD_USR_ACCESS_DENIED
System Log Message user-type User username authentication failed in MacAddress mac-addresse interface
interface-name vlan vlan-name
Description User is unauthenticated and denied access on port.
Severity info
Facility LOG_DAEMON
DOT1XD_USR_ATHNTICTD_GST_VLAN
System Log Message user-type User username non responsive host mac-addresse on interface interface-name
moved to guest vlan vlan-name
Description User has been authenticated on guest vlan if it is configured and authentication using
mac-radius for a non-responsive client failed.
Severity info
Facility LOG_DAEMON
DOT1XD_USR_AUTHENTICATED
System Log Message Custom_log user-type User username logged in MacAddress mac-addresse interface
interface-name vlan vlan-name
Description User is authenticated and allowed access on port.
Severity info
Facility LOG_DAEMON
DOT1XD_USR_ON_SRVR_FAIL_VLAN
System Log Message user-type User username logged in MacAddress mac-addresse interface interface-name
authenticated on server fail vlan vlan-name
Description User gets authenticated on server fail vlan if it is configured and when radius server is not
reachable.
Severity info

Facility LOG_DAEMON
DOT1XD_USR_ON_SRVR_REJECT_VLAN
System Log Message user-type User username logged in MacAddress mac-addresse interface interface-name
authenticated on server reject vlan vlan-name
Description User gets authenticated on server reject vlan if it is configured and when radius server
rejects the access request.
Severity info
Facility LOG_DAEMON
DOT1XD_USR_SESSION_DISCONNECTED
vlan vlan-name disconnected
Description User session has been disconnected.
Severity info
Facility LOG_DAEMON
DOT1XD_USR_SESSION_HELD
vlan vlan-name is held
Description User session has been held and dot1x shall retry authentication after held timer expires.
Severity info
Facility LOG_DAEMON
DOT1XD_USR_UNATHNTCTD_CLI_CLRD
System Log Message Clearing the interface interface-name due to user action
Description User is unauthenticated due to cli clearing.
Severity info
Facility LOG_DAEMON

CHAPTER 35
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 Unable to connect to fwauthd on socket file-descriptor: error-message
Description The connection manager authentication process could not connect to fwauthd daemon
on the indicated socket.
Severity error
Facility LOG_AUTH
DYNAMIC_VPN_AUTH_FAIL
System Log Message Username/password and token are username
Description The connection manager authentication process was unable to authenticate the indicated
user/token
Severity error
Facility LOG_AUTH
DYNAMIC_VPN_AUTH_INVALID
System Log Message type username is invalid
Description The connection manager authentication failed due to invalid user/token

Severity error
Facility LOG_AUTH
DYNAMIC_VPN_AUTH_MUL_CONN
System Log Message Connection exists for type username at client-name client-id
Description Connection already existed for this user
Severity error
Facility LOG_AUTH
DYNAMIC_VPN_AUTH_NO_CONFIG
System Log Message Authentication failed for type username due to unavailable client config
Description The connection manager authentication process was unable to obtain client config for
the indicated user/token
Severity error
Facility LOG_AUTH
DYNAMIC_VPN_AUTH_NO_LICENSE
System Log Message Authentication failed for type username due to unavailable license
Description The connection manager authentication process was unable to obtain license for the
indicated user/token
Severity error
Facility LOG_AUTH
DYNAMIC_VPN_AUTH_OK
System Log Message type username with client-name client-id authenticated successfully.
Description The connection manager authentication process was able to authenticate the indicated
user/token successfully
Severity notice
Facility LOG_AUTH
DYNAMIC_VPN_CLIENT_CONFIG_WRITE
System Log Message Client VPN config is saved in file filename for user username

Chapter 35: DYNAMIC System Log Messages
Description Connection manager writes client VPN config to file before sending to client.
Severity notice
Facility LOG_AUTH
DYNAMIC_VPN_CONN_DEL_NOTIFY
System Log Message Connection manager receives SA deleted notification for ike-id gateway-id
Description Connection manager receives SA deleted notification from IKED.
Severity notice
Facility LOG_AUTH
DYNAMIC_VPN_CONN_DEL_REQUEST
System Log Message Connection manager receives delete request from the client for user username ike-id
gateway-id
Description Connection manager receives connection delete request from the client.
Severity notice
Facility LOG_AUTH
DYNAMIC_VPN_CONN_EST_NOTIFY
System Log Message Connection manager receives SA established notification for ike-id gateway-id
Description Connection manager receives SA established notification from IKED.
Severity notice
Facility LOG_AUTH
DYNAMIC_VPN_INIT_SUCCESSFUL
System Log Message Connection manager initialization succeeded.
Description Connection manager is initialized successfully.
Severity notice
Facility LOG_AUTH

DYNAMIC_VPN_LICENSE_ASSIGNED
System Log Message Dynamic VPN license granted, license limit free, count overdrafted, current-value used
Description The Access Manager client has successfully acquired a license and is permitted to connect
to the device.
Severity info
DYNAMIC_VPN_LICENSE_CHECK_FAILED
System Log Message Dynamic VPN license check failed for user username
Description No Access Manager license is available at the moment.
Severity error
Facility LOG_AUTH
DYNAMIC_VPN_LICENSE_CHECK_OK
System Log Message Dynamic VPN license check succeed for user username
Description Preliminary check on Access Manager license is successful for the given user.
Severity notice
Facility LOG_AUTH
DYNAMIC_VPN_LICENSE_EXHAUSTED
System Log Message Dynamic VPN license denied, no available license
Description The device is out of Access Manager licenses. Connection request from the Access
Manager client is denied.
Severity error
DYNAMIC_VPN_LICENSE_FREED
System Log Message Dynamic VPN license returned, license limit free, count overdrafted, current-value used
Description The Access Manager client has disconnected and returned its license.

Chapter 35: DYNAMIC System Log Messages
Severity info
DYNAMIC_VPN_LICENSE_FREE_FAILED
System Log Message Server failed to free an Access Manager for username
Description The Access Manager client attempt to return a license has failed.
Severity error
Facility LOG_AUTH
DYNAMIC_VPN_LICENSE_FREE_OK
System Log Message Server successfully freed an Access Manager license for username
Description The Access Manager client successfully returned a license.
Severity notice
Facility LOG_AUTH
DYNAMIC_VPN_LICENSE_GET_FAILED
System Log Message Server failed to get an Access Manager license for username
Description No Access Manager license is available at the moment.
Severity error
Facility LOG_AUTH
DYNAMIC_VPN_LICENSE_GET_OK
System Log Message Server successfully got an Access Manager license for username
Description The Access Manager client successfully obtained a license.
Severity notice
Facility LOG_AUTH
DYNAMIC_VPN_LICENSE_INSTALLED
System Log Message Dynamic VPN license name installed, license limit total, count free
Description An Access Manager license was installed successfully on this device.

Severity info
DYNAMIC_VPN_LICENSE_REQUIRED
System Log Message Dynamic VPN license denied, no license installed
Description Requested operation requires an Access Manager license to be installed on this device.
Severity error
DYNAMIC_VPN_LICENSE_UNINSTALLED
System Log Message Dynamic VPN license name deleted, license limit total, count free
Description An Access Manager license is removed from this device.
Severity info

CHAPTER 36
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 interface-name: bpdu-block disabled port
Description This condition occurs when bpdu-block error condition is detected.
Severity alert
Facility LOG_DAEMON
ESWD_BPDU_BLOCK_ERROR_ENABLED
System Log Message interface-name: bpdu-block enabled port
Description This condition occurs when bpdu-block error condition is cleared.
Severity alert
Facility LOG_DAEMON
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
Description The ARP request/response receieved on this port cannot be linked to any of the IPs
assigned by DHCP.
Severity alert
Facility LOG_DAEMON

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
Description DHCP server packets are being received on a port which was not meant to receive server
traffic.
Severity alert
Facility LOG_DAEMON
ESWD_GLOBAL_MAC_LIMIT_ERROR
System Log Message error-message.
Description ESWD currently has learnt maximum number of MAC and ESWD does not allow new
MAC to be learnt in this condition.
Severity warning
Facility LOG_DAEMON
Cause ESWD reaches global mac learn limit
ESWD_INVALID_MAC_ADDRESS
System Log Message Invalid MAC address mac-addresse received on interface-name
Description Received a MAC address that is not in the configured valid MAC addresses for this
interface.
Severity alert
Facility LOG_DAEMON
Cause MAC address recieved is not configured as a valid MAC address for this interface.
ESWD_LEARNT_FDB_MEMORY_ERROR
System Log Message FDB entry for error-message creation failed as ESWD is running low on memory.
Description ESWD is currently running low on resources and ESWD does not allow MAC to be learnt
in this condition.
Severity error

Chapter 36: ESWD System Log Messages
Facility LOG_DAEMON
Cause It is possible that the ESWD lacked the resources to fulfill the request.
ESWD_MAC_LIMIT_ALERT
System Log Message MAC limit is less than the current number of MACs for the interface. You might want to
remove some of the MACs for interface interface-name using `clear ethernet-switching
table' command
Description Log message alerting user to clear the MACs because the number of MACs learned on
an interface exceeds the mac limit
Severity alert
Facility LOG_DAEMON
ESWD_MAC_LIMIT_BLOCK
System Log Message MAC limit (limit) exceeded at interface-name: shutting down the interface
Description Interface was blocked because the number of MAC addresses learned on an interface
has exceeded the user configured limit.
Severity alert
Facility LOG_DAEMON
Cause More learning requests were received by the system than the user configured.
ESWD_MAC_LIMIT_DROP
System Log Message MAC limit (limit) exceeded at interface-name: dropping the packet from src mac-addresse
Description Learning request was dropped because the number of MAC addresses learned on an
interface has reached the user configured limit.
Severity alert
Facility LOG_DAEMON
ESWD_MAC_LIMIT_EXCEEDED
System Log Message MAC limit (limit) exceeded at interface-name
Description Number of MAC addresses learned on an interface has exceeded the user configured
limit.

Severity alert
Facility LOG_DAEMON
ESWD_MAC_MOVE_LIMIT_BLOCK
System Log Message mac-move-type (limit) exceeded at vlan-name for MAC address mac-addresse; shutting
down interface interface-name
Description 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.
Severity alert
Facility LOG_DAEMON
Cause A MAC address moved to a different interface more times per second than the user
configured.
ESWD_MAC_MOVE_LIMIT_DROP
System Log Message mac-move-type (limit) exceeded at vlan-name for MAC address mac-addresse; dropping
the packet on interface interface-name
Description Learning request was dropped because the number of times a MAC address moved to
a different interface exceeded the user-configured limit.
Severity alert
Facility LOG_DAEMON
configured.
ESWD_MAC_MOVE_LIMIT_EXCEEDED
System Log Message mac-move-type (limit) exceeded at vlan-name for MAC address mac-addresse on interface
interface-name
Description The number of times that a MAC address moved to a different interface within a VLAN
exceeded the user-configured limit.
Severity alert
Facility LOG_DAEMON

configured.
ESWD_MAC_SMAC_BRIDGE_MAC_IDENTICAL
System Log Message Bridge Address argument: mac-addresse SMAC is equal to bridge mac hence don't learn
Description Source mac being same as bridge mac address (mac2me mac) shall not be added to
fdb table.
Severity error
Facility LOG_DAEMON
Cause Dynamic learnt mac or Static mac when learnt or cofigured similar to that of bridge mac
address (mac2me mac).
ESWD_MIRROR_ERROR
System Log Message Unable to establish mirror connection between Routing Engines: error-message
Description 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.
Severity warning
Facility LOG_DAEMON
Cause The master and standby Routing Engines are running incompatable versions of the Junos
OS.
Action Update the Junos OS on the master Routing Engine, standby Routing Engine, or both, so
that they are running compatible versions.
ESWD_MIRROR_VERSION_MISMATCH
System Log Message Versions of mirror software on Routing Engines are incompatible: error-message
Description 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.
Severity warning
Facility LOG_DAEMON

Cause The master and standby Routing Engines are running incompatable versions of the Junos
OS.
Action Update the Junos OS on the master Routing Engine, standby Routing Engine, or both, so
that they are running compatible versions.
ESWD_MODULE_SHUTDOWN_FAILURE
System Log Message ESWD: error-message Module shutdown failed
Description While deleting the instance of logical-switch, RST/MST Module shutdown failed.
Severity error
Facility LOG_DAEMON
ESWD_NDI_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
Description The Neighbor discovery request/response receieved on this port cannot be linked to any
of the IPs assigned by DHCPv6.
Severity alert
Facility LOG_DAEMON
ESWD_OUT_OF_LOW_MEMORY
Description ESWD is out of memory overload condition and ESWD can learn new macs now
Severity info
Facility LOG_DAEMON
ESWD_PPM_READ_ERROR
Description The ethernet bridging process (eswd) could not read a message available on the read
pipe from the periodic packet management process (ppmd).

Severity error
Facility LOG_DAEMON
ESWD_PPM_WRITE_ERROR
Description The ethernet bridging process (eswd) could not write a message on the pipe to the
periodic packet management process (ppmd).
Severity error
Facility LOG_DAEMON
ESWD_STATIC_FDB_MEMORY_WARNING
Description ESWD is currently running low on resources and further creation of FDB static entry may
fail.
Severity warning
Facility LOG_DAEMON
Cause It is possible that the ESWD lacked the resources to fulfill the request.
ESWD_STP_BASE_MAC_ERROR
System Log Message Failed to get error-message. All modules will remain disabled.
Description This condition occurs when STP cannot derive the base MAC address of the system.
Severity alert
Facility LOG_DAEMON

ESWD_STP_LOOP_PROTECT_CLEARED
System Log Message interface-name: loop protect cleared for instance instance-id

Description This condition occurs when STP loop protect condition is cleared.
Severity alert
Facility LOG_DAEMON
ESWD_STP_LOOP_PROTECT_IN_EFFECT
System Log Message interface-name: loop protect in effect for instance instance-id
Description This condition occurs when STP loop protect condition occurs.
Severity alert
Facility LOG_DAEMON
ESWD_STP_ROOT_PROTECT_CLEARED
System Log Message interface-name: root protect cleared for instance instance-id
Description This condition occurs when STP root protect condition is cleared.
Severity alert
Facility LOG_DAEMON
ESWD_STP_ROOT_PROTECT_IN_EFFECT
System Log Message interface-name: root protect in effect for instance instance-id
Description This condition occurs when STP root protect condition occurs.
Severity alert
Facility LOG_DAEMON
ESWD_STP_STATE_CHANGE_INFO
System Log Message context-name state for interface interface-name context id instance-id changed from
old-state to new-state
Description Message is logged to the syslog server when ever there is a state change.
Severity info
Facility LOG_DAEMON

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
Description Log message to alert the user to the bandwidth setting limits.
Severity alert
Facility LOG_DAEMON
ESWD_ST_CTL_ERROR_DISABLED
System Log Message interface-name: storm control disabled port
Description This condition occurs when storm control error condition is detected.
Severity alert
Facility LOG_DAEMON
ESWD_ST_CTL_ERROR_ENABLED
System Log Message interface-name: storm control enabled port
Description This condition occurs when storm-control error condition is cleared.
Severity alert
Facility LOG_DAEMON
ESWD_ST_CTL_ERROR_IN_EFFECT
System Log Message interface-name: storm control in effect on the port
Description This condition occurs when storm control error condition is detected.
Severity alert
Facility LOG_DAEMON
ESWD_ST_CTL_INFO
System Log Message storm control is enabled for interface interface-name
Description Log message to alert the user to the storm control setting.
Severity alert

Facility LOG_DAEMON
ESWD_VLAN_MAC_LIMIT_EXCEEDED
System Log Message vlan vlan-name mac mac-addresse (tag vlan-id), vlan limit exceeded
Description Number of MAC addresses learned on a vlan has exceeded the user configured limit.
Severity alert
Facility LOG_DAEMON
Cause More learning request were received by the system than the user configured.
ESWD_VMEMBER_MAC_LIMIT_DROP
System Log Message vlan vlan-name mac mac-addresse (tag vlan-id) interface interface-name, per port per
vlan limit exceeded
Description Number of MAC addresses learned on a per port per vlan has exceeded the user configured
limit.
Severity alert
Facility LOG_DAEMON
Cause More learning request were received by the system than the user configured.

CHAPTER 37
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 Unable to send acknowledgment: error-message
Description 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.
Severity error
Facility LOG_DAEMON
EVENTD_ALARM_CLEAR
System Log Message User username cleared alarm: "timestamp: message"
Description An administrator has acknowledged and cleared a security alarm.
Severity notice
Facility LOG_DAEMON
EVENTD_ALARM_FILE
System Log Message Could not open the eventd alarm file 'filename' for writing
Description The event processing process (eventd) could not open the alarm statistics file for writing.
Severity notice
Facility LOG_DAEMON

EVENTD_AUDIT_DISABLED
System Log Message Security audit alarm module "module" disabled
Description An administrator disabled a security audit module.
Severity notice
Facility LOG_DAEMON
EVENTD_AUDIT_ENABLED
System Log Message Security audit alarm module "module" enabled
Description An administrator enabled a security audit module.
Severity notice
Facility LOG_DAEMON
EVENTD_AUDIT_SHOW
System Log Message User username viewed security audit log with arguments:arguments
Description An administrator viewed the security audit log.
Severity notice
Facility LOG_DAEMON
EVENTD_COMMAND_SUBSTITUTE_ERROR
System Log Message Variable substitution failed for command 'command'
Description 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.
Severity error
Facility LOG_DAEMON

Chapter 37: EVENTD System Log Messages
EVENTD_CONFIG_CHANGE_FAILED
System Log Message Configuration change failed: error-message while executing policy policy-name with user
username privileges
Description The event processing process (eventd) could not execute the commands to change
configuration data.
Severity error
Facility LOG_DAEMON
EVENTD_CONFIG_CHANGE_SUCCESS
System Log Message Configuration change successful: while executing policy policy-name with user username
privileges
Description The event processing process (eventd) successfully executed the commands to change
configuration data.
Severity error
Facility LOG_DAEMON
EVENTD_ESCRIPT_EXECUTION
System Log Message Trying to execute the script 'filename' from 'directory-name'
Description The event process (eventd) executing the configured event script from the specified
location.
Severity info
Facility LOG_DAEMON
EVENTD_ESCRIPT_NOT_CONFIGURED
System Log Message Trying to execute the non configured script 'filename' from 'directory-name'
Description The event process (eventd) executing the non configured event script from the specified
location.
Severity info
Facility LOG_DAEMON
EVENTD_EVENT_SEND_FAILED
System Log Message Unable to send event notification: error-message

Description 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
Severity error
Facility LOG_DAEMON

EVENTD_FORK_ERR
Description The event processing process (eventd) could not create a child process for executing
policies.
Severity error
Facility LOG_DAEMON

EVENTD_JAIL_SOCKET_FAILURE
System Log Message Could not create jail socket: error-message
Description The event processing process (eventd) could not create a jail socket.
Severity error
Facility LOG_DAEMON
EVENTD_PARSE_CONTROL_INFO_FAILED
System Log Message error-message: error in parsing control info
Description Control information received with remote syslog messages are not parsed successfully.
Severity error
Facility LOG_DAEMON
EVENTD_PIPE_CREATION_FAILED
System Log Message Unable to create pipe: error-message

Description The event processing process (eventd) could not create a pipe for interprocess
communication.
Severity error
Facility LOG_DAEMON
EVENTD_POLICY_ACTION_FAILED
System Log Message Unable to execute 'action' action in policy policy-name
Description The event processing process (eventd) could not perform the indicated action, which is
specified by the indicated policy.
Severity error
Facility LOG_DAEMON
EVENTD_POLICY_LIMIT_EXCEEDED
System Log Message Unable to execute policy 'policy-name' because current number of policies (count)
exceeds system limit (limit)
Description 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.
Severity warning
Facility LOG_DAEMON
EVENTD_POLICY_UPLOAD_FAILED
System Log Message Unable to upload file 'filename' to destination 'destination-name' for policy 'policy-name'
Description The event processing process (eventd) could not upload the indicated file to the indicated
destination.
Severity error
Facility LOG_DAEMON
EVENTD_POPEN_FAIL
System Log Message Error error-code in invoking command 'command'
Description A call to the popen() function failed when the event processing process (eventd) invoked
the indicated command.

Severity error
Facility LOG_DAEMON
EVENTD_READ_ERROR
System Log Message recvmsg() failed: error-message
Description The event processing process (eventd) could not read an event sent to it, for the indicated
reason.
Severity error
Facility LOG_DAEMON
EVENTD_REGEXP_INVALID
System Log Message Invalid regular expression 'regular-expression' provided for attribute value
Description 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.
Severity error
Facility LOG_DAEMON
EVENTD_REG_VERSION_MISMATCH
System Log Message Registration version expected-value did not match expected version (received-value)
Description 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.
Severity error
Facility LOG_DAEMON
EVENTD_ROTATE_COMMAND_FAILED
System Log Message Command 'command' failed during rotation of file 'filename': error-message
Description The event processing process (eventd) invoked the indicated command while attempting
to rotate the indicated file. The command failed.
Severity error
Facility LOG_DAEMON

EVENTD_ROTATE_FORK_EXCEEDED
Description 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.
Severity error
Facility LOG_DAEMON
EVENTD_ROTATE_FORK_FAILED
Description The event processing process (eventd) could not create a child process for rotating files,
Severity error
Facility LOG_DAEMON
EVENTD_SCRIPT_CHECKSUM_MISMATCH
System Log Message checksum checksum value does not match for script filename
Description 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
Severity error
Facility LOG_DAEMON
EVENTD_SECURITY_LOG_CLEAR
System Log Message User username cleared count security log(s)
Description An administrator has cleared one or more security audit logs.
Severity notice
Facility LOG_DAEMON
EVENTD_SET_PROCESS_PRIV_FAILED
System Log Message Unable to set process privilege level to that of user 'username': error-message
Description 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.
Severity error
Facility LOG_DAEMON
EVENTD_SET_TIMER_FAILED
System Log Message evSetTimer failed: error-message
Description 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.
Severity error
Facility LOG_DAEMON
EVENTD_SYSLOG_FWD_FAILED
System Log Message Unable to forward syslog message to PSD (psd-id), errorno: error-code
Description The event processing process (eventd) encountered a system error when forwarding a
syslog message to indicated protected system domain (PSD).
Severity error
Facility LOG_DAEMON
EVENTD_TEST_ALARM
System Log Message This is test alarm argument1 of argument2
Description This is an alarm test for the eventd alarm infrastructure.
Severity notice
Facility LOG_DAEMON
EVENTD_TRANSFER_COMMAND_FAILED
System Log Message Command 'error-code' failed during transfer of file 'command': filename
Description The event processing process (eventd) invoked the indicated command while attempting
to transfer the indicated file. The command failed.
Severity error

Facility LOG_DAEMON
EVENTD_TRANSFER_FORK_EXCEEDED
Description 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.
Severity error
Facility LOG_DAEMON
EVENTD_TRANSFER_FORK_FAILED
Description The event processing process (eventd) could not create a child process for transferring
files, for the indicated reason.
Severity error
Facility LOG_DAEMON
EVENTD_VERSION_MISMATCH
System Log Message Event version expected-value did not match expected version (received-value)
Description 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.
Severity error
Facility LOG_DAEMON

EVENTD_XML_FILENAME_INVALID
System Log Message XML syntax of output filename was invalid
Description 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.

Severity error
Facility LOG_DAEMON

CHAPTER 38
FABOAMD System Log Messages
This chapter describes messages with the FABOAMD prefix on the Juniper Networks
QFabric QFX3000 switch. They are generated by the QFabric switch Operations,
Administration, and Maintenance (OAM) process (faboamd), which enables OAM
operations (such as a fabric ping) across different devices in the QFabric switch.
FABOAMD_DEBUGGING
System Log Message reason: index error-message
Description A system call made by the Fabric OAM (faboamd) failed.
Severity error
Facility LOG_DAEMON
Cause It is possible that the kernel did not have enough resources to fulfill the request.


CHAPTER 39
FC System Log Messages
This chapter describes messages with the FC prefix. They are generated by the Fibre
Channel process (fcd) which connects servers to disks and tape devices in a storage area
network.
FC_FABRIC_CREATED
System Log Message Fabric fc-fabric-name fabric-id fc-fabric-id fabric-type fc-fabric-type created
Description Fibre channel fabric is created.
Severity info
Facility LOG_DAEMON
FC_FABRIC_DELETED
System Log Message Fabric fc-fabric-name fabric-id fc-fabric-id fabric-type fc-fabric-type deleted
Description Fibre channel fabric is deleted.
Severity info
Facility LOG_DAEMON
FC_FABRIC_WWN_ASSIGNED
System Log Message Fabric fc-fabric-name fabric-wwn wwn is set
Description Fabric_WWN has been set for a fibre channel fabric.
Severity info
Facility LOG_DAEMON
FC_FABRIC_WWN_CLEARED
System Log Message Fabric fc-fabric-name fabric-wwn is cleared

Description Fabric_WWN is cleared for a fibre channel fabric.
Severity info
Facility LOG_DAEMON
FC_FLOGI_VN_PORT_LOGIN_FAILED
System Log Message Fabric fc-fabric-name interface interface-name enode-mac enode-mac-address wwn
wwn - reason
Description FIP FLOGI/FDISC from the end node has failed.
Severity error
Facility LOG_DAEMON
FC_LOGICAL_INTERFACE_CREATED
System Log Message Fabric fc-fabric-name interface interface-name created
Description Fibre channel logical interface is created.
Severity info
Facility LOG_DAEMON
FC_LOGICAL_INTERFACE_DELETED
System Log Message Fabric fc-fabric-name interface interface-name deleted
Description Fibre channel logical interface is deleted.
Severity info
Facility LOG_DAEMON
FC_LOGICAL_INTERFACE_ISOLATED
System Log Message Fabric fc-fabric-name interface interface-name reason - reason
Description Fibre channel logical interface is isolated.
Severity error
Facility LOG_DAEMON
Cause Protocol error or repeated failure must have occurred.

Chapter 39: FC System Log Messages
Action Check physical connection and reason code for isolation.
Action Interface disable followed by enable might clear this problem.
FC_PROXY_NP_PORT_AVAILABLE
System Log Message Fabric fc-fabric-name NP_Port interface-name
Description NP_Port is available.
Severity info
Facility LOG_DAEMON
FC_PROXY_NP_PORT_LB_ADDED
System Log Message Fabric fc-fabric-name NP_Port interface-name added to fabric load balance list
Description NP_Port is added to the fabric load balance list.
Severity info
Facility LOG_DAEMON
FC_PROXY_NP_PORT_LB_REMOVED
System Log Message Fabric fc-fabric-name NP_Port interface-name removed from fabric load balance list
Description NP_Port is removed from the fabric load balance list.
Severity info
Facility LOG_DAEMON
FC_PROXY_NP_PORT_LOGIN_ABORTED
System Log Message Fabric fc-fabric-name NP_Port interface-name login aborted
Description Login from NP_Port has aborted.
Severity error
Facility LOG_DAEMON
Cause It is possible that the NP_Port or fibre channel switch is experiencing timeouts.
FC_PROXY_NP_PORT_LOGIN_FAILED
System Log Message Fabric fc-fabric-name NP_Port interface-name login failed - error-message

Description Login from NP_Port has failed.
Severity error
Facility LOG_DAEMON
Cause NP_Port login is rejected by the fibre channel switch.
Action Check fibre channel switch configuration.
FC_PROXY_NP_PORT_LOGOUT
System Log Message Fabric fc-fabric-name NP_Port interface-name logged out by core switch
Description NP_Port is logged out from the fabric port.
Severity info
Facility LOG_DAEMON
FC_PROXY_NP_PORT_NPIV_FAILED
System Log Message Fabric fc-fabric-name NP_Port interface-name attached fabric port does not support
NPIV
Description Fabric port on the fibre channel switch does not support NPIV.
Severity error
Facility LOG_DAEMON
FC_PROXY_NP_PORT_OFFLINE
System Log Message Fabric fc-fabric-name NP_Port interface-name is offline
Description Proxy NP_Port is down.
Severity info
Facility LOG_DAEMON
FC_PROXY_NP_PORT_ONLINE
System Log Message Fabric fc-fabric-name NP_Port interface-name fcid: fcid online
Description Login from NP_Port is completed.

Chapter 39: FC System Log Messages
Severity info
Facility LOG_DAEMON
FC_PROXY_NP_PORT_RESTORE_FAILED
System Log Message Fabric fc-fabric-name NP_Port wwn:interface-name restore failed - reason
Description FCoE session restoration failed since no NP-Port was found.
Severity error
Facility LOG_DAEMON
Cause FCoE session information was incorrectly stored.
FC_PROXY_NP_PORT_UNAVAILABLE
System Log Message Fabric fc-fabric-name NP_Port interface-name
Description NP_Port is unavailable. The maximum login limit has been reached.
Severity info
Facility LOG_DAEMON
FC_PROXY_VN_PORT_LOGIN_ABORTED
System Log Message Fabric fc-fabric-name NP_Port interface-name FDISC is aborted for wwn wwn
Description FLOGI or FDISC from the VN_port (end node) is aborted.
Severity error
Facility LOG_DAEMON
Cause It is possible that the NP_Port or fibre channel switch is experiencing timeouts.
FC_PROXY_VN_PORT_LOGIN_FAILED
System Log Message Fabric fc-fabric-name NP_Port interface-name FDISC rejected for wwn wwn -
error-message
Description FLOGI or FDISC from the VN_Port (end node) has failed.
Severity error
Facility LOG_DAEMON
Cause VN_Port login is rejected by the fibre channel switch.


CHAPTER 40
FCOE System Log Messages
This chapter describes messages with the FCOE prefix. They are generated by the Fibre
network.
FCOE_LOGICAL_INTERFACE_CREATED
System Log Message Fabric fc-fabric-name interface interface-name mac mac-address created
Description Fibre channel over Ethernet logical interface is created.
Severity info
Facility LOG_DAEMON
FCOE_LOGICAL_INTERFACE_DELETED
System Log Message Fabric fc-fabric-name interface interface-name mac mac-address deleted
Description Fibre channel over Ethernet logical interface is deleted.
Severity info
Facility LOG_DAEMON
FCOE_LOGICAL_INTERFACE_ISOLATED
System Log Message Fabric fc-fabric-name interface interface-name mac mac-address reason - reason
Description Fibre channel over Ethernet logical interface is isolated.
Severity error
Facility LOG_DAEMON
Cause Protocol error or repeated failure must have occurred.
Action Check physical connection and reason code for isolation.

Action Interface disable followed by enable might clear this problem.

CHAPTER 41
FIP System Log Messages
This chapter describes messages with the FIP prefix. They are generated by the Fibre
network.
FIP_ENODE_CLEARED
System Log Message Fabric fc-fabric-name interface interface-name enode-mac enode-mac-address
Description FIP end node is removed from a fibre channel fabric.
Severity info
Facility LOG_DAEMON
FIP_ENODE_FKA_TIMER_EXPIRED
System Log Message Fabric fc-fabric-name interface interface-name enode-mac enode-mac-address keepalive
timer expired
Description FIP end node keepalive timer expired.
Severity error
Facility LOG_DAEMON
FIP_ENODE_LEARNED
System Log Message Fabric fc-fabric-name interface interface-name enode-mac enode-mac-address
Description FIP End node is learnt on a fibre channel fabric.
Severity info
Facility LOG_DAEMON
FIP_ENODE_TIMER_EXPIRED
System Log Message Timer expired for host enode-mac-addresse

Description FIP end node timer expired.
Severity error
Facility LOG_DAEMON
Cause Keep alives from end node are not seen
FIP_FCF_TIMER_EXPIRED
System Log Message Timer expired for fcf fc-fabric-mac-addresse
Description FIP FCF timer expired.
Severity error
Facility LOG_DAEMON
Cause Multicast Discovery Advertisements acting as keep alives from FCF are not seen
FIP_MAX_FCOE_FILTERS_REACHED
System Log Message Maximum number of allowed FCoE filters (slot) reached for this slot maximum-value
Description Maximum number of allowed FCoE filters reached.
Severity warning
Facility LOG_DAEMON
FIP_MAX_SESSIONS_REACHED
System Log Message Maximum number of allowed FIP sessions (slot) reached for this slot maximum-value
Description Maximum number of allowed FIP sessions reached.
Severity warning
Facility LOG_DAEMON
FIP_PROTOCOL_STARTED
System Log Message Fabric fc-fabric-name interface interface-name fcf-mac mac-address FIP protocol started
Description FIP protocol is started on an interface.
Severity info

Chapter 41: FIP System Log Messages
Facility LOG_DAEMON
FIP_PROTOCOL_STOPPED
System Log Message Fabric fc-fabric-name interface interface-name fcf-mac mac-address FIP protocol stopped
Description FIP protocol is stopped on an interface.
Severity info
Facility LOG_DAEMON
FIP_VN_PORT_FKA_TIMER_EXPIRED
wwn vn-mac vn-mac-address
Description VN_Port keepalive timer expired.
Severity error
Facility LOG_DAEMON
FIP_VN_PORT_LOGIN_FAILED
wwn - reason
Description FIP FLOGI/FDISC from the end node has failed.
Severity error
Facility LOG_DAEMON
Cause VN_Port login is rejected. Its possible that the maximum session limit has reached.
Action Check the number of sessions on the end node or the number of sessions on the gateway
FIP_VN_PORT_SESSION_CLEARED
wwn vn-mac vn-mac-address fcid fcid
Description VN_Port login session is terminated.
Severity info
Facility LOG_DAEMON

FIP_VN_PORT_SESSION_CREATED
wwn vn-mac vn-mac-address fcid fcid
Description FIP FLOGI/FDISC from the end node is completed.
Severity info
Facility LOG_DAEMON
FIP_VN_PORT_TIMER_EXPIRED
System Log Message Timer expired for session vn-mac-addresse
Description FIP Vn port timer expired.
Severity error
Facility LOG_DAEMON
Cause Keep alives from Vn port / sessions are not seen

CHAPTER 42
FIPS System Log Messages
FIPS_KNOWN_ANSWER_TEST
System Log Message username :test-name Known Answer Test: Passed
Description FIPS Known Answer Test passed.
Severity info
Facility ANY


CHAPTER 43
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 OS with enhanced services.
FLOW_APP_POLICY_VIOLATION
System Log Message Application service-name policy violation occurred threshold times within time-period
seconds
Description A log was generated when a deny or reject policy match on one application occurred
according to the configured threshold within the specified time window.
Severity notice
Facility LOG_PFE
FLOW_DSTIP_POLICY_VIOLATION
System Log Message Destination ip destination-address policy violation occurred threshold times within
time-period seconds
Description A log was generated when a deny or reject policy match on one destination IP address
occurred according to the configured threshold within the specified time window.
Severity notice
Facility LOG_PFE
FLOW_HIGH_WATERMARK_TRIGGERED
System Log Message Number of sessions current-flows exceeded the high watermark limit. Early aging triggered.
Description 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.

Severity info
Facility LOG_USER
FLOW_HIGH_WATERMARK_TRIGGERED_LS
System Log Message Lsys logical-system-name: Number of sessions current-flows exceeded the high watermark
limit. Early aging triggered.
out sessions. This message notifies you that the session high watermark has been
exceeded and aggressive aging of sessions has begun.
Severity info
Facility LOG_USER
FLOW_IP_ACTION
System Log Message Flow IP action detected attack attempt: source-address/source-port -->
destination-address/destination-port from interface interface-name, from zone
source-zone-name, action action.
Description Flow IP action notification is generated when a new connection matches security flow
IP action filter that has been setup to log or has ip-notify action.
Severity info
Facility LOG_PFE
FLOW_IP_ACTION_LS
System Log Message Lsys logical-system-name: Flow IP action detected attack
attempt:source-address/source-port --> destination-address/destination-port from
interface interface-name, from zone source-zone-name, action action.
Description Flow IP action notification is generated when a new connection matches security flow
IP action filter that has been setup to log or has ip-notify action.
Severity info
Facility LOG_PFE
FLOW_LOW_WATERMARK_TRIGGERED
System Log Message Number of sessions current-flows dropped below the low watermark limit. Early aging
stopped.

Chapter 43: FLOW System Log Messages
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.
Severity info
Facility LOG_USER
FLOW_LOW_WATERMARK_TRIGGERED_LS
System Log Message Lsys logical-system-name: Number of sessions current-flows dropped below the low
watermark limit. Early aging stopped.
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.
Severity info
Facility LOG_USER
FLOW_POLICY_VIOLATION
System Log Message Policy policy-name violation occurred threshold times within time-period seconds
Description A log was generated when a deny or reject policy match occurred according to the
configured threshold within the specified time window.
Severity notice
Facility LOG_PFE
FLOW_REASSEMBLE_FAIL
System Log Message FCB ageout before all fragments arrive, source source-address destination
destination-address ipid assembly-id
Description A log was generated when an FCB age out occurred before all fragments arrived.
Severity info
Facility LOG_PFE

FLOW_REASSEMBLE_SUCCEED
System Log Message Packet merged source source-address destination destination-address ipid assembly-id
succeed
Description A log was generated when the reassemble succeeded.
Severity info
Facility LOG_PFE
FLOW_SRCIP_POLICY_VIOLATION
System Log Message Source ip source-address policy violation occurred threshold times within time-period
seconds
Description A log was generated when a deny or reject policy match on one source IP address occurred
according to the configured threshold within the specified time window.
Severity notice
Facility LOG_PFE

CHAPTER 44
FPCLOGIN System Log Messages
FPCLOGIN_ADDRESS_GET_FAILED
System Log Message Unable to determine IP address of TGM in slot slot
Description 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.
Severity error
Facility LOG_DAEMON
FPCLOGIN_IPC_RECEIVE_FAILED
System Log Message Unable to receive IPC message from process-name
Description 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.
Severity error
Facility LOG_DAEMON
FPCLOGIN_IPC_SEND_FAILED
System Log Message Unable to send IPC message to process-name
Description 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).
Severity error
Facility LOG_DAEMON

FPCLOGIN_LOGIN_FAILED
System Log Message fpclogin failed: error-message
Description A user tried to log in to a Physical Interface Module (PIM). The attempt failed for the
indicated reason.
Severity error
Facility LOG_DAEMON
FPCLOGIN_MESSAGE_INVALID
System Log Message Message from process-name error-message
Description 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).
Severity error
Facility LOG_DAEMON
FPCLOGIN_SOCKET_OPERATION_FAILED
System Log Message Unable to complete 'error-message' operation
Description The Flexible PIC Concentrator (FPC) login process (pimlogin) could not perform the
indicated operation on a routing socket.
Severity error
Facility LOG_DAEMON

CHAPTER 45
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 PICs and other routing platform components.
FSAD_CONFIG_ERROR
System Log Message Reason: reason
Description The configuration file for the File System Access process (fsad) might contain an error.
Severity error
Facility LOG_DAEMON
FSAD_CONNTIMEDOUT
System Log Message Connection timed out to the client (connection-type, ip-address) having request type
port
Description The File System Access process (fsad) flushed all state information about the timed-out
connection.
Severity error
Facility LOG_DAEMON
FSAD_DIR_CREATE
System Log Message Failed to create directory directory-name: error-message
Description The File System Access process (fsad) could not create the indicated directory.
Severity error
Facility LOG_DAEMON

FSAD_DIR_STAT
System Log Message function-name: stat() failed for pathname pathname: reason
Description The File System Access process (fsad) received a request for a nonexistent file or directory.
Severity error
Facility LOG_DAEMON
Cause The path does not exist.
Action Make sure the path specified in the request is valid.
FSAD_FAILED
System Log Message In enclosing-function-name: function-name() returned: reason
Description An internal error occurred inside a function in the File System Access process (fsad).
Severity error
Facility LOG_DAEMON
FSAD_FILE_FAILED
System Log Message enclosing-function-name: function-name failed for file 'filename' with error message
reason
Description An internal error occurred while the File System Access process (fsad) was performing
a file operation.
Severity error
Facility LOG_DAEMON
FSAD_FILE_REMOVE
System Log Message Unable to remove file 'filename': reason

Chapter 45: FSAD System Log Messages
Description The File System Access process (fsad) could not remove the indicated file for the
indicated reason.
Severity error
Facility LOG_DAEMON
Cause The file to be removed does not exist or its permissions do not allow the operation.
Action Make sure that the file exists and that its permissions allow it to be deleted.
FSAD_FILE_RENAME
System Log Message Unable to rename file 'source-filename' to 'destination-filename': reason
Description The File System Access process (fsad) could not rename the indicated file for the
indicated reason.
Severity error
Facility LOG_DAEMON
Cause Either the source file does not exist, or one or both of the source and destination
pathnames are incorrect.
Action Make sure the source and destination paths exist and that the rename operation is
allowed.
FSAD_FILE_STAT
System Log Message function-name: stat() failed for file pathname pathname: reason
Description The File System Access process (fsad) received a request for a nonexistent file.
Severity error
Facility LOG_DAEMON
Cause The file path does not exist.
FSAD_FILE_SYNC
System Log Message Unable to sync file 'filename': reason

Description 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.
Severity error
Facility LOG_DAEMON
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)
Description The File System Access process (fsad) received a flow collector IPC message in which
the payload length was incorrect.
Severity error
Facility LOG_DAEMON
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 subtype field was incorrect.
Severity error
Facility LOG_DAEMON
FSAD_FLOWC_IPC_TYPE
System Log Message Received flowc IPC message with incorrect type: message type message-type, subtype
the type field was incorrect.
Severity error
Facility LOG_DAEMON
FSAD_FLOWC_IPC_VERSION
System Log Message Received flowc IPC message with incorrect version received-value (expected version
expected-value)

the version field was incorrect.
Severity error
Facility LOG_DAEMON
FSAD_FLOWC_SERVICE_INACTIVE
System Log Message reason
Description The File System Access process (fsad) received a request for the Flow Collector Transfer
Log Archive service, which is not currently active.
Severity error
Facility LOG_DAEMON
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
Description 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.
Severity error
Facility LOG_DAEMON
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
Description 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.
Severity error
Facility LOG_DAEMON
FSAD_FS_STAT
System Log Message statfs() failed for pathname pathname: reason
Description The File System Access process (fsad) encountered an error in getting filesystem
statistics.

Severity error
Facility LOG_DAEMON
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)
Description The File System Access process (fsad) received an IPC message in which the payload
length was incorrect.
Severity error
Facility LOG_DAEMON
FSAD_GEN_IPC_SUBTYPE
System Log Message Received IPC message with incorrect subtype: message type message-type, subtype
Description The File System Access process (fsad) received an IPC message in which the subtype
field was incorrect.
Severity error
Facility LOG_DAEMON
FSAD_GEN_IPC_TYPE
System Log Message Received IPC message with incorrect type: message type message-type, subtype
Description The File System Access process (fsad) received an IPC message in which the type field
was incorrect.
Severity error
Facility LOG_DAEMON
FSAD_GEN_IPC_VERSION
System Log Message Received generic IPC message with incorrect version received-value (expected version
expected-value)
Description The File System Access process (fsad) received an IPC message in which the version
field was incorrect.

Severity error
Facility LOG_DAEMON
FSAD_GEN_SERVICE_INACTIVE
System Log Message Received IPC message for inactive service service-name
Description The File System Access process (fsad) received an IPC message for a service that is
currently not active.
Severity error
Facility LOG_DAEMON
FSAD_GEN_SERVICE_INIT_FAILED
System Log Message Failed to initialize service service-name
Description The File System Access process (fsad) could not initialize the indicated service.
Severity error
Facility LOG_DAEMON
FSAD_MAXCONN
System Log Message Upper limit reached in fsad for handling connections
Description The File System Access process (fsad) stopped accepting new connections because it
reached an internal limit for handling connections.
Severity error
Facility LOG_DAEMON
FSAD_MEMORYALLOC_FAILED
System Log Message allocation-function-name failed in the function function-name (line-number)
Description The File System Access process (fsad) could not allocate memory. The system might
be running low on memory.
Severity error
Facility LOG_DAEMON

FSAD_NOT_ROOT
System Log Message Must be run as root
Description The user who attempted to start the File System Access process (fsad) was not the root
user.
Severity error
Facility LOG_DAEMON
FSAD_PARENT_DIRECTORY
System Log Message directory-name: invalid directory: message
Description The parent directory specified in the request for a file was not valid.
Severity error
Facility LOG_DAEMON
FSAD_PATH_IS_DIRECTORY
System Log Message File path cannot be a directory (pathname)
Description The File System Access process (fsad) received a request on a directory instead of a
regular file.
Severity error
Facility LOG_DAEMON
Cause The file path points to a directory.
Action Make sure the path points to a regular file.
FSAD_PATH_IS_NOT_DIRECTORY
System Log Message invalid path 'pathname' : not a directory : action
Description The File System Access process (fsad) received a request for a pathname that was not
a directory.
Severity error
Facility LOG_DAEMON

FSAD_PATH_IS_SPECIAL
System Log Message Not a regular file (pathname)
Description The File System Access process (fsad) received a request for a pathname that points to
a nonregular file.
Severity error
Facility LOG_DAEMON
Action Make sure the path points to a regular file.
FSAD_RECVERROR
System Log Message fsad received error message from client having request type connection-type at (ip-address,
port)
Description The File System Access process (fsad) received a packet with the indicated error message
from the other end of a connection.
Severity error
Facility LOG_DAEMON
FSAD_RENAME
System Log Message function-name: failed to rename temporary file filename to new-filename: reason
Description The File System Access process (fsad) could not rename the indicated temporary file
Severity error
Facility LOG_DAEMON
FSAD_TERMINATED_CONNECTION
System Log Message Open file 'filename' closed due to process shutdown
Description The File System Access process (fsad) terminated a connection, stored the connection's
(unwritten) data to disk, and purged it from its data structures.
Severity notice
Facility LOG_DAEMON

FSAD_TRACEOPEN_FAILED
System Log Message Open operation on trace file 'pathname' returned error error-message
Description The File System Access process (fsad) failed to open the indicated trace file.
Severity error
Facility LOG_DAEMON
FSAD_USAGE
System Log Message Incorrect usage, message
Description The File System Access process (fsad) displayed its usage statement.
Severity error
Facility LOG_DAEMON
Cause The fsad process was invoked with incorrect command-line arguments.
Action Check the usage and invoke the fsad process with the correct command-line arguments.

CHAPTER 46
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 Unknown option "option"
Description One or more options provided on the 'fud' command line were invalid. The UDP forwarding
process (fud) initialized but ignored the invalid options.
Severity error
Facility LOG_DAEMON
Action Reissue the 'fud' command with the correct options.
FUD_BAD_SERVER_ADDR_FAILURE
System Log Message Destination address of destination-address is invalid
Description One or more server addresses configured for the UDP forwarding process (fud) were
invalid.
Severity error
Facility LOG_DAEMON
Action Reconfigure the fud process with valid server addresses.
FUD_BIND_FAILURE
System Log Message bind(port port) failed: error-message
Description The UDP forwarding process (fud) received the indicated error when it tried to bind a
socket to a local address.

Severity error
Facility LOG_DAEMON
FUD_DAEMON_FAILURE
System Log Message Unable to run in the background as daemon: error-message
Description The UDP forwarding process (fud) could not create a version of itself to run in the
background as a daemon.
Severity error
Facility LOG_DAEMON
FUD_MEMORY_ALLOCATION_FAILURE
System Log Message Unable to allocate count bytes of memory: error-message
Description The UDP forwarding process (fud) could not allocate the indicated amount of memory
from the heap.
Severity error
Facility LOG_DAEMON
FUD_PERMISSION_FAILURE
System Log Message program-name must be run as root
Description The user who attempted to start the UDP forwarding process (fud) was not the root
user, so the process did not start.
Severity error
Facility LOG_DAEMON
Action Become the root user before issuing the 'fud' command.
FUD_PIDLOCK_FAILURE
System Log Message Unable to lock PID file; another program-name was running

Chapter 46: FUD System Log Messages
Description 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.
Severity error
Facility LOG_DAEMON
Cause Another instance of the fud process is running.
Action Check whether another fud process is running, and stop it if appropriate.
FUD_PIDUPDATE_FAILURE
System Log Message Unable to update PID file for program-name
Description 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
Severity error
Facility LOG_DAEMON
Cause Another instance of the fud process is running.
Action Check whether another fud process is running, and stop it if appropriate.
FUD_RECVMSG_FAILURE
System Log Message Exiting because of repeated recvmsg() failures
Description The UDP Forwarding process (fud) could not receive data from the network, which it
needs to do during normal operation.
Severity error
Facility LOG_DAEMON
FUD_RTSOCK_WRITE_FAILURE
System Log Message Unable to write to routing socket: error-message
Description The UDP Forwarding process (fud) could not write to its routing socket for the indicated
reason.

Severity error
Facility LOG_DAEMON
FUD_SENDMSG_FAILURE
System Log Message sendmsg() to destination-address port port on interface interface-name rt_inst
routing-instance failed: error-message
Description 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.
Severity error
Facility LOG_DAEMON
FUD_SENDMSG_NOINT_FAILURE
System Log Message sendmsg() to destination-address port port rt_inst routing-instance failed: error-message
Description 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.
Severity error
Facility LOG_DAEMON
FUD_SETSOCKOPT_FAILURE
System Log Message setsockopt(arguments) failed: error-message
Description The UDP Forwarding process (fud) could not set the indicated socket option.
Severity error
Facility LOG_DAEMON

Chapter 46: FUD System Log Messages
FUD_SOCKET_FAILURE
System Log Message socket(arguments) failed: error-message
Description The UDP Forwarding process (fud) could not create a socket.
Severity error
Facility LOG_DAEMON


CHAPTER 47
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 Authentication for user username at client-address was denied (long password).
Description The length of the password must not exceed 128 characters.
Severity info
Facility LOG_PFE
FWAUTH_FTP_LONG_PASSWORD_LS
System Log Message Lsys logical-system-name: Authentication for user username at client-address was denied
(long password).
Severity info
Facility LOG_PFE
FWAUTH_FTP_LONG_USERNAME
System Log Message Authentication for user username at client-address was denied (long username).
Description The length of the username must not exceed 64 characters.
Severity info
Facility LOG_PFE
FWAUTH_FTP_LONG_USERNAME_LS
(long username).

Description The length of the username must not exceed 64 characters.
Severity info
Facility LOG_PFE
FWAUTH_FTP_USER_AUTH_ACCEPTED
System Log Message User username of group group-name at client-address is accepted.
Description The authenticated user can start accessing protected resources.
Severity info
Facility LOG_PFE
FWAUTH_FTP_USER_AUTH_ACCEPTED_LS
System Log Message Lsys logical-system-name: User username of group group-name at client-address is
accepted.
Severity info
Facility LOG_PFE
FWAUTH_FTP_USER_AUTH_FAIL
System Log Message User username at client-address is rejected.
Description User authentication failed because the username or password was invalid.
Severity info
Facility LOG_PFE
FWAUTH_FTP_USER_AUTH_FAIL_LS
System Log Message Lsys logical-system-name: User username at client-address is rejected.
Severity info
Facility LOG_PFE

Chapter 47: FWAUTH System Log Messages
FWAUTH_HTTP_USER_AUTH_ACCEPTED
Severity info
Facility LOG_PFE
FWAUTH_HTTP_USER_AUTH_FAIL
Severity info
Facility LOG_PFE
FWAUTH_HTTP_USER_AUTH_FAIL_LS
Severity info
Facility LOG_PFE
FWAUTH_HTTP_USER_AUTH_OK_LS
accepted.
Severity info
Facility LOG_PFE
FWAUTH_TELNET_LONG_PASSWORD
System Log Message Authentication for user username at client-address was denied (long password).
Severity info

Facility LOG_PFE
FWAUTH_TELNET_LONG_PASSWORD_LS
(long password).
Severity info
Facility LOG_PFE
FWAUTH_TELNET_LONG_USERNAME
System Log Message Authentication for user username at client-address was denied (long username).
Description The length of username must not exceed 64 characters.
Severity info
Facility LOG_PFE
FWAUTH_TELNET_LONG_USERNAME_LS
(long username).
Description The length of username must not exceed 64 characters.
Severity info
Facility LOG_PFE
FWAUTH_TELNET_USER_AUTH_ACCEPTED
Description The authenticated user can start accessing protected resources
Severity info
Facility LOG_PFE
FWAUTH_TELNET_USER_AUTH_FAIL

Chapter 47: FWAUTH System Log Messages
Severity info
Facility LOG_PFE
FWAUTH_TELNET_USER_AUTH_FAIL_LS
Severity info
Facility LOG_PFE
FWAUTH_TELNET_USER_AUTH_OK_LS
accepted.
Description The authenticated user can start accessing protected resources
Severity info
Facility LOG_PFE
FWAUTH_WEBAUTH_FAIL
System Log Message WebAuth user username at client-address is rejected/timed out.
Description The provided user credentials are not valid.
Severity info
Facility LOG_PFE
FWAUTH_WEBAUTH_FAIL_LS
System Log Message Lsys logical-system-name: WebAuth user username at client-address is rejected/timed
out.
Description The provided user credentials are not valid.
Severity info
Facility LOG_PFE
FWAUTH_WEBAUTH_SUCCESS
System Log Message WebAuth user username of group group-name at client-address is accepted.

Severity info
Facility LOG_PFE
FWAUTH_WEBAUTH_SUCCESS_LS
System Log Message Lsys logical-system-name: WebAuth user username of group group-name at client-address
is accepted.
Severity info
Facility LOG_PFE

CHAPTER 48
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 Unable to allocate count bytes of memory
Description The general packet radio service daemon process (gprsd) could not allocate the indicated
number of bytes of memory.
Severity error
Facility LOG_DAEMON
Cause It is possible that system memory is exhausted.
Action Increase the amount of RAM in the Routing Engine.
GPRSD_RESTART_CCFG_READ_FAILED
System Log Message Subcomponent could not read configuration database
Description 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.
Severity error
Facility LOG_DAEMON


CHAPTER 49
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 Detected change in IP addresses for host: hostname
Description The hostname-caching process (hostname-cached) detected that the set of IP addresses
for the specified hostname changed
Severity info
Facility LOG_DAEMON
HNCACHED_NAME_RESOLUTION_FAILURE
System Log Message Failed to resolve hostname: hostname (error-message)
Description The hostname-caching process (hostname-cached) failed to resolve the specified

hostname for indicated reason
Severity error
Facility LOG_DAEMON
Action 1)If the hostname used in config is incorrect, fix it. 2) Ensure that the configured
name-server is reachabe and is working.


CHAPTER 50
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
Description 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.
Severity error
Facility LOG_DAEMON
Action 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. For more
information, see http://kb.juniper.net/InfoCenter/index?page=content&id=KB18907.
ICCPD_OPEN_ERROR
System Log Message error-message: open error on pipe
Description The interchassis communication process (iccpd) could not initialize.
Severity error
Facility LOG_DAEMON

ICCPD_READ_ERROR
System Log Message Read error on pipe from client-name: reason (error-message)
Description The interchassis communication process (iccpd) could not read a message on a pipe for
the indicated client.
Severity info
Facility LOG_DAEMON
ICCPD_WRITE_ERROR
System Log Message write error on pipe to client-name:
Description The interchassis communication process (iccpd) could not write a message on a pipe
for the indicated client.
Severity error
Facility LOG_DAEMON

CHAPTER 51
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 epoch-time 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
threat-severity threat-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
Description 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
Severity info
Facility LOG_PFE
IDP_APPDDOS_APP_ATTACK_EVENT_LS
System Log Message Lsys logical-system-name: DDOS Attack at epoch-time 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
threat-severity threat-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
Description 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

Severity info
Facility LOG_PFE
IDP_APPDDOS_APP_STATE_EVENT
System Log Message DDOS Application threshold crossed at epoch-time 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
Description 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
Severity info
Facility LOG_PFE
IDP_APPDDOS_APP_STATE_EVENT_LS
System Log Message Lsys logical-system-name: DDOS Application threshold crossed at epoch-time 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
Description 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
Severity info
Facility LOG_PFE
IDP_ATTACK_LOG_EVENT
System Log Message IDP: at epoch-time, 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,
threat-severity=threat-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,
packet-log-id: packet-log-id and misc-message message

Chapter 51: IDP System Log Messages
Description IDP Attack log generated for attack
Severity info
Facility LOG_PFE
IDP_ATTACK_LOG_EVENT_LS
System Log Message Lsys logical-system-name: IDP: At epoch-time, 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,
threat-severity=threat-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,
packet-log-id: packet-log-id and misc-message message
Description IDP Attack log generated for attack
Severity info
Facility LOG_PFE
IDP_COMMIT_COMPLETED
System Log Message IDP policy commit is complete.
Description IDP policy commit has completed. Policy compile and load however may have been a
success or failure.
Severity notice
Facility LOG_AUTH
IDP_COMMIT_FAILED
System Log Message IDP policy commit failed. Exiting from compilation.
Description There was an error while trying to commit the active policy in IDPD. Device will continue
running the current IDP policy.
Severity error
Facility LOG_AUTH

IDP_DAEMON_INIT_FAILED
System Log Message Aborting...A failure was encountered;error-message
Description An attempt to start IDP policy daemon failed because an error was encountered during
initialization.
Severity error
Facility LOG_AUTH

IDP_IGNORED_IPV6_ADDRESSES
System Log Message IDP ignores IPv6 addresses for the 'rulebase-name'
Description IDP IPv6 support is not enabled for the rulebase.
Severity warning
Facility LOG_AUTH
IDP_INTERNAL_ERROR
System Log Message Encountered an error(error-message)
Description IDP daemon encountered an internal error
Severity error
Facility LOG_AUTH

IDP_POLICY_COMPILATION_FAILED
System Log Message IDP compilation of policy[idp-policy] failed : [reason]
Description IDP policy compiler encountered an error while compiling or packaging the policy.Device
will continue running the existing IDP policy
Severity error
Facility LOG_AUTH

IDP_POLICY_LOAD_FAILED
System Log Message IDP policy loading failed ;policy[idp-policy], detector[idp-detector] ,failure detail[reason]
Description A compiled and optimized IDP policy could not be loaded into IDP engine. Device will
continue running the existing IDP policy.
Severity error
Facility LOG_AUTH
IDP_POLICY_LOAD_SUCCEEDED
System Log Message IDP policy[idp-policy] and detector[idp-detector] loaded successfully(message).
Description 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.
Severity notice
Facility LOG_AUTH
IDP_POLICY_UNLOAD_FAILED
System Log Message Failed to unload IDP policy. reason: reason.
Description A running IDP policy could not be unloaded from IDP engine. Device will continue running
the IDP policy.
Severity error
Facility LOG_AUTH
IDP_POLICY_UNLOAD_SUCCEEDED
System Log Message IDP policy unloaded successfully.
Description A running IDP policy was unloaded successfully from the IDP engine.
Severity notice
Facility LOG_AUTH
IDP_SCHEDULEDUPDATE_START_FAILED
System Log Message Failed to start scheduled update(error:error-message)
Description The scheduled IDP security package update failed to start. Device will try it again at the
next scheduled time

Severity error
Facility LOG_AUTH
IDP_SCHEDULED_UPDATE_STARTED
System Log Message Scheduled update has started(at timestamp)
Description The scheduled IDP security package update has started.
Severity notice
Facility LOG_AUTH
IDP_SECURITY_INSTALL_RESULT
System Log Message security package install result(status)
Description IDP background process has returned the security package install result
Severity notice
Facility LOG_AUTH
IDP_SESSION_LOG_EVENT
System Log Message IDP: at epoch-time, event-name.
Description IDP session threshold crossing event
Severity info
Facility LOG_PFE
IDP_SESSION_LOG_EVENT_LS
System Log Message Lsys logical-system-name: IDP: At epoch-time, event-name.
Description IDP session threshold crossing event
Severity info
Facility LOG_PFE
IDP_SIGNATURE_LICENSE_EXPIRED
System Log Message IDP Signagure update license(ID=feature-id) has expired
Description IDP signature update license key has expired. Signature update may not work any more.

Severity warning
Facility LOG_AUTH


CHAPTER 52
JADE System Log Messages
This chapter describes messages with the JADE prefix. They are generated by the Junos
XML protocol authentication process (jade), which authenticates and checks authorization
of client applications using the Junos XML management protocol.
JADE_ATTRIBUTES_TOO_LONG
System Log Message Attribute number or length in client junoscript tag was too large
Description The JUNOScript client passed too many attributes in the initial <junoscript> tag, or the
attributes were too long.
Severity error
Facility ANY
JADE_AUTH_FAILURE
System Log Message Authentication failed for user 'username' : error-message
Description The username or password supplied by the client was incorrect.
Severity notice
Facility ANY
JADE_AUTH_SUCCESS
System Log Message Authentication succeded for user 'username'
Description The jade authentication process authenticated the indicated user.
Severity notice
Facility ANY
JADE_EXEC_ERROR
System Log Message CLI xml-mode exec error: error-message

Description The JUNOScript authentication process (jade) could not start because of an internal
error.
Severity error
Facility ANY
JADE_IRI_AUTH_SUCCESS
System Log Message Authentication succeded for user 'username' over IRI 'routing-instance'
Description The jade authentication process authenticated the indicated user over IRI.
Severity notice
Facility ANY
JADE_PAM_ERROR
System Log Message PAM error: error-message
Description The JUNOScript authentication process (jade) could not process the credentials supplied
by the client.
Severity error
Facility ANY
JADE_PAM_NO_LOCAL_USER
System Log Message Unable to get local username from PAM: error-message
Description The JUNOScript authentication process (jade) could not obtain a local username while
processing the credentials supplied by the client.
Severity error
Facility ANY
JADE_SOCKET_ERROR
System Log Message Socket operation 'operation' failed: error-message
Description The indicated socket operation, initiated by the JUNOScript authentication process (jade),
failed for the indicated reason.
Severity error

Chapter 52: JADE System Log Messages
Facility ANY


CHAPTER 53
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 Blade slot load BBD falure: error-message
Description The JCS process (jcsd) could not load blade bay data for the specified blade.
Severity error
Facility LOG_DAEMON
JCS_BBD_LOCAL_MISMATCH
System Log Message Blade slot BBD error-message mismatch (expected-value != received-value)
Description 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.
Severity error
Facility LOG_DAEMON

JCS_BBD_NOT_FOUND
System Log Message Blade slot bay data not found
Description Blade bay data was not found for the specified blade.
Severity error

Facility LOG_DAEMON

JCS_BBD_NOT_VALID
System Log Message Blade slot BBD is invalid
Description The blade bay data for the specified blade is invalid.
Severity error
Facility LOG_DAEMON

JCS_BBD_PARSE_ERROR
System Log Message Blade slot bay data parse error - error-message
Description The blade bay data for the specified blade did not parse correctly.
Severity error
Facility LOG_DAEMON

JCS_BBD_PEER_MISMATCH
System Log Message Peer blade slot BBD error-message mismatch (expected-value != received-value)
Description 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.
Severity error
Facility LOG_DAEMON

JCS_BBD_SYSTEM_CONFLICT
System Log Message Local BBD error-message (value) conflicts with blade slot

Chapter 53: JCS System Log Messages
Description 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.
Severity error
Facility LOG_DAEMON
JCS_INVALID_BANDWIDTH_ERROR
System Log Message Invalid bandwidth percent (value)
Description The specified switch bandwidth is invalid. The bandwidth is defined as a percentage
between 1 and 100.
Severity error
Facility LOG_DAEMON
JCS_KERNEL_RSD_LINK_DOWN
System Log Message Kernel RSD link is DOWN (error-message)
Description The JCS process (jcsd) has disabled kernel RSD communcation for the specified reason.
Severity error
Facility LOG_DAEMON

JCS_KERNEL_RSD_LINK_ENABLED
System Log Message Kernel RSD link is ENABLED (error-message)
Description The JCS process (jcsd) has verified the blade bay data and enabled kernel RSD
communication.
Severity info
Facility LOG_DAEMON
JCS_MM_COMMUNICATION_ERROR
System Log Message MM communication error (error-message)
Description The JCS process (jcsd) could not send an SNMP request to the Management Module
because of the indicated error.

Severity error
Facility LOG_DAEMON

JCS_MM_COMMUNICATION_OK
System Log Message MM communication is OK
Description The JCS process (jcsd) has established a communication link with the Management
Module.
Severity info
Facility LOG_DAEMON
JCS_PEER_BLADE_STATE
System Log Message Peer blade slot is state
Description The JCS process (jcsd) detects a change of state for the indicated blade.
Severity info
Facility LOG_DAEMON
JCS_READ_BANDWIDTH_ERROR
System Log Message Read bandwidth error (error-code)
Description The indicated error occured when attempting to read the current switch bandwidth.
Severity error
Facility LOG_DAEMON

JCS_READ_BBD_ERROR
System Log Message Read blade bay data (error=error-code)
Description The indicated error occured when attempting to read the current blade bay data via a
sysctl call.

Chapter 53: JCS System Log Messages
Severity error
Facility LOG_DAEMON

JCS_SWITCH_BANDWIDTH_CONFIG
System Log Message Switch slot bandwidth value1 percent (value2 KBPS)
Description The indicated JCS Switch Module has changed the bandwidth configuration to the
specified value.
Severity info
Facility LOG_DAEMON
JCS_SWITCH_COMMUNICATION_ERROR
System Log Message Switch slot communication error (error-message)
Description The JCS process (jcsd) could not send an SNMP request to the indicated Switch Module
because of the indicated error.
Severity error
Facility LOG_DAEMON



CHAPTER 54
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_HSHAKE_FAIL
System Log Message Application diameter-function cannot generate handshake, disconnecting
Description The Diameter process(jdiameterd) failed to generate handshake message to the process
that implements the Diameter-function. The connection was closed so that a new
connection with full resynchronization could be established.
Severity error
Facility LOG_DAEMON
JDIAMETERD_FUNC_LOCACCEPT_NFOUND
System Log Message Path pathname does not match any application
Description The Diameter process(jdiameterd) rejected a RE function side connection because there
is no matching diameter-function.
Severity error
Facility LOG_DAEMON
JDIAMETERD_FUNC_NSCK_LISTEN_FAIL
System Log Message Unable to listen on internal-ip
Description The Diameter process(jdiameterd) is unable to listen on the internal ip socket for function
side connections.
Severity error
Facility LOG_DAEMON

JDIAMETERD_FUNC_OUT_OF_SYNC
System Log Message Application diameter-function is out of sync, disconnecting
Description 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.
Severity error
Facility LOG_DAEMON
JDIAMETERD_FUNC_PICACCEPT_NFOUND
System Log Message Port remote-port does not match any application
Description The Diameter process(jdiameterd) rejected a PIC function side connection because there
is no matching diameter-function.
Severity error
Facility LOG_DAEMON
JDIAMETERD_FUNC_TOO_MANY_BADE2ES
System Log Message Application diameter-function has too many bad end-to-end-ids, disconnecting
Description A daemon impelenting diameter function, sent too many messages with bad
end-to-end-ids the connection will be closed, so a new connection with full
resynchronization could be established.
Severity error
Facility LOG_DAEMON
JDIAMETERD_FUNC_USCK_LISTEN_FAIL
System Log Message Unable to listen on pathname
Description The Diameter process(jdiameterd) is unable to listen on the unix socket for function side
connections.
Severity error
Facility LOG_DAEMON

CHAPTER 55
JIVED System Log Messages
This chapter describes messages with the JIVED prefix. They are generated by the
mag-service process (jived).
JIVED_ALREADY_RUNNING
System Log Message Another copy of this program is running
Description Another instance of the mag-service process (jived) is already running. Only one instance
can run at a time.
Severity error
Facility LOG_DAEMON
JIVED_EVLIB_FUNC_FAILED
System Log Message function-name: event-function-name: reason
Description A function in the event library used by the mag-service process (jived) failed with the
indicated error.
Severity error
Facility LOG_DAEMON
JIVED_INITIATE_CONN_FAILED
System Log Message function-name: aborting, failed to connect to mgd.
Description The mag-service process (jived) failed to initiate the connection to RE.
Severity error
Facility LOG_DAEMON

JIVED_INIT_FAILED
System Log Message error-message: reason
Description The mag-service process (jived) failed to initialize.
Severity error
Facility LOG_DAEMON
JIVED_NOT_ROOT
System Log Message JIVED must run as root
Description The mag-service process (jived) must be run with root privileges.
Severity error
Facility LOG_DAEMON
Cause jived being run without root privilege
JIVED_PIDFILE_LOCK_FAILED
System Log Message Unable to lock pid file
Description The mag-service process (jived) failed to lock the file that records its process ID (PID).
The lock file is used to prevent multiple instances of the jived process from running
simultaneously.
Severity error
Facility LOG_DAEMON
Cause Another instance of the jived process is already running.
JIVED_PIDFILE_UPDATE_FAILED
System Log Message can not update process PID file: reason
Description The mag-service process (jived) failed to update the file that records its process ID (PID).
The lock file is used to prevent multiple instances of the jived process from running
simultaneously.
Severity error

Chapter 55: JIVED System Log Messages
Facility LOG_DAEMON
JIVED_SNMP_SEND_TRAP_FAILED
System Log Message error-message: trap
Description The mag-service process (jived) failed in the attempt to send an SNMP trap
Severity error
Facility LOG_DAEMON


CHAPTER 56
JNUD System Log Messages
JNUD_CONFIG_ERROR
System Log Message Configuration database has errors
Description The Junos Node Unifier process (jnud) detected an error in the JNU configuration database.
Severity error
Facility LOG_DAEMON
JNUD_INIT_FAILED
System Log Message jnud initialization failure: error-message
Description Initialization of the Junos Node Unifier process (jnud) failed.
Severity error
Facility LOG_DAEMON


CHAPTER 57
JPTSPD System Log Messages
This chapter describes messages with the JPTSPD prefix. They are generated by the
packet-triggered subscriber process (jptspd) which creates and manages packet-triggered
subscriber interfaces. A packet-triggered subscriber interface is created when the router
receives a packet with an IP source address that does not match any entries in the
demultiplexer table. When the router detects an unmatched packet, it generates a trigger
event that determines whether to create a dynamic subscriber interface or configure an
existing interface.
JPTSPD_INIT_FAILURE
System Log Message JPTSPD failed to initialize
Description The packet triggered subscriber process (jptspd) initialization failed.
Severity error
Facility ANY
Cause One possible cause is that the system is out of memory.
JPTSPD_OUT_OF_MEMORY
System Log Message Out of memory
Description The packet triggered subscriber process (jptspd) could not dynamically allocate memory.
Severity error
Facility ANY
Cause A software bug caused a memory leak, or too many subscriber and service sessions.

JPTSPD_PIC_CONNECTED
System Log Message JPTSPD connected to pic pic-name
Description The packet triggered subscriber process (jptspd) connected to a PIC.
Severity info
Facility ANY
JPTSPD_PIC_DISCONNECTED
System Log Message JPTSPD disconnected to pic pic-name reason
Description The packet triggered subscriber process (jptspd) disconnected to a PIC.
Severity info
Facility ANY
JPTSPD_SRC_FAST_SYNC_ABORT
System Log Message JPTSPD fast synchronization was aborted partition-name
Description The packet triggered subscriber process (jptspd) aborted fast synchronization with SRC.
Severity info
Facility ANY
Cause One possible cause is that the connection between jptspd and SRC is down.
JPTSPD_SRC_FAST_SYNC_DONE
System Log Message JPTSPD fast synchronization was done partition-name
Description The packet triggered subscriber process (jptspd) finished fast synchronization with SRC.
Severity info
Facility ANY
JPTSPD_SRC_FAST_SYNC_START
System Log Message JPTSPD fast synchronization started partition-name
Description The packet triggered subscriber process (jptspd) started fast synchronization with SRC.

Chapter 57: JPTSPD System Log Messages
Severity info
Facility ANY
JPTSPD_SRC_FULL_SYNC_ABORT
System Log Message JPTSPD full synchronization was aborted partition-name
Description The packet triggered subscriber process (jptspd) aborted full synchronization with SRC.
Severity info
Facility ANY
Cause One possible cause is that the connection between jptspd and SRC is down.
JPTSPD_SRC_FULL_SYNC_DONE
System Log Message JPTSPD full synchronization was done partition-name
Description The packet triggered subscriber process (jptspd) finished full synchronization with SRC.
Severity info
Facility ANY
JPTSPD_SRC_FULL_SYNC_START
System Log Message JPTSPD full synchronization started partition-name
Description The packet triggered subscriber process (jptspd) started full synchronization with SRC.
Severity info
Facility ANY


CHAPTER 58
JSERVICES System Log Messages
This chapter describes messages with the JSERVICES prefix.
JSERVICES_NAT_OUTOF_ADDRESSES
System Log Message natpool nat-pool-name is out of addresses
Description Network Address Translation (NAT) services could not allocate an address from the
indicated NAT pool, because no addresses were available.
Severity warning
Facility ANY
JSERVICES_NAT_OUTOF_PORTS
System Log Message natpool nat-pool-name is out of ports
Description Network Address Translation (NAT) services could not allocate a port from the indicated
NAT pool, because no ports were available.
Severity warning
Facility ANY
JSERVICES_NAT_POOL_RELEASE
System Log Message natpool release address:port[count]
Description 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.
Severity info
Facility ANY

JSERVICES_NAT_PORT_BLOCK_ACTIVE
0xobject-create-time
Description Network Address Translation (NAT) services will generate interim log at the configured
interval when the interim log is enabled, which will carry all the information logged in
JSERVICES_NAT_PORT_BLOCK_ALLOC including the create-timestamp.
Severity info
Facility ANY
JSERVICES_NAT_PORT_BLOCK_ALLOC
Description Network Address Translation (NAT) services allocated a port block for the indicated
private address, with the defined range of ports and NAT IP allocated to it.
Severity info
Facility ANY
JSERVICES_NAT_PORT_BLOCK_RELEASE
Description Network Address Translation (NAT) services released a port block associated with the
indicated private address, with the defined range of ports and NAT IP allocated to it.
Severity info
Facility ANY
JSERVICES_NAT_RULE_MATCH
System Log Message proto protocol-id (protocol-name) application: application,
interface-name:source-address:source-port -> destination-address:destination-port, Match
NAT rule-set: rule-set-name, rule: rule-name, term: term-name
nat rule. The matching packet contained the indicated information about its protocol

Chapter 58: JSERVICES System Log Messages
(numerical identifier and name), application, source (logical interface name, IP address,
Severity info
Facility ANY
JSERVICES_SESSION_CLOSE
System Log Message application:application, source-interface-name source-address:source-port
source-nat-information -> destination-address destination-port:destination-nat-information
(protocol-name)
Description The session with the indicated characteristics is removed. The NAT data is available in
the message if the session requires Network Address Translation (NAT).
Severity info
Facility ANY
Action None
JSERVICES_SESSION_OPEN
System Log Message application:application, source-interface-name source-address:source-port
source-nat-information -> destination-address destination-port:destination-nat-information
(protocol-name)
Description The packet with the indicated characteristics is accepted by the configured plugins after
a policy check. As a result, a new session is created and opened for traffic. The NAT
information is available in the message if the policy requires Network Address Translation
(NAT).
Severity info
Facility ANY
Action None
JSERVICES_SFW_RULE_ACCEPT
System Log Message proto protocol-id (protocol-name) application: application, interface:
source-interface-name, source-address:source-port -> destination-address:destination-port,
Match SFW event-type rule-set: rule-set-name, rule: rule-name, term: term-name
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

Severity info
Facility ANY
JSERVICES_SFW_RULE_DISCARD
System Log Message proto protocol-id (protocol-name) application: application, source-address:source-port
-> destination-address:destination-port, Match SFW event-type rule-set: rule-set-name,
rule: rule-name, term: term-name
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
Severity notice
Facility ANY
JSERVICES_SFW_RULE_REJECT
System Log Message proto protocol-id (protocol-name) application: application, source-address:source-port
-> destination-address:destination-port, Match SFW event-type rule-set: rule-set-name,
rule: rule-name, term: term-name
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
Severity notice
Facility ANY

CHAPTER 59
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 Aborting, unable to run in the background as a daemon: error-message
Description The Juniper Services Redundancy Protocol process (JSRPD) failed to create a version of
itself to run in the background.
Severity emergency
Facility LOG_DAEMON

JSRPD_DUPLICATE
Description The Juniper Services Redundancy Protocol process (JSRPD) detected that another
version of itself is already running.
Severity error
Facility LOG_DAEMON
JSRPD_NODE_STATE_CHANGE
System Log Message Nodechassis-id state due to reason
Description The Juniper Services Redundancy Protocol process (JSRPD) detected an event, such as
failover, that caused the state of the chassis cluster node to change due to the reason
indicated in the log.

Severity error
Facility LOG_DAEMON
Cause A link failure occurred and the secondary node is disabled.
Cause The secondary node has recovered from link failure and is being rebooted to recover from
the disabled state.
JSRPD_NOT_ROOT
Description The Juniper Services Redundancy Protocol process (JSRPD) can be instantiated only by
the user with root privileges.
Severity error
Facility LOG_DAEMON
JSRPD_PID_FILE_LOCK
System Log Message Unable to lock PID file: error-message
Description The Juniper Services Redundancy Protocol process (JSRPD) failed to lock the PID file,
which serves to prevent multiple instances of the process from running simultaneously.
Severity error
Facility LOG_DAEMON
JSRPD_PID_FILE_UPDATE
System Log Message Unable to update process PID file: error-message
Description The Juniper Services Redundancy Protocol process (JSRPD) failed to update the PID file,
which serves to prevent multiple instances of the process from running simultaneously.
Severity error
Facility LOG_DAEMON
JSRPD_REDUNDANCY_MODE_CHANGE
System Log Message Redundancy mode change will not be effective until all nodes in the cluster are rebooted
simultaneously

Chapter 59: JSRPD System Log Messages
Description The Juniper Services Redundancy Protocol process (JSRPD) detected a change in chassis
cluster redundancy mode. The new mode is not effective until all nodes in the cluster
are rebooted.
Severity warning
Facility LOG_DAEMON
JSRPD_REDUNDANCY_MODE_MISMATCH
System Log Message Change in HA redundancy mode detected..please reboot all nodes in the cluster
simultaneously!!
Description The Juniper Services Redundancy Protocol process (JSRPD) detected a change in the
chassis cluster redundancy mode configuration and detected that only some (not all)
of the nodes rebooted. The new mode is not effective until all nodes in the cluster are
rebooted.
Severity warning
Facility LOG_DAEMON
JSRPD_RG_STATE_CHANGE
System Log Message Redundancy-group rg-id transitioned from 'old-state' to 'new-state' state due to reason
Description The Juniper Services Redundancy Protocol process (JSRPD) detected an event that
caused the state of the chassis cluster redundancy group to change due to the reason
indicated in the log.
Severity alert
Facility LOG_DAEMON
JSRPD_SET_CS_MON_FAILURE
System Log Message Cold-sync Monitor failed for redundancy-group rg-id
Description The Juniper Services Redundancy Protocol process (JSRPD) detected cold-sync
monitoring failure for a redundancy group.
Severity error
Facility LOG_DAEMON
JSRPD_SET_HW_MON_FAILURE
System Log Message hw-mon failed for redundancy-group rg-id

Description The Juniper Services Redundancy Protocol process (JSRPD) detected hardware failures.
Severity error
Facility LOG_DAEMON
JSRPD_SET_INTF_MON_FAILURE
System Log Message Interface Monitor failed for redundancy-group rg-id
Description The Juniper Services Redundancy Protocol process (JSRPD) detected interface monitoring
failure for a redundancy group.
Severity error
Facility LOG_DAEMON
JSRPD_SET_IP_MON_FAILURE
System Log Message IP Monitor failed for redundancy-group rg-id
Description The Juniper Services Redundancy Protocol process (JSRPD) detected IP address
Severity error
Facility LOG_DAEMON
JSRPD_SET_LOOPBACK_MON_FAILURE
System Log Message Loopback Monitor failed for redundancy-group rg-id
Description The Juniper Services Redundancy Protocol process (JSRPD) detected data path loopback
Severity error
Facility LOG_DAEMON
JSRPD_SET_MBUF_MON_FAILURE
System Log Message Memory buffer monitor failed for redundancy-group rg-id
Description The Juniper Services Redundancy Protocol process (JSRPD) detected memory buffer
Severity error

Facility LOG_DAEMON
JSRPD_SET_NEXTHOP_MON_FAILURE
System Log Message Fabric nexthop monitor failed for redundancy-group rg-id
Description The Juniper Services Redundancy Protocol process (JSRPD) detected fabric nexthop
Severity error
Facility LOG_DAEMON
JSRPD_SET_NPC_MON_FAILURE
System Log Message NPC Monitor failed for redundancy-group rg-id
Description The Juniper Services Redundancy Protocol process (JSRPD) detected Network Processing
Card (NPC) monitoring failure for a redundancy group.
Severity error
Facility LOG_DAEMON
JSRPD_SET_OTHER_INTF_MON_FAIL
System Log Message Interface Monitor failed on other node for redundancy-group rg-id
Description The Juniper Services Redundancy Protocol process (JSRPD) detected interface monitoring
failure on the other node for a redundancy group.
Severity error
Facility LOG_DAEMON
JSRPD_SET_SPU_MON_FAILURE
System Log Message SPU Monitor failed for redundancy-group rg-id
Description The Juniper Services Redundancy Protocol process (JSRPD) detected Services Processing
Unit (SPU) monitoring failure for a redundancy group.
Severity error
Facility LOG_DAEMON
JSRPD_SOCKET_CREATION_FAILURE
System Log Message Socket creation (server) failed unexpectedly error-message.
Description The Juniper Services Redundancy Protocol process (JSRPD) failed to create a socket.

Severity error
Facility LOG_DAEMON

JSRPD_SOCKET_LISTEN_FAILURE
System Log Message Socket listen (server) failed unexpectedly. error-message
Description The Juniper Services Redundancy Protocol process (JSRPD) failed to listen on a socket.
Severity error
Facility LOG_DAEMON

JSRPD_SOCKET_RECV_HB_FAILURE
System Log Message Socket reception of heartbeat from failed unexpectedly error-message.
Description The Juniper Services Redundancy Protocol process (JSRPD) failed to receive heartbeat.
Severity error
Facility LOG_DAEMON

JSRPD_UNSET_CS_MON_FAILURE
System Log Message Cold-sync Monitor failure recovered for redundancy-group rg-id
Description The Juniper Services Redundancy Protocol process (JSRPD) detected that the previous
cold-sync monitoring failure no longer exists for a redundancy group.
Severity error
Facility LOG_DAEMON
JSRPD_UNSET_HW_MON_FAILURE
System Log Message hw-mon failure recovered for redundancy-group rg-id

hardware failures no longer exists for a redundancy group.
Severity error
Facility LOG_DAEMON
JSRPD_UNSET_INTF_MON_FAILURE
System Log Message Interface Monitor failure recovered for redundancy-group rg-id
interface monitoring failure no longer exists for a redundancy group.
Severity error
Facility LOG_DAEMON
JSRPD_UNSET_IP_MON_FAILURE
System Log Message IP Monitor failure recovered for redundancy-group rg-id
IP address monitoring failure no longer exists for a redundancy group.
Severity error
Facility LOG_DAEMON
JSRPD_UNSET_LOOPBACK_MON_FAILURE
System Log Message Previous loopback monitor failure no longer exist for redundancy-group rg-id
data path loopback monitoring failure no longer exists for a redundancy group.
Severity error
Facility LOG_DAEMON
JSRPD_UNSET_MBUF_MON_FAILURE
System Log Message Previous memory buffer monitor failure no longer exis for redundancy-group rg-id
memory buffer monitoring failure no longer exists for a redundancy group.
Severity error

Facility LOG_DAEMON
JSRPD_UNSET_NEXTHOP_MON_FAILURE
System Log Message Previous fabric nexthop monitor failure no longer exis for redundancy-group rg-id
fabric nexthop monitoring failure no longer exists for a redundancy group.
Severity error
Facility LOG_DAEMON
JSRPD_UNSET_NPC_MON_FAILURE
System Log Message NPC Monitor failure recovered for redundancy-group rg-id
Network Processing Card (NPC) monitoring failure no longer exists for a redundancy
group.
Severity error
Facility LOG_DAEMON
JSRPD_UNSET_OTHER_INTF_MON_FAIL
System Log Message Interface Monitor failure recovered on other node for redundancy-group rg-id
Description The Juniper Services Redundancy Protocol process (JSRPD)\ detected that the previous
interface monitoring failure on the other node no longer exists for a redundancy group.
Severity error
Facility LOG_DAEMON
JSRPD_UNSET_SPU_MON_FAILURE
System Log Message SPU Monitor failure recovered for redundancy-group rg-id
Services Processing Unit (SPU) monitoring failure no longer exists for a redundancy
group.
Severity error
Facility LOG_DAEMON

JSRPD_USAGE
System Log Message Usage: jsrpd [-C] [-N] [-X] [-d debug-level] [-l] [-v]
Description The Juniper Services Redundancy Protocol process (JSRPD) was invoked with incorrect
options.
Severity error
Facility LOG_DAEMON


CHAPTER 60
JTASK System Log Messages
This chapter describes messages with the JTASK prefix.
JTASK_ABORT
System Log Message abort executable-name[pid] version version built by builder on date: error-message
Description Process terminated because of an internal error.
Severity error
Facility LOG_DAEMON
information about possible causes.
JTASK_ACTIVE_TERMINATE
System Log Message Exiting with active tasks: task-name
Description After receiving multiple termination requests, the process exited without performing the
indicated cleanup tasks.
Severity notice
Facility LOG_DAEMON
JTASK_ASSERT
System Log Message Assertion failed executable-name[pid]: file "source-filename", line line-number: "message"
Description The source code for the process includes internal self-consistency checks. A check failed
at the indicated line number in the indicated source file, causing the process 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.

Severity error
Facility LOG_DAEMON
ready to provide the list of messages and the diagnostic core dump, if requested.
JTASK_ASSERT_SOFT
System Log Message Soft assertion failed executable-name[pid]: file "source-filename", line line-number:
"message", daemon continued running
Description The source code for the process includes internal self-consistency checks. A check failed
at the indicated line number in the indicated source file, but the process 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.
Severity error
Facility LOG_DAEMON
ready to provide the list of messages and the diagnostic core dump, if requested.
JTASK_BFD_READ_ERROR
System Log Message Read error on pipe from bfdd: reason (error-message)
Description The process could not read a message available on the read pipe from the Bidirectional
Forwarding Detection process (bfdd).
Severity info
Facility LOG_DAEMON
JTASK_BFD_WRITE_ERROR
System Log Message function-name: write error on pipe to bfdd (error-message)
Description The process could not write a message on the pipe to the Bidirectional Forwarding
Detection process (bfdd).

Chapter 60: JTASK System Log Messages
Severity error
Facility LOG_DAEMON
JTASK_CFG_CALLBACK_LONGRUNTIME
System Log Message function-name: excessive runtime time during action of module
Description The indicated submodule of the process ran uninterrupted for the indicated period of
time, which is considered excessive.
Severity warning
Facility LOG_DAEMON
Cause The duration was noted because task accounting is enabled. The function might be
implemented inefficiently.
JTASK_CFG_SCHED_CUMU_LONGRUNTIME
System Log Message function-name: excessive runtime (total of time in count callbacks) after action of module
Description Several submodules of the process ran uninterrupted for the indicated period of time,
which is considered excessive.
Severity warning
Facility LOG_DAEMON
JTASK_EXIT
System Log Message Exit executable-name[pid] version version built by builder on date, caller address
Description The process exited, either in response to a user request or because of a system error.
Severity notice
Facility LOG_DAEMON
Cause A system resource was unavailable, process did not understand an error, or a user
terminated the process.

information about possible causes.
JTASK_LOCK_FLOCKED
System Log Message Unable to obtain a lock on filename, is another copy of rpd running?
Description The process could not obtain the mutual exclusion lock that prevents more than one
instance of process from running simultaneously. The system terminated the indicated
process.
Severity error
Facility LOG_DAEMON
Cause Another process process is running.
Action Use the 'show system process' command to verify that another process is running.
JTASK_LOCK_LOCKED
System Log Message Unable to obtain a lock on filename, program-name[pid] is still running
Description The process could not obtain the mutual exclusion lock that prevents more than one
instance of process from running simultaneously. The system terminated this instance
of process.
Severity error
Facility LOG_DAEMON
Cause Another process is running.
Action Use the 'show system process' command to verify that another process is running.
JTASK_MGMT_TIMEOUT
System Log Message Connection to management peer process-name timed out waiting for input
Description The connection between the process and the indicated management process (mgd)
timed out before input arrived from the mgd process.
Severity warning
Facility LOG_DAEMON

JTASK_MODE_SWITCH
System Log Message Switching to mode-bit mode
Description Tasking application process is attempting to switch between 32- and 64-bit operating
mode.
Severity notice
Facility LOG_DAEMON
JTASK_MODE_SWITCH_FAIL
System Log Message Mode switch failed: error-message
Description Tasking application process could not switch to the configured 32- or 64-bit operating
mode.
Severity error
Facility LOG_DAEMON
JTASK_OS_MEMHIGH
System Log Message Using size KB of memory, percentage-value percent of available
Description The process is using the indicated amount and percentage of Routing Engine memory,
Severity error
Facility LOG_DAEMON
Cause Either process 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.
Action Increase the amount of RAM in the Routing Engine. For more information, see
JTASK_PARSE_BAD_COMMAND
System Log Message executable-name: problem processing debug shell command for command-line option
option, command 'command': error-message
Description An invalid debug shell command was specified on the command line.

Severity error
Facility LOG_DAEMON
Action Reissue the command and correct the error described.
JTASK_PARSE_BAD_FILE
System Log Message executable-name: problem processing file for command-line option option, file 'filename':
error-message
Description An invalid debug shell command file was specified on the command line.
Severity error
Facility LOG_DAEMON
Action Reissue the command and correct the error described.
JTASK_PARSE_BAD_LR_NAME
System Log Message executable-name: logical system name "logical-system-name"exceeds count characters
Description The indicated logical system name exceeds the indicated maximum number of characters.
Severity error
Facility LOG_DAEMON
Action Assign a shorter name.
JTASK_PARSE_BAD_OPTION
System Log Message executable-name: command-line option option is invalid
Description The command line used to start the indicated process included the indicated option,
which is invalid. The process did not start.
Severity error
Facility LOG_DAEMON
Action Reissue the command without the invalid option.
JTASK_PARSE_CMD_ARG
System Log Message executable-name: missing required argument for command-line option option
Description The command line used to start the indicated process did not include the argument
required by the indicated option. The process did not start.

Severity error
Facility LOG_DAEMON
Action Reissue the command and include the required argument. Examine the messages that
immediately follow this message in the system log for information about possible causes.
For more information, see
JTASK_PARSE_CMD_DUPLICATE
System Log Message executable-name: command-line option option is a duplicate
Description The command line used to start the indicated process included the indicated duplicate
option. The process did not start.
Severity error
Facility LOG_DAEMON
Action Reissue the command without the duplicate option.
JTASK_PARSE_CMD_EXTRA
System Log Message executable-name: command-line option option is extraneous
Description The command line used to start the indicated process included the indicated option,
which is extraneous. The process did not start.
Severity error
Facility LOG_DAEMON
Action Reissue the command and omit the extraneous option. For more information, see
JTASK_PTHREAD_CREATE
System Log Message Task pthread worker creation failed
Description During process initialization, creation of a thread has failed.
Severity alert
Facility LOG_DAEMON
Action Restart the application from the CLI (e.g. restart routing)

JTASK_SCHED_CUMU_LONGRUNTIME
System Log Message function-name: excessive runtime (total of time in count callbacks) after action of module
Severity warning
Facility LOG_DAEMON
JTASK_SCHED_MODULE_LONGRUNTIME
System Log Message function-name: excessive runtime time during action of module
Severity warning
Facility LOG_DAEMON
JTASK_SCHED_TASK_LONGRUNTIME
System Log Message function-name ran for total-time (user-time user, system-time system) doing action
Description A task callback within the process ran uninterrupted for the indicated period of time,
Severity warning
Facility LOG_DAEMON
JTASK_SIGNAL_TERMINATE
System Log Message signal-name termination signal received
Description In response to the indicated termination request, the process terminated adjacencies
with neighbors and shut down.

Severity notice
Facility LOG_DAEMON
JTASK_SNMP_CONN_EINPROGRESS
Description The indicated error occurred while the process was connecting to the Simple Network
Management Protocol (SNMP) master agent.
Severity info
Facility LOG_DAEMON

JTASK_SNMP_CONN_QUIT
System Log Message function-name: unable to connect to SNMP agent (pathname): error-message
Description The process could not connect to the indicated Simple Network Management Protocol
(SNMP) master agent.
Severity error
Facility LOG_DAEMON

JTASK_SNMP_CONN_RETRY
System Log Message function-name: reattempting connection to SNMP agent (pathname): error-message
Description The process tried again to connect to the indicated Simple Network Management Protocol
(SNMP) master agent after a connection attempt failed.
Severity error
Facility LOG_DAEMON
JTASK_SNMP_INVALID_SOCKET
System Log Message function-name: socket file-descriptor is invalid
Description The process could not send a message to a Simple Network Management Protocol
(SNMP) master agent because the indicated socket is invalid.

Severity error
Facility LOG_DAEMON
JTASK_SNMP_SOCKOPT_BLOCK
System Log Message function-name: unable to set nonblocking option
Description The process could not set a socket to nonblocking mode after connecting to the Simple
Network Management Protocol (SNMP) master agent.
Severity error
Facility LOG_DAEMON
JTASK_SNMP_SOCKOPT_RECVBUF
System Log Message function-name: unable to set recvbuf option
Description The process 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.
Severity error
Facility LOG_DAEMON

JTASK_SNMP_SOCKOPT_SENDBUF
System Log Message function-name: unable to set sendbf option
Description The process 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.
Severity error
Facility LOG_DAEMON

JTASK_START
System Log Message Start executable-name[pid] version version built date

Description The process started.
Severity info
Facility LOG_DAEMON
JTASK_SYSTEM
Description A system call made by the routing protocol process (process) failed.
Severity error
Facility LOG_DAEMON
Cause It is possible that the kernel lacked the resources to fulfill the request. The process process
will recover.

JTASK_TASK_BEGIN
System Log Message Commencing routing updates version process-version, built date by builder
Description The process started.
Severity notice
Facility LOG_DAEMON
JTASK_TASK_CHILDKILLED
System Log Message task-name terminated by SIGsignal-namecore-dump-status
Description While a child process of the process was performing the indicated operation, it terminated
in response to the indicated signal.
Severity error
Facility LOG_DAEMON
JTASK_TASK_CHILDSTOPPED
System Log Message task-name stopped by SIGsignal-name
Description While a child process of the process was performing the indicated operation, it stopped
in response to the indicated signal.

Severity error
Facility LOG_DAEMON
JTASK_TASK_DYN_REINIT
System Log Message Dynamic reconfiguration in process
Description The process reinitialized.
Severity info
Facility LOG_DAEMON
JTASK_TASK_FORK
System Log Message Unable to fork task-name: error-message
Description The routing protocol process failed to create the indicated child process.
Severity error
Facility LOG_DAEMON
JTASK_TASK_GETWD
System Log Message getwd: error-message
Description The getwd() system call made by the routing protocol process (process) failed.
Severity error
Facility LOG_DAEMON
Cause It is possible that the kernel lacked the resources to fulfill the request. The process process
will recover.
JTASK_TASK_MASTERSHIP
System Log Message Assuming mastership
Description The process became active when the Routing Engine on which it was running assumed
mastership.
Severity info
Facility ANY

JTASK_TASK_NOREINIT
System Log Message Reinitialization not possible
Description The process failed to reinitialize as requested, because it was running in a state that did
not allow reconfiguration.
Severity error
Facility LOG_DAEMON
JTASK_TASK_PIDCLOSED
System Log Message Unable to close and remove filename: error-message
Description The process tried to close and remove the file that records its process ID (PID), which
serves to prevent multiple instances of process from running simultaneously. The attempt
failed.
Severity error
Facility LOG_DAEMON
JTASK_TASK_PIDFLOCK
System Log Message flock(filename, LOCK_EX): error-message
Description The process issued the flock() system call on the file that records its process ID (PID),
which serves to prevent multiple instances of process from running simultaneously. The
system call failed.
Severity error
Facility LOG_DAEMON
JTASK_TASK_PIDWRITE
System Log Message Unable to write to fd filename: error-message
Description The process tried to write to the file that records its process ID (PID), which serves to
prevent multiple instances of process from running simultaneously. The attempt failed.
Severity error
Facility LOG_DAEMON
JTASK_TASK_REINIT
System Log Message Reinitializing

Description The process reinitialized.
Severity info
Facility LOG_DAEMON
JTASK_TASK_SIGNALIGNORE
System Log Message sigaction(SIGsignal-name): error-message
Description The process informed the kernel that it wished to ignore the indicated signal, but the
kernel failed to process the request.
Severity error
Facility LOG_DAEMON
JTASK_TERMINATE_DISK_SPACE
System Log Message disk full, terminating executable-name[pid] version version built by builder on
date.BACKTRACE: message
Description The routing process has terminated due to no disk space available.
Severity error
Facility LOG_DAEMON
Cause disk-full
Action Examine disk storage, especially /tmp and /var/tmp, for old or obsolete files such as old
core files or old log files that can be safely removed.

CHAPTER 61
JTRACE System Log Messages
This chapter describes messages with the JTRACE prefix.
JTRACE_FAILED
System Log Message Unable to write to trace file filename
Description 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.
Severity error
Facility LOG_DAEMON


CHAPTER 62
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 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
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 it could
not access the indicated pool.
Severity error
Facility LOG_AUTH
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
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.
Severity error
Facility LOG_AUTH
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
to IP Security (IPSec) interfaces. It could not allocate a logical interface, because none
were available in the indicated pool.

Severity error
Facility LOG_AUTH
KMD_CFG_IF_ID_POOL_RETURN_FAILED
System Log Message Unable to return logical interface to pool pool-name: pool not found
to IP Security (IPSec) interfaces. It could not return a logical interface to the indicated
pool, because it could not access the pool.
Severity error
Facility LOG_AUTH
KMD_DPD_FAILOVER_MANUAL_TUNNEL
System Log Message Tunnel tunnel-name did not fail over: it is manual type
Description 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.
Severity error
Facility LOG_AUTH
KMD_DPD_FAILOVER_MAX_ATTEMPTS
System Log Message Number of failover attempts exceeded limit count for tunnel tunnel-name
Description 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.
Severity error
Facility LOG_AUTH
Cause Failover attempts can fail repeatedly if both the primary and backup peers are unreachable
during the failover.
KMD_DPD_FAILOVER_NO_ACTIVE_PEER
System Log Message Tunnel tunnel-name did not fail over: no active peer configured

Chapter 62: KMD System Log Messages
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.
Severity error
Facility LOG_AUTH
KMD_DPD_FAILOVER_NO_BACKUP_PEER
System Log Message Tunnel tunnel-name did not fail over: no backup peer configured
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.
Severity error
Facility LOG_AUTH
KMD_DPD_FAILOVER_NO_TUNNEL_CFG
System Log Message Tunnel did not fail over: tunnel configuration not found
process (kmd) detects a dead peer. Failover was not attempted because there was no
configuration information for the tunnel.
Severity error
Facility LOG_AUTH
KMD_DPD_REMOTE_ADDRESS_CHANGED
System Log Message Remote peer address for tunnel tunnel-name changed from old-address to new-address
Description The remote peer address in the configuration for the indicated tunnel changed to a new
value as indicated.
Severity notice
Facility LOG_AUTH
KMD_PM_DUPLICATE_LIFE_DURATION
System Log Message Duplicate SA life duration value given in Quick Mode notification from
remote-address:remote-port

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.
Severity error
Facility LOG_SYSLOG
KMD_PM_IKE_SERVER_LOOKUP_FAILED
System Log Message No IKE server to connect Phase-1 to remote-peer
Description The IKE Phase-1 negotiation with indicated remote gateway address failed because there
is no corresponding IKE server running locally.
Severity error
Facility LOG_SYSLOG
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
Description There is no local IKE server context in the indicated service set, hence failed to send the
SPI delete notification request.
Severity error
Facility LOG_SYSLOG
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
Description 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.
Severity error
Facility LOG_AUTH
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

Description The specified remote gateway identity is neither an IPv4 address nor an IPv6 address.
Hence Phase-1 negotiation can not be started
Severity error
Facility LOG_SYSLOG
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
Description Initiator and responder identities at the local end are inconsistent with the remote peer's
identities. Quick Mode negotiation is aborted.
Severity error
Facility LOG_SYSLOG
KMD_PM_INVALID_LIFE_TYPE
System Log Message Invalid life type units-type found in the Quick Mode notification from
port contains invalid life type. Second and Kilobytes are the only supported life types
currently. Hence Quick Mode notification payload is dropped.
Severity error
Facility LOG_SYSLOG
KMD_PM_LIFETIME_TO_SHORT
System Log Message Lifetime negotiated for SA, "sa-name", is to short for reliable rekeying, changed from
lifetime to adjusted-lifetime seconds
Description The negotiated lifetime for the IPsec SA is to low to reliably rekey the IPsec SA. Used
lifetime was set to the minimum required value.
Severity info
Facility LOG_AUTH
KMD_PM_NO_LIFETIME
System Log Message Duplicate life time payloads present in the notification from remote-address:remote-port.
Dropping the notification.

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.
Severity error
Facility LOG_SYSLOG
KMD_PM_NO_LIFE_TYPE
System Log Message Quick mode notification from remote-address:remote-port contains lifetime duration
without corresponding SA lifetime payload.
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.
Severity error
Facility LOG_SYSLOG
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
Description It is not possible to start the Phase-1 negotiation to the indicated remote gateway because
there is no proposal present.
Severity error
Facility LOG_SYSLOG
KMD_PM_NO_SPD_PHASE1_FUNC_PTR
System Log Message Phase-1 SPD handler is not registered in instance:service-set
Description Phase-1 negotiation can not be initiated as initialization function failed.
Severity error
Facility LOG_SYSLOG
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

Description 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.
Severity error
Facility LOG_SYSLOG
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
Description 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.
Severity error
Facility LOG_SYSLOG
KMD_PM_PHASE1_GROUP_UNSPECIFIED
System Log Message Used DH group 1 because Phase 1 proposal did not specify group
Description 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.
Severity error
Facility LOG_AUTH
KMD_PM_PHASE1_POLICY_SEARCH_FAIL
System Log Message No ike-policy found for ike-access-profile: access-profile, instance:service-set
Description 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.
Severity error
Facility LOG_AUTH
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)

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.
Severity error
Facility LOG_AUTH
KMD_PM_PROTO_INVALID
System Log Message Invalid protocol protocol-id was negotiated for SA sa-name
Description 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.
Severity error
Facility LOG_AUTH
KMD_PM_PROTO_IPCOMP_UNSUPPORTED
System Log Message Unsupported IPComp protocol was negotiated for SA sa-name
Description 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.
Severity error
Facility LOG_AUTH
KMD_PM_PROTO_ISAKMP_RESV_UNSUPP
System Log Message Unsupported protocol ISAKMP or RESERVED was negotiated for SA sa-name
Description 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.
Severity error
Facility LOG_AUTH
KMD_PM_SA_CFG_NOT_FOUND
System Log Message SA sa-name configuration not found

Description 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.
Severity error
Facility LOG_AUTH
KMD_PM_SA_ESTABLISHED
System Log Message Local gateway: local-address, Remote gateway: remote-address, Local ID: local-initiator,
Remote ID: remote-responder, Direction: argument1, SPI: index1, AUX-SPI: index2, Mode:
mode, Type: type
Description A security association has ben established
Severity info
Facility LOG_SYSLOG
KMD_PM_SA_INDEX_GEN_FAILED
System Log Message Unable to generate pair index for SA sa-name in service set service-set
Description 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.
Severity error
Facility LOG_AUTH
KMD_PM_SA_PEER_ABSENT
System Log Message No active peer found in tunnel configuration block sa-name
Description Failed to find active peer information in the tunnel configuration block. Hence unable to
send SA delete notifications to the peer.
Severity error
Facility LOG_SYSLOG
KMD_PM_SA_PEER_NOT_FOUND
System Log Message Unable to find active peer for SA sa-name

Description 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.
Severity error
Facility LOG_AUTH
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
Description The SPI size in the delete notification is invalid. Hence delete request is rejected. Quick
Mode notification payload is dropped.
Severity error
Facility LOG_SYSLOG
KMD_PM_UNEQUAL_PAYLOAD_LENGTH
System Log Message Inconsistent payload lengths in Quick Mode responder life time notification from
Description IKE Quick Mode notification is dropped because of unequal payload length received in
the message.
Severity error
Facility LOG_SYSLOG
KMD_PM_UNINITIALISE_ERROR
System Log Message Invalid policy managerhandle to uninitialize service-set
Description Failed to uninitialize the Policy manager object while deleting the indicated service set.
Severity error
Facility LOG_SYSLOG
KMD_PM_UNINITIALIZE_FAILED
System Log Message Unable to uninitialize service set service-set: invalid policy manager handle
Description 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.

Severity error
Facility LOG_AUTH
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
Description Phase-1 negotiation can not be started because either the local gateway identity or the
remote gateway identity is unknown.
Severity error
Facility LOG_SYSLOG
KMD_PM_UNKNOWN_PHASE2_ENTITIES
System Log Message No Phase-2 entities present in tunnel configuration block sa-name
Description 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.
Severity error
Facility LOG_SYSLOG
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
Description The notification message sent by the indicated remote gateway and remote port is not
recognized. Hence Quick Mode notification payload is dropped.
Severity error
Facility LOG_SYSLOG
KMD_PM_UNSUPPORTED_KEY
System Log Message Key type = type, not supported
Description The specified key type is unsupported. Public/Private and Pre-shared key are are the
only types supported presently.

Severity error
Facility LOG_SYSLOG
KMD_PM_UNSUPPORTED_MODE
System Log Message New group mode not supported currently
Description The IKE New Group mode negotiations failed, because this is not a supported feature
currently.
Severity error
Facility LOG_SYSLOG
KMD_SNMP_EXTRA_RESPONSE
System Log Message PIC pic-slot sent additional response after reply to SNMP query: error-message
Description The indicated 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.
Severity error
Facility LOG_AUTH
KMD_SNMP_FATAL_ERROR
System Log Message Fatal SNMP error occurred: error-message
Description 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.
Severity error
Facility LOG_AUTH
KMD_SNMP_MALLOC_FAILED
System Log Message Unable to allocate memory for reply buffer; SNMP query to PIC pic-slot failed
Description 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 PIC.

Severity error
Facility LOG_AUTH
KMD_SNMP_PIC_CONNECTION_FAILED
System Log Message Unable to connect to PIC pic-slot; SNMP query failed
Description The key management process (kmd) could not open a connection to the indicated PIC.
As a result, it could not retrieve Simple Network Management Protocol (SNMP) statistics
about IP Security (IPSec) security associations (SAs).
Severity error
Facility LOG_AUTH
KMD_SNMP_PIC_NO_RESPONSE
System Log Message PIC pic-slot did not respond to SNMP query: error-message
Description The indicated 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).
Severity error
Facility LOG_AUTH

KMD_SNMP_PIC_SLOT_NOT_FOUND
System Log Message Unable to retrieve slot information for PIC pic-slot; SNMP query failed
Description The key management process (kmd) could not retrieve information about the slot housing
the indicated PIC. As a result, it could not retrieve Simple Network Management Protocol
(SNMP) statistics about IP Security (IPSec) security associations (SAs) from the PIC.
Severity error
Facility LOG_AUTH
KMD_VPN_DFBIT_STATUS_MSG
System Log Message The DF-BIT for VPN vpn-name has been set to argument.
Description VPN DF bit status has been set.

Severity info
Facility LOG_DAEMON
KMD_VPN_DOWN_ALARM_USER
System Log Message VPN vpn-name from remote-address is down.
Description Notifiication to user that VPN monitor detects IPSec SA is down.
Severity info
Facility LOG_DAEMON
KMD_VPN_PV_LIFETIME_CHANGED
System Log Message Config key lifetime changed
Description The key lifetime has been changed by a user.
Severity info
Facility LOG_DAEMON
KMD_VPN_PV_PHASE1
System Log Message IKE Phase-1 Failure: source-address [spi=destination-address, src_ip=error-message,
dst_ip=data]
Description The threshold value set has been reached due to several ike-phase1 failures that have
occurred.
Severity error
Facility LOG_DAEMON
KMD_VPN_PV_PHASE2
System Log Message IKE Phase-2 Failure: source-address [spi=destination-address, src_ip=error-message,
dst_ip=data]
Description The threshold value set has been reached due to several ike-phase2 failures that have
occurred.
Severity error
Facility LOG_DAEMON
KMD_VPN_PV_PSK_CHANGED
System Log Message Pre-shared key changed

Description The pre-shared key has been changed by a user.
Severity info
Facility LOG_DAEMON
KMD_VPN_UP_ALARM_USER
System Log Message VPN vpn-name from remote-address is up.
Description Notifiication to user that VPN monitor detects IPSec SA is up.
Severity info
Facility LOG_DAEMON


CHAPTER 63
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_BD_CREATE_FAILURE
System Log Message BD bridge-domain creation failed. Attempting to recover after some interval
Description The Layer 2 address learning process (l2ald) failed to create BD in kernel. This can happen
when kernel cannot allocate BD due to temporary resource exhaustion or due to over
configuration. The first case is automatically handled by l2ald. The latter case can be
recovered from by removing configurations which are beyond platform limitations
Severity warning
Facility LOG_DAEMON
L2ALD_BD_CREATE_RETRY_SUCCESS
System Log Message BD bridge-domain creation suceeded after retry-count retries.
Description The Layer 2 address learning process (l2ald) successfully recovered from intial BD creation
that failed. The initial failure could have been becuase of temporary resource exhaustion
in kernel or due to over configuration. The retry mechanism has receovered sucessfully
from that state
Severity warning
Facility LOG_DAEMON

L2ALD_BD_NAME_RESTRICTION
System Log Message Reserved character '/' is not allowed as part of bridge-domain(bridge-domain) name.
Any firewall filter applied to this bridge-domain might fail to work.
Description firewall filter will not work for restricted BD name
Severity warning
Facility LOG_DAEMON
L2ALD_DEFAULT_VLAN_DISABLED
System Log Message Internal vlan "bridge-domain/default" creation failed.!!
Description Default vlan feature has been disabled due to an exsisting vlan configuration with vlan-id
1.
Severity warning
Facility LOG_DAEMON
Action explicit configuration of vlan by name default or removal of the vlan configured with
vlan-id 1.
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
Description The l2 learning process (l2ald) already has this particular BEB mac existing for a different
PBBN ID.
Severity error
Facility LOG_DAEMON
L2ALD_FREE_MAC_FAILED
System Log Message ERROR:error-message
Description Before a MAC address is freed from system, it is removed from all lists and the kernel.
Due to unexpected events, a mac about to be freed is found to be still in a list

Chapter 63: L2ALD System Log Messages
Severity warning
Facility LOG_DAEMON
Cause Unexpected sequence of events or loops in the topology or some kind of misconfiguration.
L2ALD_GENCFG_OP_FAILED
System Log Message Unable to complete gencfg operation operation (major type, minor subtype): error-message
Description 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.
Severity error
Facility LOG_DAEMON
L2ALD_IFBD_COUNT_EXCEED
System Log Message warning-message ; current count is count
Description When max number of ifbd / vmmember supported exceed due to user configuration,
warning message will be generated.
Severity error
Facility LOG_DAEMON
L2ALD_IPC_MESSAGE_ERROR
System Log Message Message (type message-type, subtype message-subtype, opcode message-opcode)
received with error error-message
Description The Layer 2 address learning process (l2ald) detected an error in an interprocess
communication (IPC) message with the indicated characteristics.
Severity error
Facility LOG_DAEMON
L2ALD_IPC_MESSAGE_INVALID
System Log Message Invalid message received (message type message, subtype message-type):
message-subtype

Description The Layer 2 address learning process (l2ald) received a message with the indicated
characteristics. The message was invalid for the indicated reason.
Severity error
Facility LOG_DAEMON
L2ALD_IPC_MESSAGE_SEND_FAILED
System Log Message Unable to send IPC message to peer-name identifier
Description The Layer 2 address learning process (l2ald) could not send an interprocess
communication (IPC) message to the indicated Layer 2 peer.
Severity warning
Facility LOG_DAEMON
L2ALD_IPC_PIPE_WRITE_ERROR
System Log Message Unable to write on pipe: error-message
Description The Layer 2 address learning process (l2ald) could not write to an interprocess
communication (IPC) pipe for the indicated reason.
Severity error
Facility LOG_DAEMON
Cause One possible reason is that there was no reader for the pipe.
L2ALD_MAC_LIMIT_EXCEEDED_BD
System Log Message Limit on learned MAC addresses exceeded for routing instance 'routing-instance', domain
'bridge-domain:vlan-id'; mac-limit is count mac-address THE PACKET with mac-address
of drop-packet
Description The Layer 2 address learning process (l2ald) stopped adding addresses to the MAC
address table that were learned by interfaces in the indicated bridge-domain, because
the indicated count of learned addresses exceeds the limit configured or default limit for
the bridge-domain.

Severity error
Facility LOG_DAEMON
Action Increase the limit on addresses learned by interfaces in the bridge-domain, by increasing
the value of the 'mac-table-size' statement at the [edit vlans <vlan-name>
switch-options] hierarchy level.
L2ALD_MAC_LIMIT_EXCEEDED_BLOCK
System Log Message Limit on learned MAC addresses exceeded for interface-name; current count is count
SHUTTING THE INTERFACE
Description The Layer 2 address learning process (l2ald) blocked the indicated interface, because
the indicated count of learned addresses exceeds the limit configured for the interface.
Severity error
Facility LOG_DAEMON
Action 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.
L2ALD_MAC_LIMIT_EXCEEDED_IF
mac-address THE PACKET with mac address: drop-packet
address table that were learned by the indicated interface, because the indicated count
of learned addresses exceeds the limit configured for the interface.
Severity error
Facility LOG_DAEMON
hierarchy level.

L2ALD_MAC_LIMIT_EXCEEDED_IFBD
mac-address THE PACKET with mac address: drop-packet
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.
Severity error
Facility LOG_DAEMON
hierarchy level.
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
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.
Severity error
Facility LOG_DAEMON
Action 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.
L2ALD_MAC_LIMIT_REACHED_GLOBAL
System Log Message Global limit on learned MAC addresses reached; current count is count
address table, because the indicated count of learned addresses exceeds the limit for
the router.
Severity warning

Facility LOG_DAEMON
Action 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.
L2ALD_MAC_LIMIT_REACHED_IF
System Log Message Limit on learned MAC addresses reached for interface-name; current count is count
of learned addresses exceeds the limit configured for the interface.
Severity warning
Facility LOG_DAEMON
hierarchy level.
L2ALD_MAC_LIMIT_REACHED_IFBD
System Log Message Limit on learned MAC addresses reached for interface-name; current count is count
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.
Severity warning
Facility LOG_DAEMON
hierarchy level.
L2ALD_MAC_LIMIT_REACHED_RTT
System Log Message Limit on learned MAC addresses reached for routing instance 'routing-instance'; current
count is count
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.
Severity error
Facility LOG_DAEMON
Action 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
Description The Layer 2 address learning process (l2ald) resumed adding addresses to the MAC
the indicated count of learned addresses no longer exceeds the limit configured for the
domain.
Severity warning
Facility LOG_DAEMON
Cause 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_GLOBAL
System Log Message Resumed adding MAC addresses for router; current count is count
address table, because the indicated count of learned addresses no longer exceeds the
configured limit.
Severity warning
Facility LOG_DAEMON
L2ALD_MAC_LIMIT_RESET_IF
System Log Message Resumed adding MAC addresses learned by interface-name; current count is count

of learned addresses no longer exceeds the limit configured for the interface.
Severity warning
Facility LOG_DAEMON
L2ALD_MAC_LIMIT_RESET_RTT
System Log Message Resumed adding MAC addresses learned from routing instance 'routing-instance'; current
count is count
the indicated count of learned addresses no longer exceeds the limit configured for the
instance.
Severity warning
Facility LOG_DAEMON
L2ALD_MAC_MOVE_EXCEEDED_BD
System Log Message Limit on MAC moves exceeded at VLAN bridge-domainfor MAC mac-address moved from
interface interface-name to interface interface-name1;Mac move limit is count. drop-packet
THE PACKET
Description 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 beyond the
configured value, an error is sent
Severity error
Facility LOG_DAEMON
Cause The probable reason for mac moves is the loops in the topology or some kind of
misconfiguration.

L2ALD_MAC_MOVE_EXCEEDED_BD_ACTION_NONE
System Log Message Limit on MAC moves exceeded at VLAN bridge-domainfor MAC mac-address moved from
interface interface-name to interface interface-name1;Mac move limit is count. No action
( Forwarding the packet)
but a different unit number, it is considered a MAC move. When this happens beyond the
configured value, an error is sent
Severity error
Facility LOG_DAEMON
misconfiguration.
L2ALD_MAC_MOVE_NOTIFICATION
System Log Message MAC Moves detected in the system
but a different unit number, it is considered a MAC move. When this happens frequently
for a specific time duration, a notification is sent
Severity warning
Facility LOG_DAEMON
misconfiguration.
L2ALD_MAC_MOVE_NOTIF_ACTION
System Log Message MAC move error-message
for a specific time duration, and bridge domain has action enabled, the IFL on which the
mac is learnt last is blocked for the bridge domain. A notification is sent with
blocking/unblocking event, Offending MAC(for blocking), IFL name and bridge domain.
Severity notice
Facility LOG_DAEMON
misconfiguration. The blocking action is taken to stop the loop for a configurable duration.

L2ALD_MAC_MOVE_NOTIF_EXTENSIVE
System Log Message MAC move error-message
for a specific time duration, a notification is sent with details on the interface,
bridge-domain.
Severity warning
Facility LOG_DAEMON
misconfiguration. This message is invoked based on the user configurable knob
L2ALD_MAC_MOVE_SHUTDOWN
System Log Message Shutting down the interface bridge-domain. Detected excessive mac moves for MAC
mac-address in vlan interface-name from interface interface-name1 ;Mac move limit is
count.
for a specific time duration, a notification is sent with details on the interface,
bridge-domain.
Severity error
Facility LOG_DAEMON
misconfiguration.
L2ALD_MALLOC_FAILED
System Log Message Unable to allocate memory: error-message
Description The Layer 2 address learning process (l2ald) could not allocate memory while creating
a data structure.
Severity error
Facility LOG_DAEMON

L2ALD_MANAGER_CONNECT
System Log Message Unable to create pipe to Layer 2 address-learning manager: error-message
Description The Layer 2 address learning process (l2ald) could not open a pipe for interprocess
communication (IPC) with a Layer 2 address-learning manager process.
Severity error
Facility LOG_DAEMON
L2ALD_NAME_LENGTH_IF_DEVICE
System Log Message Unable to add interface device interface-name; name exceeds limit of length characters
Description 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.
Severity error
Facility LOG_DAEMON
L2ALD_NAME_LENGTH_IF_FAMILY
System Log Message Unable to add interface family interface-family; name exceeds limit of length characters
Description 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.
Severity error
Facility LOG_DAEMON
L2ALD_NAME_LENGTH_IF_LOGICAL
System Log Message Unable to add logical interface interface-name; name exceeds limit of length characters
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.

Severity error
Facility LOG_DAEMON
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.
Description The Layer 2 address learning process (l2ald) could not initialize the interface for the
provider backbone bridging (PBB) feature because the interface was on a revision A card.
Severity warning
Facility LOG_DAEMON
Cause Revision A cards do not support provider backbone bridging (PBB) features.
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.
Description 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.
Severity warning
Facility LOG_DAEMON
Cause The interface is no longer present on the revision A card.
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.
Description 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.

Severity warning
Facility LOG_DAEMON
Cause An interface was discovered on the revision A card. Revision A cards do not support
provider backbone bridging (PBB) features.
L2ALD_PIP_IFD_READ_RETRY
System Log Message Retry count exceeded trying to read pip-interface from the kernel. Retry count is retry-count
Description The Layer 2 address learning process (l2ald) could not read the provide-in-provider
interface (pip0) interface from the kernel.
Severity critical
Facility LOG_DAEMON
Cause The chassis process may have been too slow in creating the interface.
L2ALD_RPD_LR_ALLOC_FAILED
System Log Message Unable to allocate context data for rpd connection
Description The Layer 2 Address learning Protocol process (l2ald) could not allocate a memory for
context information while attempting to initialize a connection to the routing protocol
process (rpd).
Severity error
Facility LOG_DAEMON
L2ALD_RPD_SESS_CREATE_FAILED
System Log Message Unable to establish session with rpd (error-code)
Description The Layer 2 Address learning Protocol process (l2ald) could not establish a session with
the routing protocol process (rpd).
Severity error
Facility LOG_DAEMON

L2ALD_RPD_SESS_HANDLE_ALLOC_FAIL
System Log Message Unable to allocate session handle for rpd connection: error-message (error-code)
Description The Layer 2 Address learning Protocol process (l2ald) could not allocate a session handle
while attempting to initialize a connection to the routing protocol process (rpd).
Severity error
Facility LOG_DAEMON
L2ALD_RPD_SOCKET_ALLOC_FAILED
System Log Message Unable to allocate socket address for rpd connection
Description The Layer 2 Address learning Protocol process (l2ald) could not allocate a socket address
structure while attempting to initialize a connection to the routing protocol process (rpd).
Severity error
Facility LOG_DAEMON
L2ALD_RPD_STATE_ALLOC_FAILED
System Log Message Unable to allocate l2ald rpd state
Description The Layer 2 Address learning Protocol process (l2ald) could not allocate a memory for
l2ald rpd state information while attempting to initialize a connection to the routing
protocol process (rpd).
Severity error
Facility LOG_DAEMON
L2ALD_RPD_VERSION_MISMATCH
System Log Message Versions of rpd and librpd did not match; not retrying
Description The Layer 2 Address learning Protocol process (l2ald) 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.
Severity error
Facility LOG_DAEMON
L2ALD_ST_CTL_DISABLED
System Log Message interface-name: storm control disabled port

Description This condition occurs when storm control condition is detected.
Severity alert
Facility LOG_DAEMON
L2ALD_ST_CTL_ENABLED
System Log Message interface-name: storm control enabled port
Description This condition occurs when storm-control condition is cleared.
Severity alert
Facility LOG_DAEMON
L2ALD_ST_CTL_IN_EFFECT
System Log Message interface-name: storm control in effect on the port
Description This condition occurs when storm control condition is detected.
Severity alert
Facility LOG_DAEMON

CHAPTER 64
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_KERNEL_VERSION
System Log Message Kernel version (kernel-version) of routing sockets was not required version (l2cpd-version)
Description 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.
Severity error
Facility LOG_DAEMON
Action Upgrade the kernel package.
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)
Description The Layer 2 Control Protocol process (l2cpd) determined that the kernel supports an
indicated older version of the indicated routing socket message type than it requires.
Severity error
Facility LOG_DAEMON
L2CPD_KERNEL_VERSION_UNSUPP
System Log Message Kernel version of routing socket message type 'message-type' was not required version
(l2cpd-version)
Description 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.

Severity error
Facility LOG_DAEMON
L2CPD_MIRROR_ERROR
Description The Layer 2 Control Protocol process (l2cpd) could not establish the mirror connection
(which supports nonstop routing) between the master and backup Routing Engines.
Severity warning
Facility LOG_DAEMON
Cause The master and backup Routing Engines are running incompatible versions of the JUNOS
software.
Action Update the JUNOS software to compatible versions on the master and backup Routing
Engines.
L2CPD_MIRROR_VERSION_MISMATCH
Description 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.
Severity warning
Facility LOG_DAEMON
Action Update the JUNOS software to compatible versions on the master and backup Routing
Engines.
L2CPD_PPM_READ_ERROR
Description The Layer 2 Control Protocol process (l2cpd) could not read a message available on the
read pipe from the periodic packet management process (ppmd).
Severity error

Chapter 64: L2CPD System Log Messages
Facility LOG_DAEMON
L2CPD_PPM_WRITE_ERROR
Description The Layer 2 Control Protocol process (l2cpd) could not write a message on the pipe to
the periodic packet management process (ppmd).
Severity error
Facility LOG_DAEMON
L2CPD_XSTP_SHUTDOWN_FAILED
System Log Message Unable to shut down error-message module
Description 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.
Severity error
Facility LOG_DAEMON


CHAPTER 65
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
Description 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.
Severity error
Facility LOG_NEWS
Action Remove the CoS profile from the RADIUS database or contact your technical support
representative.
L2TPD_COS_PROFILE_DELETE
System Log Message Unable to delete CoS profile (L2TP tunnel tunnel-id, session session-id): error-message
Description 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.
Severity error
Facility LOG_NEWS
Action Remove the CoS profile from the RADIUS database or contact your technical support
representative.

L2TPD_DB_ADD_FAILED
System Log Message Unable to add node for node-name to internal database
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_DB_DELETE_FAILED
System Log Message Unable to delete node for node-name from internal database
configuration database in memory. It could not delete the indicated node to the in-memory
database.
Severity error
Facility LOG_NEWS
L2TPD_DB_INIT_FAILED
System Log Message Unable to initialize root node object-name in internal database: error-message
configuration database in memory. It could not initialize the root node for the indicated
object in the in-memory database.
Severity error
Facility LOG_NEWS
L2TPD_DB_TUN_GRP_ALLOC_FAILED
System Log Message Unable to allocate memory for tunnel group
Description The Layer 2 Tunneling Protocol process (l2tpd) could not allocate memory for the data
structure used to record tunnel group information.
Severity error
Facility LOG_NEWS

Chapter 65: L2TPD System Log Messages
L2TPD_DEFAULT_PROTO_CREATE_FAIL
System Log Message Unable to create default L2TP module
Description The Layer 2 Tunneling Protocol process (l2tpd) could not create a default L2TP module.
Severity error
Facility LOG_NEWS
L2TPD_EVLIB_CREATE_FAILED
System Log Message Unable to create event context: error-message
Description The Layer 2 Tunneling Protocol process (l2tpd) could not create a context for handling
asynchronous events.
Severity emergency
Facility LOG_NEWS
L2TPD_EVLIB_FD_DEREGISTER_FAILED
System Log Message Unable to deregister file descriptor: not registered
Description The Layer 2 Tunneling Protocol process (l2tpd) could not deregister a file descriptor,
because it did not exist.
Severity error
Facility LOG_NEWS
L2TPD_EVLIB_FD_DESELECT_FAILED
System Log Message Unable to deselect file descriptor: error-message
Description The Layer 2 Tunneling Protocol process (l2tpd) could not deselect a file descriptor.
Severity error
Facility LOG_NEWS
L2TPD_EVLIB_FD_NOT_REGISTERED
System Log Message No file descriptor registered
Description The Layer 2 Tunneling Protocol process (l2tpd) could not find a registered file descriptor
while attempting to set an event mask.

Severity error
Facility LOG_NEWS
L2TPD_EVLIB_FD_SELECT_FAILED
System Log Message Unable to select file descriptor for events event-id: error-message
Description The Layer 2 Tunneling Protocol process (l2tpd) could not select the file descriptor for
the indicated events.
Severity error
Facility LOG_NEWS
L2TPD_EVLIB_TIMER_CLEAR_FAILED
System Log Message Unable to clear event timer: error-message
Description The Layer 2 Tunneling Protocol process (l2tpd) could not clear an event timer for the
indicated reason.
Severity error
Facility LOG_NEWS
L2TPD_EVLIB_TIMER_SET_FAILED
System Log Message Unable to set event timer: error-message
Description The Layer 2 Tunneling Protocol process (l2tpd) could not set an event timer for the
indicated reason.
Severity error
Facility LOG_NEWS
L2TPD_FILTER_FILE_OPEN_FAILED
System Log Message Unable to open file filename
Description The Layer 2 Tunneling Protocol process (l2tpd) could not open the indicated filter file.
Severity error
Facility LOG_NEWS

L2TPD_GLOBAL_CFG_ADD_FAILED
System Log Message Unable to add global configuration for PIC pic-slot (errno error-code)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not add the global configuration
for the indicated PIC.
Severity error
Facility LOG_NEWS
L2TPD_GLOBAL_CFG_CHANGE_FAILED
System Log Message Unable to change global configuration for PIC pic-slot (errno error-code)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not change the global configuration
Severity error
Facility LOG_NEWS
L2TPD_GLOBAL_CFG_DELETE_FAILED
System Log Message Unable to delete global configuration for PIC pic-slot (errno error-code)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not delete the global configuration
Severity error
Facility LOG_NEWS
L2TPD_IFD_ADD_FAILED
System Log Message function-name: unable to add interface device interface-name
configuration database in memory. It could not add the indicated interface device to the
in-memory database.
Severity error
Facility LOG_NEWS
L2TPD_IFD_DELETE_FAILED
System Log Message function-name: unable to delete interface device interface-name

configuration database in memory. It could not delete the indicated interface device from
the in-memory database.
Severity error
Facility LOG_NEWS
L2TPD_IFD_MSG_REGISTER_FAILED
System Log Message Unable to register message handler for interface device: error-message
Description The Layer 2 Tunneling Protocol process (l2tpd) could not register an interface device
message handler.
Severity error
Facility LOG_NEWS
L2TPD_IFD_ROOT_ALLOC_FAILED
System Log Message Unable to allocate memory for interface device root node: error-message
configuration database in memory. It could not allocate memory in the in-memory
database for the root node for an interface device.
Severity error
Facility LOG_NEWS
L2TPD_IFL_ADD_FAILED
System Log Message function-name: unable to add interface interface-name
configuration database in memory. It could not add the indicated logical interface to the
in-memory database.
Severity error
Facility LOG_NEWS
L2TPD_IFL_DELETE_FAILED
System Log Message function-name: unable to delete interface interface-name

configuration database in memory. It could not delete the indicated logical interface
from the in-memory database.
Severity error
Facility LOG_NEWS
L2TPD_IFL_MSG_REGISTER_FAILED
System Log Message Unable to register message handler for interface: error-message
Description The Layer 2 Tunneling Protocol process (l2tpd) could not register a logical interface
message handler.
Severity error
Facility LOG_NEWS
L2TPD_IFL_NOT_FOUND
System Log Message Unable to find logical interface (L2TP tunnel tunnel-id, session session-id)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not retrieve a logical interface in
the indicated tunnel and session.
Severity error
Facility LOG_NEWS
L2TPD_IFL_ROOT_ALLOC_FAILED
System Log Message Unable to allocate memory for interface root node: error-message
configuration database in memory. It could not allocate memory in the in-memory
database for the root node for a logical interface.
Severity error
Facility LOG_NEWS
L2TPD_INSTANCE_CREATE_FAILED
System Log Message Unable to create L2TP instance tunnel-group
Description The Layer 2 Tunneling Protocol process (l2tpd) could not create an L2TP instance for
the indicated tunnel group.

Severity error
Facility LOG_NEWS
L2TPD_INSTANCE_RESTART_FAILED
System Log Message Unable to trigger restart of L2TP instance tunnel-group
Description The Layer 2 Tunneling Protocol process (l2tpd) could not restart the L2TP instance for
the indicated tunnel group.
Severity error
Facility LOG_NEWS
L2TPD_INTERFACE_ID_NOT_FOUND
System Log Message Unable to find interface ID interface-name
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_MESSAGE_REGISTER_FAILED
System Log Message Unable to register L2TP message handler: error-message
Description The Layer 2 Tunneling Protocol process (l2tpd) could not register an L2TP message
handler.
Severity error
Facility LOG_NEWS
L2TPD_MLPPP_BUNDLE_ALLOC_FAILED
System Log Message Unable to allocate MLPPP bundle
Description The Layer 2 Tunneling Protocol process (l2tpd) could not allocate memory for a multilink
Point-to-Point Protocol (MLPPP) bundle.
Severity error
Facility LOG_NEWS

L2TPD_MLPPP_BUNDLE_CREATE_FAILED
System Log Message Unable to create MLPPP bundle (L2TP tunnel tunnel-id, session session-id)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not create a multilink Point-to-Point
Protocol (MLPPP) bundle in the indicated tunnel and session.
Severity error
Facility LOG_NEWS
L2TPD_MLPPP_BUNDLE_INVALID_ID
System Log Message MLPPP bundle ID was invalid
Description The identifier assigned to a multilink Point-to-Point Protocol (MLPPP) bundle was invalid.
Severity error
Facility LOG_NEWS
L2TPD_MLPPP_COPY_CFG_FAILED
System Log Message Unable to copy MLPPP configuration (L2TP tunnel tunnel-id, session session-id)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not copy the multilink Point-to-Point
Protocol (MLPPP) configuration for the indicated tunnel and session.
Severity error
Facility LOG_NEWS
L2TPD_MLPPP_ID_ALLOC_FAILED
System Log Message Unable to allocate MLPPP ID map
Description The Layer 2 Tunneling Protocol process (l2tpd) could not allocate memory for a multilink
Point-to-Point Protocol (MLPPP) identifier map data structure.
Severity error
Facility LOG_NEWS
L2TPD_MLPPP_ID_BITMAP_ALLOC_FAIL
System Log Message Unable to allocate bitmap field for MLPPP ID map
Description The Layer 2 Tunneling Protocol process (l2tpd) could not allocate memory for a bitmap
field in a multilink Point-to-Point Protocol (MLPPP) identifier map data structure.

Severity error
Facility LOG_NEWS
L2TPD_MLPPP_ID_NODE_ADD_FAILED
System Log Message Unable to add node for bundle bundle to MLPPP ID map
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_MLPPP_ID_ROOT_ALLOC_FAILED
System Log Message Unable to allocate root node for MLPPP ID map
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_MLPPP_LINK_CREATE_FAILED
System Log Message Unable to create MLPPP bundle links (L2TP tunnel tunnel-id, session session-id)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not create multilink Point-to-Point
Protocol (MLPPP) bundle links for the indicated tunnel and session.
Severity error
Facility LOG_NEWS
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)
Description 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.
Severity error

Facility LOG_NEWS
L2TPD_MLPPP_POOL_ADDRESS_FAILED
System Log Message Unable to assign pool address for MLPPP bundle bundle (L2TP tunnel tunnel-id, session
session-id)
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_MLPPP_SESSION_CREATE_FAIL
System Log Message Unable to create MLPPP session (L2TP tunnel tunnel-id, session session-id)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not create a multilink Point-to-Point
Protocol (MLPPP) session for the indicated tunnel and session.
Severity error
Facility LOG_NEWS
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)
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_MLPPP_SPEED_MISMATCH
System Log Message Unable to add link: speed differs for bundle bundle (L2TP tunnel tunnel-id, session
session-id)
Description 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.
Severity error

Facility LOG_NEWS
L2TPD_NH_DELETE_FAILED
System Log Message Unable to delete next hop next-hop
Description The Layer 2 Tunneling Protocol process (l2tpd) could not delete the indicated next hop.
Severity error
Facility LOG_NEWS
L2TPD_POLICER_ADD_FAILED
System Log Message Unable to add policer filter-name (L2TP tunnel tunnel-id, session session-id):
error-message
Description 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.
Severity error
Facility LOG_NEWS
Action 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
Description 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.
Severity error
Facility LOG_NEWS
Action Remove the policer profile from the RADIUS database or contact your technical support
representative.
L2TPD_POOL_ADDRESS_FAILED
System Log Message Unable to assign pool address (L2TP tunnel tunnel-id, session session-id)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not assign a pool address in the
indicated tunnel and session.

Severity error
Facility LOG_NEWS
L2TPD_POOL_ASSIGN_ADDRESS_FAILED
System Log Message Unable to assign L2TP pool address: pool pool-name is invalid or has no free addresses
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_PPP_ROUTE_ADD_FAILED
System Log Message Unable to add PPP peer route (L2TP tunnel tunnel-id, session session-id)
configuration database in memory. It could not add information about a Point-to-Point
Protocol (PPP) peer route to the in-memory configuration for the indicated tunnel and
session.
Severity error
Facility LOG_NEWS
L2TPD_PPP_ROUTE_DELETE_FAILED
System Log Message Unable to remove PPP peer route (L2TP tunnel tunnel-id, session session-id)
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.
Severity error
Facility LOG_NEWS
L2TPD_PROFILE_NOT_FOUND
System Log Message Profile profile-name not found
Description The Layer 2 Tunneling Protocol process (l2tpd) could not locate an access profile from
the configuration in order to find radius servers to authenticate.
Severity error

Facility LOG_NEWS
L2TPD_PROFILE_NO_RADIUS_SERVERS
System Log Message Can't find radius servers for profile 'profile-name
Description The Layer 2 Tunneling Protocol process (l2tpd) could not locate any radius servers for
the configured access profile.
Severity error
Facility LOG_NEWS
L2TPD_RADIUS_ACCT_PORT_ZERO
System Log Message RADIUS server accounting port is zero
Description The Layer 2 Tunneling Protocol process (l2tpd) determined that the RADIUS server
accounting port is zero, which is not a valid value.
Severity error
Facility LOG_NEWS
L2TPD_RADIUS_GETHOSTNAME_FAILED
Description The Layer 2 Tunneling Protocol process (l2tpd) could not obtain a hostname for an
outgoing RADIUS message.
Severity error
Facility LOG_NEWS
L2TPD_RADIUS_RT_INST_ENOENT
System Log Message Ignoring RADIUS server radius-server: routing instance routing-instance did not exist
Description 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.
Severity notice
Facility LOG_NEWS
L2TPD_RADIUS_RT_INST_NOT_FOUND
System Log Message Ignoring RADIUS server radius-server: unable to retrieve routing instance routing-instance
(error-message)

because it could not retrieve the indicated routing instance specified for the server.
Severity error
Facility LOG_NEWS
L2TPD_RADIUS_SERVER_NOT_FOUND
System Log Message Unable to find RADIUS server (tunnel tunnel-id, session session-id)
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_RADIUS_SRC_ADDR_BIND_FAIL
System Log Message Ignoring RADIUS server radius-server: unable to bind to source address source-address
(error-message)
because it could not bind to the indicated source address.
Severity error
Facility LOG_NEWS
L2TPD_RADIUS_SRC_ADDR_ENOENT
System Log Message Ignoring RADIUS server radius-server: source address source-address did not exist
because the indicated source address did not exist in the routing instance for the server.
Severity notice
Facility LOG_NEWS
L2TPD_RPD_ASYNC_UNREG_FAILED
System Log Message Unable to unregister with rpd (return-value)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not unregister asynchronously with

Severity error
Facility LOG_NEWS
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
Description 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.
Severity error
Facility LOG_NEWS
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)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not add a route for the indicated
address and prefix, gateway, tunnel, and session.
Severity error
Facility LOG_NEWS
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
Description 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.
Severity error
Facility LOG_NEWS
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)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not delete a route for the indicated
address and prefix, gateway, tunnel, and session.
Severity error

Facility LOG_NEWS
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)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not add a route for the indicated
address and prefix, tunnel, and session.
Severity error
Facility LOG_NEWS
L2TPD_RPD_SESS_CREATE_FAILED
System Log Message Unable to establish session with rpd (error-code)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not establish a session with the
routing protocol process (rpd).
Severity error
Facility LOG_NEWS
L2TPD_RPD_SESS_HANDLE_ALLOC_FAIL
System Log Message Unable to allocate session handle for rpd connection: error-message (error-code)
Description 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).
Severity error
Facility LOG_NEWS
L2TPD_RPD_SOCKET_ALLOC_FAILED
System Log Message Unable to allocate socket address for rpd connection
Description 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).
Severity error
Facility LOG_NEWS
L2TPD_RPD_TBL_LOCATE_BY_NAME
System Log Message Unable to locate rpd table by name: error-message (error-code)

Description The Layer 2 Tunneling Protocol process (l2tpd) attempted to retrieve a routing protocol
process table by providing the table name. The attempt failed.
Severity error
Facility LOG_NEWS
L2TPD_RPD_TBL_LOCATE_FAILED
System Log Message Unable to locate table table-name for identifier (return-value)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not retrieve the indicated routing
protocol process table.
Severity error
Facility LOG_NEWS
L2TPD_RPD_VERSION_MISMATCH
System Log Message Versions of rpd and librpd did not match; not retrying
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_RTSLIB_ASYNC_OPEN_FAILED
System Log Message Unable to open asynchronous routing socket connection
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_RTSLIB_OPEN_FAILED
System Log Message Unable to open routing socket connection
Description The Layer 2 Tunneling Protocol process (l2tpd) could not open a routing socket
connection, which it uses to communicate with the Junos operating system kernel.

Severity error
Facility LOG_NEWS
L2TPD_SERVER_START_FAILED
System Log Message Startup of L2TP server failed
Description The Layer 2 Tunneling Protocol (L2TP) server did not start.
Severity error
Facility LOG_NEWS
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)
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.
Severity error
Facility LOG_NEWS
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)
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.
Severity error
Facility LOG_NEWS
L2TPD_SESSION_CFG_ADD_ERROR
System Log Message Unable to add L2TP tunnel tunnel-id, session session-id to PIC configuration (errno
error-code)
configuration database in memory. It could not add information about the indicated
session and tunnel to the in-memory configuration for the PIC.

Severity error
Facility LOG_NEWS
L2TPD_SESSION_CFG_ADD_FAILED
System Log Message Unable to add L2TP tunnel tunnel-id, session session-id to PIC configuration
session and tunnel to the in-memory configuration for the PIC.
Severity error
Facility LOG_NEWS
L2TPD_SESSION_CFG_DELETE_FAILED
System Log Message Unable to remove L2TP tunnel tunnel-id, session session-id from PIC configuration
session and tunnel from the in-memory configuration for the PIC.
Severity error
Facility LOG_NEWS
L2TPD_SESSION_DELETE_FAILED
System Log Message Unable to delete session (L2TP tunnel tunnel-id, session session-id, errno error-code)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not delete information about the
Severity error
Facility LOG_NEWS
L2TPD_SESSION_IFF_NOT_FOUND
System Log Message Unable to find family structure for interface interface-name (L2TP tunnel tunnel-id,
session session-id)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not retrieve the interface family
structure for the indicated logical interface index in the indicated tunnel and session.
Severity error

Facility LOG_NEWS
L2TPD_SESSION_IFL_ADD_FAILED
System Log Message function-name: unable to assign session session-id to interface interface-name
Description The Layer 2 Tunneling Protocol process (l2tpd) could not associate the indicated session
with the indicated logical interface.
Severity error
Facility LOG_NEWS
L2TPD_SESSION_IFL_ALLOC_FAILED
System Log Message function-name: unable to allocate memory for session session-id, interface interface-name
Description The Layer 2 Tunneling Protocol process (l2tpd) could not allocate memory for the
indicated session to be associated with the indicated logical interface.
Severity error
Facility LOG_NEWS
L2TPD_SESSION_IFL_CLI_TREE_ALLOC
System Log Message Unable to allocate memory for session tree for interface interface-name
configuration database in memory. It could not allocate memory for a command-line
interface (CLI)-specific session tree structure for the indicated logical interface.
Severity error
Facility LOG_NEWS
L2TPD_SESSION_IFL_DELETED
System Log Message function-name: interface interface-name is deleted
Description The Layer 2 Tunneling Protocol process (l2tpd) detected that the configuration
information for the indicated logical interface was deleted for a session.
Severity error
Facility LOG_NEWS
L2TPD_SESSION_IFL_DELETE_FAILED
System Log Message function-name: unable to delete session identifier from interface interface-name

Description The Layer 2 Tunneling Protocol process (l2tpd) could not delete information about a
session from the configuration information for a logical interface.
Severity error
Facility LOG_NEWS
L2TPD_SESSION_IFL_GET_FAILED
System Log Message function-name: unable to find interface interface-name
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_SESSION_IFL_NOT_EQUAL
System Log Message function-name: interface interface-name not equal
Description The Layer 2 Tunneling Protocol process (l2tpd) could not add a session for the indicated
logical interface.
Severity error
Facility LOG_NEWS
L2TPD_SESSION_IFL_NOT_FOUND
System Log Message Unable to find interface interface-name (L2TP tunnel tunnel-id, session session-id)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not find the indicated logical
interface corresponding to the indicated tunnel and session.
Severity error
Facility LOG_NEWS
L2TPD_SESSION_IFL_OCCUPIED
System Log Message function-name: interface interface-name already has associated session (value1/value2)
Description The Layer 2 Tunneling Protocol process (l2tpd) determined that the indicated logical
interface already had an associated session.

Severity error
Facility LOG_NEWS
L2TPD_SESSION_IFL_REMOVE_FAILED
System Log Message Unable to remove L2TP tunnel tunnel-id, session session-id from logical interface (errno
error-code)
Description 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.
Severity error
Facility LOG_NEWS
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
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_SESSION_IP_DUPLICATE
System Log Message IP address peer-address/prefix-length (vrf) already used in other session (L2TP tunnel
tunnel-id, session session-id); closing session
Description 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 already used by another session, and the l2tpd process
started closing down the session.
Severity error
Facility LOG_NEWS
L2TPD_SESSION_ROUTE_ADD_FAILED
System Log Message Unable to add PPP route (L2TP tunnel tunnel-id, session session-id, errno error-code)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not add a Point-to-Point Protocol
(PPP) route for the indicated tunnel and session.

Severity error
Facility LOG_NEWS
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)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not retrieve the indicated routing
table associated with the indicated logical interface in the indicated tunnel and session.
Severity error
Facility LOG_NEWS
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
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_SETSOCKOPT_FAILED
System Log Message setsockopt() failed operation: error-message
Description The Layer 2 Tunneling Protocol process (l2tpd) could not set socket options during the
indicated operation.
Severity error
Facility LOG_NEWS
L2TPD_SET_ASYNC_CONTEXT
System Log Message Unable to set asynchronous context (errno error-code)
Description 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.

Severity error
Facility LOG_NEWS
L2TPD_SHOW_MULTILINK
System Log Message Detail level level is not supported by 'show services l2tp multilink' command
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_SHOW_SESSION
System Log Message Detail level level is not supported by 'show services l2tp session' command
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_SHOW_TUNNEL
System Log Message Detail level level is not supported by 'show services l2tp tunnel' command
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_SOCKET_FAILED
System Log Message socket() failed operation: error-message
Description The Layer 2 Tunneling Protocol process (l2tpd) could not open socket during the indicated
operation.
Severity error
Facility LOG_NEWS

L2TPD_SUBUNIT_ROUTE_ALLOC_FAILED
System Log Message Unable to allocate L2TP route (tunnel tunnel-id, session session-id)
Description The Layer 2 Tunneling Protocol process (l2tpd) could not allocate a subunit route record
for the indicated tunnel and session.
Severity error
Facility LOG_NEWS
L2TPD_TRACE_FILE_OPEN_FAILED
System Log Message Unable to open trace file: error-message
Description The Layer 2 Tunneling Protocol process (l2tpd) could not open its trace file.
Severity error
Facility LOG_NEWS
L2TPD_TUNNEL_CFG_ADD_FAILED
System Log Message Unable to add L2TP tunnel tunnel-id to PIC configuration (errno error-code)
tunnel to the in-memory configuration for the PIC.
Severity error
Facility LOG_NEWS
L2TPD_TUNNEL_CFG_ADD_INV_ADDR
System Log Message Unable to add L2TP tunnel tunnel-id to PIC configuration: address invalid
tunnel to the in-memory configuration for the PIC, because the local or remote address
provided for the tunnel was invalid.
Severity error
Facility LOG_NEWS
L2TPD_TUNNEL_CFG_DELETE_FAILED
System Log Message Unable to remove L2TP tunnel tunnel-id from PIC configuration

tunnel from the in-memory configuration for the PIC.
Severity error
Facility LOG_NEWS
L2TPD_TUNNEL_DELETE_FAILED
System Log Message Unable to delete L2TP tunnel tunnel-id (errno error-code)
indicated tunnel.
Severity error
Facility LOG_NEWS
L2TPD_TUNNEL_DEST_IF_LOOKUP_FAIL
System Log Message Unable to find destination interface for L2TP tunnel tunnel-id remote address:
error-message
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_TUNNEL_GROUP_ADD_FAILED
System Log Message Unable to create L2TP tunnel group
Description The Layer 2 Tunneling Protocol process (l2tpd) could not create a tunnel group.
Severity error
Facility LOG_NEWS
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

tunnel group and service set to the in-memory configuration for the indicated PIC.
Severity error
Facility LOG_NEWS
L2TPD_TUNNEL_GROUP_CFG_DEL_FAIL
System Log Message Unable to delete tunnel group tunnel-group (service set service-set): error-code
indicated tunnel group and service set.
Severity error
Facility LOG_NEWS
L2TPD_TUNNEL_GROUP_CREATE_FAILED
System Log Message Unable to create L2TP module for tunnel group address
Description The Layer 2 Tunneling Protocol process (l2tpd) could not create the indicated protocol
tunnel group.
Severity error
Facility LOG_NEWS
L2TPD_TUNNEL_GROUP_DELETE_FAILED
System Log Message Unable to delete L2TP tunnel group tunnel-group-id (errno error-code)
indicated tunnel group.
Severity error
Facility LOG_NEWS
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
Description 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.

Severity error
Facility LOG_NEWS
L2TPD_TUNNEL_GROUP_RESTART_FAIL
System Log Message Unable to restart L2TP module for tunnel group
Description The Layer 2 Tunneling Protocol process (l2tpd) could not restart a protocol tunnel group.
Severity error
Facility LOG_NEWS
L2TPD_USER_AUTHN_NOT_FOUND
System Log Message Unable to find user profile username during PPP authentication
Description 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.
Severity error
Facility LOG_NEWS
L2TPD_USER_AUTHN_ORDER_UNKNOWN
System Log Message Unknown authentication order authentication-order (tunnel tunnel-id, session session-id)
Description 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
Severity error
Facility LOG_NEWS
L2TPD_USER_AUTHN_PWD_NOT_FOUND
System Log Message Unable to retrieve password during PPP authentication of user username
Description 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.
Severity error

Facility LOG_NEWS

CHAPTER 66
LACP System Log Messages
This chapter describes messages with the LACP prefix. The Link Aggregation Control
Protocol (LACP) provides a method to control the bundling of several physical ports
together to form a single logical channel. LACP allows a network device to negotiate an
automatic bundling of links by sending LACP packets to the peer (directly connected
device that also implements LACP).
LACP_INTF_DOWN
System Log Message interface-name: Interface marked down due to lacp timeout on member
child-interface-name
Description The Link Aggregation Control Protocol process (lacpd) experienced timeout hence
interface marked down.
Severity notice
Facility LOG_DAEMON


CHAPTER 67
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_ISSU_ACK_TIMEOUT
System Log Message error-message: Peer port did not move to long timeout for ISSU
Description The Link Aggregation Control Protocol process (lacpd) sends a request during ISSU to
peer to move to Long Tiemout. As per the information received in the PDU peer did not
move to Long Timeout.
Severity notice
Facility LOG_DAEMON
LACPD_MEMORY_ALLOCATION_FAILED
System Log Message Unable to allocate memory for interface interface-name
Description The Link Aggregation Control Protocol process (lacpd) could not allocate memory for
the indicated interface.
Severity error
Facility LOG_DAEMON
LACPD_TIMEOUT
System Log Message error-message: lacp current while timer expired current Receive State: CURRENT
Description The Link Aggregation Control Protocol process (lacpd) experienced timeout hence
Receive State will change from Current to Expired/Defaulted.
Severity notice
Facility LOG_DAEMON


CHAPTER 68
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_3AH_LINKDOWN
System Log Message (interface-name): 802.3ah link-fault status changed to fault with reason reason
Description 802.3ah link-fault status for given interface has changed to fault
Severity info
Facility LOG_DAEMON
LFMD_3AH_LINKUP
System Log Message (interface-name): 802.3ah link-fault status changed to good
Description 802.3ah link-fault status for given interface has changed to good
Severity info
Facility LOG_DAEMON
LFMD_3AH_LOCAL_LB_CHANGED
System Log Message (interface-name): action remote-loopback on local port on peer's request
Description 802.3ah local loopback status changed on given interface on peer request
Severity info
Facility LOG_DAEMON
LFMD_3AH_LT_LOOP_CLEARED
System Log Message (interface-name): 802.3ah loop tracking marked interface up for reason "reason"

Description 802.3ah loop tracking marked given interface up for specified reason
Severity info
Facility LOG_DAEMON
LFMD_3AH_LT_LOOP_DETECTED
System Log Message (interface-name): 802.3ah loop tracking detected loop. Marking interface down.
Description 802.3ah loop tracking detected loop on given interface and marked interface down
Severity info
Facility LOG_DAEMON
LFMD_3AH_REQ_REMOTE_LB_CHANGE
System Log Message (interface-name): requesting remote-loopback action to peer
Description 802.3ah requested peer loopback status change on given interface
Severity info
Facility LOG_DAEMON
LFMD_RTSOCK_OPEN_FAILED
System Log Message Unable to open synchronous routing socket: error-message
Description The Ethernet Operation, Administration and Management link-fault management process
(lfmd) could not open a routing socket to create a connection.
Severity error
Facility LOG_DAEMON

CHAPTER 69
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
Description A Junos process could not notify the audit process (auditd) about user activity related
to system accounting, because of an interprocess communication (IPC) error.
Severity error
Facility ANY
Cause Any of the following reasons: auditd was not running auditd was still initializing after a
restart there was a socket error.
LIBJNX_AUDIT_TACPLUS_ERROR
System Log Message function-name: message error-message
Description A Junos process could not notify the audit process (auditd) about user activity related
to system accounting, because of an interprocess communication (IPC) error.
Severity error
Facility ANY
Cause Any of the following reasons: failure in writing tacacs+ accounting data to auditd failure
in auditd shared memory operations

LIBJNX_COMPRESS_EXEC_FAILED
System Log Message Unable to compress file 'filename' using program-name: error-message
Description 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.
Severity info
Facility ANY
LIBJNX_DEFAULT_IP_ADDR_NOT_SET
System Log Message Unable to retrieve system default IP address: not set in kernel (error-message)
Description A Junos process could not retrieve the system default IP address from the kernel, because
the address is not defined there.
Severity critical
Facility ANY
LIBJNX_EVLIB_FAILURE
Description A Junos process called the indicated function in the event library. The function failed for
the indicated reason.
Severity emergency
Facility ANY

Chapter 69: LIBJNX System Log Messages
LIBJNX_EXEC_EXITED
System Log Message Command stopped: PID pid, signal='return-value'core-dump-status, command 'command'
Description A Junos process created a child process to execute the indicated command for it. The
child process stopped unexpectedly.
Severity notice
Facility ANY
LIBJNX_EXEC_FAILED
System Log Message Child exec failed for command 'command': error-message
Description A Junos process called the exec() system call while creating a child process to execute
the indicated command for it. The system call failed.
Severity error
Facility ANY
LIBJNX_EXEC_PIPE
System Log Message Unable to create pipes for command 'command': error-message
Description 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.
Severity error
Facility ANY

LIBJNX_EXEC_SIGNALED
System Log Message Command received signal: PID pid, signal signal-namecore-dump-status, command
'command'
child process received the indicated signal and exited.
Severity error
Facility ANY
LIBJNX_EXEC_WEXIT
System Log Message Command exited: PID pid, status return-valuecore-dump-status, command 'command'
child process exited abnormally with the indicated exit code.
Severity notice
Facility ANY
LIBJNX_FILE_COPY_FAILED
System Log Message Failed to copy from source-filename to destination-filename
Description A Junos process could not copy the indicated source file to the indicated destination
name or location.
Severity error
Facility ANY
LIBJNX_FILE_SYSTEM_FAIL
System Log Message pathname: error-message
Description A Junos process could not obtain status information for the indicated file system.

Severity error
Facility ANY
LIBJNX_FILE_SYSTEM_SPACE
System Log Message Not enough space left on device pathname
Description A Junos process found that the indicated file system did not have the free space needed
for storing temporary files.
Severity warning
Facility ANY
LIBJNX_INVALID_XML_DATA
System Log Message Invalid XML data '\\data'
Description The XML parser closed its session with a client application because the indicated XML
data sent by the client was invalid.
Severity error
Facility ANY
LIBJNX_LOGIN_ACCOUNTS_NOT_LOCKED
System Log Message No user accounts were locked.
Description No user accounts had been locked.
Severity notice
Facility ANY
LIBJNX_LOGIN_ACCOUNT_LOCKED
System Log Message Account for user 'username' has been locked out from logins
Description Logins from a locked account are not permitted.
Severity notice
Facility ANY
LIBJNX_LOGIN_ACCOUNT_NOT_LOCKED
System Log Message Account for user 'username' was not locked.

Description The user account had not been locked.
Severity notice
Facility ANY
LIBJNX_LOGIN_ACCOUNT_UNLOCKED
System Log Message Account for user 'username' has been unlocked for logins
Description Logins from an unlocked account are permitted again.
Severity notice
Facility ANY
LIBJNX_LOGIN_ACCT_NOT_UNLOCKED
System Log Message Failed to unlock account for user 'username'.
Description An attempt to unlock the user account failed.
Severity error
Facility ANY
LIBJNX_PRIV_LOWER_FAILED
System Log Message Unable to lower privilege level: error-message
Description A Junos process attempted to revert its effective user ID to the original user. The attempt
failed.
Severity error
Facility ANY
LIBJNX_PRIV_RAISE_FAILED
System Log Message Unable to raise privilege level: error-message
Description A Junos process attempted to set its effective user ID to the root user. The attempt failed.

Severity error
Facility ANY
LIBJNX_REPLICATE_RCP_ERROR
System Log Message operation: operational-status
Description The rcp command failed during replication.
Severity error
Facility ANY
LIBJNX_REPLICATE_RCP_EXEC_FAILED
System Log Message rcp failed: error-message
Description A Junos process created a child process to copy a file to the other Routing Engine. The
copy operation failed.
Severity error
Facility ANY
LIBJNX_SNMP_ENGINE_FILE_FAILURE
System Log Message function-name: operation: operation filename: error-message
Description A Junos process could not perform the indicated operation on the indicated SNMP engine
data file.
Severity critical
Facility ANY

LIBJNX_SNMP_ENGINE_SCAN_FAILURE
System Log Message function-name: fscanf : filename scanning: data Error: error-message
Description A Junos process could not perform the scan operation on the indicated SNMP engine
data file.
Severity critical
Facility ANY
LIBJNX_SOCKET_BUFF_ERROR
System Log Message Socket buffer error - 'error-message':
Description JUNOS system can not allocate the requested amount of the socket buffer.
Severity error
Facility ANY
LIBJNX_SOCKET_FAILURE
System Log Message operation: error-message
Description Various system processes use Transmission Control Protocol (TCP), User Datagram
Protocol (UDP), and Reliable Data Protocol (RDP) sockets. The indicated socket operation
Severity emergency
Facility ANY

LIBJNX_SOCKET_FLUSH_TIMEOUT
System Log Message exit flush timeout error-message
Description Various system processes use sockets for Inter-process Communication, and during the
termination phase of the process the socket is flushed to ensure all the data sent has
been received by the peer process. If the flush operation takes an excessive amount of
time, the flush is aborted and process termination completes.
Severity error
Facility ANY
LIBJNX_XML_DECODE_FAILED
System Log Message Invalid XML encoding 'data', skipping to ';'
Description 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.
Severity error
Facility ANY
Cause A possible cause is improper escaping of character constants in the data stream.


CHAPTER 70
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 snmp_ms_trap_api return argument
Description Sub-agents SNMP context either too long or of zero size
Severity error
Facility ANY
LIBJSNMP_IPC_ERROR
System Log Message argument: sock:port (type:port-type)
Description Error in SNMP related IPC messages size mismatch, corruption or memory failure
Severity error
Facility ANY
LIBJSNMP_IPC_READ_ERROR
System Log Message Unable to read inbound-bytes bytes: sock: port (type: port-type)
Description Error in reading IPC messages during SNMP related messaging

Severity error
Facility ANY
LIBJSNMP_MTHD_API_UNKNOWN_TYPE
System Log Message unknown oev type: tag-type
Description Internal error - Unknown SNMP object indexing type
Severity error
Facility ANY
LIBJSNMP_NS_LOG_CRIT
System Log Message CRIT: argument
Description Logs for SNMP critical message
Severity critical
Facility ANY
LIBJSNMP_NS_LOG_EMERG
System Log Message EMERG: argument
Description SNMP errors with LOG_EMERG as severity
Severity emergency
Facility ANY

Chapter 70: LIBJSNMP System Log Messages
LIBJSNMP_NS_LOG_ERR
System Log Message ERR: argument
Description SNMP errors with LOG_ERR as severity
Severity error
Facility ANY
LIBJSNMP_OID_GEN_FAILED
System Log Message Unable to generate OID: object-name (system-error-message)
Description Unable to translate SNMP object string to OID
Severity error
Facility ANY
LIBJSNMP_READ_LEN_ERR
System Log Message error error-code reading routing socket
Description Failure while reading rtsocket for SNMP related operation
Severity error
Facility ANY
LIBJSNMP_RTMSIZE_MISMATCH_ERR
System Log Message routing socket msg size argument of argument1d (call buf = argument2)

Description Error in message length while reading rtsocket for SNMP related operation
Severity error
Facility ANY
LIBJSNMP_SMS_HDR_ERR
System Log Message problem with hdr size (record-size) or msg size (size)
Description Discrepancy in sub-agent message length and header size
Severity error
Facility ANY
LIBJSNMP_SMS_MSG_ERR
System Log Message received received-value bytes, expected expected-value bytes
Description Various discrepancies in sub-agent message lengths. SNMP Message errors
Severity error
Facility ANY
LIBJSNMP_SNMP_PH_INIT_ERR
System Log Message snmp platform hooks initialization failure: argument
Description Error during initialization of snmp platform hook library
Severity error
Facility ANY

Chapter 70: LIBJSNMP System Log Messages
LIBJSNMP_SOCKET_OPEN_ERR
System Log Message routing socket open error argument
Description Failure in opening routing socket
Severity error
Facility ANY
LIBJSNMP_SOCKET_VER_MISMATCH
System Log Message routing socket version mismatch
Description Routing socket version mismatch between kernel andi application
Severity error
Facility ANY
LIBJSNMP_TRAP_API_FAILURE
System Log Message function-name: Trap API: argument argument1
Description Misc. error while creating SNMP traps
Severity error
Facility ANY

LIBJSNMP_TRAP_UTILS_ERR
System Log Message unknown trap object: object-name
Description Trying to send invalid object as varbind while creating SNMP traps
Severity error
Facility ANY

CHAPTER 71
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 Can't create msprpc client: error-message
Description A Junos process (mspinfo) could not establish initialization of the RPC client.
Severity error
Facility ANY
Cause Possible reasons: process is out of memory
LIBMSPRPC_CLIENT_KCOM_FAILED
System Log Message Can't initialize kcom for msprpc client: error-message
Description A Junos process (mspinfo) could not establish initialization of the kcom subsystem.
Severity error
Facility ANY
Cause Possible reasons: can't initialize kcom services.
LIBMSPRPC_CLIENT_KCOM_NO_IF
System Log Message No active extension-provider interfaces

Description A Junos process (mspinfo) could not found any configured and active extension-provider
interfaces.
Severity notice
Facility ANY
Cause Possible reasons: can't initialize kcom services.
LIBMSPRPC_CLIENT_NO_CONNECTION
System Log Message Failed connecting fpc=fpc-slot, pic=pic-slot
Description Remote execution of the command given from the RE to the PIC failed, can not connect
to the PIC.
Severity notice
Facility ANY
Cause Possible reasons: a)PIC appears online but is not responding b)msprpc server is not
running on the PIC.
LIBMSPRPC_CLIENT_NO_REPLY
System Log Message Error executing "command": no reply from the PIC
Description Remote execution of the command given from the RE to the PIC failed, no reply from the
PIC.
Severity notice
Facility ANY
Cause 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.

Chapter 71: LIBMSPRPC System Log Messages
LIBMSPRPC_CLIENT_PIC_DOWN
System Log Message Interface interface-name is down
Description Remote execution of the command given from the RE to the PIC failed, the PIC is down.
Severity error
Facility ANY
Cause Possible reasons: the given PIC is not responding and/or is offline.
LIBMSPRPC_CLIENT_WRONG_OUTPUT
System Log Message Error executing "command": output length exceeds correct-length characters
Description Remote execution of the command given from the RE to the PIC failed, PIC returned
unexpected output.
Severity notice
Facility ANY
Cause Possible reasons: a)wrong command b)wrong arguments.


CHAPTER 72
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 Connection could not be set up: error-message
Description The indicated error occured because a connection to the license-check process was not
established.
Severity error
Facility ANY
LICENSE_CONN_TO_LI_CHECK_FAILURE
System Log Message Process could not connect to license-check in maximum-value tries; giving up
Description The indicated process failed to connect to the license-check process after the indicated
maximum tries.
Severity error
Facility ANY
LICENSE_CONN_TO_LI_CHECK_SUCCESS
System Log Message Connected to license-check
Description The indicated process succesfully connected to the license-check process.
Severity info
Facility ANY

LICENSE_EXPIRED
System Log Message License for feature feature-name(feature-id) expired
Description The time-based license for the indicated feature expired. The feature remains inactive
until a new license is installed.
Severity alert
Facility LOG_DAEMON

http://kb.juniper.net/InfoCenter/index?page=content&id=/KB18966.
LICENSE_EXPIRED_KEY_DELETED
System Log Message License key "filename" has expired.
Description The indicated license-key has been removed from the file-system.
Severity notice
Facility ANY
LICENSE_GRACE_PERIOD_APPROACHING
System Log Message License grace period for feature feature-name(feature-id) will expire in time
Description 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.
Severity alert
Facility LOG_DAEMON

LICENSE_GRACE_PERIOD_EXCEEDED
System Log Message License grace period for feature feature-name(feature-id) will expire in time (limit =
maximum-value)
Description 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.

Chapter 72: LICENSE System Log Messages
Severity alert
Facility LOG_DAEMON

LICENSE_GRACE_PERIOD_EXPIRED
System Log Message License grace period for feature feature-name(feature-id) has expired
Description The grace period for a licensable feature has expired. Strict license enforcement will
remain active until a new license is installed.
Severity alert
Facility LOG_DAEMON

LICENSE_INCORRECT_USAGE_API
System Log Message Incorrect usage of API. Use the API lc_write_scale_usage.
Description The indicated process has called an incorrect usage of a liblicense API
Severity warning
Facility ANY
LICENSE_INVALIDE_FEATURE_ID
System Log Message It is an invalid feature id: feature-id
Description The indicated process has encoutered an invalid feature id.
Severity error
Facility ANY
LICENSE_JVERSION_READ_ERROR
System Log Message Failed to get JUNOS version : error: system-error-message
Description The indicated process encountered a system error while trying to obtain release version
of JUNOS.
Severity error

Facility ANY
LICENSE_LIST_MANAGEMENT
System Log Message Error occurred for feature feature-name: error-message (system error:
system-error-message)
Description 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.
Severity error
Facility ANY
LICENSE_NEARING_EXPIRY
System Log Message License for feature feature-name(feature-id) expires in time
Description 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.
Severity alert
Facility LOG_DAEMON

LICENSE_READ_ERROR
System Log Message recvmsg() failed:error-message
Description The indicated process failed to read an event sent to it, for the indicated reason.
Severity error
Facility ANY
LICENSE_REG_ERROR
System Log Message Registration request failed: current-value
Description The license registration request failed. A request needs to be resent to the license-check
process.
Severity error
Facility ANY

LICENSE_REVOKE_DB_CREATE_FAILURE
System Log Message Failed to create license revoked db filename : error-message
Description The indicated process failed to create license revoked db.
Severity error
Facility ANY
LICENSE_REVOKE_DB_OPEN_FAILURE
System Log Message Unable to open license revoke db filename : error-message
Description The indicated process failed to open license revoked db.
Severity error
Facility ANY
LICENSE_SHM_ATTACH_FAILURE
System Log Message Failed to attach shared memory
Description The indicated process failed to attach the shared memory.
Severity error
Facility ANY
LICENSE_SHM_CREATE_FAILURE
System Log Message Failed to allocate shared memory
Description The indicated process failed to allocate the shared memory.
Severity error
Facility ANY
LICENSE_SHM_DETACH_FAILURE
System Log Message Failed to detach shared memory error-argument
Description The indicated process failed to release the shared memory.
Severity error

Facility ANY
LICENSE_SHM_DIR_OPEN_FAILURE
System Log Message Unable to create directory filename: error-message
Description The indicated process encountered a system error while attempting to create the directory.
Severity error
Facility ANY
LICENSE_SHM_FILE_OPEN_FAILURE
System Log Message Failed to open the shared memory file filename, errno=error-message
Description The indicated process encountered a system error while attempting to open the shared
memory file.
Severity error
Facility ANY
LICENSE_SHM_KEY_CREATE_FAILURE
System Log Message Failed to create key for shared memory from the file filename
Description The indicated process encountered a system error while creating an IPC identifier from
a pathname.
Severity error
Facility ANY
LICENSE_SHM_SCALE_READ_FAILURE
System Log Message Failed to read license scale usage
Description The indicated process failed to read scale usage data.
Severity error
Facility ANY
LICENSE_SHM_SCALE_UPDATE_FAILURE
System Log Message Failed to update license scale usage
Description The indicated process failed to update scale usage data.

Severity error
Facility ANY
LICENSE_SHM_USAGE_READ_FAILURE
System Log Message Failed to read license feature usage shared memory
Description The indicated process has failed to read feature usage shared memory.
Severity error
Facility ANY
LICENSE_SHM_USAGE_WRITE_FAILURE
System Log Message Failed to update license feature usage shared memory
Description The indicated process has failed to update feature usage shared memory.
Severity error
Facility ANY
LICENSE_SIGNATURE_VERIFY_FAILED
System Log Message Signature verification failed: error-message
Description The management process (mgd) could not verify a license because the license's signature
was invalid.
Severity error
Facility ANY
LICENSE_UNKNOWN_RESPONSE_TYPE
System Log Message unknown message type received: current-value
Description An unknown response type was received from the license-check process.
Severity error
Facility ANY
LICENSE_VERIFICATION_FILE_ERROR
System Log Message License verification failed for file 'error-message': filename (system error:
system-error-message)

Description The management process (mgd) could not verify the indicated license file because of
the indicated internal file-handling error.
Severity error
Facility ANY

CHAPTER 73
LLDP System Log Messages
This chapter describes messages with the LLDP prefix. They are generated by the link
layer discovery protocol process (lldpd) which is used by MX Series routers, ACX Series
routers, and 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.
LLDP_NEIGHBOR_DOWN
System Log Message A neighbor of interface interface-name has gone down. Now, this interface has
neighbor-count neighbor/s.
Description LLDP has detected that a neighbor has gone down for an interface.
Severity info
Facility LOG_DAEMON
Cause TTL is expired for RDB neighbor. So deleting neighbor from rdb.
LLDP_NEIGHBOR_UP
System Log Message A neighbor has come up for interface interface-name. Now, this interface has
neighbor-count neighbor/s.
Description LLDP has detected that a neighbor has come up for an interface.
Severity info
Facility LOG_DAEMON
Cause New neighbor has come up. Adding neighbor to rdb.


CHAPTER 74
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 Client aborted login
Description A login attempt was cancelled, either by the remote user or in response to a signal.
Severity info
Facility LOG_AUTH
LOGIN_ATTEMPTS_THRESHOLD
System Log Message Threshold for unsuccessful authentication attempts (limit) reached by user 'username'
Description The user made too many failed login attempts.
Severity notice
Facility LOG_AUTH
LOGIN_FAILED
System Log Message Login failed for user username from host source-address
Description A login attempt failed for the indicated username.
Severity notice
Facility LOG_AUTH
LOGIN_FAILED_LIMIT
System Log Message Specified number of login failures (limit) for user 'username' reached from 'source-address'
Description Several login attempts failed for the indicated username.

Severity notice
Facility LOG_AUTH
LOGIN_FAILED_SET_CONTEXT
System Log Message Failed to set context for user username
Description The login process (login) could not set login context properties for the indicated user
and cancelled the authentication attempt.
Severity error
Facility LOG_AUTH
LOGIN_FAILED_SET_LOGIN
System Log Message Failed to set login ID for user username: error-message
Description The login process (login) could not assume the user ID of the indicated user and cancelled
the authentication attempt.
Severity error
Facility LOG_AUTH
LOGIN_HOSTNAME_UNRESOLVED
System Log Message Unable to resolve hostname hostname: error-message
Description The login process (login) could not resolve the indicated remote hostname for the
indicated reason.
Severity error
Facility LOG_AUTH
LOGIN_INFORMATION
System Log Message User username logged in from host hostname on device tty-name
Description The indicated username was authenticated and logged into the shell specified for it in
the password file.
Severity info

Chapter 74: LOGIN System Log Messages
Facility LOG_AUTH
LOGIN_MALFORMED_USER
System Log Message Invalid username: username
Description The indicated username was invalid.
Severity info
Facility LOG_AUTH
LOGIN_PAM_AUTHENTICATION_ERROR
System Log Message Failed password for user username
Description The login process (login) could not authenticate the indicated user via PAM.
Severity error
Facility LOG_AUTH
LOGIN_PAM_ERROR
System Log Message Failure while authenticating user username: error-message
Description The PAM authentication process failed for the indicated username, for the indicated
reason.
Severity error
Facility LOG_AUTH
LOGIN_PAM_MAX_RETRIES
System Log Message Too many retries while authenticating user username
Description The number of failed PAM authentication attempts for the indicated user exceeded the
maximum limit.
Severity error
Facility LOG_AUTH
LOGIN_PAM_STOP
System Log Message Failed to end PAM session: error-message
Description The login process (login) could not end the PAM authentication session, for the indicated
reason.

Severity error
Facility LOG_AUTH
LOGIN_PAM_USER_UNKNOWN
System Log Message Attempt to authenticate unknown user username
Description The login process (login) failed to authenticate the indicated user via PAM because the
username was unknown.
Severity error
Facility LOG_AUTH
LOGIN_PASSWORD_EXPIRED
System Log Message Forcing change of expired password for user username
Description The password provided for the indicated username was expired and the user was
prompted to set a new one.
Severity info
Facility LOG_AUTH
LOGIN_REFUSED
System Log Message Login of user username from host hostname on device tty-name was refused: reason
Description A login attempt for the indicated username was rejected for the indicated reason.
Severity notice
Facility LOG_AUTH
LOGIN_ROOT
System Log Message User username logged in as root from host hostname on device tty-name
Description The indicated username was authenticated as a superuser and logged into the shell
specified for the root user in the password file.
Severity info
Facility LOG_AUTH

Chapter 74: LOGIN System Log Messages
LOGIN_TIMED_OUT
System Log Message Login attempt timed out after duration seconds
Description A login attempt failed to complete in the maximum time allowed.
Severity info
Facility LOG_AUTH


CHAPTER 75
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 Failed to open profile database: error-message
Description The local policy decision function process (lpdfd) failed to open the profile database.
Severity error
Facility LOG_DAEMON

LPDFD_DYN_REGISTER_FAILED
System Log Message Dynamic config register failed: error-message
Description The local policy decision function process (lpdfd) failed to register with the dynamic
configuration subsystem.
Severity error
Facility LOG_DAEMON

LPDFD_PCONN_SERVER
System Log Message argument: Cannot retrieve peer info for session. Error: error-message
Description The local policy decision function process (lpdfd) pconn server failed to initialize

Severity error
Facility LOG_DAEMON

CHAPTER 76
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 Failed to exec command
Description The Logical System 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.
Severity error
Facility LOG_DAEMON
LRMUX_LRPD_PID_LOCK
System Log Message Lock not found on PID file filename
Description The Logical System Multiplexer process (lrmuxd) could not find a lock for a logical system.
Severity error
Facility LOG_DAEMON
Cause A logical system process (rpd) died.
LRMUX_LRPD_PID_OPEN
System Log Message Unable to open PID file filename
Description The Logical System Multiplexer process (lrmuxd) could not open the indicated PID lock
file for a logical system process (rpd).
Severity error
Facility LOG_DAEMON

LRMUX_LRPD_SEND_HUP
System Log Message Unable to send signal to PID pid
Description The Logical System Multiplexer process (lrmuxd) could not forward a SIGHUP signal to
a logical system process (rpd).
Severity error
Facility LOG_DAEMON

CHAPTER 77
LSYSD System Log Messages
This chapter describes messages with the LSYSD prefix. They are generated by the logical
system process (lsysd), which handles logical systems on devices running Junos OS.
LRMUX_FAILED_EXEC
System Log Message Failed to exec command
Description The Logical System 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.
Severity error
Facility LOG_DAEMON
LRMUX_LRPD_PID_LOCK
System Log Message Lock not found on PID file filename
Description The Logical System Multiplexer process (lrmuxd) could not find a lock for a logical system.
Severity error
Facility LOG_DAEMON
Cause A logical system process (rpd) died.
LRMUX_LRPD_PID_OPEN
System Log Message Unable to open PID file filename
Description The Logical System Multiplexer process (lrmuxd) could not open the indicated PID lock
file for a logical system process (rpd).
Severity error
Facility LOG_DAEMON

LRMUX_LRPD_SEND_HUP
System Log Message Unable to send signal to PID pid
Description The Logical System Multiplexer process (lrmuxd) could not forward a SIGHUP signal to
a logical system process (rpd).
Severity error
Facility LOG_DAEMON

CHAPTER 78
MBG System Log Messages
This chapter describes messages with the MBG prefix.
MBG_ADDR_ALLOC_ALLOCATED
System Log Message Address allocation failed, routing-instance routing-instance address address in use.
Description Address allocation failed - requested address in use.
Severity error
Facility LOG_DAEMON
MBG_ADDR_ALLOC_MM
System Log Message Address allocation failed, routing-instance routing-instance pool-name pool-name in
Maintenance Mode.
Description Address allocation failed - address pool in maintenance mode.
Severity error
Facility LOG_DAEMON
MBG_ADDR_ALLOC_NO_ADDR
System Log Message Address allocation failed, no address available in routing-instance routing-instance
pool-name pool-name.
Description Address allocation failed - no address available in pool(group).
Severity error
Facility LOG_DAEMON
Action Configure additional addresses for allocation.

MBG_ADDR_ALLOC_NO_POOL
System Log Message Address allocation failed, routing-instance routing-instance definition for pool-name
pool-name not found.
Description Address allocation failed - pool configuration not found.
Severity error
Facility LOG_DAEMON
MBG_ADDR_ALLOC_NO_VRF
System Log Message Address allocation failed, routing-instance ID routing-instance not found.
Description Address allocation failed - routing-instance configuration not found.
Severity error
Facility LOG_DAEMON
MBG_ADDR_ALLOC_UNDEFINED
System Log Message Address allocation failed, routing-instance routing-instance address address is not
configured.
Description Address allocation failed - address has not been configured for allocation.
Severity error
Facility LOG_DAEMON
Action Configure the requested address for allocation.
MBG_ADDR_APFE_DN
System Log Message Anchor PFE pic-name went down.
Description Anchor PFE went DOWN.
Severity info
Facility LOG_DAEMON
MBG_ADDR_APFE_UP
System Log Message Anchor PFE pic-name came up.
Description Anchor PFE came UP.

Chapter 78: MBG System Log Messages
Severity info
Facility LOG_DAEMON
MBG_ADDR_INIT_OK
System Log Message Mobile Subscriber IP Address allocation Library initialized.
Description Mobile Subscriber IP Address allocation Library initialized.
Severity info
Facility LOG_DAEMON
MBG_ADDR_MM_ACK
System Log Message Maintenance Mode Ack sent for routing-instance routing-instance pool-name pool-name.
Description Mobile Subscriber IP Address allocation library Address pool maintenance mode
acknowledged. Configuration modifications can now be made to the address pool.
Severity info
Facility LOG_DAEMON
MBG_ADDR_MM_ENABLE
System Log Message Routing-instance routing-instance pool-name pool-name placed in Maintenance Mode.
Description Mobile Subscriber IP Address allocation Library Address pool maintenance mode enabled.
Severity info
Facility LOG_DAEMON
MBG_ADDR_NO_MEMORY_HEAP
System Log Message Out of heap memory.
Description Mobile Subscriber IP Address memory allocation - out of heap memory.
Severity error
Facility LOG_DAEMON
MBG_ADDR_NO_MEMORY_OC
System Log Message Out of object-cache memory
Description Mobile Subscriber IP Address memory allocation - out of object-cache memory.

Severity error
Facility LOG_DAEMON
MBG_ADDR_PRIMARY
System Log Message High-availibility state set to Primary.
Description Mobile Subscriber IP Address allocation Library high-availability state set to Primary.
Severity info
Facility LOG_DAEMON
MBG_ADDR_SECONDARY
System Log Message High-availibility state set to Secondary.
Description Mobile Subscriber IP Address allocation Library high-availability state set to Secondary.
Severity info
Facility LOG_DAEMON
MBG_ADDR_STANDALONE
System Log Message High-availibility state set to Standalone.
Description Mobile Subscriber IP Address allocation Library high-availability state set to Standalone.
Severity info
Facility LOG_DAEMON
MBG_CFG_COMMIT_FAIL
System Log Message Failed to create mobiled commit task
Description Child Mobility Daemon failed to create subtask for committing configuration.
Severity error
Facility LOG_DAEMON
Cause Task creation failure possibly because of limited resources (memory/CPU cycles)
Action Internal Software failure, Contact technical help

MBG_CFG_DB_OPEN_FAIL
System Log Message Commit check daemon failed to open configuration database
Description Mobility Daemon failed to open static configuration database during initialization.
Severity error
Facility LOG_DAEMON
Cause Failed possibly because Mobiled failed to parse it or configuration not found
Action Check if router configuration is in place, Contact technical help
MBG_CG_CONF_SERVER_REGIST_FAIL
System Log Message Failed to register configuration plugin for chargemand charge
Description Mobiled charging configuration server failed to get register.
Severity error
Facility LOG_DAEMON
MBG_CG_CP_MM_STATE_CHANGE
System Log Message Gateway type gw-personality gateway name gateway-name profile name profile-namenew
state new-state old state old-state
Description This indicates that given charging profile underwent a change in the maintenance-mode.
Severity info
Facility LOG_DAEMON
MBG_CG_EVENT_SERVER_REGIST_FAIL
System Log Message Failed to register event plugin for chargemand charge
Description Mobiled charging event notification server failed to get register.
Severity error
Facility LOG_DAEMON
MBG_CG_TSP_MM_STATE_CHANGE
System Log Message Gateway type gw-personality gateway name gateway-name profile name profile-namenew
state new-state old state old-state

Description This indicates that given transport profile underwent a change in the maintenance-mode.
Severity info
Facility LOG_DAEMON
MBG_CG_UI_SERVER_REGIST_FAIL
System Log Message Failed to register ui plugin for chargemand charge
Description Mobiled charging UI server failed to get register.
Severity error
Facility LOG_DAEMON
MBG_CMD_ATTACH_FAIL
System Log Message unable to attach to SMD shared province
Description CMD unable to attach to SMD shared province.
Severity error
Facility LOG_DAEMON
MBG_CMD_CDR_DEST
System Log Message Gateway type gw-personality gateway name gateway-nameCDR destination status-code
server name profile-namefpc slot id fpc-slot pic slot id pic-slot
Description This signifies change in the destination of the CDRs (Charging Data Record).
Severity info
Facility LOG_DAEMON
MBG_CMD_CDR_ENCODING_FAIL
System Log Message Gateway type gw-personality gateway name gateway-namecharging id charging-id lrsn
id lrsn-id
Description For the specified charging id charging data record encoding failed.
Severity error
Facility LOG_DAEMON

MBG_CMD_CONF_CLIENT_INIT_FAIL
System Log Message Gateway type gw-personality gateway name gateway-name charging configuration client
init failed
Description UI client has failed to connect to mobiled charging UI server.
Severity error
Facility LOG_DAEMON
MBG_CMD_EVE_CLIENT_INIT_FAIL
System Log Message Gateway type gw-personality gateway name gateway-name charging event client plugin
registration failed
Description Event client has failed to connect to mobiled charging event server.
Severity error
Facility LOG_DAEMON
MBG_CMD_GTPP_DOWN
System Log Message Gateway type gw-personality gateway name gateway-nameGTPP client profile-name
down on fpc slot id fpc-slot pic slot id pic-slot
Description This event signifies that the specified server has been marked dead.
Severity error
Facility LOG_DAEMON
MBG_CMD_GTPP_UP
System Log Message Gateway type gw-personality gateway name gateway-nameGTPP client profile-name
up on fpc slot id fpc-slot pic slot id pic-slot
Description This event signifies that the specified server has been marked alive.
Severity info
Facility LOG_DAEMON
MBG_CMD_GTPP_VER_MIS_MATCH
System Log Message Gateway type gw-personality gateway name gateway-name CGF id peer-id version
mismatchconfigured version configured-version received version received-version
Description This event signifies that the version not supported message received from the CGF server.

Severity error
Facility LOG_DAEMON
MBG_CMD_GW_SER_UP
System Log Message Charging is UP for Gateway type gw-personality gateway name gateway-namefpc slot
id fpc-slot pic slot id pic-slot
Description This signifies the Charging daemon is UP on the SPIC.
Severity info
Facility LOG_DAEMON
MBG_CMD_HA_CHARGED_CONNEC_FAIL
System Log Message Failed to establish connection to Charged gateway type gw-personalitygateway name
gateway-name
Description Backup chargemand failed to establish connection with charged.
Severity error
Facility LOG_DAEMON
MBG_CMD_HMEM_THRES
System Log Message Gateway type gw-personality gateway name gateway-namefpc slot id fpc-slot pic slot
id pic-slot SPIC memory reaches to limitalarm type alarm-type
Description This event is sent out when the utilization exceeds or falls below configured high threshold
of internal memory space for charging data records.
Severity error
Facility LOG_DAEMON
MBG_CMD_IRI_EXTRACT_FAIL
System Log Message Gateway type gw-personality Gateway name gateway-name failed to extractthe IRI
address for chargemand to charged fpc slot fpc-slot pic slot pic-slot
Description Failed to extract the internal routing instance of the corresponding chargemand.
Severity error
Facility LOG_DAEMON

MBG_CMD_LMEM_THRES
Description This event is sent out when the utilization exceeds or falls below configured low threshold
of internal memory space for charging data records.
Severity info
Facility LOG_DAEMON
MBG_CMD_MMEM_THRES
Description This event is sent out when the utilization exceeds or falls below configured medium
threshold of internal memory space for charging data records.
Severity info
Facility LOG_DAEMON
MBG_CMD_PMNGR_IPC_REGISTER_FAIL
System Log Message Path manager IPC register failed gateway type gw-personalitygateway name
gateway-name fpc id fpc-slot pic id pic-slot
Description IPC registration of the path manager has failed.
Severity error
Facility LOG_DAEMON
MBG_CMD_PMNGR_SERVER_CONNEC_FAIL
System Log Message Failed to establish the pathmgr server connectiongateway type gw-personality gateway
name gateway-name
Description Failed to create the path manager server connection.
Severity error
Facility LOG_DAEMON
MBG_CMD_RE_DISK_FULL
System Log Message RE hard disk full gateway type gw-personality gateway name gateway-name

Description Disk full message received by chargemand from the charged.
Severity info
Facility LOG_DAEMON
MBG_CMD_RE_DISK_FULL_RESOLVED
System Log Message Received RE hard disk full resolved status messagegateway type gw-personality gateway
name gateway-name
Description RE Disk full has resolved and disk is available for the storage.
Severity info
Facility LOG_DAEMON
MBG_CMD_RE_DISK_OFFLINE
System Log Message Received RE disk offline in batch response messagegateway type gw-personality gateway
name gateway-name
Description RE local storage disk is not available.
Severity info
Facility LOG_DAEMON
MBG_CMD_RE_DISK_ONLINE
System Log Message RE hard disk is available. gateway type gw-personality gateway name gateway-name
Description RE local storage disk is available.
Severity info
Facility LOG_DAEMON
MBG_CMD_TIMER_START_FAIL
System Log Message Gateway type gw-personality gateway name gateway-nameFailed to start the timer
event-type
Description For the specified event timer has failed to start.
Severity error
Facility LOG_DAEMON

MBG_CMD_TIMER_STOP_FAIL
System Log Message Gateway type gw-personality gateway name gateway-nameFailed to stop the timer
event-type
Description For the specified event timer has failed to stop.
Severity error
Facility LOG_DAEMON
MBG_CMD_TSP_LOOK_UP_FAIL
System Log Message Gateway type gw-personality gateway name gateway-nameFailed to access transport
profile Id group-id
Description Transport profile does not exists in the data base.
Severity error
Facility LOG_DAEMON
MBG_CMD_UI_CLIENT_INIT_FAIL
System Log Message Gateway type gw-personality gateway name gateway-name charging UI client plugin
registration failed
Description Configuration client has failed to connect to mobiled charging configuration server.
Severity error
Facility LOG_DAEMON
MBG_CMD_WFA_FULL
System Log Message Gateway type gw-personality gateway name gateway-name WFA is full TSP Id group-id
Description Batch/DRT messages will not be created until the WFA becomes free
Severity error
Facility LOG_DAEMON
MBG_CONF_SERVER_INIT_FAIL
System Log Message Mobilility configuration server creation failed
Description Mobility Configuration server (which communicates with peers on SPIC) creation failed,
there is one configuration server for all the peers.

Severity error
Facility LOG_DAEMON
Cause Configuration server creation failure possibly because of limited resources (memory/CPU
cycles)
Action Internal software failure, Contact technical help
MBG_EVENT_SERVER_INIT_FAIL
System Log Message Mobility event server creation failed
Description Mobility Event server (which communicates with peers on SPIC) creation failed, there is
one event server for all the peers.
Severity error
Facility LOG_DAEMON
Cause Event server creation failure possibly because of limited resources (memory/CPU cycles)
MBG_GW_TASK_CREATION_FAILURE
System Log Message Failed to create Gateway Module task
Description Mobility Daemon failed to create Gateway Module task.
Severity error
Facility LOG_DAEMON
Cause Gateway Module task creation failure possibly because of limited resources (memory/CPU
cycles)
MBG_IF_TASK_CREATION_FAILURE
System Log Message Failed to create IF module task
Description Mobility Daemon failed to create IF Module task.
Severity error

Facility LOG_DAEMON
Cause IF Module task creation failure possibly because of limited resources (memory/CPU
cycles)
MBG_INIT_FAIL
System Log Message Failed to create Mobility Main task
Description During Mobility infrastructure initializations, Main task creation failed.
Severity critical
Facility LOG_DAEMON
Cause Main task creation failed possibly because of task block memory allocation failure
MBG_MM_TASK_CREATE_FAIL
System Log Message Failed to create Maintenance Mode Server Task
Description Mobility Daemon failed to create maintenance mode server task.
Severity error
Facility LOG_DAEMON
Cause Maintenance mode task creation failure possibly because of limited resources
(memory/CPU cycles)
MBG_PKG_NOT_FOUND
System Log Message Mobility software package jmobile is not present
Description The mobility software package (jmobile) is not currently installed after jinstall package
installation.
Severity error
Facility LOG_DAEMON
Cause Mobility package is not installed

Action Install jmobile mobility package
MBG_PLATFORM_NOT_SUPPORTED
System Log Message Mobility software is not compatible with the current platform
Description Mobility software is compatible with MODEL_MX960, MODEL_MX480 and

MODEL_MX240.
Severity error
Facility LOG_DAEMON
Cause Platform is not supported by Mobility software
Action Change to compatible platform, Contact technical help
MBG_ROUTING_SOCKET_INIT_FAIL
System Log Message Routing Socket Initialization failure
Description During Mobility infrastructure initialization, internal routing socket library initialization
failed, which is used by different application modules for communication.
Severity error
Facility LOG_DAEMON
Cause Routing socket open failure
MBG_TIMER_CREATE_FAIL
System Log Message Timer task creation failure for Mobility Daemon
Description Mobility Daemon failed to create alarm timer task, which is a periodic timer to poll alarm
related stats.
Severity error
Facility LOG_DAEMON
Cause Failed to create timer task possibly because of limited resources (memory/CPU cycles)

MBG_UI_SERVER_INIT_FAIL
System Log Message Mobility UI server creation failed
Description MObility UI server (which communicates with peers on SPIC) creation failed, there is one
UI server for all peers.
Severity error
Facility LOG_DAEMON
Cause UI server creation failure possibly because of limited resources (memory/CPU cycles)


CHAPTER 79
MCSN System Log Messages
This chapter describes messages with the MCSN 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.
MCSN_SYSTEM
Description A system call made by the multicast snooping process (mcsnoopd) failed.
Severity error
Facility LOG_DAEMON
Cause It is possible that the kernel lacked the resources to fulfill the request. The mcsnoopd
process will recover.


CHAPTER 80
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
Description The MIB II process (mib2d) could not process ATM-related information.
Severity error
Facility LOG_DAEMON
MIB2D_CONFIG_CHECK_FAILED
System Log Message function-name: configuration database has errors
Description The portion of the candidate configuration related to the MIB II process (mib2d) was
checked for validity during a 'commit' operation. The check failed.
Severity error
Facility LOG_DAEMON
Cause The configuration was invalid.
Action Correct the invalid portion of the configuration as described in the error message on the
console.

MIB2D_COUNTER_DECREASING
System Log Message function-name: counter counter-name decreasing for type(index), new(new-value)
old(<old-value)
Description The MIB II process (mib2d) received a counter which value is less than the last retrieved
value.
Severity error
Facility LOG_DAEMON
MIB2D_FILE_OPEN_FAILURE
System Log Message Unable to open file 'filename': error-message
Description The MIB II process (mib2d) could not open the indicated file.
Severity error
Facility LOG_DAEMON
MIB2D_IFD_IFDINDEX_FAILURE
System Log Message Ifd index assigned to interface-name changed from old-value to new-value, removing old
interface
Description There was a change to the ifd Index assigned to the indicated existing interface.
Severity error
Facility LOG_DAEMON
MIB2D_IFD_IFINDEX_FAILURE
System Log Message SNMP index assigned to interface-name changed from old-value to new-value
Description There was a change to the SNMP ifIndex assigned to the indicated existing interface.

Chapter 80: MIB2D System Log Messages
Severity error
Facility LOG_DAEMON
MIB2D_IFL_IFINDEX_FAILURE
System Log Message SNMP index assigned to interface-name.interface-unit changed from old-value to
new-value
Description There was a change to the SNMP ifIndex assigned to the indicated existing interface.
Severity error
Facility LOG_DAEMON
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)
Description The MIB II process (mib2d) is blocked on the kernel for synchronous message. If there is
an interface flap (down and then back up again) in the time mib2d is blocked in the kernel,
mib2d will miss asychronous messages from the kernel about state changes.
Severity notice
Facility LOG_DAEMON
MIB2D_KVM_FAILURE
System Log Message function-name: reason: error-message
Description A call to the indicated function in the kernel virtual memory library failed.
Severity error
Facility LOG_DAEMON

MIB2D_MASTERSHIP_UPDATE
System Log Message Mastership switched new Chassis State chassis-type, new RE State state
Description mib2d process updated its Mastership state. This can happen during GRES, or at daemon
startup.
Severity info
Facility LOG_DAEMON
MIB2D_PMON_OVERLOAD_CLEARED_TRAP
System Log Message Overload name: overload-name, interface: interface-name
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.
Severity warning
Facility LOG_DAEMON
MIB2D_PMON_OVERLOAD_SET_TRAP
System Log Message Overload name: overload-name, interface: interface-name
Description The MIB II process (mib2d) generated a jnxPMonOverloadSet trap when it detected an
overload condition on the indicated monitoring services interface.
Severity warning
Facility LOG_DAEMON
MIB2D_RTSLIB_READ_FAILURE
System Log Message function-name: failed in operation object-name: index (error-message)
Description A call to the indicated function in the routing socket library failed during the indicated
operation on the indicated object.
Severity error
Facility LOG_DAEMON

MIB2D_RTSLIB_SEQ_MISMATCH
System Log Message function-name: sequence mismatch (expected-value, received-value), resyncing
Description 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.
Severity info
Facility LOG_DAEMON
MIB2D_SNMP_INDEX_ASSIGN
System Log Message function-name: reason snmpid(snmp-interface-index)
ifname(interface-name.interface-unit)
Description MIB2D can not assign snmp index for each interface.
Severity error
Facility LOG_DAEMON
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)
Description The SNMP index for first interface name was assigned the same SNMP index as second
interface name.
Severity emergency
Facility LOG_DAEMON
MIB2D_SNMP_INDEX_UPDATE_STAT
System Log Message function-name reason filename

Description MIB2D can not get the status of SNMP index file
Severity error
Facility LOG_DAEMON
MIB2D_SNMP_INDEX_WRITE
System Log Message function-name: reason filename
Description MIB2D can not write into a file containing all the indices
Severity error
Facility LOG_DAEMON
MIB2D_SYSCTL_FAILURE
System Log Message function-name: sysctl type failed: error-message
Description A request to the Junos kernel for system data failed.
Severity error
Facility LOG_DAEMON
MIB2D_TRAP_HEADER_FAILURE
System Log Message function-name: trap_request_header failed
Description The MIB II process (mib2d) could not allocate a trap header.

Severity error
Facility LOG_DAEMON
Cause The Routing Engine is low on memory.
MIB2D_TRAP_SEND_FAILURE
System Log Message function-name: trap_request_send: error-message
Description The MIB II process (mib2d) could not send a trap header.
Severity error
Facility LOG_DAEMON


CHAPTER 81
MPLS System Log Messages
This chapter describes messages with the MPLS 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 fec-address: traceroute fanout limit was reached
Description The traceroute fanout limit was reached.
Severity info
Facility LOG_DAEMON
Action Raise the traceroute fanout limit parameter.
MPLS_OAM_INVALID_SOURCE_ADDRESS
System Log Message fec-address: source address ip-address is invalid
Description The traceroute utility is configured to use an invalid source address.
Severity error
Facility LOG_DAEMON
Action Configure traceroute to use a valid source address.
MPLS_OAM_PATH_LIMIT_REACHED
System Log Message fec-address: traceroute path limit was reached
Description The traceroute path limit was reached.
Severity info

Facility LOG_DAEMON
Action Raise the traceroute path limit parameter.
MPLS_OAM_SEND_FAILED
System Log Message fec-address: unable to send probe (error-message)
Description The Multiprotocol Label Switching (MPLS) Operation, Administration, and Maintenance
(OAM) process (mplsoamd) could not send a traceroute probe packet.
Severity error
Facility LOG_DAEMON
MPLS_OAM_SOCKET_OPEN_FAILED
System Log Message fec-address: unable to open socket (error-message)
(OAM) process (mplsoamd) could not open a socket to initiate a traceroute operation.
Severity error
Facility LOG_DAEMON
MPLS_OAM_SOCKET_SELECT_FAILED
System Log Message fec-address: unable to select socket (error-message)
(OAM) process (mplsoamd) could not select a socket to initiate a traceroute operation.
Severity error
Facility LOG_DAEMON
MPLS_OAM_TRACEROUTE_INTERRUPTED
System Log Message fec-address: topology update interrupted traceroute
Description A traceroute operation was interrupted by a topology change.

Chapter 81: MPLS System Log Messages
Severity info
Facility LOG_DAEMON
Action Wait for the next scheduled traceroute operation.
MPLS_OAM_TTL_EXPIRED
System Log Message fec-address: traceroute TTL limit was reached
Description The time-to-live (TTL) limit for the traceroute utility was reached.
Severity info
Facility LOG_DAEMON
Action Raise the traceroute TTL limit parameter.
MPLS_OAM_UNREACHABLE
System Log Message fec-address: traceroute encountered unreachable node
Description 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.
Severity info
Facility LOG_DAEMON


CHAPTER 82
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 Limit on components reached for flood next hop for routing instance 'routing-instance'
Description 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.
Severity error
Facility ANY


CHAPTER 83
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
OS with enhanced services.
NSD_MEMORY_ALLOC_FAILED
Description The network security process (nsd) could not allocate the indicated number of bytes of
memory.
Severity error
Facility LOG_DAEMON
Cause It is possible that system memory is exhausted.
NSD_RESTART_COMP_CFG_READ_FAILED
Description 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.
Severity error
Facility LOG_DAEMON
NSD_SEC_NODE_COMP_SYNC_FAILED
System Log Message One or more subcomponents could not sync their state on backup RE
Description One or more subcomponents of the network security process (nsd) failed to synchronize
their state when the nsd restarted on secondary mode.

Severity error
Facility LOG_DAEMON


CHAPTER 84
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
Description The USP trace process (nstraced) could not allocate the indicated number of bytes of
memory.
Severity error
Facility LOG_DAEMON
Cause System memory was exhausted.
NSTRACED_RESTART_CFG_READ_FAILED
Description When the USP trace process (nstraced) restarted, it could not read its configuration
information from the configuration database.
Severity error
Facility LOG_DAEMON


CHAPTER 85
NTPDATE System Log Messages
This chapter describes messages with the NTPDATE prefix. They are generated by the
Network Time Protocol process (ntpd) process, which regularly synchronizes system
time with internet time servers.
NTPDATE_TIME_CHANGED
System Log Message step time offset new-value sec
Description The ntp service changed the time of day
Severity info
Facility ANY


CHAPTER 86
NTPD System Log Messages
This chapter describes messages with the NTPD prefix. They are generated by the Network
Time Protocol process (ntpd) process, which regularly synchronizes system time with
internet time servers.
NTPD_CHANGED_TIME
System Log Message time reset rate s
Description The ntp service changed the time of day
Severity info
Facility ANY


CHAPTER 87
PARSE System Log Messages
This chapter describes messages with the PARSE prefix. They are generated by the Virtual
Router Redundancy Protocol (VVRP) process (vrrpd), which provides the user interface
for management of VRRP groups.
PARSE_WARN_DUPLICATE_ROUTER_AD
System Log Message Duplicate 'router-advertisement' configured for interface interface-name
Description Duplicate router-advertisement is configured for given interface.
Severity warning
Facility LOG_DAEMON
PARSE_WARN_NO_LS_ROUTER_AD_CFG
System Log Message 'router-advertisement' is not configured for interface interface-name, logical system:
logical-router-name. It is configured on logical system: logical-system-name
Description Router-advertisement is not configured for an interface (part of a logical system) having
IPv6 vrrp config. Instead its configured on another logical system.
Severity warning
Facility LOG_DAEMON
PARSE_WARN_NO_ROUTER_AD_CFG
System Log Message 'router-advertisement' is not configured for interface interface-name
Description Router-advertisement is not configured for an interface having IPv6 vrrp config.
Severity warning
Facility LOG_DAEMON

PARSE_WARN_PROXY_ARP_CFG_ERR
System Log Message Cannot have more than one VRRP group on subnet ip-address when proxy arp is
configured
Description When proxy arp is configured, you cannot have more than one VRRP group configured
on same subnet.
Severity warning
Facility LOG_DAEMON

CHAPTER 88
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 Error in Analyzer error-message for index = index error-code = error-code
Description The configuration analyzer terminated because an error occured during the configuration.
Severity error
Facility ANY
PFE_ANALYZER_SHIM_CFG_FAILED
System Log Message Error in Analyzer error-message for index = index error-code = error-code
Description The configuration analyzer terminated because an error occured while the chip was being
programmed.
Severity error
Facility ANY
PFE_ANALYZER_TABLE_WRITE_FAILED
System Log Message index Could not create analyzer error-message table
Description The logical interfaces (ifl) index failed to configure the analyzer because of an error.
Severity error
Facility ANY
PFE_ANALYZER_TASK_FAILED
System Log Message Following task failed : error-message

Description The task analyzer terminated because an error occurred during the task.
Severity error
Facility ANY
PFE_CBF_UNSUPPORTED
System Log Message Internet Processor I does not support CoS-based forwarding
Description The Internet Processor I application-specific integrated circuit (ASIC) does not support
class-of-service (CoS)-based forwarding (CBF).
Severity warning
Facility LOG_PFE
PFE_COS_B2_ONE_CLASS
System Log Message COSMAN: classifier classifier-id-new for ifl index replaces classifer classifier-id-old still
used
Description Only one classifier can be active on a B2-based FPC at any given time.
Severity error
Facility LOG_PFE
PFE_COS_B2_UNSUPPORTED
System Log Message COSMAN: B2 FPC cannot support classifier type classifier-type-name
Description B2-based FPCs can only handle IP precedence classifiers. They do not support any other
classifier.
Severity error
Facility LOG_PFE
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
Description 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.

Chapter 88: PFE System Log Messages
Severity error
Facility LOG_PFE
PFE_FW_IF_DIALER_ERR
System Log Message DFW: output type (firewall-name) on ifl logical-interface-index rejected, invalid interface
Description Firewalls that use the ipsec-sa action to forward traffic to an IP Security (IPSec) security
association (SA) cannot be configured on the ES 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.
Severity error
Facility LOG_PFE
PFE_FW_IF_INPUT_ERR
System Log Message DFW: input type (firewall-name) on ifl logical-interface-index rejected, invalid interface
problematic firewall was automatically removed from the indicated interface.
Severity error
Facility LOG_PFE
PFE_FW_IF_OUTPUT_ERR
System Log Message DFW: output type (firewall-name) on ifl logical-interface-index rejected, invalid interface
problematic firewall was automatically removed from the indicated interface.
Severity error
Facility LOG_PFE
PFE_FW_PSF_DELETE_MISMATCH_ERR
System Log Message Instance mismatch for type (installed-firewall-name != deleted-firewall-name) hardware
label index family protocol-family
Description 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.

Severity error
Facility LOG_PFE
PFE_FW_SYSLOG_ETH
System Log Message FW: interface-name action destination-address source-address protocol-name (count
packets)
Description An Ethernet frame matched against a stateless firewall filter with the indicated 'syslog'
action (A = Accept, D = Discard, R = Reject).
Severity info
Facility LOG_PFE
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)
Description An IP packet matched against a stateless firewall filter with the indicated 'syslog' action
(A = Accept, D = Discard, R = Reject).
Severity info
Facility LOG_PFE
PFE_FW_SYSLOG_IP6_GEN
System Log Message FW: interface-name action protocol-name source-address destination-address (count
packets)
Description An IP version 6 (IPv6) packet matched against a stateless firewall filter with the indicated
'syslog' action (A = Accept, D = Discard, R = Reject).
Severity info
Facility LOG_PFE
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)
Description 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).

Severity info
Facility LOG_PFE
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)
Description 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).
Severity info
Facility LOG_PFE
PFE_MGCP_MEM_INIT_FAILED
System Log Message Failed to create memory pool for error-message
Description Failed to initialize the MGCP memory pool.
Severity error
Facility LOG_PFE
PFE_MGCP_REG_HDL_FAIL
System Log Message Failed to register object-name handle
Description Failed to register the handler with the external module.
Severity error
Facility LOG_PFE
PFE_NH_RESOLVE_THROTTLED
System Log Message Next-hop resolution requests from interface logical-interface-index throttled
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.

Severity info
Facility LOG_PFE
PFE_SCCP_ADD_PORT_FAIL
System Log Message Failed to add SCCP ALG port to application definition table
Description Failed to add the SCCP port to the application definition table.
Severity error
Facility LOG_PFE
PFE_SCCP_DEL_PORT_FAIL
System Log Message Failed to remove SCCP ALG port from application definition table
Description Failed to delete the SCCP port from application definition table.
Severity error
Facility LOG_PFE
PFE_SCCP_REG_NAT_VEC_FAIL
System Log Message Failed to add SCCP ALG vector to flow module
Description Failed to register the SCCP vector with the flow module.
Severity error
Facility LOG_PFE
PFE_SCCP_REG_RM_FAIL
System Log Message Failed to register SCCP client to Resource Manager
Description Failed to register the SCCP Resource Manager client.
Severity error
Facility LOG_PFE
PFE_SCCP_REG_VSIP_FAIL
System Log Message Failed to register SCCP client to VoIP State IP port
Description Failed to register the SCCP client to VoIP State IP port.

Severity error
Facility LOG_PFE
PFE_SCCP_RM_CLIENTID_FAIL
System Log Message Failed to get SCCP Resource Manager client identifier
Description Failed to get the SCCP Resource Manager client identifier.
Severity error
Facility LOG_PFE
PFE_SCREEN_MT_CFG_ERROR
System Log Message failed to operation the screen config due to error-message
Description failed to change the configuration of screen module
Severity error
Facility LOG_PFE
PFE_SCREEN_MT_CFG_EVENT
System Log Message [operation]: screen name - context-name
Description configuration of screen module is changed
Severity info
Facility LOG_PFE
PFE_SCREEN_MT_ZONE_BINDING_ERROR
System Log Message screen index1 failed to apply to zone index2 due to reason
Description failed to bind screen to zone
Severity error
Facility LOG_PFE
PFE_SIP_MEM_INIT_FAILED
System Log Message Failed to create memory pool for object-name
Description Failed to create a memory pool for SIP.

Severity error
Facility LOG_PFE
PFE_SIP_REG_HDL_FAIL
System Log Message Failed to register object-name handle
Description Failed to register the handler with the external module.
Severity error
Facility LOG_PFE

CHAPTER 89
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 Unable to retrieve notification statistics
Description The Packet Forwarding Engine process (pfed) could not retrieve Packet Forwarding
Engine notification statistics.
Severity info
Facility LOG_PFE


CHAPTER 90
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 The pgcpd process shut down
Description The packet gateway control process (pgcpd) state was shut down.
Severity notice
Facility LOG_DAEMON
PGCPD_STARTUP
System Log Message The pgcpd process just started up
Description The packet gateway control process (pgcpd) just started up
Severity notice
Facility LOG_DAEMON
PGCPD_SWITCH_OVER
System Log Message switch over
Description Switch over from active to backup Routing Engine
Severity warning
Facility LOG_DAEMON


CHAPTER 91
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 pingCtlOwnerIndex = test-owner, pingCtlTestName = test-name
Description The jitter for the egress trip time exceeded the configured threshold during the indicated
test conducted by the indicated user.
Severity info
Facility LOG_DAEMON
PING_EGRESS_STDDEV_THRESH_EXCEED
Description The standard deviation of the egress trip time exceeded the configured threshold during
the indicated test conducted by the indicated user.
Severity info
Facility LOG_DAEMON
PING_EGRESS_THRESHOLD_EXCEEDED
Description The egress trip time measured for a probe exceeded the configured threshold during the
indicated test conducted by the indicated user.
Severity info
Facility LOG_DAEMON

PING_INGRESS_JTR_THRESH_EXCEED
Description The jitter for the ingress trip time exceeded the configured threshold during the indicated
Severity info
Facility LOG_DAEMON
PING_INGRESS_STDDV_THRESH_EXCEED
Description The standard deviation of the ingress trip time exceeded the configured threshold during
Severity info
Facility LOG_DAEMON
PING_INGRESS_THRESHOLD_EXCEEDED
Description The ingress trip time measured for a probe exceeded the configured threshold during the
Severity info
Facility LOG_DAEMON
PING_PROBE_FAILED
Description The number of successive probe failures exceeded the pingCtlTrapProbeFailureFilter

threshold.
Severity info
Facility LOG_DAEMON
PING_RTT_JTR_THRESH_EXCEED
Description The jitter for the round trip time exceeded the configured threshold during the indicated

Chapter 91: PING System Log Messages
Severity info
Facility LOG_DAEMON
PING_RTT_STDDV_THRESH_EXCEED
Description The standard deviation of the round trip time exceeded the configured threshold during
Severity info
Facility LOG_DAEMON
PING_RTT_THRESHOLD_EXCEEDED
Description The round trip time measured for a probe exceeded the configured threshold during the
Severity info
Facility LOG_DAEMON
PING_TEST_COMPLETED
Description All probes were sent and the number of failed probes was less than the
pingCtlTrapTestFailureFilter threshold.
Severity info
Facility LOG_DAEMON
PING_TEST_FAILED
Description All probes were sent but the number of failed probes equaled or exceeded the
pingCtlTrapTestFailureFilter threshold.
Severity info
Facility LOG_DAEMON

PING_UNKNOWN_THRESH_TYPE_EXCEED
Description An unknown type of threshold event was reported during the indicated test conducted
by the indicated user.
Severity info
Facility LOG_DAEMON

CHAPTER 92
PKID System Log Messages
This chapter describes messages with the PKID prefix. They are generated by the Public
Key Infrastructure process (pkid), which supports Public Key Infrastructure by maintaining
keypairs, certificates and CRLs. It also provides a mechanism to authenticate and enroll
certificates.
PKID_AFTER_KEY_GEN_SELF_TEST
System Log Message Running FIPS self-tests after key generaration
Description Running FIPS self-tests for PRNG, HMAC-SHA, RSA, and DSA.
Severity info
Facility LOG_DAEMON
PKID_CERT_BASIC_CNSTRS_INV_CA
System Log Message Basic constraints field contains an invalid CA flag for the CA certificate argument1
Description Certificate doesn't have valid CA flag.
Severity error
Facility LOG_DAEMON
PKID_CERT_BASIC_CNSTRS_MISSING
System Log Message Basic constraints field is missing for the CA certificate argument1
Description Certificate has no basic constraints field.
Severity error
Facility LOG_DAEMON
PKID_CERT_ID_LOOKUP_FAIL
System Log Message Certificate chain does not contain certificate with ID argument1 and Type argument2

Description Certificate chain doen't contain certificate with valid ID. The IKE-ID must match with
once of the certificate's ID.
Severity error
Facility LOG_DAEMON
PKID_CERT_NOT_AFTER_FAIL
System Log Message Certificate argument1 has expired, not valid after argument2
Description Certificate is expired. Get new certificate to continue.
Severity error
Facility LOG_DAEMON
PKID_CERT_NOT_BEFORE_FAIL
System Log Message Certificate argument1 is not valid until argument2
Description Certficate validity period is in future. Use the certificate after it becomes valid.
Severity error
Facility LOG_DAEMON
PKID_CERT_SIGN_VERIFY_FAIL
System Log Message Signature verification failed for certificate type-string
Description Signature validation failed for the certificate. The certificate might be tampered.
Severity error
Facility LOG_DAEMON
PKID_CORRUPT_CERT
System Log Message Certificate subject field does not match length: error-message
Description The certificate subject name and length are inconsistent.
Severity error
Facility LOG_DAEMON

Chapter 92: PKID System Log Messages
PKID_CRL_CERTIFICATE_REVOKED
System Log Message Certificate argument1 with serial number argument2 is revoked
Description Signature verification failed for CRL file received from CA server.
Severity error
Facility LOG_DAEMON
PKID_CRL_CHECK_SKIPPED
System Log Message CRL check skipped for certificate argument1 with serial argument2 due to CRL download
failure
Description Skipped CRL check as disable on-download-failure option is configured for the CA profile.
Severity info
Facility LOG_DAEMON
PKID_CRL_DOWNLOAD_FAIL_LF
System Log Message CRL download failed due to large file for CA type-string, next retry user-seconds seconds
Description CRL file size has exceeded the allowed limit. Reduce CRL file size on CA server to download
CRL successfully.
Severity error
Facility LOG_DAEMON
PKID_CRL_DOWNLOAD_SUCCESS
System Log Message CRL download successful for CA type-string, next refresh user-seconds seconds
Description CRL downloaded from CA server. Next refresh interval is based on configured value or
CRL expiry time, whichever is earlier.
Severity info
Facility LOG_DAEMON
PKID_CRL_LOCAL_CERT_REVOKED
System Log Message Local certificate argument1 is revoked, subject argument2 serial-number argument3
Description Local certificate cannot be used for PKI based authentication as it is revoked by CA server
or CA is unreachable. Please use new local certificate or make sure that CA server is
reachable.

Severity error
Facility LOG_DAEMON
PKID_CRL_SIGNATURE_FAIL
System Log Message CRL signature verification failed for CA type-string
Description Signature verification failed for CRL file received from CA server.
Severity error
Facility LOG_DAEMON
PKID_FIPS_DSA_NOT_ALLOWED
System Log Message DSA argument1 argument2 not loaded because the Digital Signature Algorithm (DSA) is
not permitted in a FIPS-compliant system .
Description DSA key-pair or certificate not loaded because it is not FIPS compliant
Severity error
Facility LOG_DAEMON
PKID_FIPS_KAT_SUCCESS
System Log Message FIPS test-name Known Answer Test executed successfully
Description The FIPS Known Answer Test completed successfully.
Severity info
Facility LOG_DAEMON
PKID_FIPS_RSA_TOO_WEAK
System Log Message RSA argument1 argument2 not loaded because the modulus size (argument3 bits) is not
permitted in a FIPS-compliant system.
Description Weak RSA key-pair or certificate not loaded because it is not FIPS compliant
Severity error
Facility LOG_DAEMON
PKID_NO_CA_CERT
System Log Message CA Certificate for certificate type-string not found in local database

Description CA certficate for the local certificate is not present in local storage. Enroll CA certificate
to continue.
Severity error
Facility LOG_DAEMON
PKID_NO_KEYPAIR
System Log Message Keypair not found for local certficate type-string
Description Keypair must be generated for the local certificate. After generating keypair, enroll the
local certificate to continue.
Severity error
Facility LOG_DAEMON
PKID_NO_LOCAL_CERT
System Log Message Local certficate type-string is not enrolled
Description Local certificate is not present in storage. Enroll local certificate to continue.
Severity error
Facility LOG_DAEMON
PKID_OCSP_CA_CERT_MISSING
System Log Message The OCSP response from responder argument1 cannot be verified; the CA certificate is
missing.
Description OCSP response cannot be verified, missing CA.
Severity error
Facility LOG_DAEMON
PKID_OCSP_CONNECTION_FAILOVER
System Log Message The OCSP responder failed over from argument1 to argument2 because of a connection
failure.
Description OCSP connection failed, failover next responder.
Severity error

Facility LOG_DAEMON
PKID_OCSP_FALLBACK_TO_CRL
System Log Message The OCSP check was skipped. CRL is being used for revocation check for certificate
argument1
Description Use CRL to check revocation status as OCSP responder is unreachable.
Severity error
Facility LOG_DAEMON
PKID_OCSP_NONCE_CHECK_FAIL
System Log Message The nonce check failed for OCSP responder argument1.
Description Nonce check failed for OCSP response.
Severity error
Facility LOG_DAEMON
PKID_OCSP_RESPONSE_INT_ERROR
System Log Message The OCSP responder argument1 has an internal error.
Description Response from OCSP responder has internal error.
Severity error
Facility LOG_DAEMON
PKID_OCSP_RESPONSE_MALFORMED
System Log Message The OCSP response from responder argument1 is malformed.
Description Response from OCSP responder is malformed.
Severity error
Facility LOG_DAEMON
PKID_OCSP_RESPONSE_SIGN_REQUIRED
System Log Message The OCSP request was rejected by responder argument1 as it requires signed requests.
Description OCSP responder accepts signed requests only.

Severity error
Facility LOG_DAEMON
PKID_OCSP_RESPONSE_TRY_LATER
System Log Message The OCSP responder argument1 is busy; try later.
Description OCSP responder expects to try revocation check later.
Severity error
Facility LOG_DAEMON
PKID_OCSP_RESPONSE_UNAUTHORIZED
System Log Message The OCSP responder argument1 does not accept requests from unauthorized clients.
Description OCSP responder accepts requests from authorized clients.
Severity error
Facility LOG_DAEMON
PKID_OCSP_RESP_CA_CERT_MISSING
System Log Message The OCSP responder argument1 certificate cannot be verified; the CA certificate is missing.
Description OCSP responder certificate verification failed, missing CA.
Severity error
Facility LOG_DAEMON
PKID_OCSP_RESP_CERT_REVOKED
System Log Message The revocation check failed for OCSP responder certificate, subject argument1
serial-number argument2
Description The revocation check for OCSP responder certificate failed.
Severity error
Facility LOG_DAEMON
PKID_OCSP_RESP_CERT_VERIFY_FAIL
System Log Message The OCSP responder argument1 certificate signature verification failed.
Description OCSP responder certificate verification failed.

Severity error
Facility LOG_DAEMON
PKID_OCSP_SIGN_VERIFY_FAIL
System Log Message The OCSP response signature verification failed for responder argument1
Description OCSP responder signature verification failed.
Severity error
Facility LOG_DAEMON
PKID_OCSP_SKIP_REVOCATION_CHECK
System Log Message The OCSP revocation check was skipped for certificate argument1
Description Skip OCSP revocation check as responder is unreachable.
Severity error
Facility LOG_DAEMON
PKID_PV_ASYM_KEYGEN
System Log Message Asymmetric key-pair (error-message) generation failure
Description An asymmetric key has failed to generate.
Severity error
Facility LOG_DAEMON
PKID_PV_CERT_DEL
System Log Message Certificate deletion has occurred for type-string
Description A certificate has been deleted.
Severity notice
Facility LOG_DAEMON
PKID_PV_CERT_LOAD
System Log Message Certificate type-string has been successfully loaded
Description A certificate has been loaded.

Severity notice
Facility LOG_DAEMON
PKID_PV_KEYPAIR_DEL
System Log Message Key-Pair deletion failed for type-string
Description Key-Pair deletion for a digital signature failed.
Severity notice
Facility LOG_DAEMON
PKID_PV_KEYPAIR_GEN
System Log Message A argument1 bit argument2 key-Pair has been generated for argument3
Description Key-Pair for a digital signature is generated.
Severity notice
Facility LOG_DAEMON
PKID_PV_OBJECT_READ
System Log Message A PKI object was read into memory fro source-filename
Description A PKI object was read from storage.
Severity info
Facility LOG_DAEMON
PKID_SCEP_INV_DIGEST_ALG
System Log Message Enrollment failed as SCEP server response was signed with argument1 digest, when client
request was signed with argument2 digest.
Description SCEP enrollment failed as server response was signed with wrong algorithm
Severity error
Facility LOG_DAEMON
PKID_SCEP_INV_ENCRYPT_ALG
System Log Message Enrollment failed as SCEP server response was encrypted with argument1 algorithm,
when client request was encrypted with argument2 algorithm.

Description SCEP enrollment failed as server response was encrypted with wrong algorithm
Severity error
Facility LOG_DAEMON
PKID_UNABLE_TO_GET_CRL
System Log Message Failed to retrieve CRL from received file for CA type-string
Description Failed to retrieve CRL from received CRL file from CA server. Check the CRL file format.
Severity error
Facility LOG_DAEMON

CHAPTER 93
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
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
Description 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.
Severity error
Facility LOG_NEWS
ready to provide the list of messages and the diagnostic core file, if requested. For more
information, see http://kb.juniper.net/InfoCenter/index?page=content&id=KB19021.
PPMD_MIRROR_ERROR
System Log Message Unable to establish BFD mirror connection between Routing Engines: error-message
Description The PPMD could not establish the mirror connection between the master and backup
Routing Engines.
Severity warning
Facility LOG_NEWS

OS.
PPMD_OPEN_ERROR
System Log Message function-name: open error on pipe to protocol-name (error-message)
Description The periodic packet management process (ppmd) could not initialize the indicated
protocol.
Severity error
Facility LOG_NEWS
PPMD_READ_ERROR
System Log Message Read error on pipe from protocol-name: reason (error-message)
Description The periodic packet management process (ppmd) could not read a message on a pipe
for the indicated protocol.
Severity info
Facility LOG_NEWS
PPMD_WRITE_ERROR
System Log Message function-name: write error on pipe to protocol-name (error-message)
Description The periodic packet management process (ppmd) could not write a message on a pipe
for the indicated protocol.
Severity error
Facility LOG_NEWS

CHAPTER 94
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 Unable to allocate authentication handle: error-message
Description The Point-to-Point Protocol process (pppd) could not allocate an authentication object,
Severity error
Facility LOG_AUTH
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
Description 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.
Severity error
Facility LOG_AUTH
PPPD_CHAP_GETHOSTNAME_FAILED
System Log Message interface-name: Unable to obtain hostname for outgoing CHAP message: error-message
Description The Point-to-Point Protocol process (pppd) could not obtain the hostname needed to
fill in the 'Name' field in an outgoing CHAP packet.
Severity error

Facility LOG_AUTH
PPPD_CHAP_INVALID_IDENTIFIER
System Log Message Interface interface-name received 'operation' message with CHAP ID message-id instead
of expected ID expected-value
Description 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.
Severity info
Facility LOG_AUTH
PPPD_CHAP_INVALID_OPCODE
System Log Message interface-name: received invalid operation code operation (type operation-code, CHAP
ID message-id)
Description The Point-to-Point Protocol process (pppd) received a Challenge Handshake

Authentication Protocol (CHAP) message that included the indicated operation code,
which is invalid.
Severity error
Facility LOG_AUTH
PPPD_CHAP_LOCAL_NAME_UNAVAILABLE
System Log Message Unable to determine value for 'Name' in outgoing CHAP packet
Description 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.
Severity error
Facility LOG_AUTH
PPPD_CHAP_OPERATION_UNEXPECTED
System Log Message interface-name: unexpected operation type operation (CHAP ID message-id)
Description The Challenge Handshake Authentication Protocol (CHAP) message with the indicated
identifier had the indicated operation type, which the Point-to-Point Protocol process
(pppd) did not expect.

Chapter 94: PPPD System Log Messages
Severity info
Facility LOG_AUTH
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.
Description 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.
Severity error
Facility LOG_AUTH
PPPD_EVLIB_CREATE_FAILURE
System Log Message Unable to create event context: error-message
Description The Point-to-Point Protocol process (pppd) could not create a context for handling
asynchronous events, for the indicated reason.
Severity error
Facility LOG_AUTH
PPPD_LOCAL_CREATE_FAILED
System Log Message Unable to allocate LOCAL module handle: error-message
Description 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.
Severity error
Facility LOG_AUTH
PPPD_MEMORY_ALLOCATION_FAILURE
System Log Message Unable to allocate memory for object object-name: error-message
Description The Point-to-Point Protocol process (pppd) could not allocate memory from the heap
for the indicated object.

Severity error
Facility LOG_AUTH
PPPD_PAP_GETHOSTNAME_FAILED
System Log Message Unable to obtain hostname for PAP message sent from interface interface-name:
error-message
Description 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.
Severity error
Facility LOG_AUTH
PPPD_PAP_INVALID_IDENTIFIER
System Log Message Interface interface-name received 'operation' message with PAP ID message-id instead
of expected ID expected-value
Description 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.
Severity info
Facility LOG_AUTH
PPPD_PAP_INVALID_OPCODE
System Log Message Interface interface-name received 'operation' message with PAP ID message-id and invalid
operation code operation-code
(PAP) message from a peer that included the indicated operation code, which is invalid.
Severity error
Facility LOG_AUTH
PPPD_PAP_LOCAL_PASSWORD_UNAVAIL
System Log Message Unable to determine value for 'Password' in outgoing PAP packet
Description The Point-to-Point Protocol process (pppd) could not determine the value to write in
the 'Password' field in an outgoing Password Authentication Protocol (PAP) packet.

Severity error
Facility LOG_AUTH
Cause The local password was not defined for the local hostname.
PPPD_PAP_OPERATION_UNEXPECTED
System Log Message interface-name: unexpected operation type operation (PAP ID message-id)
(PAP) message with the indicated identifier and operation type. The operation type was
not valid.
Severity info
Facility LOG_AUTH
PPPD_POOL_ADDRESSES_EXHAUSTED
System Log Message No addresses available in pool "pool-name" to assign to remote peer on interface
interface-name
Description 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.
Severity error
Facility LOG_AUTH
Action Increase the number of addresses in the address pool.
PPPD_RADIUS_ADD_SERVER_FAILED
System Log Message Unable to add RADIUS server radius-server for profile access-profile: error-message
Description The Point-to-Point Protocol process (pppd) could not add the indicated RADIUS server
for the indicated access profile.
Severity error
Facility LOG_AUTH
PPPD_RADIUS_ALLOC_PASSWD_FAILED
System Log Message Unable to allocate RADIUS password of size size: error-message

Description 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.
Severity error
Facility LOG_AUTH
PPPD_RADIUS_CREATE_FAILED
System Log Message Unable to allocate RADIUS module handle: error-message
Description The Point-to-Point Protocol process (pppd) attempted to allocate a RADIUS

authentication module as part of its authentication sequence. The allocation failed.
Severity error
Facility LOG_AUTH
PPPD_RADIUS_CREATE_REQ_FAILED
System Log Message Unable to create RADIUS access request message: error-message
Description The Point-to-Point Protocol process (pppd) could not create an access request message
to send to the RADIUS server.
Severity error
Facility LOG_AUTH
PPPD_RADIUS_GETADDRINFO_FAILED
System Log Message Unable to resolve radius-sever address: error-message
Description The Point-to-Point Protocol process (pppd) could not resolve radius-server address
configured.
Severity error
Facility LOG_AUTH
PPPD_RADIUS_GETHOSTNAME_FAILED
Description 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.

Severity error
Facility LOG_AUTH
PPPD_RADIUS_MESSAGE_UNEXPECTED
System Log Message Unknown response from RADIUS server: return-value
Description The RADIUS authentication module for the Point-to-Point Protocol process (pppd)
received a message from the RADIUS server that it could not process.
Severity error
Facility LOG_AUTH
PPPD_RADIUS_NO_VALID_SERVERS
System Log Message Unable to find valid RADIUS server for profile access-profile
Description The Point-to-Point Protocol process (pppd) could not access a valid RADIUS server to
use for the indicated access profile.
Severity error
Facility LOG_AUTH
PPPD_RADIUS_OPEN_FAILED
System Log Message rad_auth_open failed: error-message
Description The Point-to-Point Protocol process (pppd) could not create a RADIUS object handle,
which it uses to communicate with the RADIUS server.
Severity error
Facility LOG_AUTH
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
Description The indicated routing instance, which the Point-to-Point Protocol process (pppd) uses
for routing of RADIUS packets, was not defined.
Severity notice
Facility LOG_AUTH

Cause The process of adding the required routing instance was still in progress when the message
was logged.
Action None required. Authentication with the indicated RADIUS server is automatically
reattempted, and can succeed when the interface exists.

CHAPTER 95
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 SIGHUP - re-reading configuration
Description In response to a SIGHUP signal, the profiler service process (profilerd) read its
configuration from the configuration database
Severity info
Facility LOG_DAEMON


CHAPTER 96
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 PICs.
RDD_EVLIB_CREATE_FAILURE
System Log Message evCreate failed (error-message)
Description The redundant interfaces process (rdd) could not create a context used for handling all
asynchronous events (such as timers and message availability).
Severity emergency
Facility LOG_DAEMON

RDD_IFDEV_ADD_FAILURE
System Log Message function-name: unable to add interface device interface-name (error-message)
Description The redundant interfaces process (rdd) could not create an interface device because an
error occurred during the indicated call to the routing socket library.
Severity error
Facility LOG_DAEMON
RDD_IFDEV_DELETE_FAILURE
System Log Message function-name: rtslib delete operation failed for interface device interface-name
(error-message)
Description The redundant interfaces process (rdd) could not delete an interface device because an

Severity error
Facility LOG_DAEMON
RDD_IFDEV_GET_FAILURE
System Log Message function-name: rtslib get operation failed for interface device interface-name
(error-message)
Description The redundant interfaces process (rdd) could not get an interface device because an
Severity error
Facility LOG_DAEMON
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
Description 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.
Severity error
Facility LOG_DAEMON
RDD_IFDEV_INCOMPATIBLE_SWITCH
System Log Message Unable to switch rsp-interface-name to secondary interface secondary-interface-name;
PIC is incompatible with primary
Description 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.
Severity error
Facility LOG_DAEMON

Chapter 96: RDD System Log Messages
RDD_IFDEV_RETRY_NOTICE
System Log Message function-name: repeated attempt to add interface device interface-name failed
(error-message)
Description 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.
Severity warning
Facility LOG_DAEMON
Cause Necessary resources might have been unavailable. They should become available soon.
RDD_NEW_INTERFACE_STATE
System Log Message Event event-name changed state of interface interface-name from 'old-state' to
'new-state'
Description The indicated event on the indicated redundant interface changed the interface state
as indicated.
Severity info
Facility LOG_DAEMON


CHAPTER 97
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 Multicast address is not allowed
Description 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.
Severity error
Facility LOG_DAEMON
RMOPD_ADDRESS_SOURCE_INVALID
System Log Message Source address invalid: error-message
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.
Severity notice
Facility LOG_DAEMON
RMOPD_ADDRESS_STRING_FAILURE
System Log Message Unable to convert numeric address to string: error-message
Description The remote Simple Network Management Protocol (SNMP) operations process (rmopd)
could not convert a numeric host address to the corresponding hostname text string.

Severity error
Facility LOG_DAEMON
RMOPD_ADDRESS_TARGET_INVALID
System Log Message rmop_util_set_address status message: error-message
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.
Severity error
Facility LOG_DAEMON
RMOPD_ICMP_ADDR_TYPE_UNSUPPORTED
System Log Message Only IPv4 source address is supported
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.
Severity error
Facility LOG_DAEMON
RMOPD_IFINDEX_NOT_ACTIVE
System Log Message ifindex: snmp-interface-index
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.
Severity error
Facility LOG_DAEMON
RMOPD_IFINDEX_NO_INFO
System Log Message No information for snmp-interface-index, message: error-message

Chapter 97: RMOPD System Log Messages
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.
Severity error
Facility LOG_DAEMON
RMOPD_IFNAME_NOT_ACTIVE
System Log Message ifname: interface-name
by either its numerical index or its name. The indicated name was invalid because it
represents an inactive interface.
Severity error
Facility LOG_DAEMON
RMOPD_IFNAME_NO_INFO
System Log Message No information for interface-name, message: error-message
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.
Severity error
Facility LOG_DAEMON
RMOPD_ROUTING_INSTANCE_NO_INFO
System Log Message No information for routing instance routing-instance: error-message
Description The indicated routing instance does not exist, so the Simple Network Management
Protocol (SNMP) remote operations process (rmopd) could not retrieve information
about it.
Severity error
Facility LOG_DAEMON
RMOPD_TRACEROUTE_ERROR
System Log Message Message: error-message

Description The traceroute application reported the indicated error message to the Simple Network
Management Protocol (SNMP) remote operations process (rmopd).
Severity notice
Facility LOG_DAEMON

CHAPTER 98
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_AMT_CFG_ADDR_FMLY_INVALID
System Log Message Valid address family information is required
Description An invalid address family value was encountered while parsing AMT configuration.
Severity warning
Facility ANY
Action Modify the configuration statement to use a valid value.
RPD_AMT_CFG_ANYCAST_INVALID
System Log Message An invalid anycast-prefix is configured
Description An invalid anycast prefix was encountered while parsing AMT configuration.
Severity warning

Facility ANY
RPD_AMT_CFG_ANYCAST_MCAST
System Log Message Anycast-prefix route-prefix cannot be a multicast address
Description A multicast address cannot be configured as the anycast-prefix
Severity warning
Facility ANY
RPD_AMT_CFG_LOC_ADDR_INVALID
System Log Message An invalid local-address is configured
Description An invalid local address was encountered while parsing AMT configuration.
Severity warning
Facility ANY
RPD_AMT_CFG_LOC_ADDR_MCAST
System Log Message Local-address route-prefix cannot be a multicast address
Description A multicast address cannot be configured as the local-address.
Severity warning
Facility ANY
RPD_AMT_CFG_PREFIX_LEN_SHORT
System Log Message Prefix length prefix-length is too short for prefix route-prefix
Description The prefix length for the indicated prefix is too short and it has a non-zero host portion.
Excess host bits will be ignored.
Severity warning

Chapter 98: RPD System Log Messages
Facility ANY
RPD_AMT_CFG_RELAY_INVALID
System Log Message Invalid relay information is configured
Description Invalid relay configuration was encountered while parsing AMT configuration.
Severity warning
Facility ANY
RPD_AMT_RELAY_DISCOVERY
System Log Message AMT relay discovery message from gateway destination-address port destination-port
at time
Description AMT relay discovery event.
Severity info
Facility ANY
RPD_AMT_TUNNEL_CREATE
System Log Message Tunnel created between gateway destination-address port destination-port relay
source-address port source-port on interface interface-name at time
Description AMT tunnel create event.
Severity info
Facility ANY
RPD_AMT_TUNNEL_DELETE
System Log Message Tunnel deleted between gateway destination-address port destination-port relay
source-address port source-port on interface interface-name at time
Description AMT tunnel delete event.
Severity info
Facility ANY

RPD_AMT_UCAST_STRM_LMT_EXCEEDED
System Log Message AMT ucast stream cnt exceeded max ucast streamlimit and this should not have
happened
Description unicast stream limit cannot exceed the maximum unicast stream limit configured. This
should not have happened.
Severity error
Facility ANY
RPD_BGP_CFG_ADDR_INVALID
System Log Message Invalid argument address ip-address
Description An invalid local or neighbor address was encountered while parsing BGP configuration.
Severity warning
Facility LOG_DAEMON
RPD_BGP_CFG_LOCAL_ASNUM_WARN
System Log Message local as-number cannot be set to confederation as-number data-id, statement ignored
Description Local autonomous-system number cannot be set to the confederation

autonomous-system number. Statement will be ignored.
Severity warning
Facility LOG_DAEMON
RPD_BGP_NEIGHBOR_LLST_EXPIRED
System Log Message peer-name: Long-lived stale timer expired for nlri-type nlri (instance instance) -- purging
stale routes
Description The graceful restart long-lived stale timer (LLST) expired for a peer. Routes from that
peer that were previously held in Long-Lived Stale state will now be purged.
Severity warning
Facility LOG_DAEMON

RPD_BGP_NEIGHBOR_STATE_CHANGED
System Log Message BGP peer peer-name changed state from old-state to new-state (event event-type)
(instance instance)
Description 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.
Severity warning
Facility LOG_DAEMON
RPD_DYN_CFG_BUSY_SIGNAL_FAILED
System Log Message Dynamic config action busy signal failed: error-message
Description The routing protocol process (rpd) failed to notify the dynamic configuration clients
about its availability to process the dynamic configuration requests.
Severity error
Facility LOG_DAEMON
RPD_DYN_CFG_GET_PROFILE_FAILED
System Log Message Get dynamic profiles failed: error-code
Description The routing protocol process (rpd) tried to load a profile from the database and failed.
Severity error
Facility LOG_DAEMON
RPD_DYN_CFG_GET_PROF_NAME_FAILED
System Log Message Get profile name for session client-session-id failed: error-code
Description The routing protocol process (rpd) tried to get the profile name from the session snapshot
and failed.
Severity error

Facility LOG_DAEMON
RPD_DYN_CFG_GET_SES_STATE_FAILED
System Log Message Get session state for session client-session-id failed: error-code
Description The routing protocol process (rpd) failed to get the session state from the session
snapshot.
Severity error
Facility LOG_DAEMON
RPD_DYN_CFG_GET_SES_TYPE_FAILED
System Log Message Get session type for session client-session-id failed: error-code
Description The routing protocol process (rpd) tried to get the session type from the session snapshot
and failed.
Severity error
Facility LOG_DAEMON
RPD_DYN_CFG_GET_SNAPSHOT_FAILED
System Log Message Get session id client-session-id snapshot failed: error-code
Description The routing protocol process (rpd) tried to load client session data from the database
and failed.
Severity error
Facility LOG_DAEMON
RPD_DYN_CFG_PDB_CLOSE_FAILED
System Log Message Failed to close profile database: error-code

Description The routing protocol process (rpd) tried to close the profile database and failed.
Severity error
Facility LOG_DAEMON

RPD_DYN_CFG_PDB_OPEN_FAILED
System Log Message Failed to open profile database: error-code
Description The routing protocol process (rpd) tried to open the profile database and failed.
Severity error
Facility LOG_DAEMON

RPD_DYN_CFG_REGISTER_FAILED
System Log Message Dynamic config registration failed: error-message
Description The routing protocol process (rpd) tried to register with the dynamic configuration
subsystem and failed.
Severity error
Facility LOG_DAEMON

RPD_DYN_CFG_REQUEST_ACK_FAILED
System Log Message Failed to ack request data-id: error-code
Description The routing protocol process (rpd) tried to acknowledge a dynamic configuration request
and failed.
Severity error
Facility LOG_DAEMON


RPD_DYN_CFG_RESPONSE_SLOW
System Log Message Dynamic config response for session id client-session-id took system-seconds seconds
Description The routing protocol process (rpd) is responding slowly to dynamic config requests.
Severity error
Facility LOG_DAEMON
RPD_DYN_CFG_SCHEMA_OPEN_FAILED
System Log Message Could not open configuration schema: error-message
Description The routing protocol process (rpd) tried to open the configuration schema and failed.
Severity error
Facility LOG_DAEMON

RPD_DYN_CFG_SES_RECOVERY_FAILED
System Log Message Recovery of session client-session-id failed
Description The routing protcol process (rpd) tried to recover a session and failed.
Severity error
Facility LOG_DAEMON
RPD_DYN_CFG_SET_CONTEXT_FAILED
System Log Message Set dynamic config context for profile profile-name session client-session-id failed
Description The routing protocol process (rpd) tried to set up the dynamic configuration context and
failed.

Severity error
Facility LOG_DAEMON
RPD_DYN_CFG_SMID_RECOVERY_FAILED
System Log Message Dynamic config send recovery complete failed: error-code
Description The routing protocol process (rpd) tried to send recovery complete to SMID and failed.
Severity error
Facility LOG_DAEMON
RPD_DYN_CFG_SMID_REG_FAILED
System Log Message Failed to open session database: error-code
Description The routing protocol process (rpd) tried to register with SMID and failed.
Severity info
Facility LOG_DAEMON
RPD_DYN_CFG_SMID_UNREG_FAILED
System Log Message Failed to unregister with SMID: error-code
Description The routing protocol process (rpd) tried to unregister with SMID and failed.
Severity error
Facility LOG_DAEMON
RPD_ESIS_ADJDOWN
System Log Message ES-IS lost adjacency-type adjacency to neighbor-nsap-netn on interface-name, reason:
reason
Description 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.
Severity notice
Facility LOG_DAEMON
Cause The communication path to the neighboring router was disrupted, a protocol error
occurred, or the neighboring router was powered down.

RPD_ESIS_ADJUP
System Log Message ES-IS new adjacency-type adjacency to neighbor-nsap-netn on interface-name
Description An ES-IS adjacency was established with the indicated neighboring router. The local
router can now exchange information with it.
Severity info
Facility LOG_DAEMON
RPD_FEC129_AII_COLLISION
System Log Message Attachment-individual-identifier attachment-individual-identifier in VPN vpn-name learned
from PE peer-address with RD route-discriminator is also configured locally
Description The remote provider edge (PE) router with the indicated address which is a member of
the indicated virtual private network (VPN) advertised an attachment individual identifier
(AII), but the AII is already associated with a local site.
Severity error
Facility LOG_DAEMON
RPD_FEC129_AII_COLLISION_CLEARED
System Log Message Attachment-individual-identifier collision cleared for AII attachment-individual-identifier
in VPN vpn-name
Description A collision between two attachment individual identifiers (AIIs) with the indicated value
has been cleared for the indicated virtual private network (VPN).
Severity notice
Facility LOG_DAEMON
RPD_FEC129_REMOTE_AII_COLLISION
System Log Message Attachment-individual-identifier attachment-individual-identifier in VPN vpn-name learned
from PE peer-address with RD route-discriminator was also learned from PE
neighbor-address with RD route-discriminator2
Description Two provider edge (PE) routers which are members of the the indicated virtual private
network (VPN) are both configured with the same attachment-individual-identifier (AII).
The identities of the two PEs are indicated by the IP addresses and first and second route
discriminators.
Severity error

Facility LOG_DAEMON
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)
Description 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.
Severity error
Facility LOG_DAEMON
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_IFD_NAMECOLLISION
System Log Message Physical interface collision -- different name, same index (new new-interface-name
new-index, old old-interface-name old-value)
Description The routing protocol process (rpd) received a message from the kernel in which the name
associated with the indicated numerical interface index differed from the name-to-index
mapping maintained by rpd.
Severity error
Facility LOG_DAEMON
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)
numerical index associated with the indicated interface name differed from the
index-to-name mapping maintained by rpd.
Severity error
Facility LOG_DAEMON

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)
Description The routing protocol process (rpd) received a message from the kernel in which the name
associated with the indicated numerical interface index differed from the name-to-index
mapping maintained by rpd.
Severity error
Facility LOG_DAEMON
RPD_IGMP_ACCOUNTING_OFF
System Log Message interface-name time
Description Internet Group Management Protocol (IGMP) accounting for the indicated interface was
disabled at the indicated time.
Severity info
Facility LOG_DAEMON
RPD_IGMP_ACCOUNTING_ON
Description Internet Group Management Protocol (IGMP) accounting for the indicated interface was
enabled at the indicated time.
Severity info
Facility LOG_DAEMON
RPD_IGMP_ALL_SUBSCRIBERS_DELETED
System Log Message All IGMP subscribers on interface interface-name deleted at time because the interface
is down
Description All IGMP subscribers have been deleted because the interface is down.
Severity info
Facility LOG_DAEMON

RPD_IGMP_CFG_CREATE_ENTRY_FAILED
System Log Message Could not create entry for entry.
Description Internet Group Management Protocol (IGMP) failed to create the indicated configuration
entry. The configuration request failed.
Severity error
Facility LOG_DAEMON
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.
Description The configuration request failed because the indicated configuration object contained
a group that is out of range.
Severity error
Facility LOG_DAEMON
Action Modify configuration statement to use a valid value.
RPD_IGMP_CFG_INVALID_VALUE
System Log Message The object-name configuration object identifier field has an invalid value of value
the indicated invalid value.
Severity error
Facility LOG_DAEMON
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.
a source that is out of range.

Severity error
Facility LOG_DAEMON
RPD_IGMP_DYN_CFG_ALREADY_BOUND
System Log Message Dynamic configuration session id client-session-idfor interface interface-name is already
bound to interface old-interface-name.
Description The indicated dynamic configuration session id is already bound to another interface.
The dynamic configuration instantiation request was rejected.
Severity error
Facility LOG_DAEMON
Action Unbind session id from existing interface.
RPD_IGMP_DYN_CFG_INVALID_STMT
System Log Message Invalid dynamic configuration statement: configuration-statement
Description The indicated dynamic configuration statement was invalid. The dynamic configuration
instantiation request was rejected.
Severity error
Facility LOG_DAEMON
Action Remove the unsupported configuration statement.
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.
Description Failed to associate the indicated dynamic configuration session id to specified interface.
Severity error
Facility LOG_DAEMON

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.
Description The dynamic configuration instantiation request matched an existing dynamic

configuration block that had a different session id. The dynamic configuration instantiation
request was rejected.
Severity error
Facility LOG_DAEMON
RPD_IGMP_GROUP_LIMIT_EXCEED
System Log Message IGMP group limit exceeded Instance: instance Interface: interface-name.Group Limit:
group-limit Current Group Count: current-groups
Description IGMP groups on this interface exceeds limit configured for this group on this interface in
this instance.
Severity warning
Facility LOG_DAEMON
RPD_IGMP_GROUP_THRESHOLD_EXCEED
System Log Message IGMP group threshold exceeded Instance: instance Interface: interface-nameGroup
Threshold: group-threshold Current Group Count: current-groups
Description IGMP groups on this interface exceeds threshold configured for this group on this interface
in this instance.
Severity warning
Facility LOG_DAEMON
RPD_IGMP_GRP_THRESH_LIMIT_BELOW
System Log Message IGMP group count went below configured threshold/limitInstance:instance Interface:
interface-name.Group Limit: group-limit Group Threshold : group-threshold Current Group
Count: current-groups
Description IGMP groups on this interface are now below the limit configured for this group on this
interface in this instance.

Severity warning
Facility LOG_DAEMON
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
Description IGMP join event.
Severity info
Facility LOG_DAEMON
RPD_IGMP_LEAVE
System Log Message Listener source-address sent a leave to destination-address for group group-address
source sender-address on interface interface-name at time
Description IGMP leave event.
Severity info
Facility LOG_DAEMON
RPD_IGMP_MEMBERSHIP_TIMEOUT
System Log Message Membership timeout for listener source-address for group group-address source
Description IGMP group membership timeout.
Severity info
Facility LOG_DAEMON
RPD_IGMP_ROUTER_VERSION_MISMATCH
System Log Message IGMP version mismatch on interface-name. Local version: local-version Remote version:
remote-version
Description The IGMP version running on the local router does not match the one received in the
query
Severity warning
Facility LOG_DAEMON

RPD_ISIS_ADJDOWN
System Log Message IS-IS lost Lisis-level adjacency to neighbor-system-ids on interface-name, reason: reason
Description 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.
Severity notice
Facility LOG_DAEMON
RPD_ISIS_ADJUP
System Log Message IS-IS new Lisis-level adjacency to neighbor-system-ids on interface-name
Description An IS-IS adjacency was established with the indicated neighboring router. The local router
can now exchange information with it.
Severity info
Facility LOG_DAEMON
RPD_ISIS_ADJUPNOIP
System Log Message IS-IS new Lisis-level adjacency to neighbor-system-ids on interface-name without an
address
Description An IS-IS adjacency was established with the indicated neighboring router, which is not
configured for IS-IS for IP.
Severity notice
Facility LOG_DAEMON
Cause The neighboring router is misconfigured: it is enabled for IS-IS but not for exchange of IP
route information.
Action Configure the neighboring router for IS-IS with IP, or remove it from the IS-IS mesh.
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

Description 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.
Severity warning
Facility LOG_DAEMON
Action Determine why LDP lost synchronization with IS-IS.
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
Description The indicated IS-IS informational link-state PDU (LSP) failed an internal checksum
validity test, implying that it was corrupted.
Severity warning
Facility LOG_DAEMON
Cause The packet was corrupted in transit between the neighboring IS-IS router and this router,
or memory on one of the routers was corrupted.
Action None, unless a large number of these messages appear in the system log file. The
corrupted LSP is silently discarded. For mor einformation, see KB19068.
RPD_ISIS_NO_ROUTERID
System Log Message IS-IS instance does not have a valid router ID
Description The IS-IS instance did not have a valid router ID.
Severity alert
Facility LOG_DAEMON
Cause 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.
Action 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.

RPD_ISIS_OVERLOAD
System Log Message IS-IS database overload
Description The IS-IS link-state database is full and no additional memory can be allocated for it.
Severity alert
Facility LOG_DAEMON
Cause 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.
Action 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. For more
information, see KB19069.
RPD_KRT_CCC_IFL_MODIFY
System Log Message error-code, error-message
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.
Severity info
Facility LOG_DAEMON
Cause It is possible that the kernel lacked the resources to fulfill the request. The rpd process
will recover.
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
Description The routing protocol process (rpd) received a message from the kernel that referred to
a routing table that no longer exists.
Severity error
Facility LOG_DAEMON

RPD_KRT_IFA_GENERATION
System Log Message ifa generation mismatch -- ifl interface-name rpd rpd-generation kernel kernel-generation
interface address associated with the indicated numerical index differed from the
address-to-index mapping maintained by rpd.
Severity notice
Facility LOG_DAEMON
RPD_KRT_IFDCHANGE
System Log Message task-name CHANGE for ifd interface-device-index address/prefix-length failed, error
"error-message"
Description The routing protocol process (rpd) sent a request to the kernel to change the state of
the indicated interface. The request failed.
Severity error
Facility LOG_DAEMON
will recover.
RPD_KRT_IFDEST_GET
System Log Message task-name IFDEST GET for ifd rpd-interface-name failed, error "error-message"
Description The routing protocol process (rpd) requested state information about the indicated
interface from the kernel. The request failed.
Severity error
Facility LOG_DAEMON
will recover.
RPD_KRT_IFDGET
System Log Message task-name GET index for ifd interface-name failed, error "error-message"

Description The routing protocol process (rpd) requested state information about the indicated
interface from the kernel. The request failed.
Severity error
Facility LOG_DAEMON
will recover.
RPD_KRT_IFD_CELL_RELAY_INV_MODE
System Log Message Invalid mode (mode) specified for interface device interface-name; defaulting to port
mode
Description 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.
Severity notice
Facility LOG_DAEMON
RPD_KRT_IFD_CELL_RELAY_NO_MODE
System Log Message No mode specified for interface device interface-name; defaulting to port mode
the cell-relay encapsulation for the indicated physical interface, but not the cell-relay
mode.
Severity notice
Facility LOG_DAEMON
RPD_KRT_IFD_GENERATION
System Log Message ifd interface-device-index generation mismatch -- rpd rpd-generation kernel
kernel-generation
physical interface associated with the indicated numerical index differed from the
interface-to-index mapping maintained by rpd.
Severity notice
Facility LOG_DAEMON

RPD_KRT_IFL_CELL_RELAY_INV_MODE
System Log Message Invalid mode (mode) specified for logical interface interface-name; defaulting to port
mode
the cell-relay encapsulation for the indicated logical interface, but the specified cell-relay
mode (port, virtual-circuit, or virtual-path) was invalid.
Severity notice
Facility LOG_DAEMON
RPD_KRT_IFL_CELL_RELAY_NO_MODE
System Log Message No mode specified for logical interface interface-name; defaulting to port mode
the cell-relay encapsulation for the indicated logical interface but not the cell-relay mode.
Severity notice
Facility LOG_DAEMON
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
logical interface associated with the indicated numerical index differed from the
interface-to-index mapping maintained by rpd.
Severity notice
Facility LOG_DAEMON
RPD_KRT_KERNEL_BAD_ROUTE
System Log Message task-name: lost interface-hierarchy logical-interface-index for route route-prefix
Description 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.

Severity warning
Facility LOG_DAEMON
Cause rpd did not recognize some elements in the route message, such as the logical interface
index or an address family.
Action 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. For more information, see
RPD_KRT_NEXTHOP_OVERFLOW
System Log Message type route-prefix: number of next hops (count) exceeded the maximum allowed
(maximum-value) -- truncating
Description The number of next hops for the indicated route exceeded the indicated limit for a single
route add operation.
Severity error
Facility LOG_DAEMON
Cause 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.
Action Eliminate common next hops across forwarding classes, thereby reducing the total
number of next hops that must be specified.
RPD_KRT_NOIFD
System Log Message No device interface-device-index for interface logical-interface-index (interface-name)
Description 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.
Severity error
Facility LOG_DAEMON

RPD_KRT_VERSION
System Log Message Routing socket version mismatch (kernel kernel-version != rpd rpd-version) -- kernel
upgrade required
Description The routing protocol process (rpd) discovered that the kernel does not support the version
of routing sockets it requires.
Severity error
Facility LOG_DAEMON
Cause The kernel version is older than the rpd version.
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
Description The routing protocol process (rpd) discovered that the kernel does not support the routing
socket message types that it requires.
Severity error
Facility LOG_DAEMON
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
Description The routing protocol process (rpd) discovered that the kernel uses an older version of
routing socket message types than it does.
Severity error
Facility LOG_DAEMON

RPD_KRT_VPLS_IFL_MODIFY
System Log Message Unable to modify VPLS-related state: error-code (errno error-message)
Description 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.
Severity info
Facility LOG_DAEMON
will recover.
RPD_L2VPN_INSTANCE_NOT_FOUND
System Log Message Routing Instance routing-instance
Description The routing protocol process (rpd) received an update for the indicated routing-instance,
but was unable to find the layer2 VPN instance object. This could result in inconsistent
rpd state between PEs or Routing Engines.
Severity error
Facility LOG_DAEMON
Action Please check routing-instance configuration.
RPD_L2VPN_LABEL_ALLOC_FAILED
System Log Message Unable to allocate label-type labels for site name with ID identifier in instance vpn-name
Description 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.
Severity error
Facility LOG_DAEMON
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
Description 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.

Severity warning
Facility LOG_DAEMON
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)
Description 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.
Severity error
Facility LOG_DAEMON
RPD_LAYER2_VC_BFD_DOWN
System Log Message BFD session for Layer 2 VC vc-name went down
Description 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.
Severity notice
Facility LOG_DAEMON
RPD_LAYER2_VC_BFD_UP
System Log Message BFD session for Layer 2 VC vc-name came up
(BFD) protocol session for the the indicated Layer 2 virtual private network (VPN) virtual
circuit (VC) came up.
Severity notice
Facility LOG_DAEMON
RPD_LAYER2_VC_DOWN
System Log Message State of Layer 2 VC vc-name changed from UP to state
Description The state of the indicated Layer 2 virtual private network (VPN) virtual circuit (VC)
changed as indicated (to either down or deleted).

Severity notice
Facility LOG_DAEMON
RPD_LAYER2_VC_PING_DOWN
System Log Message Ping failure for Layer 2 VC vc-name
Description The routing protocol process (rpd) determined that the Ping for the indicated Layer 2
virtual private network (VPN) virtual circuit (VC) failed.
Severity notice
Facility LOG_DAEMON
RPD_LAYER2_VC_UP
System Log Message State of Layer 2 VC vc-name changed to UP
Description The state of the indicated Layer 2 virtual private network (VPN) virtual circuit (VC)
changed to up.
Severity info
Facility LOG_DAEMON
RPD_LDP_BFD_DOWN
System Log Message LDP BFD session for FEC fec-address went down
Description 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.
Severity notice
Facility LOG_DAEMON
RPD_LDP_BFD_DOWN_TRACEROUTE_FAIL
System Log Message LDP BFD sessions for FEC fec-address going down due to traceroute failure
equivalence class (FEC) was terminated due to traceroute failure.
Severity notice
Facility LOG_DAEMON

RPD_LDP_BFD_UP
System Log Message LDP BFD session for FEC fec-address came up
equivalence class (FEC) came up.
Severity notice
Facility LOG_DAEMON
RPD_LDP_GR_CFG_IGNORED
System Log Message LDP needs duration seconds for restart. Instance restart-duration is time-period seconds
only. Graceful restart will not be attempted
Description Instance restart-duration is less than that needed by LDP to finish graceful-restart. LDP
GR will not be attempted.
Severity warning
Facility LOG_DAEMON
Action Modify the instance restart-duration and ldp GR configurations.
RPD_LDP_INTF_BLOCKED
System Log Message Duplicate session ID detected from neighbor-addressi, interface interface-name, blocking
interface
Description 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.
Severity warning
Facility LOG_DAEMON
RPD_LDP_INTF_UNBLOCKED
System Log Message LDP interface interface-name is now unblocked
Description 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.
Severity warning

Facility LOG_DAEMON
RPD_LDP_NBRDOWN
System Log Message LDP neighbor neighbor-addressi (interface-name) is down
Description 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.
Severity notice
Facility LOG_DAEMON
RPD_LDP_NBRUP
System Log Message LDP neighbor neighbor-addressi (interface-name) is up
Description 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.
Severity info
Facility LOG_DAEMON
RPD_LDP_PING_DOWN
System Log Message LDP LSP ping failure for FEC fec-address
Description The routing protocol process (rpd) determined that LSP ping returned error for the
indicated forwarding equivalence class (FEC) of Label Distribution Protocol (LDP).
Severity notice
Facility LOG_DAEMON
RPD_LDP_SESSIONDOWN
System Log Message LDP session neighbor-addressi is down, reason: reason
Description The routing protocol process (rpd) terminated a Label Distribution Protocol (LDP) session
with the indicated neighbor and deleted all labels exchanged during the session.
Severity notice
Facility LOG_DAEMON

RPD_LDP_SESSIONUP
System Log Message LDP session neighbor-addressi is up
Description The routing protocol process (rpd) established a Label Distribution Protocol (LDP) session
with the indicated neighbor. The routers began exchanging labels.
Severity info
Facility LOG_DAEMON
RPD_LMP_ALLOC_ACK
System Log Message Unknown context in ALLOC_ACK message
Description The routing protocol process (rpd) received a label allocation acknowledgment that
contained invalid context.
Severity error
Facility LOG_DAEMON
RPD_LMP_ALLOC_REQUEST_TIMEOUT
System Log Message Allocation request timeout for context address, client request ID 0xrequest-id
Description The label allocation request with the indicated client request ID and for the indicated
context timed out before completion.
Severity error
Facility LOG_DAEMON
RPD_LMP_CONTROL_CHANNEL
System Log Message operation operation failed: control channel logical-interface-index unknown
Description The routing protocol process (rpd) received a message that specified the indicated type
of operation on the indicated control channel. The channel does not exist.
Severity error
Facility LOG_DAEMON
RPD_LMP_NO_CALLBACK
System Log Message No function callback for label removed event
Description 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.

Severity error
Facility LOG_DAEMON
RPD_LMP_NO_MEMORY
System Log Message function-name: malloc() failed (error-message, errno error-code)
Description The routing protocol process (rpd) could not allocate memory.
Severity error
Facility LOG_DAEMON
RPD_LMP_NO_PEER
System Log Message Peer peer-id not found for TE link link-name (index link-id)
Description 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.
Severity error
Facility LOG_DAEMON
RPD_LMP_PEER
System Log Message operation operation failed: peer peer-name (index peer-id) reason
Description The routing protocol process (rpd) could not perform the indicated operation for the
peer with the indicated name and index, for the indicated reason.
Severity error
Facility LOG_DAEMON
RPD_LMP_PEER_IFL
System Log Message operation operation failed because reason for peer peer-name (index peer-id):
error-message (errno error-code)
peer with the indicated name and index, for the indicated reason.
Severity error

Facility LOG_DAEMON
RPD_LMP_PEER_INDEX
System Log Message No more peer indexes
Description No more peer indexes were available for allocation.
Severity error
Facility LOG_DAEMON
RPD_LMP_RESOURCE
System Log Message operation operation failed: resource resource (type type, index index) reason
resource with the indicated name, type, and index, for the indicated reason.
Severity error
Facility LOG_DAEMON
RPD_LMP_RESOURCE_NO_LINK
System Log Message TE link link-id not found for resource resource (type type, index index)
Description The routing protocol process (rpd) could not locate the indicated traffic-engineering link
for the resource with the indicated name, type, and index.
Severity error
Facility LOG_DAEMON
RPD_LMP_SEND
System Log Message function-name: handling write exception (error-message, errno error-code)
Description The routing protocol process (rpd) could not send a message to the Label Management
Protocol (LMP) process (lmpd).
Severity error
Facility LOG_DAEMON
RPD_LMP_SEND_ALLOCATION_MESSAGE
System Log Message Unable to send allocation message: error-message (error-code)
Description The routing protocol process (rpd) could not send an allocation message.

Severity error
Facility LOG_DAEMON
RPD_LMP_SYSFAIL
System Log Message Unable to start type timer
Description 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.
Severity error
Facility LOG_DAEMON
information about possible reasons that lmpd failed.
RPD_LMP_TE_LINK
System Log Message operation operation failed: TE link link-name (index index) reason
traffic-engineering link with the indicated name and index, for the indicated reason.
Severity error
Facility LOG_DAEMON
RPD_LMP_TE_LINK_INDEX
System Log Message No more TE-link indexes
Description No more traffic-engineering link indexes were available for allocation.
Severity error
Facility LOG_DAEMON
RPD_LMP_UNEXPECTED_OPCODE
System Log Message message-type message had unexpected operation code operation-code
Description The routing protocol process (rpd) received the indicated type of message, which had
the indicated invalid operation code.

Severity error
Facility LOG_DAEMON
RPD_MC_CFG_CREATE_ENTRY_FAILED
Description The multicast configuration request failed because the routing protocol process (rpd)
failed to create the specified configuration entry.
Severity error
Facility LOG_DAEMON
RPD_MC_CFG_FWDCACHE_CONFLICT
System Log Message Multicast forwarding-cache: reuse value must be less than or equal to suppress value
Description Multicast forwarding-cache reuse value is configured to be greater than the suppress
value. Reuse value must be less than or equal to the suppress value.
Severity warning
Facility LOG_DAEMON
RPD_MC_CFG_PREFIX_LEN_SHORT
System Log Message Multicast argument: prefix length prefix-length is too short for prefix route-prefix, ignoring
excess host bits
Severity warning
Facility LOG_DAEMON
RPD_MC_COSD_WRITE_ERROR
System Log Message Unable to write to pipe to COS process: (error-message)
Description The routing protocol process (rpd) could not write a message on the write pipe to the
Class Of Service process (cosd).

Severity info
Facility LOG_DAEMON
RPD_MC_DESIGNATED_PE_CHANGE
System Log Message Designated forwarder changed to ip-address for backup-pe-group group-name in
routing-instance instance
Description 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.
Severity notice
Facility LOG_DAEMON
RPD_MC_DYN_CFG_ALREADY_BOUND
Description The dynamic configuration instantiation request was rejected because the specified
dynamic configuration sesssion ID was already bound to another interface.
Severity error
Facility LOG_DAEMON
Action Unbind the session ID from the existing interface.
RPD_MC_DYN_CFG_SES_ID_ADD_FAIL
interface-name.
Description 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.
Severity error
Facility LOG_DAEMON

RPD_MC_DYN_CFG_SES_ID_MISMATCH
Description The dynamic configuration instantiation request was rejected because the request
matched an existing dynamic configuration block that had a different session ID.
Severity error
Facility LOG_DAEMON
RPD_MC_FWD_CACHE_SUPPRESSED
System Log Message Number of entries (routing-instance) in Multicast Forwarding cache exceeded configured
suppress_val (address-family) in instance num-mc-fwd-cache-entries for family
num-mc-fwd-cache-suppress
Description Multicast forwarding cache suppressed as number of entries in the cache exceeded
configured suppress value.
Severity error
Facility LOG_DAEMON
RPD_MC_FWD_CACHE_THRESH_BELOW
System Log Message Number of entries (routing-instance) in Multicast Forwarding cache went below configured
warning threshold (address-family%%) in instance num-mc-fwd-cache-entries for family
num-mc-fwd-cache-threshold
Description Number of entries in the multicast forwarding cache went below configured warning
threshold value.
Severity info
Facility LOG_DAEMON
RPD_MC_FWD_CACHE_THRESH_EXCEED
System Log Message Number of entries (routing-instance) in Multicast Forwarding cache exceeded configured
warning threshold (address-family%%) in instance num-mc-fwd-cache-entries for family
num-mc-fwd-cache-threshold
Description Number of entries in the multicast forwarding cache exceeded configured warning
threshold value.

Severity error
Facility LOG_DAEMON
RPD_MC_FWD_CACHE_UNSUPPRESSED
System Log Message Number of entries (routing-instance) in Multicast Forwarding cache went below configured
reuse_val (address-family) in instance num-mc-fwd-cache-entries for family
num-mc-fwd-cache-reuse
Description Multicast forwarding cache suppressed as number of entries in the cache went below
configured reuse value.
Severity error
Facility LOG_DAEMON
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
Description 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.
Severity notice
Facility LOG_DAEMON
RPD_MC_OIF_REJECT
System Log Message group-address source-address (flow-rate bps) rejected due to lack of bandwidth on
interface-name (maximum maximum-flow-rate bps, admitted admitted-flow-rate
bps)oif-map-interface-name
Description 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.
Severity info
Facility LOG_DAEMON
RPD_MC_OIF_RE_ADMIT
System Log Message group-address source-address (flow-rate bps) admitted due to newly available bandwidth
on interface-name (maximum maximum-flow-rate bps, admitted admitted-flow-rate
bps)oif-map-interface-name

Description The indicated downstream interface that was previously rejected was readmitted for
the flow because there was newly availabe bandwidth on the interface.
Severity info
Facility LOG_DAEMON
RPD_MIRROR_ERROR
Description The routing protocol process (rpd) could not establish the mirror connection (which
supports nonstop routing) between the master and backup Routing Engines.
Severity warning
Facility LOG_DAEMON
OS .
RPD_MIRROR_VERSION_MISMATCH
Description 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 OS on the Routing Engines were incompatible.
Severity warning
Facility LOG_DAEMON
RPD_MLD_ACCOUNTING_OFF
Description The Multicast Listener Discovery (MLD) accounting for the indicated interface was
disabled at the indicated time.
Severity info
Facility LOG_DAEMON

RPD_MLD_ACCOUNTING_ON
Description The Multicast Listener Discovery (MLD) accounting for the indicated interface was
enabled at the indicated time.
Severity info
Facility LOG_DAEMON
RPD_MLD_ALL_SUBSCRIBERS_DELETED
System Log Message All MLD subscribers on interface interface-name deleted at time because the interface
is down
Description All MLD subscribers have been deleted because the interface is down.
Severity info
Facility LOG_DAEMON
RPD_MLD_CFG_CREATE_ENTRY_FAILED
Description MLD failed to create the indicated configuration entry. The configuration request failed.
Severity error
Facility LOG_DAEMON
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.
a group that is out of range.
Severity error
Facility LOG_DAEMON

RPD_MLD_CFG_INVALID_VALUE
Severity error
Facility LOG_DAEMON
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.
a source that is out of range.
Severity error
Facility LOG_DAEMON
RPD_MLD_DYN_CFG_ALREADY_BOUND
Description The indicated dynamic configuration session id is already bound to another interface.
Severity error
Facility LOG_DAEMON
RPD_MLD_DYN_CFG_INVALID_STMT
Description The indicated dynamic configuration statement was invalid. The dynamic configuration
instantiation request was rejected.

Severity error
Facility LOG_DAEMON
RPD_MLD_DYN_CFG_SES_ID_ADD_FAIL
interface-name.
Description Failed to associate the indicated dynamic configuration session id to specified interface.
Severity error
Facility LOG_DAEMON
RPD_MLD_DYN_CFG_SES_ID_MISMATCH
Description The dynamic configuration instantiation request matched an existing dynamic

configuration block that had a different session id. The dynamic configuration instantiation
request was rejected.
Severity error
Facility LOG_DAEMON
RPD_MLD_GROUP_LIMIT_EXCEED
System Log Message MLD group limit exceed Instance:instance Interface: interface-name.Group Limit:
group-limit Current Group Count: current-groups
Description MLD groups on this interface exceeds limit configured for this group on this interface in
this instance.
Severity warning
Facility LOG_DAEMON
RPD_MLD_GROUP_THRESHOLD_EXCEED
System Log Message MLD group threshold exceed Instance: instance Interface: interface-nameGroup Threshold:
group-threshold Current Group Count: current-groups

Description MLD groups on this interface exceeds threshold configured for this group on this interface
in this instance.
Severity warning
Facility LOG_DAEMON
RPD_MLD_GRP_THRESH_LIMIT_BELOW
System Log Message MLD group count went below configured threshold/limitInstance:instance Interface:
interface-name.Group Limit: group-limit Group Threshold : group-threshold Current Group
Count: current-groups
Description MLD groups on this interface are below limit configured for this group on this interface
in this instance.
Severity warning
Facility LOG_DAEMON
RPD_MLD_JOIN
System Log Message Listener source-address sent a join to destination-address for group group-address source
Description MLD join event.
Severity info
Facility LOG_DAEMON
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
Description MLD leave event.
Severity info
Facility LOG_DAEMON
RPD_MLD_MEMBERSHIP_TIMEOUT
System Log Message Membership timeout for listener source-address for group group-address source
Description MLD group membership timeout.

Severity info
Facility LOG_DAEMON
RPD_MLD_ROUTER_VERSION_MISMATCH
System Log Message MLD version mismatch on interface-name. Local version: local-version Remote version:
remote-version
Description The MLD version running on the local router does not match the one received in the query
Severity warning
Facility LOG_DAEMON
RPD_MPLS_DYNAMIC_POOL_EXHAUSTED
System Log Message Label allocation failure : Dynamic label pool exhausted
Description There was a failure while allocating a label.The dynamic label pool space got exhausted.
Severity warning
Facility LOG_DAEMON
RPD_MPLS_INTERFACE_ROUTE_ERROR
System Log Message Unable to add route in table table-name for label mpls-label pointing to interface-name
Description There was a failure in adding a Multiprotocol Label Switching (MPLS) route pointing to
an interface
Severity notice
Facility LOG_DAEMON
RPD_MPLS_INTF_MAX_LABELS_ERROR
System Log Message Maximum labels exceeded - failed to stack additional label to nexthop on interface
interface-name nhid: next-hop fnh: memory-address lspname: lsp-name label: data-buffer
Description There was a failure in stacking additional label to a nexthop which already has maximum
number of labels allowed for the interface
Severity warning
Facility LOG_DAEMON

RPD_MPLS_LABEL_LIMIT_EXCEEDED
System Log Message Label allocation failure : Label limit label-limit exceeded
Description There was a failure while allocating a label.The dynamic label limit got exceeded while
allocating new label.
Severity warning
Facility LOG_DAEMON
RPD_MPLS_LABEL_THRESHOLD_LIMIT_EXCEEDED
System Log Message tag-type label space usage crossed threshold limit of 90 percent
Description The label space usage has exceeded the threshold limit for this particular label space.
Severity warning
Facility LOG_DAEMON
RPD_MPLS_LOSS_DELAY_NOTICE
System Log Message MPLS lsp-name
Description Loss and delay over a lsp has crossed configured threshold values
Severity warning
Facility LOG_DAEMON
RPD_MPLS_LSP_AUTOBW_NOTICE
System Log Message mpls LSP lsp-name Autobw already in progress, ignoring new trigger
Description The auto-bandwidth adjustment for the indicated Multiprotocol Label Switching (MPLS)
label-switched path (LSP) already in progress, ignoring new trigger.
Severity notice
Facility LOG_DAEMON
RPD_MPLS_LSP_BANDWIDTH_CHANGE
System Log Message MPLS LSP lsp-name bandwidth changed, lsp bandwidth bandwidth bps
Description The bandwidth associated with the indicated Multiprotocol Label Switching (MPLS)
label-switched path (LSP) changed.

Severity warning
Facility LOG_DAEMON
RPD_MPLS_LSP_CHANGE
System Log Message MPLS LSP lsp-name change on path-type(pathname) Route lsp-rro lsp bandwidth
bandwidth bps
Description The indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) was
rerouted and its Record Route Object (RRO) changed.
Severity warning
Facility LOG_DAEMON
RPD_MPLS_LSP_DOWN
System Log Message MPLS LSP lsp-name down on path-type(pathname)
Description The indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) went
down and could not be used to send traffic.
Severity warning
Facility LOG_DAEMON
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
Description The indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) switched
from primary path to secondary path or vice versa.
Severity warning
Facility LOG_DAEMON
RPD_MPLS_LSP_UP
System Log Message MPLS LSP lsp-name up on path-type(pathname) Route lsp-rro lsp bandwidth bandwidth
bps
Description The indicated Multiprotocol Label Switching (MPLS) label-switched path (LSP) came
up and could be used to send traffic.
Severity warning

Facility LOG_DAEMON
RPD_MPLS_OAM_LSP_PING_REPLY_ERR
System Log Message Received ping reply with an error: error-code.
Description 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
Severity error
Facility LOG_DAEMON
RPD_MPLS_OAM_PING_REPLY_TIMEOUT
System Log Message LSP ping reply timed out lsp-name
Description LSP ping timed out waiting for a reply. If any failure action is configured, the failure action
will get executed
Severity error
Facility LOG_DAEMON
RPD_MPLS_OAM_READ_ERROR
System Log Message Unable to read from pipe to MPLS OAM process: reason (error-message)
Description The routing protocol process (rpd) could not read a message available on the read pipe
from the MPLS Operation, Administration, and Maintenance process (mplsoamd).
Severity info
Facility LOG_DAEMON
RPD_MPLS_OAM_WRITE_ERROR
System Log Message Unable to write to pipe to MPLS OAM process: (error-message)
Description The routing protocol process (rpd) could not write a message on the write pipe to the
MPLS Operation, Administration, and Maintenance process (mplsoamd).
Severity info
Facility LOG_DAEMON

RPD_MPLS_PATH_BANDWIDTH_CHANGE
System Log Message MPLS path pathname (lsp lsp-name) bandwidth changed, path bandwidth bandwidth
bps
Description The bandwidth associated with the indicated Multiprotocol Label Switching (MPLS)
path changed.
Severity warning
Facility LOG_DAEMON
RPD_MPLS_PATH_BFD_DOWN
System Log Message BFD session for MPLS path pathname went down on LSP lsp-name
(BFD) protocol session for the indicated Multiprotocol Label Switching (MPLS) path
terminated on the indicated label-switched path (LSP).
Severity notice
Facility LOG_DAEMON
RPD_MPLS_PATH_BFD_UP
System Log Message BFD session for MPLS path pathname came up on LSP lsp-name
(BFD) protocol session for the the indicated Multiprotocol Label Switching (MPLS) path
came up on the indicated label-switched path (LSP).
Severity notice
Facility LOG_DAEMON
RPD_MPLS_PATH_BW_NOT_AVAILABLE
System Log Message Unable to satisfy bandwidth configured for MPLS path pathname on LSP lsp-name
Description 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.
Severity warning
Facility LOG_DAEMON

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 MPLS path pathname down on LSP lsp-name
Description The indicated Multiprotocol Label Switching (MPLS) path went down on the indicated
label-switched path (LSP).
Severity warning
Facility LOG_DAEMON
RPD_MPLS_PATH_PING_DOWN
System Log Message LSP ping failure occured for MPLS path pathname on LSP lsp-name
Description The routing protocol process (rpd) determined that the LSP ping returned error for the
indicated Multiprotocol Label Switching (MPLS) path terminated on the indicated
Severity notice
Facility LOG_DAEMON
RPD_MPLS_PATH_UP
System Log Message MPLS path pathname up on LSP lsp-name path bandwidth bandwidth bps
Description The indicated Multiprotocol Label Switching (MPLS) path came up on the indicated
Severity warning
Facility LOG_DAEMON
RPD_MPLS_REQ_BW_NOT_AVAILABLE
System Log Message Requested bandwidth unavailable for MPLS path pathname on LSP lsp-name
Description After a successful CSPF computation, network conditions changed and RSVP failed to
set up the path with the requested bandwidth which resulted in a path error. The LSP
did not come up if the error occurred when the LSP was initially established. Otherwise,
during an optimization or auto-bandwidth adjustment, the LSP continued to stay up on
the old path and used the previous amount of bandwidth.
Severity warning

Facility LOG_DAEMON
RPD_MPLS_TABLE_ROUTE_ERROR
System Log Message Unable to add route in table table-name for label mpls-label pointing to next-table-name
Description There was a failure in adding a Multiprotocol Label Switching (MPLS) route pointing to
another MPLS routing table
Severity notice
Facility LOG_DAEMON
RPD_MSDP_CFG_SA_LIMITS_CONFLICT
System Log Message Threshold value threshold must be less than or equal to maximum value maximum-value.
Setting threshold to maximum
Description The MSDP active-source-limit threshold is either undefined or exceeds the maximum
value. Threshold will be set to maximum.
Severity warning
Facility LOG_DAEMON
Action Consider modifying the MSDP active-source-limit configurations.
RPD_MSDP_CFG_SRC_INVALID
System Log Message argument is an invalid source address
Description The indicated MSDP source is configured with an invalid address
Severity warning
Facility LOG_DAEMON
RPD_MSDP_PEER_DOWN
System Log Message MSDP peer peer-address peer-group peer-group out of Established state
Description 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.
Severity notice

Facility LOG_DAEMON
RPD_MSDP_PEER_UP
System Log Message MSDP peer peer-address peer-group peer-group into Established state
Description The indicated MSDP peer entered the Established state.
Severity info
Facility LOG_DAEMON
RPD_MSDP_SRC_ACTIVE_OVER_LIMIT
System Log Message Number of MSDP source-active messages about originator exceeded configured limit
(msdp-sa-max)
Description 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.
Severity error
Facility LOG_DAEMON
RPD_MSDP_SRC_ACTIVE_OVER_LOGWARN
System Log Message Number of MSDP source-active messages about originator exceeded configured log
warning (msdp-sa-warn-thresh)
peer, or source exceeded the configured log warning. 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.
Severity error
Facility LOG_DAEMON
RPD_MSDP_SRC_ACTIVE_OVER_THRESH
System Log Message Number of MSDP source-active messages about originator exceeded configured
threshold(msdp-sa-count)
peer, or source exceeded the configured threshold. Until the threshold is no longer
exceeded, a random early discard (RED) profile is applied to incoming messages so that

only some of them are accepted. During periods when the event reported by this message
occurs frequently, the routing protocol process (rpd) does not log every occurrence.
Severity error
Facility LOG_DAEMON
RPD_MSDP_SRC_ACTIVE_UNDER_LIMIT
System Log Message Number of MSDP source-active messages about originator no longer over configured log
warning (msdp-sa-max)
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 does not log every occurence.
Severity error
Facility LOG_DAEMON
RPD_MSDP_SRC_ACTIVE_UNDER_LOGWAR
System Log Message Number of MSDP source-active messages about originator no longer exceeded configured
log-warning (msdp-sa-warn-thresh)
peer, or source under the configured log warning. 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.
Severity error
Facility LOG_DAEMON
RPD_MSDP_SRC_ACTIVE_UNDER_THRESH
System Log Message Number of MSDP source-active messages about originator no longer exceeded configured
threshold (msdp-sa-count)
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.

Severity error
Facility LOG_DAEMON
RPD_MVPN_CFG_PREFIX_LEN_SHORT
System Log Message MVPN argument: prefix length prefix-length is too short for prefix route-prefix, ignoring
excess host bits
Description The prefix length for MVPN source or group object is too short and the indicated prefix
has a non-zero host portion. Excess host bits will be ignored.
Severity warning
Facility LOG_DAEMON
RPD_MVPN_HOT_ROOT_STANDBY_STATUS
System Log Message MVPN instance instance: status
Description MVPN Hot Root Standby status changed
Severity info
Facility LOG_DAEMON
RPD_MVPN_SENDER_BASED_RPF_STATUS
System Log Message MVPN instance instance: status
Description MVPN Sender-Based RPF status changed
Severity info
Facility LOG_DAEMON
RPD_OSPF_CFGNBR_P2P
System Log Message Ignored configured neighbors on point-to-point realm realm-name interface
interface-name area area-idi
Description For point-to-point interfaces, OSPF neighbors are learned by using hello messages, so
the implicit configuration of neighbors was ignored for the indicated point-to-point
interface.
Severity warning
Facility LOG_DAEMON
Action Remove the neighbor configuration for the indicated interface.

RPD_OSPF_IF_COST_CHANGE
System Log Message Interface interface-name (interface-address) area area-idi: cost changed cost -> metric
Description OSPF interface cost changed due to change in interface bandwidth.
Severity info
Facility LOG_DAEMON
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
Description 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.
Severity warning
Facility LOG_DAEMON
Action Determine why LDP lost synchronization with OSPF.
RPD_OSPF_LSA_MAXIMUM_EXCEEDED
System Log Message OSPF realm realm-name number of non-local LSAs exceeded maximum limit
Description The number of non self-generated LSAs exceeded maximum limit specified for database
protection in the indicated realm. Consequently, all non self-generated LSA were deleted
and all neighbors were killed. The router will not send any OSPF hellos and will ignore
any incoming OSPF packets till ignore-time has elapsed.
Severity notice
Facility LOG_DAEMON
RPD_OSPF_LSA_WARNING_EXCEEDED
System Log Message OSPF realm realm-name number of non-local LSAs exceeded warning limit
Description The number of non self-generated LSAs exceeded warning limit specified for database
protection in the indicated realm.
Severity notice
Facility LOG_DAEMON

RPD_OSPF_NBRDOWN
System Log Message OSPF neighbor neighbor-address (realm realm-name interface-name area area-idi) state
changed from old-state to new-state due to event-name (event reason: reason)
Description 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.
Severity notice
Facility LOG_DAEMON
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)
Description An OSPF adjacency was established with the indicated neighboring router. The local
router can now exchange information with it.
Severity info
Facility LOG_DAEMON
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)
Description The indicated topology in the indicated OSPF instance became overloaded and will
remain in that state until an administrator intervenes.
Severity warning
Facility LOG_DAEMON
Cause The number of export prefixes exceeded the configured limit.
Action Unconfigure or modify export policies that inject a large number of routes.
RPD_OSPF_TOPO_IF_COST_CHANGE
System Log Message Interface interface-name (interface-address) area area-idi topology topology: cost changed
cost -> metric
Description OSPF topology interface cost changed due to change in interface bandwidth.

Severity info
Facility LOG_DAEMON
RPD_PIM_BSR_DROP_PKT
System Log Message Instance routing-instance: Dropping BSR packets as BSR send queue exceeded limit of
limit packet drop count is count
Description The routing protocol process (rpd) is dropping PIM BSR packets in order to prevent BSR
packet send queue from growing unbounded and deplete memory. This is usually an
indication of an abnormal network activity like malacious pkt being received.
Severity warning
Facility LOG_DAEMON
RPD_PIM_BSR_SEND_Q_THRESHOLD
System Log Message Instance routing-instance: BSR packet send queue length isnow count, BSR packets will
be dropped if queue length exceeds limit
Description The routing protocol process (rpd) has large amount of PIM BSR messages to send out.
Usually an indication of an abnormal network activity like malacious pkt being received.
Severity info
Facility LOG_DAEMON
RPD_PIM_FOUND_NON_BIDIR_NBR
System Log Message Instance routing-instance received a PIM Hello from a non-Bidir capable neighbor
neighbor-address on interface-name
Description The routing protocol process (rpd) declared that the indicated PIM neighbor is not
PIM-Bidir capable. As a result, PIM-Bidir will be disabled on the indicated interface.
Severity error
Facility LOG_DAEMON
RPD_PIM_GRP_RP_MAP_LIMIT_BELOW
System Log Message PIM (group-prefix, RP) current count (routing-instance) went below configured limit
(address-family) in PIM Routing Instance: pim-rpg-count for Address Family: pim-rpg-max
Description Currently active PIM (group-prefix, RP) count went below configured maximum from
above configured maximum earlier.

Severity error
Facility LOG_DAEMON
RPD_PIM_GRP_RP_MAP_LIMIT_EXCEED
System Log Message PIM (group-prefix, RP) (routing-instance) exceeds configured maximum (address-family)
in PIM Routing Instance: pim-rpg-count for Address Family: pim-rpg-max
Description Currently active PIM (group-prefix, RP) count has exceeded configured maximum.
Severity error
Facility LOG_DAEMON
RPD_PIM_GRP_RP_MAP_THRES_EXCEED
System Log Message PIM (group-prefix, RP) (routing-instance) exceeds configured warning threshold
(address-family) in PIM Routing Instance: pim-rpg-count for Address Family:
pim-rpg-threshold
Description Currently active PIM (group-prefix, RP) count has exceeded configured maximum.
Severity error
Facility LOG_DAEMON
RPD_PIM_JP_INFINITE_HOLDTIME
System Log Message Instance routing-instance: Received PIM J/P msg with holdtime 0xffff from source-address
intf interface-name
Description The RPD received a PIM Join/Prune message with holdtime set to 0xffff (infinite).
Severity warning
Facility LOG_DAEMON
RPD_PIM_NBRDOWN
System Log Message Instance routing-instance: PIM neighbor neighbor-address (interface-name) removed due
to: reason
Description The routing protocol process (rpd) declared the indicated PIM neighbor inactive.
Severity notice
Facility LOG_DAEMON

RPD_PIM_NBRUP
System Log Message Instance routing-instance: PIM new neighbor neighbor-address interface interface-name
Description The routing protocol process (rpd) discovered the indicated new PIM neighbor on the
indicated interface.
Severity info
Facility LOG_DAEMON
RPD_PIM_NON_BIDIR_RPF
System Log Message Instance routing-instance indicated that the RPF interface, interface-name, to the RPA
rp-address is not a PIM-BIDIR enabled interface
Description The routing protocol process (rpd) declared that the indicated PIM Bidir RPF interface
is not a PIM-Bidir enabled interface. As a result, PIM-Bidir forwarding will not work properly.
Severity error
Facility LOG_DAEMON
RPD_PIM_REGISTER_LIMIT_BELOW
System Log Message PIM Register current count (routing-instance) went below configured limit (address-family)
in PIM Routing Instance: pim-register-count for Address Family: pim-register-max
Description Currently active PIM registers count went below configured maximum from above
configured maximum earlier. Only those registers that result in creation of (S, G) are
counted.
Severity error
Facility LOG_DAEMON
RPD_PIM_REGISTER_LIMIT_EXCEED
System Log Message PIM Register count (routing-instance) exceeds configured maximum (address-family) in
PIM Routing Instance: pim-register-count for Address Family: pim-register-max
counted.
Severity error
Facility LOG_DAEMON

RPD_PIM_REG_THRESH_EXCEED
System Log Message PIM Register count (routing-instance) exceeds configured warning threshold
(address-family) in PIM Routing Instance: pim-register-count for Address Family:
pim-register-threshold
counted.
Severity error
Facility LOG_DAEMON
RPD_PIM_SG_LIMIT_BELOW
System Log Message PIM (S,G) current count (routing-instance) went below configured limit (address-family)
in PIM Routing Instance: pim-sg-count for Address Family: pim-sg-max
Description Currently active PIM (S, G)/(*, G) count went below configured maximum from above
configured maximum earlier.
Severity error
Facility LOG_DAEMON
RPD_PIM_SG_LIMIT_EXCEED
System Log Message PIM (S,G) current count (routing-instance) exceeds configured maximum (address-family)
in PIM Routing Instance: pim-sg-count for Address Family: pim-sg-max
Description Currently active PIM (S, G)/(*, G) count has exceeded configured maximum.
Severity error
Facility LOG_DAEMON
RPD_PIM_SG_THRESHOLD_EXCEED
System Log Message PIM (S,G) current count (routing-instance) exceeds configured warning threshold
(address-family) in PIM Routing Instance: pim-sg-count for Address Family:
pim-sg-threshold
Description Currently active PIM sg count has exceeded configured threshold.
Severity error
Facility LOG_DAEMON

RPD_PLCY_CFG_COMMUNITY_FAIL
System Log Message Failed to parse community string under policy-options: error-message
Description The routing protocol process (rpd) encountered a non-catastrophic error in bgp
community member string while parsing policy-options.
Severity warning
Facility LOG_DAEMON
RPD_PLCY_CFG_FWDCLASS_OVERRIDDEN
System Log Message argument supersedes forwarding-class under policy-statement policy-name
Description During configuration parsing, a destination-class or source-class statement overrode

the forwarding-class statement.
Severity warning
Facility LOG_DAEMON
RPD_PLCY_CFG_IFALL_NOMATCH
System Log Message The interface 'all' statement under policy-statement policy-name will not match anything
Description Interface 'all' does not have any special meaning under the policy-options hierarchy
unlike under various other hierarchies.
Severity warning
Facility LOG_DAEMON
RPD_PLCY_CFG_PARSE_GEN_FAIL
System Log Message Policy warning: error-message
Description A conflict was detected while parsing the policy-options configuration hierarchy.
Severity warning
Facility LOG_DAEMON
RPD_PLCY_CFG_PREFIX_LEN_SHORT
System Log Message prefix length prefix-length is too short for prefix route-prefix under policy-statement
policy-name, ignoring excess host bits

Severity warning
Facility LOG_DAEMON
RPD_PPM_READ_ERROR
Description The routing protocol process (rpd) could not read a message available on the read pipe
from the periodic packet management process (ppmd).
Severity info
Facility LOG_DAEMON
RPD_PPM_WRITE_ERROR
Description The routing protocol process (rpd) could not write a message on the pipe to the periodic
packet management process (ppmd).
Severity error
Facility LOG_DAEMON
RPD_RA_CFG_CREATE_ENTRY_FAILED
Description The configuration request failed because the IPv6 routing advertisements failed to create
the indicate configuration entry.
Severity error
Facility LOG_DAEMON
RPD_RA_CFG_INVALID_VALUE
Description The configuration request failed because the configuration object contained the indicated
invalid value.

Severity error
Facility LOG_DAEMON
Action Change the value in the configuration statement to a valid one.
RPD_RA_DYN_CFG_ALREADY_BOUND
Description The dynamic configuration instantiation request was rejected because the indicated
session ID was already bound to another interface.
Severity error
Facility LOG_DAEMON
RPD_RA_DYN_CFG_INVALID_STMT
Description The dynamic configuration instantiation request was rejected because the indicated
dynamic configuration statement was invalid.
Severity error
Facility LOG_DAEMON
RPD_RA_DYN_CFG_SES_ID_ADD_FAIL
interface-name.
Description The dynamic configuration instantiation request was rejected because it failed to associate
the indicated session ID with the specified interface.
Severity error
Facility LOG_DAEMON

RPD_RA_DYN_CFG_SES_ID_MISMATCH
Description The dynamic configuration instantiation request was rejected because it matched an
existing dynamic configuration block that had a different session ID.
Severity error
Facility LOG_DAEMON
RPD_RDISC_CKSUM
System Log Message Bad checksum for router solicitation from source-address to destination-address
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.
Severity warning
Facility LOG_DAEMON
Cause The solicitation message was incorrectly generated or damaged in transit.
Action Examine the host that generated the solicitation message.
RPD_RDISC_NOMULTI
System Log Message Ignoring interface interface-address on interface-name -- multicast not available
Description 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.
Severity warning
Facility LOG_DAEMON
Action Do not configure router discovery on the interface.
RPD_RDISC_NORECVIF
System Log Message Unable to locate interface for router solicitation from source-address to
destination-address

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.
Severity warning
Facility LOG_DAEMON
Cause 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.
Action Ignore this message if it indicates the desired configuration, or reconfigure one or both
routers to share a common network.
RPD_RDISC_SOLICITADDR
System Log Message Expected multicast (expected-address) for router solicitation from source-address to
destination-address
Description A router discovery solicitation message received from the indicated address was not sent
to the expected multicast address for all routers.
Severity warning
Facility LOG_DAEMON
Action Examine the configuration of the router that generated the router discovery solicitation
message.
RPD_RDISC_SOLICITICMP
System Log Message Nonzero ICMP code (value) for router solicitation from source-address to
destination-address
the indicated router because the ICMP code in the message header was nonzero.
Severity warning
Facility LOG_DAEMON
Cause The solicitation message was incorrectly generated.

RPD_RDISC_SOLICITLEN
System Log Message Insufficient length (length) for router solicitation from source-address to
destination-address
the indicated router, because the indicated message length is too short.
Severity warning
Facility LOG_DAEMON
Cause The solicitation message was incorrectly generated.
RPD_RIP_AUTH_ACK
System Log Message Ack with invalid authentication from source-address (interface-name)
Description The routing protocol process (rpd) ignored an RIP ack because the ack authentication
failed.
Severity notice
Facility LOG_DAEMON
RPD_RIP_AUTH_REQUEST
System Log Message Request with invalid authentication from source-address (interface-name)
Description The routing protocol process (rpd) ignored an RIP request because the request
authentication failed.
Severity notice
Facility LOG_DAEMON
RPD_RIP_AUTH_UPDATE
System Log Message Update with invalid authentication from source-address (interface-name)
Description The routing protocol process (rpd) ignored a RIP update because authentication of the
update failed.
Severity notice
Facility LOG_DAEMON

RPD_RIP_JOIN_BROADCAST
System Log Message Unable to get broadcast address on interface-name; using the all-ones address
Description 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.
Severity error
Facility LOG_DAEMON
RPD_RIP_JOIN_MULTICAST
System Log Message Unable to join multicast group on interface-name: error-message
Description 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.
Severity error
Facility LOG_DAEMON
RPD_RSVP_BACKUP_DOWN
System Log Message Backup for protecting LSP lsp-name down, using bypass bypass-lsp-namereason
Description 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.
Severity warning
Facility LOG_DAEMON
RPD_RSVP_BYPASS_DOWN
System Log Message RSVP bypass bypass-lsp-name for protecting interface interface-name went downreason
Description 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.
Severity warning
Facility LOG_DAEMON

RPD_RSVP_BYPASS_UP
System Log Message RSVP bypass bypass-lsp-name for protecting interface interface-name came up
Description The indicated RSVP link-protection bypass was established to protect the indicated
interface.
Severity warning
Facility LOG_DAEMON
RPD_RSVP_COS_CFG_WARN
System Log Message RSVP: Error while checking the existence of [edit class-of-service]: error-message
Description RSVP detected an error while parsing configurations under the CoS hierarchy. RSVP CoS
configurations will be ignored.
Severity warning
Facility LOG_DAEMON
RPD_RSVP_INCORRECT_FLOWSPEC
System Log Message Bandwidth in PATH Tspec greater than RESV flowspec for lsp-name
Description A downstream router sent an incorrect Resv message with a bandwidth in flowspec less
than the bandwidth required by TSPEC in the Path message.
Severity info
Facility LOG_DAEMON
RPD_RSVP_LSP_SWITCH
System Log Message RSVP LSP lsp-name switched to backup; using bypass LSP bypass-lsp-name, route
lsp-rro
Description RSVP detected a failure downstream for the indicated label-switched path (LSP) and
switched it to a backup using the indicated bypass LSP.
Severity info
Facility LOG_DAEMON
Cause The downstream interface or router for the LSP went down.

RPD_RSVP_MAXIMUM_SESSIONS
System Log Message RSVP maximum session limit of limit reached
Description The routing protocol process (rpd) could not set up an RSVP session because the
indicated limit on the number of sessions was reached.
Severity warning
Facility LOG_DAEMON
RPD_RSVP_NBRDOWN
System Log Message RSVP neighbor neighbor-address down on interface interface-name nbr-type
neighbor-type, reason
Description The RSVP neighbor to the indicated address was terminated.
Severity warning
Facility LOG_DAEMON
RPD_RSVP_NBRUP
System Log Message RSVP neighbor neighbor-address up on interface interface-name nbr-type neighbor-type
Description An RSVP neighbor was established to the indicated address.
Severity warning
Facility LOG_DAEMON
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
Description A conflict occurred between the system backup router configuration and the indicated
static route.
Severity warning
Facility LOG_DAEMON

Action Add the retain flag to the static route
RPD_RT_CFG_CREATE_ENTRY_FAILED
System Log Message Could not create entry entry
Description RT failed to create the indicated configuration entry. The configuration request failed.
Severity error
Facility LOG_DAEMON
RPD_RT_CFG_INVALID_VALUE
Severity error
Facility LOG_DAEMON
RPD_RT_CFG_TABLE_NON_MATCHING
System Log Message Routing-table table-name under routing-instance instance associated with session-id
session-iddoes not match the instance
Description The dynamic config request with a specific session id and routing-instance cannot be
completed because a routing-table where routes should be added does not match the
instance
Severity error
Facility LOG_DAEMON
RPD_RT_DUPLICATE_RD
System Log Message routing-instance routing-instance has duplicate route-distinguisher route-discriminator
as routing-instance existing-routing-instance
Description The route-distinguisher assigned to this routing instance has already been assigned to
another routing instance (as indicated).

Severity error
Facility LOG_DAEMON
RPD_RT_DYN_CFG_INST_NOT_FOUND
System Log Message Routing-instance instance associated with session-id session-id not found
Description The dynamic-config request for a specific session id and routing instance cannot be
completed because the instance was not found
Severity error
Facility LOG_DAEMON
RPD_RT_DYN_CFG_TABLE_NOT_FOUND
System Log Message Routing-table table-name under routing-instance instance associated with session-id
session-idnot found
Description The dynamic config request with a specific session id and routing-instance cannot be
completed because a routing table where routes should be added was not found
Severity error
Facility LOG_DAEMON
RPD_RT_ERROR
System Log Message rt_event_event-name: fatal state error
Description A route in the routing table was found to be in an unrecoverable error state.
Severity critical
Facility LOG_DAEMON
RPD_RT_IFUP
System Log Message UP route for interface interface-name index logical-interface-index address/prefix-length
Description The interface route for the indicated interface and prefix changed state from down to
up, becoming available for routing.
Severity warning
Facility LOG_DAEMON

RPD_RT_INST_CFG_RESERVED_NAME
System Log Message The routing-instance name instance is reserved and cannot be used
Description The routing-instances configuration was rejected by rpd because of a reserved

routing-instance name was used
Severity error
Facility LOG_DAEMON
RPD_RT_INST_IMPORT_PLCY_WARNING
System Log Message Instance routing-instance: commandrouting-options instance-import]error-message
Description The policy configured for instance-import in the indicated instance needs modification
to become operational.
Severity warning
Facility LOG_DAEMON
RPD_RT_PATH_LIMIT_BELOW
System Log Message Number of paths (count) in table table-name is now less than the configured maximum
(limit)
Description 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.
Severity warning
Facility LOG_DAEMON
RPD_RT_PATH_LIMIT_REACHED
System Log Message Number of paths (count) in table table-name status configured maximum (limit)
Description 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.
Severity error
Facility LOG_DAEMON

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)
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.
Severity warning
Facility LOG_DAEMON
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)
Description 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.
Severity warning
Facility LOG_DAEMON
RPD_RT_PREFIX_LIMIT_REACHED
System Log Message Number of prefixes (prefix-count) in table table-name status configured maximum (limit)
Description 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.
Severity error
Facility LOG_DAEMON
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)
Description 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.

Severity warning
Facility LOG_DAEMON
RPD_RT_SHOWMODE
System Log Message invalid display mode (mode)
Description The indicated display mode was specified in a 'show route' command and is unsupported.
Severity error
Facility LOG_DAEMON
RPD_RT_TAG_ID_ALLOC_FAILED
System Log Message Unable to allocate object-name for routing instance instance
Description 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.
Severity error
Facility LOG_DAEMON
RPD_RV_SESSIONDOWN
System Log Message Route validation session ip-address, old-state -> new-state
Description An route validation session with the indicated RPKI cache was terminated. The local
router no longer receives route validation information from the RPKI cache server.
Severity notice
Facility LOG_DAEMON
Cause The communication path to the RPKI cache server was disrupted, a protocol error
occurred, or the RPKI cache server was powered down.
RPD_START
System Log Message Start executable-name[pid] version version built date
Description The routing protocol process (rpd) started.
Severity info
Facility LOG_DAEMON

RPD_SYSTEM
Description A system call made by the routing protocol process (rpd) failed.
Severity error
Facility LOG_DAEMON
will recover.
RPD_VPLS_CW_NOT_SUPPORTED
System Log Message Control-word not supported for instance instance on this platform with no-tunnel-services
Description no-tunnel-services is configured for a VPLS instance along with control-word on a

platform which does not support control-word.
Severity warning
Facility LOG_DAEMON
Action Default to not using any control-word.
RPD_VPLS_INTF_NOT_IN_SITE
System Log Message Some interfaces of instance instance are not configured under its single site
Description Some interfaces of the indicated vpls instance have not been configured under the sole
site of the instance.
Severity warning
Facility LOG_DAEMON
Action Configure all interfaces of the instace under its single site.


CHAPTER 99
RT System Log Messages
This chapter describes messages with the RT prefix. They are generated on routers running
Junos OS by the Packet Forwarding Engine as it processes packets for security control
in real time.
RT_ALG_ERR_GATE
System Log Message name ALG message.
Description ALG tried to open gate, but encounter error
Severity error
Facility LOG_PFE
RT_ALG_ERR_INIT
System Log Message name ALG initialization failed.
Description Specific ALG initialization process failed
Severity error
Facility LOG_PFE
RT_ALG_ERR_MEM_ALLOC
Description ALG tried to allocate memory, such as session cookie, but failed
Severity error
Facility LOG_PFE
RT_ALG_ERR_NAT

Description ALG called NAT API to translate IP/PORT in payload, but encounter error
Severity error
Facility LOG_PFE
RT_ALG_ERR_RES_ALLOC
Description ALG tried to allocate pre-reserved resources, such as ASL group, failed
Severity error
Facility LOG_PFE
RT_ALG_NTC_FSM_DROP
Description Packet hit incorrect finite state machine, drop it
Severity notice
Facility LOG_PFE
RT_ALG_NTC_PARSE_ERR
Description ALG parse packet payload encounter error
Severity notice
Facility LOG_PFE
RT_ALG_NTC_PKT_MALFORMED
Description Packet payload format incorrect, or payload element value incorrect
Severity notice
Facility LOG_PFE
RT_ALG_WRN_CAPACITY_LMT

Chapter 99: RT System Log Messages
Description Requirement exceeded ALG pre-defined capacity limitation
Severity warning
Facility LOG_PFE
RT_ALG_WRN_CFG_NEED
System Log Message name ALG message
Description Necessary configurations need apply to let traffic pass
Severity warning
Facility LOG_PFE
RT_FLOW_SESSION_CLOSE
System Log Message session closed reason: source-address/source-port->destination-address/destination-port
service-name
packets-from-server(bytes-from-server) elapsed-time application nested-application
username(roles) packet-incoming-interface encrypted
Description A security session was closed.
Severity info
Facility LOG_USER
RT_FLOW_SESSION_CLOSE_LS
System Log Message Lsys logical-system-name: session closed reason:
packets-from-server(bytes-from-server) elapsed-time application nested-application
username(roles) packet-incoming-interface encrypted
Description A security session was closed.
Severity info
Facility LOG_USER

RT_FLOW_SESSION_CREATE
System Log Message session created source-address/source-port->destination-address/destination-port
service-name
destination-zone-name session-id-32 username(roles) packet-incoming-interface
Description A security session was created.
Severity info
Facility LOG_USER
RT_FLOW_SESSION_CREATE_LS
System Log Message Lsys logical-system-name: session created
destination-zone-name session-id-32 username(roles) packet-incoming-interface
Description A security session was created.
Severity info
Facility LOG_USER
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 application nested-application username(roles)
packet-incoming-interface encrypted
Description A security session was not permitted by policy.
Severity info
Facility LOG_USER
RT_FLOW_SESSION_DENY_LS
System Log Message Lsys logical-system-name: session denied
protocol-id(icmp-type) policy-name source-zone-name destination-zone-name application
nested-application username(roles) packet-incoming-interface encrypted
Description A security session was not permitted by policy.

Severity info
Facility LOG_USER
RT_H323_NAT_COOKIE_NOT_FOUND
System Log Message object-name cannot find cookie from session
Description Failed to find the H.323 NAT cookie.
Severity error
Facility LOG_PFE
RT_IPSEC_AUTH_FAIL
System Log Message IPSec error, error-message
Description HMAC verification failed for received IPSec packet \ Possibly due to a mis-match in
authentication keys.
Severity error
Facility LOG_PFE
RT_IPSEC_BAD_SPI
System Log Message IPSec tunnel on int interface-name with tunnel ID 0xtunnel-id received a packet with a
bad SPI. source-address->destination-address/length, type, SPI 0xindex, SEQ
0xsequence-number.
Description Received IPSec packet with bad SPI
Severity error
Facility LOG_PFE
RT_IPSEC_DECRYPT_BAD_PAD
System Log Message Decryption failure: error-message
Description Decryption error due to invalid padding content \ during ESP padding check.
Severity error
Facility LOG_PFE

RT_IPSEC_PV_DECRYPTION
System Log Message Decryption failure: error-message
Description Threshold value set has been reached due to \ several decryption failures that have
occurred.
Severity error
Facility LOG_PFE
RT_IPSEC_PV_ENCRYPTION
System Log Message Encryption failure: error-message
Description Threshold value set has been reached due to \ several encryption failures that have
occurred.
Severity error
Facility LOG_PFE
RT_IPSEC_PV_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.
Description Threshold value set has been reached due to \ several replay attacks that have occurred.
Severity error
Facility LOG_PFE
RT_IPSEC_PV_SYM_KEYGEN
System Log Message Symmetric key generation failure: error-message
Description A symmetric key has failed to generate.
Severity error
Facility LOG_PFE
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.

Description Received IPSec replay packet
Severity error
Facility LOG_PFE
RT_MGCP_CALL_LIMIT_EXCEED
System Log Message Exceed maximum call max active call numbermaximum-value
Description The maximum MGCP active call limit has been exceeded.
Severity error
Facility LOG_PFE
RT_MGCP_DECODE_FAIL
System Log Message Failed to decode MGCP packet
Description Failed to decode MGCP message.
Severity error
Facility LOG_PFE
RT_MGCP_MEM_ALLOC_FAILED
System Log Message Failed to allocate memory for object-name
Description Failed to allocate memory for the MGCP objects.
Severity error
Facility LOG_PFE
RT_MGCP_REM_NAT_VEC_FAIL
System Log Message Failed to remove MGCP object-name from flow module
Description Failed to remove the MGCP ALG vector from the flow module.
Severity error
Facility LOG_PFE
RT_MGCP_RM_CLIENTID_FAIL
System Log Message MGCP ALG Resource Manager client registration failed

Description Failed to obtain the MGCP Resource Manager client identifier.
Severity error
Facility LOG_PFE
RT_MGCP_UNREG_BY_RM
System Log Message MGCP ALG client has been unregistered by Resource Manager
Description The Resource Manager has unregistered the MGCP Resource Manager client.
Severity error
Facility LOG_PFE
RT_SCCP_CALL_LIMIT_EXCEED
System Log Message Failed to create SCCP ALG call, call limit maximum-value exceeded
Description The maximum SCCP call limit has been exceeded.
Severity error
Facility LOG_PFE
RT_SCCP_CALL_RATE_EXCEED
System Log Message The SCCP active call rate limit maximum-value has been exceeded
Description The SCCP active call rate limit has been exceeded.
Severity error
Facility LOG_PFE
RT_SCCP_DECODE_FAIL
System Log Message Failed to decode SCCP packet from source-address->destination-address
Description Failed to decode SCCP packet.
Severity error
Facility LOG_PFE
RT_SCCP_NAT_COOKIE_NOT_FOUND
System Log Message Failed to find SCCP ALG cookie from session

Description Failed to find SCCP NAT cookie.
Severity error
Facility LOG_PFE
RT_SCCP_REM_NAT_VEC_FAIL
System Log Message Failed to remove SCCP ALG vector from flow module
Description Failed to remove the SCCP ALG vector from the flow module.
Severity error
Facility LOG_PFE
RT_SCCP_UNREG_RM_FAIL
System Log Message Failed to unregister SCCP client from Resource Manager when the ALG was unregistered
Description Failed to unregister SCCP client from Resource Manager when the ALG was unregistered.
Severity error
Facility LOG_PFE
RT_SCREEN_ICMP
System Log Message attack-name source: source-address, destination: destination-address, zone name:
source-zone-name, interface name: interface-name, action: action
Description ICMP attack category
Severity error
Facility LOG_PFE
RT_SCREEN_ICMP_LS
System Log Message [lsys: logical-system-name] attack-name source: source-address, destination:
destination-address, zone name: source-zone-name, interface name: interface-name,
action: action
Description ICMP attack category
Severity error
Facility LOG_PFE

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, action: action
Description IP attack category
Severity error
Facility LOG_PFE
RT_SCREEN_IP_LS
System Log Message [lsys: logical-system-name] attack-name source: source-address, destination:
destination-address, protocol-id: protocol-id, zone name: source-zone-name, interface
name: interface-name, action: action
Description IP attack category
Severity error
Facility LOG_PFE
RT_SCREEN_SESSION_LIMIT
System Log Message attack-name message: ip-address, zone name: source-zone-name, interface name:
interface-name, action: action
Description Session limit category
Severity error
Facility LOG_PFE
RT_SCREEN_SESSION_LIMIT_LS
System Log Message [lsys: logical-system-name] attack-name message: ip-address, zone name:
Description Session limit category
Severity error
Facility LOG_PFE

RT_SCREEN_TCP
System Log Message attack-name source: source-address:source-port, destination:
destination-address:destination-port, zone name: source-zone-name, interface name:
Description TCP attack category
Severity error
Facility LOG_PFE

RT_SCREEN_TCP_DST_IP
System Log Message attack-name destination: destination-address, zone name: source-zone-name, interface
name: interface-name, action: action
Description TCP destination IP attack category
Severity error
Facility LOG_PFE
RT_SCREEN_TCP_DST_IP_LS
System Log Message [lsys: logical-system-name] attack-name destination: destination-address, zone name:
Description TCP destination IP attack category
Severity error
Facility LOG_PFE
RT_SCREEN_TCP_LS
System Log Message [lsys: logical-system-name] attack-name source: source-address:source-port, destination:
Description TCP attack category
Severity error
Facility LOG_PFE

RT_SCREEN_TCP_SRC_IP
System Log Message attack-name source: source-address, zone name: source-zone-name, interface name:
Description TCP source IP attack category
Severity error
Facility LOG_PFE
RT_SCREEN_TCP_SRC_IP_LS
System Log Message [lsys: logical-system-name] attack-name source: source-address, zone name:
Description TCP source IP attack category
Severity error
Facility LOG_PFE
RT_SCREEN_UDP
System Log Message attack-name source: source-address:source-port, destination:
Description UDP attack category
Severity error
Facility LOG_PFE

RT_SCREEN_UDP_LS
System Log Message [lsys: logical-system-name] attack-name source: source-address:source-port, destination:
Description UDP attack category
Severity error
Facility LOG_PFE

RT_SCREEN_WHITE_LIST
System Log Message bypass SYN proxy source: source-address, destination: destination-address, zone name:
source-zone-name, interface name: interface-name
Description Screen white list category for bypassing a screen
Severity info
Facility LOG_PFE
RT_SCREEN_WHITE_LIST_LS
System Log Message [lsys: logical-system-name] bypass SYN proxy source: source-address, destination:
destination-address, zone name: source-zone-name, interface name: interface-name
Description Screen white list category for bypassing a screen
Severity info
Facility LOG_PFE
RT_SCTP_LOG_INFO
System Log Message ***SCTP configuration: message
Description SCTP log info.
Severity info
Facility ANY
RT_SCTP_PKT_INFO
System Log Message ***SCTP (type message-type source-address/source-port ->
destination-address/destination-port) message
Description SCTP packet info.
Severity info
Facility ANY


CHAPTER 100
RTLOG System Log Messages
This chapter describes messages with the RTLOG prefix. They are generated on routers
running Junos OS by the system log module of the Packet Forwarding Engine as it
processes packets for security control in real time.
RTLOG_JLOG_TEST
System Log Message JLOG test OK, jlog_handle=current-value
Description Test JSF Log plugin registration.
Severity info
Facility LOG_PFE
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
Description Security LOG UTP fake TCP SYN flood attack.
Severity error
Facility LOG_PFE
RTLOG_UTP_TCP_SYN_FLOOD_LS
System Log Message lsys: logical-system-name source: source-address-source-port, destination:
destination-address-destination-port, zone name: filter-name, interface name:
interface-name
Description The security LOG UTP faked a TCP SYN flood attack with the name Lsys.
Severity error
Facility LOG_PFE


CHAPTER 101
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 Junos OS.
RTLOGD_LOG_BIND_ERROR
System Log Message Failed to bind socket to PFE: error-message
Description The sytem logging utility for real-time security processing of packets (rtlogd) could not
connect to a log generation module on the Packet Forwarding Engine.
Severity error
Facility LOG_DAEMON

RTLOGD_LOG_READ_ERROR
System Log Message Failed to read from PFE: error-message
Description The system logging utility for real-time security processing of packets (rtlogd) forwards
logs from log generation modules on the Packet Forwarding Engine to the JUNOS event
process (eventd) for recording in the system log. The rtlogd process could not read logs
from the Packet Forwarding Engine for the indicated reason.
Severity error
Facility LOG_DAEMON



CHAPTER 102
RTPERF System Log Messages
This chapter describes messages with the RTPERF prefix. They are related to performance
logs for the data plane.
NOTE: These system log messages are not supported on MX Series.
RTPERF_CPU_THRESHOLD_EXCEEDED
System Log Message FPC fpc-slot PIC pic-slot CPU utilization exceeds threshold, current value=current-value
Description PFE cpu threshold exceeded
Severity critical
Facility LOG_PFE
RTPERF_CPU_USAGE_OK
System Log Message FPC fpc-slot PIC pic-slot CPU utilization returns to normal, current value=current-value
Description PFE cpu usage okay
Severity info
Facility LOG_PFE


CHAPTER 103
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 Error with rtsock: error-message
Description The MAC SA Validate system process (jsavald) experienced the indicated error with a
routing socket.
Severity info
Facility LOG_DAEMON


CHAPTER 104
SDK System Log Messages
This chapter describes messages with the SDK prefix.
SDK_VMMD_COMMAND_OPTIONS
System Log Message sdk_vmmd_cmd_opts called with option index arg argument
Description App-engine virtual machine management process cmd line options not handled by
junos_app_init
Severity info
Facility LOG_DAEMON
SDK_VMMD_MOD_LAG
System Log Message cn-name: use-lacp=use-lacp
Description Either received first nodealive or missed a nodealive; modify the LAG settings accordingly
Severity info
Facility LOG_DAEMON


CHAPTER 105
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 Graceful close of BEEP session failed
Description 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.
Severity notice
Facility LOG_DAEMON
Cause The usual cause is that the session was already partially or completely closed.
Action None required. The sdxd process recovers automatically in this situation.
SDXD_BEEP_INIT_FAIL
System Log Message BEEP initialization failed
Description 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.
Severity error
Facility LOG_DAEMON
Cause An internal software failure might have occurred.
SDXD_CHANNEL_START_FAIL
System Log Message Notification channel could not be started (error-code): message

Description The indicated Blocks Extensible Exchange Protocol (BEEP) channel could not be started
Severity error
Facility LOG_DAEMON
Cause The usual cause is an abnormal operation, which might be described in the system log
message.
SDXD_CONNECT_FAIL
System Log Message Connection to SDX server failed: message
Description The Session and Resource Control (SRC) process (sdxd) could not connect to an SRC
server for the indicated reason.
Severity notice
Facility LOG_DAEMON
Cause There was a network problem or the server was not running.
SDXD_DAEMONIZE_FAIL
Description The Service Deployment System process (sdxd) could not create a version of itself to
run in the background as a daemon.
Severity emergency
Facility LOG_DAEMON

SDXD_EVLIB_FAILURE
Description The Service Deployment System process (sdxd) called the indicated function in the
event library. The function failed with the indicated error.
Severity error
Facility LOG_DAEMON

Chapter 105: SDXD System Log Messages
SDXD_KEEPALIVES_MISSED
System Log Message No server keepalives received for three intervals
Description 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.
Severity notice
Facility LOG_DAEMON
SDXD_KEEPALIVE_SEND_FAIL
System Log Message Unable to send keepalive
Description 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.
Severity notice
Facility LOG_DAEMON
Cause There might have been a network problem.
SDXD_MGMT_SOCKET_IO
System Log Message management daemon I/O failure: reason
Description 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).
Severity error
Facility LOG_DAEMON
Cause The mgd process might have exited abnormally.
SDXD_OUT_OF_MEMORY
System Log Message Insufficient memory during operation
Description The Service Deployment System (sdxd) attempted to allocate memory for an internal
object during the indicated operation. The attempt failed.

Severity error
Facility LOG_DAEMON
SDXD_PID_FILE_UPDATE
Description 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
Severity error
Facility LOG_DAEMON
SDXD_SOCKET_FAILURE
System Log Message operation failed: error-message
Description 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.
Severity error
Facility LOG_DAEMON

CHAPTER 106
SM System Log Messages
This chapter describes messages with the SM prefix.
SM_IPPOOL_MM_STATE_CHANGE
System Log Message In [logical-system-name:routing-instance] pool pool-name MM state changed
prev-maintenance-mode (new-maintenance-mode)
Description This notification signifies that the maintenance-mode state changed for the given pool
Severity info
Facility LOG_DAEMON
SM_IPPOOL_POOL_THRESH_EXCEEDED
System Log Message In [logical-system-name:routing-instance] pool pool-name exceeded threshold
current-threshold (configured-threshold)
Description This notification signifies that the pool utilization for the given pool has exceeded the
configured threshold
Severity info
Facility LOG_DAEMON


CHAPTER 107
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 Dropped mail to user:error-message. Send failed or queued reached max
Description 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.
Severity error
Facility LOG_DAEMON
SMTPD_NO_CONFIGURED_SERVER
System Log Message Unable to send mail to error-message. Configure server with relay
Description The smtp client process (smtpd) is unable to send mail payload. A gateway server must
be configured. This server must allow relaying.
Severity error
Facility LOG_DAEMON


CHAPTER 108
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 ? and
SNMPD System Log Messages on page ?.
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 ?.
SNMP_GET_ERROR1
System Log Message function-name operation failed for object-name: index1 index1 (error-message)
Description An SNMP Get or GetNext request failed for the indicated object, which has the indicated
index.
Severity error
Facility LOG_DAEMON
SNMP_GET_ERROR2
System Log Message function-name operation failed for object-name: index1 index1 index2 index2
(error-message)
indexes.

Severity error
Facility LOG_DAEMON
SNMP_GET_ERROR3
System Log Message function-name operation failed for object-name: index1 index1 index2 index2 index3 index3
(error-message)
indexes.
Severity error
Facility LOG_DAEMON
SNMP_GET_ERROR4
System Log Message function-name operation failed for object-name: index1 index1 index2 index2 index3 index3
index4 index4 (error-message)
indexes.
Severity error
Facility LOG_DAEMON
SNMP_RTSLIB_FAILURE
System Log Message function-name: reason: error-message
Description A call to the indicated function in the routing socket library failed with the indicated error.
Severity emergency

Chapter 108: SNMP System Log Messages
Facility LOG_DAEMON
SNMP_TRAP_LINK_DOWN
System Log Message ifIndex snmp-interface-index, ifAdminStatus admin-status, ifOperStatus operational-status,
ifName interface-name
Description The SNMP agent process (snmpd) generated a linkDown trap because the indicated
interface changed state to 'down'.
Severity warning
Facility LOG_DAEMON
SNMP_TRAP_LINK_UP
System Log Message ifIndex snmp-interface-index, ifAdminStatus admin-status, ifOperStatus operational-status,
ifName interface-name
Description The SNMP agent process (snmpd) generated a linkUp trap because the indicated interface
changed state to 'up'.
Severity info
Facility LOG_DAEMON
SNMP_TRAP_TRACERT_PATH_CHANGE
System Log Message traceRouteCtlOwnerIndex = test-owner, traceRouteCtlTestName = test-name
Description 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.
Severity info
Facility LOG_DAEMON
SNMP_TRAP_TRACERT_TEST_COMPLETED
generated a tracerouteTestCompleted trap because the test completed and the full
path to the target was determined.

Severity info
Facility LOG_DAEMON
SNMP_TRAP_TRACERT_TEST_FAILED
generated a tracerouteTestFailed trap because the test completed and the full path to
the target was not determined.
Severity info
Facility LOG_DAEMON

CHAPTER 109
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 function-name: message from source-address to destination-address (index1)
Description The indicated function failed because the authorization check failed for the interface,
Simple Network Management Protocol (SNMP) community, or user making the request.
Severity notice
Facility LOG_DAEMON
SNMPD_AUTH_PRIVILEGES_EXCEEDED
System Log Message function-name: source-address: request exceeded community privileges
Description The indicated function failed because the Simple Network Management Protocol (SNMP)
community making the access request did not have the required privileges.
Severity notice
Facility LOG_DAEMON

SNMPD_AUTH_RESTRICTED_ADDRESS
System Log Message function-name: request from address source-address not allowed
Description The indicated function failed because access requests from the indicated source address
are not allowed.
Severity notice
Facility LOG_DAEMON
SNMPD_AUTH_WRONG_PDU_TYPE
System Log Message function-name: source-address: unauthorized SNMP PDU type: pdu-type
Description The indicated function failed because the indicated type of protocol data unit (PDU) is
not supported.
Severity notice
Facility LOG_DAEMON
SNMPD_BIND_INFO
System Log Message Source address for trap socket was set to bind-address
Description 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.
Severity info
Facility LOG_DAEMON
Cause An administrator changed the JUNOS configuration for the process or for an interface.
Cause The online/offline state changed for a Physical Interface Card (PIC). This can also cause
the address to become newly available or unavailable.

Chapter 109: SNMPD System Log Messages
SNMPD_CONFIG_ERROR
System Log Message Configuration database has errors
Description The Simple Network Management Protocol (SNMP) agent process (snmpd) detected
an error in the SNMP configuration database.
Severity error
Facility LOG_DAEMON
SNMPD_CONTEXT_ERROR
System Log Message function-name: error in operation context context-name
Description The indicated operation (addition or deletion) failed during configuration of the indicated
Simple Network Management Protocol (SNMP) context.
Severity error
Facility LOG_DAEMON
SNMPD_ENGINE_ID_CHANGED
System Log Message Warning: warning-message
Description The Simple Network Management Protocol (SNMP) agent process (snmpd) maintains
an engine id. This engine id has changed .
Severity warning
Facility LOG_DAEMON
SNMPD_FILE_FAILURE
System Log Message function-name: fopen filename: error-message
Description The Simple Network Management Protocol (SNMP) agent process (snmpd) could not
access the indicated file.
Severity emergency
Facility LOG_DAEMON

SNMPD_GROUP_ERROR
System Log Message function-name: error in operation group: 'group-id' user 'username' model 'model'
Description The indicated operation (creation, installation, or deletion) failed during configuration
of the indicated group.
Severity error
Facility LOG_DAEMON
SNMPD_HEALTH_MON_THRESH_CROSS
System Log Message syslog-subtagdelimiterevent-name
Description A system parameter monitored by the self-monitoring feature crossed a rising or falling
threshold.
Severity error
Facility LOG_DAEMON
Cause System resources were being consumed.
SNMPD_INIT_FAILED
System Log Message snmpd initialization failure: error-message
Description Initialization of the Simple Network Management Protocol (SNMP) agent process
(snmpd) failed.
Severity error
Facility LOG_DAEMON

SNMPD_LIBJUNIPER_FAILURE
System Log Message function-name: system_default_inaddr: error-message
Description The indicated function from the Juniper Networks Simple Network Management Protocol
(SNMP) library failed and returned the indicated error to the SNMP agent process
(snmpd).
Severity error
Facility LOG_DAEMON
SNMPD_MISSING_REGISTRATION
System Log Message Detected missing OID registration for context "context-name"
Description The Simple Network Management Protocol (SNMP) agent process (snmpd) has detected
OID registration pertaining to the shared MIBs is missing at snmpd side.
Severity error
Facility LOG_DAEMON
SNMPD_RADIX_FAILURE
System Log Message function-name: radix_add failed: error-message
Description 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.
Severity error
Facility LOG_DAEMON
SNMPD_RECEIVE_FAILURE
System Log Message function-name: receive message failure: error-message

Description 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.
Severity error
Facility LOG_DAEMON
SNMPD_RMONFILE_FAILURE
System Log Message function-name: operation: operation filename: error-message
Description The indicated operation failed on the indicated remote monitoring (RMON) data file.
Severity critical
Facility LOG_DAEMON
SNMPD_RMON_COOKIE
System Log Message function-name: Null cookie
Description An invalid data pointer was returned when the remote monitoring (RMON) asynchronous
completion handler performed an RMON alarm operation.
Severity error
Facility LOG_DAEMON
SNMPD_RMON_EVENTLOG
System Log Message syslog-subtagdelimitermessage
Description The indicated remote monitoring (RMON) event completed.

Severity warning
Facility LOG_DAEMON
SNMPD_RMON_MIBERROR
System Log Message function-name: internal Get request error: description, alarm alarm-id, error error-message,
variable: name (oid)
Description A Get request for a monitored object instance failed during initialization of the indicated
remote monitoring (RMON) alarm.
Severity error
Facility LOG_DAEMON
SNMPD_RTSLIB_ASYNC_EVENT
System Log Message function-name: sequence mismatch (expected-value, received-value), resyncing
Description A notification from the kernel to the Simple Network Management Protocol (SNMP)
agent process (snmpd) was lost.
Severity notice
Facility LOG_DAEMON
SNMPD_SCRIPT_OID_ERROR
System Log Message function-name: OID oid is not juniper enterprise mib(filename)
Description The OID provided by the Simple Network Management Protocol (SNMP) pass-through
mechanism is not under Juniper private enterprise Management Information Base (MIB).
Severity error
Facility LOG_DAEMON
SNMPD_SCRIPT_REGISTERED
System Log Message SNMP script filename registered with oid oid and with priority priority
Description SNMP script has registered with OID and priority.

Severity info
Facility LOG_DAEMON
SNMPD_SEND_FAILURE
System Log Message function-name: send type (index1) failure: error-message
send either a protocol data unit (PDU) to the User Datagram Protocol (UDP) or a message
to a subagent.
Severity error
Facility LOG_DAEMON
SNMPD_SET_FAILED
System Log Message Snmp set failed: error-message
Description 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.
Severity error
Facility LOG_DAEMON
SNMPD_SMOID_GEN_FAILURE
System Log Message Unable to generate OID from product-name (error-message)
generate a value for the self-monitoring object identifier (OID) of the indicated product.
Severity error
Facility LOG_DAEMON

SNMPD_SOCKET_FAILURE
System Log Message function-name: socket failure: reason (error-message)
Description The Simple Network Management Protocol (SNMP) agent process (snmpd) uses sockets
for communication with subagents. A socket operation, such as creation or removal,
failed.
Severity emergency
Facility LOG_DAEMON
SNMPD_SOCKET_FATAL_FAILURE
System Log Message function-name: socket failure: reason (error-message)
Description 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.
Severity emergency
Facility LOG_DAEMON
SNMPD_SYSLIB_FAILURE
System Log Message function-name: system function 'system-function-name' failed: error-message
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).
Severity error
Facility LOG_DAEMON

SNMPD_SYSOID_FAILURE
System Log Message Unable to determine sysObjectID from internal model: model
determine the value of the sysObjectID object.
Severity error
Facility LOG_DAEMON
SNMPD_SYSOID_GEN_FAILURE
System Log Message Unable to generate OID for product product-name (error-message)
generate a value for the sysObjectID object for the indicated product.
Severity error
Facility LOG_DAEMON
SNMPD_THROTTLE_QUEUE_DRAINED
System Log Message function-name: cleared all throttled traps
Description The queue of throttled traps was cleared.
Severity info
Facility LOG_DAEMON
SNMPD_TRAP_COLD_START
System Log Message function-name: SNMP trap: cold start
Description The Simple Network Management Protocol (SNMP) agent process (snmpd) generated
a cold-start trap when the entire Routing Engine (including the snmpd process) initialized.

Severity critical
Facility LOG_DAEMON
SNMPD_TRAP_GEN_FAILURE
System Log Message function-name: SNMP trap error: trap-message (error-message)
generate a trap.
Severity error
Facility LOG_DAEMON
SNMPD_TRAP_INVALID_DATA
System Log Message function-name: SNMP trap error: invalid message (value) received
Description The Simple Network Management Protocol (SNMP) agent process (snmpd) received a
trap message from a subagent that contained an invalid variable binding (varbind) type.
Severity error
Facility LOG_DAEMON
SNMPD_TRAP_QUEUED
System Log Message Adding trap to trap-destination to queue-name queue, size traps in queue
Description A trap was queued for later transmission.
Severity info
Facility LOG_DAEMON
Cause Possible causes include the following: (a) the system is not completely initialized, (b) a
route does not exist, or (c) traps are being throttled.

SNMPD_TRAP_QUEUE_DRAINED
System Log Message function-name: traps queued to trap-destination sent successfully
Description The queued traps for the indicated destination were successfully sent.
Severity info
Facility LOG_DAEMON
SNMPD_TRAP_QUEUE_MAX_ATTEMPTS
System Log Message function-name: after count attempts, deleting trap-count traps queued to trap-destination
Description The number of attempts to send traps to the indicated destination exceeded the
configured maximum. The traps still waiting to be sent were discarded.
Severity error
Facility LOG_DAEMON
SNMPD_TRAP_QUEUE_MAX_SIZE
System Log Message function-name: maximum queue size exceeded (size), discarding trap to trap-destination
from queue-name queue
Description The number of traps in the trap queue exceeded the configured maximum. The traps
still waiting to be sent were discarded.
Severity info
Facility LOG_DAEMON
SNMPD_TRAP_TARGET_ADD_NOTICE
System Log Message trap target is added, address : target-info
Description The given trap target is added
Severity notice
Facility LOG_DAEMON
SNMPD_TRAP_TARGET_DELETE_NOTICE
System Log Message trap target is removed, henceforth agent will not send any trap to this target : target-info

Description The given trap target is deleted
Severity notice
Facility LOG_DAEMON
SNMPD_TRAP_THROTTLED
System Log Message function-name: traps throttled after count traps
Description The number of traps waiting for transmission exceeded the configured maximum, so the
remaining traps were throttled.
Severity info
Facility LOG_DAEMON
SNMPD_TRAP_WARM_START
System Log Message function-name: SNMP trap: warm start
Description The Simple Network Management Protocol (SNMP) agent process (snmpd) generated
a warm-start trap when it initialized (other Routing Engine processes were already active).
Severity error
Facility LOG_DAEMON
SNMPD_USER_ERROR
System Log Message function-name: error in action user 'username' auth 'authentication-type' priv 'privilege-type'
Description The indicated operation (creation, installation, or deletion) failed during configuration
of the indicated user.
Severity error
Facility LOG_DAEMON


CHAPTER 110
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 PICs.
SPD_CONFIGURATION_COMPILE
System Log Message Compilation of configuration rule rule-name term index failed: reason
Description The adaptive services process (spd) could not compile a configured object, such as a
rule or rule term.
Severity error
Facility LOG_DAEMON
SPD_CONN_FAILURE
System Log Message Connection did not succeed (Pic is down or busy) error: error-message
Description 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.
Severity error
Facility LOG_DAEMON
SPD_CONN_NO_REPLY
System Log Message function-name: no reply from interface-name (error-message)
Description 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.

Severity error
Facility LOG_DAEMON
SPD_CONN_OPEN_FAILURE
System Log Message function-name: unable to open connection to interface-name (error-message)
Description The adaptive services process (spd) attempted to open a connection to the indicated
interface on an Adaptive Services PIC, to gather information requested in a Simple
Network Management Protocol (SNMP) query. The attempt failed for the indicated
reason.
Severity error
Facility LOG_DAEMON
SPD_CONN_SEND_FAILURE
System Log Message function-name: unable to send query to interface-name (error-message)
Description 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.
Severity error
Facility LOG_DAEMON
SPD_CONN_UNEXPECTED_MSG
System Log Message function-name: unexpected response received from interface-name (error-message)
Description 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.
Severity error
Facility LOG_DAEMON
SPD_DAEMONIZE_FAILED
Description The adaptive services process (spd) could not create a version of itself to run in the
background as a daemon.

Chapter 110: SPD System Log Messages
Severity emergency
Facility LOG_DAEMON

SPD_DB_IF_ADD_FAILURE
System Log Message Unable to add database entry for interface-name: error-message
Description 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).
Severity error
Facility LOG_DAEMON
SPD_DB_IF_ALLOC_FAILURE
System Log Message Unable to allocate database entry for interface-name: error-message
allocate an entry in the database for the indicated interface on an Adaptive Services
Physical Interface Card (PIC).
Severity error
Facility LOG_DAEMON
SPD_DB_SVC_SET_ADD_FAILURE
System Log Message Unable to add database entry for service-set: error-message
add an entry to the database for the indicated service set.
Severity error
Facility LOG_DAEMON
SPD_DB_SVC_SET_ALLOC_FAILURE
System Log Message Unable to allocate database entry for service-set: error-message

allocate an entry in the database for the indicated service set.
Severity error
Facility LOG_DAEMON
SPD_DUPLICATE
Description An attempt to start the adaptive services process (spd) failed because an instance of
the process is already running.
Severity error
Facility LOG_DAEMON
SPD_EVLIB_CREATE_FAILURE
System Log Message evCreate failed with: error-message
Description The adaptive services process (spd) could not create a context used for handling all
asynchronous events (such as timers and message availability).
Severity emergency
Facility LOG_DAEMON

SPD_EVLIB_EXIT_FAILURE
System Log Message evMainLoop return value: return-value, error: error-message
Description The adaptive services process (spd) returned from an event loop, which it should never
do.
Severity error
Facility LOG_DAEMON
SPD_GEN_NUM_FAIL
System Log Message Initialization of generation number failed, error-message

Description The adaptive services process (spd) attempted to initialize the generation-number for
the service sets. However, the memory allocation failed.
Severity error
Facility LOG_DAEMON

SPD_NOT_ROOT
Description The user who attempted to start the adaptive services process (spd) was not the root
user.
Severity error
Facility LOG_DAEMON
SPD_OUT_OF_MEMORY
System Log Message Insufficient memory for operation operation
Description The adaptive services process (spd) attempted to allocate memory for an internal object.
The attempt failed.
Severity error
Facility LOG_DAEMON
SPD_PID_FILE_LOCK
System Log Message Unable to lock PID file: error-message
Description 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.
Severity error
Facility LOG_DAEMON
SPD_PID_FILE_UPDATE

Description 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.
Severity error
Facility LOG_DAEMON
SPD_SERVICE_NEXT_HOP_ADD_FAILED
System Log Message Unable to add service next hop: error-message (error-code)
Description The adaptive services process (spd) could not add a service next hop for the indicated
reason.
Severity error
Facility LOG_DAEMON
SPD_SERVICE_NEXT_HOP_DEL_FAILED
System Log Message Unable to delete service next hop: error-message (error-code)
Description The adaptive services process (spd) could not delete a service next hop for the indicated
reason.
Severity error
Facility LOG_DAEMON
SPD_TRAP_OID_GEN_FAILED
System Log Message Unable to generate OID for identifier (error-message)
Description The adaptive services process (spd) could not generate the indicated object identifier
(OID) for a Simple Network Management Protocol (SNMP) trap notification.
Severity error
Facility LOG_DAEMON
SPD_TRAP_REQUEST_FAILURE
System Log Message function-name: type request failed: error-message
Description 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.

Severity error
Facility LOG_DAEMON
SPD_USAGE
System Log Message Usage: spd [-N] [-v] [-d debug-level]
Description The adaptive services process (spd) displayed the syntax statement for the 'spd'
command because the command was invoked incorrectly.
Severity error
Facility LOG_DAEMON


CHAPTER 111
SSH System Log Messages
This chapter describes messages with the SSH prefix. They are generated by the ssh-relay
process (ssh).
SSH_MSG_REPLAY_DETECT
System Log Message Potential replay attack detected on SSH connection initiated from
source-address:source-port
Description Potential ssh replay attack detected on the indicated connection.
Severity notice
Facility ANY
SSH_MSG_REPLAY_LIMIT
System Log Message Specified number of replay attacks (limit) detected on SSH connection initiated from
source-address:source-port
Description Several potential ssh replay attacks detected on the indicated connection
Severity notice
Facility ANY
SSH_RELAY_CONNECT_ERROR
System Log Message Unable to connect to service-name server: error-message
Description The 'ssh-relay' program could not connect to the server process for the indicated service.
Severity error
Facility ANY
Cause The server process is not running or has not enabled the service.

SSH_RELAY_SERVER_ERROR
System Log Message SSH relay error for service-name service: error-message
Description The indicated error occurred when a Junos process tried to establish secure shell (SSH)
relay during initialization of the indicated service.
Severity error
Facility ANY
SSH_RELAY_USAGE
System Log Message Usage: ssh-relay -s service-name
Description The syntax statement for the 'ssh-relay' command was displayed because the command
was invoked with one or more incorrect options, or without necessary options.
Severity error
Facility ANY

CHAPTER 112
SSHD System Log Messages
This chapter describes messages with the SSHD prefix. They are generated by the secure
shell process (sshd) which grants you access to specified shell accounts.
SSHD_LOGIN_ATTEMPTS_THRESHOLD
System Log Message Threshold for unsuccessful authentication attempts (limit) reached by user 'username'
Description The user made too many failed login attempts.
Severity notice
Facility ANY
SSHD_LOGIN_FAILED
System Log Message Login failed for user 'username' from host 'source-address'
Description A login attempt failed for the indicated username.
Severity notice
Facility ANY
SSHD_LOGIN_FAILED_LIMIT
System Log Message Specified number of login failures (limit) for user 'username' reached from 'remote-address'
Description Several login attempts failed for the indicated username.
Severity notice
Facility ANY


CHAPTER 113
SSL System Log Messages
This chapter describes messages with the SSL prefix. They are generated by the Secure
Sockets Layer (protocol) (SSL) services. These logs contain information about logical
system names, SSL proxy whitelists, policy information, and SSL proxy information.
SSL is an application-level protocol that provides encryption technology for the Internet.
SSL, also called Transport Layer Security (TLS), ensures the secure transmission of data
between a client and a server through a combination of privacy, authentication,
confidentiality, and data integrity. SSL relies upon certificates and private-public key
exchange pairs for this level of security.
SSL_PROXY_ERROR
System Log Message lsys:logical-system-name session-id
<source-address/source-port->destination-address/destination-port>
NAT:<nat-source-address/nat-source-port->nat-destination-address/nat-destination-port>
profile-name
<source-zone-name:source-interface-name->destination-zone-name:destination-interface-name>
message: message
Description ssl proxy error log
Severity error
Facility LOG_PFE
SSL_PROXY_INFO
profile-name
message: message
Description ssl proxy info log
Severity info

Facility LOG_PFE
SSL_PROXY_SESSION_IGNORE
profile-name
message: message
Description This log is generated when a non-ssl session is allowed to pass through ssl-proxy. This
will happen when initially a session is marked for proxy processing and at some later
point it turns out to be a non-ssl session.
Severity info
Facility LOG_PFE
SSL_PROXY_SESSION_WHITELIST
System Log Message lsys:logical-system-name session-id host:url
profile-name
message: message
Description This log is generated when an session is whitelisted.
Severity info
Facility LOG_PFE
SSL_PROXY_SSL_SESSION_ALLOW
profile-name
message: message
Description This log is generated when an ssl session is allowed to pass through ssl-proxy after some
error is detected
Severity info
Facility LOG_PFE

Chapter 113: SSL System Log Messages
SSL_PROXY_SSL_SESSION_DROP
profile-name
message: message
Description This log is generated when an ssl proxy session is dropped by ssl-proxy
Severity info
Facility LOG_PFE
SSL_PROXY_WARNING
profile-name
message: message
Description ssl proxy warning log
Severity info
Facility LOG_PFE


CHAPTER 114
SYSTEM System Log Messages
This chapter describes messages with the SYSTEM prefix. Messages without an event
ID are grouped under this set of system log messages. For example, messages generated
by the kernel, Packet Forwarding Engine, PIC, line-card chassis (LCC), switch-card chassis
(SCC), etc. are grouped under the SYSTEM messages.
SYSTEM_ABNORMAL_SHUTDOWN
System Log Message System abnormally shut down
Description The system shut down abnormally. This can be caused by any number of factors such
as pulling the power plug, a kernel panic, a thermal shutdown, and so forth.
Severity notice
Facility LOG_DAEMON
SYSTEM_OPERATIONAL
System Log Message System is operational
Description The system has entered operational status, and security logging has been started.
Severity notice
Facility LOG_DAEMON
SYSTEM_SHUTDOWN
System Log Message System type by username at time: message
Description An administrator requested that the system be shut down or rebooted.
Severity notice
Facility LOG_DAEMON


CHAPTER 115
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 Unexpected address family address-family-type
Description 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.
Severity error
Facility ANY
TFTPD_BIND_ERR
System Log Message bind: error-message
Description Binding of a socket to an address failed due to a system error.
Severity error
Facility ANY
TFTPD_CONNECT_ERR
System Log Message connect: error-message
Description Connection of a socket to an address failed due to a system error.
Severity error
Facility ANY

TFTPD_CONNECT_INFO
System Log Message TFTP operation from address address port port file filename
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.
Severity info
Facility ANY
TFTPD_CREATE_ERR
System Log Message check_space error-message
Description The TFTP process (tnp.tftpd) could not create a core dump file.
Severity error
Facility ANY
Cause 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 ioctl(FIONBIO): error-message
Description The TFTP process (tnp.tftpd) could not set the standard input to be nonblocking.
Severity error
Facility ANY
TFTPD_FORK_ERR
System Log Message fork: error-message
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.
Severity error
Facility ANY

Chapter 115: TFTPD System Log Messages
TFTPD_NAK_ERR
System Log Message nak error error-code, error-message
Description The TFTP process (tnp.tftpd) sent a negative acknowledgment to a client because of
the indicated error condition.
Severity warning
Facility ANY
TFTPD_OPEN_ERR
System Log Message Unable to open file 'filename', error: error-message
Description The TFTP process (tnp.tftpd) could not open the indicated file because of the indicated
error.
Severity warning
Facility ANY
TFTPD_RECVCOMPLETE_INFO
System Log Message Received count blocks of block-size size for file 'filename'
Description 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.
Severity info
Facility ANY
TFTPD_RECVFROM_ERR
System Log Message recvfrom: error-message
Description The TFTP process (tnp.tftpd) issued the recvfrom() system call when attempting to
receive data from the network. The system call failed.
Severity error
Facility ANY
TFTPD_RECV_ERR
System Log Message recv: error-message
Description The TFTP process (tnp.tftpd) could not receive data from the network.

Severity error
Facility ANY
TFTPD_SENDCOMPLETE_INFO
System Log Message Sent count blocks of block-size and 1 block of size for file 'filename'
Description 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.
Severity info
Facility ANY
TFTPD_SEND_ERR
System Log Message send: error-message
Description The TFTP process (tnp.tftpd) could not send data.
Severity error
Facility ANY
TFTPD_SOCKET_ERR
System Log Message socket: error-message
Description The TFTP process (tnp.tftpd) could not open a socket for data transmission or reception.
Severity error
Facility ANY
TFTPD_STATFS_ERR
System Log Message statfs filename, error: error-message
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.
Severity error
Facility ANY

CHAPTER 116
TRANSPORTD System Log Messages
This chapter describes messages with the TRANSPORTD prefix.
TRANSPORTD_IPC_MSG_ERROR
Description The transport process (transportd) detected an error in an interprocess communication

(IPC) message with the indicated characteristics.
Severity error
Facility LOG_DAEMON
TRANSPORTD_IPC_MSG_UNHANDLED
System Log Message function-name: unable to handle message with type message-type, subtype
message-subtype, length length, opcode message-opcode, error error-code
Description The transport process (transportd) received an interprocess communication (IPC)

message about the indicated FRU. The message had the indicated characteristics. The
transportd process could not handle the message.
Severity error
Facility LOG_DAEMON
TRANSPORTD_IPC_UNEXPECTED_MSG
message-subtype)
Description The transport process (transportd) received a unexpected message with the indicated
characteristics.
Severity error

Facility LOG_DAEMON
TRANSPORTD_IPC_WRITE_ERROR
System Log Message function-name: errno error-code, error-message
Description transport process's (transportd) attempt to write to a pipe (to another component)
failed.
Severity warning
Facility LOG_DAEMON
TRANSPORTD_IPC_WRITE_ERR_NO_PIPE
System Log Message function-name pipe is NULL
Description The transport process (transportd) could not send a message to the indicated component
because the interprocess communication (IPC) pipe to that component no longer existed.
Severity warning
Facility LOG_DAEMON
TRANSPORTD_MGR_CONNECT
Description The transport process (transportd) could not open a pipe for interprocess communication
(IPC) to another component.
Severity error
Facility LOG_DAEMON
TRANSPORTD_PIPE_WRITE_ERROR
System Log Message Pipe write error: error-message
Description The transport process (transportd) experienced a fatal error while writing to a pipe.
Severity error
Facility LOG_DAEMON
TRANSPORTD_SYSCALL_ERROR
System Log Message function-name: error from sysctl-function-name: error-message (errno error-code)
Description The transport process (transportd) received the indicated error from the indicated
syscall() operation.

Chapter 116: TRANSPORTD System Log Messages
Severity error
Facility LOG_DAEMON


CHAPTER 117
UFDD System Log Messages
This chapter describes messages with the UFDD prefix. They are generated by the Junos
OS 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.
UFDD_GROUP_ACTION_COMPLETE
System Log Message UFD action complete for group error-message
Description Downlink ports configured under group was disabled through UFD action.
Severity alert
Facility LOG_DAEMON
UFDD_LINK_CHANGE
System Log Message UFD Grp group-name: Downlink interface-name is state
Description Status of downlink in link-to-disable changed.
Severity alert
Facility LOG_DAEMON
Cause Status change of Uplinks in link-to-monitor list.


CHAPTER 118
UI System Log Messages
This chapter describes messages with the UI prefix. They are generated by the Junos OS
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_BAD_LOCATION
System Log Message User 'username' not allowed to log in from host client-name (client-address)
Description The indicated user was denied login based on the location from which the user was
logging in.
Severity notice
Facility LOG_AUTH
UI_AUTH_EVENT
System Log Message Authenticated user 'username' at permission level 'authentication-level'
Description The management process (mgd) authenticated the indicated user.
Severity info
Facility ANY
UI_AUTH_INVALID_CHALLENGE
System Log Message Received invalid authentication challenge for user 'username': response
Description 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.
Severity error

Facility LOG_USER
UI_BOOTTIME_FAILED
System Log Message Unable to fetch boot time: error-message
Description The management process (mgd) could not retrieve the system boot time from the kernel.
Severity error
Facility ANY
UI_CFG_AUDIT_NEW
System Log Message User 'username' action: pathname new-name
Description The indicated user created a new configuration object by copying or renaming an existing
object as indicated.
Severity info
Facility ANY
UI_CFG_AUDIT_OTHER
System Log Message User 'username' action: pathname delimitervalue
Description The indicated user deleted, activated, or deactivated a configuration object, as indicated.
The Junos configuration log facility logged the change.
Severity info
Facility ANY
UI_CFG_AUDIT_SET
System Log Message User 'username' action: pathname delimiterdata -> "value"
Description The indicated user set a value for a configuration object, as indicated.

Chapter 118: UI System Log Messages
Severity info
Facility ANY
UI_CFG_AUDIT_SET_SECRET
System Log Message User 'username' action: pathname
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.
Severity info
Facility ANY
UI_CHILD_ARGS_EXCEEDED
System Log Message Too many arguments for child process 'command'
Description The management process (mgd) invokes some commands on behalf of users. It supplied
more arguments than the command's syntax statement specifies.
Severity error
Facility ANY
UI_CHILD_CHANGE_USER
System Log Message Unable to switch to local user: username
Description The management process (mgd) invokes some commands on behalf of users. Its attempt
to adopt the UID of the indicated user failed.
Severity error
Facility ANY
UI_CHILD_EXEC
System Log Message Child exec failed for command 'command': error-message

Description 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.
Severity error
Facility ANY
UI_CHILD_EXITED
System Log Message Child exited: PID pid, status return-valuecore-dump-status, command 'command'
Description 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.
Severity notice
Facility ANY
UI_CHILD_FOPEN
System Log Message Unable to append to log 'filename': error-message
Description The management process (mgd) attempted to save the output from a command in the
indicated log file, but could not open the file.
Severity error
Facility ANY
UI_CHILD_OUTPUT
System Log Message Child output: message
Description The management process (mgd) spawned a child process that output some messages
which were requested to be hidden but need to be logged for informational purposes.

Severity info
Facility ANY
UI_CHILD_PIPE_FAILED
System Log Message Unable to create pipe for command 'command': error-message
command for it. Its attempt to create pipes for communication with the child process
failed.
Severity error
Facility ANY
UI_CHILD_STOPPED
System Log Message Child stopped: PID pid, signal=signal-namecore-dump-status, command='command')
command for it. The child process received the indicated signal and stopped.
Severity notice
Facility ANY
UI_CHILD_WAITPID
System Log Message waitpid failed: PID pid, rc return-value, status status-code: error-message
Description The management process (mgd) created a child process to execute a command for it.
It could not wait for the child process to finish.
Severity error
Facility ANY

UI_CLASS_MODIFIED_USERS
System Log Message Class 'class-name' modified, affects users: username
Description The indicated class was modified, affecting the indicated users, who are assigned to that
class
Severity info
Facility ANY
UI_CLI_IDLE_TIMEOUT
System Log Message Idle timeout for user 'username' exceeded and session terminated
Description The indicated user's session was ended after a period of prolonged inactivity.
Severity info
Facility LOG_USER
UI_CMDLINE_READ_LINE
System Log Message User 'username', command 'command'
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).
Severity info
Facility LOG_AUTH
UI_CMD_AUTH_REGEX_INVALID
System Log Message Invalid 'allow-deny' command authorization regular expression 'regular-expression':
error-message
Description An operation that attempted to set command or configuration authorization included

the indicated regular expression. The operation failed because the expression syntax
was invalid.
Severity error
Facility ANY
Action Correct any errors in the regular expression.

UI_COMMIT
System Log Message User 'username' requested 'command' operation (comment: message)
Description 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.
Severity notice
Facility ANY
UI_COMMIT_AT_ABORT
System Log Message reason, will try again
Description An attempt to complete a pending commit operation was cancelled for the indicated
reason.
Severity error
Facility ANY
UI_COMMIT_AT_COMPLETED
System Log Message 'commit at' was successful
Description Changes to the candidate configuration were activated at the time scheduled by a 'commit
at' operation.
Severity notice
Facility ANY
UI_COMMIT_AT_FAILED
System Log Message reason, scheduled commit cleared
Description A 'commit at' operation did not complete, for the indicated reason.
Severity error
Facility ANY
UI_COMMIT_COMPLETED
System Log Message commit complete
Description Changes to the candidate configuration were committed successfully.

Severity warning
Facility ANY
UI_COMMIT_COMPRESS_FAILED
System Log Message Unable to compress file 'filename'
Description 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.
Severity error
Facility ANY
Cause The Routing Engine is low on resources.
UI_COMMIT_CONFIRMED_REMINDER
System Log Message 'commit confirmed' must be confirmed within duration minutes
Description 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.
Severity notice
Facility ANY
UI_COMMIT_EMPTY_CONTAINER
System Log Message Skipped empty object 'node-name'
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.
Severity info
Facility ANY

Cause When the commit operation began, the user who created the new container object had
not populated it and was in configuration mode but not at the top level of the hierarchy.
Action 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.
UI_COMMIT_NOT_CONFIRMED
System Log Message Commit was not confirmed; message
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 automatic
rollback restores management access to the routing platform in case an error in the
configuration blocks access.
Severity notice
Facility LOG_AUTH
UI_COMMIT_PREV_CNF_SAVED
System Log Message Previously committed configuration saved to filename
Description In case automatic rollback of unconfirmed commit fails, previously committed

configuration is saved up for further inspection.
Severity notice
Facility LOG_AUTH
Cause The cause of the problem might be recorded in messages that precede this message in
the system log.
UI_COMMIT_PROGRESS
System Log Message Commit operation in progress: message
Description As it performed a commit operation, the management process (mgd) recorded its
execution of the indicated step.
Severity info
Facility ANY

UI_COMMIT_ROLLBACK_FAILED
System Log Message Automatic rollback failed
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.
Severity error
Facility LOG_AUTH
Cause The cause of the problem might be recorded in messages that precede this message in
the system log.
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
Description 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.
Severity notice
Facility ANY
UI_COND_GROUPS
System Log Message message 'group-name' is reason
Description Conditional groups may get internally effective or revoked as per specified condition
Severity info
Facility ANY
UI_COND_GROUPS_COMMIT
System Log Message Cond-Groups: message
Description Info about an attempt to complete a pending commit operation as by indicated reason.

Severity info
Facility ANY
UI_COND_GROUPS_COMMIT_ABORT
System Log Message Cond-Groups: reason
Description An attempt to complete a pending commit operation was cancelled for the indicated
reason.
Severity error
Facility ANY
UI_CONFIGURATION_ERROR
System Log Message Process: process-name, path: pathname, statement: configuration-statement,
error-message
Description The indicated process found a problem in its configuration.
Severity error
Facility ANY
UI_CONFIGURATION_WARNING
System Log Message Process: process-name, path: pathname, statement: configuration-statement,
warning-message
Description The indicated process found a problem in its configuration.
Severity warning
Facility ANY
UI_CONNECT_COMMITD_FAILED
System Log Message process-name error-message
Description Commitd is not up to provide access to ephemeral db
Severity error
Facility ANY
UI_DAEMON_ACCEPT_FAILED
System Log Message connection-type socket connection accept failed: error-message

Description The management process (mgd) did not accept an incoming connection request.
Severity error
Facility LOG_AUTH
UI_DAEMON_FORK_FAILED
System Log Message Unable to create session child: error-message
Description The management process (mgd) invokes the fork() system call to create a copy of itself
for each CLI session. The system call failed.
Severity error
Facility LOG_AUTH
UI_DAEMON_SELECT_FAILED
System Log Message select failed: error-message
Description The management process (mgd) uses the select() system call to listen for incoming
connection requests on a socket. The system call failed.
Severity error
Facility LOG_AUTH
UI_DAEMON_SOCKET_FAILED
System Log Message connection-type socket create failed: error-message
Description The management process (mgd) uses sockets to communicate with other JUNOS
software processes running on the routing platform. It could not allocate a socket.

Severity error
Facility LOG_AUTH
Cause System resources are exhausted.
UI_DBASE_ACCESS_FAILED
System Log Message Unable to reaccess configuration database file 'filename', address address, size size:
reason
Description 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.
Severity error
Facility ANY
UI_DBASE_CHECKOUT_FAILED
System Log Message Database 'filename' is out of data and needs to be rebuilt
Description When the routing platform boots, the management process (mgd) checks the
configuration database for internal consistency. It found one or more inconsistencies.
Severity alert
Facility ANY
Cause mgd restarted after new Junos OS was installed.
Action None; mgd will rebuild the database.
UI_DBASE_EXTEND_FAILED
System Log Message Unable to extend configuration database file 'filename' to size requested-size: reason
Description The management process (mgd) could not increase the configuration database to the
indicated size.
Severity error

Facility ANY
Cause The hard disk is defective or is not installed in the routing platform.
Action Repair or replace the hard disk.
Cause There is insufficient disk space on the /var partition on the hard disk.
Action Delete user files from the /var/homes directory to increase the available disk space.
UI_DBASE_LOGIN_EVENT
System Log Message User 'username' entering configuration mode
Description The indicated user entered configuration mode (logged into the configuration database).
Severity notice
Facility ANY
UI_DBASE_LOGOUT_EVENT
System Log Message User 'username' exiting configuration mode
Description The indicated user exited configuration mode (logged out of the configuration database).
Severity notice
Facility ANY
UI_DBASE_MISMATCH_EXTENT
System Log Message Database header extent mismatch for file 'filename': expecting expected-value, got
received-value
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.
Severity error
Facility ANY
Cause The database file is corrupted.

UI_DBASE_MISMATCH_MAJOR
System Log Message Database header major version number mismatch for file 'filename': expecting
expected-value, got received-value
Description For compatibility, the version number recorded in the header of the configuration database
must match the version of Junos OS 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.
Severity error
Facility ANY
Cause A recent software upgrade did not complete successfully.
Action 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.
UI_DBASE_MISMATCH_MINOR
System Log Message Database header minor version number mismatch for file 'filename': expecting
expected-value, got received-value
Description For compatibility, the version number recorded in the header of the configuration database
must match the version of Junos OS 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.
Severity error
Facility ANY
Action Issue the 'show version' command to check the Junos version. If necessary, issue the

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.
Description 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 OS
installed on the routing platform does not match the header value.
Severity warning
Facility ANY
Action Issue the 'show version' command to check the Junos version. If necessary, issue the
UI_DBASE_MISMATCH_SIZE
System Log Message Database header size mismatch for file 'filename': expecting expected-valuex, got
received-value
Description 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.
Severity error
Facility ANY
UI_DBASE_OPEN_FAILED
System Log Message Database open failed for file 'filename': reason
Description The management process (mgd) could not open the indicated configuration database
file.

Severity error
Facility ANY
Cause The database file does not exist.
Action Select a different filename or create a new configuration.
Cause The /config directory does not have sufficient space for a new database.
Action Remove files from the /config directory to make more space available.
UI_DBASE_REBUILD_FAILED
System Log Message modeusername rebuild of the database 'filename' failed
Description The management process (mgd) could not rebuild the configuration database file.
Severity alert
Facility ANY
UI_DBASE_REBUILD_SCHEMA_FAILED
System Log Message Automatic rebuild of the database failed
Description The management process (mgd) could not rebuild the schema for the configuration
database.
Severity alert
Facility ANY
UI_DBASE_REBUILD_STARTED
System Log Message modeusername rebuild/rollback of the database 'filename' started

Description 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.
Severity alert
Facility ANY
UI_DBASE_RECREATE
System Log Message User 'username' attempting database re-creation
Description The management process (mgd) discovered that the version of Junos OS 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.
Severity notice
Facility ANY
UI_DBASE_REOPEN_FAILED
System Log Message Reopen of the database failed
Description 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.
Severity alert
Facility ANY
UI_DELTA_CONSTRAINT_CHECK_FAILED
System Log Message Delta constraint check process failed
Description Delta constraint check process failed to build constraint dependency graph database.
Subsequent commits will not be able to use delta constraint check feature. Next reboot
will recreate constraint dependency graph database.
Severity error
Facility ANY

UI_DELTA_CONSTRAINT_CHECK_FORK_FAILED
System Log Message Management process can not fork delta constraint check process
Description Management process can not fork delta constraint check process. Management process
would fall back to existing mechanism of constraint checks.
Severity info
Facility ANY
UI_DELTA_CONSTRAINT_CHECK_NOT_RUNNING
System Log Message delta constraint check process can not run because persist groups is not configured
Description Delta constraint check process can not run because persist groups feature is not
configured. To configure persist groups feature 'system commit
persist-groups-inheritance' knob is required.
Severity info
Facility ANY
UI_DELTA_CONSTRAINT_CHECK_VERSION_MISMATCH
System Log Message constraint dependency graph database version mismatch
Description Constraint dependency graph database version mismatch. Delta constraint check process
can not make use of this database.
Severity info
Facility ANY
UI_DELTA_EXPORTER_FAILURE
System Log Message delta exporter process failed to export juniper.conf
Description Delta exporter process failed to export juniper.conf due to some error. Subsequent
commits will not use delta-export feature. Please try to reinitialize the delta exporter
process using request system commit delta-exporter initialize to use this feature in
subsequent commits also.
Severity error
Facility ANY

UI_DELTA_EXPORTER_INIT_FAIL
System Log Message Delta exporter db initialization failed
Description Delta exporter process failed to initialize it's internal data base. The delta-export feature
will not be used for subsequent commits
Severity error
Facility LOG_AUTH
UI_DUPLICATE_UID
System Log Message Users username1 and username2 have the same UID uid
Description The Junos OS 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.
Severity notice
Facility ANY
Action Assign different UIDs to the affected users.
UI_EPHEMERAL_COMMIT
System Log Message User 'username' has requested commit on 'instance' ephemeral database
Description The indicated user requested the commit operation on the indicated ephemeral instance
Severity warning
Facility ANY
UI_EPHEMERAL_COMMIT_COMPLETED
System Log Message commit complete on 'instance' ephemeral database
Description Changes to the indicated ephemeral instance were committed successfully
Severity warning
Facility ANY
UI_EPHEMERAL_DB_EVENT
System Log Message User 'username' is changing configuration into ephemeral db: 'operation'
Description The indicated user is changing ephemeral db configuration

Severity info
Facility ANY
UI_FACTORY_OPERATION
System Log Message Committing factory default configuration because CONFIG button was pressed and held
Description The management process (mgd) began a commit operation to activate the factory
default configuration, because the CONFIG button on the chassis was pressed and held
for 15 seconds or more.
Severity notice
Facility LOG_AUTH
UI_INITIALSETUP_OPERATION
System Log Message Committing EZsetup configuration as EZsetup option is chosen
Description 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.
Severity notice
Facility LOG_AUTH
UI_INVALID_REMOTE_PERMISSION
System Log Message invalid permissions from authorization server: permission-name
Description RADIUS and TACACS+ authorization servers use Juniper Networks vendor-specific
attributes (VSAs) to specify user permissions. A VSA included the indicated permission
name, which is invalid.
Severity error
Facility ANY
UI_JUNOSCRIPT_CMD
System Log Message User 'username' used JUNOScript client to run command 'command'
Description The indicated user ran the indicated command using the JUNOS XML management
protocol.
Severity info

Facility LOG_AUTH
UI_JUNOSCRIPT_ERROR
System Log Message JUNOScript error: error-message
Description The management process (mgd) normally sends an error message to the Junos OS 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.
Severity warning
Facility ANY
UI_LCC_NO_MASTER
System Log Message No master Routing Engine defined for LCClcc
Description 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.
Severity error
Facility ANY
Action Resolve the mastership situation on the T640 routing node and install the software on
its Routing Engines.
UI_LOAD_EVENT
System Log Message User 'username' is performing a 'operation'
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.
Severity notice
Facility ANY
UI_LOAD_JUNOS_DEFAULT_FILE_EVENT
System Log Message Loading the default config from pathname
Description The system is loading junos default configuration from file.

Severity info
Facility ANY
UI_LOCK_AUTHENTICATION_FAILED
System Log Message username failed authentication when unprotecting pathname
Description Given hierarchy is locked using apply-lock statement and the user can only unprotect
the hierarchy by meeting the required criteria set in apply-lock statement. User doesn't
belong to users/classes list configured in apply-lock statement or he has failed to provide
correct protect password.
Severity info
Facility ANY
UI_LOCK_AUTHENTICATION_SUCCESS
System Log Message username authenticated to unprotect pathname
Description Given hierarchy is locked using apply-lock statement and the user can only unprotect
the hierarchy by meeting the required criteria set in apply-lock statement. User
autheticated himself successfully.
Severity info
Facility ANY
UI_LOGIN_EVENT
System Log Message User 'username' login, class 'class-name' local-peer[pid], ssh-connection 'ssh-connection',
client-mode 'client-mode'
Description The indicated user started a Junos OS CLI session.
Severity info
Facility ANY
UI_LOGOUT_EVENT
System Log Message User 'username' logout
Description The indicated user exited from a Junos OS CLI session.
Severity info
Facility ANY

UI_LOST_CONN
System Log Message Lost connection to daemon 'process-name'
Description The management process (mgd) uses sockets to communicate with other Junos OS
processes. The socket it was using for the indicated process closed prematurely.
Severity error
Facility ANY
UI_MASTERSHIP_EVENT
System Log Message mastership-event card-name mastership by 'username'
Description 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.
Severity warning
Facility ANY
UI_MOTD_PROPAGATE_ERROR
System Log Message Unable to propagate login announcement (motd) to pathname
Description 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.
Severity error
Facility ANY
UI_NETCONF_CMD
System Log Message User 'username' used NETCONF client to run command 'command'
Description The indicated user ran the indicated command using the NETCONF application
programming interface (API).

Severity info
Facility LOG_AUTH
UI_NETCONF_ERROR
System Log Message NETCONF error: error-message
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.
Severity warning
Facility ANY
UI_PARSE_JUNOSCRIPT_ATTRIBUTES
System Log Message Error parsing attributes in client junoscript tag
Description 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.
Severity error
Facility LOG_AUTH
UI_READ_FAILED
System Log Message read failed for peer peer-name: error-message
Description 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.
Severity error
Facility ANY
UI_READ_TIMEOUT
System Log Message Timeout on read of peer 'peer-name'
Description 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.

Severity notice
Facility ANY
UI_REBOOT_EVENT
System Log Message System halt-reboot by 'username'
Description The indicated software process restarted as requested by the indicated user.
Severity warning
Facility ANY
UI_RESCUE_OPERATION
System Log Message Committing rescue configuration because CONFIG button was pressed
Description The management process (mgd) began a commit operation to activate the rescue
configuration, because the CONFIG button on the chassis was pressed.
Severity notice
Facility LOG_AUTH
UI_RESTART_EVENT
System Log Message User 'username' restarting daemon 'process-name'description
Description The indicated software process restarted as requested by the indicated user.
Severity warning
Facility LOG_AUTH
UI_RESTART_FAILED_EVENT
System Log Message Failed to restart 'process-name'
Description Failed to restart the indicated software process as requested by the user.
Severity warning
Facility LOG_AUTH
UI_SCHEMA_CHECKOUT_FAILED
System Log Message Schema is out of date and needs to be rebuilt

Description The Junos user interface schema file records all CLI commands and configuration
statements available in the Junos OS. While initializing, the new management process
(mgd) determined that the schema's sequence number means that the schema is
incompatible with the Junos OS installed on the routing platform.
Severity alert
Facility ANY
Cause The schema is out of date.
Action None; mgd will rebuild the schema based on the current Junos version.
UI_SCHEMA_MISMATCH_MAJOR
System Log Message Schema major version mismatch for package package-name (expected-value vs.
received-value)
statements available in the Junos OS. 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 OS installed on the routing
platform. The mismatch could lead to corruption of the configuration database.
Severity error
Facility ANY
Cause The schema is incompatible with the installed Junos OS.
Action None; mgd will rebuild the schema based on the current Junos version.
UI_SCHEMA_MISMATCH_SEQUENCE
System Log Message Schema header sequence numbers mismatch for package package-name
statements available in the Junos OS. 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.

Severity error
Facility ANY
Cause The Junos OS installation did not succeed, possibly because of an internal software error.
UI_SCHEMA_SEQUENCE_ERROR
System Log Message Schema sequence number mismatch
statements available in the Junos OS. The management process (mgd) rebuilds the
schema as necessary to be compatible with the Junos OS 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.
Severity alert
Facility ANY
UI_SCRIPTS_COPY_FAILED
System Log Message Unable to copy scripts to re: peer-name
Description This message is an error.
Severity error
Facility ANY
UI_SOCK_WARNING
System Log Message process-name warning-message
Description Default socket buffer size retained, could not resize
Severity error
Facility ANY

UI_VERSION_FAILED
System Log Message Unable to fetch system version: error-message
Description The management process (mgd) could not retrieve version information from the kernel.
Severity error
Facility ANY
UI_WRITE_RECONNECT
System Log Message Re-establishing connection to peer 'peer-name'
Description The management process (mgd) reconnected to the indicated Junos process running
on the routing platform.
Severity notice
Facility ANY
UI_XPATH_CONSTRAINT_CHECK_FAILED
System Log Message XPath Constraint check failed
Description Xpath constraint check failed. Cannot proceed with the commit process
Severity error
Facility ANY
UI_XPATH_CONSTRAINT_DA_INIT_FAILED
System Log Message Direct-Access module for Xpath Constaint checkfailed to initialize
Description Direct-access module failed to initialize, XPath constraint check cannot proceed. Disable
the direct access to proceed with commit.
Severity error
Facility ANY
UI_XPATH_CONSTRAINT_DOC_FAILED
System Log Message Failed to create XML Document Object

Description Failed to create the XML DOM required for XPath constraint check. Cannot proceed with
XPath constraint checks. Commit wil fail.
Severity error
Facility ANY

CHAPTER 119
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_MAILNOTIFIER_FAILURE
System Log Message Error:error-message
Description The connection could have failed during memory allocation or socket creation
Severity warning
Facility LOG_DAEMON
UTMD_MALLOC_FAILURE
System Log Message Out of memory. Unable to malloc error-message bytes
Description The example process (utmd) could not allocate memory for a resource possibly due to
lack of memory
Severity error
Facility LOG_DAEMON

UTMD_SSAMLIB_FAILURE
System Log Message ssamlib call returned error : error-message
Description The example process (utmd) encoutered an error while calling a function or from a
callback of the ssamlib library.
Severity error
Facility LOG_DAEMON



CHAPTER 120
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_FABRIC_LSDB_LOOKUP_FAILED
System Log Message device-id:error-message: Unable to find function-name for dev line-number.
Description This LSP is not present in the vccpdf link-state database.
Severity error
Facility LOG_DAEMON
Cause 1. The vccpdf link-state database is full and no additional memory can be allocated for
it. 2. LSP already deleted from the database.
VCCPD_FABRIC_MALLOC_FAILURE
System Log Message function-name:line-number - error-message.
Description The vccpdf process could not allocate memory. The vccpdf 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.
Severity error
Facility LOG_DAEMON
Cause No additional memory is available. Either system resources are exhausted or a software
error occurred (such as a memory leak).
by vccpdf, (2) Add more memory to the switch. (3) Contact your technical support
representative. For more information, see

VCCPD_FABRIC_PROCESS_OIR_MSG
System Log Message argument1: argument2.
Description OIR is user driven feature. After user initiates OIR using CLI configuration, OIR processing
through tlv updates for fabric node info based on the oir_slot received through gencfg
messages from chassism.
Severity error
Facility LOG_DAEMON
Cause OIR intiation through.
VCCPD_FABRIC_SYSCTL_ERROR
System Log Message function-name: Read error for error-message: sysctl-error (errno error-code).
Description The vccpdf process received the indicated error from the indicated sysctl() operation.
Severity error
Facility LOG_DAEMON
VCCPD_FABRIC_SYSTEM
System Log Message function-name: error-message (errno error-code).
Description A system call made by vccpdf process failed.
Severity error
Facility LOG_DAEMON
VCCPD_FABRIC_UNSUPPORTED_RE_TYPE
System Log Message argument1:argument2: argument3.
Description Vccpdf process detected unsupported RE-type during initialization. The installed software
version doesnt not support the indicated RE-type.

Chapter 120: VCCPD System Log Messages
Severity error
Facility LOG_DAEMON
VCCPD_FABRIC_UNSUPPORTED_SKU_TYPE
System Log Message argument1: Neighbor sku type argument2 argument3.
Description Vccpdf process detected neighbor with unsupported SKU-type while forming adjacency
for the given device.
Severity error
Facility LOG_DAEMON
Cause Due to miswiring of FTE interfaces.
VCCPD_KNL_VERSION
System Log Message Routing socket version mismatch (kernel kernel-version != vccpd version) -- kernel upgrade
required
Description The virtual chassis control protocol process (VCCPD) discovered that the kernel does
not support the version of routing sockets it requires.
Severity error
Facility LOG_DAEMON
Cause The kernel version is older than the VCCPD version.
VCCPD_KNL_VERSIONNONE
System Log Message Routing socket message type message-type's version is not supported by kernel, expected
version -- kernel upgrade required
Description The virtual chassis control protocol process (VCCPD) discovered that the kernel does
not support the routing socket message types that it requires.
Severity error
Facility LOG_DAEMON

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
Description The virtual chassis control protocol process (VCCPD) discovered that the kernel uses
an older version of routing socket message types than it does.
Severity error
Facility LOG_DAEMON
VCCPD_PROTOCOL_ADJDOWN
System Log Message Lost adjacency to neighbor-system-ids on interface-name,
Description A virtual chassis adjacency with the indicated neighboring switch was terminated. The
local switch no longer exchanges information with the neighboring switch.
Severity notice
Facility LOG_DAEMON
Cause The communication path to the neighboring switch was disrupted, a protocol error
occurred, or the neighboring switch was powered down.
VCCPD_PROTOCOL_ADJUP
System Log Message New adjacency to neighbor-system-ids on interface-name
Description A virtual chassis adjacency was established with the indicated neighboring switch. The
local switch can now exchange information with it.
Severity info
Facility LOG_DAEMON
VCCPD_PROTOCOL_LSPCKSUM
System Log Message LSP checksum error, interface interface-name, LSP id lspl, sequence sequence-number,
checksum checksum, lifetime duration

Chapter 120: VCCPD System Log Messages
Description The indicated vccpd link-state PDU (LSP) failed an internal checksum validity test,
implying that it was corrupted.
Severity warning
Facility LOG_DAEMON
Cause The packet was corrupted in transit between the neighboring switch and this switch, or
memory on one of the switches was corrupted.
Action 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. For
more information, see http://kb.juniper.net/InfoCenter/index?page=content&id=KB19129.
VCCPD_PROTOCOL_OVERLOAD
System Log Message vccpd database overload
Description The vccpd link-state database is full and no additional memory can be allocated for it.
Severity alert
Facility LOG_DAEMON
Cause 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).
by vccpd, (2) Add more memory to the switch. For more information, see
VCCPD_SYSTEM
Description A system call made by this process failed.
Severity error
Facility LOG_DAEMON


CHAPTER 121
VM System Log Messages
This chapter describes messages with the VM prefix.
VM_DCF_PB_COMMUNICATION_FAILED
System Log Message Network problems encountered during PB API call. uid.
Description The communication failure happens when pb is unreachable. The pb no-longer able to
communicate with the junos on dcf or vdcf
Severity error
Facility LOG_DAEMON
Cause Either the pb node is dead or the communication between the pb and junos vms is down
Action Perform following actions to re-establish the communication: (1) check the link both
up/down between pb and junos vms. (2) check whether either of the pb nodes is up and
running Once the communication is restored the requests in the queue will be processed
normally.
VM_DCF_PB_INVALID_IMAGE
System Log Message Invalid image tag-name for the vm request device-name
Description Image requested for the vm creation to the pb is invalid. The corresponding image is not
found at pb node
Severity error
Facility LOG_DAEMON
Cause The junos image copy is not present at pb node
Action None

VM_DCF_PB_INVALID_UUID
System Log Message Delete request to PB failed: invalid uuid uid
Description The delete request for the vm delete did not get executed as uuid is not found in the PB
uuid DB.
Severity error
Facility LOG_DAEMON
Cause The vm spawned by PB in the past may have went down and this is not communicated
to the parent of the node.
Action None
VM_DCF_PB_RESOURCE_FAILURE
System Log Message No resource to spawn new vm of the label device-name
Description The request for the virtual machine (VM) create did not get executed because of the
resource failure at the pb node.
Severity error
Facility LOG_DAEMON
Cause The pb node is running out of resources to spawn new vms. The server may be hosting
vms nearing the capacity
Action Check whether the servers on which the vms are hosted is up and running. If possible
provide additional resources to meet the demand

CHAPTER 122
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
Description 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.
Severity error
Facility LOG_DAEMON
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
Description 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.
Severity warning
Facility LOG_DAEMON
VRRPD_GET_TRAP_HEADER_FAILED
System Log Message Request for trap signature header failed
Description The Virtual Routing Redundancy Protocol (VRRP) process requested the signature header
for an SNMP trap. The request failed.
Severity error
Facility LOG_DAEMON
VRRPD_LINK_LOCAL_ADD_MISMATCH
System Log Message Link-Local Address Mismatch: received-value expected-value
Description 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
Severity error
Facility LOG_DAEMON
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
Description 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.

Chapter 122: VRRPD System Log Messages
Severity error
Facility LOG_DAEMON

VRRPD_NEW_BACKUP
System Log Message Interface interface-name.interface-unit (local address interface-address) became VRRP
backup for group vrrp-group-id
Description 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.
Severity warning
Facility LOG_DAEMON
VRRPD_NEW_MASTER
System Log Message Interface interface-name.interface-unit (local address interface-address) became VRRP
master for group vrrp-group-id with master reason reason
Description 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.
Severity warning
Facility LOG_DAEMON
VRRPD_V3_PROTO_ERROR
System Log Message VRRP ad packet from ip-address received by interface interface-name.interface-unit was
invalid: reason
Description The Virtual Routing Redundancy Protocol (VRRP) advertisement packet sent from the
indicated IP address and received by the VRRP process (vrrpd) contained protocol error
as specified in RFC 6527.
Severity warning
Facility LOG_DAEMON
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

Description 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.
Severity error
Facility LOG_DAEMON

CHAPTER 123
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 Unable to authenticate httpd client (username username)
Description The checklogin authentication process could not authenticate the indicated user.
Severity notice
Facility LOG_AUTH
WEB_AUTH_SUCCESS
System Log Message Authenticated httpd client (username username)
Description The checklogin authentication process authenticated the indicated user.
Severity notice
Facility LOG_AUTH
WEB_AUTH_TIME_EXCEEDED
System Log Message Login attempt exceeded maximum processing time
Description The checklogin process halted a login attempt because it took longer than the maximum
processing time allowed.
Severity error
Facility LOG_AUTH
WEB_CERT_FILE_NOT_FOUND
System Log Message Could not find certificate file 'filename', disabling HTTPS

Description http-gk could not open the configured HTTPS certificate for reading.
Severity error
Facility LOG_DAEMON
WEB_CERT_FILE_NOT_FOUND_RETRY
System Log Message Could not find certificate file 'filename', retry after 1 sec
Description http-gk retry to open the configured HTTPS certificate for reading.
Severity error
Facility LOG_DAEMON
WEB_CHILD_STATE
System Log Message Unable to retrieve child state: error-message
Description The Web management process (httpd) could not retrieve state information for a child
process that had exited, for the indicated reason.
Severity error
Facility LOG_DAEMON
WEB_CONFIG_OPEN_ERROR
System Log Message Could not open 'filename' for writing
Description httpd-gk could not open the web server configuration file for writing.
Severity error
Facility LOG_DAEMON
WEB_CONFIG_WRITE_ERROR
System Log Message Could not write 'filename' configuration. Disk full?
Description httpd-gk could not write the web server configuration file to disk.
Severity error
Facility LOG_DAEMON

Chapter 123: WEB System Log Messages
WEB_COULDNT_START_HTTPD
System Log Message Could not fork httpd process!
Description The Web management gatekeeper process (httpd-gk) could not start the web
management process (httpd).
Severity error
Facility LOG_DAEMON
WEB_EVENTLIB_INIT
System Log Message Unable to initialize event library: error-message
Description The Web management gatekeeper process (httpd-gk) attempted to initialize the event
library during startup. The attempt failed for the indicated reason.
Severity error
Facility LOG_DAEMON
WEB_KEYPAIR_FILE_NOT_FOUND
System Log Message Could not find key pair file 'filename', disabling HTTPS
Description http-gk could not open the configured HTTPS key pair file for reading.
Severity error
Facility LOG_DAEMON
WEB_MGD_BIND_ERROR
System Log Message Could not bind mgd listener socket: error-message
Description The web management process could not open the MGD listening socket.
Severity error
Facility LOG_DAEMON
WEB_MGD_CHMOD_ERROR
System Log Message Could not chmod mgd listener socket
Description The web management process could not change the MGD listening socket to proper file
permissions.

Severity error
Facility LOG_DAEMON
WEB_MGD_CONNECT_ERROR
System Log Message Could not connect to mgd management socket
Description The web management process could not connect to the MGD management socket.
Severity error
Facility LOG_DAEMON
WEB_MGD_FCNTL_ERROR
System Log Message Could not set incoming mgd request to nonblocking
Description The web management process could not set the MGD listening socket to nonblocking.
Severity error
Facility LOG_DAEMON
WEB_MGD_LISTEN_ERROR
System Log Message Could not listen mgd listener socket: error-message
Severity error
Facility LOG_DAEMON

WEB_MGD_RECVMSG_PEEK_ERROR
System Log Message Could not peek recvmsg() mgd connection
Description The web management process could not peek the incoming MGD request.
Severity error
Facility LOG_DAEMON

Chapter 123: WEB System Log Messages
WEB_MGD_SOCKET_ERROR
System Log Message Could not create mgd listener socket
Severity error
Facility LOG_DAEMON
WEB_PIDFILE_LOCK
System Log Message Unable to lock PID file pathname: error-message
Description 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.
Severity error
Facility LOG_DAEMON
WEB_PIDFILE_UPDATE
System Log Message Unable to update PID file pathname: error-message
Description 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
Severity error
Facility LOG_DAEMON
Cause The most common reason is that another httpd-gk process was already running.
WEB_UNAME_FAILED
System Log Message Unable to retrieve system hostname: error-message
Description 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.
Severity error
Facility LOG_DAEMON

WEB_WEBAUTH_AUTH_FAIL
System Log Message Web-authentication of user username with fwauthd failed
Description The web-authentication authentication process was unable to authenticate the indicated
user
Severity notice
Facility LOG_DAEMON
WEB_WEBAUTH_AUTH_OK
System Log Message Web-authentication of user username with fwauthd successful
Description The web-authentication authentication process was able to authenticate the indicated
user successfully
Severity notice
Facility LOG_DAEMON
WEB_WEBAUTH_CONNECT_FAIL
System Log Message Unable to connect to fwauthd on socket file-descriptor: error-message
Description The web-authentication authentication process could not connect to fwauthd daemon
on the indicated socket
Severity error
Facility LOG_DAEMON

CHAPTER 124
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 Failed to enable the web-filtering category cache
Description Failed to enable the category cache for web-filtering
Severity error
Cause Temporarily out of system memory
Action No recommended action. For more information, see

WEBFILTER_INTERNAL_ERROR
System Log Message Error encountered: error-message
Description An error is encountered in a periodical task or during a server update
Severity error
Cause An error is encountered in a periodical task or during a server update
WEBFILTER_REQUEST_NOT_CHECKED
System Log Message Error encountered: server down, failed to check request error-message

Description Web-filtering failed to check a web request,
Severity error
Cause Failed to talk to web server, temporary out of system memory or internal error
Action No recommended action. For more information, see

WEBFILTER_SERVER_CONNECTED
System Log Message Successfully connected to webfilter server name
Description Client successfully connected to web server
Severity notice
Cause Successfully connected to web server
WEBFILTER_SERVER_DISCONNECTED
System Log Message Webfilter: server name disconnected
Description A socket error is encountered upon connecting to a web server
Severity notice
Cause A socket error is encountered upon connecting to a web server
WEBFILTER_SERVER_ERROR
System Log Message WebFilter: An error is received from server name (0xstatus-code): error-message
Description An error status is received from web server
Severity notice

Chapter 124: WEBFILTER System Log Messages
Cause An error status is received from web server


PART 3
Index
Index on page 881


ALARMD system log messages.........................................75
alert (system logging severity level 1).............................24
AMS System Log Messages.................................................81
ANALYZER System Log Messages...................................83
ANTISPAM system log messages....................................85
Index any (system logging facility)...............................................10
any (system logging severity level)..................................10
APPID system log messages..............................................87
Symbols APPIDD system log messages..........................................89
! APPPXY system log messages..........................................91
regular expression operator APPTRACK system log messages...................................93
system logging................................................26, 28 archive statement
#, comments in configuration statements...................lxx usage guidelines.............................................................20
$ archive-sites statement
regular expression operator system logging
system logging................................................26, 28 usage guidelines....................................................20
() ASP system log messages...................................................97
regular expression operator AUDITD system log messages.........................................129
system logging................................................26, 28 AUTHD system log messages..........................................133
( ), in syntax descriptions....................................................lxx authorization (system logging facility)...........................10
* option to facility-override statement.......................17
regular expression operator AUTOCONFD system log messages..............................137
system logging.................................................26, 27 AV system log messages.....................................................141
+
regular expression operator B
BBE system log messages.................................................145
system logging................................................26, 28
BFDD system log messages..............................................147
.
BGP system log messages.................................................151
regular expression operator
BOOTPD system log messages.......................................165
system logging.................................................26, 27
braces, in configuration statements................................lxx
< >, in syntax descriptions..................................................lxx
brackets
?
angle, in syntax descriptions.....................................lxx
square, in configuration statements......................lxx
system logging................................................26, 28
brief statement
[]
system logging
usage guidelines.....................................................12
system logging................................................26, 28
[ ], in configuration statements........................................lxx
^
C
CFMD system log messages...............................................171
change-log (system logging facility)...............................10
system logging................................................26, 28
CHASSISD system log messages....................................175
{ }, in configuration statements........................................lxx
CHASSISM system log messages..................................275
|
CLKSYNCD system log messages..................................277
comments, in configuration statements.......................lxx
system logging................................................26, 28
Common Criteria
| (pipe), in syntax descriptions..........................................lxx
system logging...................................................................7
conflict-log (system logging facility)...............................10
A
AAA system log messages..................................................69
ACCT system log messages.................................................71

console statement FCOE system log messages.............................................369

system logging file statement
usage guidelines.....................................................13 system logging
conventions usage guidelines......................................................11
text and syntax..............................................................lxix files
COSD system log messages............................................287 system log messages, archiving...............................20
critical (system logging severity level 2)........................24 files statement
curly braces, in configuration statements.....................lxx system logging
customer support..................................................................lxxi usage guidelines....................................................20
contacting JTAC............................................................lxxi FIP system log messages...................................................371
FIPS system log messages................................................375
D firewall (system logging facility).......................................10
daemon (system logging facility).....................................10 FLOW system log messages.............................................377
option to facility-override statement.......................17 font conventions....................................................................lxix
DCBX system log messages............................................303 FPCLOGIN system log messages....................................381
DCD system log messages...............................................305 FSAD system log messages.............................................383
DDOS system log messages.............................................313 ftp (system logging facility)................................................10
debug (system logging severity level 7).........................24 option to facility-override statement.......................17
dfc (system logging facility)................................................10 FUD system log messages................................................393
DFCD system log messages..............................................317 FWAUTH system log messages.....................................399
DFWD system log messages............................................321
DHCPD system log messages.........................................323 G
DIAM system log messages.............................................329 GPRSD system log messages.........................................405
documentation
comments on..................................................................lxx H
DOT1XD system log messages.........................................331 help syslog command
DYNAMIC system log messages....................................335 usage guidelines............................................................60
HNCACHED system log messages................................407
E host statement
emergency (system logging severity level 0)...............24 system logging
error (system logging severity level 3)............................24 usage guidelines for routing
ESWD system log messages............................................341 matrix.............................................................37, 46
EVENTD system log messages........................................351 usage guidelines for single-chassis
explicit-priority statement system....................................................................13
usage guidelines
routing matrix..................................................36, 45 I
single-chassis system..........................................22 ICCPD system log messages...........................................409
icons defined, notice..........................................................lxviii
F IDP system log messages...................................................411
FABOAMD System Log Messages..................................361 info (system logging severity level 6)..............................24
facilities (system logging) interactive-commands (system logging
alternate for remote machine.....................................17 facility)....................................................................................10
default for remote machine.........................................17
for local machine............................................................10 J
mapping of codes to names......................................23 JADE system log messages...............................................419
facility-override statement JCS system log messages.................................................423
system logging JDIAMETERD system log messages.............................429
usage guidelines.....................................................15 JIVED system log messages..............................................431
FC system log messages...................................................363 JNUD system log messages.............................................435

Index
JPTSPD system log messages.........................................437 no-world-readable statement

JSERVICES system log messages..................................441 system logging
JSRPD system log messages...........................................445 usage guidelines....................................................20
JTASK system log messages...........................................455 notice (system logging severity level 5).........................24
Junos-FIPS notice icons defined...........................................................lxviii
system logging...................................................................7 NSD system log messages................................................617
NSTRACED system log messages..................................619
K NTPD system log messages............................................623
kernel (system logging facility)..........................................10
option to facility-override statement......................18 O
operators, regular expression
L system logging.........................................................26, 27
L2ALD system log messages...........................................487 other-routing-engine option to host statement
L2CPD system log messages..........................................503 usage guidelines
L2TPD system log messages...........................................507 routing matrix..................................................37, 46
LACP system log messages..............................................537 single-chassis system...........................................13
LACPD system log messages..........................................539
LFMD system log messages.............................................541 P
LIBJNX system log messages..........................................543 parentheses, in syntax descriptions................................lxx
LIBJSNMP system log messages...................................553 pfe (system logging facility)................................................10
LIBMSPRPC system log messages...............................559 PFE system log messages........................................621, 627
LICENSE system log messages......................................563 PFED system log messages.............................................635
LLDP system log messages...............................................571 PGCPD system log messages..........................................637
local0 - local7 (options to facility-override PING system log messages..............................................639
statement).............................................................................18 PKID system log messages..............................................643
log files PPMD system log messages...........................................653
specifying properties....................................................20 PPPD system log messages............................................655
log-prefix statement priorities
system logging system logging, including in log message
usage guidelines.....................................................19 for routing matrix...........................................36, 45
LOGIN system log messages............................................573 for single-chassis system...................................22
LPDFD system log messages...........................................579 PROFILER system log messages...................................663
LRMUX system log messages..........................................581
LSYSD system log messages..........................................583 R
RDD system log messages...............................................665
M regular expression operators
manuals system logging.................................................................27
comments on..................................................................lxx RMOPD system log messages.......................................669
match statement routing matrix
usage guidelines.............................................................25 system logging.................................................................31
MBG system log messages..............................................585 RPD system log messages................................................673
MCSN system log messages............................................601 RT system log messages....................................................747
MIB2D system log messages..........................................603 RTLOG system log messages...........................................761
MPLS_OAM system log messages..................................611 RTLOGD system log messages.......................................763
N S
NEXTHOP system log messages....................................615 SAVAL system log messages............................................767
scc-master option to host statement
usage guidelines.............................................................33

SDK system log messages................................................769 regular expression filtering..........................................25

SDXD system log messages..............................................771 regular expression operators......................................27
severity levels for system logging.....................................24 routing matrix...................................................................31
size statement severity levels...................................................................24
system logging single-chassis system.....................................................7
usage guidelines....................................................20 timestamp, modifying..................................................25
SMTPD system log messages..........................................777 SYSTEM system log messages........................................813
SNMP system log messages............................................779
SNMPD system log messages.........................................783 T
source-address statement technical support
system logging contacting JTAC............................................................lxxi
usage guidelines for routing TFTPD system log messages...........................................815
matrix.............................................................37, 46 time-format statement
usage guidelines for single-chassis usage guidelines.............................................................25
system....................................................................15 transfer-interval statement
SPD system log messages................................................797 system logging
SSH system log messages...............................................805 usage guidelines....................................................20
SSHD system log messages.................................807, 809 TRANSPORTD system log messages...........................819
start-time statement TX Matrix platform
system logging system logging.................................................................31
usage guidelines....................................................20
structured-data statement U
usage guidelines..............................................................12 UFDD system log messages............................................823
support, technical See technical support UI system log messages....................................................825
syntax conventions...............................................................lxix user (system logging facility)..............................................10
syslog statement option to facility-override statement......................18
system processes user statement
usage guidelines.......................................................3 system logging
system logging usage guidelines.....................................................13
Common Criteria...............................................................7 UTMD system log messages...........................................855
defaults................................................................................4
different on each node in routing matrix..............38 V
disabling............................................................................28 VCCPD system log messages..........................................857
examples...........................................................................29 VM system log messages.................................................863
facilities VRRPD system log messages.........................................865
alternate for remote machine............................17
default for remote machine................................17 W
for local machine...................................................10 warning (system logging severity level 4).....................24
mapping of codes to names.............................23 WEB system log messages..............................................869
files, archiving..................................................................20 WEBFILTER system log messages................................875
forwarding messages in routing matrix.................33 world-readable statement
Junos-FIPS...........................................................................7 system logging
message descriptions usage guidelines....................................................20
displaying.................................................................60
fields in......................................................................60
messages, displaying
generated by Junos process..............................55
generated by service on PIC..............................56
structured-data format.......................................51

Syslog Messages

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Syslog Messages

Transféré par

Droits d'auteur :

Formats disponibles

Junos OS

System Log Messages Reference

Copyright 2015, Juniper Networks, Inc.

YEAR 2000 NOTICE

END USER LICENSE AGREEMENT

ii Copyright 2015, Juniper Networks, Inc.

Part 2 System Log Messages

Copyright 2015, Juniper Networks, Inc. iii

Chapter 29 DDOS System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

iv Copyright 2015, Juniper Networks, Inc.

Chapter 67 LACPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539

Copyright 2015, Juniper Networks, Inc. v

Chapter 105 SDXD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771

vi Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. vii

Adding a Text String to System Log Messages Directed to a Remote

viii Copyright 2015, Juniper Networks, Inc.

Displaying and Interpreting System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . 49

Part 2 System Log Messages

Copyright 2015, Juniper Networks, Inc. ix

x Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xi

xii Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xiii

xiv Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xv

xvi Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xvii

xviii Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xix

xx Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xxi

xxii Copyright 2015, Juniper Networks, Inc.

Chapter 25 CLKSYNCD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Copyright 2015, Juniper Networks, Inc. xxiii

xxiv Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xxv

xxvi Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xxvii

xxviii Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xxix

xxx Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xxxi

Chapter 51 IDP System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

xxxii Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xxxiii

xxxiv Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xxxv

xxxvi Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xxxvii

xxxviii Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xxxix

xl Copyright 2015, Juniper Networks, Inc.

Copyright 2015, Juniper Networks, Inc. xli

xlii Copyright 2015, Juniper Networks, Inc.

Chapter 74 LOGIN System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573

Copyright 2015, Juniper Networks, Inc. xliii

xliv Copyright 2015, Juniper Networks, Inc.

Chapter 79 MCSN System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601

Copyright 2015, Juniper Networks, Inc. xlv

Chapter 86 NTPD System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623

xlvi Copyright 2015, Juniper Networks, Inc.

Chapter 91 PING System Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639

Copyright 2015, Juniper Networks, Inc. xlvii