VRF under HPE are called vpn-instance, I still call them VRF because working with some disinterested colleagues … they constantly confuse a vpn-instance from a vpn IPSec. Another reason why I call it VRF is because when I started this job I was only dealing with Cisco devices and the VRF initials remained in my heart. Uhm and it is also shorter!
Nevermind!
here’s the conf:
# HPE
#
ip vpn-instance Lab_ipv4
route-distinguisher 172.29.0.5:1
vpn-target 5:1 import-extcommunity
vpn-target 5:1 export-extcommunity
#
address-family ipv4
#Remember that if you wanto to participate to this virtual routing table, your L3 interface must be associate whit the VRF:
# HPE
#
interface Vlan-interface100
description to NHB vrf Lab_ipv4
ip binding vpn-instance Lab_ipv4
ip address 192.168.0.90 255.255.255.0
#
interface Vlan-interface101
description to OHB vrf Lab_ipv4
ip binding vpn-instance Lab_ipv4
ip address 192.168.90.0 255.255.252.0
#Bye!
.glitchlist crew