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

Use Syslog Messages

When something of interest happens on an individual device in the overlay network, the device reports the event in the following ways:

  • Send a notification to the vManage NMS. The vManage NMS filters the event notifications and correlates related events, and it consolidates major and critical events into alarms.
  • Send an SNMP trap to the configured trap target. For each SNMP trap that a device generates, the device also generates a corresponding notification message.
  • Generate a system logging (syslog) message and place it in a syslog file in the /var/log directory on the local device and, if configured, on a remote device.

On SD-WAN devices, you can log event notification system log (syslog) messages to files on the local device or on a remote host, or both. 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.

Each syslog message has a corresponding number. The tables list all syslog messages and their number even if the messages are defined in the header files but are not currently used in the operating software. For these messages, the Message Format, Description, and Action fields are empty.

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 Process

Priority: Informational

Message Number Message Format Description Action
CFGMGR_SYSLOG_END 399999 Terminating cfgmgr

Configuration manager is stopping

E
CFGMGR_SYSLOG_SPEED_DUPLEX_NOT_SUPPORTED 300003 Interface does not support duplex mode E
CFGMGR_SYSLOG_SPURIOUS_TIMER 300002 Internal error A
CFGMGR_SYSLOG_IF_STATE 300004

Interface state reported by configuration manager E

CFGMGR_SYSLOG_START

300001

Starting cfgmgr

Configuration manager is starting E

CFLOWD: Cflowd Traffic Flow Monitoring Process

Priority: Informational

Message Number Message Format Description Action
CFLOWD_SYSLOG_MSG 2200002

Received information about vpn_id %ld, vpn_id

Cflowd detected a VPN change

E

Priority: Notice

Message Number Message Format Description Action
CFLOWD_SYSLOG_END 2299999

Terminating module cflowd because of sysmgr abort

Cflowd module going down at request of sysmgr

E

CFLOWD_SYSLOG_END

2299999

Terminating module cflowd with error code %d

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

CHMGR: Chassis Manager

The chassis manager process runs only on hardware vEdge routers.

Priority: Informational

Message Number Message Format Description Action

CHMGR_CHASSIS_INFO

100009

Chassis-Type %s max-modules %d

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

E

CHMGR_FAN_SPEED_HIGH

100003 Fan speed is high

E

CHMGR_FAN_SPEED_NORMAL 100004 Fan speed is normal E

CHMGR_FANTRAY_INSERTED

100052

Fantray %d inserted

Fan tray inserted (on vEdge 2000 only) E

CHMGR_FANTRAY_REMOVED

100053

Fantray %d removed

Fan tray removed (on vEdge 2000 only) E

CHMGR_MODULE_INSERTED

100007

Module %d inserted - port type: %s, num_ports: %s

PIM module inserted E

CHMGR_MODULE_REMOVED

100008

Module %d removed

PIM module removed E
CHMGR_PIM_OK 100057 PIM module status is normal E

CHMGR_PORT_INSERTED

100005

Port %s inserted in module %d

SFP inserted E

CHMGR_PORT_REMOVED

100006

Port %s removed from module %d

SFP removed E
CHMGR_SIGTERM 100024

Received sigterm, exiting gracefully

Debug-level message indicating that chassis manager is going down E
CHMGR_SYSLOG_START 100001 Starting chassis manager Chassis manager process is starting E
CHMGR_USB_INSERTED 100058

USB media inserted in slot %d

USB media inserted E
CHMGR_USB_REMOVED 100059

USB media removed from slot %d

USB media removed E

Priority: Notice

Message Number Message Format Description Action
CHMGR_EMMC_OK 100039

eMMC read successful

EMMC read was successful E
CHMGR_FAN_OK 100041

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

Fan fault cleared E
CHMGR_FANTRAY_OPER 100055

Fan tray '%d' up, ftrayid

Fan tray detected A
CHMGR_FLASH_OK 100037

Flash memory status read successful

Flash read successful E
CHMGR_PEM_OK 100043

Power supply '%d' fault cleared

Power supply fault cleared E
CHMGR_PEM_OPER 100045

Power supply '%d' up

Power supply inserted or detected E
CHMGR_SDCARD_OK 100047 SD card read successful SD card read successful E
CHMGR_SFP_UNSUPPORTED 10060 SFP %s is not supported SFP is not supported E
CHMGR_SHORT_RESET_REQUEST 100018 Chassis manager received a request to reboot the router E
CHMGR_TEMP_GREEN 100030

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

Temperature sensor reading below yellow threshold E
CHMGR_TEMP_OK 100027

%s temperature sensor fault cleared

Temperature sensor read successful after a previous failed attempt E

Priority: Warning

Message Number Message Format Description Action

CHMGR_HOTSWAP_DIFF_MOD

100051

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 Number Message Format Description Action

CHMGR_CONFD_DATACB_REGISTER_FAILED

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

CHMGR_CONFD_REPLY_FAILED

100022

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

100011

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

Failed to read details of inserted PIM AE

CHMGR_EEPROM_VERSION_ERROR

100012

Unsupported eeprom format version for module %d

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

CHMGR_EMMC_FAULT

100038 eMMC fault detected Error occurred reading EMMC information A

CHMGR_FAN_FAULT

100040

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

Fan fault detected A

CHMGR_FANTRAY_DOWN

100054

Fan tray '%d' not present, ftrayid id

