Crazy error message when SSH’ing from vManage to vEdge

Back story here is I did a factory reset on the software via the command line (#request reset configuration).  After the reload and new ZTP pull I tried to connect to the vEdge via SSH from the vManage command line.

I got the following error:

# request execute ssh username@x.x.x.x

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!

Someone could be eavesdropping on you right now (man-in-the-middle attack)!

It is also possible that a host key has just been changed.

 

This is caused by the SSH hash changing after the new config was applied.  This is to be expected.  I had to have support fix it.  I will update this post when I get a clear response on what they did to fix it.

You have to love the “SOMEONE IS DOING SOMETHING NASTY”.  Never in my wildest dreams did I think I’d see that in production code. 🙂

UPDATE:  To fix this error you need to delete the offending device information from the host file.

Advertisements

How to configure vEdge via command line when attach to vManage

If you try and configure a Viptela device via the command line while a template is attached to it in vManage you get the following error:

Aborted: ‘system is-vmanaged’: This device is being managed by the vManage. Configuration through the CLI is not allowed.

To get around this you’ll need to call support because no one will give you the password needed.  But here are the commands that will let you over ride the vManage attached template.

# unhide viptela_internal
Password: ************   >>NOTE this password changes every time a new version of code is released

(config)# no system is_vmanaged

After this you can configure via the command line to your hearts content.