Central Management Console (CMC)

[isack2230]

How can it be configured that if I push a change via the CMC's Send CLI commands that it doesn't show the CMC in alarmed stat?  Isn't it obvious that the config changed since I told CMC to make the change?  

What does "Push required" even really mean?  I already "pushed" the changes using CMC, why does it need to warn me to tell me it has changed?

[BFreed]

This is great news, I always thought it would be nice to click on the 'not equals sign' and it would tell you what is different.

Thanks Riverbed - keep up the great work !

Brian

[cgeary]

Thanks. We have an RFE open for that: 54300. I've added your comments to it.

[-Tuomas-]

Hi all.

One thing that could be usefull, if CMC could tell us how the config has been changed.

Since it already can tell us that the config has been changed.

[ecornwell]

Thanks for the suggestion Derek, that worked.   Things look much better now.

[djewhurst]

If this is just the result of a one-off change, then you can log into the CLI of your CMC and run the following:

enable

stats alarm config_change clear

That should clear the alarm you are seeing.

-Derek

[cgeary]

Please open a new support case for this issue and our TAC team will investigate.

[ecornwell]

Hello,

We recently had a problem with some of our Steelheads locking up.  There was a work around provided by support to put a few lines in the devices to help avoid the problem.  I jumped in CMC and used the send CLI command operation to run it on all our SH's.  Now everyone of them is showing the status:

Connected: Needs Attention (The configuration on appliance has been changed) 

From what I understand, the changes I got aren't something that can be done through the web interface.  Now when we log into CMC it looks like we have a problem with a bunch of devices.  On top of that, since CMC doesn't show the changes its going to push down, I now don't want to use it to configure the devices as I'm afraid it will over write the commands.   If there isn't anything planned for the future to address this, please add it.