Cisco CUCM - The rhosts file on does not match the publisher

Just a brief note re: checking Cisco CUCM database replication.

I am fond of using the "Cisco Unified Reporting" option in the upper right drop down of the Cisco CUCM web admin interface to verify replication is good.  You can do the same via CLI or via RTMT, but the "Unified CM Database Status" report is a conglomeration of multiple CLI commands in on easy to run report.  Why try to remember all the options when you can run one report?

With that, had you only verified DB replication from CLI or RTMT, you might never encounter the "The rhosts file on XXX.XXX.XXX.XXX does not match the publisher" error.

The easiest first step to regenerate the rhosts file on the offending server is to restart the A Cisco DB service on the server in question.

SSH to the server with the rhosts file out of order.
Run utils service restart A Cisco DB and wait until the process completes.  You should see A Cisco DB[STARTED] when it's successful.
Run your "Unified CM Database Status" report again, and you should be all set.

I can't even imagine something more horrifying...

Cisco WFO QM Calabrio error QMAD2003 sync with UCCX

Installing Cisco WFO Quality Manager 9.0.1 on UCCX 9.0.1 and find there are no agents available in the QM Administrator to license, link or whatever.  When attempting to synchronize database with UCCX from the Administrator menu, I receive a QMAD2003 error popup.   See below...

The QM synch log files indicate failures to reach side A and B.  See below...

2014-02-19 11:53:58,655 INFO SYNC0000 Getting agents...
2014-02-19 11:53:58,836 ERROR SYNC2000
Failed to connect to side A of an ACD connection. Will try side B
2014-02-19 11:53:59,013 ERROR SYNC2001 Synchronization failed with exception.
2014-02-19 11:54:25,829 INFO SYNC0000 Synchronizing [com.calabrio.qm.sync.QmSourceFactory$1@1dec1dd to com.calabrio.qm.sync.target.AgentTargetDao@189c036 using com.calabrio.qm.sync.target.AgentSynchronizer@aa233f].
2014-02-19 11:54:25,829 INFO SYNC0000 Getting agents...
2014-02-19 11:54:26,000 ERROR SYNC2000 Failed to connect to side A of an ACD connection. Will try side B
2014-02-19 12:03:58,504 INFO SYNC0000 Initiating scheduled batch synchronization.
2014-02-19 12:03:58,653 INFO SYNC0000 Synchronizing [com.calabrio.qm.sync.QmSourceFactory$1@1dec1dd to com.calabrio.qm.sync.target.AgentTargetDao@189c036 using com.calabrio.qm.sync.target.AgentSynchronizer@aa233f].
2014-02-19 12:03:58,653 INFO SYNC0000 Getting agents...
2014-02-19 12:03:58,829 ERROR SYNC2000 Failed to connect to side A of an ACD connection. Will try side B
2014-02-19 12:03:59,027 ERROR SYNC2001 Synchronization failed with exception.

The workforce user in UCCX (see password management in UCCX) was simplified in the event extended characters were an issue.  They were set on both UCCX servers in the HA pair and validated to match.  The QM synch service was restarted on the base server and both QM server(s) were restarted entirely.  Was not feeling the love.

Ultimately, the fix was to change the UCCX servers to lower case in postinstall or QM admin.  That's all.  Just change the names to lower case.

Don't mess with the _uccx suffix, don't try adding domain names, don't think you missed anything because I still can't find any Cisco or Calabrio documentation or training video or material that references this requirement.

EDIT: There is reference to name requirements in some Cisco OEM documentation. From the Cisco 901 Quality Management Installation Guide: If the server name contains a hyphen (-), replace the hyphen with an underscore (_) when you enter the server name in this field. This ensures the correct configuration of the file name. Configuration Setup appends _uccx to the name that appears in this field the next time you run Configuration Setup.

Good stuff.

Cisco CER Emergency Responder Native Agent Adapter stopped

Recently performed a bridge upgrade from Cisco Emergency Responder 7 something to 9.0.2.10000-1.  I backed up the production system, installed fresh on a lab server, upgraded to an interim release that could get me to version 9 and that failed miserably.  TAC supplied an installable ISO of the interim version and I was able to install that on the lab server successfully and then upgrade to 9, where I could only do a backup do the nature of the bridge upgrade.  With that, I figured something would go wrong.

After ultimately putting the new 9 version into production and testing alerting and call routing successfully, I poked around to verify health and found the Native Agent Adapter stopped.  I couldn't start it from the Serviceability GUI, nor the CLI.

This was concerning as the description is "This service allows you to forward SNMP requests to another SNMP agent that runs on the system." and given CER relies heavily on SNMP, I was sure I was doomed.

As it turns out, it's a bug, you don't need it, it will never run in VMware, and Cisco is going to make it go away at some point.

There goes an hour of Googling....

CSCto04582    "Native Agent Adapter " service should be removed

Symptom:
VMware install Native agent adapter service is stopped in the CER services page. Cannot be started.
CLI from CER when executing 
utils service list
Native Agent Adapter[STOPPED] Component is not running

Conditions:
VMware installations.. VMware installs will show Native Agent Adapter STOPPED and cannot be started.

Workaround:
There is None. This is a cosmetic error and can be avoided. VMware does not use the Native Agent Adapter and will not start nor can be started.

Google Chrome hangs opening home page downloading proxy settings

Ran into an issue running Chrome Version 32.0.1700.76 m.  Found a fix courtesy of a peer to peer post on Google's support site.  This is a paraphrase...

If it takes a long time to load a website or search, Chrome may be configured to access pages through a web proxy. You may see "downloading proxy settings" in the lower-left corner of the browser window.

To change this in Windows:
Click the Chrome menu on the browser tool bar.
Select "Settings".
Click "Show advanced settings" at the bottom of the page.
In the "Network" section, click "Change proxy settings". This will open the Internet Properties dialogue.
Click "LAN settings".
Deselect the "Automatically detect settings" check box.

See below: