Skip to main content
Cisco SD-WAN
Support
Product Documentation
Viptela Documentation

Use Syslog Messages

On Viptela devices, you can log event notification system log (syslog) messages to files on the local device or on a remote host. On the local device, syslog files are placed in the /var/log directory.

Configure System Logging

Logging syslog messages with a priority level of "information," to the local device's hard disk, is enabled by default. Log files are placed in the local /var/log directory. By default, log files are 10 MB in size, and up to 10 files are stored. After 10 files have been created, the oldest one is discarded to create a file for newer syslog messages.

To modify the default syslog parameters from vManage NMS, use the Logging feature template. From the CLI, include the logging disk or logging server command in the device configuration.

Display Syslog Logging Information

In vManage NMS, to display the contents of a device's syslog files:

  1. In the Administration ► Settings screen, ensure that Data Stream is enabled.
  2. From the Monitor ► Network screen, select the vEdge router.
  3. Click Troubleshooting in the left pane.
  4. From the Logs pane, click Debug Log.
  5. In the Log Files field, select the name of the log file. The lower part of the screen displays the log information.

To display the contents of a syslog file from the CLI, use the show log command. For example:

vEdge# show log auth.log tail 10
==> /var/log/auth.log <==
auth.info: Nov 14 14:33:35 vedge sshd[2570]: Accepted publickey for admin from 10.0.1.1 port 39966 ssh2: RSA SHA256:pkFQ5wE//DmiA0d0JU1rOt91CMTVGkscm9wLSYQrI1s
auth.info: Nov 14 14:39:42 vedge sshd[2578]: Received disconnect from 10.0.1.1 port 39966:11: disconnected by user
auth.info: Nov 14 14:39:42 vedge sshd[2578]: Disconnected from 10.0.1.1 port 39966
auth.info: Nov 16 10:51:45 vedge sshd[6106]: Accepted publickey for admin from 10.0.1.1 port 40012 ssh2: RSA SHA256:pkFQ5wE//DmiA0d0JU1rOt91CMTVGkscm9wLSYQrI1s
auth.info: Nov 16 11:21:55 vedge sshd[6108]: Received disconnect from 10.0.1.1 port 40012:11: disconnected by user
auth.info: Nov 16 11:21:55 vedge sshd[6108]: Disconnected from 10.0.1.1 port 40012
auth.info: Nov 17 12:59:52 vedge sshd[15889]: Accepted publickey for admin from 10.0.1.1 port 40038 ssh2: RSA SHA256:pkFQ5wE//DmiA0d0JU1rOt91CMTVGkscm9wLSYQrI1s
auth.info: Nov 17 13:45:13 vedge sshd[15894]: Received disconnect from 10.0.1.1 port 40038:11: disconnected by user
auth.info: Nov 17 13:45:13 vedge sshd[15894]: Disconnected from 10.0.1.1 port 40038
auth.info: Nov 17 14:47:31 vedge sshd[30883]: Accepted publickey for admin from 10.0.1.1 port 40040 ssh2: RSA SHA256:pkFQ5wE//DmiA0d0JU1rOt91CMTVGkscm9wLSYQrI1s

To display the configured system logging settings for a device, use the show logging command from the CLI. For example:

vEdge# show logging

System logging to  in vpn 0 is disabled
Priority for host logging is set to: info

System logging to disk is enabled
Priority for disk logging is set to:  info
File name for disk logging is set to:  /var/log/vsyslog
File size for disk logging is set to:  10 MB
File recycle count for disk logging is set to:  10

Syslog facility is set to: local7

System Log Files

