Cisco Cisco Multicast Manager 3.1
6
Release Notes for Cisco Multicast Manager 3.1
OL-21271-01
System Requirements
Identification of Down PIM Interfaces
CMM 3.1 trace logic relies on Protocol Independent Multicast (PIM) interface reachability. If any one
of the PIM interfaces along the multicast tree is down, the trace is not completed and the user does not
know the problem. CMM provides a feature to show the users which PIM interfaces are down. The
analysis is done on a per-domain basis.
of the PIM interfaces along the multicast tree is down, the trace is not completed and the user does not
know the problem. CMM provides a feature to show the users which PIM interfaces are down. The
analysis is done on a per-domain basis.
Configurable Login Message
CMM 3.1 provides a login message that is presented to users immediately after they successfully log in
to the application. This message is configurable by an administrator and allows messages of at least 1600
Unicode characters. The message must be specifically acknowledged to continue with the login. Users
can disable this feature, if no login message is desired. Typical uses of such a message are an
unauthorized use warning message or to remind users of planned application downtime, etc.
to the application. This message is configurable by an administrator and allows messages of at least 1600
Unicode characters. The message must be specifically acknowledged to continue with the login. Users
can disable this feature, if no login message is desired. Typical uses of such a message are an
unauthorized use warning message or to remind users of planned application downtime, etc.
Northbound API
CMM provides a software development kit (SDK) that allows you to develop a client application that
communicates with CMM by using Web Services Definition Language (WSDL) messages. The API
operations provided by the SDK allow you to perform tasks such as:
communicates with CMM by using Web Services Definition Language (WSDL) messages. The API
operations provided by the SDK allow you to perform tasks such as:
•
Getting a trace image file from the CMM server for use by your application.
•
Getting the Source and Group (S,G) in a domain or on a device.
•
Getting multicast events.
•
Getting the multicast devices in a domain.
•
Adding Layer 2 devices, Layer 3 devices, or video probes in bulk.
•
Adding, deleting, and viewing polling configurations.
•
Saving global configurations.
System Requirements
This section describes the system requirements for Cisco Multicast Manager 3.1.
Hardware Requirements
Disk Space
•
4-GB or more of free space for CMM application and data
Processors
Cores
•
4 cores for less than 500 devices