11-19-2022 05:10 AM - last edited on 11-21-2022 12:54 AM by Translator
May I know the purpose of Defining
address-family
within VRF? Is it required on a Nexus platform? I'm trying to understand the real life scenarios? In my case, I'm going to create a VRF for a VPC keepalive.
Solved! Go to Solution.
11-19-2022 05:19 AM - last edited on 11-21-2022 12:55 AM by Translator
using different
import export for each address-family
is one case that we use
address-family
under VRF.
for your case only for keepalive I dont think you need
address-family
11-19-2022 05:19 AM - last edited on 11-21-2022 12:55 AM by Translator
using different
import export for each address-family
is one case that we use
address-family
under VRF.
for your case only for keepalive I dont think you need
address-family
11-19-2022 02:58 PM - last edited on 11-21-2022 12:56 AM by Translator
Hi @MHM Cisco World ,
With the new VRF cli (i.e. vrf definition <vrf-name>), you are forced to specify the address family you want (ipv4 and/or ipv6). Otherwise you will get an error message as follow when trying to configure the ipv4 or ipv6 address on the interface:
R3(config)#vrf definition test
R3(config-vrf)#int gi0/2
R3(config-if)#vrf forwarding test
R3(config-if)#ip address 192.168.1.1 255.255.255.0
%GigabitEthernet0/2 is linked to a VRF. Enable IPv4 on that VRF first.
Regards,
11-19-2022 03:10 PM - edited 11-19-2022 03:14 PM
this also apply to Nexus ?
FROM cisco Doc.
Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide, Release 7.x - Configuring vPCs [Cisco Nexus 9000 Series Switches] - Cisco
Create a separate VRF for the vPC peer-keepalive link and add a Layer 3 interface to that VRF.
switch(config)# vrf context pkal switch(config-vrf)# exit switch(config)# interface ethernet 8/1 switch(config-if)# vrf member pkal switch(config-if)# ip address 172.23.145.218/24 switch(config-if)# no shutdown switch(config-if)# exit
11-20-2022 01:38 PM
Thanks @Harold Ritter for the explanation!
11-19-2022 02:22 PM
@MHM Cisco World Thanks for the explanation.
12-16-2023 02:04 AM - edited 01-02-2024 08:44 AM
In Nexus devices, the concept of "address-family" within a Virtual Routing and Forwarding (VRF) instance serves a crucial purpose. Essentially, it allows the segregation and management of multiple routing instances within a single device.
By defining an address-family within a VRF, you're specifying the address type and the associated routing protocols that will be used within that particular VRF instance. This segregation enables different types of traffic (IPv4, IPv6, multicast, etc.) to be handled independently within their designated VRF, ensuring better network control, security, and scalability.
In simpler terms, the "address-family" feature in VRF helps organize and manage various types of traffic more effectively within a Nexus device by providing a way to separate and control routing information for different address types or protocols.
Great piece of information,
Thank You,
Lisa Rollins
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide