Posted on December 4, 2020 11:46 am
 |  Asked by daehan we
 |  506 views
RESOLVED
0
0
Print Friendly, PDF & Email

Hi there I made vEOS lab for bgp evpn switchs and i got some error

 

when i made vxlan interface configuration ..

i add static vlan vni mapping on that interface like this

!
interface Vxlan1
vxlan source-interface Loopback1
vxlan controller-client import vlan none
vxlan udp-port 4789

vxlan vlan 1000-2000 vni 1000-2000

!

it works..   then i want to extend of range for more vlan useage

i changed like this

!
interface Vxlan1
vxlan source-interface Loopback1
vxlan controller-client import vlan none
vxlan udp-port 4789

vxlan vlan 11-3200 vni 11-3200

!

Then..  Ethernet interface wont up state

it told notconnect state to spine node interface..! ( i used ztp startup-config)

 

i knew the internal vlan use age so i changed it  using this configuation

 

vlan internal order descending range 3500 4094

 

problem is..  spine’s arp protocol is came to virtio interface which is named.. vmnicet#

but it cant propagate to et# interface which is made by arista switch

 

 

So my question is.. Are there are any limits for static vlan vni mapping range on vxlan interface  of vEOS lab?

0
Answered on December 4, 2020 5:11 pm

Hi Daehan,

I tried your order of operations and I see the same issue:

  1. I have the default vlan allocation policy
    sw1(config)#sh vlan internal allocation policy
    Internal VLAN Allocation Policy: ascending
    Internal VLAN Allocation Range: 1006-4094
  2. Created vlan to VNI mapping
    sw1(config)#int vxlan 1
    sw1(config-if-Vx1)#vxlan vlan 11-3200 vni 11-3200
  3. Changed the internal vlan allocation policy
    sw1(config)#vlan internal order descending range 3500 4094
  4. Made the spine interface as routed port.
    sw1(config)#int et1
    sw1(config-if-Et1)#no switchport
  5. But there was no internal vlan allocated for the interface

    sw1(config-if-Et1)#sh vlan internal usage
    sw1(config-if-Et1)#

I removed all configurations, rebooted the switch, and changed the order of my operations. After the switch came back up:

  1. Change the internal vlan allocation policy
    sw1(config)#vlan internal order descending range 3500 4094
    sw1(config)#show vlan internal allocation policy
    Internal VLAN Allocation Policy: descending
    Internal VLAN Allocation Range: 3500-4094
    sw1(config)#
  2. Configured the spine interface as routed port and verify internal vlan was allocated

    sw1(config)#int et1
    sw1(config-if-Et1)#no switchport
    sw1(config-if-Et1)#show vlan internal usage
    4094 Ethernet1
    sw1(config-if-Et1)#

  3. Created the vlan to vni mapping
    sw1(config)#int vxlan 1
    sw1(config-if-Vx1)#vxlan vlan 11-3200 vni 11-3200
  4. Now the internal vlan allocated to the spine switch stays and I can ping the spine

    sw1(config-if-Et1)#sh ip int br | grep Ethernet1
    Ethernet1 192.168.1.1/30 up up 1500
    sw1(config-if-Et1)#ping 192.168.1.2
    PING 192.168.1.2 (192.168.1.2) 72(100) bytes of data.
    80 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=218 ms
    80 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=301 ms
    80 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=414 ms
    80 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=499 ms
    80 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=610 ms

    --- 192.168.1.2 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 41ms
    rtt min/avg/max/mdev = 218.755/409.083/610.865/139.175 ms, pipe 5, ipg/ewma 10.321/324.175 ms
    sw1(config-if-Et1)#

It looks like there might be a bug in the order of operations begin performed, but vEOS lab is not meant for scale testing or production grade deployment. Hope this help in your tests.

Thanks,
Bharath

Post your Answer

You must be logged in to post an answer.