vPC problem

[multiplexer002]

Hi, 

I have two 5596UP in a domain and they are connected single-homed with one 2232 each. I am having a server connected dual-homed with the two FEX.

I am trying to create a port channel but after issuing the sh vpc brief I am getting the following output from the secondary 5596UP:

status - *down

consistency - not applicable 

reason - consistency check not performed

port-channel on the primary 5596UP switch has been created succesfully.

Any help?

Thanks 

John

[Jigar Dave]

John,

Please follow a procedure to create vpc, vpcpeerkeepalive links between two Nexus 5k. then create vpc 20 on each 5k to connect to server.

follow below steps to configure vpc domain, peer keep alive link


N5k-1# conf t
Enter configuration commands, one per line.  End with CNTL/Z.
N5k-1(config)# feature vpc


N5k-1(config)# vrf context vpc-keepalive
N5k-1(config-vrf)# int eth 2/10
N5k-1(config-if)# no switchport
N5k-1(config-if)# vrf member vpc-keepalive
N5k-1(config-if)# ip add 10.1.2.1 255.255.255.252
N5k-1(config-if)# no shut
!
N5k-2(config)# vrf context vpc-keepalive
N5k-2(config-vrf)# int eth 2/10
N5k-2(config-if)# no switchport
N5k-2(config-if)# vrf member vpc-keepalive
N5k-2(config-if)# ip add 10.1.2.2 255.255.255.252
N5k-2(config-if)# no shut



N5k-1(config)# vpc domain 1
N5k-1(config-vpc-domain)# peer-keepalive destination 10.1.1.2 source 10.1.1.1 vrf vpc-keepalive
!
N5k-2(config)# vpc domain 1
N5k-2(config-vpc-domain)# peer-keepalive destination 10.1.1.1 source 10.1.1.2 vrf vpc-keepalive


N5k-1(config)# int ethernet 1/1 - 2
N5k-1(config-if-range)# channel-group 100 on
N5k-1(config-if-range)# interface port-channel 100
N5k-1(config-if)# switchport
N5k-1(config-if)# switchport mode trunk
N5k-1(config-if)# vpc peer-link
Please note that spanning tree port type is changed to "network" port type on vPC peer-link.
This will enable spanning tree Bridge Assurance on vPC peer-link provided the STP Bridge Assurance (which is enabled by default) is not disabled.
!
N5k-2(config)# int ethernet 1/1 - 2
N5k-2(config-if-range)# channel-group 100 on
N5k-2(config-if-range)# interface port-channel 100
N5k-2(config-if)# switchport
N5k-2(config-if)# switchport mode trunk
N5k-2(config-if)# vpc peer-link
Please note that spanning tree port type is changed to "network" port type on vPC peer-link.
This will enable spanning tree Bridge Assurance on vPC peer-link provided the STP Bridge Assurance (which is enabled by default) is not disabled.
!

N5k-1(config)# interface eth2/1
N5k-1(config-if)# channel-group 1 mode active
N5k-1(config-if)# no shutdown
N5k-1(config-if)# interface port-channel 1
N5k-1(config-if)# switchport
N5k-1(config-if)# switchport mode trunk
N5k-1(config-if)# vpc 1
!
N5k-2(config)# interface eth2/2
N5k-2(config-if)# channel-group 1 mode active
N5k-2(config-if)# no shutdown
N5k-2(config-if)# interface port-channel 1
N5k-2(config-if)# switchport
N5k-2(config-if)# switchport mode trunk
N5k-2(config-if)# vpc 1

Please follow a procedure to create vpc 20 on both Nexus first, this will connect to server which is dual homed with FEX.

Nexus-1 config
let's say your fex connected with nexus-5-1 is FEX101

conf t
int po20
switchport mode trunk
vpc 20
no sh
exit

int eth101/10
switchport mode trunk
channel-group 20 mode active
no sh
exit

now , connect Fex port number 10 to server NIC-1

Nexus-2 config
let's say your fex connected with nexus-5-2 is FEX 102


conf t
int po20
switchport mode trunk
vpc 20
no sh
exit

int eth101/10
switchport mode trunk
channel-group 20 mode active
no sh
exit

now , connect Fex port number 10 to server NIC-2

**********************************************************************************

I hope this is helpful.

Thanks

[multiplexer002]

Hi Jigar,

The problem was the inconsistency of VLAN's.

Thanks  for the info though. 

John