Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Issues with registering CTMS to CTSMan

Hi All,

Is there a round trip delay constraint on registering a CTMS to CTSMan.  We have 2 CTMS's, on in Slough, UK and the other in Ohio, US.  Our CTSMan is also in Slough.  The Ohio based CTMS appears to register ok at first, but then errors appear where CTSMan says the CTMS failed to authenticate.   The credentials are correct, so my suspicion is that CTSMan expects an acknowledgement from the Ohio CTMS fast that it is recieving (the round trip delay is 109ms)

Does that sound about right?  What is the recommended way to resolve this?

Kind Regards, Glen

Everyone's tags (2)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Issues with registering CTMS to CTSMan

Hi Glen:

If 109ms is RTT from the Ohio CTMS to CTM in Slough then that should be fine.  Last I checked the default timeout for registration was two seconds.

In your CTS-Manager, do you have your CTMS servers entered with IP address or hostname?  Are CTS-Manager/CMTS configured with specific DNS servers?  CTS-Manager/CTMS versions (I'm assuming you're at 1.7 or 1.8 on both)?

A more common cause of what you describe is lack of DNS; ensure you have your DNS servers set up to resolve for the CTMS in Ohio, as well as CTM in Slough.  Periodic checks are done from both CTM and CTMS.  This is listed in chapter 8 of our CTS-Manager Install/Admin guide:

http://www.cisco.com/en/US/partner/docs/telepresence/cts_manager/1_7/admin/ctm_instalCTS_M.html

You can issue "utils network host " from the CLI of the CTS-Manager, and "utils network host from the CLI of CTMS to see if either fail to resolve.

"DNS configuration for forward name resolution is required for CTS-Manager and all servers configured in CTS-Manager.  All server names can be resolved by DNS from CTS-Manager and CTS-Manager's server name can be resolved by DNS from all other servers."

Also, make sure the correct ports are open between CTMS and CTM (if the servers are secured and this is a new install I'd definitely check this); the list of ports is here:

http://www.cisco.com/en/US/partner/docs/telepresence/security_solutions/ctss_app_a.html

If neither of the two above seem to be the issue, then a TAC case might be a good idea so we can take a look.

HTH -

Tina

1 REPLY
Cisco Employee

Issues with registering CTMS to CTSMan

Hi Glen:

If 109ms is RTT from the Ohio CTMS to CTM in Slough then that should be fine.  Last I checked the default timeout for registration was two seconds.

In your CTS-Manager, do you have your CTMS servers entered with IP address or hostname?  Are CTS-Manager/CMTS configured with specific DNS servers?  CTS-Manager/CTMS versions (I'm assuming you're at 1.7 or 1.8 on both)?

A more common cause of what you describe is lack of DNS; ensure you have your DNS servers set up to resolve for the CTMS in Ohio, as well as CTM in Slough.  Periodic checks are done from both CTM and CTMS.  This is listed in chapter 8 of our CTS-Manager Install/Admin guide:

http://www.cisco.com/en/US/partner/docs/telepresence/cts_manager/1_7/admin/ctm_instalCTS_M.html

You can issue "utils network host " from the CLI of the CTS-Manager, and "utils network host from the CLI of CTMS to see if either fail to resolve.

"DNS configuration for forward name resolution is required for CTS-Manager and all servers configured in CTS-Manager.  All server names can be resolved by DNS from CTS-Manager and CTS-Manager's server name can be resolved by DNS from all other servers."

Also, make sure the correct ports are open between CTMS and CTM (if the servers are secured and this is a new install I'd definitely check this); the list of ports is here:

http://www.cisco.com/en/US/partner/docs/telepresence/security_solutions/ctss_app_a.html

If neither of the two above seem to be the issue, then a TAC case might be a good idea so we can take a look.

HTH -

Tina

439
Views
0
Helpful
1
Replies
CreatePlease to create content