Fan tray not detected A

CHMGR_FLASH_FAULT

100036 Flash memory status fault Internal error reading flash AE

CHMGR_GET_HWADDR_FAILED

100010

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

100016

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_IFFLAGS_SET_FAIL 100050 Setting an interface flag failed E
CHMGR_IF_GSO_OFF_FAILED 100025 Setting interface options failed E

CHMGR_PEM_DOWN

100044

Power supply '%d' down or not present

Power supply removed or not detected A

CHMGR_PEM_FAULT

100042

Power supply '%d' fault detected

Power supply fault detected AE

CHMGR_PIM_FAULT

100056

PIM %d power fault

PIM power fault detected AE
CHMGR_PIM_FAULT 100056

PIM %d power fault cleared

PIM power fault cleared A
CHMGR_SDCARD_FAULT 100046 SD card fault detected (no present or unreadable) SD card fault detected A

CHMGR_SET_IFFLAG_FAILED

100017

Failed to set ifflags to %x for %s err %d

Interface initialization failure; interface may remain down, or device may reboot A
CHMGR_SHORT_RESET_CLEAR_FAILED 100019 Clearing a reboot request failed. A
CHMGR_SHORT_RESET_FAILED 100020 Request to reset the router by rebooting failed A

CHMGR_SPURIOUS_TIMER

100035

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

Internal error A

CHMGR_SYSOUT_OF_RESOURCES

100049

Timer add failed. Out of resources

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

CHMGR_UNKNOWN_MODULE_TYPE

100013

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

Unrecognized PIM module type in slot AE

CHMGR_UNSUPPORTED_MODULE_TYPE

100014

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 Number Message Format Description Action
CHMGR_IF_RENAME_FAILED 100015

Unable to rename %s to %s

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

%s temperature sensor fault detected. Unable to read temperature

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

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

Temperature sensor reading above red threshold AE
CHMGR_TEMP_YELLOW 100029

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

Temperature sensor reading above yellow threshold A

Priority: Alert

Message Number Message Format Description Action
CHMGR_CONFD_INIT_FAILED 100021

Initialization failed. vconfd_module_init returned %d

Chassis manager failed to initialize and start

AE

CVMX: Internal Cavium Driver Process

Priority: Informational

Message Number Message Format Description Action
CVMX_SYSLOG_END 999999 Terminating Cavium drivers

Internal Cavium drivers ending

E
CVMX_SYSLOG_START 900001 Starting Cavium drivers Internal Cavium drivers starting E

CXP: Cloud onRamp for SaaS Process

Priority: Informational

Message Number Message Format Description Action
CXP_SYSLOG_END 2799999 Terminating Cloud onRamp process Cloud onRamp for SaaS ending E
CXP_SYSLOG_START 2700001 Starting Cloud onRamp process Cloud onRamp for SaaS starting E

CONTAINER: Containers

Priority: Informational

Message Number Message Format Description Action
CONTAINER_SYSLOG_END 2699999 Terminating container process Container process ending E
CONTAINER_SYSLOG_START 2600001 Starting container process Container process starting E

DBGD: Debug Process

Priority: Informational

Message Number Message Format Description Action
DBGD_SYSLOG_END 2900001 Terminating debug process Debug process ending E
DBGD_SYSLOG_START 2999999 Starting debug process Debug process starting E

DHCPC: DHCP Client

The DHCP client process runs only on vEdge routers.

Priority: Informational

Message Number Message Format Description Action

DHCP_SYSLOG_CLEAR_INTERFACE

1300006

Clearing dhcp state for interface %s,

DHCP client cleared DHCP state for interface

E

DHCP_SYSLOG_DISCOVER_TIMEOUT

1300005 No response for dhcp discover packets for interface %s, DHCP discovery failure E
DHCP_SYSLOG_END 1300001 Terminating syslog process Syslog process ending E

DHCP_SYSLOG_IP_ADDR_ASSIGNED

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

DHCP_SYSLOG_IP_ADDR_RELEASED

1300003

Released address for interface %s

DHCP client released address E
DHCP_SYSLOG_IP_ADDR_RENEWED 1300010 Renewed address %s for interface %s DHCP client address renewed E

DHCP_SYSLOG_IP_ADDR_REQUEST_RENEW

1300004

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

1300004

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

1300004

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

DHCP client renewal request at 100% of lease expiration time E
DHCP_SYSLOG_START 1399999 Starting syslog process Syslog paroces starting E

Priority: Critical

Message Number Message Format Description Action

DHCP_SYSLOG_IP_ADDR_CONFLICT

1300007

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

DHCP client detected IP address conflict with another interface

E

DHCP: DHCP Server

The DHCP server process runs only on vEdge routers.

Priority: Informational

Message Number Message Format Description Action

DHCP_SYSLOG_CLEAR_SERVER_BINDINGS

1300008

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

DHCP server cleared bindings for interface E

DHCP_SYSLOG_CLEAR_SERVER_BINDINGS

1300008

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

DHCP server cleared bindings for interface E

FPMD: Forwarding Policy Manager Process

Priority: Informational

Message Number Message Format Description Action
FPMD_SYSLOG_ACL_PROGRAM_SUCCESS 1100005 Successfully reprogrammed access list - %s Access list successfully created E

FPMD_SYSLOG_END

1199999

Terminating fpmd