Syslog messages at or above the default or configured priority value are recorded in a number of files in the /var/log directory on the local device. These files include the following:

  • auth.log—Login, logout, and superuser access events, and usage of authorization systems.​
  • kern.log—Kernel messages.
  • messages—Consolidated log file that contains syslog messages from all sources.
  • vconfd—All configuration-related syslog messages.
  • vdebug—All debug messages for modules whose debugging is turned on and all syslog messages above the configured priority value. Debug logging supports various levels of logging based on the module. Different modules implement the logging levels differently. For example, the system manager (sysmgr) has two logging levels (on and off), while the chassis manager (chmgr) has four different logging levels (off, low, normal, and high). You cannot send debug messages to a remote host. To enable debugging, use the debug operational command.
  • vsyslog—All syslog messages from Viptela processes (daemons) above the configured priority value. The default priority value is "informational" (severity level 6), so by default, all "notice", "warning", "error", "critical", "alert", and "emergency" syslog messages (severity levels 5 through 0, respectively) are saved.

The Viptela software does not use the following standard LINUX files, which are present in /var/log, for logging: cron.log, debug, lpr.log, mail.log, and syslog.

The writing of messages to syslog files is not rate-limited. This means that if many syslog messages are generated in a short amount of time, the overflow messages are buffered and placed in a queue until they can be written to a syslog file. The overflow messages are not dropped.

For repeating syslog messages—identical messages that occur multiple times in succession—only one copy of the message is placed in the syslog file. The message is annotated to indicate the number of times that the message occurred.

The maximum length of a syslog message is 1024 bytes. Longer messages are truncated.

Syslog messages related to AAA authentication and Netconf CLI access and usage are placed in the auth.log and messages files. Each time a vManage NMS logs in to a vEdge router to retrieve statistics and status information and to push files to the router, the router generates AAA and Netconf log messages. So, over time, these messages can fill the log files. To prevent these messages from filling the log files, you can disable the logging of AAA and Netconf syslog messages:

Viptela(config)# system aaa logs
Viptela(config-logs)# audit-disable
Viptela(config-logs)# netconf-disable

Syslog Message Format

Syslog message generated by the Viptela software have the following format:

facility.source date - source - module - level - MessageID: text-of-syslog-message

Here is an example of a syslog message. In the file, this message is on a single line. This message has the facility name of local7, which is the name used for all Viptela processes, and a priority of "info".

local7.info: Apr  3 13:40:31 vsmart SYSMGR[221]:
%Viptela-vsmart-sysmgrd-6-INFO-1400002:
Notification : 4/3/2017 20:40:31 system-login-change severity-level:minor host-name:"vm1" system-ip:172.16.255.11 user-name:"admin" user-id:162 

Syslog Message Acronyms

The following Viptela-specific acronyms are used in syslog messages and in the explanations of the messages:

Acronym Meaning
confd CLI configuration process
FTM Forwarding table manager
FP Forwarding process
RTM Route table manager
TTM Tunnel table manager

Syslog Messages

The tables below list the syslog messages generated by Viptela devices. The messages are grouped based on the software module that generates them. The software modules are typically processes (daemons) that run on the Viptela device.

All syslog messages are generated on all Viptela devices unless otherwise indicated.

In these tables, the Action field indicates the recommended action you should take in response to the syslog message:

  • A—Automatically open a ticket in your organization's support team.
  • AE—Automatically open a support ticket and escalate the ticket
  • E—Send email to the appropriate team within your organization.

If you see a syslog message that is not listed in one of the tables below, please send the message, along with the Viptela device and software version, to docs@viptela.com.

CFGMGR: Configuration Manager

Priority: Informational

Message Message Format Description Action
CFGMGR_SYSLOG_END Terminating cfgmgr

Configuration manager is stopping

E
CFGMGR_SYSLOG_IF_STATE

VPN %lu Interface %s %s, vpn_id, user_ifname, if_state_up?"UP":"DOWN"

Interface state changed to up or down

E

CFGMGR_SYSLOG_START

Starting cfgmgr

Configuration manager is starting E

CFLOWD: Cflowd Traffic Flow Monitoring

Priority: Informational

Message Message Format Description Action
CFLOWD_SYSLOG_MSG

Received information about vpn_id %ld, vpn_id

Cflowd detected a VPN change

E

Priority: Notice

Message Message Format Description Action
CFLOWD_SYSLOG_END

