02-18-2010 07:02 AM
Hi,
We're running ANM version 3.0 and different ACE software versions in different locations managed by this ANM server.
It seems that ANM never updates the version information running on different ACE modules after first switch/module import.
Certain features like restore/backup are only available after ANM thinks/knows that the ACE is running at least version A2-3.0.
Is there a way to update/refresh this in ANM without deleting and reimporting the whole switch chassis again and again?
--Sebastian
Solved! Go to Solution.
02-18-2010 04:34 PM
Hi Sebastian,
In the current ANM implementation, you need to do a chassis CLI sync after ACE
module upgrade.
You might need to do an ACE module CLI sync after the chassis CLI sync, once
ANM detects some ACE version change (as compared with the version from the
initial chassis import).
Let me know.I tried it and it worked fine.
Venky
02-18-2010 04:34 PM
Hi Sebastian,
In the current ANM implementation, you need to do a chassis CLI sync after ACE
module upgrade.
You might need to do an ACE module CLI sync after the chassis CLI sync, once
ANM detects some ACE version change (as compared with the version from the
initial chassis import).
Let me know.I tried it and it worked fine.
Venky
02-19-2010 08:30 AM
Hi Venky,
thx for the quick response. I tried it and it works for newly imported chassis.
But I see no way to change the username or protocol (telnet/ssh) that ANM uses to log into the supervisor engine after first import.
You can only change the pasword and enable password for chassis CLI Sync.
We have migrated to TACACS authentication for the chassis in the mean time and now I think I'll have to reimport all chassis and modules and have to use my personal tacacs id for ANM to sync.
Do you know any better way to handle this?
Br,
Sebastian
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide