Error discovering OcNOS device

[stubarea51]

Error adding OcNOS device.

I'm trying to add a node in EVE-NG to Unimus 2.5.1 which is an OcNOS VM. OcNOS is listed as a supported OS.

However, when I try to discover the device, I get the following error:

Code: Select all

Error: CLI mode change command not supported by device

Discovery log:
Service check:
  SSH: Service available

Service connection:
  SSH: Connection successful

Authentication:
  SSH: Login successful

Device discovery:
  Basic device info: UNSUPPORTED_DEVICE

Discovery of available CLI modes:
  Enable (privilege exec) mode: discovered
  Config (configure) mode: MODE_SWITCH_COMMAND_NOT_SUPPORTED

[Tomas]

I'm trying to add a node in EVE-NG to Unimus 2.5.1 which is an OcNOS VM. OcNOS is listed as a supported OS.

However, when I try to discover the device, I get the following error:
...

Hi, the issue is here:

Code: Select all

Device discovery:
  Basic device info: UNSUPPORTED_DEVICE

This means our existing OcNOS driver was not able to identify the device. I checked the driver, and it was based on:

Code: Select all

 Software Product: OcNOS, Version: 1.3.5
 Hardware Model: DELL S4048ON

Likely when OcNOS runs on a VM it's output is different enough that our driver won't pick it up. Or the OS has changed enough in newer versions that the driver can't recognize it.

I will spin up an OcNOS VM here and check out why it fails

[stubarea51]

Thanks Tomas! I figured that might be the case. They have updated quite a bit since that version which is now up to OcNOS 6.5.2.x

Probably the most notable as it relates to Unimus is the addition of commit/confirm configuration management similar to Juniper and Cisco IOS-XR.

[Tomas]

Thanks Tomas! I figured that might be the case. They have updated quite a bit since that version which is now up to OcNOS 6.5.2.x

Hi. Took a look at this today. Just as an observation - it seems OcNOS changed their versioning scheme, as the 1.3.x version chain was alive all the way to 2020. Then OcNOS seems to have started bumping major versions instead of minors, so we are at OcNOS 6.5.x now. So our driver was (relatively) not that ancient

To the root of the issue tho - the driver will work even on latest OcNOS devices, problems arise when OcNOS runs as a VM (or in GNS3). It doesn't report anything for the hardware it's running:

Code: Select all

OcNOS>show version
Software version: DEMO_VM-OcNOS-SP-PLUS-x86-6.5.2-GA 08/06/2024 14:15:23
 Copyright (C) 2024 IP Infusion. All rights reserved

 Software Product: OcNOS-SP, Version: 6.5.2
 Build Number: 101
 Release: GA
 Hardware Model: 
 Software Feature Code: PLUS-x86
 Software Baseline Version: 6.5.0-164
OcNOS>

This does kinda make sense, as it's a VM. The problem is our OcNOS driver relies on this (to collect it for display in the "Model" field), and since it's empty, the driver fails. Most vendors show "VM" or "x64" at least, so the driver was not written to allow for an empty value here.

Should be an easy fix, we will adjust the driver to report the OcNOS type when the hardware field is empty. The fix should make it into 2.6.0-Beta1