Terminating module cflowd because of sysmgr abort

Cflowd module going down at request of sysmgr

E

CFLOWD_SYSLOG_END

Terminating module cflowd with error code %d, err

Cflowd initialization failed and cflowd is about to go down, or cflowd module is going down A
CFLOWD_SYSLOG_START Starting module cflowd Cflowd module is starting  

CHMGR: Chassis Manager

The chassis manager process runs only on hardware vEdge routers.

Priority: Informational

Message Message Format Description Action

CHMGR_CHASSIS_INFO

Chassis-Type %s max-modules %d, chassis-type, max-modules

Informational message indicating chassis type and maximum number of modules (PIMs + fixed) supported by chassis

E

CHMGR_FANTRAY_INSERTED

Fantray %d inserted, p_fantray->id

Fan tray inserted (on vEdge 2000 only) E

CHMGR_FANTRAY_REMOVED

Fantray %d removed, p_fantray->id

Fan tray removed (on vEdge 2000 only) E

CHMGR_MODULE_INSERTED

Module %d inserted - port type: %s, num_ports: %s, module_id, port-type-str, num-ports

PIM module inserted E

CHMGR_MODULE_REMOVED

Module %d removed, p_mod->module_id

PIM module removed E

CHMGR_PORT_INSERTED

Port %s inserted in module %d,

SFP inserted E

CHMGR_PORT_REMOVED

Port %s removed from module %d,

SFP removed E
CHMGR_SIGTERM

Received sigterm, exiting gracefully

Debug-level message indicating that chassis manager is going down E
CHMGR_USB_INSERTED

USB media inserted in slot %d, id

USB media inserted E
CHMGR_USB_REMOVED

USB media removed from slot %d, id

USB media removed E

Priority: Notice

Message Message Format Description Action
CHMGR_EMMC_OK

eMMC read successful

EMMC read was successful E
CHMGR_FAN_OK

Fan Tray %d Fan %d fault cleared, ftrayid, id

Fan fault cleared E
CHMGR_FANTRAY_OPER

Fan tray '%d' up, ftrayid

Fan tray detected A
CHMGR_FLASH_OK

Flash memory status read successful

Flash read successful E
CHMGR_PEM_OK

Power supply '%d' fault cleared, id);

Power supply fault cleared E
CHMGR_PEM_OPER

Power supply '%d' up, id);

Power supply inserted or detected E
CHMGR_TEMP_GREEN

%s temperature (%d degrees C) is below yellow threshold (%d degrees C),

Temperature sensor reading below yellow threshold E
CHMGR_TEMP_OK

%s temperature sensor fault cleared, p_tempsensor->name);

Temperature sensor read successful after a previous failed attempt E

Priority: Warning

Message Message Format Description Action

CHMGR_HOTSWAP_DIFF_MOD

Hot-Insertion of a module of different type requires reboot. Module %d will remain down,

PIM module of a different type was inserted in the slot; it was detected, but will remain down until the next reboot

E

Priority: Error

Message Message Format Description Action

CHMGR_CONFD_DATACB_REGISTER_FAILED

Failed to register data cb Internal error registering a data callback function with confd AE

CHMGR_CONFD_REPLY_FAILED

Failed to send oper data reply - %s (%d)

Internal error occurred when processing chassis manager–related configuration of show command A

CHMGR_EEPROM_READ_FAILED

Failed to read module %d eeprom on chassis %s, module, chassis-name

Failed to read details of inserted PIM AE

CHMGR_EEPROM_VERSION_ERROR

Unsupported eeprom format version for module %d

EEPROM version of PIM module is supported; module will not be recognized AE

CHMGR_EMMC_FAULT

eMMC fault detected Error occurred reading EMMC information A

CHMGR_FAN_FAULT

Fan Tray %d Fan %d fault detected, ftrayid, id

Fan fault detected A

CHMGR_FANTRAY_DOWN

Fan tray '%d' not present, ftrayid id

Fan tray not detected A

CHMGR_FLASH_FAULT

