Home > Articles > Cisco > CCNP Routing and Switching

  • Print
  • + Share This
This chapter is from the book


This section is where you configure the traces that can assist you in troubleshooting. They are trace configurations and troubleshooting traces. You can configure three types of traces: SDI, SDL, and Log4j. The trace configuration option you pick has a big impact on the information you will receive and how much time you will probably spend during problem resolution. You can see what type of traces you can configure by checking out Figure 3-2. The files can be viewed in RTMT:

  • Configuration: Configure traces.
  • Troubleshooting Trace Settings: Set up predefined troubleshooting traces.
Figure 3-2

Figure 3-2 Where and How You Set Up Traces

You are probably wondering how to choose between a trace and troubleshooting trace. The following table lists the main difference between these two.


Troubleshooting Traces

Minimal information, could miss relevant information

Lots of information, more than is needed to troubleshoot a specific problem

Apply filters

Turns on almost all trace options

Less system impact

Major system impact

Trace types include the following:

  • SDI

    Runtime events for the related software

    IP address

    Time stamp

    Device name

  • SDL

    Call processing from Unified Communications Manager and Cisco CTI Manager Services.

    Used by Cisco TAC engineers. Normal administrators provide this information to them only upon request.

  • Log4J

    Used for Java applications

To configure a trace, follow these steps:

  1. Select the server.
  2. Select the service group from the drop-down.
  3. Select the service.
  4. Check the trace boxes you want.
  5. Click Save.
  • + Share This
  • 🔖 Save To Your Account