Avaya Site Administration Connection Error 1

[CChambleeJr]

I'm using Avaya Site Administration version 6.0.07. I have a duplicated pair of HP servers running CM 6.0.1. Before I performed a server interchange, I could SAT and SSH into the active server using PuTTY with no issues. I could also access the active server using Avaya Site Administration. However, after performing an interchange, I can no longer connect to the active server via ASA. I can connect with PuTTY just fine, although I did initially get a pop-up regarding the RSA fingerprint, where I had to confirm the new RSA fingerprint/key. That being the case, is there something in ASA that needs to be reset/configured in order to allow it to connect to the duplicated IP address now that the other server is the active one? Seems like this has got to be a fingerprint/key issue with SSH.


===
Chuck Chamblee
ACSS (CM) | CTP | A+

 

[wpetilli]

No, you go into task manager on your PC. highlight and right click on the ASA process and there's a choice for 'set affinity' Click there and you'll see the list of CPU's

 

[CChambleeJr]

I tried setting the affinity on another desktop machine to only CPU 0 for ASA (the older version 6.0.007), and it still won't connect to the "A" server. I think this is an issue unrelated to SSH keys. My issue here is the known_hosts issue, which is resolved by upgrading ASA to SP11.01. Thanks.

===
Chuck Chamblee
ACSS (CM) | CTP | A+

 

[wpetilli]

@CChamblee-- There was another ASA issue mentioned in this thread, which was what the affinity change was for. You're issue with the active server is not tied to this.. sorry about that.