DX Infrastructure Management

  • Private Community
Back to Library

Tech Tip / How To: CA UIM – Free resources on the primary hub in a tunneled environment 

Dec 13, 2018 11:44 AM

Introduction:
In this scenario the UIM environment has two-tiers. The primary hub is the Tunnel Server and all remote hubs connect to the primary hub as Tunnel Clients.

We need to onboard new Hubs which require a connection over Tunnels. With our current architecture GET/ATTACH queues are configured between our Tunnel Server and Tunnel Clients. Each queue we create on the Primary Hub creates a new subscriber. 

The primary hub is a Windows Server and we are almost at the 64-subscriber limit. How can we proceed?
 
Environment:
UIM v9.0.2
Hub v7.96
Robot v7.96
 
Instructions:
Recommendation from Support: 

Add another tier in this environment to remove the load from the primary hub. Install a new remote hub that will act as the middle tier between the primary and secondary hubs.

The new remote hub should be a Linux Server to avoid any future issues with the subscriber count (Only Windows Servers have a subscriber limit). The new remote hub will be a Tunnel Client. The existing primary and remote hubs will be their own Tunnel Servers that connect to the new remote hub Tunnel Client.
 
Example:
Tier 1: Primary Hub (Tunnel Server)
*Primary Connected to New Remote Hub via Tunnel*
Tier 2: New Remote Hub (Tunnel Client)
*Remote Hubs Connected to New Remote Hub via Tunnels*
Tier 3: Remote Hubs (Tunnel Servers)
 
NOTE: Due to multiple Primary Hub restarts we recommend you schedule down time to carry out the suggested actions.

 Actions to take:
  1. Install the new Remote Hub which will be the Tunnel Client.
  2. Add the new Remote Hub as a Static Hub to the Primary Hub.
    • Open the Primary Hub GUI via IM or AC -> Name Services -> Static Hubs -> New -> enter the new remote hub IP or Hostname -> OK -> Apply and Save the changes. The new remote hub should now be visible in IM / AC.
  3. Configure the Tunnel Server <-> Client connection between the Primary Hub (Tunnel Server) and new Remote Hub (Tunnel Client).  
  4. Create the required GET and ATTACH queues to transfer data between the new Remote Hub and Primary Hub.
    • Open the new Remote Hub GUI via IM or AC -> Queues -> New:
      • Name: Create a name for your queue i.e. alarm_NewRemoteTunnelClient
      • Type: attach
      • Subject: alarm
      • Bulk Size: <default>
    • Once complete select OK -> Apply and Save the changes.
    • An Attach queue collects messages (based on subject) for forwarding to another hub.
  • Open the Primary Hub GUI via IM or AC -> Queues -> New:
    • Name: Create a name for your queue i.e. alarm_from_NewRemoteTunnelClient
    • Type: get
    • Address: /<uim_domain>/<hubname>/<hubrobotname>/hub (Select the hub address of the new Remote Hub)
    • Queue: alarm_NewRemoteTunnelClient (Name of the queue created on the new Remote Hub)
    • Bulk Size: <default>
  • Once complete select OK -> Apply and Save the changes.
NOTE: A Get queue retrieves messages collected by an attach queue on another hub.
  • You will need to repeat the above actions for all required queues, example:
    • QOS_MESSAGE, QOS_DEFINITION, QOS_BASELINE
    • probe_discovery
    • BASELINE_CONFIG
    • PREDICTION_ENGINE, PREDICTION_CONFIG
 
 
The next sections are the steps required for creating the tunnel connection between the Tunnel Servers (Remote Hubs) and the Tunnel Client (New Remote Hub). 
We would suggest following the below actions one Remote Hub at a time. Once complete and the tunnel communication is successful, repeat these actions for your next Remote Hub. 
 
 
  1. Remove the GET queues previously created on the Primary Hub to fetch data from the Remote Servers.
    • Open the Primary Hub GUI via IM or AC -> Queues -> Right click on the queues in question -> Delete.
    • Apply and Save the changes.
    • NOTE: As the ATTACH queues are still configured no data will be lost, the ATTACH queues will queue data until a successful connection is established. 
  2. Add the new Remote Hub (Tunnel Client) as a Static Hub to the Remote Server (will be Tunnel Server).
    • Open the Remote Hub GUI via IM or AC -> Name Services -> Static Hubs -> New -> enter the new remote hub IP or Hostname -> OK -> Apply and Save the changes. The new remote hub should now be visible in IM and AC.
  3. Deactivate the active tunnel connection between the Primary Hub and Remote Server.
    • At this point, you should delete the hubs.sds from primary and remote once more, and restart them. The hub.sds is located here: \Nimsoft\hub.
    • Apply and Save the changes.
    • Open the Primary Hub GUI via IM or AC -> Tunnels -> Client Configuration -> Tunnel Client Setup. Select the Client connection in question and Delete it.
  4. Configure the Tunnel Server <-> Client connection between the Remote Hub (Tunnel Server) and new Remote Hub (Tunnel Client). 
  5. Create GET queues on the new Remote Hub (Tunnel Client) to fetch data using the existing ATTACH queues created on the Remote Hub (Tunnel Server).
    • Open the new Remote Hub GUI via IM or AC -> Queues -> New:
      • Name: Create a name for your queue i.e. alarm_from_RemoteTunnelClient
      • Type: get
      • Address: /<uim_domain>/<hubname>/<hubrobotname>/hub
      • Queue: alarm_RemoteTunnelClient (Name of the queue created on the Remote Hub)
      • Bulk Size: <default>
    • Once complete select OK -> Apply and Save the changes.

Attached to this article is the above instructions in a Word document with an easier format to follow. 
Additional Information:
hub and tunnel connection settings in 7.x and 8.x - https://comm.support.ca.com/kb/hub-and-tunnel-connection-settings/kb000072187

Prepare Your Server Hardware, Secondary Hub Server Requirements - https://docops.ca.com/ca-unified-infrastructure-management/9-0-2/en/installing/pre-installation-planning/prepare-your-server-hardware#PrepareYourServerHardware-SecondaryHubServerRequirements

Receiving Alarm "The Hub *** has too many active subscribers. You should consider to offload some of the subscribers to another Hub." - https://comm.support.ca.com/kb/receiving-alarm-the-hub-has-too-many-active-subscribers-you-should-consider-to-offload-some-of-the-subscribers-to-another-hub/kb000034326https://comm.support.ca.com/kb/receiving-alarm-the-hub-has-too-many-active-subscribers-you-should-consider-to-offload-some-of-the-subscribers-to-another-hub/kb000034326

Statistics
0 Favorited
19 Views
1 Files
0 Shares
1 Downloads
​
Attachment(s)
docx file
Instructions.docx   18 KB   1 version
Uploaded - May 29, 2019
 
Download

Related Entries and Links

No Related Resource entered.