Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Remote Syslog configuration, uses a syslog server to store a larger amount of log activity for extended period of time. Using a Remote Logging configuration is the recommended logging method since it allows for a greater logging history and level of detail. You must use this method of logging when working with Sonus Technical Support (TAC).
  • Local Log configuration (available only on the Sonus SBC 2000 chassis model, Ribbon SBC 1000 v2 equipped with eUSB, and SBC SWe Lite), stores temporary log files directly on the

    Spacevars
    0series2
     systemthe system. Each local log file retains a limited amount of recorded log messages. Local logging is only useful for quick, high level, troubleshooting, and is not recommended (nor suited) for extended troubleshooting sessions.

    Warning
    titleLocal Logging at Debug or Trace Level
    • Increasing the local log level of any subsystem to Debug or Trace levels should be performed only if requested by Sonus Technical Support (TAC).
    • After completing the collection of logs from the tests, all subsystems with custom log level must be reset to the Default local log level (Warning) or deleted.
    • Avoid performing this action on a production system.

 

Info

When troubleshooting Authentication or Authorization issues, you must apply the Authentication log profile. See Managing Subsystems Logging and Log Profiles for details.

 

A fully running

Spacevars
0product
 system can generate a large amount of logging information. For this reason, the
Spacevars
0product
 logging service allows you to customize the types of logging messages (and level of detail) you wish to be recorded by Managing Subsystems Logging and Log Profiles.

...