This chapter contains the following sections:
•Set Up Trace by Management IP Address (Optional)
The trace function in CMM 3.1 and previous releases required access to the PIM interface of the device. CMM 3.2 provides trace functionality in the multicast network even if the PIM interface is not accessible. This is an optional configuration in the event that in your network PIM interface access is restricted across particular points. In most cases, you can use the default setting (trace using PIM interface IP address).
Note The feature is domain specific. The same router can be in multiple domains with some domains using autodiscovery and PIM interfaces for CMM multicast trace and other domains using IP Management addresses for CMM multicast trace.
The Trace by IP Management Address feature is implemented in two files:
•The multicasttrace_type.properties file—A trace configuration file that specifies whether CMM uses the IP management address of the device or the PIM neighbor address of the device to perform a trace.
See Coding the multitrace_type.properties File.
•A CSV file that you provide to list the Management IP addresses and associated SNMP community strings for the devices you will manage using the feature.
See Coding a CSV File to Provide Management IP Addresses.
Implementing Discovery for Trace by Management IP Address
To use the Trace by IP Management Feature, you must perform Discovery using the Contiguous Discovery by Import setting. For information on this setting, see Contiguous Discovery by Import, page 6-12.
Coding the multitrace_type.properties File
The multicasttrace_type.properties file is located in the following directory:
CMMROOT/mmtsys/sys
Example 4-1 shows a sample multicasttrace_type.properties file.
Example 4-1 Sample multicasttrace_type.properties File
#****************************************************
# Copyright (c) 2010 Cisco Systems, Inc.
# All rights reserved.
#****************************************************
# Give 1 -> for Trace using management Ip address and 0 -> for PIM interface ip address
useManagementIp=0
If you need to change the default trace functionality, edit this file to specify the type of trace functionality your CMM installation uses. To specify:
•Trace using IP management address - set useManagementIp=1
•Trace using PIM interface IP address - set useManagementIp=0
In the example above, trace functionality is set to use the PIM interface IP address. In the CMM trace pages, trace functionality shows the same output or both types of trace.
Coding a CSV File to Provide Management IP Addresses
If you are using the Trace by IP Management address feature, then before you perform device discovery, you must code a comma-separated value (CSV) file that provides the management IP address and associated SNMP community string for each device in your multicast network.
The CSV file has the following format:
<ip address>, <snmp community string>
Example 4-2 shows a sample CSV file.
Example 4-2 Sample CSV file for a Domain Using Management by IP Address
10.1.255.1, snmp-ro
10.1.255.1, snmp-ro
The first step in CMM for monitoring the multicast network is to create a domain. A domain is the grouping that you assign to the multicast network. A domain can include Layer 2 (L2) devices, Layer 3 (L3) devices, video probes, and VidMon devices. Multiple domains can exist, and routers can belong to multiple domains. Using Domain Management, you can create and edit domains.
You can create a domain by in two ways:
•By adding the domain and setting the configuration manually.
See Creating a Domain.
•By importing an existing domain configuration from a comma-separated value (CSV) file.
See Importing a Domain.
To create a domain:
Step 1 From the Multicast Manager menu, choose System Configuration.
Step 2 Select Domain Management.
The Domain Management Summary page appears, as shown in Figure 4-1.
Figure 4-1 Domain Management Summary Page
The domain summary page contains all the domain information that has been created for this server and indicates whether the domains have been discovered. You can discover multicast devices by clicking the Start Discovery link for undiscovered domains, and you can rediscover previously discovered domains by clicking the Re-discovery link for the domain.
Step 3 To add a new domain, click the Add button and from the drop-down list, choose By Domain.
Step 4 To edit an existing domain, check the check box for the desired domain listing and click Edit.
If you click Add and choose By Domain or click Edit, the System Configuration page appears, as shown in Figure 4-2.
Figure 4-2 System Configuration Page
The System Configuration page contains the following fields:
Step 5 Complete the fields in the System Configuration page and click Save and then Reset to clear the data fields and create the new domain. Click Cancel to exit without creating a domain.
The new domain name appears in the list of domains on the Domain Management page.
Step 6 If you want to discover the devices in the domain at this time, click on the Start Discovery link in the table row for the domain.
If you click on Start Discovery, the Multicast Discovery page appears, which allows you to enter parameters for the discovery process.
Step 7 For information on the Multicast Discovery page and discovering a domain, see Multicast Discovery, page 6-2.
Rediscovering a Domain
On the Domain Management domains, domains that have been previously discovered have a Re-discovery link in the table row for the domain.
If you want to rediscover the domain, click the Re-discovery link for the domain.
If you click on Start Discovery, the Multicast Discovery page appears, which allows you to enter parameters for the discovery process.
For information on the Multicast Discovery page and discovering a domain, see Multicast Discovery, page 6-2.
To import a domain:
Step 1 From the Multicast Manager menu, choose System Configuration.
Step 2 Select Domain Management.
Step 3 From the drop-down list in the Add field, choose By Import button to import a new domain.
Step 4 Click the Browse button to locate the CSV file that contains the domain information to import.
Step 5 Click the Upload button.
Note After the upload process is initiated, the System Configuration page populates with information.
You can configure each polling element to start and stop at specific times. Each element also has its own polling interval. You can configure these values through the Global Polling Configuration page.
Note You must restart the polling daemon after making changes on this page. Click the Restart button in the Polling Actions field to restart polling. Click the Stop button to stop polling.
To configure global polling:
Step 1 From the Multicast Manager menu, choose System Configuration.
Step 2 Select Global Polling Configuration.
The Global Polling Configuration page appears.
Step 3 On the top part of the Global Polling Configuration page, configure polling intervals and run times for each type of polling, as shown in the following table.
Note Setting any one of these values to less than 1 disables that specific polling feature.
Step 4 Scroll down the page to see the Trap Receiver and Global Default E-mail configuration sections of the page, shown in Figure 4-3.
Figure 4-3 Trap Receiver/E-mail Polling Configuration
Step 5 To enable or disable the continuous sending of PPS threshold traps, use the Enable Rising/Falling and Normalized Traps for Thresholds section:
•If the Rising/Falling option is not checked (disabled), traps are sent whenever the PPS rate for a monitored S,G exceeds specified thresholds.
•If the Rising/Falling option is checked (enabled), a trap is sent only when the PPS rate initially exceeds the high or low threshold. After the PPS rate returns to the specified range, a normalized threshold trap is sent.
•Because SNMP v1 traps are sent unreliably, you can set the Trap-Repeat option to allow the initial and normalized traps to be sent from 1 to 5 times when an event occurs.
Step 6 To add trap receivers, complete these steps:
a. Go to the Configure Global Default SNMP Trap Receivers section.
b. Enter the IP address for the trap receiver.
c. Click the Add button.
The IP address appears in the Configured Trap Receivers list.
d. If you want to forward Mixed Signal traps northbound to another application, check the Forward Mixed Signal Traps check box.
Note If you enable the Mixed Signal trap forwarding option, the Mixed Signal traps are not displayed on the trap viewer page.
Note The SNMP trap receivers specified here are only used if domain-specific SNMP trap receivers are not specified. Domain-specific trap receivers are specified from the Domain Trap/Email Polling Configuration page.
e. Click the Save button.
A message appears instructing you to start the snmptrapd processes to cause the changes in Mixed Signal trap forwarding to take effect.
Step 7 To remove trap receivers, click the IP address of the trap receiver that you want to remove and then click the Remove button, then click Save.
Step 8 To add or remove e-mail addresses, use the Configure Global Default E-mail Addresses for Event Notification section. E-mail addresses are notified of SSG exceptions and threshold related events. The e-mail addresses specified here are used only if domain-specific e-mail addresses are not specified. Domain-specific email addresses are specified from the Domain Trap/Email Polling Configuration page.