About Device Logs

Refer to the following sections for information about the log message types and format, log categories, logging levels, logging processes, and packet format for syslog output:

Standardized Logs

Standardized log messages can be streamed to GigaVUE‑FM. The log messages follow the industry standard described in RFC5424. The format includes structured data, timestamp, version, and message ID. The timestamp includes milliseconds for increased accuracy.

In GigaVUE‑FM, the log information is displayed in a table with configurable, sortable columns and extensive filter options. Refer to Viewing Device Logs for information about viewing and filtering logs in GigaVUE‑FM.

The following is an example of a standardized log message in the GigaVUE-OS CLI:

<173>1 2017-10-05T00:25:29.145Z TA40.flex.com peripd.NOTICE 2332 LINK [linkDown@26866 portId="1/1/q1"] Link change: 1/1/q1 is down with speed 40G and duplex full

The following table illustrates how to interpret the example:

Format

In this example:

<Facility+Severity>

<173>

Version

1

Timestamp

2017-10-05T00:25:29.145Z

Hostname

TA40.flex.com

Process-name

peripd.NOTICE

PID

2332

MSG-ID

LINK

[Structured-Data]

[linkDown@26866 portId="1/1/q1"]

MSG

Link change: 1/1/q1 is down with speed 40G and duplex full

Device Log Categories

The following table describes the categories in the device or cluster log messages based on the standardized log format:

Log Category

Description

GENERAL-ERR

Errors that are common across applications

HIGH-TEMPERATURE

High Temperature

PACKET DROP

Packet Drop

LINK

Link

INIT

Initialization

RESOURCE-UTIL

Resource Utilization

REQUEST

Query System Information

Device Log Message Types

The following table describes the types of log messages in the device or cluster based on the standardized log format:

Message Type

Description

memoryAllocError

Memory allocation error

memoryAccessError

Unexpected NULL access

fileAccessError

File access error

switchCpuHighTemperature

High Switch CPU Temperature

opticsHighTemperature

High Optics Temperature

caviumCpuHighTemperature

High Cavium CPU Temperature

ambientCpuHighTemperature

High Ambient CPU Temperature

exhaustCpuHighTemperature

High Exhaust CPU Temperature

egressPacketDrop

Packet Drop at Egress

ingressPacketDrop

Packet Drop at Ingress

linkChangeNotify

Link Change Notification

mgmtModule

Failed to load mgmt module

systemCpuUtil

High System CPU Utilization

systemMemoryUtil

High System Memory utilization

processCpuUtil

High CPU Consumption by a process

processMemoryUtil

High Memory Consumption by a process

processAccessError

Process access errors

systemAccessError

System access errors

queryFail

Failed to fetch system data

moduleInitFail

Failed to load a cli module

Device Logging Levels

The following table shows the standard logging levels that are used to rank logged events by degree of severity. When configuring the device/cluster logs to stream, the highest severity level will capture fewer logs than the lowest severity. For example, if the lowest level (info or debug) is selected in your configuration, all levels of logs, from the selected level up to the highest level, will be streamed. If the highest level (emergency) is selected, only emergency logs will be streamed.

Logging Level

Description

emergency

The system is unusable. The severity level with the least logging – only emergency level events/commands are logged.

alert

Action must be taken immediately.

critical

Critical condition.

error

error condition.

warning

Warning condition.

notice

Normal but significant condition.

info

Informational messages.

debug

Debug-level messages. Authorized for factory use only.

Device Logging Processes

Logs that are specific to a process are logged with the process ID. The following table provides a list of logging processes and their descriptions:

Logging Process

Description

acctd

AAA Accounting daemon

avd

Active Visibility daemon

cli

Command Line Interface

clusterd

Cluster daemon

debuggabilityd

Debuggability daemon

frm

Foreign Resource Manager

gsd

GigaSMART daemon

gprof

Profiler

httpd

HTTP daemon

licd

License daemon

mgmtd

Management daemon

ndiscd

Network Discovery daemon

netdevd

Netdev daemon

notf_mgr

Notification Manager

ntpd

Network Time Protocol daemon

peripd

Peripheral daemon

persistd

Persistence daemon

pm

Process Manager

ptpd

PTP Protocol daemon

restapid

REST API daemon

sched

Scheduler daemon

snmpd

SNMP daemon

statsd

Statistics daemon

syncd

Sync daemon

syshth

System Health

ugwd

Unified Gateway daemon

wizard

Wizard

wsmd

Web session Manager daemon

xd

XML Gateway

xinetd

Extended Internet Service daemon

Packet Format for Syslog Output

Syslog packets sent by the GigaVUE HC Series node to an external syslog server conform to the format recommended by RFC 3164 (but are not compatible with facility numerical code). Keep in mind the following about this packet format:

  • Severity indications in the packet’s PRI field are derived from corresponding event levels on the GigaVUE HC Series and GigaVUE TA Series nodes.
  • Timestamps are provided in Mmm dd hh:mm:ss format, where Mmm is the standard English language abbreviation of the month (for example, Jan, Feb, Mar).
  • Syslog packets include the IP address of the Mgmt port.