Forwarding policy manager process is ending E
FPMD_SYSLOG_POLICY_PROGRAM_SUCCESS 1100004 Successfully reprogrammed policy %s - %s Policy created successfully E
FPMD_SYSLOG_START 1100001 Starting fpmd Forwarding policy manager process is starting E

Priority: Alert

Message Number Message Format Description Action
FPMD_SYSLOG_ACL_PROGRAM_FAILED 1100003 Failed to allocate memory for access list %s. Continuing without the access Access list could not be created A
FPMD_SYSLOG_POLICY_PROGRAM_FAILED 1100002

Failed to allocate memory for policy %s - %s. Continuing without the policy

Policy could not be created A

FTMD: Forwarding Table Management Process

The forwarding table management process runs only on vEdge routers.

Priority: Informational

Message Number Message Format Description Action
FTMD_SLA_CLASS_ADD 1000020 SLA Class %s added at index %d: loss = %d%%, latency = %d ms SLA class added E
FTMD_SYSLOG_BFD_STATE 1000009

record with discriminator %u invalid

BFD state is invalid E
FTMD_SYSLOG_BFD_STATE 1000009

BFD Session %s.%u->%s.%u %s:%u->%s:%u %s %s %s %d

BFD state changed

E

FTMD_SYSLOG_DBGD_STATE 1000036

Connection to DBGD came up

Connection to DBGD went down

DBGD FTM: Initialized message queue

DBGD FTM oper %d vpn %u sip %s:%u dip %s %u

DBGD FTM: oper %d vpn %lu localc %d remote %d remoteip %s

Messages related to the FTM debugging process E
FTMD_SYSLOG_DPI_FLOW_OOM 1000024 Out-of-memory status for DPI flows: %s Memory status for DPI flows E
FTMD_SYSLOG_DPI_WRITE_OFF 1000032 Turning off writing DPI records to disk DPI records are no longer being written to disk E
FTMD_SYSLOG_END 1999999 Terminating FTM process Forwarding table management process ending E

FTMD_SYSLOG_FIB_GROW

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

FTMD_SYSLOG_FIB_GROW

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

VPN %lu Interface %s %s,

FTM detected interface state change E
FTMD_SYSLOG_LR_ADD 1000027 LR: Adding Iface %s as LR Last-resort interface is being added E
FTMD_SYSLOG_LR_ADD 1000027 LR: Iface %s has become an LR Interface has become a last-resort interface E
FTMD_SYSLOG_LR_DEL 1000028 LR: Found iface %s while looking for iface %s Last-resort interface found while looking for another interface E
FTMD_SYSLOG_LR_DEL 1000028 LR: iface %s has become non-LR. Hence set OPER UP on that interface Last-resort interface has become an active interface E
FTMD_SYSLOG_LR_DEL 1000028

LR: Iface %s has become a non-LR

LR: Removing Iface %s as LR

Messages related to an interface that is no longer a last-resort interface E
FTMD_SYSLOG_LR_DOWN 1000030

LR: At least one bfd session of non-LR is active

LR: At least one non-LR's bfd session in Up

LF bfd session = SIP: %s DIP:%s SPORT:%u DPORT:%u PROTO:%u is Up for at least &u interval msecs

LR: Bringing LR's wan if Down in %u msecs

LR: Bringing LR's wan if Down right away

LR: Cleared LR down_in-progress

Messages related to shutting down an interface of last resort E
FTMD_SYSLOG_LR_UP 1000029 LR: All bfd sessions gone down. Setting LR %s's OPER state to UP Last-resort interface's status set to Up because no other circuits on the router are active E
FTMD_SYSLOG_LR_UP 1000029 LR: Bring LR's wan if up immediately as no other circuit's bfd sessions are up Last-resort interface activated because no other circuits on the router are active E
FTMD_SYSLOG_LR_UP 1000029 LR: Starting hold up timer immediately !! Hold timer for last-resort interface activated because no other circuits on the router are active E
FTMD_SYSLOG_NAT_FLOW_ADD 1000039 NAT flow add: Private %s, Public %s FTM detected the addition of a NAT flow with the specified private and public IP addresses E
FTMD_SYSLOG_NAT_FLOW_DELETE 1000040 NAT flow delete: Private %s, Public %s FTM detected the deletion of a NAT flow with the specified private and public IP addresses E
FTMD_SYSLOG_PIM_DOWN 1000017 FTM detected that PIM ended E
FTMD_SYSLOG_PIM_UP 1000018 FTM detected that PIM started E

FTMD_SYSLOG_ROUTE_ADD_FAIL

1000004

Route Add for prefix %s Failed. Reason %s

FTM failed to add a route received from the RTM E
FTMD_SYSLOG_ROUTE_VERIFY 1000033 Successfully verified RIB and FIB routes on the vEdge FTM verified the routes in the router's RIB and FIB E
FTMD_SYSLOG_ROUTE_VERIFY_FAIL 1000034 RIB and FIB router verification failed E
FTMD_SYSLOG_SIGTERM 1000005

Received Cleanup signal. Exiting gracefully

FTM received termination signal from sysmgr and is about to go down E
FTMD_SYSLOG_START 1000001 Starting FTM process Forwarding table management process starting E
FTMD_SYSLOG_TCPD_STATE 1000035 Sent tcp_opt_disable successfully for vpn %ld Disabling of TCP options was successful on the interface E
FTMD_SYSLOG_TUNNEL_ADD_FAIL 1000015

