Hi  moquery -c eqptPsu - you can use grep to gather the important information - for example: moquery -c eqptPsu -x 'order-by=eqptPsu.dn|asc' | egrep "#|dn|ser|operSt"   HTH Marcel   ... View more

Hi Have you tried to query just the uribv4Route-MO?   https:// {{IP}} /api/class/uribv4Route.json?query-target-filter=wcard(uribv4Route.dn,"<TENANT>:<VRF>")&rsp-subtree=full&order-by=uribv4Route.dn|asc (you need to replace <TENANT> and <VRF> with the corresponding names...)   HTH Marcel ... View more

It's the TEP-range which is different in both fabrics. You cannot change this range after initial configuration. Try to setup your lab with the identical TEP-range as your production system.   Marcel ... View more

You are using a AES-encryption key on your production ACI. If you want to import this configuration in your lab, you must configure the same AES-key in your lab-ACI before importing the config (Admin > AAA > AES Encryption...).    ... View more

Hello   You can query this information with the following command:   moquery -c infraAttEntityP -x 'query-target-filter=eq(infraAttEntityP.name,"<AEP-NAME>") rsp-subtree=full rsp-subtree-class=infraRtAttEntP' Or you can also query direct for the infraRtAttEntP: moquery -c infraRtAttEntP -f 'infra.RtAttEntP.dn*"attentp-<AEP-NAME>/"' | grep tDn   You have to replace <AEP-NAME> with the name of your AEP. For example to get all Policy-Groups which have the AEP "AEP-TEST" configured:   moquery -c infraAttEntityP -x 'query-target-filter=eq(infraAttEntityP.name,"AEP-TEST") rsp-subtree=full rsp-subtree-class=infraRtAttEntP' moquery -c infraRtAttEntP -f 'infra.RtAttEntP.dn*"attentp-AEP-TEST/"' | grep tDn   HTH Marcel ... View more

Hi    You can query the ethpmPhysIf MO and check the "operSt"-attribut (up/down). For example via moquery to get all "down" interfaces: moquery -c ethpmPhysIf -x 'query-target-filter=eq(ethpmPhysIf.operSt,"down") order-by=ethpmPhysIf.dn|asc' | egrep "dn|operSt\b"   Or check the l1PhysIf MO - all unused ports usually report a usage of "discovery": moquery -c l1PhysIf -x 'query-target-filter=eq(l1PhysIf.usage,"discovery") order-by=l1PhysIf.dn|asc' | egrep "dn|discovery"   HTH Marcel ... View more

Hi    The L3out configured with SVIs is correct. Also configuring your "SVI-IP" as a secondary address. But your "physical IP" must be the same for all ports on the same leaf. Leaf-111 eth1/5 IP:  10.1.1.11/24 Secondary-IP: 10.1.1.10/24 Leaf-111 eth1/6 IP: 10.1.1.11/24 Secondary-IP: 10.1.1.10/24   You must change the interface IP only if you connect the FW on another leaf - for example if the FW members are connected on leaf-111 and leaf-112 then the IP will change: Leaf-111 eth1/5 IP:  10.1.1.11/24 Secondary-IP: 10.1.1.10/24 Leaf-112 eth1/5 IP: 10.1.1.12/24 Secondary-IP: 10.1.1.10/24   HTH Marcel       ... View more

Hi Yoann   Because the wcard-Filter is not working with the fvCEp.ip attribute you can use ge and le filters: GET https://APIC/api/class/fvCEp.json?query-target-filter=and(ge(fvCEp.ip,"192.168.0.0"),le(fvCEp.ip,"192.168.255.255")) HTH Marcel ... View more

In a LB-PBR scenario your VIPs will typically be part of the LB-service BD itself, so the VIP-subnet is directly connected to ACI. Have a look at the following whitepaper: https://www.cisco.com/c/en/us/solutions/data-center-virtualization/application-centric-infrastructure/white-paper-c11-739971.html   HTH     ... View more