You can configure ContentReporter to use HTTP or HTTPS to collect log files from one or more NetCache appliances at scheduled intervals.
Note
When you configure ContentReporter to collect NetCache appliance log files, you must synchronize NetCache appliance logging and ContentReporter log file collection to ensure data integrity. If you do not want to synchronize NetCache logging and ContentReporter log file collection, configure your NetCache to push its log files to either a directory or an FTP server. To learn about synchronizing NetCache logging and ContentReporter collection, see Appendix C, Synchronizing logging rotation and log file collection.
ContentReporter provides two methods of adding caches to collect and process NetCache appliance log files:
If you installed SecureAdminTM software on a NetCache appliance, you can configure ContentReporter to use the Secure Sockets Layer (SSL) protocol to securely collect log files from the NetCache. SSL configuration is discussed in Configuring ContentReporter for SSL. You must complete this configuration process before you add a cache to collect and process NetCache appliance log files.
SSL provides an encrypted administrative exchange between a NetCache and a client browser. By default, the ContentReporter server uses port 443 to access the NetCache log files when using SSL. When the ContentReporter server accesses the NetCache appliance log files through SSL, it uses the SSL certificate that you copied to the ContentReporter machine during this configuration process. You can use a self-signed certificate generated by the NetCache appliance, or a CA-signed certificate signed by a trusted authority for secure Web services, such as Verisign, Inc., SecureIT Enterprise, and Thawte Consulting.
Note
For ContentReporter to collect a NetCache appliance's log files using the SSL protocol, you must ensure that you configured the DNS settings of the machine on which you installed ContentReporter so that the ContentReporter server can resolve the fully qualified domain name of the NetCache appliance.
If ContentReporter will collect NetCache log files using the SSL protocol, you must copy the NetCache SSL certificate into the ContentReporter server folder:
..\Network Appliance\ContentReporter\jakarta-tomcat\webapps\ContentReporter\
and save the certificate file as cachename.cer (where cachename is the name you will enter for the cache in the Name field of the New Cache window if you manually add the cache to a cache group and .cer is the required file extension).
See step 8 of Configuring ContentReporter for SSL and step 4 of Manually adding a NetCache appliance.
Note
If you add a cache using the Auto Discovery feature to collect from a NetCache with SSL, save the certificate file as cachename.cer (where cachename is the NetCache appliance's fully qualified domain name and .cer is the required file extension).
The name you enter (when generating the SSL certificate) in the Common Name field in Step 4 (Generate the SSL Certificate) of the Software - SecureAdmin page of the Maintenance tab of the NetCache management console must match the name you specify for the NetCache in the Name or IP Address field of ContentReporter's NetCache Settings window. If these names do not match, the certificate will not be accepted and the log file collection will fail.
See step 5 of Manually adding a NetCache appliance.
Note
By default, the Auto Discovery feature of ContentReporter uses the NetCache appliance's IP address in the Name or IP Address field of the NetCache Settings window. If you add a cache using the Auto Discovery feature to collect from a NetCache with SSL, modify the Name or IP Address field value for the cache after adding the cache with Auto Discovery to match the name you entered in the NetCache management console Common Name field.
To configure ContentReporter to collect a NetCache appliance's log files using the SSL protocol, complete the following steps.
Note
Complete the following configuration steps for each NetCache appliance that will have its log files collected by ContentReporter using SSL.
Note
The following instructions explain how to import a self-signed certificate for Internet Explorer 5.0. Some of these steps will vary for other browsers.
| 1 | |
| 2 | To test whether the ContentReporter server can resolve the fully qualified domain name of the NetCache, enter the following at the command line of the ContentReporter server machine: > nslookup cachename cachename is the fully qualified domain name of the NetCache. Result:Your system displays the results of the nslookup command. If your system found the NetCache, continue with Step 3. If your system did not find the NetCache, ask your IT Administrator to correct this problem, and then continue with Step 3. |
| 3 | |
| 4 | |
| 5 | From the Certificate window, click the Details tab, and then click Copy to File. |
| 6 | |
| 7 | From the Certificate Export File window, select the Base64 Encoded X.509 (.CER) button, and click Next. Result: |
| 8 |
On the ContentReporter server machine, browse to the cachename is the name you will enter for the cache in the Name field of the New Cache window if you manually add the cache to a cache group, or the NetCache's fully qualified domain name if you will use Auto Discovery to add the cache to a cache group .cer is the required file extension To learn more about the certificate name, see Cache Name for SSL. |
| 9 | Click Next to copy the NetCache's certificate into the directory. |
| 10 | |
| 11 | |
| 12 | Click Yes to confirm that you can open the NetCache Manager using the SSL protocol. |
| 13 | |
| 14 | Repeat Steps 1-13 for each NetCache you want to add to a cache group. |
| 15 |
If you prefer to add a NetCache appliance to a group without using the Auto Discovery feature, you can manually add one NetCache at a time to a cache group.
To manually add a NetCache appliance to a cache group, complete the following steps.
| 1 | From a page in ContentReporter, click the Administration tab. |
|
| 2 | ||
| 3 | From the Cache Group tab, select a cache group in the left-hand panel, and click New Cache. |
|
| 4 | In the New Cache window, enter a name for the NetCache, select the Collect from NetCache button, and then click Settings. Note |
|
| 5 | In the NetCache Settings window, enter the NetCache's IP address or fully qualified domain name. Note |
|
| 6 | ||
| 7 | Ensure that the port field displays 3132 if NetCache allows HTTP collection of log files, or select the SSL check box and ensure that the port field displays 443 to allow SSL protocol collection. |
|
| 8 | To test connectivity between ContentReporter and the NetCache, click Test. Result:The Test Cache Connectivity window appears. When ContentReporter completes the test, displays a status of either "available" or "not available." |
|
| 9 | ||
|
||
| 10 | If you want, enter the NetCache model, such as C720, and the NetCache OS version, such as 5.1R2D5. |
|
| 11 | ||
| 12 | Accept the default location to store this cache's log files, or click Browse, select an appropriate directory, and click OK. Note |
|
| 13 | To delete the log files after processing, select the appropriate check box. |
|
| 14 | Accept the default number of error lines (200), or enter another number. If you do not want the number of error lines in a log file to stop the ContentReporter server from processing, enter the number 0. |
|
| 15 | After you enter all the required information, click OK. Result:You return to the Cache Group tab and the cache appears under the cache group in the left-hand panel. |
|
| 16 | Click Apply or OK to save the changes to the ContentReporter server. Result:You successfully added the NetCache to a cache group. |
|
| 17 | Go to Step three: Scheduling log file collection to create a scheduled event to collect and process this cache group's log files. |
|
You can use the ContentReporter Auto Discovery feature to add one or more SNMP-enabled NetCache appliances (for which you have community string names) to a cache group to collect and process log files. You can only discover NetCaches with Class C IP addresses using the Auto Discovery feature. Each NetCache appliance has an IP address consisting of four numbers separated by periods. In ContentReporter, the first three numbers represent the subnet on which the NetCache is located. You can add some or all of the NetCache appliances located on the same subnet at one time with the Auto Discovery feature.
Note
You can only detect SNMP-enabled NetCaches for which you have a community string names with the Auto Discovery feature. For more information, see Appendix C, Enabling SNMP and using Auto Discovery.
To use Auto Discovery to add NetCache appliances to a cache group, complete the following steps.
Note
If you want to use Auto Discovery to discover some NetCaches that allow collection by SSL and others that do not, complete the following steps twice. The first time you complete these steps, select SSL in Step 9, and select only the NetCaches that allow collection by SSL in Step 11. The second time you complete these steps, do not select SSL in Step 9, and select only the NetCaches that do not use SSL in Step 11.
| 1 | From a page in ContentReporter, click the Administration tab. |
|
| 2 | ||
| 3 | From the Cache Group tab, select a cache group in the left-hand panel, and click Discover. Result: |
|
| 4 | Ensure that the appropriate cache group appears in the upper-right Cache Groups field, then click Discover New Caches. Result:The second Auto Discovery window appears.
|
|
| 5 | Enter the subnet on which the NetCache appliances are located. |
|
| 6 | In the Range fields, enter the first and last numbers of the range you want to search for NetCache appliances. Any range between the numbers 1 and 254 is acceptable. |
|
| 7 | Ensure that the correct string appears in the community field to detect the SNMP-enabled NetCaches. The default is "public." |
|
| 8 | ||
| 9 | Ensure that the port field displays 3132 for caches allowing HTTP collection of log files or, check the SSL box, and ensure that the port field displays 443 for caches allowing SSL protocol collection.
|
|
| 10 | After you enter all required information, click Discover. Note Result:ContentReporter searches for all SNMP-enabled NetCache appliances in the range of the subnet that are recognized with the selected community string. |
|
ContentReporter discovers any NetCache appliances in the subnet range, you return to the first Auto Discovery window, and the discovered NetCaches appear in the left-hand Discovered Caches panel. |
Proceed to step 11 to select the NetCache appliances for this cache group. |
|
| 11 | Select the NetCaches in the left-hand Discovered Caches panel, and click Add. Result:The NetCaches appear in the right-hand panel. |
|
| 12 | To test connectivity between ContentReporter and the selected NetCaches, click Test Connection. Result:The Test Cache Connectivity window appears, and, when ContentReporter completes the test, displays a status of either "available" or "not available" for each NetCache. |
|
| 13 | ||
|
||
| 14 |
Result:You return to the Cache Group tab, and the NetCaches discovered with the Auto Discovery feature appear under the cache group in the left-hand panel. |
|
| 15 | ||
| 16 | ||
| 17 | Go to Step three: Scheduling log file collection to create a scheduled event to collect and process this cache group's log files. Note ..\Network Appliance\ContentReporter\jakarta-tomcat\webapps\ContentReporter\cache group name\cache name\. To specify a different location to store a particular cache's log files, you must modify the cache's settings. See step 4 of Modifying a cache's settings. Note See step 6 of Modifying a cache's settings. To learn about the NetCache Common Name field, see NetCache Name or IP Address for SSL. |
|
Copyright © 1994-2001, Network Appliance, Inc. All rights
reserved.
Part No. 210-00066
File: cr3sacc6.htm
Last updated: 12/10/01 11:48:55