Tunnel Add to TLOC %s.%s Failed. Reason %s

Failed to add new TLOC; reported by TTM E
FTMD_SYSLOG_WWAN_STATE 1000025 Bring %s last resort circuit Up or down status of circuit of last resort

E

FTMD_SYSLOG_WWAN_STATE 1000025 Connection to WWAN came up Circuit of last resort came up E
FTMD_SYSLOG_WWAN_STATE 1000025 Connection to WWAN went down Circuit of last resort went down E

Priority: Notice

Message Number Message Format Description Action
FTMD_SLA_CLASS_DEL 1000022 Sla class %s at index %d removed: loss = %d%%, latency = %d ms, jitter = %d ms SLA class deleted A
FTMD_SLA_CLASS_MOD 1000021 Sla class %s at index %d modified: loss = %d%%, latency = %d ms, jitter = %d ms SLA class changed A
FTMD_SLA_CLASS_VIOLATION 1000023 [%lu] SLA class violation application %s %2:%u._%s:&u protocol: %d dscp: %d %s, status - %s SLA class violation for application in specified VPN, with specified source address and port, destination address and port, protocol, DSCP, and reason A
FTMD_SYSLOG_DOT1X_HOST 1000031

Host %s denied access on interface %s in single host mode

An 802.1X interface in single-host mode is denying access, because it has already granted access to a client E
FTMD_SYSLOG_FLOW_LOG 1000026 %s FTM detected a new flow E

FTMD_SYSLOG_FP_CORE_FAIL

1000013

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

1000016

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
FTMD_SYSLOG_ZBFW_FLOW_ADD 1000037 ZBF flow created zone-air %s key %s src_vpn %d dst_vpn %d expiry secs %d state %s FTM detected the creation of a zone pair E
FTMD_SYSLOG_ZBFW_FLOW_DEL 1000038 ZBF flow deleted zone-air %s key %s src_vpn %d dst_vpn %d state %s FTM detected the deletion of a zone pair E

Priority: Warning

Message Number Message Format Description Action

FTMD_SYSLOG_TTM_DOWN

1000008

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

1000007

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

FTM connected with TTM E
FTMD_TUNNEL_SLA_CHANGED 1000019 SLA changed for session: %s.%u->%s:%u->%s:%u. New loss = %d%%, latency = %d ms, jitter = %d ms, SLA Classes: %s (ox%x) %s%s FTM detected SLA changes on a tunnel E

Priority: Error

Message Number Message Format Description Action

FTMD_SYSLOG_CONFD_FAIL

1000003

Failed to register bfd show data cb

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

FTMD_SYSLOG_CONFD_FAIL

1000003

Failed to register policer show data cb

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

FTMD_SYSLOG_CONFD_FAIL

1000003

%s: Failed to register data cb, __FUNCTION__

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

FTMD_SYSLOG_CONFD_FAIL

1000003

%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

1000011

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

FTM detected an FP crash; device will reboot soon AE
FTMD_SYSLOG_IFADD_FAIL 1000014 Failed to add interface %s in vpn %lu. Out of forwarding interface records Interface not added because of insufficient forwarding interface database records A
FTMD_SYSLOG_IFADD_FAIL 1000014 Failed to add interface %s in vpn %lu. Out of snmp interface indices Interface not added because of insufficient SNMP interface indices A
FTMD_SYSLOG_INIT_FAIL 1000002 vconf_module_init returned %d FTM failed to start with confd A
FTMD_SYSLOG_LR_DEL 1000028 LR: LR is not enabled...while we are trying to remove iface %s as last resort Interface being removed is not configured as a last-resort interface A
FTMD_SYSLOG_LR_DEL 1000028 LR: Unable to remove iface %s as LR Interface is no longer a last-resort interface so it cannot be deleted A
FTMD_SYSLOG_RTM_DECODE_FAIL 1000006

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 1000010

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

Internal error A

GPS: Global Positioning System

Priority: Informational

Message Number Message Format Description Action
GPS_SYSLOG_END 2599999 Terminating GPS GPS process is ending E
GPS_SYSLOG_GGA_FIX 2500002 GGA %d:%d:%d lat=%f lon=%f alt=%f sat=%d hdop %f fix%d GPS fix information E
GPS_SYSLOG_GSA_FIX 2500004 GSA %s pdop=%.2f hdop=%.2f vdop=%.2f GPS satellite and dilution of precision (DOP) information E
GPS_SYSLOG_PSTOP 2500005

Polling disabled

Stopping polling timers

Messages related to polling for GPS information E
GPS_SYSLOG_RMC_FIX 2500003 RMC %s %d %d lat=%f lon=%f speed %f course=%s status valid Essential minimum GPS information E
GPS_SYSLOG_START 2500001

Starting GPS

GPS process is starting E

IGMP: Internet Group Management Protocol

Priority: Informational

Message Number Message Format Description Action
IGMP_SYSLOG_END 1800001 Terminating IGMP IGMP process is ending E
IGMP_SYSLOG_START 1899999 Starting IGMP IGMP process is starting E

LIBBSS: UNIX BSS Library

Unused Messages

Message Number Message Format Description Action
LIBBSS_SYSLOG_END 1699999 Terminating libbss UNIX BSS library process is ending E
LIBBSS_SYSLOG_START 1600001 Starting libbss UNIX BSS library process is starting E

