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

debug

[no] debug—Enable and disable debugging mode for all or selected software function. Debug output is placed in the /var/log/tmplog/vdebug file on the local device.

Command Syntax

[no] debug all
[no] debug aaa login (radius | tacacs)
[no] debug bgp (all | events | fsm | ipcs | packets) vpn vpn-id
[no] debug cflowd (cli | events | ipc | misc | pkt_tx) [level (high | low)]
[no] debug chmgr all
[no] debug cloudexpress (events | ftm | omp | rtm | ttm) [level (high | low)]
[no] debug confd (developer-log [level (high | low)] | snmp)
[no] debug config-mgr events
[no] debug config-mgr pppoe
 [level (high | low)]
[no] debug dhcp-client (all | events | packets)
[no] debug dhcp-helper (all | events | packets)
[no] debug fpm (all | config | dpi | policy | ttm)
[no] debug ftm all
[no] debug igmp (config | events | fsm | ipc | packets) [level (high | low)]
[no] debug iked (all | confd | error | events | misc) [level (high | low)]
[no] debug netconf traces
[no] debug omp (all | events | ipcs | packets)
[no] debug ospf (all | events | ipcs | ism | lsa | nsm | nssa | packets) vpn vpn-id
[no] debug pim (auto-rp | events | fsm | ipcs | packets) [level (high | low)] vpn vpn-id
[no] debug resolver events [level (high | low)]
[no] debug rtm (events | ipc | next-hop | packets | rib) vpn vpn-id
[no] debug snmp events [level (high | low)]
[no] debug sysmgr all
[no] debug transport events [level (high | low)]
[no] debug tcpd [level (high | low)]
[no] debug ttm events
[no] debug vdaemon (all | confd | events | misc | packets) (high | low)
[no] debug vrrp (all | events | packets) vpn vpn-id

Options

