Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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

    Related Documentation


    Logging SRC VTA Messages to a System Logging Server

    Use this procedure to configure the SRC VTA to save messages, such as event messages, SRC VTA startup messages, errors, and so on, on a system logging server.

    Use the following statement to configure the SRC VTA to save messages on a system logging server:

    shared vta group name logger name syslog {filter filter;host host;}
    1. From configuration mode, access the statement that configures logging to the system log facility. For example, to configure a logger called vta1-logger for the SRC VTA group called vta1:
      [edit]user@host# edit shared vta group vta1 logger vta1-logger syslog
    2. (Optional) Specify a filter that determines the type of messages that this log file contains.
      [edit shared vta group vta1 logger vta1-logger syslog]user@host# set filter filter

      The filter is specified in an expression. The software filters events by evaluating each subexpression from left to right. When the software finds a match, it logs or ignores the message accordingly. You can specify an unlimited number of subexpressions. The order in which you specify the subexpressions affects the result. Expressions have the format:

      singlematch [,singlematch]


      singlematch—[!] ( <category> | ([<category>]/[<severity>] | [<minimumSeverity>]-[<maximumSeverity>] ))

      • !—Do not log matching events.
      • <category>—SRC component that generated the event message. To log only events in a specific category, you can define the category, which is a text string that matches the name of a category. The text string is not case sensitive. For the names of categories, view a log file for a default filter. Juniper Networks Technical Assistance Center (JTAC) can also provide category names.
      • [<severity>] | [<minimumSeverity>]-[<maximumSeverity>]—Name or number in the range 1–127. A higher number indicates a higher severity level. Table 1 shows common severity levels that you can specify by name.

        Table 1: Named Severity Levels


        Severity Level























        For the SRC VTA, you can perform event trail logging, which is helpful when debugging the SRC VTA configuration. Event trail logging logs messages that show you exactly how the SRC VTA is handling each event as it passes through the SRC VTA. You can follow a particular event as it passes through the SRC VTA and see exactly how each event handler and action handles that event.

        To set up event trail logging, set the filter option to filter EventTrail/9-. Enabling event trail logging generates messages such as the following:

        14:19:59.008 EST 16.11.2011 [Thread-21 (group:HornetQ-client-global-threads-1542419015)] [EventTrail] [9] 
          Event trail afe51007-7e35-465b-a515-3be12735afd6
          VTA received event: 
            Event type = SAEPluginEvent
            Event name = USERSTART
              PA_ACCT_INTERIM_TIME = 0
              PA_DOMAIN =
              PA_EVENT_TIME = 1321471198
              PA_EVENT_TIME_MILLISECOND = 1321471198995
              PA_INTERFACE_NAME = ip10.227.1.96
              PA_INTERFACE_SPEED = 0
              PA_IN_OCTETS = 0
              PA_IN_PACKETS = 0
              PA_LAC_IP = 0
              PA_LOGIN_NAME =
              PA_NAS_INET_ADDRESS =
              PA_NAS_IP =
              PA_NAS_PORT = 0
              PA_OUT_OCTETS = 0
              PA_OUT_PACKETS = 0
              PA_PRIMARY_USER_NAME =
              PA_ROUTER_NAME = sim
              PA_ROUTER_TYPE = junos
              PA_SESSION_ID = KcVGVRM6OAwL0AAU
              PA_SESSION_TIME = 0
              PA_SESSION_TIMEOUT = -1
              PA_SSP_HOST = kimberley
              PA_TERMINATE_CAUSE = 0
              PA_TUNNEL_ID = 0
              PA_TUNNEL_SESSION_ID = 0
              PA_USER_DN = uniqueId=vtatest1,ou=group01,retailerName=vtatest,o=Users,o=UMC
              PA_USER_INET_ADDRESS =
              PA_USER_IP_ADDRESS =
              PA_USER_TYPE = AUTHINTF
              PA_VPN_ID = 
              currentTime = 1321471199007
              processingUuid = afe51007-7e35-465b-a515-3be12735afd6
              subscriberId =
            SAE information:
              SAE references = [IOR:000000000000003549444C3A736D67742E6A756E697065722E6E657
              NIC proxy namespace = /nicProxies/np1
              VTA subscriber ID solution = [Subscriber ID = PA_LOGIN_NAME, NIC key = PA_LOGIN_NAME, SAE key = LOGIN_NAME]
              SAE subscriber ID = LOGIN_NAME
            SAE subscriber references: 0
        14:19:59.008 EST 16.11.2011 [Thread-21 (group:HornetQ-client-global-threads-1542419015)] [EventTrail] [9] 
          Event trail afe51007-7e35-465b-a515-3be12735afd6
          VTA ignoring event.
        14:19:59.039 EST 16.11.2011 [Thread-19 (group:HornetQ-client-global-threads-1542419015)] [EventTrail] [9] 
          Event trail cea6f3b3-efc7-46c1-9e8a-b26b721f03cc
          Event handler NoQuota: Received event.
        14:19:59.039 EST 16.11.2011 [Thread-19 (group:HornetQ-client-global-threads-1542419015)] [EventTrail] [9] 
          Event handler NoQuota: Ignoring event cea6f3b3-efc7-46c1-9e8a-b26b721f03cc
        14:19:59.040 EST 16.11.2011 [Thread-19 (group:HornetQ-client-global-threads-1542419015)] [EventTrail] [9] 
          Event trail cea6f3b3-efc7-46c1-9e8a-b26b721f03cc
          VTA completed processing event.

        This is only an excerpt of the log and does not show all messages. Notice that each message starts with a unique ID generated when the SRC VTA starts processing an event—for example, “Event trail afe51007-7e35-465b-a515-3be12735afd6.”

        Enabling debug log messages has a negative effect on system performance. Do not enable debug log messages unless JTAC instructs you to do so.

        You can define a severity level as follows:

        • Specify an explicit severity. For example:

          warning—Defines only warning 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 severity to log all event messages.
      • Example—Table 2 shows some examples of filters.

        Table 2: Examples of Filters for Event Messages


        Event Messages Saved


        All event messages


        Event messages of level info and higher from all categories


        Debug events from the SRC VTA category only


        All debug events except those from the SRC VTA category


        All messages from the SRC VTA category, except those from the VtaMsg category with level lower than info

    3. Specify the host information for the system log server.
      [edit shared vta group vta1 logger vta1-logger syslog]user@host# set host host

      Specify an IP address or name of a host that collects event messages with a standard system logging daemon.


    Related Documentation


    Published: 2014-12-16