ciscoworks and ssh

Unanswered Question
Apr 29th, 2009

We are having a heck of a time trying to get consistent results on catos boxes whether its 4006's or 6500's running catos . You run a netconfig job and a lot of the 4006's seem to go ok but still get a fair amount of failures say 13 out of 50 saying they could not create a ssh session . SSh is configured on the boxes and you can ssh to the device without an issue , no differences in the configs between ones that work and ones that don't work, running catos 7.6.17. The 6500's have the same issue whether its a sup1 running 7.4.3 or a sup2 running 7.6.21 , these have a much higher job failure rate of probably 75-80% . SSH configured on all boxes. On the ones that fail they will also fail when trying to do netshow commands with ciscoworks . Not sure where to go with this . Think RME is 3.5 . Does ciscoworks have a ssh key cache that might need to be cleared or something of that nature ? Any help appreciated....

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Wed, 04/29/2009 - 17:10

RME 3.5 is obsolete, and no longer supported. Additionally, RME 3.5 only supported SSHv1, so any devices that answer with v2 only would fail. Additionally, if you did not have Common Services 2.2 SP 3 applied, any device which replied with SSH-1.99 would also fail. No, there was no key cache.

You should strongly consider upgrading to LMS 3.1 which includes RME 4.2. This latest version supports both SSHv1 and SSHv2.

Actions

This Discussion