| Asset ID: |
1-71-1594428.1 |
| Update Date: | 2017-05-09 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1594428.1
:
Acme Packet: Log Types and Their Meaning
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Session Delivery Network>SN-SND: Acme Service Provider
|
In this Document
Applies to:
Acme Packet 4500 - Version S-Cx6.2.0 and later
Information in this document applies to any platform.
Goal
Log types and their meaning.
Solution
The log files are stored in the /ramdrv/logs directory on the Net-Net SD.
log.sysmand
This log contains information about the system manager task. This task is currently responsible for writing the system log (acmelog), dispatching commands to other application tasks, and starting the application-level code.
log.bootstrap
This log records information about the boot process as the Net-Net system becomes operational.
log.berpd
This log contains process logs for the berpd task or the redundancy health task. This file is primarily used for storing health messages and events and for determining whether a switchover is required.
log.brokerd
This log contains information about platform-level tasks. For example, when the ARP manager wants to log information in a place other than the console, it sends a message to log.brokerd. This is also true of the various host tasks related to communicating with the network processors and/or the CAM. This log also contains messages from the IP fragmenter, which currently takes part in the SIP NAT process. Brokerd forwards these messages through sysmand to the acmelog (the overall system log). Thus, log.brokerd contains a subset of the logs that acmelog contains.
log.lemd
This log refers to the local element manager (or local database server) processes. Information in log.lemd pertains to remote retrievals of and writing of configuration data.
log.algd
This log contains information pertaining to MGCP processing. It occasionally contains information about the SIP NAT function.
log.mbcd
This log contains information pertaining to the application flow manager, such as the creating, updating, and removing media NAT entries.
miboco.log
Tasks use MIBOCO protocol processing to communicate with the mbcd task. This log can be used to determine whether the mbcd has returned any error messages or other type of messages. It is possible that sipmsg.log and algd.log contain MIBOCO messages. However, the miboco.log is used infrequently because log.sipd and log.algd also report return codes from the mbcd.
log.radd
This log is used for the accounting daemon for RADIUS. It serves as a RADIUS client to the outside world.
However, it also serves as a place to concentrate RADIUS records from various signaling protocol tasks running on the Net-Net SD. Its logs reflect the latter function.
log.h323d
This log contains information pertaining to H.323 tasks.
log.sipd
This log contains information pertaining to the SIP processing task. The log contains information about how the Net-Net system’s SIP daemon is processing messages.
sipmsg.log
A protocol trace log that contains information about SIP messages that have been received, NAT’d, and sent by the SIP daemon. MIBOCO messages sent and received by the sipd process are also contained in this log.
log.acli
This log contains information pertaining to ACLI processing.
log.acliConsole
This log contains information about ACLI console functions.
log.acliTelnet(0-4)
This log contains information about ACLI Telnet sessions if your system access method is Telnet. You can have one log for each instance.
log.SSH(0-4)
This log contains information about SSH processes. You can have one log for each instance.
log.tCliWorker
This log contains information about tCliWorker processes.
Attachments
This solution has no attachment
