cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1377
Views
10
Helpful
2
Replies

Cisco ACI vPC link not aggregated

sandyblaza
Level 1
Level 1

I created a vPC link on ACI to Internal firewall, and found out the link is not aggregated and the port-channel group id does not match on Leaf 1 and Leaf 2.

I'm wondering how this mismatch happened when the configuration is the same on the working one (I configured it via GUI). And how this will be fixed.

 

ACILP01# show port-channel summary

-------------------------------------------------------------------------------
Group Port-       Type     Protocol  Member Ports
      Channel
-------------------------------------------------------------------------------
1     Po1(SD)     Eth      LACP      Eth1/11(P)
ACILP02# show port-channel summary

-------------------------------------------------------------------------------
Group Port-       Type     Protocol  Member Ports
      Channel
-------------------------------------------------------------------------------
1     Po2(SD)     Eth      LACP      Eth1/11(P)
ACILP01# show vpc extended vpc 3

---------------------------------------------------------------------------------
id   Port   Status Consistency Reason               Active vlans Bndl Grp Name
--   ----   ------ ----------- ------               ------------ ----------------

3    Po1    up     success     success              1,10-11,15,7 vpcForIntFW-101
                                                    0,112-114,11 -102_IPG
                                                    6-118,120,12
                                                    2,1201-1204,
                                                    1206-1208,13
                                                    01-1304,1306
                                                    -1308,1401-1
                                                    404,1406-140           ....
ACILP02# show vpc extended vpc 3

---------------------------------------------------------------------------------
id   Port   Status Consistency Reason               Active vlans Bndl Grp Name
--   ----   ------ ----------- ------               ------------ ----------------

3    Po2    up     success     success              1,10-11,15,7 vpcForIntFW-101
                                                    0,112-114,11 -102_IPG
                                                    6-118,120,12
                                                    2,1201-1204,
                                                    1206-1208,13
                                                    01-1304,1306
                                                    -1308,1401-1
                                                    404,1406-140           ....
1 Accepted Solution

Accepted Solutions

julian.bendix
Level 3
Level 3

Hey, 

the Port-Channel ID does not have to match in VPC setups, that is the case for both NX-OS and ACI mode..

What needs to match is the VPC ID - in your case it is 3... looks good to me!

Do you have any issue in the setup? Anything not woring?

P.S.: having a VPC pair in NX-OS mode you will probably choose the same Port-Channel ID on both nodes and then the exact same number for VPC ID when connecting a new endpoint via VPC - that is the beautiful way to do it.
But you don't have to, you can choose Port-Channel ID 123 on node 1, Port-Channel ID 321 on node 2 and then VPC ID 17 for this VPC.
As long als necessary interface level settings are matchig, VPC ID matches and the VPC pair is OK ... it will work just fine

Let me know if that helps..

Juls

View solution in original post

2 Replies 2

anoop verma
Level 1
Level 1

PO is only a logical interface. Are you facing any operational issue?

julian.bendix
Level 3
Level 3

Hey, 

the Port-Channel ID does not have to match in VPC setups, that is the case for both NX-OS and ACI mode..

What needs to match is the VPC ID - in your case it is 3... looks good to me!

Do you have any issue in the setup? Anything not woring?

P.S.: having a VPC pair in NX-OS mode you will probably choose the same Port-Channel ID on both nodes and then the exact same number for VPC ID when connecting a new endpoint via VPC - that is the beautiful way to do it.
But you don't have to, you can choose Port-Channel ID 123 on node 1, Port-Channel ID 321 on node 2 and then VPC ID 17 for this VPC.
As long als necessary interface level settings are matchig, VPC ID matches and the VPC pair is OK ... it will work just fine

Let me know if that helps..

Juls

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