Mailing List Archive

Hi,

responding to Ryan Gelobter ????

Yes, it seems SSH works. Guess the main source of confusion is the Observium PHP script generating them as Dell, rather than SMC. Had sure seen the comment in the source as well, but previously the switches were accessed via telnet, which seems problematic (at least for me)

D

________________________________
From: Dennis Jasch <dennis.jasch@anticlockwise.com.au>
Sent: Wednesday, 24 July 2019 11:40 AM
To: john heasley <heas@shrubbery.net>
Subject: Re: [rancid] Rancid with Dell PowerConnect M8024-k

Hi,

I have tested dllogin, hlogin, and clogin, each with telnet and SSH


* telnet
* dllogin
does not authenticate
* hlogin
does not authenticate
* clogin
works as expected
* SSH
* dllogin
does not authenticate
* hlogin
works as expected
* clogin
works as expected

I attached test output.

I was able to get it to work all the way through via SSH and smc.

I guess the Observium PHP script to generate router.db might need an adjustment to output this device as smc and not dell.

Regards,
Dennis.

________________________________
From: john heasley <heas@shrubbery.net>
Sent: Wednesday, 24 July 2019 3:56 AM
To: Dennis Jasch <dennis.jasch@anticlockwise.com.au>
Subject: Re: [rancid] Rancid with Dell PowerConnect M8024-k

EXTERNAL: This email originated from outside Anticlockwise.

Tue, Jul 23, 2019 at 02:26:34PM +0000, Dennis Jasch:
> Hi,
>
> thanks for the response!
>
> It seems the process is getting stuck at dllogin:
>
> rancid@observium:/opt/rancid/bin$ ./clogin -t 300 -c "show switch;" 10.253.249.55
> 10.253.249.55
> spawn ssh -x -l acadmin 10.253.249.55
> acadmin@10.253.249.55's password:
>
> sy2-blade-chassis-01-sw1>enable
> Password:*********
>
> sy2-blade-chassis-01-sw1#
> sy2-blade-chassis-01-sw1#terminal length 0
>
> sy2-blade-chassis-01-sw1#terminal width 132
> ^
> % Invalid input detected at '^' marker.
>
> sy2-blade-chassis-01-sw1#show switch
>
> Management Standby Preconfig Plugged-in Switch Code
> SW Status Status Model ID Model ID Status Version
> --- ---------- --------- ------------- ------------- ------------- -----------
> 1 Stack Mbr Oper Stby PCM8024-k PCM8024-k OK 5.1.0.1
> 2 Mgmt Sw PCM8024-k PCM8024-k OK 5.1.0.1
>
> sy2-blade-chassis-01-sw1#
> sy2-blade-chassis-01-sw1#exit
>
> sy2-blade-chassis-01-sw1>exitConnection to 10.253.249.55 closed.
> rancid@observium:/opt/rancid/bin$
> rancid@observium:/opt/rancid/bin$
> rancid@observium:/opt/rancid/bin$ ./dllogin -t 300 -c "show switch;" 10.253.249.55
> 10.253.249.55
> spawn ssh -x -l acadmin 10.253.249.55
> acadmin@10.253.249.55's password:
>
> sy2-blade-chassis-01-sw1>
>
> >From here on it just times out eventually.
>
> clogin seems to work just fine. That device is a switch card in a blade chassis, and is fairly "Cisco-esk". So, I would assume dllogin is not quite compatible.

that sure sounds like smc. Can you test with hlogin, which is what smc
uses?

> I had been trying to create a new type in rancid.types.conf, and tell it to use regular clogin - but have not managed to do so yet - any pointers would be highly appreciated.

this depends upon the module; the older monolithic modules like smc have
the login program hard-coded, but the new ones that have 'command' lines
in etc/rancid.types.* utilize the login definition therein.