your positive result for 3 indicates that primary comms are ok and that the device prompts are compatible with the existing phrasebooks. not succeeding in step 4 means that none of the existing command sets have matched this device - either because it has no os-info configuration data at all, or because the properties are subtly but sufficiently different from, say, what the ios or iosxr command sets look for. if you add the debug=1 flag to the opconfig-cli invocation you'll get more detailed output about the wheres and whys of the command set selection procedure.
Thanks,
I will try the debug=1 flag today and see what I get
bin
/opconfig-cli
.pl act=test_connect
nodes=node_name
connect to the device properly, or is there an error? Fix this step before continuingbin
/opconfig-cli
.pl act=run_command_sets nodes=node_name This should run all the Command Sets associated with the device type and O/S.
When I run this for the single node I get an error that says "Error: No commands were found to run. None of your nodes matched your criteria."
Hello Matt,
A quick check -
bin
/opconfig-cli
.pl act=test_connect
nodes=node_name
connect to the device properly, or is there an error? Fix this step before continuingbin
/opconfig-cli
.pl act=run_command_sets nodes=node_name This should run all the Command Sets associated with the device type and O/S.
Regards,
Mark H