IOSXRv9000 - ether-channel / port-channel support on EVE-NG
Moderator: mike
-
- Posts: 79
- Joined: Wed May 10, 2017 12:11 pm
- Contact:
IOSXRv9000 - ether-channel / port-channel support on EVE-NG
Hi
Any one tried ether-channel / port-channel with IOS-XRv9k image 6.2.x on EVE-NG?
It seems this L2 feature is supported as it has got DATA plane support. I tested MPLS L2 VPN P2P, traffic is passing.
Noticed the below link/discussion and according to that, XRv9k, supports port-channel.
https://community.cisco.com/t5/xr-os-an ... -p/3390432
Any idea whether EVE-NG has any limitations or not supported yet?
I am using Community Edition Version 2.0.3-92 and did not try on 2.0.3-95. I am not sure whether it works on Ver 2.0.3-95.
Mathew
Any one tried ether-channel / port-channel with IOS-XRv9k image 6.2.x on EVE-NG?
It seems this L2 feature is supported as it has got DATA plane support. I tested MPLS L2 VPN P2P, traffic is passing.
Noticed the below link/discussion and according to that, XRv9k, supports port-channel.
https://community.cisco.com/t5/xr-os-an ... -p/3390432
Any idea whether EVE-NG has any limitations or not supported yet?
I am using Community Edition Version 2.0.3-92 and did not try on 2.0.3-95. I am not sure whether it works on Ver 2.0.3-95.
Mathew
-
- Posts: 5067
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: IOSXRv9000 - ether-channel / port-channel support on EVE-NG
Works my dear:
just make a note this image is super heavy !!!
2 XRv9k require min 8 CPU and 32G RAM
XRv9K vers 6.6.2
And STOP blame EVE here...
if image does not support something it is not EVE Issue, EVE supports ALL what current images does... !!!!!!!!!
6.6.2 image does not support
bundle load-balancing hash src-ip
Rest is fine
Uldis
just make a note this image is super heavy !!!
2 XRv9k require min 8 CPU and 32G RAM
XRv9K vers 6.6.2
And STOP blame EVE here...
if image does not support something it is not EVE Issue, EVE supports ALL what current images does... !!!!!!!!!
6.6.2 image does not support
bundle load-balancing hash src-ip
Rest is fine
Uldis
You do not have the required permissions to view the files attached to this post.
-
- Posts: 79
- Joined: Wed May 10, 2017 12:11 pm
- Contact:
Re: IOSXRv9000 - ether-channel / port-channel support on EVE-NG
Hi,
First thanks for the reply and sorry that I suspected EVE-NG but I was asking and was not aware of the those XRv9k limitations.
However, I tried but I can not get the IP connectivity and tried to set the "bundle load-balancing hash dst-ip" but commit failed - see below.
Also I have shared the bundle interface status and configuration.
Can you please share your configuration that worked in your setup to get IP connectivity?
I am wondering what is missing here to get the IP connectivity between the PE1 and PE2 when bundle interfaces are UP on both side. My topology is same as yours - PE1 and PE2 on G0/0/0/2 and G0/0/0/3 with Bundle interface 12.
RP/0/RP0/CPU0:PE1#conf t
Sat Jun 15 01:30:24.126 UTC
^[[ARP/0/RP0/CPU0:PE1(config)#interface Bundle-Ether12
RP/0/RP0/CPU0:PE1(config-if)#bundle load-balancing ?
hash Select the hash function used for traffic forwarded over the bundle
RP/0/RP0/CPU0:PE1(config-if)#bundle load-balancing hash ?
dst-ip Use the destination IP as the hash function
src-ip Use the source IP as the hash function
RP/0/RP0/CPU0:PE1(config-if)#bundle load-balancing hash dst-ip ?
<cr>
RP/0/RP0/CPU0:PE1(config-if)#bundle load-balancing hash dst-ip
RP/0/RP0/CPU0:PE1(config-if)#commit
Sat Jun 15 01:30:46.641 UTC
% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed [inheritance]' from this session to view the errors
RP/0/RP0/CPU0:PE1(config-if)#show configuration failed
Sat Jun 15 01:30:56.901 UTC
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.
interface Bundle-Ether12
bundle load-balancing hash dst-ip
!!% 'bundlemgr' detected the 'warning' condition 'The feature is not supported on this platform'
!
end
RP/0/RP0/CPU0:PE1(config-if)#bundle load-balancing hash s
RP/0/RP0/CPU0:PE1(config-if)#commit
Sat Jun 15 01:31:07.970 UTC
% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed [inheritance]' from this session to view the errors
RP/0/RP0/CPU0:PE1(config-if)#show configuration failed
Sat Jun 15 01:31:11.362 UTC
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.
interface Bundle-Ether12
bundle load-balancing hash src-ip
!!% 'bundlemgr' detected the 'warning' condition 'The feature is not supported on this platform'
!
end
RP/0/RP0/CPU0:PE1(config-if)#
Status and configuration:
RP/0/RP0/CPU0:PE1#sho int Bundle-Ether12
Sat Jun 15 01:25:29.636 UTC
Bundle-Ether12 is up, line protocol is up
Interface state transitions: 1
Hardware is Aggregated Ethernet interface(s), address is 0013.1a1a.f31b
Internet address is 10.1.12.1/30
MTU 9216 bytes, BW 2000000 Kbit (Max: 2000000 Kbit)
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation ARPA,
Full-duplex, 2000Mb/s
loopback not set,
Last link flapped 00:01:56
ARP type ARPA, ARP timeout 04:00:00
No. of members in this bundle: 2
GigabitEthernet0/0/0/2 Full-duplex 1000Mb/s Active
GigabitEthernet0/0/0/3 Full-duplex 1000Mb/s Active
Last input 00:00:00, output 00:00:00
Last clearing of "show interface" counters never
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
28 packets input, 1176 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 14 broadcast packets, 0 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
55 packets output, 2310 bytes, 0 total output drops
Output 27 broadcast packets, 0 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
RP/0/RP0/CPU0:PE1#
RP/0/RP0/CPU0:PE1#ping 10.1.12.2
Sat Jun 15 01:27:00.043 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.12.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
RP/0/RP0/CPU0:PE1#
PE1 config
!
interface Bundle-Ether12
mtu 9216
ipv4 address 10.1.12.1 255.255.255.252
bundle minimum-active links 2
load-interval 30
!
interface GigabitEthernet0/0/0/2
bundle id 12 mode on
!
interface GigabitEthernet0/0/0/3
bundle id 12 mode on
!
RP/0/RP0/CPU0:PE2#sho int Bundle-Ether12
Sat Jun 15 01:25:37.883 UTC
Bundle-Ether12 is up, line protocol is up
Interface state transitions: 1
Hardware is Aggregated Ethernet interface(s), address is 0013.1a1a.f31b
Internet address is 10.1.12.2/30
MTU 9216 bytes, BW 2000000 Kbit (Max: 2000000 Kbit)
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation ARPA,
Full-duplex, 2000Mb/s
loopback not set,
Last link flapped 00:02:21
ARP type ARPA, ARP timeout 04:00:00
No. of members in this bundle: 2
GigabitEthernet0/0/0/2 Full-duplex 1000Mb/s Active
GigabitEthernet0/0/0/3 Full-duplex 1000Mb/s Active
Last input 00:00:00, output 00:00:00
Last clearing of "show interface" counters never
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
56 packets input, 2352 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 28 broadcast packets, 0 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
29 packets output, 1218 bytes, 0 total output drops
Output 14 broadcast packets, 0 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
RP/0/RP0/CPU0:PE2#
RP/0/RP0/CPU0:PE2#ping 10.1.12.1
Sat Jun 15 01:26:55.180 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.12.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
RP/0/RP0/CPU0:PE2#
PE2 config
!
interface Bundle-Ether12
mtu 9216
ipv4 address 10.1.12.2 255.255.255.252
bundle minimum-active links 2
load-interval 30
!
interface GigabitEthernet0/0/0/2
bundle id 12 mode on
!
interface GigabitEthernet0/0/0/3
bundle id 12 mode on
!
Mathew
First thanks for the reply and sorry that I suspected EVE-NG but I was asking and was not aware of the those XRv9k limitations.
However, I tried but I can not get the IP connectivity and tried to set the "bundle load-balancing hash dst-ip" but commit failed - see below.
Also I have shared the bundle interface status and configuration.
Can you please share your configuration that worked in your setup to get IP connectivity?
I am wondering what is missing here to get the IP connectivity between the PE1 and PE2 when bundle interfaces are UP on both side. My topology is same as yours - PE1 and PE2 on G0/0/0/2 and G0/0/0/3 with Bundle interface 12.
RP/0/RP0/CPU0:PE1#conf t
Sat Jun 15 01:30:24.126 UTC
^[[ARP/0/RP0/CPU0:PE1(config)#interface Bundle-Ether12
RP/0/RP0/CPU0:PE1(config-if)#bundle load-balancing ?
hash Select the hash function used for traffic forwarded over the bundle
RP/0/RP0/CPU0:PE1(config-if)#bundle load-balancing hash ?
dst-ip Use the destination IP as the hash function
src-ip Use the source IP as the hash function
RP/0/RP0/CPU0:PE1(config-if)#bundle load-balancing hash dst-ip ?
<cr>
RP/0/RP0/CPU0:PE1(config-if)#bundle load-balancing hash dst-ip
RP/0/RP0/CPU0:PE1(config-if)#commit
Sat Jun 15 01:30:46.641 UTC
% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed [inheritance]' from this session to view the errors
RP/0/RP0/CPU0:PE1(config-if)#show configuration failed
Sat Jun 15 01:30:56.901 UTC
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.
interface Bundle-Ether12
bundle load-balancing hash dst-ip
!!% 'bundlemgr' detected the 'warning' condition 'The feature is not supported on this platform'
!
end
RP/0/RP0/CPU0:PE1(config-if)#bundle load-balancing hash s
RP/0/RP0/CPU0:PE1(config-if)#commit
Sat Jun 15 01:31:07.970 UTC
% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed [inheritance]' from this session to view the errors
RP/0/RP0/CPU0:PE1(config-if)#show configuration failed
Sat Jun 15 01:31:11.362 UTC
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.
interface Bundle-Ether12
bundle load-balancing hash src-ip
!!% 'bundlemgr' detected the 'warning' condition 'The feature is not supported on this platform'
!
end
RP/0/RP0/CPU0:PE1(config-if)#
Status and configuration:
RP/0/RP0/CPU0:PE1#sho int Bundle-Ether12
Sat Jun 15 01:25:29.636 UTC
Bundle-Ether12 is up, line protocol is up
Interface state transitions: 1
Hardware is Aggregated Ethernet interface(s), address is 0013.1a1a.f31b
Internet address is 10.1.12.1/30
MTU 9216 bytes, BW 2000000 Kbit (Max: 2000000 Kbit)
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation ARPA,
Full-duplex, 2000Mb/s
loopback not set,
Last link flapped 00:01:56
ARP type ARPA, ARP timeout 04:00:00
No. of members in this bundle: 2
GigabitEthernet0/0/0/2 Full-duplex 1000Mb/s Active
GigabitEthernet0/0/0/3 Full-duplex 1000Mb/s Active
Last input 00:00:00, output 00:00:00
Last clearing of "show interface" counters never
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
28 packets input, 1176 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 14 broadcast packets, 0 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
55 packets output, 2310 bytes, 0 total output drops
Output 27 broadcast packets, 0 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
RP/0/RP0/CPU0:PE1#
RP/0/RP0/CPU0:PE1#ping 10.1.12.2
Sat Jun 15 01:27:00.043 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.12.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
RP/0/RP0/CPU0:PE1#
PE1 config
!
interface Bundle-Ether12
mtu 9216
ipv4 address 10.1.12.1 255.255.255.252
bundle minimum-active links 2
load-interval 30
!
interface GigabitEthernet0/0/0/2
bundle id 12 mode on
!
interface GigabitEthernet0/0/0/3
bundle id 12 mode on
!
RP/0/RP0/CPU0:PE2#sho int Bundle-Ether12
Sat Jun 15 01:25:37.883 UTC
Bundle-Ether12 is up, line protocol is up
Interface state transitions: 1
Hardware is Aggregated Ethernet interface(s), address is 0013.1a1a.f31b
Internet address is 10.1.12.2/30
MTU 9216 bytes, BW 2000000 Kbit (Max: 2000000 Kbit)
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation ARPA,
Full-duplex, 2000Mb/s
loopback not set,
Last link flapped 00:02:21
ARP type ARPA, ARP timeout 04:00:00
No. of members in this bundle: 2
GigabitEthernet0/0/0/2 Full-duplex 1000Mb/s Active
GigabitEthernet0/0/0/3 Full-duplex 1000Mb/s Active
Last input 00:00:00, output 00:00:00
Last clearing of "show interface" counters never
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
56 packets input, 2352 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 28 broadcast packets, 0 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
29 packets output, 1218 bytes, 0 total output drops
Output 14 broadcast packets, 0 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
RP/0/RP0/CPU0:PE2#
RP/0/RP0/CPU0:PE2#ping 10.1.12.1
Sat Jun 15 01:26:55.180 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.12.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
RP/0/RP0/CPU0:PE2#
PE2 config
!
interface Bundle-Ether12
mtu 9216
ipv4 address 10.1.12.2 255.255.255.252
bundle minimum-active links 2
load-interval 30
!
interface GigabitEthernet0/0/0/2
bundle id 12 mode on
!
interface GigabitEthernet0/0/0/3
bundle id 12 mode on
!
Mathew
-
- Posts: 5067
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: IOSXRv9000 - ether-channel / port-channel support on EVE-NG
do not use
bundle load-balancing hash dst-ip
And remove MTU, rest is ok
interface Bundle-Ether12
ipv4 address 10.1.12.2 255.255.255.252
bundle minimum-active links 1
bundle maximum-active links 2
!
interface GigabitEthernet0/0/0/2
bundle id 12 mode on
!
interface GigabitEthernet0/0/0/3
bundle id 12 mode on
bundle load-balancing hash dst-ip
And remove MTU, rest is ok
interface Bundle-Ether12
ipv4 address 10.1.12.2 255.255.255.252
bundle minimum-active links 1
bundle maximum-active links 2
!
interface GigabitEthernet0/0/0/2
bundle id 12 mode on
!
interface GigabitEthernet0/0/0/3
bundle id 12 mode on
-
- Posts: 79
- Joined: Wed May 10, 2017 12:11 pm
- Contact:
Re: IOSXRv9000 - ether-channel / port-channel support on EVE-NG
Hi
Thank you for the reply.
I did the same configuration but I still can not ping between the two routers. I reloaded the two routers, EVE-NG etc.
BTW, I use RAM 16384 and CPU 4 for each XRv9k.
Do you think this is the issue?
is it possible to help check you can get it to work with this RAM and CPU in your setup?
Accordingly, I will add more RAM, if the issue is RAM.
Mathew
Thank you for the reply.
I did the same configuration but I still can not ping between the two routers. I reloaded the two routers, EVE-NG etc.
BTW, I use RAM 16384 and CPU 4 for each XRv9k.
Do you think this is the issue?
is it possible to help check you can get it to work with this RAM and CPU in your setup?
Accordingly, I will add more RAM, if the issue is RAM.
Mathew
-
- Posts: 5067
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: IOSXRv9000 - ether-channel / port-channel support on EVE-NG
My eve where I tested is:
Dual CPU X5680, 80Gb RAM
EVE VM on esxi 6.0.
EVE Pro 2.0.5-21
Dual CPU X5680, 80Gb RAM
EVE VM on esxi 6.0.
EVE Pro 2.0.5-21
-
- Posts: 79
- Joined: Wed May 10, 2017 12:11 pm
- Contact:
Re: IOSXRv9000 - ether-channel / port-channel support on EVE-NG
Hi,
Thank you very much for checking on this.
I found the issue from logs - it was duplicate MAC address under bundle-ether 12. Because "/opt/qemu/bin/qemu-img commit virtioa.qcow2" failed on the 2nd one and success on 1st one, I copied the virtioa.qcow2 from 1 to 2 folder. This might have caused the same MAC address.
I had to add "mac-address 1e.bd01.503X" under bundle interface to fix it.
L3 reachability is good between the 2 routers now.
BTW, is there any good/easy fix for "/opt/qemu/bin/qemu-img commit virtioa.qcow2" failes?
In my server, always, only first one worked.
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/1# /opt/qemu/bin/qemu-img commit virtioa.qcow2
Image committed.
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/1# /opt/qemu/bin/qemu-img commit virtioa.qcow2
Co-routine re-entered recursively
Aborted
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/2#
RP/0/RP0/CPU0:Jun 15 10:03:20.310 UTC: BM-DISTRIB[1256]: %L2-BM-6-ACTIVE : GigabitEthernet0/0/0/3 is Active as part of Bundle-Ether12
RP/0/RP0/CPU0:Jun 15 10:03:20.310 UTC: BM-DISTRIB[1256]: %L2-BM-6-ACTIVE : GigabitEthernet0/0/0/2 is Active as part of Bundle-Ether12
LC/0/0/CPU0:Jun 15 10:03:25.831 UTC: arp[184]: %IP-ARP-6-INFO_DUPMAC : 'Duplicate MAC address 001e.bd01.5030'
LC/0/0/CPU0:Jun 15 10:03:30.225 UTC: arp[184]: %IP-ARP-6-INFO_DUPADDR : 'Duplicate IP address 10.1.12.1 on Bundle-Ether12, sourced by 001e.bd01.5030'
RP/0/RP0/CPU0:PE1#sho int bundle-ether 12
Sat Jun 15 10:15:29.924 UTC
Bundle-Ether12 is up, line protocol is up
Interface state transitions: 1
Hardware is Aggregated Ethernet interface(s), address is 001e.bd01.5032
Internet address is 10.1.12.1/30
MTU 1514 bytes, BW 2000000 Kbit (Max: 2000000 Kbit)
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation ARPA,
Full-duplex, 2000Mb/s
loopback not set,
Last link flapped 00:12:10
ARP type ARPA, ARP timeout 04:00:00
No. of members in this bundle: 2
GigabitEthernet0/0/0/2 Full-duplex 1000Mb/s Active
GigabitEthernet0/0/0/3 Full-duplex 1000Mb/s Active
Last input 00:00:13, output 00:00:13
Last clearing of "show interface" counters never
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
186 packets input, 11412 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 68 broadcast packets, 0 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
181 packets output, 11202 bytes, 0 total output drops
Output 65 broadcast packets, 0 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
RP/0/RP0/CPU0:PE1#sho runn int bundle-ether 12
Sat Jun 15 10:15:46.464 UTC
interface Bundle-Ether12
ipv4 address 10.1.12.1 255.255.255.252
mac-address 1e.bd01.5032
bundle maximum-active links 2
bundle minimum-active links 1
!
RP/0/RP0/CPU0:PE1#ping 10.1.12.2
Sat Jun 15 10:16:01.288 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.12.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 86/87/93 ms
RP/0/RP0/CPU0:PE1#
RP/0/RP0/CPU0:PE2#sho int bundle-ether 12
Sat Jun 15 10:15:37.246 UTC
Bundle-Ether12 is up, line protocol is up
Interface state transitions: 1
Hardware is Aggregated Ethernet interface(s), address is 001e.bd01.5031
Internet address is 10.1.12.2/30
MTU 1514 bytes, BW 2000000 Kbit (Max: 2000000 Kbit)
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation ARPA,
Full-duplex, 2000Mb/s
loopback not set,
Last link flapped 00:12:42
ARP type ARPA, ARP timeout 04:00:00
No. of members in this bundle: 2
GigabitEthernet0/0/0/2 Full-duplex 1000Mb/s Active
GigabitEthernet0/0/0/3 Full-duplex 1000Mb/s Active
Last input 00:00:15, output 00:00:15
Last clearing of "show interface" counters never
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
181 packets input, 11202 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 65 broadcast packets, 0 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
188 packets output, 11496 bytes, 0 total output drops
Output 69 broadcast packets, 0 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
RP/0/RP0/CPU0:PE2#sho runn int bundle-ether 12
Sat Jun 15 10:15:52.453 UTC
interface Bundle-Ether12
ipv4 address 10.1.12.2 255.255.255.252
mac-address 1e.bd01.5031
bundle maximum-active links 2
bundle minimum-active links 1
!
RP/0/RP0/CPU0:PE2#ping 10.1.12.1
Sat Jun 15 10:15:56.152 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.12.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 85/86/87 ms
RP/0/RP0/CPU0:PE2#
Regards,
Mathew
Thank you very much for checking on this.
I found the issue from logs - it was duplicate MAC address under bundle-ether 12. Because "/opt/qemu/bin/qemu-img commit virtioa.qcow2" failed on the 2nd one and success on 1st one, I copied the virtioa.qcow2 from 1 to 2 folder. This might have caused the same MAC address.
I had to add "mac-address 1e.bd01.503X" under bundle interface to fix it.
L3 reachability is good between the 2 routers now.
BTW, is there any good/easy fix for "/opt/qemu/bin/qemu-img commit virtioa.qcow2" failes?
In my server, always, only first one worked.
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/1# /opt/qemu/bin/qemu-img commit virtioa.qcow2
Image committed.
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/1# /opt/qemu/bin/qemu-img commit virtioa.qcow2
Co-routine re-entered recursively
Aborted
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/2#
RP/0/RP0/CPU0:Jun 15 10:03:20.310 UTC: BM-DISTRIB[1256]: %L2-BM-6-ACTIVE : GigabitEthernet0/0/0/3 is Active as part of Bundle-Ether12
RP/0/RP0/CPU0:Jun 15 10:03:20.310 UTC: BM-DISTRIB[1256]: %L2-BM-6-ACTIVE : GigabitEthernet0/0/0/2 is Active as part of Bundle-Ether12
LC/0/0/CPU0:Jun 15 10:03:25.831 UTC: arp[184]: %IP-ARP-6-INFO_DUPMAC : 'Duplicate MAC address 001e.bd01.5030'
LC/0/0/CPU0:Jun 15 10:03:30.225 UTC: arp[184]: %IP-ARP-6-INFO_DUPADDR : 'Duplicate IP address 10.1.12.1 on Bundle-Ether12, sourced by 001e.bd01.5030'
RP/0/RP0/CPU0:PE1#sho int bundle-ether 12
Sat Jun 15 10:15:29.924 UTC
Bundle-Ether12 is up, line protocol is up
Interface state transitions: 1
Hardware is Aggregated Ethernet interface(s), address is 001e.bd01.5032
Internet address is 10.1.12.1/30
MTU 1514 bytes, BW 2000000 Kbit (Max: 2000000 Kbit)
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation ARPA,
Full-duplex, 2000Mb/s
loopback not set,
Last link flapped 00:12:10
ARP type ARPA, ARP timeout 04:00:00
No. of members in this bundle: 2
GigabitEthernet0/0/0/2 Full-duplex 1000Mb/s Active
GigabitEthernet0/0/0/3 Full-duplex 1000Mb/s Active
Last input 00:00:13, output 00:00:13
Last clearing of "show interface" counters never
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
186 packets input, 11412 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 68 broadcast packets, 0 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
181 packets output, 11202 bytes, 0 total output drops
Output 65 broadcast packets, 0 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
RP/0/RP0/CPU0:PE1#sho runn int bundle-ether 12
Sat Jun 15 10:15:46.464 UTC
interface Bundle-Ether12
ipv4 address 10.1.12.1 255.255.255.252
mac-address 1e.bd01.5032
bundle maximum-active links 2
bundle minimum-active links 1
!
RP/0/RP0/CPU0:PE1#ping 10.1.12.2
Sat Jun 15 10:16:01.288 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.12.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 86/87/93 ms
RP/0/RP0/CPU0:PE1#
RP/0/RP0/CPU0:PE2#sho int bundle-ether 12
Sat Jun 15 10:15:37.246 UTC
Bundle-Ether12 is up, line protocol is up
Interface state transitions: 1
Hardware is Aggregated Ethernet interface(s), address is 001e.bd01.5031
Internet address is 10.1.12.2/30
MTU 1514 bytes, BW 2000000 Kbit (Max: 2000000 Kbit)
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation ARPA,
Full-duplex, 2000Mb/s
loopback not set,
Last link flapped 00:12:42
ARP type ARPA, ARP timeout 04:00:00
No. of members in this bundle: 2
GigabitEthernet0/0/0/2 Full-duplex 1000Mb/s Active
GigabitEthernet0/0/0/3 Full-duplex 1000Mb/s Active
Last input 00:00:15, output 00:00:15
Last clearing of "show interface" counters never
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
181 packets input, 11202 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 65 broadcast packets, 0 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
188 packets output, 11496 bytes, 0 total output drops
Output 69 broadcast packets, 0 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
RP/0/RP0/CPU0:PE2#sho runn int bundle-ether 12
Sat Jun 15 10:15:52.453 UTC
interface Bundle-Ether12
ipv4 address 10.1.12.2 255.255.255.252
mac-address 1e.bd01.5031
bundle maximum-active links 2
bundle minimum-active links 1
!
RP/0/RP0/CPU0:PE2#ping 10.1.12.1
Sat Jun 15 10:15:56.152 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.12.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 85/86/87 ms
RP/0/RP0/CPU0:PE2#
Regards,
Mathew
-
- Posts: 5067
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: IOSXRv9000 - ether-channel / port-channel support on EVE-NG
Dear Mat,
my serious advice to you, want do labs on eve, go to EVE Pro![Smile :)](./images/smilies/icon_e_smile.gif)
But its good that you figured it..
Uldis
my serious advice to you, want do labs on eve, go to EVE Pro
![Smile :)](./images/smilies/icon_e_smile.gif)
But its good that you figured it..
Uldis
-
- Posts: 79
- Joined: Wed May 10, 2017 12:11 pm
- Contact:
Re: IOSXRv9000 - ether-channel / port-channel support on EVE-NG
Hi,
Thanks for the support and advice.
Do you mean to say that for the below fix is in EVE-NG Pro and not in Community edition any more?
Please let me know.
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/1# /opt/qemu/bin/qemu-img commit virtioa.qcow2
Image committed.
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/1# /opt/qemu/bin/qemu-img commit virtioa.qcow2
Co-routine re-entered recursively
Aborted
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/2#
Regards,
Mathew
Thanks for the support and advice.
Do you mean to say that for the below fix is in EVE-NG Pro and not in Community edition any more?
Please let me know.
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/1# /opt/qemu/bin/qemu-img commit virtioa.qcow2
Image committed.
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/1# /opt/qemu/bin/qemu-img commit virtioa.qcow2
Co-routine re-entered recursively
Aborted
root@eve-ng: /opt/unetlab/tmp/0/bb080b1c-9074-4c7a-a71a-fafdf5da0c84/2#
Regards,
Mathew
-
- Posts: 5067
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: IOSXRv9000 - ether-channel / port-channel support on EVE-NG
same server but EVE community,
XRv9K 6.6.2
all works
XRv9K 6.6.2
all works
You do not have the required permissions to view the files attached to this post.