vPC Orphan Port

[mayaanan]

Hi All,

Greetings!!!

A quick question about vPC orphan port. What problem we will get due to orphan port and how we can mitigate the orphan port.Basic function is when Peer-Link goes down , Secondary vPC port disable the member port and down the SVI.

What problem will get create after peer link fail ?

As i know there are four following method to overcome on this issue , could you explain which would be better and how it would be better from another solution.

1.Dual Home All End Host

2.Single attached hosts could attached via dual homed access switch. 

3.Single attached home could use non-vpc vlans.

4.When peer link fail dont disable SVI.

[Sergiu.Daniluk]

Hi @mayaanan 

The best solution for not vPC-capable servers (basically the servers who cannot be configured with port-channels), is to connect them to both vPC peers with individual links. Now you should configure the orphan ports with the " vpc orphan-port suspend". With this configuration, the ports on secondary peer will be shut down in response to a peer link failure and restored when the peer-link is restored.

This feature is valid as well for servers connected to one single vPC peers, to avoid traffic black holing during PL failure.

Cheers,

Sergiu

[mayaanan]

Hi msdaniluk,

Thanks for the response....Could you elaborate me about.

Single attached home could use non-vpc vlans.

 How vPC and no vPC vlan work together ?

How fail over work after this configuration ?

As i know , we need to configuration another Port channel parallel to peer link but no vpc member vlan will passs through this new port channel . The what i the work of vPC here ?

[Sergiu.Daniluk]

Hi,

That is true, it is recommended to split vPC and non-vPC VLANs on different interswitch port channels: use vPC peer-link to carry vPC VLAN and the other interswitch port-channel to carry non-vPC VLAN. Important to remember is that SVIs associated to these VLAN are not shut down when vPC peer-link goes down, regardless of using or not a dedicated interswitch link for non-vPC vlans. However, the advantage of having a spearate interswitch port-channel is to have a dedicated link in case of vpc peer-link failure and avoid isolation on operational secondary vpc peer. 

Communications from non-vPC VLAN to vPC VLAN must be done as usually, through inter-VLAN routing.

Cheers,

Sergiu

[paul driver]

Hello
An orphan port is just a port that’s not it a VPC, so depending on where this port resides would depend if you lose connectivity to it - So if/when you incur a peer-link failure, and that orphan port is associated with the secondary peer then unlike vpc member ports that will automatically be shutdown orphan ports don’t so this could cause some issues with the device that’s connected to that port so its suggested that these orphan ports should also be brought down alongside vpc member ports when a peer-link failure is incurred

This can be accomplished by configuring any orphan port with the following command.

Int x/x
description  Orphan port
vpc orphan-ports suspend

[Sergiu.Daniluk]

Hi,

Orphan port is a port on vPC peer device (primary or secondary) that is not configured as vPC and carries vPC VLANs. If the port carries a non-vPC VLAN, it is no more defined as Orphan Port.  

To display all Orphan Ports on vPC peer device use command:

show vpc orphan-ports

Cheers,

Sergiu