vPC Initial Configuration on Nexus 5500

Enable vPC&LACP Globally
feature lacp
feature vpc

Create vPC Domain & Define peer-keepalive address
vpc domain 1
peer-keepalive destination 192.168.0.52
show vpc
sh run int e1/1-3(ensure any mismatch)

Create port-channel for vPC peer link
int e1/1 - 3
channel-group 50 mode active
int po50
switchport mode trunk
vpc peer-link

Notes: port type will change to "Network"

sh run int po 50
show port-channel summary
show vpc
show vpc peer-keepalive

 Verify vPC consistency Parameters
sh vpc consistency-parameters global

Assign Member port
int e1/24
shutdown
channel-group 51 mode on
switchport mode access
switchport access vlan 10
vpc 51
no shut

:Reference INE(Brian)

MPLS L3 VPN

1. The problem with VRFs is that you have to create them everywhere. When our goal is to have connectivity between CE1 and CE3 then we will have to add a VRF on the PE1, P and PE2 router. Also, all the service provider routes will have to participate with routing.

2. We will use MP-BGP between the PE routers so that they can share information from the VRFs without run VRF at P routers.

The PE2 router will learn 192.168.1.0 /24 from the PE1 router but it has no clue to what customer it will belong. There is no way to differentiate if something belongs to customer A or B.

RD (Route Distinguisher)
To fix this issue, we will use a RD (Route Distinguisher). We will add something to the prefix of the customer so that it will become unique: The RD and the prefix combined is what we call a VPNv4 route. We now have a method to differentiate between the different prefixes of our customers.

RT (Route Target)
We use something called a RT (Route Target) to decide in which VRF we import and export VPNv4 routes.

Steps to Configure MPLS L3 VPN