LIBCHMGR: Chassis Manager Library Process

Unused Messages

Message Number Message Format Description Action
LIBCHMGR_SYSLOG_END 1599999 Terminating libchmrg Chassis manager library process is ending E
LIBCHMGR_SYSLOG_START 1500001

Starting libchmgr

Chassis manager libryary process is starting E

MSGQ: Message Queue Process

Ununsed Messages

Message Number Message Format Description Action
MSGQ_SYSLOG_END 899999 Terminating msgq Message queue process is ending E
MSGQ_SYSLOG_START 800001 Starting msgq Message queue process is starting E

OMP: Overlay Management Protocol

Priority: Informational or Other

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

OMP_PEER_STATE_CHANGE

400002

%s peer %s state changed to %s,

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

OMP_TLOC_STATE_CHANGE

400004

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

TLOC state changed E

Priority: Notice

Message Number Message Format Description Action
OMP_SYSLOG_END 400006 Terminating OMP process is stopping E
OMP_SYSLOG_START 400001 Starting OMP process is starting E

PIM: Protocol-Independent Multicast Process

Priority: Informational

Message Number Message Format Description Action
IGMP_SYSLOG_END 1900001 Terminating PIM process is ending E
IGMP_SYSLOG_START 1999999 Starting PIM process is starting E

Priority: Notice

Message Number Message Format Description Action
PIM_SYSLOG_IF_STATE_CHANGE 1900003

VPN %lu Interface %s %s

In specified VPN, interface state changed to up or down

E

PIM_SYSLOG_NBR_STATE_CHANGE 1900002 Neighbor %s state changed to up PIM neighbor came up E
PIM_SYSLOG_TUNNEL_STATE_CHANGE 1900004 Tunnel %s state changed to %s Tunnel used for PIM when down or came up E

Priority: Error

Message Number Message Format Description Action
PIM_SYSLOG_NBR_STATE_CHANGE 1900002 Neighbor %s stated changed to down PIM neighbor went down E

POLICY: Policy Process

Unused Messages

Message Number Message Format Description Action
POLICY_SYSLOG_END 799999 Terminating policy

Policy process is ending

E
POLICY_SYSLOG_START 700001 Starting policy Policy process is starting E

RESOLV: Resolver Process

Unused Messages

Message Number Message Format Description Action
RESOLV_SYSLOG_END 2000001 Terminating resolver Resolver process is ending E
RESOLV_SYSLOG_START 2099999 Starting resolver Resolver process is starting E

SNMP Listener Process

Unused Messages

Message Number Message Format Description Action
SNMP_SYSLOG_END 2100001 Terminating SNMP listener SNMP listener process is ending E
SNMP_SYSLOG_START 2199999 Starting SNMP listener SNMP listener process is starting E

SYSMGR: System Manager Process

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 Number Message Format Description Action

SYSMGR_CONFD_PHASE1_INFO

200041

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

200007

Confd Phase2 Up

Successful device bringup E

SYSMGR_DAEMON_START

200017

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

System manager started process in VPN E

SYSMGR_DAEMON_UP

200011

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

Daemon started by system manager came up as expected E

SYSMGR_SIGTERM

200001

Received sigterm, stopping all daemons except confd

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

SYSMGR_VPN_DESTROY

200022

vpn %lu destroy. lookup returned %p

Stopping all processes in VPN E

Priority: Notice

Message Number Message Format Description Action
SYSMGR_CLOCK_SET 200025

System clock set to %s

System clock set by user E

SYSMGR_CONFD_CDB_NOT_INITED

200031

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

First-time initialization of configuration database E

SYSMGR_CONFD_PHASE1_INFO

200041

Install successfully completed from %s to %s

Failed to read installation ID; will fall back to default E
SYSMGR_CORE_FILE_COMPRESSED 200045 Core file was compressed E
SYSMGR_DAEMON_EXIT_NORMAL 200021 A process terminated normally E
SYSMGR_DAEMON_RESTARTED 200043 A process restarted E

SYSMGR_DISK_ALERT_OFF

200036

Disk usage is below 60%%.

Disk usage is below threshold E

SYSMGR_MEMORY_ALERT_OFF

200058

System memory usage is below 50%

System memory usage is below 50% E
SYSMGR_MISC 200065 Miscellaneous message E

SYSMGR_REBOOT

200038

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

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

Created shared memory %s

Successfully initialized shared memory for communication with other processes E
SYSMGR_SHUTDOWN 200040

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 200050

System up with software version %s

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

System status red (software version '%s')

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

Starting system with viptela software version %s

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

System timezone changed from %s to %s

System timezone changed as result of configuration change E
SYSMGR_UPGRADE_AUTO_CONFIRMED 200063 A software upgrade was automatically confirmed E
SYSMGR_UPGRADE_NOT_CONFIRMED 200049 A software upgrade was as not confirmed E
SYSMGR_UPGRADE_PENDING_CONFIRMATION 200059 A software upgrade is pending confirmation E
SYSMGR_VDEBUG_LOG_CLEANUP_NEEDED 200066 Debug logs exceed expected storage quota. Performing age-based cleanup to restore debug logging operations. Debug logs were deleted to create space A
SYSMGR_DAEMON_TERMINATED 200020 A process terminated E
SYSMGR_WATCHDOG_EXPIRED 200062 The watchdog process expired A

Priority: Warning

