Use ICMDBA and check the "Space Used Summary" - look at this on the Logger and on the HDS and confirm that the tables are out of date. Check that the replication process on the HDS is connecting and requesting the updates - turn up the trace and watch what's happening there.
when i tried to open the ICMDBA on the HDS server, i get the attached warrning.
is it a normal behavior?
No it's not normal behaviour, but it's not a big deal - I have it on one of my servers too!
It's something to do with the inability to see the other SQL servers in the ICM Domain, but you can always add them manually. If you press OK, it probably opens ICMDBA OK on the HDS. You have to enter the SQL Server hostname to manually to reach (say) the logger.
Bump up the trace in Replication through the registry and just watch it for a bit. You should see messages every second or so as it requests table updates from the Logger. Let's just make sure you are seeing those happen.
So why are the loggers not synchronized? That's a problem and I would concentrate on that. The HDS uploads from the logger its connected to. When you have two HDS, one connected to loggerA and one connected to loggerB, they are updated independently. Because the loggers are normally synchronized, the HDS end up with the same data - but the HDS don't talk to each other.
Looking at the RCD tables, loggerA was last updated on Dec 13 but loggerB has Dec 21. These should be identical (of course) so you need to check loggerA and figure out why it's not being updated.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...