Dec. 18, 2015
A CloudBridge solution requires the CloudBridge product to be present at both sides of the link. This imposes a deployment burden on the remote offices, especially the ones without dedicated IT staff. The autoconfiguration feature of Command Center eliminates this burden by offloading the deployment and configuration effort to the datacenters, thus reducing the effort and expertise required at the branch offices. The autoconfiguration feature eases deployments involving large number of branch offices.
With the autoconfiguration feature, Command Center automates the configuration and deployment of CloudBridge devices in the branch offices. You can use this feature to add new branch devices for either a new deployment or an existing deployment.
The autoconfiguration feature implicitly registers, discovers, and configures a CloudBridge device by using the CloudBridge device identifier and the configuration profile input provided by the datacenter administrator. It requires minimal manual configuration at both the datacenter and the branch offices.
After the initial setup of the CloudBridge device is completed, and the Command Center server IP address is resolved, the branch office user enables the device for registration with the Command Center server.
On completion of automatic registration and configuration on the CloudBridge device, the Command Center server raises an internal event. The information about this configuration is stored in execution logs on the Command Center server. The datacenter administrator can view the progress of the automatic registration, discovery, and configuration on the Command Center graphical user interface (GUI.)
Before you begin configuration, make sure you have the following information:
Branch Office User
The configuration of the autoconfiguration feature requires the datacenter administrator to provide the CloudBridge device serial number or the management service IP address and the configuration profile to the Command Center server. At the branch office, the user needs to power on the device, perform initial setup, and set the device for registration with the Command Center server.
Configuration Steps Performed by the Datacenter Administrator
Configuration Steps Performed by the Branch Office User
After the configuration is complete at both the datacenter and the branch office, the datacenter administrator and the branch office user can monitor and verify the progress and success of the registration, discovery, and configuration process.
Verification at the datacenter
On the Command Center server, navigate to AutoConfiguration tab.and, in the details pane, click the
You can view the registration status and the configuration status of the device in the AutoConfiguration pane, as shown in the following image.
Verification at the branch office
You can apply a license to the device by using the autoconfiguration feature. In such a case, after the autoconfiguration process is completed, the device is licensed with the license file that is specified in the configuration profile.
The License Information tab of the Licensing page displays the details of the license applied to the device.
If the Registration Status column or the Configuration Status column on the Command Center server ( and click AutoConfiguration) does not show a green check mark, check if you see one of the following status messages and take the specified action.
To verify, on the CloudBridge device, after you perform the initial configuration on the setup wizard (CloudBridge Registration Settings screen, check to see if the AutoConfiguration by Command Center flag is unset.), on the
Configuration Profile Sample
########## # System Configuration enable unit enable acceleration enable traffic-shaping ########## # Link Configuration remove link -all add link -name "Link (apA.2)" -type WAN -max-in-bandwidth 10000000 bps -max-out-bandwidth 10000000 bps -adapters apA.2 add link -name "Link (apA.1)" -type LAN -max-in-bandwidth 1000000000 bps -max-out-bandwidth 1000000000 bps -adapters apA.1 #Set the License Server set license-server -location remote -model 2000-050 -ip 10.102.137.44 -port 27000 #Set the apA network configuration set adapter apa -ip 220.127.116.11 -netmask 255.255.255.0 -gateway 18.104.22.168 -vlan enable -vlan-group 75 set dns-server 10.140.50.5 -backup-dns 10.140.50.6 ########## # Date Time Configuration add ntpserver 10.102.76.127 set timezone Asia/Kolkata #Enable video caching.As Enable video caching takes RESTART hence above changes will take effect automatically enable videocaching #Add the Video sources ########## # Video Caching Source and Listen Port List remove videocaching -video-source -clear-enabled remove videocaching -video-source -clear-disabled remove videocaching -video-source -clear-excluded remove videocaching -listen-ports -clear add videocaching -video-source "vimeo.com" -state enable add videocaching -video-source "youtube.com" -state enable add videocaching -video-source "dailymotion.com" -state disable add videocaching -video-source "metacafe.com" -state disable add videocaching -video-source "youku.com" -state disable add videocaching -listen-ports "80" #Add the Pre-population list #Advanced Configuration ########## # Video Caching DNS Suffix, Max Object Size remove videocaching dns-suffix set videocaching -dns-suffix "citrix.com" set videocaching -max-object-size 100 ########## # SYSLOG Configuration add syslog -ip 22.214.171.124 -port 514 # SNMP Configuration enable snmp add snmp-manager -community "public" -ip 10.102.203.199 -netmask 32 add snmp-trapdest -name "MYSNMP_Trap203.199" -ip 10.102.203.199 -port 162 -version v2c -community "public"