Flash memory status fault Internal error reading flash AE

CHMGR_GET_HWADDR_FAILED

Failed to get macaddr for %s, p_ifname

Internal error resulting from failure to obtain an interface's MAC address A

CHMGR_GET_IFFLAG_FAILED

Failed to get ifflags for %s err %d, p_port->kernel_name, errno

Interface initialization failure; interface may remain down, or device may reboot A

CHMGR_PEM_DOWN

Power supply '%d' down or not present, id);

Power supply removed or not detected A

CHMGR_PEM_FAULT

Power supply '%d' fault detected, id);

Power supply fault detected AE

CHMGR_PIM_FAULT

PIM %d power fault, module_id);

PIM power fault detected AE
CHMGR_PIM_FAULT

PIM %d power fault cleared, module_id);

PIM power fault cleared A

CHMGR_SET_IFFLAG_FAILED

Failed to set ifflags to %x for %s err %d, ifr.ifr_flags,

Interface initialization failure; interface may remain down, or device may reboot A

CHMGR_SPURIOUS_TIMER

Spurious timer ignored what = %#x arg = %p, what, chmgr

Internal error A

CHMGR_SYSOUT_OF_RESOURCES

Timer add failed. Out of resources

Interal error; if fatal, device may reboot to recover A

CHMGR_UNKNOWN_MODULE_TYPE

Invalid module-type %x in module-slot %d on chassis %s,

Unrecognized PIM module type in slot AE

CHMGR_UNSUPPORTED_MODULE_TYPE

Module-Type %s not supported in slot %d on chassis %s

PIM module is not supported in slot in which it is inserted A

Priority: Critical

Message Message Format Description Action
CHMGR_IF_RENAME_FAILED

Unable to rename %s to %s,

Interface initialization failed; interface may remain down or the device may reboot A
CHMGR_TEMP_FAULT

%s temperature sensor fault detected. Unable to read temperature, tempsensor-name

Failed to read from a temperature sensor; possible temperature sensor failure A
CHMGR_TEMP_RED

%s temperature (%d degrees C) is above red threshold (%d degrees C).

Temperature sensor reading above red threshold AE
CHMGR_TEMP_YELLOW

%s temperature (%d degrees C) is above yellow threshold (%d degrees C),

Temperature sensor reading above yellow threshold A

Priority: Alert

Message Message Format Description Action
CHMGR_CONFD_INIT_FAILED

Initialization failed. vconfd_module_init returned %d, status

Chassis manager failed to initialize and start

AE

DHCPC: DHCP Client

The DHCP client process runs only on vEdge routers.

Priority: Informational

Message Message Format Description Action

DHCP_SYSLOG_CLEAR_INTERFACE

Clearing dhcp state for interface %s,

DHCP client cleared DHCP state for interface

E

DHCP_SYSLOG_DISCOVER_TIMEOUT

No response for dhcp discover packets for interface %s, DHCP discovery failure E

DHCP_SYSLOG_IP_ADDR_ASSIGNED

Assigned address %s to interface %s, DHCP client assigned address to interface E

DHCP_SYSLOG_IP_ADDR_RELEASED

Released address for interface %s, entry_p->user_if_name);

DHCP client released address E

DHCP_SYSLOG_IP_ADDR_REQUEST_RENEW

Requesting renew [50%%] for interface %s address %s/%d,

DHCP client renewal request at 50% of lease expiration time E

DHCP_SYSLOG_IP_ADDR_REQUEST_RENEW

Requesting renew [85%%] for interface %s address %s/%d,

DHCP client renewal request at 85% of lease expiration time E

DHCP_SYSLOG_IP_ADDR_REQUEST_RENEW

Requesting renew [100%%] for interface %s address %s/%d,

DHCP client renewal request at 100% of lease expiration time E

Priority: Critical

Message Message Format Description Action

DHCP_SYSLOG_IP_ADDR_CONFLICT

Interface %s IP Address %s conflict with interface %s,

DHCP client detected IP address conflict with another interface

