08-05-2015 11:02 AM - edited 03-01-2019 07:59 AM
Hello Folks,
I tried creating L3 on Nexus 7K & got message "% Deleted all L3 config on interface Vlan136" there was no existing vlan 136.
Is it standard behivour in Nexus ?
X7K01(config)#
7K01(config)# vlan 136
7K01(config-vlan)# name Dev-136
7K01(config-vlan)# exit
7K01(config)# interface Vlan136
7K01(config-if)# vrf member Ext
% Deleted all L3 config on interface Vlan136
7K01(config-if)# ip address 10.20.136.2/22
7K01(config-if)# hsrp 136
7K01(config-if-hsrp)# preempt delay minimum 180
7K01(config-if-hsrp)# priority 103
7K01(config-if-hsrp)# timers 1 3
7K01(config-if-hsrp)# ip 10.20.136.1
7K01(config-if-hsrp)# no shutdown
Regards,
PSP
Solved! Go to Solution.
08-06-2015 03:25 AM
Hi,
This is the standard behaviour when configuring an interface as part of an existing VRF. As per the Guidelines and Limitations section on page 6 of the Configuring Layer 3 Virtualization configuration guide:
VRFs have the following guidelines and limitations:
I may be wrong, but I'd imagine this is to ensure that configuration or addressing from one VRF could not accidently be introduced into a different VRF if you move an interface from one VRF to another.
Regards
08-06-2015 03:25 AM
Hi,
This is the standard behaviour when configuring an interface as part of an existing VRF. As per the Guidelines and Limitations section on page 6 of the Configuring Layer 3 Virtualization configuration guide:
VRFs have the following guidelines and limitations:
I may be wrong, but I'd imagine this is to ensure that configuration or addressing from one VRF could not accidently be introduced into a different VRF if you move an interface from one VRF to another.
Regards
08-06-2015 04:20 AM
Looks like you are correct, Thanks for your response !!!
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