Cisco Cisco StadiumVision Director Manuale Di Manutenzione

Pagina di 103
 
 
© 2012 Cisco Systems, Inc. All rights reserved.   
 
Page 91 of 103 
Cisco StadiumVision Director responds with status code 200 (OK), indicating that it 
recognizes this URL and is able to process it: 
[guest@svd1 httpd]# pwd 
/var/log/httpd 
[guest@svd1 httpd]# grep 10.10.99.20 access_log 
10.10.99.20 - - [08/Sep/2011:06:00:35 -0600] "POST /StadiumVision/dmp_reg 
HTTP/1.1" 200 6796 "-" "curl/7.19.6 (mipsel-unknown-linux-gnu) libcurl/7.19.6 
OpenSSL/0.9.8o zlib/1.2.3 c-ares/1.7.3" 
 
Step 6: Confirm that auto-registration has been enabled. If auto-registration is 
disabled then the following error message will appear in the sv_dev_debug.log file. 
The same message will also appear in the dashboard under the System tab. 
[guest@svd1 logs]# pwd 
/opt/sv/servers/config/logs 
[guest@svd1 logs]# egrep -i 'auto registration' sv_dev_debug.log 
2011-09-08 06:17:16,000 [HPMThreadPoolExecutor-ThreadPool-system]  INFO  
com.cisco.sv.tools.common.SvLoggerFactory  - Auto registration is disabled.  
Discarding registration message from: 10.10.99.20 
 
Step 7: Confirm that auto-provisioning has been enabled. If auto-provisioning is not 
enabled then the following error message will appear in the sv_dev_debug.log file. 
In this case there is no corresponding message posted in the dashboard. 
[guest@svd1 logs]# pwd 
/opt/sv/servers/config/logs 
2011-09-08 06:26:55,574 [HPMThreadPoolExecutor-ThreadPool-system]  INFO  
com.cisco.sv.hpm.endpoint.dmp.CompositeCommand  - Auto provision is disabled, 
device com.cisco.sv.hpm.endpoint:type=DMP,id=181 ,name=181-ip-10-10-99-20-mac-00-
0f-44-01-57-b7 must be manually provisioned by using the 'Provision DMP' command 
 
Step 8: Make sure that the DMP trying to auto-register is not already present in the 
Cisco StadiumVision Director database. If it is present then Cisco StadiumVision 
Director will assume this is an existing DMP that is simply rebooting and hence 
ignore the auto-registration request. The following error messages will appear in the 
sv_dev_debug.log file. The same message will also appear in the dashboard under 
the System tab, but not under the Console tab as you might expect since the DMP 
in question is listed in the dashboard. To correct this situation either delete the DMP 
from the database or change its state to ‘Not Ready’.
 
[guest@svd1 logs]$ egrep -i 'NEW|10.10.99.30' sv_dev_debug.log 
2011-10-20 22:01:06,847 [TP-Processor10] 9968bfae INFO  
com.cisco.sv.autoregister.DMPAutoRegister  - Received DMP auto register message 
from: 10.10.99.30 message: 00:0f:44:01:57:b7 
2011-10-20 22:01:22,204 [HPMThreadPoolExecutor-ThreadPool-system]  INFO  
com.cisco.sv.tools.common.SvLoggerFactory  - Device 'Boulder-A' is not 'NEW', 
ignoring register message