Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Categories and Severity Levels for Event Messages

    In the logging configuration, you can specify a filter for each type of log. This filter can include an expression that defines the categories and severity levels of event messages that the software saves. You can also enable network device-specific filtering for service activation engine (SAE) debug logs.

    Defining Categories

    The category of an event message defines the SRC component that generated the event message. If you want to view only event logs in a specific category, you can define a variable <category>, which is a text string that matches the name of a category. This variable is not case sensitive. To view the names of categories for event messages, view a log file for one of the default filters.

    For example purposes, Table 1 lists the SAE logging categories and associated severity levels. These categories are relevant only for loggers configured with the shared sae …. configuration logger statement. The extension refers to loggers that dynamically change their name at runtime. Juniper Networks Customer Service can also provide names of categories for other components, especially for troubleshooting purposes.

    Table 1: SAE Categories and Severity Levels

    CategoryExtensionSeverity Level

    AAAExtIntf

    error, debug, debug_8

    AAAExtIntfIDGenerator

    error

    AAALdapListener

    error, debug

    AAARouterDriver

    info, error, debug

    AAASolicitedJob

    info, warning, error, debug

    AccessManager

    info, error, debug

    AccountingFileDict

    info, error, debug

    AccountingFilePeer

    info, error, debug

    ACPIntfListener

    error, debug

    ACRMsg

    warning, debug

    AddressCtx

    info, error, debug

    Admin

    info, error, debug

    AggregateServiceSession

    error, debug

    AMGroupLDAPListener

    info, debug

    ASRMsg

    warning, debug

    Atom

    debug

    BEEPDebug

    -

    debug_9

    ClassifyDhcp

    error, debug

    ClassifyInterface

    info, error, debug

    ClassifyUser

    error

    Client

    /

    info, error, debug

    ClientMgr

    /

    info, error, debug

    Commands

    error

    CommunityManager

    error, debug

    CommunityMember

    info, error, debug, debug_9

    ConfigChecker

    info, error, debug

    COPSDecoder

    info, debug_9

    COPSEncoder

    info, debug_10

    Core API

    error, debug

    CustomRadiusAccounting

    error, debug

    CustomRadiusAuth

    error, debug

    DataManagerMIData

    error

    DCImpl

    warning, error, debug

    DhcpManager

    error, debug

    DhcpOptions

    error

    DiameterDriverManager

    info, error, debug

    DiameterMsgHandler

    warning, error, debug, debug_8

    DiameterPlacementProcessor

    error

    DiameterRouterDriver

    info, warning, error, debug

    DiameterUnsolictedMsg

    info, warning, error, debug

    DiscoverDecisionHelper

    error

    DynRadiusServer

    error, debug

    EmbeddedPrecedenceProcessor

    error, debug_9

    EquipRamCache

    debug

    EquipRegLdapDataManager

    info, error, debug

    EquipRegLDAPDataManagerConnectionThread

    info, error, debug

    EventBatch

    error, debug

    EventPublisher

    error, debug

    Extension Script

    info, error, debug

    ExtInterface

    info, warning, error, debug

    ExtIntf

    info, error, debug

    FailQueue

    error, debug

    FeedbackManager

    info, error

    FileDeleter

    info, error, debug

    FileRotater

    info, error, debug

    FileTrackingPluginEventListener

    info, error, debug

    FlexibleRadiusAuthPluginEventListener

    info, error, debug

    FlexibleRadiusTrackingPluginEventListener

    info, error, debug

    FloatingContext

    info, error, debug

    GateProcessor

    error, debug

    GenericService

    error, debug

    GenericSessionJobManager

    info, error, debug

    HostUtil

    error, debug

    HttpAttachmentProcessor

    info, error, debug

    IdleTimeoutObject

    debug

    InfrastructureServiceSession

    error, debug

    InterfaceSession

    error

    InterfaceTimeoutManager

    debug

    InterimSessionJobManager

    info, error, debug

    IpInterfaceCtx

    info, error, debug

    ISEExtIntf

    error, debug

    ISEPORetriever

    error, debug

    ISEProvisioningContext

    error

    ISERouterDriver

    info, warning, error, debug

    ISESolicitedJob

    info, warning, error, debug

    JobQueue

    info, debug_9

    JunoScriptConfHelper

    -

    info

    JunoScriptSubChannelHandler

    -

    debug, trace

    JunosDriverManager

    info, error, debug

    JunosEDriverManager

    info, error, debug

    JunosEIcc

    error, debug

    JunoseJob

    error, debug

    JunosERouterDriver

    info, error, debug, debug_9, perf

    JunosERouterFactory

    info

    JunosEXDRRouterDriver

    info, error, debug, debug_9, perf

    JunosRouterDriver

    info, error, debug, debug_9

    JunosRouterFactory

    info

    JunosServiceActivationPoint

    error, debug

    JunosSessionManager

    error, debug

    JunosSyslogConfigHandler

    info, error, debug

    JunosSyslogSubChannelHandler

    info, error, debug

    KeepAliveTimer

    error

    LdapAuthenticator

    error, debug

    LDAPConfManager

    error

    LicenseCheck

    info, error

    LicenseLDAPListener

    debug

    LicenseManager

    info, error, debug

    LicenseServerClient

    info, error, debug

    LicenseUtil

    debug

    LimitNumSubscriberPerIntfAuthPluginListener

    debug

    ListenerJobManager

    debug

    LiveSessions

    /

    info, error, debug

    LocalPersistentCheck

    error

    LoginNameParser

    error

    LoginRequest

    error, debug

    LogoutRequest

    error, debug

    Main

    info, debug, panic

    MemFailQueue

    error, debug

    MsgInOps

    info, error, debug_8

    MsgOutPostUpdateOps

    info, debug, debug_8

    MsgOutUpdateOps

    info, debug

    NasPortUtil

    debug

    NicProxyCompleter

    error

    OpsBuffer

    info, error, debug

    PingJob

    error, debug_9

    PluginManager

    info, error, debug

    PluginUtil

    error

    PolicyParameterEngine

    debug_8

    PolicyDecisionPointLDAPListener

    info, debug

    PolicyListAugmentingProcessor

    info, error, debug

    PolicyLists

    debug_9

    PolicyListSharingProcessor

    error, debug

    PolicyPPRMsg

    warning, error, debug

    PolicyServiceSession

    error, debug

    PolicySharedCtx

    info, error, debug

    Portal API

    error, debug

    PostponedScheduledService

    debug

    PostSyncJob

    debug

    ProcessorManager

    error, debug

    ProxyDriverManager

    error, debug

    ProxyRouterDriver

    info, error, debug, debug_9

    ProxySessionManager

    info, error, panic

    PTSPRouterDriver

    error, debug

    PublisherQueue

    info, error, debug

    QoSAttachmentProcessor

    info, error, debug

    QosProfileTrackingEntry

    info, error, debug

    QTPEventListener

    info, error, debug

    QTPJobQueue

    error

    QTPThreadPoolThread

    error, debug

    RadiusAuthPluginEventListener

    info, error, debug

    RadiusPacket

    error, debug

    RadiusPeer

    -

    info, error, debug, debug_9

    RadiusPeerGroup

    -

    info, error, debug

    RadiusPluginEventListener

    info, error, debug

    RadiusSocket

    info, error, debug, debug_9

    RadiusTrackingPluginEventListener

    info, error, debug

    ReadyToSyncJob

    error, debug_9

    RefCounter

    error

    ReferencedPrecedenceProcessor

    error, debug_9

    ReferencedProcessor

    error, debug

    RemotePlugin

    info, error, debug

    ReplayJob

    error, debug

    Replicator

    info, error, debug, debug_9

    Retailer

    error, debug

    RetailerLdapListener

    error, debug

    RksEventListener

    info, error, debug

    RksPluginPublisher

    error, debug

    RouteConfigPPRMsg

    warning, error, debug

    RouterComponent

    info, error

    RouterLDAPListener

    debug

    RouterRegistry

    info, error, debug

    RouterScript

    info, error, debug

    RouterScriptComponent

    error

    SAEAccessImpl

    debug

    SAE-AUDIT

    info, notice, warning

    SchedulingAuthPlugin

    info, error, debug

    ScriptServiceSession

    info, error, debug

    ServiceActivator

    info, error, debug

    ServiceAuthEvent

    debug

    ServiceFragment

    debug

    ServiceLDAPDataManager

    info, error, debug

    ServiceLDAPDataManagerConnectionThread

    info, error, debug

    ServiceLdapListener

    error, debug

    ServiceManager

    error, debug

    ServiceMutexGroup

    error

    ServiceMutexGroupLdapListener

    info, error, debug

    ServiceMutexGroupManager

    debug

    ServiceProfile

    error

    ServiceProfileLdapListener

    error, debug

    ServiceSchedule

    error

    ServiceScheduleLdapListener

    info, error, debug

    ServiceScheduleManager

    debug

    ServiceScopeLdapListener

    info, error, debug

    ServiceSession

    info, error, debug

    ServiceSessionAttributes

    debug

    ServiceVrLdapListener

    info, error, debug

    SessionAudit

    notice

    SessionFactory

    info, error, debug

    SessionJob

    error

    SessionJobManager

    info, error, debug

    SessionStoreFactory

    info, error, debug

    SessionStoreImpl

    /

    info, error, debug

    SimRouter

    info, warning, error, debug

    SimRouterDriver

    info, error, debug, debug_9

    Slave

    /

    info, error, debug

    SlaveMgr

    info, error, debug

    SolicitedReplyFactory

    error, debug, debug_9

    SRQMsg

    warning, debug

    SSFile

    info, error, debug

    SSFiles

    /

    info, error, debug, debug_6

    SspAccRadiusPeerMI

    info, error

    SspAuthRadiusPeerMI

    info, error

    SspSM

    info, error, debug

    SsrAttributePluginHelper

    error, debug

    SsrEventHandler

    info, error, debug

    SSREventJob

    error

    SsrReaderPluginEventListener

    error, debug

    SSRServiceEventJob

    info, error, debug

    SSRSubscriberEventJob

    info, error, debug

    SsrWriterPluginEventListener

    info, error, debug

    StateSynchronizer

    info, error, debug

    Stats

    info, error, debug

    StoreConfig

    info, error, debug

    StoreOpIterator

    debug, debug_8

    SubscriberRef

    info, error, debug

    SubscriberScheduleLdapListener

    error, debug

    SubscriberScheduleManager

    debug

    SubscriptionParser

    error

    Table

    debug

    TestMaster

    info, error, debug

    TestPromo

    debug

    TimeoutSessionJobManager

    info, error, debug

    TimePolicyManager

    info, error, debug

    Transaction

    error, debug, debug_9

    TransactionManager

    debug, debug_9

    UCCImpl

    error, debug

    UnsolicitedMessage

    error, debug

    UnsolicitedMsgFactory

    debug

    UnsolicitedTimeoutJob

    error, debug

    UserLDAPDataManager

    info, error, debug

    UserLDAPDataManagerConnectionThread

    info, error, debug

    UserLdapListener

    debug

    UserManager

    error, debug

    UserProfile

    error, debug

    UserProfileManager

    debug

    UserRamCache

    debug

    UserSession

    info, error, debug

    WrapperServiceSession

    error, debug

    Defining Severity Levels

    The event filter provides 128 levels of severity numbered 1–127. A higher number indicates a higher level of severity. Common levels of severity also have a specific name, as shown in Table 2.

    Caution: Enabling the generation of debug log messages has a negative affect on system performance. Do not enable debug log messages unless you are instructed to do so by Juniper Networks Technical Assistance Center (JTAC).

    Table 2: Named Severity Levels

    Name

    Severity Level

    logmin

    1

    debug

    10

    info

    20

    notice

    30

    warning

    40

    error

    50

    crit

    60

    alert

    70

    emerg

    80

    panic

    90

    logmax

    127

    You can define a severity level as follows:

    • Specify an explicit severity. For example:
      • debug—Defines only debug messages
    • Specify a minimum severity and a maximum severity. For example:
      • info-warning—Defines messages of minimum severity level of info and a maximum severity level of warning
      • Accept the default minimum (logmin) or maximum (logmax) severity by omitting the minimum or maximum severity. For example:
      • info-—Defines messages of minimum severity level info and maximum severity level logmax
      • -warning—Defines messages of minimum severity level logmin and maximum severity level warning
    • Specify no severities to log all event messages.

    The syntax for the severity takes the format:

    [<severity>] | [<minimumSeverity>]-[<maximumSeverity>]

    Use either the name or the number of a severity level shown in Table 2 for the variables in this syntax.

    Defining Filters

    You specify a filter by defining an expression with the following format:

    singlematch [,singlematch]*

    • singlematch—[!] ( <category> | ([<category>]/[<severity>] | [<minimumSeverity>]-[<maximumSeverity>] ))
    • !—Do not log matching events
    • <category>—See Defining Categories
    • [<severity>] | [<minimumSeverity>]-[<maximumSeverity>]—See Defining Severity Levels .

    The software filters events by evaluating each subexpression in order from left to right. When the software determines that an event message matches a subexpression, the software logs or ignores the message accordingly. You can specify an unlimited number of subexpressions; however, the order in which you specify the subexpressions affects the result.

    Note: When you configure a filter, you must set appropriate values for categories and severity levels. Otherwise, the commit is not successful and when you commit the changes, a message indicating that the configured filter is invalid is displayed.

    Table 3 shows some examples of filters.

    Table 3: Examples of Filters for Event Messages

    Syntax

    Event Messages Saved

    /

    All event messages

    /info-

    Event messages of level info and above from all categories

    Cops/debug

    Debug events from COPS category only

    !Cops,/debug

    All debug events except those from COPS category

    CopsMsg/info-,!CopsMsg,Cops

    All messages from COPS category, except those from CopsMsg category with level less than info

    Enabling Network Device-Specific Filtering for SAE Debug Logs (SRC CLI)

    You can enable network device-specific filtering for SAE debug logs based on router name, interface name, or login name by including the device-filter-key option under the shared sae …. configuration logger hierarchy level. Enabling network device-specific SAE debug log filtering reduces the size of the debug log files, thereby simplifying troubleshooting and minimizing the impact on SAE performance.

    You can enable network device-specific filtering of SAE debug logs only if you set the SAE severity level to debug and then include the device-filter-key option under the shared sae …. configuration logger hierarchy level. If you do not set the SAE severity level to debug, but enable network device-specific filtering, then no information is logged in to the SAE debug log file. When using network device-specific filtering, you can add one or more device filters by using an expression that defines certain criteria. Only log events matching the criteria are logged in the SAE debug log file. Events that do not match the criteria are not logged in the SAE debug log file.

    Note: SRC network device–specific filtering for SAE debug logs is supported on JunosE (COPS) and Junos OS (JSRC) devices.

    If the network device-specific debug log filtering is not enabled, the SAE debug logger displays its default behavior. By default, log events that match the subexpression defined by using the filter option are logged.

    You can configure network device-specific debug log filtering by defining an expression with the following format:

    deviceFilter [deviceFilter]*

    • deviceFilter—OpenQuotes deviceFilterKey CloseQuotes
    • deviceFilterKey—SingleDevKey *[Operands SingleDevKey]
    • SingleDevKey—varName Equality valName
    • varName—“router-name” or “interface-name” or “login-name”
    • AlphaNumeric—%x41-5A / %x61-7A / %x30-39 / %x2A
    • valName—1*AlphaNumeric
    • Equality—“=” or “!=”
    • Operands—“&” or “|”
    • OpenQuotes—“
    • CloseQuotes—”

    The deviceFilterKey expression is composed of one or more SingleDevKey expressions. A SingleDevKey expression should begin with an open brace and end with a close brace.

    The SAE filters events by evaluating each deviceFilter in order from left to right. You can specify an unlimited number of device filters; however, the order in which you specify the device filter affects the result. The SAE only logs event messages that match all the criteria.

    You specify the deviceFilter with the format rules described in Table 4.

    Table 4: SAE Debug Device Filter Formatting Rules

    Rule

    Definition

    Meaning

    OpenQuotes

    Denotes an open single or double quotation mark, which is used at the beginning of an expression

    CloseQuotes

    Denotes a close single or double quotation mark, which is used at the end of an expression

    Equality

    =

    Allows logging of only the logevent whose value is equal to the value specified in the valName

    !=

    Allows logging of only the logevent whose value is not equal to the value specified in the valName

    Operands

    &

    Allows logging of only the logevent whose value matches the valName value specified in all SingleDevKey expressions in a deviceFilterKey

    |

    Allows logging of the logevent even if its value matches the valName value specified in any one of the SingleDevKey expressions in a deviceFilterKey

    varName

    router-name or interface-name or login-name

    Variable names supported to specify the deviceFilterKey.

    valName

    AlphaNumeric

    Value name associated with each variable name. A valName can contain alphanumeric characters as well as a wildcard character (*).

    SingleDevKey

    varName Equality valName

    Pair of varName and valName associated by using an Equality. Multiple SingleDevKey expressions are associated by using Operands.

    Table 5 lists some examples of network device-specific SAE debug filter configurations.

    Table 5: Sample Combinations of Conditions for the device-filter-key Expression

    Syntax

    Notes

    set device-filter-key “router-name=erx440 & interface-name=Fast*”

    Uses the AND operator

    set device-filter-key “router-name=erx440 | interface-name=Fast*”

    Uses the OR operator

    set device-filter-key “router-name=erx440 & interface-name=Fast* | login-name = jane@virneo.net”

    Uses the AND and OR operators

    set device-filter-key “router-name=erx440 & interface-name=Fast* & login-name = jane*net”

    Uses the wildcard character (*) for pattern match

    set device-filter-key “router-name=erx440 | router-name =erx448”

    Uses multiple deviceFilterKey configurations

    set device-filter-key “router-name=erx440 & interface-name!=Fast*”

    Uses the “not equal to” condition

    Modified: 2015-07-22