cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
747
Views
0
Helpful
2
Replies

ACI Ftriage failed

a12288
Level 3
Level 3

Hi, Community.

I am troubleshooting a potential L3Out issue so I tried ftriage to investigate, somehow I cannot have ftriage completed, not sure what I missed. Thanks.

ACI-APIC1# ftriage -user admin route -ii L3OUT:common:out-CCS-L3Out -sip 172.18.1.10 -dip 8.8.8.8
Starting ftriage
Log file name for the current run is: ftlog_2022-11-18-12-05-37-736.txt
2022-11-18 12:05:37,741 INFO /controller/bin/ftriage -user admin route -ii L3OUT:common:out-CCS-L3Out -s ip 172.18.1.10 -dip 131.104.136.11
Request password info for username: admin
Password:
2022-11-18 12:05:51,190 INFO ftriage: pif:703 LEAF111: L3 with IFS: eth1/2 L3Type: rtdif L3IP: 172 .16.127.9 Encap: untagged
2022-11-18 12:06:20,906 INFO ftriage: pif:703 LEAF101: L3 with IFS: eth1/2 L3Type: rtdif L3IP: 172 .16.127.1 Encap: untagged
2022-11-18 12:06:47,569 INFO ftriage: main:2064 Invoking ftriage with username: admin
2022-11-18 12:06:49,095 INFO ftriage: main:1491 Enable Async parellel ELAM with 2 nodes
2022-11-18 12:06:49,104 INFO ftriage: main:1200 Async Peforming ELAM on {LEAF111: [('Eth1/2', 'untagged')]}
2022-11-18 12:06:49,105 INFO ftriage: main:1200 Async Peforming ELAM on {LEAF101: [('Eth1/2', 'untagged')]}
2022-11-18 12:06:49,106 INFO ftriage: main:1210 Async ElamJoin checking ELAM results on all nodes
2022-11-18 12:07:59,498 ERROR ftriage: main:1237 Async Elam capture failed on all ingress nodes
2022-11-18 12:07:59,499 ERROR ftriage: main:1237 Async Elam capture failed on all ingress nodes
ACI-APIC1#

Leo

2 Replies 2

a12288
Level 3
Level 3

The EP 172.18.1.0 is at CCS tenant and CCS-L3Out is at common tenant.

Sergiu.Daniluk
VIP Alumni
VIP Alumni

Hi @a12288 

I think you are using wrong values for "-ii" argument.

apic3# ftriage route -h

usage: ftriage route [-h] [-ii intf] [-ie encap] [-iie encap] [-ei intf]
                     [-ee encap] [-eie encap] -dip addr [-sip addr]
                     [-l4-type l4type] [-l4-src-port l4srcport]
                     [-l4-dst-port l4dstport] [-mpls] [-mplslabel0 mplslabel0]
                     [-mplslabel1 mplslabel1]

optional arguments:
  -h, --help            show this help message and exit
  -ii intf              ingress if (siteid::(node:if|LEAF:<leaf-name>|VPC:<vpc-name>[:<leaf-name>,..]|PC:<pc-name>[:<leaf-name>,..]|L3OUT:<tnname>:<l3name>)[+vtep])

Basically, -ii is the ingress interface, which in your case is the egress interface (dip = 8.8.8.8). 

Try using the correct interface using the format from above.

 

Take care,

Sergiu

Review Cisco Networking for a $25 gift card

Save 25% on Day-2 Operations Add-On License