Message Number Message Format Description Action
SYSMGR_CORE_FILE_DELETED 200044 Core file was deleted A
SYSMGR_DAEMON_RESTART_ABORTED 200060 The restarting of a process was aborted A

SYSMGR_DAEMON_STOP

200018

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

System manager stopped a daemon E

SYSMGR_DISK_ALERT_ORANGE

200054

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

Disk usage is above 75% E

SYSMGR_DISK_ALERT_YELLOW

200035

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

Disk usage is above 60% E
SYSMGR_FILE_DELETED 200064 Deleted file %s (size %lu MB) to recover disk space File deleted to free up disk space A

SYSMGR_MEMORY_ALERT_ORANGE

200056

System memory usage is above 75%%

System memory usage is above 75% E

SYSMGR_MEMORY_ALERT_YELLOW

200057

System memory usage is above 60%%

System memory usage is above 60% E

Priority: Error

Message Number Message Format Description Action

SYSMGR_BAUD_RATE_SET

200046

Console baud rate changed to '%d', baud_rate

Console baud rate changed E

SYSMGR_BAUD_RATE_SET_FAIL

200047

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

200047

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

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

SYSMGR_CLOCK_SET_FAIL

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

A

SYSMGR_CONFD_CDB_INIT_OPEN_FAIL

200030 Failed to open cdb init file (%s) Failed to open the configuration database A
SYSMGR_DAEMON_EXIT_FAIL 200023 A process could not terminate A

SYSMGR_CONFD_DATACB_REGISTER_FAIL

200010

Failed to register data cb

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

SYSMGR_CONFD_CDB_DEL_FAIL

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

SYSMGR_CONFD_FORK_FAILURE

200003

Cannot move confd to phase2 (err %s)

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

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 200005 Failed to generate SSH keys for archive Failed to generate SSH keys E

SYSMGR_CONFD_PHASE1_FAILURE

200005

Failed to get install id from file, using 00_00

Failed to read previous system version A
SYSMGR_CONFD_PHASE1_FAILURE 200005

Failed to get previous version, using 0.0

Failed to read system version A
SYSMGR_CONFD_PHASE1_FAILURE 200005

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 200005 Verified that archive keys exist Verified that configuration archive keys exist A
SYSMGR_CONFD_PHASE2_FAILURE 200006

Failed to get current version, using 0.0

Failed to read system version file A
SYSMGR_CONFD_PHASE2_FAILURE 200006

Failed to open %s, version_file

Failed to open system version file A
SYSMGR_CONFD_PHASE2_FAILURE 200006

Failed to read %s, version_file

Failed to read system version file A
SYSMGR_CONFD_PHASE2_FAILURE 200006

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

200009

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

Failed to reply to confd; some show commands may not work A
SYSMGR_CONFD_SETPGID_FAILURE 200004 setpgid(0,0) failed: %d Process group failed to start A

SYSMGR_DAEMON_DOWN

200012

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

Process started by system manager went down A

SYSMGR_DAEMON_EXECV_FAILURE

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

SYSMGR_DAEMON_FORK_FAILURE

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

SYSMGR_DAEMON_INACTIVE

200033

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

200013

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

200013

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_SETAFFINITY_FAILURE 200061 The scheduling of a process failed E

SYSMGR_DAEMON_SETPGID_FAILURE

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

SYSMGR_DAEMON_STOPPED

200019

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

200027

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

Failed to update hardware clock to system time specified by user

A

SYSMGR_SHM_FAIL 200042

Failed to close shared memory %s with an error %d

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

Failed to map shared memory %s

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

Failed to open shared memory %s with an error %d

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

Failed to truncate shared memory %s with an error %d

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

Failed to unmap shared memory %s

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

SYSMGR_SWITCHBACK_FAILED

200053

Software upgrade to version %s failed because of %s

Software upgrade failed A

SYSMGR_TIMEZONE_SET_FAIL

200029

Failed to set system timezone to %s (rc = %d)

Failed to set system timezone to timezone specified by user A
SYSMGR_TRACE_ERROR 200024 A trace error occurred A

Priority: Critical

Message Number Message Format Description Action

SYSMGR_CONFD_INIT_FAIL

200008

Sysmgr child in charge of migrating confd/ncs to phase2 exited with error code %d

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

SYSMGR_DISK_ALERT_RED

200034

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

Disk usage is above 90% AE

SYSMGR_MEMORY_ALERT_RED

200055

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

System memory usage is above 90% AE

SYSMGR_REBOOT_HALTED

200039 Reboot (reason: %s) aborted..too many reboots

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

AE

SYSMGR_UPGRADE_FAILED

200052

Software upgrade to version %s failed because of reason

Software upgrade failed AE

TCPD: TCP Options Process

Priority: Informational

Message Number Message Format Description Action
TCPD_MSGQ_SERVER 2800002 Server Exception: %s Proxy server did not accept connection E
TCPD_PROXY 2800004

Enabled TCP_OPT for vpn %lu: %s:%u

%s

Starting sysmgr_app object

tcpd<->ftmd channel established

tcpd<->ftmd = Will try connecting

Messages related to starting a proxy E
TCPD_PROXY 2800004 tcpd error counters -%s Count of TCP option errors E
TCPD_SYSLOG_END 2800001 Terminating TCP options TCP options process ending E
TCPD_SYSLOG_START 2899999 Starting TCP options TCP options process starting E
TCPD_SYSMGR_APP 2800003

