Starting OMPROUTE tracing and debugging from the z/OS UNIX System Services shell

If OMPROUTE is started from the z/OS UNIX System Services shell command line (using the omproute command), you can specify the following parameters to indicate the level of tracing or debugging that you want.

  • -tn and -6tn (where n is a supported trace level)

    These options specify the OMPROUTE external tracing levels, with -tn covering both OMPROUTE initialization and IPv4 routing protocols and -6tn covering IPv6 routing protocols. These options provide information about the operation of the routing application and can be used for many purposes, such as debugging a configuration, education on the operation of the routing application, verification of test cases, and so on. The following trace levels are supported:

    • 1 = Informational messages
    • 2 = Formatted packet trace
  • -sn (where n is a supported debug level)

    This option specifies the internal debugging level for the OMPROUTE subagent. It provides internal debugging information needed for debugging problems. The following level is supported:

    • 1 = Internal debugging messages. This turns on DPIdebug(2).
  • -dn and -6dn (where n is a supported debug level)

    These options specify the OMPROUTE internal debugging levels, with -dn covering both OMPROUTE initialization and IPv4 routing protocols and -6dn covering IPv6 routing protocols. These options provide internal debugging information needed for debugging problems. The following levels are supported:

    • 1 = Internal debugging messages.
    • 2 = Unformatted hexadecimal packet trace
    • 3 = Function entry or exit trace
    • 4 = Task add or run
Guidelines:
  • The -tn, -6tn, -dn, and -6dn options affect OMPROUTE performance. As a result, you might have to increase the Dead Router Interval on OSPF and IPv6 OSPF interfaces to prevent neighbor adjacencies from collapsing.
  • The trace and debug levels are cumulative; each level includes all lower levels. For example, -t2 provides formatted packet trace and informational messages. You can enter more than one parameter by inserting a space after each parameter, for example, omproute -t1 -d2, which is the trace level most often requested by support. For more information, see APAR II12026.
  • Parameters can be specified in mixed case.
Parent topic: OMPROUTE traces and debug information