- Introduction
- Cover Page
- play_arrow Junos OS Release Notes for ACX Series
- play_arrow Junos OS Release Notes for cPCE
- play_arrow Junos OS Release Notes for cRPD
- play_arrow Junos OS Release Notes for cSRX
- play_arrow Junos OS Release Notes for JRR Series
- play_arrow Junos OS Release Notes for MX Series
- play_arrow What's New
- Hardware
- Authentication and Access Control
- Chassis
- Class of Service
- Dynamic Host Configuration Protocol
- EVPN
- Forwarding Options
- High Availability
- Interfaces
- Juniper Extension Toolkit (JET)
- Junos OS API and Scripting
- Junos Telemetry Interface
- MPLS
- Network Management and Monitoring
- Precision Time Protocol (PTP)
- Public Key Infrastructure (PKI)
- Routing Policy and Firewall Filters
- Routing Protocols
- Securing GTP and SCTP Traffic
- Serviceability
- Services Applications
- Source Packet Routing in Networking (SPRING) or Segment Routing
- Software Installation and Upgrade
- Subscriber Management and Services
- Additional Features
- What's Changed
- Known Limitations
- Open Issues
- Resolved Issues
- Migration, Upgrade, and Downgrade Instructions
- play_arrow Junos OS Release Notes for NFX Series
- play_arrow Junos OS Release Notes for QFX Series
-
- play_arrow What's New
- Hardware
- Application Identification (AppID)
- Chassis
- Flow-Based and Packet-Based Processing
- High Availability
- Interfaces
- Juniper Advanced Threat Prevention Cloud (ATP Cloud)
- Juniper Extension Toolkit (JET)
- J-Web
- Network Management and Monitoring
- Public Key Infrastructure (PKI)
- Serviceability
- Software Installation and Upgrade
- VPNs
- Additional Features
- What's Changed
- Known Limitations
- Open Issues
- Resolved Issues
- Migration, Upgrade, and Downgrade Instructions
- Documentation Updates
- play_arrow Junos OS Release Notes for vSRX
- Licensing
- Finding More Information
- Requesting Technical Support
- Revision History
System Logging
Support for sending system log messages from the default routing instance when the dedicated management instance is configured (EX2300, EX2300-MP, EX2300-C, EX2300-VC, EX3400, EX3400-VC, EX4100-48MP, EX4100-H-12P, EX4100-H-12P-DC, EX4100-H-24P, EX4100-H-24P-DC, EX4100-H-24F, EX4100-H-24F-DC, EX4100-24MP, EX4100-48P, EX4100-48T, EX4100-24P, EX4100-24T, EX4100-F-48P, EX4100-F-24P, EX4100-F-48T, EX4100-F-24T, EX4100-F-12P, EX4100-F-12T, EX4300-MP, EX4300VC, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4600-VC, EX4650, EX4650-48Y-VC, EX9204, EX9208 and EX9214)—Starting in Junos OS Release 24.2R1, when you configure the system logging information, the system does not have to use the dedicated management instance. System logging traffic prioritizes routing instances configured at the
host
level. Next, it prioritizes the routing instances configured at thesyslog
level. If you do not configure a routing instance at either of these levels, even if the management instance is configured at the global level, the system log messages default to the default routing instance and the inet.0 routing table. Prior to this release, when the dedicated management instancemgmt_junos
was configured, system logging traffic used it by default. Thus, system logs reach the host only if the host is reachable by the default inet.0 routing instance.[See System Logging and Routing Instances and Management Interface in a Dedicated Instance.]