E

DHCPS: DHCP Server

The DHCP server process runs only on vEdge routers.

Priority: Informational

Message Message Format Description Action

DHCP_SYSLOG_CLEAR_SERVER_BINDINGS

Clearing dhcp server bindings for interface %s, vpn %ld,

DHCP server cleared bindings for interface E

DHCP_SYSLOG_CLEAR_SERVER_BINDINGS

Clearing dhcp server binding for interface %s, vpn %ld, mac addr %x:%x:%x:%x:%x:%x,

DHCP server cleared bindings for interface E

FTMD: Forwarding Table Management Process

The forwarding table management process runs only on vEdge routers.

Priority: Informational

Message Message Format Description Action
FTMD_SYSLOG_BFD_STATE

record with discriminator %u invalid

BFD state is invalid E
FTMD_SYSLOG_BFD_STATE

BFD Session %s.%u->%s.%u %s:%u->%s:%u %s %s %s %d\n,

BFD state changed

E

FTMD_SYSLOG_ROUTE_ADD_FAIL

Route Add for prefix %s Failed. Reason %s\n,

FTM failed to add a route received from the RTM E

FTMD_SYSLOG_FIB_GROW

Growing FIB6 memory to accommodate larger tables): IPv6 forwarding table size is being increased E

FTMD_SYSLOG_FIB_GROW

Growing FIB memory to accommodate larger tables): IPv4 forwarding table size is being increased E
FTMD_SYSLOG_SIGTERM

Received Cleanup signal. Exiting gracefully\n);

FTM received termination signal from sysmgr and is about to go down E
FTMD_SYSLOG_IF_STATE

VPN %lu Interface %s %s,

FTM detected interface state change E
FTMD_SYSLOG_TUNNEL_ADD_FAIL

Tunnel Add to TLOC %s.%s Failed. Reason %s\n,

Failed to add new TLOC; reported by TTM E

Priority: Notice

Message Message Format Description Action

FTMD_SYSLOG_FP_CORE_FAIL

FP core watchdog expired (rc = %d). %s, rc, action_str);

FTM detected that FP may not be functioning; device will reboot soon A

FTMD_SYSLOG_PMTU_LOWERED

Tunnel %s/%d -> %s/%d MTU Changed to %u due to Path-MTU Discovery,

MTU size on a tunnel changed due to path MTU discovery E

Priority: Warning

Message Message Format Description Action

FTMD_SYSLOG_TTM_DOWN

Connection to TTM went down. p_msgq %p p_ftm %p,

FTM connection with TTM went down; BFD sessions will be cleared E

FTMD_SYSLOG_TTM_UP

Connection to TTM came up. p_msgq %p p_ftm %p,

FTM connected with TTM  

Priority: Error

Message Message Format Description Action

FTMD_SYSLOG_CONFD_FAIL

Failed to register bfd show data cb

FTM failed to register data callback wtih confd; device may reboot AE

FTMD_SYSLOG_CONFD_FAIL

Failed to register policer show data cb

FTM failed to register data callback with confd; device may reboot AE

FTMD_SYSLOG_CONFD_FAIL

%s: Failed to register data cb, __FUNCTION__ );

FTM failed to register data callback with confd; device may reboot AE

FTMD_SYSLOG_CONFD_FAIL

%s: Failed to send oper data reply - %s (%d) : %s,

FTM failed to respond correctly to confd; some show commands may not work

A

FTMD_SYSLOG_FP_COREDUMP

FP Core %d Died. Core file recorded at %s,

FTM detected an FP crash; device will reboot soon AE
FTMD_SYSLOG_RTM_DECODE_FAIL

Bad RTM Msg: Msg-Type %u Msg-Len %u len: %u decoded-len %u,

Could not process route or interface change message from RTM A
FTMP_SYSLOG_SPURIOUS_TIMER

Spurious timer ignored what = %#x arg = %p,

Internal error A

OMP: Overlap Management Protocol

Priority: Informational or Other

