How to find what EPGs are assigned to a Port?

[Nathan Young]

What EPGs are assigned to the port that is connected to my device?  This is a question I get from time to time, but I cannot find this information anywhere in the ACI GUI.  This question would come up for verification or troubleshooting purposes for devices, such as UCS, that require multiple EPGs to be assigned to their port(s).  If 100 EPGs need to be assigned to a port, how do you verify all 100 are besides manually clicking each EPG and finding that port or going the CLI of the leaf switch?  This seems to be such a simple request, but other then getting into a Leaf switch and finding via CLI, it is nowhere to be found in the GUI.  I know the new 2.2 code allows apps to be developed by third parties on the APICs, but this is basic information that Cisco should provide.  It would also help in cleaning up when ports are no long used, instead of having to follow a fault trail until they are all cleared.  If I am wrong on this, please let me know where to find this information in the GUI.

[ahojmark]

How about moquery:

CON-LAB-APIC1# bash

admin@CON-LAB-APIC1:~> moquery -c fvStPathAtt | grep dn | grep 'eth1/9'

dn           : uni/epp/fv-[uni/tn-DEMO/ap-DEMO/epg-VLAN0102]/node-101/stpathatt-[eth1/9]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-DEMO/epg-VLAN0102]/node-102/stpathatt-[eth1/9]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-DEMO/epg-VLAN0101]/node-102/stpathatt-[eth1/9]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-DEMO/epg-VLAN0101]/node-101/stpathatt-[eth1/9]

admin@CON-LAB-APIC1:~> moquery -c fvDyPathAtt | grep dn | grep 'eth1/9'

dn           : uni/epp/fv-[uni/tn-DEMO/ap-VMI/epg-APP-SERVERS]/node-102/dyatt-[topology/pod-1/paths-102/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-VMI/epg-APP-SERVERS]/node-101/dyatt-[topology/pod-1/paths-101/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-MITH/ap-DOCKER-HOSTS/epg-DOCKERHOSTS]/node-101/dyatt-[topology/pod-1/paths-101/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-MITH/ap-DOCKER-HOSTS/epg-DOCKERHOSTS]/node-102/dyatt-[topology/pod-1/paths-102/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-UCSD/epg-BMA01]/node-102/dyatt-[topology/pod-1/paths-102/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-UCSD/epg-BMA01]/node-101/dyatt-[topology/pod-1/paths-101/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-infra/ap-access/epg-default]/node-101/dyatt-[topology/pod-1/paths-101/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-L47/epg-SERVERS]/node-102/dyatt-[topology/pod-1/paths-102/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-L47/epg-SERVERS]/node-101/dyatt-[topology/pod-1/paths-101/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-UCSD/epg-ESX01]/node-102/dyatt-[topology/pod-1/paths-102/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-UCSD/epg-ESX01]/node-101/dyatt-[topology/pod-1/paths-101/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-VMI/epg-CLIENTS]/node-101/dyatt-[topology/pod-1/paths-101/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-VMI/epg-CLIENTS]/node-102/dyatt-[topology/pod-1/paths-102/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-L47/epg-CLIENTS]/node-102/dyatt-[topology/pod-1/paths-102/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-DEMO/ap-L47/epg-CLIENTS]/node-101/dyatt-[topology/pod-1/paths-101/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-ACP/ap-ANYCAST-DOMAIN/epg-ANYCAST-1]/node-101/dyatt-[topology/pod-1/paths-101/pathep-[eth1/9]]

dn           : uni/epp/fv-[uni/tn-ACP/ap-ANYCAST-DOMAIN/epg-ANYCAST-1]/node-102/dyatt-[topology/pod-1/paths-102/pathep-[eth1/9]]

Or possibly show vlan ext:

CON-LAB-LEAF1# show vlan ext | grep Eth1/9

2    infra:default                    active    Eth1/1, Eth1/2, Eth1/3, Eth1/9,

4    DEMO:UCSD:BMA01                  active    Eth1/9                         

5    DEMO:VMI-APP-SERVERS             active    Eth1/9, Eth1/10, Eth1/19,      

8    DEMO:VMI:APP-SERVERS             active    Eth1/9                         

9    DEMO:UCSD-ESX01                  active    Eth1/9                         

10   DEMO:UCSD:ESX01                  active    Eth1/9                         

11   DEMO:L47-CLIENTS                 active    Eth1/9, Eth1/10, Eth1/19,      

12   DEMO:L47:CLIENTS                 active    Eth1/9                         

13   DEMO:VMI-CLIENTS                 active    Eth1/9, Eth1/10, Eth1/19,      

14   DEMO:VMI:CLIENTS                 active    Eth1/9                         

18   DEMO:DEMO-VLAN101                active    Eth1/9, Eth1/48                

19   DEMO:DEMO:VLAN0101               active    Eth1/9, Eth1/48                

22   DEMO:DEMO-VLAN102                active    Eth1/9, Eth1/48                

23   DEMO:DEMO:VLAN0102               active    Eth1/9, Eth1/48                

30   ACP:ANYCAST-1                    active    Eth1/9, Eth1/48                

31   ACP:ANYCAST-DOMAIN:ANYCAST-1     active    Eth1/9                         

38   DEMO:L47-SERVERS                 active    Eth1/9, Eth1/10, Eth1/19,      

39   DEMO:L47:SERVERS                 active    Eth1/9                         

40   DEMO:UCSD-BMA01                  active    Eth1/9                         

44   DEMO:VMI:CLIENTS                 active    Eth1/9                         

45   MITH:DOCKERHOST                  active    Eth1/9                         

46   MITH:DOCKER-HOSTS:DOCKERHOSTS    active    Eth1/9                         

48   DEMO:VMI:APP-SERVERS             active    Eth1/9                         

HTH,

-A

[sebas.jacobs]

This one works as well.

Could do a api call as well to check upon tagging information for vPC's.

{{protocol}}://{{apic}}/api/node/class/vpcIf.json?query-target-filter=and(wcard(vpcIf.accBndlGrpDn,""))

Or approach from the epg side and request all static bindings for a specific epg.

{{protocol}}://{{apic}}/api/mo/uni/tn-LAB.json?query-target=subtree&target-subtree-class=fvRsPathAtt&query-target-filter=wcard(fvRsPathAtt.dn,"uni/tn-LAB/ap-anp_LAB/epg-epg_LAB")