hub raw configuration template missing

[Hong Zhi Lin]

Dear expert,

Version 9.20S / Secure hub & Robot.

First time encounter issue with the hub to hub communication.
No firewall rule. Any any rule applied. 
Both the hubs can talk back to each other. However, When trying to talk back to client server, only secondary hub is successful.   

I just notices that under the raw configuration for hub - ldap - server - template - 1) active directory 2) edirectory and 3) sundirectory was missing?
Is this important? 

I have try to restart the client server and is still not working on primary hub. 

Thanks. 

[Gene Howard]

The LDAP section has nothing to do with HUB to HUB communication.
This is only for authentication and usually only set up on the primary hub.

Question:
Was this ever working?
did you update any robot or hub versions?
did you review the controller log and hub logs at loglevel 3 or higher on both sides of the tunnel?

We would need more information on exact versions and os and probe versions on both sides of the problem to be able to help further.

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[Hong Zhi Lin]

Dear Gene Howard,

Yup agreed that LDAP section is for user authentication. 

It was working before when there is no IPs change. (however, all cert have been recreate as well)
All the robot and hub are the latest version when install to the latest CAUIM 9.2S.
Yup, only stated connect refused at the client server. 
Secondary hub is working all the while with all the tunnel status and queue.  
Unable to tenet 48003 from the client server. But firewall rule is any any.

[Hong Zhi Lin]

Dear Expert,

I might consider upgrade my hub to 9.30.
Will there be any impact when my primary hub is 9.30 and secondary hub is 9.20? 
What are the safe step to upgrade the hub? Backup and screenshot?

[Gene Howard]

I would not try a new version of the hub until you understand what problem you are facing and resolve it.
So far from what you have described a new version, I do not think will help.

I would suggest changing your loglevel to 3 and logsize to 35000 on both sides of your tunnel and restarting the robot watcher server on both hubs and then check the logs for errors.

There is just not enough information to provide you any type of root cause at this time.

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------