Message Message Format Description Action
OMP_NUMBER_OF_VSMARTS Number of vSmarts connected: %u Number of vSmart controllers to which device is connected (on vEdge routers only) E

OMP_PEER_STATE_CHANGE

%s peer %s state changed to %s,

OMP peer stated changed to up or down E
OMP_POLICY_CHANGE Using policy from peer %s, Forwarding policy received from vSmart controller (on vEdge routers only) E
OMP_STATE_CHANGE Operational state changed to %s, OMP internal operational state changed E

OMP_TLOC_STATE_CHANGE

TLOC %s state changed to %s for address-family: %s,

TLOC state changed E

SYSMGR: System Manager

The system manager process (daemon) spawns, monitors, and terminates all the processes in the system, and it collects and logs vital system information, such as memory and CPU status.

Priority: Informational

Message Message Format Description Action

SYSMGR_CONFD_PHASE1_INFO

Generated authorized keys on %s, p_sysmgr->cfg.my_personality);

Generated authorized keys for SSH-based login between vManage server and Viptela device

E

SYSMGR_CONFD_PHASE2_SUCCESS

Confd Phase2 UP

Successful device bringup E

SYSMGR_DAEMON_START

Started daemon %s @ pid %d in vpn %lu,

System manager started process in VPN E

SYSMGR_DAEMON_UP

Daemon %s @ pid %d came up in vpn %lu (%d %d)\n,

Daemon started by system manager came up as expected E

SYSMGR_SIGTERM

Received sigterm, stopping all daemons except confd

System manager received termination signal and will initiate termination of all processes E

SYSMGR_VPN_DESTROY

vpn %lu destroy. lookup returned %p\n, vpn_id, p_vpn);

Stopping all processes in VPN E

Priority: Notice

Message Message Format Description Action
SYSMGR_CLOCK_SET

System clock set to %s\n, asctime(&tm));

System clock set by user E

SYSMGR_CONFD_CDB_NOT_INITED

Confd db initialization not complete. Deleting cdb and starting afresh.

First-time initialization of configuration database E

SYSMGR_CONFD_PHASE1_INFO

Install successfully completed from %s to %s, prev_ver_buf, curr_ver_buf);

Failed to read installation ID; will fall back to default E

SYSMGR_DISK_ALERT_OFF

Disk usage is below 60%%.

Disk usage is below threshold E

SYSMGR_MEMORY_ALERT_OFF

System memory usage is below 50%%);

System memory usage is below 50% E

SYSMGR_REBOOT

System going down for a reboot.. (%s), reason);

System manager initiating a device reboot, possibly because of a process failure E
SYSMGR_SHM_FAIL

Created shared memory %s, VCONFD_SHM_NAME);

Successfully initialized shared memory for communication with other processes E
SYSMGR_SHUTDOWN

System shutting down.. (%s), reason);

System manager is powering down the device; device will not come back up unless it is physically power-cycled A
SYSMGR_SYSTEM_GREEN

System up with software version '%s',

System status is green, indicating that all processes came up as expected E
SYSMGR_SYSTEM_RED

System status red (software version '%s'),

System status is red, possibly because of a process failure A
SYSMGR_SYSTEM_START

Starting system with viptela software version '%s',

System has stated; usually one of the first messages during device bringup E
SYSMGR_TIMEZONE_SET

System timezone changed from '%s' to '%s'\n,

System timezone changed as result of configuration change E

Priority: Warning

Message Message Format Description Action

SYSMGR_DAEMON_STOP

Stopping daemon %s @ pid %d. Sending signal %d,

System manager stopped a daemon E

SYSMGR_DISK_ALERT_ORANGE

Disk usage is above 75%%. Please clean up unnecessary files.);

Disk usage is above 75% E

SYSMGR_DISK_ALERT_YELLOW

Disk usage is above 60%%. Please clean up unnecessary files.);

Disk usage is above 60% E

SYSMGR_MEMORY_ALERT_ORANGE

System memory usage is above 75%%);

System memory usage is above 75% E

