Hi Fredrik,
We noticed that the StarOS NED v 4.2.2 has 2 issues with the config tree for setting the boot system priority.
Issue #: 1
The boot priority command throws an error with the latest version of the NED but works fine with an older version of the NED (v4.1.15). Please refer to the below screenshots.
We have a use-case for StarOS upgrade & setting the boot priority is critical for that.
Issue #: 2
In StarOS v4.1.15, I was able to run the boot command and checked the changes on the CDB device tree.
But after doing a sync-from the device the boot configurations are getting wiped off from the CDB device tree.
Is this a known issue? Whom should we forward this to get the NED fixed?
Thanks,
StarOS Version 4.2.2: - Failure
Entering configuration mode terminal
admin@ncs(config)# devices device vpc config staros:boot system priority 12 config /flash/test.cfg image /flash/qvpc-20-21-si.bin
admin@ncs(config-config)# commit
Aborted: Network Element Driver error ned_prepare_cli for device vpc: command: boot system priority 12 image /flash/qvpc-20-21-si.bin config /flash/test.cfg:
Saturday August 27 05:40:42 IST 2016
admin@ncs(config-config)#
Java-VM-Log:
<WARN> 26-Aug-2016::19:05:05.036 ResourceManager Ned-Worker-Thread-0: - class CiscoStarosNedCli not loaded by tail-f classloader, defaulting to package 'UNKNOWN'
<ERROR> 26-Aug-2016::19:05:10.096 NedWorker Ned-Worker-Thread-0: - NedWorker error for ned_prepare_cli
com.tailf.packages.ned.ciscoStaros.CiscoStarosNedCli$ExtendedApplyException: command: boot system priority 12 image /flash/qvpc-20-21-si.bin config /flash/test.cfg:
Saturday August 27 05:34:47 IST 2016
at com.tailf.packages.ned.ciscoStaros.CiscoStarosNedCli.print_line_wait(CiscoStarosNedCli.java:646)
at com.tailf.packages.ned.ciscoStaros.CiscoStarosNedCli.applyConfig(CiscoStarosNedCli.java:1173)
at com.tailf.packages.ned.ciscoStaros.CiscoStarosNedCli.prepare(CiscoStarosNedCli.java:769)
at com.tailf.ned.NedWorker.dorun(NedWorker.java:1402)
at com.tailf.ned.NedWorker.run(NedWorker.java:292)
<WARN> 26-Aug-2016::19:05:10.099 ResourceManager Ned-Worker-Thread-0: - class CiscoStarosNedCli not loaded by tail-f classloader, defaulting to package 'UNKNOWN'
<WARN> 26-Aug-2016::19:05:10.102 ResourceManager Ned-Worker-Thread-0: - class CiscoStarosNedCli not loaded by tail-f classloader, defaulting to package 'UNKNOWN'
Star OS Version 4.1.15: - Successful
Note that the boot configs are gone after doing a sync-from
admin@ncs(config)#
admin@ncs(config)# devices device vpc config staros:boot system priority 12 config /flash/test.cfg image /flash/qvpc-20-21-si.bin
admin@ncs(config-config)# commit
Commit complete.
admin@ncs(config-config)# show full-configuration devices device vpc config staros:boot system
devices device vpc
config
staros:boot system priority 12 image /flash/qvpc-20-21-si.bin config /flash/test.cfg
!
!
admin@ncs(config-config)# top
admin@ncs(config)# devices device vpc sync-from
result true
admin@ncs(config)# show full-configuration devices device vpc config staros:boot system
% No entries found.
admin@ncs(config)#
Hi Giri,
If this is for a customer, you can open a TAC case here:
https://mycase.cloudapps.cisco.com/start?referring_site=wwcontacts
A few days ago Bilal shared this link to a post that shows how to open a TAC case step by step:
Best Regards,
.:|:.:|:. Michel Papiashvili
Thanks Michel.
I’ve opened a TAC case for this.