I have been through this in a lot of detail and can tell you that there a few "gotchas" that can trip you up.
The first one is that even if you think you should be using a Deployment Type of Progger (Lab only) because that's what you built, do not set that as your Deployment Type. It simply will not work.
Instead, set the Deployment Type to 4000 Agent Rogger. You can only use the coresident install of CUIC/LD/IdS for a 2000 agent design or for a progger in your lab. But the deployment type must be 4000 Agent Rogger.
Now you need to work on the Infrastructure. This must be absolutely correct - no alerts, 11.5 version showing. All the necessary items there.
Make sure you followed the instructions for the Live Data SQL user you created - this user is not like a CUIC user who can be read only. This user has extensive write capabilities to the AWDB and has the sysadmin role. It needs to write to the database!
Now you may wonder what the Live Data server is doing when it checks the Side A configuration. I could not figure this out from logs on the LD side, but debugged the SQL side and can tell you what the query is. If this fails to find any rows, it says that the Config is invalid.
SELECT
ISNULL(Machine_Host.HostName, Machine_Address.Address) AS HostName,
Machine_Service.ServicePort,
Machine_Service.Pairing,
Machine_Service.ServiceType,
Machine_Service.UserName,
Machine_Service.Password
FROM Machine_Service
INNER JOIN Machine_Host ON Machine_Host.MachineHostID=Machine_Service.MachineHostID
INNER JOIN Machine_Address ON Machine_Address.MachineAddressID=Machine_Service.MachineAddressID
WHERE Machine_Service.ServiceType=7
OR Machine_Service.ServiceType=8
You can see the important tables in the database - Machine_Service is critical. I wrote a query that fetches this table and joins to Machine_Host and Machine_Address and this is very useful. The most important things you must see are the TIP services on the Router and the PG. The ports listed there are also very important, and you can do netstat on those ports on the Router or PG to see if the box is listening and when it's working, you will see the IP address of the CUIC/LD/IdS there in the ESTABLISHED state.
This is the query. It's huge because of all the case statements but it has saved me a lot of time.
SELECT
MachineServiceID,
mh.MachineName,
--mh.MachineType,
CASE mh.MachineType
WHEN 1 THEN 'VM Host (ESXi Server)'
WHEN 2 THEN 'Unified CCE Data Server'
WHEN 3 THEN 'Unified CCE Call Server'
WHEN 4 THEN 'Unified CVP'
WHEN 5 THEN 'Unified CM (unknown type)'
WHEN 6 THEN 'Unified CM Publisher'
WHEN 7 THEN 'Unified CM Subscriber'
WHEN 8 THEN 'Unified CVP Reporting Server'
WHEN 9 THEN 'Cores. CUIC, LD, and IdS Publisher'
WHEN 10 THEN 'Cores. CUIC, LD, and IdS Subscriber'
WHEN 11 THEN 'Unified CVP Operations Console Server'
WHEN 12 THEN 'Finesse'
WHEN 13 THEN 'Gateway'
WHEN 14 THEN 'External Social Miner'
WHEN 15 THEN 'External Unified CM Publisher'
WHEN 16 THEN 'External Unified CM Subscriber'
WHEN 17 THEN 'External CVP Reporting Server'
WHEN 18 THEN 'External CCE HDS'
WHEN 19 THEN 'External Media Sense'
WHEN 20 THEN 'External Enterprise Chat and Email'
WHEN 21 THEN 'External Third Party Multichannel'
WHEN 22 THEN 'Unified CCE Router'
WHEN 23 THEN 'Unified CCE Peripheral Gateway'
WHEN 24 THEN 'Unified CCE LiveData Server'
WHEN 25 THEN 'Unified CCE Primary AW'
WHEN 26 THEN 'Unified CCE Secondary AW'
WHEN 27 THEN 'Unified CCE Progger'
WHEN 28 THEN 'Unified CCE AW'
WHEN 29 THEN 'Unified CCE Rogger'
WHEN 30 THEN 'Enterprise Chat and Email'
WHEN 31 THEN 'Identity Server Publisher'
WHEN 32 THEN 'Identity Server Subscriber'
WHEN 33 THEN 'Finesse Primary'
WHEN 34 THEN 'Finesse Secondary'
WHEN 35 THEN 'Standalone Unified IC Publisher'
WHEN 36 THEN 'Standalone Unified IC Subscriber'
WHEN 37 THEN 'Cisco Virtualized Voice Browser'
ELSE 'Unknown'
END AS MachineTypeName,
mh.HostName,
ma.Address,
--ServiceType,
CASE ServiceType
WHEN 1 THEN 'Peripheral Gateway TIP'
WHEN 2 THEN 'Router TIP'
WHEN 3 THEN 'LiveData Active MQ'
WHEN 4 THEN 'Peripheral Gateway TIP TOS'
WHEN 5 THEN 'Router TIP TOS'
WHEN 6 THEN 'LiveData Storm DRPC'
WHEN 7 THEN 'LiveData Socket.IO'
WHEN 8 THEN 'LiveData Web Service Rest API'
WHEN 9 THEN 'LiveData Cassandra'
WHEN 10 THEN 'Administration & Data Server (AW) Rest API'
WHEN 11 THEN 'Media Routing Peripheral Gateway Connection'
WHEN 1000 THEN 'ESXi'
WHEN 1002 THEN 'AXL'
WHEN 1003 THEN 'Diagnostic Portal'
WHEN 1004 THEN 'ISE Authentication'
WHEN 1005 THEN 'Gateway'
WHEN 1006 THEN 'Management Link'
WHEN 1007 THEN 'Administration'
WHEN 1008 THEN 'SocialMiner REST API'
WHEN 1009 THEN 'Media Routing Peripheral Gateway A'
WHEN 1010 THEN 'Media Routing Peripheral Gateway B'
WHEN 1011 THEN 'Principal AW'
WHEN 1012 THEN 'Context Service'
WHEN 1013 THEN 'Identity Server'
WHEN 1014 THEN 'Publisher/Primary Machine IP Address'
WHEN 1015 THEN 'Identity Server Primary Machine IP Address'
WHEN 1016 THEN 'Identity Server Secondary Machine IP'
ELSE 'Unknown'
END AS ServiceTypeName,
ServicePort,
Pairing,
UserName,
--EnablePassword,
ms.AutoGenerated,
ms.Description
FROM Machine_Service AS ms
INNER JOIN Machine_Address AS ma ON (ms.MachineAddressID=ma.MachineAddressID)
INNER JOIN Machine_Host AS mh ON (mh.MachineHostID=ms.MachineHostID)
ORDER BY ms.AutoGenerated DESC, mh.MachineName ASC
Finally, to be able to run the GRANT SQL statements for your CUIC SQL user as shown in the install guide, you must give that user read permission to the master database. This is not obvious.
Gerard O'Rourke's Blog
Regards
Geoff
