XRV9k Support
Moderator: mike
-
- Posts: 5
- Joined: Thu Apr 20, 2017 7:33 pm
XRV9k Support
I am able to boot XRV9k 6.3.1. Everything goes fine except that the interfaces are not visible in the device.
Only the management interface is available.
I had tried to change the NIC type in XRV9k.php template file from virtio-net-pci to e1000.
Issue does not get resolved.
Any suggestions or tweaks to get the interfaces visible in XRV9k?
Only the management interface is available.
I had tried to change the NIC type in XRV9k.php template file from virtio-net-pci to e1000.
Issue does not get resolved.
Any suggestions or tweaks to get the interfaces visible in XRV9k?
-
- Posts: 54
- Joined: Mon Mar 20, 2017 3:52 pm
Re: XRV9k Support
i've been able to run the 9k with software version 5.4.0 I have not tried 6 code.
-
- Posts: 5
- Joined: Thu Apr 20, 2017 7:33 pm
Re: XRV9k Support
During boot, after initializing the interfaces, following messages are observed:
[ 0.108006] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[ 0.108547] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
This type of message is not being observed when booted using VMware ESXi / Workstation.
I could find the interfaces in Vmware scenario.
Any help / suggestion to avoid these errors in Qemu emulation
[ 0.108006] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[ 0.108547] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
This type of message is not being observed when booted using VMware ESXi / Workstation.
I could find the interfaces in Vmware scenario.
Any help / suggestion to avoid these errors in Qemu emulation
-
- Posts: 533
- Joined: Wed Mar 15, 2017 1:54 pm
Re: XRV9k Support
next release will support xrv9k.
(Gitlab is already updated for full xrv9k support)
E.
(Gitlab is already updated for full xrv9k support)
E.
-
- Posts: 36
- Joined: Wed Mar 22, 2017 6:40 am
Re: XRV9k Support
running on version
nxosv9k-7.0.3.I5.2
support vpc ....finally
nxosv9k-7.0.3.I5.2
support vpc ....finally
-
- Posts: 10
- Joined: Sat Mar 25, 2017 9:29 pm
Re: XRV9k Support
@ rajmohan
did you find any fix for your issue,
I've got the same problem with ios xrv9k 6.1.2,
I can boot it up, but only mgmt int is visible
I'm running eve ver 2.0.3-60
@ecze
that means xrv9k is not supported yet in eve ver am running?
did you find any fix for your issue,
I've got the same problem with ios xrv9k 6.1.2,
I can boot it up, but only mgmt int is visible
I'm running eve ver 2.0.3-60
@ecze
that means xrv9k is not supported yet in eve ver am running?
-
- Posts: 9
- Joined: Mon Apr 24, 2017 8:17 pm
Re: XRV9k Support
Found this:
sramtam
sramtam
Code: Select all
For successful start of xrv9k ver 6.1.2 just change the qemu options in the template file(xrv9k.php) to:
$p['qemu_options'] = '-smbios type=1,manufacturer=cisco,product=CiscoIOSXRv9000 -cpu host -m 16384 -smp cores=4,threads=1,sockets=1 -enable-kvm -display none -serial mon:stdio -rtc base=utc -boot once=d';
Thanks to Rajmohan R.
-
- Posts: 10
- Joined: Sat Mar 25, 2017 9:29 pm
Re: XRV9k Support
I applied the above, rebooted eve-ng, removed xrv hosts from the lab, added them again, booted up xrv9k and still the same
I noticed however, on 6.0.1, that when I checked on first logon, only mgmt was there. couple minutes later int gi0/0/0/0 turn up - weird
Any clue?
I noticed however, on 6.0.1, that when I checked on first logon, only mgmt was there. couple minutes later int gi0/0/0/0 turn up - weird
Any clue?
-
- Posts: 5086
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: XRV9k Support
next release will be fixed
-
- Posts: 7
- Joined: Tue Jun 27, 2017 8:38 pm
Re: XRV9k Support
I am running 6.2.2 and the LC wont come up. I tried it with standard recent version and also tried the fix in the iosxr9k.php file and both show up with same issue.
Here is the console output of the LC failing.
Any ideas?
LC/0/0/CPU0:Feb 6 20:10:14.729 : processmgr[51]: %OS-SYSMGR-3-ERROR : dp_launcher(1) (jid 140) exited, will be respawned with a delay (slow-restart)
LC/0/0/CPU0:Feb 6 20:10:14.730 : processmgr[51]: %OS-SYSMGR-3-ERROR : dp_launcher(140) (fail count 5) will be respawned in 120 seconds
Here is the console output of the LC failing.
Any ideas?
LC/0/0/CPU0:Feb 6 20:10:14.729 : processmgr[51]: %OS-SYSMGR-3-ERROR : dp_launcher(1) (jid 140) exited, will be respawned with a delay (slow-restart)
LC/0/0/CPU0:Feb 6 20:10:14.730 : processmgr[51]: %OS-SYSMGR-3-ERROR : dp_launcher(140) (fail count 5) will be respawned in 120 seconds