11-02-2026 10:33 PM
Cisco ACI recently deployed to my office. Our servers have already migrated to the ACI with vpc. Physical servers are also connected as access ports. All the configurations are done and the servers are working. But now we want to connect a switch to the ACI with vpc. We created vpc policy group, but when we tried to create interface port selector on the system auto-generated leaf interface profile, it comes with an error. Can't we reuse this profile? Should we create a new profile for the vpc? If so, doesn't it create any problem? Please help me.
Solved! Go to Solution.
11-02-2026 11:10 PM
Hi @Abiot ,
You are most likely using the interface wizard (Fabric > Access Policies > Interface Configuration). The system generated leaf interface profiles it creates (system-port-profile-node-101) are managed by APIC.
You can reuse the profile, but you can’t add a vPC port selector to it manually. You need to configure it through the interface wizard:
Make sure the vPC explicit protection group for the leaf pair exists. The port-channel policy (LACP active/passive) must match the downstream switch. This is most likely already done, since your servers are already connected with vPC.
Stick to one way of configuring interfaces, either through the wizard or manually (the “old” way).
I hope this helps.
11-02-2026 11:45 PM
I would recommend creating a separate leaf interface profile for the new vPC-connected switch rather than modifying the system-generated profile. In Cisco ACI, creating a new interface profile for this purpose is completely normal and should not cause any issues, provided the port selectors and policy group are configured correctly.
You can keep your existing server configurations as they are and create a separate profile for the new vPC connection. Just make sure both physical interfaces are mapped to the correct leaf switches and associated with the appropriate vPC policy group.
This approach will also keep your existing configuration clean and make future troubleshooting easier. Always double-check the interface selector and vPC configuration before deploying the changes.
11-02-2026 11:54 PM
Hi @Abiot
Since your servers are already configured through the interface wizard, I’d recommend configuring the new vPC the same way, without creating a separate interface profile manually. Also there is no way to modify system generated profiles.
Creating a new profile the “old” way is technically possible. However, it mixes two configuration models in one fabric, which makes troubleshooting harder not easier in my opinion.
11-03-2026 12:29 AM
Yes, keep it as it is. The wizard always creates a separate switch and interface profile for each leaf. That’s simply how it works, so you don’t need to change anything.
For example, one of my customers also uses the wizard and has mostly vPC connected devices, and there isn’t a single combined profile there.
11-02-2026 10:59 PM
11-02-2026 11:05 PM
Version 5.2(8e)
11-02-2026 11:10 PM
Hi @Abiot ,
You are most likely using the interface wizard (Fabric > Access Policies > Interface Configuration). The system generated leaf interface profiles it creates (system-port-profile-node-101) are managed by APIC.
You can reuse the profile, but you can’t add a vPC port selector to it manually. You need to configure it through the interface wizard:
Make sure the vPC explicit protection group for the leaf pair exists. The port-channel policy (LACP active/passive) must match the downstream switch. This is most likely already done, since your servers are already connected with vPC.
Stick to one way of configuring interfaces, either through the wizard or manually (the “old” way).
I hope this helps.
11-02-2026 11:31 PM
Thank you so much! Now I understand it very well. I was also able to configure it successfully.
11-02-2026 11:43 PM
Great! Glad it works now.
11-02-2026 11:45 PM
I would recommend creating a separate leaf interface profile for the new vPC-connected switch rather than modifying the system-generated profile. In Cisco ACI, creating a new interface profile for this purpose is completely normal and should not cause any issues, provided the port selectors and policy group are configured correctly.
You can keep your existing server configurations as they are and create a separate profile for the new vPC connection. Just make sure both physical interfaces are mapped to the correct leaf switches and associated with the appropriate vPC policy group.
This approach will also keep your existing configuration clean and make future troubleshooting easier. Always double-check the interface selector and vPC configuration before deploying the changes.
11-02-2026 11:54 PM
Hi @Abiot
Since your servers are already configured through the interface wizard, I’d recommend configuring the new vPC the same way, without creating a separate interface profile manually. Also there is no way to modify system generated profiles.
Creating a new profile the “old” way is technically possible. However, it mixes two configuration models in one fabric, which makes troubleshooting harder not easier in my opinion.
11-03-2026 12:00 AM
Thank you so much for the additional option! I read somewhere that creating a new interface profile would cause confusion to the system auto-generated profile. But now it is clear.
There is one more thing. In our deployment individual interface and switch profiles are used, not combined profiles. I think that's because different types are connected to the leaf switches. Should I keep it that way?
11-03-2026 12:29 AM
Yes, keep it as it is. The wizard always creates a separate switch and interface profile for each leaf. That’s simply how it works, so you don’t need to change anything.
For example, one of my customers also uses the wizard and has mostly vPC connected devices, and there isn’t a single combined profile there.
11-03-2026 12:54 AM
Thank you SO MUCH! Now everything is clearer. Our deployment is the same way.
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