Central Management Console (CMC)

[davesalaman]

Tested and confirmed fixed in 6.5.1a

[davesalaman]

Good work Riverbed.

I suspect we might have been hitting ...

86716 Fixed an issue where the appliance configuration alarm would trigger when a secure peer gets automatically added to the white list with a self signed certificate.

Looking forward to testing this release soon.

[-Tuomas-]

Hi, just to let you know.

I have 6.5.1 CMC and no errors that steelheads would be out of sync.

[-Tuomas- · Accepted solution]

Hi, I noticed that 6.5.1 is out and release notes have:

82855 Untrusted appliances which were not auto registered could not be marked trusted in CMC 6.5.0.

Anyone brave enough to test?

[-Tuomas-]

Hi all.

Any updates on this case?

-Tuomas-

[cgeary]

Please open a support case and we'll analyse your CMC sysdump, ideally set it to INFO level and wait for an appliance to become out of sync. Also please upload a sysdump from one of the out of sync Steelheads.

[ecornwell]

I think I've seen the same thing.  Since the upgrade, all of our devices show out of sync.

[ecornwell]

We had about 50% of our SH's installed before we got the CMC.  Most of them showed out of sync.  The new ones all showed that they were in-sync.  Since we upgraded CMC to 6.5 they all show out sync.  I was wondering if the was a way to pull in a new policy again and get the devices that haven't changed to show that they are in sync.

[skipcourt]

I am also having the same symptoms after applying 6.5.0 to our CMC. So far only 2 of my 47 SHA's show the message......All my units are running the 6.5.0a RIOS

[Edwin Groothuis]

Hello Dave,

I haven't heard of this (mis)behaviour yet, my current suggestion is to open a TAC case with them for analysis.

Before you do, turn on info-level logging, sync everything and wait until two or three are out of sync again and then create a system-dump. Note the times that the various events happen for easier investigation.

Let us know how it goes!

Edwin