SYSMGR_MEMORY_ALERT_YELLOW

System memory usage is above 60%%);

System memory usage is above 60% E

Priority: Error

Message Message Format Description Action

SYSMGR_BAUD_RATE_SET

Console baud rate changed to '%d', baud_rate);

Console baud rate changed E

SYSMGR_BAUD_RATE_SET_FAIL

Failed to set console baud rate in OS to '%d'

Failed to set user-specified console baud rate in Linus A

SYSMGR_BAUD_RATE_SET_FAIL

Failed to set console baud rate in U-boot to '%d'

Failed to set user-specified console baud rate in Uboot A

SYSMGR_CONFD_CDB_INIT_OPEN_FAIL

Failed to open cdb init file (%s) Failed to open the configuration database A

SYSMGR_CLOCK_SET_FAIL

Cannot set system clock to %s Failed to set system clock to time specified by user

A

SYSMGR_CONFD_DATACB_REGISTER_FAIL

Failed to register data cb);

Failed to register data callback function with confd; device may reboot A

SYSMGR_CONFD_CDB_DEL_FAIL

Failed to remove cbd directory '%s' Failed to reinitialize configuration database to recover from failure AE

SYSMGR_CONFD_FORK_FAILURE

Cannot move confd to phase2 (err %s)\n, strerror(errno));

Failed to move confd to Phase 2; device will reboot soon A
SYSMGR_CONFD_PHASE1_FAILURE Failed to generate archive keys Failed to generate keys required for archiving configuration E
SYSMGR_CONFD_PHASE1_FAILURE

Failed to generate authorized keys on %s, p_sysmgr->cfg.my_personality);

Failed to generate keys required for SSH-based login between vManage server and Viptela device

E
SYSMGR_CONFD_PHASE1_FAILURE Failed to generate SSH keys for archive); Failed to generate SSH keys E

SYSMGR_CONFD_PHASE1_FAILURE

Failed to get install id from file, using 00_00);

Failed to read previous system version A
SYSMGR_CONFD_PHASE1_FAILURE

Failed to get previous version, using 0.0);

Failed to read system version A
SYSMGR_CONFD_PHASE1_FAILURE

Failed to transition confd to phase1. Re-initializing CDB..

Confd module failed to move to Phase 1, indicating a possible configuration database failure; device will reboot soon

A

SYSMGR_CONFD_PHASE1_FAILURE Verified that archive keys exist Verified that configuration archive keys exist A
SYSMGR_CONFD_PHASE2_FAILURE

Failed to get current version, using 0.0);

Failed to read system version file A
SYSMGR_CONFD_PHASE2_FAILURE

Failed to open %s, version_file

Failed to open system version file A
SYSMGR_CONFD_PHASE2_FAILURE

Failed to read %s, version_file);

Failed to read system version file A
SYSMGR_CONFD_PHASE2_FAILURE

Failed to transition confd to phase2

Confd module failed to move to Phase 2, indicating a possible configuration database failure; device will reboot soon A

SYSMGR_CONFD_REPLY_FAIL

Failed to send oper data reply - %s (%d)

Failed to reply to confd; some show commands may not work A

SYSMGR_DAEMON_DOWN

Daemon %s [%u] went down in vpn %lu,

Process started by system manager went down A

SYSMGR_DAEMON_EXECV_FAILURE

execv %s failed Internal failure occurred while starting a process A

SYSMGR_DAEMON_FORK_FAILURE

Cannot start daemon %s: %s Internal failure occurred while starting a process A

SYSMGR_DAEMON_INACTIVE

Daemon %s[%lu] @ pid %d died. Rebooting device..,

System manager detected a process failure and is about to reboot the device A

SYSMGR_DAEMON_MSGQ_FAILURE

Could not start msgq to daemon %s. err %d,

Failed to establish message queue with process; device may reboot soon A

SYSMGR_DAEMON_MSGQ_FAILURE

Could not start msgq to quagga daemon %s. err %d,

Failed to establish message queue with routing process; device may reboot soon A

