01-19-2017 06:42 PM - edited 03-01-2019 05:08 AM
I have a pair of switches that are deployed with only 2 VLANs in 2 different EPGs
one for PXE boot - using 802.1p,
one for normal tagged traffic, using trunk.
so I am thinking to use static binding(leaves) to create less objects. My question is, if I am using vPC, will it still work ? The following is from ACI doc, but did not mention any restrictions for vPC or PC
If a leaf switch is configured for static binding (leaves) under an EPG, the following restrictions apply:
Interfaces in that switch cannot be assigned IP addresses .
Also, what class can I query on the switch to verify that they've been deployed correctly to each switch port ? I've tried 'stpDomFabEncap' and 'fvIfConn' , but they don't give me exactly what I am looking for.
Thanks!
Solved! Go to Solution.
01-20-2017 05:03 AM
Hello
Thanks for using SupportForums
Just tested in the lab and yes it will deploy on vPC/PC. To verify if it has been deployed, simply run "show vlan ex" and you will see the BD/EPG applied to every port and port-channel
31 dpita-tenant:dpita-BD1 active Eth1/2, Eth1/3, Eth1/4, Eth1/5,
Eth1/6, Eth1/7, Eth1/8, Eth1/9,
Eth1/10, Eth1/11, Eth1/12,
Eth1/13, Eth1/14, Eth1/15,
Eth1/16, Eth1/17, Eth1/18,
Eth1/19, Eth1/20, Eth1/21,
Eth1/22, Eth1/23, Eth1/24,
Eth1/25, Eth1/26, Eth1/27,
Eth1/28, Eth1/33, Eth1/34,
Eth1/35, Eth1/36, Eth1/37,
Eth1/38, Eth1/39, Eth1/40,
Eth1/41, Eth1/42, Eth1/43,
Eth1/44, Eth1/45, Eth1/46,
Eth1/47, Eth1/48, Eth115/1/1,
Eth115/1/2, Eth115/1/3,
Eth115/1/4, Eth115/1/5,
Eth115/1/6, Eth115/1/7,
Eth115/1/8, Eth115/1/9,
Eth115/1/10, Eth115/1/11,
Eth115/1/12, Eth115/1/13,
Eth115/1/14, Eth115/1/15,
Eth115/1/16, Eth115/1/17,
Eth115/1/18, Eth115/1/19,
Eth115/1/20, Eth115/1/21,
Eth115/1/22, Eth115/1/23,
Eth115/1/24, Eth115/1/25,
Eth115/1/26, Eth115/1/27,
Eth115/1/28, Eth115/1/29,
Eth115/1/30, Eth115/1/31,
Eth115/1/32, Po1, Po3, Po5
32 dpita-tenant:dpita-AP:dpita-EPG1 active Eth1/2, Eth1/3, Eth1/4, Eth1/5,
Eth1/6, Eth1/7, Eth1/8, Eth1/9,
Eth1/10, Eth1/11, Eth1/12,
Eth1/13, Eth1/14, Eth1/15,
Eth1/16, Eth1/17, Eth1/18,
Eth1/19, Eth1/20, Eth1/21,
Eth1/22, Eth1/23, Eth1/24,
Eth1/25, Eth1/26, Eth1/27,
Eth1/28, Eth1/33, Eth1/34,
Eth1/35, Eth1/36, Eth1/37,
Eth1/38, Eth1/39, Eth1/40,
Eth1/41, Eth1/42, Eth1/43,
Eth1/44, Eth1/45, Eth1/46,
Eth1/47, Eth1/48, Eth115/1/1,
Eth115/1/2, Eth115/1/3,
Eth115/1/4, Eth115/1/5,
Eth115/1/6, Eth115/1/7,
Eth115/1/8, Eth115/1/9,
Eth115/1/10, Eth115/1/11,
Eth115/1/12, Eth115/1/13,
Eth115/1/14, Eth115/1/15,
Eth115/1/16, Eth115/1/17,
Eth115/1/18, Eth115/1/19,
Eth115/1/20, Eth115/1/21,
Eth115/1/22, Eth115/1/23,
Eth115/1/24, Eth115/1/25,
Eth115/1/26, Eth115/1/27,
Eth115/1/28, Eth115/1/29,
Eth115/1/30, Eth115/1/31,
Eth115/1/32, Po1, Po3, Po5
31 enet CE vxlan-15990734
32 enet CE vlan-2377
Finally, the object you are looking for is fvRsNodeAtt
admin@rtp-f2-p1-apic1:~> moquery -c fvRsNodeAtt
Total Objects shown: 1
# fv.RsNodeAtt
tDn : topology/pod-1/node-215
childAction :
descr :
dn : uni/tn-dpita-tenant/ap-dpita-AP/epg-dpita-EPG1/rsnodeAtt-[topology/pod-1/node-215]
encap : vlan-2377
forceResolve : yes
instrImedcy : immediate
lcC :
lcOwn : local
modTs : 2017-01-20T07:38:58.943-05:00
mode : regular
rType : mo
rn : rsnodeAtt-[topology/pod-1/node-215]
state : unformed
stateQual : none
status :
tCl : fabricNode
tType : mo
uid : 15374
admin@rtp-f2-p1-apic1:~>
You are on the right track with fvIfConn, the interesting part with static leaf is that it skips the concrete object for path and i guess the logic dictates if there is no specific path, apply to all ports. Typically the way a vlan gets on a port is
fvEpP > fvLocale > fvDyPathAtt | fvStPathAtt > fvIfConn
Hope that helps!
01-20-2017 05:03 AM
Hello
Thanks for using SupportForums
Just tested in the lab and yes it will deploy on vPC/PC. To verify if it has been deployed, simply run "show vlan ex" and you will see the BD/EPG applied to every port and port-channel
31 dpita-tenant:dpita-BD1 active Eth1/2, Eth1/3, Eth1/4, Eth1/5,
Eth1/6, Eth1/7, Eth1/8, Eth1/9,
Eth1/10, Eth1/11, Eth1/12,
Eth1/13, Eth1/14, Eth1/15,
Eth1/16, Eth1/17, Eth1/18,
Eth1/19, Eth1/20, Eth1/21,
Eth1/22, Eth1/23, Eth1/24,
Eth1/25, Eth1/26, Eth1/27,
Eth1/28, Eth1/33, Eth1/34,
Eth1/35, Eth1/36, Eth1/37,
Eth1/38, Eth1/39, Eth1/40,
Eth1/41, Eth1/42, Eth1/43,
Eth1/44, Eth1/45, Eth1/46,
Eth1/47, Eth1/48, Eth115/1/1,
Eth115/1/2, Eth115/1/3,
Eth115/1/4, Eth115/1/5,
Eth115/1/6, Eth115/1/7,
Eth115/1/8, Eth115/1/9,
Eth115/1/10, Eth115/1/11,
Eth115/1/12, Eth115/1/13,
Eth115/1/14, Eth115/1/15,
Eth115/1/16, Eth115/1/17,
Eth115/1/18, Eth115/1/19,
Eth115/1/20, Eth115/1/21,
Eth115/1/22, Eth115/1/23,
Eth115/1/24, Eth115/1/25,
Eth115/1/26, Eth115/1/27,
Eth115/1/28, Eth115/1/29,
Eth115/1/30, Eth115/1/31,
Eth115/1/32, Po1, Po3, Po5
32 dpita-tenant:dpita-AP:dpita-EPG1 active Eth1/2, Eth1/3, Eth1/4, Eth1/5,
Eth1/6, Eth1/7, Eth1/8, Eth1/9,
Eth1/10, Eth1/11, Eth1/12,
Eth1/13, Eth1/14, Eth1/15,
Eth1/16, Eth1/17, Eth1/18,
Eth1/19, Eth1/20, Eth1/21,
Eth1/22, Eth1/23, Eth1/24,
Eth1/25, Eth1/26, Eth1/27,
Eth1/28, Eth1/33, Eth1/34,
Eth1/35, Eth1/36, Eth1/37,
Eth1/38, Eth1/39, Eth1/40,
Eth1/41, Eth1/42, Eth1/43,
Eth1/44, Eth1/45, Eth1/46,
Eth1/47, Eth1/48, Eth115/1/1,
Eth115/1/2, Eth115/1/3,
Eth115/1/4, Eth115/1/5,
Eth115/1/6, Eth115/1/7,
Eth115/1/8, Eth115/1/9,
Eth115/1/10, Eth115/1/11,
Eth115/1/12, Eth115/1/13,
Eth115/1/14, Eth115/1/15,
Eth115/1/16, Eth115/1/17,
Eth115/1/18, Eth115/1/19,
Eth115/1/20, Eth115/1/21,
Eth115/1/22, Eth115/1/23,
Eth115/1/24, Eth115/1/25,
Eth115/1/26, Eth115/1/27,
Eth115/1/28, Eth115/1/29,
Eth115/1/30, Eth115/1/31,
Eth115/1/32, Po1, Po3, Po5
31 enet CE vxlan-15990734
32 enet CE vlan-2377
Finally, the object you are looking for is fvRsNodeAtt
admin@rtp-f2-p1-apic1:~> moquery -c fvRsNodeAtt
Total Objects shown: 1
# fv.RsNodeAtt
tDn : topology/pod-1/node-215
childAction :
descr :
dn : uni/tn-dpita-tenant/ap-dpita-AP/epg-dpita-EPG1/rsnodeAtt-[topology/pod-1/node-215]
encap : vlan-2377
forceResolve : yes
instrImedcy : immediate
lcC :
lcOwn : local
modTs : 2017-01-20T07:38:58.943-05:00
mode : regular
rType : mo
rn : rsnodeAtt-[topology/pod-1/node-215]
state : unformed
stateQual : none
status :
tCl : fabricNode
tType : mo
uid : 15374
admin@rtp-f2-p1-apic1:~>
You are on the right track with fvIfConn, the interesting part with static leaf is that it skips the concrete object for path and i guess the logic dictates if there is no specific path, apply to all ports. Typically the way a vlan gets on a port is
fvEpP > fvLocale > fvDyPathAtt | fvStPathAtt > fvIfConn
Hope that helps!
01-20-2017 05:24 AM
Thanks Daniel ! This is very helpful !
The disadvantage is that you can't pre-configure the leaf port, not even with script. The leaf itself has to be active.... however, for static path binding interface, I can use a script to deploy configurations even if the leaf is not yet part of the fabric.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide