'devices authgroups' command missing

[diegonuevo]

Hi all,

I just deployed a local install following the steps indicated here:

https://github.com/hpreston/nso-getting-started/blob/master/01-installing-nso.md

I'm trying now to set up device authentication, but when I try to enter the following command at the NSO config prompt, I get a syntax error:

devices authgroups group labadmin

It seems the command is not available at all:

admin@ncs(config)# devices auth         
                           ^
% Invalid input detected at '^' marker.
admin@ncs(config)#             
admin@ncs(config)# devices ?
Possible completions:
  check-sync            Check if the NCS config is in sync with the device
  check-yang-modules    Check if NCS and the devices have compatible YANG modules
  clear-trace           Clear all trace files
  commit-queue          List of queued and completed commits
  connect               Set up sessions to all unlocked devices
  device                The list of managed devices
  device-group          Groups of devices
  disconnect            Close all sessions to all devices
  fetch-ssh-host-keys   Retrieve SSH host keys from all devices
  migrate               Migrate the matching devices to a new NED type
  partial-sync-from     Synchronize parts of the devices' configuration by pulling from the network.
  profiles              Device profile parameters
  session-pool          List of pooled NED sessions
  sync-from             Synchronize the config by pulling from the devices
  sync-to               Synchronize the config by pushing to the devices

Any hint on what could be happening?

[vleijon · Accepted solution]

You see no configuration at all there, maybe your aaa settings are wrong somehow? You can try doing ncs_cli -u admin -C --noaaa to turn off aaa for your session that may help.

[diegonuevo]

You nailed it. Disabling AAA works like a charm.

Thank you very much.

[vleijon]

The next question is _why_ aaa is broken for you, if it happens every time it is some kind of installation problem but if it just happens sometimes it might be because you accidentally cleared the database.

[diegonuevo]

I created a new NSO instance with the nso-setup script in another directory and it works fine without the --noaaa option.

I must have screwed up the first instance somehow. The ncs.conf file is identical for both instances, but obviously there must be something different in some file or directory.

Thanks for your help.

[Jason Belk]

Hi!

It might be too late for you, but could help others. We have a DevNet reservable Sandbox and Lab now:
https://blogs.cisco.com/developer/nso-learning-lab-and-sandbox 

which the lab is an adaptation of the one you are going through, but streamlined for the sandbox.