UNSUPPORTED_DEVICE for host which was still working yesterday

[swong]

Hello Support team,

We noticed one of our devices in a particular model is no longer supported since last night but the backup was working fine before.
Below is the message in the error log.

Code: Select all

Error: Multiple CLI mode changes failed
MODE_SWITCH_COMMAND_NOT_SUPPORTED
MODE_SWITCH_COMMAND_NOT_SUPPORTED

Discovery log:
Service check:
  SSH: Service available
  TELNET: Service available

Service connection:
  SSH: Connection successful
  TELNET: Connection successful

Authentication:
  SSH: Login successful
  TELNET: Login successful

Device discovery:
  Basic device info: UNSUPPORTED_DEVICE

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

When I issued 'show version' on that device, I got the following output.

Code: Select all

admin@host> show ver
Hardware type      : NXFMB-01

Could you please help?

Thanks,
Steven

[Tomas]

We noticed one of our devices in a particular model is no longer supported since last night but the backup was working fine before.
Below is the message in the error log.

...

Hi, there are a few things that come to mind:
1) Are you using credential discovery or binding?
2) If credential discovery, how many credentials are valid for that device, did you add any new credentials into the system?
3) Are you using Radius or Tacacs for authentication to your devices
4) Is there a chance the security / privileges of your login user (the user that logs in to the device) have changed?
5) have you updated your Unimus server?

In the Discovery fail results, we can see:

Code: Select all

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

Since I don't know what kind of a device this is, this might be OK, but it might be not. If the device needs to be switched to Enable to be Discovered, but the user used for the job doesn't have privilege to execute that command, that would explain why it fails.

Finally, I recommend enabling Device Output Logging (Zones > your_zone > Debug mode), rerunning the discovery, and after it fails, download the Device Output file. You should see the entire CLI conversation in the log. Is there anything that would suggest why discovery fails?

[swong]

Hi Tomas,

Please see my answers next to your questions.

We noticed one of our devices in a particular model is no longer supported since last night but the backup was working fine before.
Below is the message in the error log.

...

Hi, there are a few things that come to mind:
1) Are you using credential discovery or binding?

Binding for Credentials
Discover for Enable password
Discover for Configure password

Remark:
The device doesn't require enable/configure password.
I made a change from 'Discover' to 'Bind' and it still failed the discovery.

2) If credential discovery, how many credentials are valid for that device, did you add any new credentials into the system?

There are four device credentials and only one (the first in the list) works on it.

3) Are you using Radius or Tacacs for authentication to your devices

For this device, we only use local account.

4) Is there a chance the security / privileges of your login user (the user that logs in to the device) have changed?

We didn't make changes to this local account.

5) have you updated your Unimus server?

We didn't for the past 7 days.

In the Discovery fail results, we can see:

Code: Select all

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

Since I don't know what kind of a device this is, this might be OK, but it might be not. If the device needs to be switched to Enable to be Discovered, but the user used for the job doesn't have privilege to execute that command, that would explain why it fails.

It's not a normal switch and it doesn't need 'enable' for configuration change.

Finally, I recommend enabling Device Output Logging (Zones > your_zone > Debug mode), rerunning the discovery, and after it fails, download the Device Output file. You should see the entire CLI conversation in the log. Is there anything that would suggest why discovery fails?

No. I could see it able to do 'show version' and get the output properly.

Will see if I can PM you the output file.

[Tomas]

Hi Tomas,

Please see my answers next to your questions.
...
Will see if I can PM you the output file.

Thank you - I checked the output log, and it looks like the Exablaze driver should pick this up correctly.
Can you please also send me the Debug Log for a failed Discovery run?

Thanks!

[swong]

Hi Tomas,

Please see attached.

I'll PM you the password.

Thanks,
Steven