SYSMGR_DAEMON_SETPGID_FAILURE

setpgid(0,0) failed Internal failure setting process group of a process A

SYSMGR_DAEMON_STOPPED

Daemon %s @ pid %u terminated - %s

Daemon started by system manager terminated; device may reboot soon (except for vBond orchestrator)

A

SYSMGR_RTC_CLOCK_SET_FAIL

Cannot set hardware clock to %s - %s (errno

Failed to update hardware clock to system time specified by user

A

SYSMGR_SHM_FAIL

Failed to close shared memory %s with an error %d, VCONFD_SHM_NAME, errno);

Failed to completely and properly close the shared memory for communication with other processes E
SYSMGR_SHM_FAIL

Failed to map shared memory %s, VCONFD_SHM_NAME);

Failed to initialize shared memory for communication with other processes E
SYSMGR_SHM_FAIL

Failed to open shared memory %s with an error %d, VCONFD_SHM_NAME, errno);

Failed to open shared memory for communication with other processes E
SYSMGR_SHM_FAIL

Failed to truncate shared memory %s with an error %d, VCONFD_SHM_NAME, errno);

Failed to initialize shared memory for communication with other processes E
SYSMGR_SHM_FAIL

Failed to unmap shared memory %s, VCONFD_SHM_NAME);

Failed to completely and properly close shared memory for communication with other processes E

SYSMGR_SWITCHBACK_FAILED

Software upgrade to version '%s' failed because of

Software upgrade failed A

SYSMGR_TIMEZONE_SET_FAIL

Failed to set system timezone to '%s' (rc = %d)\n,

Failed to set system timezone to timezone specified by user A

Priority: Critical

Message Message Format Description Action

SYSMGR_CONFD_INIT_FAIL

Confd exited with error code %d,

System manager detected a confd process failure; device may reboot AE

SYSMGR_DISK_ALERT_RED

Disk usage is above 90%% (critically high). Please clean up unnecessary files.);

Disk usage is above 90% AE

SYSMGR_MEMORY_ALERT_RED

System memory usage is above 90%% (critically high));

System memory usage is above 90% AE

SYSMGR_REBOOT_HALTED

Reboot (reason

System manager stopped short of rebooting the device because it detected too many reboots in a short period of time

AE

SYSMGR_UPGRADE_FAILED

Software upgrade to version '%s' failed because of

Software upgrade failed AE

VDAEMON: Viptela Software Process

Priority: Informational

Message Message Format Description Action

VDAEMON_SYSLOG_DOMAIN_ID_CHANGE

System Domain-ID changed from '%d' to '%d',

System domain ID changed

E

VDAEMON_SYSLOG_ORG_NAME_CHANGE

System Organization-Name changed from '%s' to '%s'

System organization name changed E

VDAEMON_SYSLOG_PEER_STATE

Peer %s Public-TLOC %s Color %u %s,

Peer state changed to up or down E

VDAEMON_SYSLOG_SITE_ID_CHANGE

System Site-ID changed from '%d' to '%d'

System site ID changed E

VDAEMON_SYSLOG_SYSTEM_IP_CHANGE

System-IP changed from '%s' to '%s'

System IP address changed E

Priority: Error

Message Message Format Description Action

VDAEMON_SYSLOG_PEER_AUTH_FAIL

Peer %s Public-TLOC %s Color %u %s,

Authentication with a vdaemon peer failed

E

VDAEMON_SYSLOG_PEER_STATE

Failed to read system host name

Internal error reading system hostname; device will not register with vManage server or ZTP will fail

A

VRRP: Virtual Router Redundancy Protocol

The VRRP process runs only on vEdge routers.

Priority: Informational

Message Message Format Description Action
VRRPD_STATE_CHANGE

Group %d, interface %s, vpn %lu state changed to %s, group-id, group-if-name, group-vpn-id, vrrp-group-state-string

VRRP interface state change

E

Additional Information

See the Configuring System Logging article for your software release.

  • Was this article helpful?