cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1962
Views
3
Helpful
3
Replies

SX10 VCS Provisioning Server - DNS name when using static IP

Greg Roberts
Level 1
Level 1

Have an SX10 in the lab for testing & evaluation.  When testing the setup assistant, I have been able to point the SX10 to the VCS for provisioning using the IP address, but not the DNS name of the server.  Our video environment uses static IP addressing, so that's the only way I've tried it.  Has anybody else tried this and made it work using DNS server name in either DHCP or static IP environment?

3 Replies 3

Enrico Conedera
Cisco Employee
Cisco Employee

Hello Greg -

Let's assume you are using the Provisioning Wizard. For VCS, you will get to a page that looks like this (you will note I have custom wallpaper): SX10 Provisioning.png

For the Host server address, you can enter either an IP address or a DNS name. Please reference the Cisco TelePresence SX10 Quick Set Getting Started Guide (TC7.1) which can be found here: http://www.cisco.com/c/en/us/support/collaboration-endpoints/telepresence-quick-set-series/products-installation-guides-list.html

The VCS should have a static IP address, not DHCP, which is always our recommendation for infrastructure. The SX10 endpoint can be using either static or DHCP. Either way, as long as the VCS is properly setup with a DNS name, the SX10 should be able to use it for provisioning.

It may be the case that, if you are using static addressing, that the DNS server information did not get entered into your SX10. If it doesn't have DNS server information, then it won't be able to find the VCS using DNS. Looking at the wizard, when you enter static IP address information it does not prompt you to enter DNS server information. I would recommend that at the point in the setup, after confirming the IP address information, you open a web browser and put in your DNS servers.

Then continue your wizard, and the DNS setting for the VCS should work.

Thanks, that worked.  But, it's really a workaround that requires an installer to either browse to the system--or a sys admin to the do same remotely--in the middle of a quick setup/installation process that should only require the handheld remote.

Cisco could remedy this by adding a field for a DNS server in the static IP setup (screen #3 of Setup Assistant).

Greg, you are absolutely correct, and I have already notified the product manager of the need to add DNS server fields to the static IP screen of the setup wizard.