All
[no] debug all
Control debugging for all software functions that can be debugged.
AAA Login via RADIUS or TACACS
[no] debug aaa login (radius | tacacs)
Control debugging for login attempts make using RADIUS or TACACS.
BGP
[no] debug bgp (all | events | fsm | ipcs | packets) vpn vpn-id
Control debugging for BGP:
all—Control the debugging of all BGP events, finite-state machine transitions, interprocess communications, and packets.
events—Control the debugging of BGP events, including damping events, finite-state machine events and transitions, keepalive message events, next-hop events, and routing table update events.
fsm—Control the debugging of BGP finite-state machine transitions.
ipcs—Control the debugging of all BGP interprocess communications.
packets—Control the debugging of all BGP protocol packets.
vpn vpn-id—Specify the VPN in which to perform debugging.
Cflowd Traffic Flow Monitoring
[no] debug cflowd (cli | events | ipc | misc | pkt_tx) [level (high | low)]
Control debugging for cflowd:
cli—Control the debugging of messages that are logged as the result of a configuration change made either directly on the vEdge router or because the changes have been pushed from the vSmart controller to the router.
events—Control the debugging of events to which the cflowd process (daemon) responds, including when the process connects with a collector or loses connectivity with it, and when the source-interface as configured in the vSmart template is removed.
ipc—Control the debugging of all cflowd interprocess communications.
level (high | low)—Set the detail of the comments logged by the debugging operation. The default level, low, provides comments sufficient to help you understand the actions that are occurring. The level high provides greater detail for the live debugging that might typically be performed by the Viptela engineering team.
misc—Control the debugging of miscellaneous cflowd events.
pkt_tx—Control the debugging of cflowd packet transmissions.
Chassis Manager
[no] debug chmgr all
Control debugging for the chassis manager.
CloudExpress Service
[no] debug cloudexpress (events | ftm | omp | rtm | ttm) [level (high | low)]
Control debugging for CloudExpress service:
events—Control the debugging of events to which the cflowd process (daemon) responds, including when the process connects with a collector or loses connectivity with it, and when the source-interface as configured in the vSmart template is removed.
ftm—Control debugging of the communication between the CloudExpress service and the forwarding table manager.
level (high | low)—Set the detail of the comments logged by the debugging operation. The default level, low, provides comments sufficient to help you understand the actions that are occurring. The level high provides greater detail for the live debugging that might typically be performed by the Viptela engineering team.
omp—Control the debugging of all CloudExpress OMP operations.
rtm—Control the debugging of communication between the CloudExpress service and the route table manager.
ttm—Control the debugging of communication between the CloudExpress service and the tunnel table manager.
DHCP Client
[no] debug dhcp-client (all | events | packets)
Control the debugging of Dynamic Host Configuration Protocol (DHCP) client activities:
all—Control the debugging of all DHCP client events and packets.
events—Control the debugging of DHCP client protocol events.
packets—Control the debugging of all DHCP client packets.
DHCP Helper
[no] debug dhcp-helper (all | events | packets)
Control the debugging of Dynamic Host Configuration Protocol (DHCP) helper activities:
all—Control the debugging of all DHCP helper events and packets.
events—Control the debugging of DHCP helper protocol events.
packets—Control the debugging of all DHCP helper packets.
Forwarding Policy Manager
[no] debug fpm (all | config | dpi | policy | ttm)
Control debugging for the forwarding policy manager:
all—Control the debugging of events related to the forwarding policy manager, including configuration changes, application-aware routing events, and communication with the tunnel table manager.
config—Control the debugging of messages that are logged as a result of a policy configuration change made either directly on the vEdge router or because the changes have been pushed from the vSmart controller to the router.
dpi—Control the debugging of all application-aware routing (deep packet inspection) events.
policy—Control the debugging of messages that are logged as the result of policy programming events.
ttm—Control the debugging of communication between the forwarding policy manager and the tunnel table manager.
Forwarding Table Manager
[no] debug ftm all
Control debugging for the forwarding table manager operations.
IGMP
[no] debug igmp (all | events | fsm | ipcs | packets)
Control debugging for IGMP:
all—Control the debugging of all IGMP events, finite-state machine transitions, interprocess communications, and packets.
events—Control the debugging of IGMP events, including finite-state machine events and transitions, keepalive message events, next-hop events, and routing table update events.
fsm—Control the debugging of IGMP finite-state machine transitions.
ipcs—Control the debugging of all IGMP interprocess communications.
packets—Control the debugging of all IGMP protocol packets.
IKE
[no] debug ike (all | confd | error | events | misc) [level (high | low)]
Control debugging for the forwarding policy manager:
all—Control the debugging of all events related to IKE.
confd—Control the debugging of Netconf activity to log all IKE-related Netconf configuration messages between the local device and the vManage NMS.
error—Control the debugging of IKE errors.
events—Control the debugging of IKE protocol events.
level (high | low)—Set the detail of the comments logged by the debugging operation. The default level, low, provides comments sufficient to help you understand the actions that are occurring. The level high provides greater detail for the live debugging that might typically be performed by the Viptela engineering team.
misc—Control the debugging of miscellaneous IKE events.
Netconf
[no] debug netconf traces
Enable and disable Netconf activity to log all Netconf configuration messages between the local device and the vManage NMS. Netconf debug messages are logged to the /var/log/confd/netconf.trace file.
OMP
[no] debug omp (all | events | ipcs | packets)
Control the debugging of OMP:
all—Control the debugging of all OMP events, interprocess communications, and packets.
events—Control the debugging of OMP events.
ipcs—Control the debugging of all OMP interprocess communications.
packets—Control the debugging of all OMP protocol packets.
OSPF
[no] debug ospf (all | events | ipcs | ism | lsa | nsm | nssa | packets) vpn vpn-id
Control the debugging of OSPF:
all—Control the debugging of all OSPF functions.
events—Control the debugging of OSPF events, including adjacencies, flooding information, designated router selection, and shortest path first (SPF) calculations.
ipcs—Control the debugging of all OSPF interprocess communications.
ism—Control the debugging of OSPF interface state machine transitions.
lsa—Control the debugging of OSPF LSA messages
nsm—Control the debugging of OSPF network tate machine transitions.
nssa—Control the debugging of OSPF NSSA messages.
packets—Control the debugging of all OSPF protocol packets.
PIM
[no] debug pim (all | events | fsm | ipcs | packets) vpn vpn-id
Control debugging for PIM:
all—Control the debugging of all PIM events, finite-state machine transitions, interprocess communications, and packets.
events—Control the debugging of PIM events, including finite-state machine events and transitions, keepalive message events, next-hop events, and routing table update events.
fsm—Control the debugging of PIM finite-state machine transitions.
ipcs—Control the debugging of all PIM interprocess communications.
packets—Control the debugging of all PIMP protocol packets.
vpn vpn-id—Specify the VPN in which to perform debugging.
Resolver
[no] debug resolver events [level (high | low)]
Control debugging for all resolver process events. The resolver process handles a plethora of tasks, including tracking ARP, MAC addresses, DNS, and connected interfaces.
level (high | low)—Set the detail of the comments logged by the debugging operation. The default level, low, provides comments sufficient to help you understand the actions that are occurring. The level high provides greater detail for the live debugging that might typically be performed by the Viptela engineering team.
Route Table Manager
[no] debug rtm (events | ipc | next-hop | packets | rib) vpn vpn-id
Control debugging for the route table manager:
events—Control the debugging of route table manager events.
ipc—Control the debugging of all route table manager interprocess communications.
next-hop—Control the debugging of the route table manager handling of next hops.
packets—Control the debugging of the route table manager handling of route exchange packets.
rib—Control the debugging of route table manager communication with the route table.
vpn vpn-id—Specify the VPN in which to perform debugging.
SNMP
[no] debug snmp events [level (high | low)]
Control debugging for all SNMP events:
level (high | low)—Set the detail of the comments logged by the debugging operation. The default level, low, provides comments sufficient to help you understand the actions that are occurring. The level high provides greater detail for the live debugging that might typically be performed by the Viptela engineering team.
System Manager
[no] debug sysmgr all
Control debugging for the system manager.
TCP Optimization Process
[no] debug tcpd [level (high | low)]
Control debugging for TCP optimization.
level (high | low)—Set the detail of the comments logged by the debugging operation. The default level, low, provides comments sufficient to help you understand the actions that are occurring. The level high provides greater detail for the live debugging that might typically be performed by the Viptela engineering team.
Transport Process
[no] debug transport events [level (high | low)]
Control debugging for all vtracker transport process events. The vtracker process pings the vBond orchestrator every second.
level (high | low)—Set the detail of the comments logged by the debugging operation. The default level, low, provides comments sufficient to help you understand the actions that are occurring. The level high provides greater detail for the live debugging that might typically be performed by the Viptela engineering team.
Tunnel Table Manager
[no] debug ttm events
Control debugging for all tunnel table manager events.
Vdaemon Process
[no] debug vdaemon (all | confd | events | misc | packets)
Control debugging for vdaemon, the Viptela software process:
all—Control the debugging of all vdaemon process functions.
confd—Control the debugging of vdaemon process CLI functions.
events—Control the debugging of vdaemon process events.
misc—Control the debugging of miscellaneous vdaemon process events.
packets—Control the debugging of all vdaemon process packets.
VRRP
[no] debug vrrp (all | events | packets) vpn vpn-id
Control debugging for the Virtual Router Redundancy Protocol (VRRP):
all—Control the debugging of all VRRP events and packets.
events—Control the debugging of VRRP events.
packets—Control the debugging of VRRP packets.

Output Fields

The output fields are self-explanatory.

Release Information

Command introduced in Viptela Software Release 14.1.
Starting with Release 16.3, output is placed in the /var/log/tmplog/vdebug file, not the /var/log/vdebug file.

  • Was this article helpful?