Hello,
I have a few IBM Rackswitch G8000 (older units, part of the Rackswitch Family)
Unimus is having trouble doing discovery on it .. (we also have some G8264 & G8124, which are not having an issue )
Failed discovery show log is showing :-
-----------------
Error: Device login failed
Discovery log:
Service check:
SSH: UNAVAILABLE
TELNET: Service available
Service connection:
TELNET: Connection successful
Authentication:
TELNET: CONNECTION_ERROR
---------------
Any suggestion on how we can resolve this would be greatly appreciated.
Thank you.
[Solved] Discovery Trouble -- IBM Rackswitch 8000
-
- Posts: 198
- Joined: Thu Aug 05, 2021 6:35 pm
Hello,
We will need to take a closer look at logs.
Please submit a support ticket via our Portal and we will get back to you with information on what we need.
We will need to take a closer look at logs.
Please submit a support ticket via our Portal and we will get back to you with information on what we need.
-
- Posts: 198
- Joined: Thu Aug 05, 2021 6:35 pm
Update, we found out the issue was this device had turned on terminal logging. This kind of logging will cause issues as it is printing log messages right after prompts, which means Unimus won't be able to recognize a known prompt and Discovery will eventually time out.
There are some rather rare cases when Unimus might even be able to finish Discovery, but we saw in such cases in the past (one example was discussed in this thread), it could also cause other problems such as unwanted debug messages which would be captured during backup. This would trigger false positives in config change notifications.
Our recommendation then would be to:
- not enable terminal logging for the user Unimus uses to communicate with a device, or
- disable terminal logging altogether.
There are some rather rare cases when Unimus might even be able to finish Discovery, but we saw in such cases in the past (one example was discussed in this thread), it could also cause other problems such as unwanted debug messages which would be captured during backup. This would trigger false positives in config change notifications.
Our recommendation then would be to:
- not enable terminal logging for the user Unimus uses to communicate with a device, or
- disable terminal logging altogether.