Bidirectional Forwarding Detection Flap-Reason Definitions on Cisco vEdge Routers
Available Languages
Download Options
Updated:April 1, 2020
Document ID:215359
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Contents
Introduction
This document describes the various Bidirectional Forwarding Detection (BFD) flap-reasons on a Cisco vEdge router.
Prerequisites
Requirements
Cisco recommends that you have knowledge of Cisco SDWAN solution.
Components Used
This document is based on Cisco cloud vEdge router running 19.2.1.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Topology Overview
This document is not restricted to any specific topology.
IP addresses and colors of some important components in this document:
| Component | System-IP | VPN 0 IP / Color | VPN 0 IP / Color |
| VEDGE-1 | 10.13.13.13 | 192.168.1.4 / mpls | 192.168.2.4 / mpls |
| VEDGE-2 | 10.15.15.15 | 192.168.1.8 / biz-internet | 192.168.2.8 / biz-internet |
| vSmart | 10.8.8.8 | 192.168.1.3 / default | NA |
| vManage | 10.7.7.7 | 192.168.1.1 / default | NA |
BFD States
The possible values of 'flap-reason' on a Cisco vEdge router are:
1. bfd-deleted - BFD goes down because the control plane has deleted it.
You raise two notifications when BFD is deleted. One for BFD down and one when BFD gets deleted.
2. timeout - No BFD response from the remote end.
3. remote-down - Remote end sent a BFD packet that indicates that it has gone to down-state.4.
4. na - not applicable. This is set when the BFD session is created for the first time and when the BFD session comes up.
Scenarios
Scenario 1. flap-reason:bfd-deleted
Perform a port-hop on VEDGE-1 router and reproduce this scenario:
HUB-1# request port-hop color biz-internet
VEDGE-1# show log tail -f /var/log/tmplog/vdebug
local7.debug: Mar 20 09:29:21 VEDGE-1 VDAEMON[1136]: vdaemon_disable_my_tloc[1308]: %VDAEMON_DBG_EVENTS-1: Disabling tloc ge0_1.
local7.debug: Mar 20 09:29:21 VEDGE-1 VDAEMON[1136]: vdaemon_send_tloc_info[8282]: %VDAEMON_DBG_MISC-1: Sending TLOC: ifname:ge0_1 color:biz-internet spi:1499 smarts:1 manages:1 state:DOWN LR encap: 0 LR hold time : 7000 Pairwise-Keys Disabled key-id 0
local7.info: Mar 20 09:29:21 VEDGE-1 VDAEMON[1136]: %Viptela-VEDGE-1-vdaemon-6-INFO-1400002: Notification: 3/20/2020 9:29:21 control-connection-state-change severity-level:major host-name:"VEDGE-1" system-ip:10.13.13.13 personality:vEdge peer-type:vsmart peer-system-ip:10.8.8.8 peer-vmanage-system-ip:0.0.0.0 public-ip:192.168.1.3 public-port:12946 src-color:biz-internet remote-color:default uptime:"0:00:35:57" new-state:down
local7.info: Mar 20 09:29:21 VEDGE-1 VDAEMON[1136]: %Viptela-VEDGE-1-vdaemon-6-INFO-1400002: Notification: 3/20/2020 9:29:21 control-connection-state-change severity-level:major host-name:"VEDGE-1" system-ip:10.13.13.13 personality:vEdge peer-type:vmanage peer-system-ip:10.7.7.7 peer-vmanage-system-ip:0.0.0.0 public-ip:192.168.1.1 public-port:12946 src-color:biz-internet remote-color:mpls uptime:"0:01:56:34" new-state:down
local7.info: Mar 20 09:29:21 VEDGE-1 FTMD[1126]: %Viptela-VEDGE-1-ftmd-6-INFO-1400002: Notification: 3/20/2020 9:29:21 bfd-state-change severity-level:major host-name:"VEDGE-1" system-ip:10.13.13.13 src-ip:192.168.2.4 dst-ip:192.168.1.6 proto:ipsec src-port:12406 dst-port:12347 local-system-ip:10.13.13.13 local-color:"biz-internet" remote-system-ip:10.14.14.14 remote-color:"mpls" new-state:down deleted:false flap-reason:bfd-deleted
Check BFD and control connection uptime on biz-internet:
VEDGE-1# show control connections | t
LOCAL LOCAL CFG V
PEER SITE DOMAIN PRIVATE PRIVATE PUBLIC PUBLIC SYSTEM PRIVATE PRIVATE CONTROLLER SYSTEM ORG BEHIND
INSTANCE TYPE ID ID IP PORT IP PORT IP PROTOCOL LOCAL COLOR REMOTE COLOR IP PORT STATE UPTIME GROUP ID IP NAME PROXY
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
0 vsmart 8 1 192.168.1.4 12366 192.168.1.3 12946 10.8.8.8 dtls mpls default 192.168.1.3 12946 up 0:00:03:47 0 - - No
0 vsmart 8 1 192.168.2.4 12426 192.168.1.3 12946 10.8.8.8 dtls biz-internet default 192.168.1.3 12946 up 0:00:01:52 0 - - No
0 vbond 0 0 192.168.1.4 12366 192.168.1.10 12346 0.0.0.0 dtls mpls mpls 192.168.1.10 12346 up 0:00:03:47 0 - - -
0 vbond 0 0 192.168.2.4 12426 192.168.1.10 12346 0.0.0.0 dtls biz-internet biz-internet 192.168.1.10 12346 up 0:00:00:31 0 - - -
0 vmanage 8 0 192.168.2.4 12426 192.168.1.1 12946 10.7.7.7 dtls biz-internet mpls 192.168.1.1 12946 up 0:00:01:52 0 - - No
VEDGE-1# sh bfd sess | t
SRC DST SITE DETECT TX
SRC IP DST IP PROTO PORT PORT SYSTEM IP ID LOCAL COLOR COLOR STATE MULTIPLIER INTERVAL UPTIME TRANSITIONS
---------------------------------------------------------------------------------------------------------------------------------------------
192.168.1.4 192.168.1.6 ipsec 12366 12347 10.14.14.14 14 mpls mpls up 7 1000 0:00:03:48 0
192.168.1.4 192.168.2.6 ipsec 12366 12387 10.14.14.14 14 mpls biz-internet up 7 1000 0:00:03:48 0
192.168.2.4 192.168.1.6 ipsec 12426 12347 10.14.14.14 14 biz-internet mpls up 7 1000 0:00:01:55 0
192.168.2.4 192.168.2.6 ipsec 12426 12387 10.14.14.14 14 biz-internet biz-internet up 7 1000 0:00:01:55 0
192.168.1.4 192.168.1.8 ipsec 12366 12406 10.15.15.15 15 mpls mpls up 7 1000 0:00:03:48 0
192.168.1.4 192.168.2.8 ipsec 12366 12366 10.15.15.15 15 mpls biz-internet up 7 1000 0:00:03:48 0
192.168.2.4 192.168.1.8 ipsec 12426 12406 10.15.15.15 15 biz-internet mpls up 7 1000 0:00:01:55 0
192.168.2.4 192.168.2.8 ipsec 12426 12366 10.15.15.15 15 biz-internet biz-internet up 7 1000 0:00:01:55 0
192.168.1.4 192.168.1.11 ipsec 12366 12346 10.16.16.16 16 mpls mpls up 7 1000 0:00:03:48 0
192.168.1.4 192.168.2.11 ipsec 12366 12426 10.16.16.16 16 mpls biz-internet up 7 1000 0:00:03:48 0
192.168.2.4 192.168.1.11 ipsec 12426 12346 10.16.16.16 16 biz-internet mpls up 7 1000 0:00:01:55 0
192.168.2.4 192.168.2.11 ipsec 12426 12426 10.16.16.16 16 biz-internet biz-internet up 7 1000 0:00:01:55 0
192.168.1.4 192.168.1.12 ipsec 12366 12426 10.17.17.17 17 mpls mpls up 7 1000 0:00:03:48 0
192.168.1.4 192.168.2.12 ipsec 12366 12406 10.17.17.17 17 mpls biz-internet up 7 1000 0:00:03:48 0
192.168.2.4 192.168.1.12 ipsec 12426 12426 10.17.17.17 17 biz-internet mpls up 7 1000 0:00:01:55 0
192.168.2.4 192.168.2.12 ipsec 12426 12406 10.17.17.17 17 biz-internet biz-internet up 7 1000 0:00:01:55 0
192.168.1.4 192.168.1.14 ipsec 12366 12426 10.18.18.18 18 mpls mpls up 7 1000 0:00:03:48 0
192.168.1.4 192.168.2.14 ipsec 12366 12426 10.18.18.18 18 mpls biz-internet up 7 1000 0:00:03:48 0
192.168.2.4 192.168.1.14 ipsec 12426 12426 10.18.18.18 18 biz-internet mpls up 7 1000 0:00:01:55 0
192.168.2.4 192.168.2.14 ipsec 12426 12426 10.18.18.18 18 biz-internet biz-internet up 7 1000 0:00:01:55 0
192.168.1.4 192.168.3.40 ipsec 12366 12366 10.19.19.19 19 mpls mpls up 7 1000 0:00:03:48 0
192.168.1.4 192.168.4.40 ipsec 12366 12366 10.19.19.19 19 mpls biz-internet up 7 1000 0:00:03:48 0
192.168.2.4 192.168.3.40 ipsec 12426 12366 10.19.19.19 19 biz-internet mpls up 7 1000 0:00:01:55 0
192.168.2.4 192.168.4.40 ipsec 12426 12366 10.19.19.19 19 biz-internet biz-internet up 7 1000 0:00:01:55 0
You can also clear a control connection on VEDGE-1 in order to test this scenario (which also disables a TLOC):
local1.info: Mar 20 09:34:20 VEDGE-1 confd[897]: audit user: admin/60155 CLI 'clear control connections'
local7.info: Mar 20 09:34:20 VEDGE-1 VDAEMON[1136]: %Viptela-VEDGE-1-vdaemon-6-INFO-1400002: Notification: 3/20/2020 9:34:20 control-connection-state-change severity-level:major host-name:"VEDGE-1" system-ip:10.13.13.13 personality:vEdge peer-type:vsmart peer-system-ip:10.8.8.8 peer-vmanage-system-ip:0.0.0.0 public-ip:192.168.1.3 public-port:12946 src-color:biz-internet remote-color:default uptime:"0:00:00:51" new-state:down
local7.info: Mar 20 09:34:20 VEDGE-1 VDAEMON[1136]: %Viptela-VEDGE-1-vdaemon-6-INFO-1400002: Notification: 3/20/2020 9:34:20 control-connection-state-change severity-level:major host-name:"VEDGE-1" system-ip:10.13.13.13 personality:vEdge peer-type:vmanage peer-system-ip:10.7.7.7 peer-vmanage-system-ip:0.0.0.0 public-ip:192.168.1.1 public-port:12946 src-color:biz-internet remote-color:mpls uptime:"0:00:01:09" new-state:down
local7.info: Mar 20 09:34:20 VEDGE-1 FTMD[1126]: %Viptela-VEDGE-1-ftmd-6-INFO-1400002: Notification: 3/20/2020 9:34:20 bfd-state-change severity-level:major host-name:"VEDGE-1" system-ip:10.13.13.13 src-ip:192.168.2.4 dst-ip:192.168.1.6 proto:ipsec src-port:12426 dst-port:12347 local-system-ip:10.13.13.13 local-color:"biz-internet" remote-system-ip:10.14.14.14 remote-color:"mpls" new-state:down deleted:false flap-reason:bfd-deleted
Check the uptime on mpls and biz-internet colors this time:
VEDGE-1# sh bfd sess | t
SRC DST SITE DETECT TX
SRC IP DST IP PROTO PORT PORT SYSTEM IP ID LOCAL COLOR COLOR STATE MULTIPLIER INTERVAL UPTIME TRANSITIONS
---------------------------------------------------------------------------------------------------------------------------------------------
192.168.1.4 192.168.1.6 ipsec 12366 12347 10.14.14.14 14 mpls mpls up 7 1000 0:00:01:37 2
192.168.1.4 192.168.2.6 ipsec 12366 12387 10.14.14.14 14 mpls biz-internet up 7 1000 0:00:01:37 2
192.168.2.4 192.168.1.6 ipsec 12426 12347 10.14.14.14 14 biz-internet mpls up 7 1000 0:00:01:55 2
192.168.2.4 192.168.2.6 ipsec 12426 12387 10.14.14.14 14 biz-internet biz-internet up 7 1000 0:00:01:55 2
192.168.1.4 192.168.1.8 ipsec 12366 12406 10.15.15.15 15 mpls mpls up 7 1000 0:00:01:37 2
192.168.1.4 192.168.2.8 ipsec 12366 12366 10.15.15.15 15 mpls biz-internet up 7 1000 0:00:01:37 2
192.168.2.4 192.168.1.8 ipsec 12426 12406 10.15.15.15 15 biz-internet mpls up 7 1000 0:00:01:55 2
192.168.2.4 192.168.2.8 ipsec 12426 12366 10.15.15.15 15 biz-internet biz-internet up 7 1000 0:00:01:55 2
192.168.1.4 192.168.1.11 ipsec 12366 12346 10.16.16.16 16 mpls mpls up 7 1000 0:00:01:37 2
192.168.1.4 192.168.2.11 ipsec 12366 12426 10.16.16.16 16 mpls biz-internet up 7 1000 0:00:01:37 2
192.168.2.4 192.168.1.11 ipsec 12426 12346 10.16.16.16 16 biz-internet mpls up 7 1000 0:00:01:55 2
192.168.2.4 192.168.2.11 ipsec 12426 12426 10.16.16.16 16 biz-internet biz-internet up 7 1000 0:00:01:55 2
192.168.1.4 192.168.1.12 ipsec 12366 12426 10.17.17.17 17 mpls mpls up 7 1000 0:00:01:37 2
192.168.1.4 192.168.2.12 ipsec 12366 12406 10.17.17.17 17 mpls biz-internet up 7 1000 0:00:01:37 2
192.168.2.4 192.168.1.12 ipsec 12426 12426 10.17.17.17 17 biz-internet mpls up 7 1000 0:00:01:55 2
192.168.2.4 192.168.2.12 ipsec 12426 12406 10.17.17.17 17 biz-internet biz-internet up 7 1000 0:00:01:55 2
192.168.1.4 192.168.1.14 ipsec 12366 12426 10.18.18.18 18 mpls mpls up 7 1000 0:00:01:37 2
192.168.1.4 192.168.2.14 ipsec 12366 12426 10.18.18.18 18 mpls biz-internet up 7 1000 0:00:01:37 2
192.168.2.4 192.168.1.14 ipsec 12426 12426 10.18.18.18 18 biz-internet mpls up 7 1000 0:00:01:55 2
192.168.2.4 192.168.2.14 ipsec 12426 12426 10.18.18.18 18 biz-internet biz-internet up 7 1000 0:00:01:55 2
192.168.1.4 192.168.3.40 ipsec 12366 12366 10.19.19.19 19 mpls mpls up 7 1000 0:00:01:37 2
192.168.1.4 192.168.4.40 ipsec 12366 12366 10.19.19.19 19 mpls biz-internet up 7 1000 0:00:01:37 2
192.168.2.4 192.168.3.40 ipsec 12426 12366 10.19.19.19 19 biz-internet mpls up 7 1000 0:00:01:55 2
192.168.2.4 192.168.4.40 ipsec 12426 12366 10.19.19.19 19 biz-internet biz-internet up 7 1000 0:00:01:54 3
VEDGE-1# show control connections | t
LOCAL LOCAL CFG V
PEER SITE DOMAIN PRIVATE PRIVATE PUBLIC PUBLIC SYSTEM PRIVATE PRIVATE CONTROLLER SYSTEM ORG BEHIND
INSTANCE TYPE ID ID IP PORT IP PORT IP PROTOCOL LOCAL COLOR REMOTE COLOR IP PORT STATE UPTIME GROUP ID IP NAME PROXY
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
0 vsmart 8 1 192.168.1.4 12366 192.168.1.3 12946 10.8.8.8 dtls mpls default 192.168.1.3 12946 up 0:00:01:41 0 - - No
0 vsmart 8 1 192.168.2.4 12426 192.168.1.3 12946 10.8.8.8 dtls biz-internet default 192.168.1.3 12946 up 0:00:01:59 0 - - No
0 vbond 0 0 192.168.1.4 12366 192.168.1.10 12346 0.0.0.0 dtls mpls mpls 192.168.1.10 12346 up 0:00:01:42 0 - - -
0 vbond 0 0 192.168.2.4 12426 192.168.1.10 12346 0.0.0.0 dtls biz-internet biz-internet 192.168.1.10 12346 up 0:00:00:01 0 - - -
0 vmanage 8 0 192.168.2.4 12426 192.168.1.1 12946 10.7.7.7 dtls biz-internet mpls 192.168.1.1 12946 up 0:00:01:59 0 - - No
Scenario 2. flap-reason:timeout
You can reproduce this scenario by disabling a TLOC (biz-internet in this case) on VEDGE-1 by shutting down an interface in the underlay.
BFD state on VEDGE-2 before you disable a TLOC on VEDGE-1 side:
VEDGE-2# show bfd sessions remote-color mpls system-ip 10.13.13.13 | t
SRC DST SITE DETECT TX
SRC IP DST IP PROTO PORT PORT SYSTEM IP ID LOCAL COLOR COLOR STATE MULTIPLIER INTERVAL UPTIME TRANSITIONS
-------------------------------------------------------------------------------------------------------------------------------------
192.168.1.8 192.168.1.4 ipsec 12406 12366 10.13.13.13 13 mpls mpls up 7 1000 0:00:03:15 2
192.168.2.8 192.168.1.4 ipsec 12366 12366 10.13.13.13 13 biz-internet mpls up 7 1000 0:00:03:15 2
Logs on VEDGE-2 after you reproduce the issue:
local7.info: Mar 20 10:00:04 VEDGE-2 FTMD[1119]: %Viptela-VEDGE-2-ftmd-6-INFO-1400002: Notification: 3/20/2020 10:0:4 bfd-state-change severity-level:major host-name:"VEDGE-2" system-ip:10.15.15.15 src-ip:192.168.1.8 dst-ip:192.168.2.14 proto:ipsec src-port:12406 dst-port:12426 local-system-ip:10.15.15.15 local-color:"mpls" remote-system-ip:10.18.18.18 remote-color:"biz-internet" new-state:down deleted:false flap-reason:timeout
local7.info: Mar 20 10:00:05 VEDGE-2 FTMD[1119]: %Viptela-VEDGE-2-ftmd-6-INFO-1400002: Notification: 3/20/2020 10:0:4 bfd-state-change severity-level:major host-name:"VEDGE-2" system-ip:10.15.15.15 src-ip:192.168.2.8 dst-ip:192.168.4.40 proto:ipsec src-port:12386 dst-port:12366 local-system-ip:10.15.15.15 local-color:"biz-internet" remote-system-ip:10.19.19.19 remote-color:"biz-internet" new-state:down deleted:false flap-reason:timeout
VEDGE-2# show bfd sessions remote-color mpls system-ip 10.13.13.13 | t
SRC DST SITE DETECT TX
SRC IP DST IP PROTO PORT PORT SYSTEM IP ID LOCAL COLOR COLOR STATE MULTIPLIER INTERVAL UPTIME TRANSITIONS
-------------------------------------------------------------------------------------------------------------------------------------
192.168.1.8 192.168.1.4 ipsec 12406 12366 10.13.13.13 13 mpls mpls up 7 1000 0:00:21:56 3
192.168.2.8 192.168.1.4 ipsec 12386 12366 10.13.13.13 13 biz-internet mpls down 7 1000 NA 1
Scenario 3. flap-reason:na
You can reproduce this scenario by doing a no shut on the underlay interface from the previous scenario.
local7.info: Mar 20 10:01:20 VEDGE-2 FTMD[1119]: %Viptela-VEDGE-2-ftmd-6-INFO-1400002: Notification: 3/20/2020 10:1:18 bfd-state-change severity-level:major host-name:"VEDGE-2" system-ip:10.15.15.15 src-ip:192.168.2.8 dst-ip:192.168.1.11 proto:ipsec src-port:12386 dst-port:12346 local-system-ip:10.15.15.15 local-color:"biz-internet" remote-system-ip:10.16.16.16 remote-color:"mpls" new-state:up deleted:false flap-reason:na
local7.info: Mar 20 10:01:20 VEDGE-2 FTMD[1119]: %Viptela-VEDGE-2-ftmd-6-INFO-1400002: Notification: 3/20/2020 10:1:18 bfd-state-change severity-level:major host-name:"VEDGE-2" system-ip:10.15.15.15 src-ip:192.168.1.8 dst-ip:192.168.2.11 proto:ipsec src-port:12406 dst-port:12426 local-system-ip:10.15.15.15 local-color:"mpls" remote-system-ip:10.16.16.16 remote-color:"biz-internet" new-state:up deleted:false flap-reason:na
VEDGE-2# show bfd sessions remote-color mpls system-ip 10.13.13.13 | t
SRC DST SITE DETECT TX
SRC IP DST IP PROTO PORT PORT SYSTEM IP ID LOCAL COLOR COLOR STATE MULTIPLIER INTERVAL UPTIME TRANSITIONS
-------------------------------------------------------------------------------------------------------------------------------------
192.168.1.8 192.168.1.4 ipsec 12406 12366 10.13.13.13 13 mpls mpls up 7 1000 0:00:22:32 3
192.168.2.8 192.168.1.4 ipsec 12386 12366 10.13.13.13 13 biz-internet mpls up 7 1000 0:00:00:04 1
Scenario 4. flap-reason:remote-down
You can reproduce this scenario with the command no control-connections on VEDGE-1 on a specific color (mpls in this case).
Logs on VEDGE-1:
vpn 0
interface ge0/0
ip address 192.168.1.4/24
tunnel-interface
encapsulation ipsec
color mpls
no control-connections
VEDGE-1# show control connections | t
LOCAL LOCAL CFG V
PEER SITE DOMAIN PRIVATE PRIVATE PUBLIC PUBLIC SYSTEM PRIVATE PRIVATE CONTROLLER SYSTEM ORG BEHIND
INSTANCE TYPE ID ID IP PORT IP PORT IP PROTOCOL LOCAL COLOR REMOTE COLOR IP PORT STATE UPTIME GROUP ID IP NAME PROXY
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
0 vsmart 8 1 192.168.2.4 12426 192.168.1.3 12946 10.8.8.8 dtls biz-internet default 192.168.1.3 12946 up 0:00:17:54 0 - - No
0 vbond 0 0 192.168.2.4 12426 192.168.1.10 12346 0.0.0.0 dtls biz-internet biz-internet 192.168.1.10 12346 up 0:00:02:37 0 - - -
0 vmanage 8 0 192.168.2.4 12426 192.168.1.1 12946 10.7.7.7 dtls biz-internet mpls 192.168.1.1 12946 up 0:00:22:44 0 - - No
Logs on VEDGE-2:
local7.info: Mar 20 11:36:40 VEDGE-2 FTMD[1119]: %Viptela-VEDGE-2-ftmd-6-INFO-1400002: Notification: 3/20/2020 11:36:40 bfd-state-change severity-level:major host-name:"VEDGE-2" system-ip:10.15.15.15 src-ip:192.168.1.8 dst-ip:192.168.1.4 proto:ipsec src-port:12406 dst-port:12406 local-system-ip:10.15.15.15 local-color:"mpls" remote-system-ip:10.13.13.13 remote-color:"mpls" new-state:down deleted:false flap-reason:remote-down
local7.info: Mar 20 11:36:40 VEDGE-2 FTMD[1119]: %Viptela-VEDGE-2-ftmd-6-INFO-1400002: Notification: 3/20/2020 11:36:40 bfd-state-change severity-level:major host-name:"VEDGE-2" system-ip:10.15.15.15 src-ip:192.168.2.8 dst-ip:192.168.1.4 proto:ipsec src-port:12386 dst-port:12406 local-system-ip:10.15.15.15 local-color:"biz-internet" remote-system-ip:10.13.13.13 remote-color:"mpls" new-state:down deleted:false flap-reason:remote-down
local7.info: Mar 20 11:36:41 VEDGE-2 FTMD[1119]: %Viptela-VEDGE-2-ftmd-6-INFO-1400002: Notification: 3/20/2020 11:36:41 bfd-state-change severity-level:major host-name:"VEDGE-2" system-ip:10.15.15.15 src-ip:192.168.1.8 dst-ip:192.168.1.4 proto:ipsec src-port:12406 dst-port:12406 local-system-ip:10.15.15.15 local-color:"mpls" remote-system-ip:10.13.13.13 remote-color:"mpls" new-state:up deleted:false flap-reason:na
local7.info: Mar 20 11:36:41 VEDGE-2 FTMD[1119]: %Viptela-VEDGE-2-ftmd-6-INFO-1400002: Notification: 3/20/2020 11:36:41 bfd-state-change severity-level:major host-name:"VEDGE-2" system-ip:10.15.15.15 src-ip:192.168.2.8 dst-ip:192.168.1.4 proto:ipsec src-port:12386 dst-port:12406 local-system-ip:10.15.15.15 local-color:"biz-internet" remote-system-ip:10.13.13.13 remote-color:"mpls" new-state:up deleted:false flap-reason:na
VEDGE-2# show bfd sessions remote-color mpls system-ip 10.13.13.13 | t
SRC DST SITE DETECT TX
SRC IP DST IP PROTO PORT PORT SYSTEM IP ID LOCAL COLOR COLOR STATE MULTIPLIER INTERVAL UPTIME TRANSITIONS
-------------------------------------------------------------------------------------------------------------------------------------
192.168.1.8 192.168.1.4 ipsec 12406 12406 10.13.13.13 13 mpls mpls up 7 1000 0:00:05:27 16
192.168.2.8 192.168.1.4 ipsec 12386 12406 10.13.13.13 13 biz-internet mpls up 7 1000 0:00:05:27 9
Related Information
Contributed by Cisco Engineers
- Utsav DuttCisco TAC Engineer
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)