%s Exception: %s

%s - Sysmgr app::connect -Exception - %s

Messages related to the connection between the system manager and the TCP proxy process E

Priority: Debug

Message Number Message Format Description Action
TCPD_SYSMGR_APP 2800003

%s - Registering for send_hello-msg

%s: Sending following register msg

Sending msg of length %u

%s - Sysmgr app::connect

%s - Write %u bytes

%s - Wrote register msg %u

Messages related to the connection between the system manager and the TCP proxy process E

TRACKER: Interface Tracker Process

Priority: Informational

Message Number Message Format Description Action
TRACKER_SYSLOG_CONN_DOWN 1700003 Connection to %s %s Down Connection to interface is down E
TRACKER_SYSLOG_CONN_UP 1700002 Connection to %s %s Up Connection to interface is up E
TRACKER_SYSLOG_END 1700001 Terminating Interface tracker process is ending E
TRACKER_SYSLOG_START 1799999 Starting Interface tracker process is starting E

VCONFD: Viptela Configuration Process

Priority: Informational

Message Number Message Format Description Action
VCONFD_SYSLOG_END 1400001 Terminating Configuration process is ending E
TRACKER_SYSLOG_NOTIFICATION 1400002 Notification: %d/%d?%d %d:%d:%d %s
severity level: %s hostname: %s system-ip %s
process name: %s process id: %s reason: %s
Configuration at specified date and time for a process, with reason E
TRACKER_SYSLOG_NOTIFICATION 1400002 Notification: %d/%d?%d %d:%d:%d %s
severity level: %s hostname: %s system-ip %s
status: %s install id: %s message %s
Configuration at specified date and time, with specified status (minor, major) E
TRACKER_SYSLOG_NOTIFICATION 1400002 Notification: %d/%d?%d %d:%d:%d %s
severity level: %s hostname: %s system-ip %s
reason: %s
Configuration at specified date and time, with reason E
TRACKER_SYSLOG_NOTIFICATION 1400002 Notification: %d/%d?%d %d:%d:%d %s
severity level: %s hostname: %s system-ip %s
reboot reason: %s
Configuration at specified date and time, with reboot reason E
TRACKER_SYSLOG_NOTIFICATION 1400002 Notification: %d/%d?%d %d:%d:%d %s
severity level: %s hostname: %s system-ip %s
username: %s remote host: %s
Configuration at specified date and time, for username and remote host E
TRACKER_SYSLOG_NOTIFICATION 1400002 Notification: %d/%d?%d %d:%d:%d %s
severity level: %s hostname: %s system-ip %s
vpn id: %s if name: %s mac addr: %s ip-addr:%s
Configuration at specified date and time, for VPN, interface, MAC address, and IP address E
VCONFD_SYSLOG_START 1499999 Starting Configuration process is starting E

VDAEMON: Viptela Software Process

Priority: Informational

Message Number Message Format Description Action

VDAEMON_SYSLOG_DOMAIN_ID_CHANGE

500006

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

System domain ID changed

E
VDAEMON_SYSLOG_END 599999 Process ending E

VDAEMON_SYSLOG_ORG_NAME_CHANGE

500008

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

System organization name changed E

VDAEMON_SYSLOG_PEER_STATE

500003

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

Peer state changed to up or down E

VDAEMON_SYSLOG_SITE_ID_CHANGE

500005

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

System site ID changed E
VDAEMON_SYSLOG_START 500001 Process starting E

VDAEMON_SYSLOG_SYSTEM_IP_CHANGE

500007

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

System IP address changed E

Priority: Error

Message Number Message Format Description Action
VDAEMON_BOARD_ID_CHALLENGE_FAILED 500002 Board ID could not be verified E
VDAEMON_BOARD_ID_INIT_FAILED 500001 Board initialization failed because board ID could not be verified E
VDAEMON_SYSLOG_CERT_STORE_FAIL 500009 Certificate store init failed Certificate not stored AE

VDAEMON_SYSLOG_PEER_AUTH_FAIL

500004

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

Authentication with a vdaemon peer failed

E

VDAEMON_SYSLOG_PEER_STATE

500003

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 Number Message Format Description Action
VRRPD_STATE_CHANGE 600002

Group %d, interface %s, vpn %lu state changed to %s

VRRP interface state change

E
VRRPD_SYSLOG_END 699999 Terminating VRRPD VRRP process is ending E
VRRPD_SYSLOG_START 600001 Starting VRRPD VRRP process is starting E

WLAN: Wireless LAN Process

The wireless LAN process runs only on vEdge routers.

Priority: Informational

Message Number Message Format Description Action
WLAN_SYSLOG_END 2300001 Terminating wlan WLAN process is ending E
WLAN_SYSLOG_START 2399999 Starting wlan WLAN process is starting E

WWAND: Cellular Process

The wireless WAN process runs only on vEdge routers.

Priority: Informational

Message Number Message Format Description Action
WWAN_SYSLOG_ADMIN_DWL 2400010 Cellular%d interface is set for deletion Cellular interface is about to be deleted E
WWAN_SYSLOG_ADMIN_DOWN 2400009 Cellular%d interface is set to admin down Cellular interface is administratively Down E
WWAN_SYSLOG_ADMIN_UP 2400008 Cellular%d interface is set to admin up Cellular interface is administratively Up E
WWAN_SYSLOG_CONNECT 2400002 Connected to Cellular%d modem Connection to cellular modem established E
WWAN_SYSLOG_CONNECT_DATA 2400006 E
WWAN_SYSLOG_DATA_MONITOR 2400032

Info: %lld bytes left

Info: exceeded by %lld bytes

Information about amount of data remaining in billing cycle E
WWAN_SYSLOG_DATA_SESSION 2400019 Data session started successfully Data session on cellular interface started successfully E
WWAN_SYSLOG_DATA_SESSION_BEARER 2400028 Data bearer changed to %s (%lx) Data carrier changed E
WWAN_SYSLOG_DATA_SESSION_DISCONNECT 2400023 Data session disconnect: restarting session Data session was disconnected and is restarting E
WWAN_SYSLOG_DATA_SESSION_DISC_REASON 2400024 Data session disconnect reason: %s Reason data session was disconnected E
WWAN_SYSLOG_DATA_SESSION_DISC_VERB 2400025 Data session disconnect reason verbose: %s More information about why data session disconnected E
WWAN_SYSLOG_DATA_SESSION_DOMAIN 2400026 Packet-switched domain state change to %s: registration: %s ran: %s if: %s Packet-switched domain changed E
WWAN_SYSLOG_DATA_SESSION_DORMANCY 2400029 Dormancy state changed to %s Session dormancy state changed E
WWAN_SYSLOG_DATA_SESSION_NETWORK 2400027 Network registration changed to %s: domain: %s ran: %s if: %s Network registration changed E
WWAN_SYSLOG_DATA_SESSION_START 2400018 Starting data session on Cellular%e Data session on cellular interface is starting E
WWAN_SYSLOG_DATA_SESSION_STATE 2400020 Data session state changed to %s Data session status E
WWAN_SYSLOG_DATA_SESSION_STOP 2400022 Data session stopped successfully Data session stopped E
WWAN_SYSLOG_DISCONNECT 2400003 Disconnected LTE modem %d Disconnection from LTE modem E
WWAN_SYSLOG_END 2400001 Terminating WWAND Ending WWAN process E
WWAN_SYSLOG_FIRMWARE 2400007

Failed to get firmware details after upgrade on modem %d

Firmware upgrade failed on modem %d

Firmware upgrade successful on modem %d

Upgrading firmware configuration on modem %d

Upgrading firmware image on modem %d

Messages related to firmware upgrade on the cellular modem E
WWAN_SYSLOG_LR_DOWN 2400012 %s%d: bringing down Last-resort interface is shutting down E
WWAN_SYSLOG_LR_UP 2400011 %s%d: bringing up Last-resort interface is starting E
WWAN_SYSLOG_MODEM_ACTIVATION 2400039 Modem activation status: %s (%lu) Modem actual state and status E
WWAN_SYSLOG_MODEM_PMODE 2400017

Modem is not in online mode

Modem is not in online mode (tmp: %s degrees C)

Modem power state is: %s (prev: %s)

Modem set to %s (prev: %s)

Powered off the modem %d

Messages related to modem power mode status E
WWAN_SYSLOG_MODEM_STATE 2400034 Modem device state changed to %s Modem state changed E
WWAN_SYSLOG_MODEM_TEMP 2400037 Modem temperature %d degree C: %s Modem temperature and state E
WWAN_SYSLOG_MODEM_UP 2400035 WWAN cellular%d modem is back up Modem reconnected E
WWAN_SYSLOG_OMA_DM_DONE 2400041 Modem OMA DM configuration completed Modem OMA-DM configuration finished E
WWAN_SYSLOG_OPER_DOWN 2400014 Cellular%d set if down Cellular interface is operationally Down E
WWAN_SYSLOG_OPER_UP 2400013 Cellular%d set if up Cellular interface is operationally Up E
WWAN_SYSLOG_PROFILE_CHECK 2400030 Profile %lu with PDP: %s APN: %s Auth: %s User: %s Cellular profile information E
WWAN_SYSLOG_REBOOT 2400040 Cellular%d modem mode updated: rebooting; %s reason Reason why celluar modem rebooted E
WWAN_SYSLOG_SDK_DOWN 2400005 SDK got terminated: %s Connection to software development kit terminated E
WWAN_SYSLOG_SDK_UP 2400004 Connected to Cellular%d sdk process Connection to cellular software development kit established E
WWAN_SYSLOG_SIM_STATUS 2400033 SIM status changed to: %s SIM status changed E
WWAN_SYSLOG_START 2499999

Starting WWAND

Starting WWAN process E
WWAN_SYSLOG_TRACK_GW_UP 2400015 Cellular%d gateway %s is reachable Cellular gateway is reachable E

Priority: Error

Message Number Message Format Description Action
WWAN_SYSLOG_AUTO_PROFILE_MISS 2400031 Manually configure APN profile for the data connection Data session could not start because required APN could not be located E
WWAN_SYSLOG_MODEM_DOWN 2400036 WWAN cellular%d modem went down Modem is disconnected E
WWAN_SYSLOG_MODEM_RESET 2400038 Failed to recover Cellular %d modem Connection to modem could not be reestablished E
WWAN_SYSLOG_TRACK_GW_DOWN 2400016 Cellular%d gateway %s is not reachable Cellular gateway is not reachable E
  • Was this article helpful?