Multicast Manager. User Guide. Document 5132

Transcription

1

2 Notice Copyright Notice Copyright 2003-present by Aprisma Management Technologies, Inc. All rights reserved worldwide. Use, duplication, or disclosure by the United States government is subject to the restrictions set forth in DFARS (c)(1)(ii) and FAR Liability Disclaimer Aprisma Management Technologies, Inc. ( Aprisma ) reserves the right to make changes in specifications and other information contained in this document without prior notice. In all cases, the reader should contact Aprisma to inquire if any changes have been made. The hardware, firmware, or software described in this manual is subject to change without notice. IN NO EVENT SHALL APRISMA, ITS EMPLOYEES, OFFICERS, DIRECTORS, AGENTS, OR AFFILIATES BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATED TO THIS MANUAL OR THE INFORMATION CONTAINED IN IT, EVEN IF APRISMA HAS BEEN ADVISED OF, HAS KNOWN, OR SHOULD HAVE KNOWN, THE POSSIBILITY OF SUCH DAMAGES. Trademark, Service Mark, and Logo Information SPECTRUM, IMT, and the SPECTRUM IMT/VNM logo are registered trademarks of Aprisma Management Technologies, Inc., or its affiliates. APRISMA, APRISMA MANAGEMENT TECHNOLOGIES, the APRISMA MANAGEMENT TECHNOLOGIES logo, MANAGE WHAT MATTERS, DCM, VNM, SpectroGRAPH, SpectroSERVER, Inductive Modeling Technology, Device Communications Manager, SPECTRUM Security Manager, and Virtual Network Machine are unregistered trademarks of Aprisma Management Technologies, Inc., or its affiliates. For a complete list of Aprisma trademarks, service marks, and trade names, go to: All referenced trademarks, service marks, and trade names identified in this document, whether registered or unregistered, are the intellectual property of their respective owners. No rights are granted by Aprisma Management Technologies, Inc., to use such marks, whether by implication, estoppel, or otherwise. If you have comments or concerns about trademark or copyright references, please send an to spectrum-docs@aprisma.com; we will do our best to help. Restricted Rights Notice (Applicable to licenses to the United States government only.) This software and/or user documentation is/are provided with RESTRICTED AND LIMITED RIGHTS. Use, duplication, or disclosure by the government is subject to restrictions as set forth in FAR (June 1987) Alternate III(g)(3) (June 1987), FAR (June 1987), or DFARS (c)(1)(ii) (June 1988), and/or in similar or successor clauses in the FAR or DFARS, or in the DOD or NASA FAR Supplement, as applicable. Contractor/manufacturer is Aprisma Management Technologies, Inc. In the event the government seeks to obtain the software pursuant to standard commercial practice, this software agreement, instead of the noted regulatory clauses, shall control the terms of the government's license. Virus Disclaimer Aprisma makes no representations or warranties to the effect that the licensed software is virus-free. Aprisma has tested its software with current virus-checking technologies. However, because no antivirus system is 100-percent effective, we strongly recommend that you write protect the licensed software and verify (with an antivirus system with which you have confidence) that the licensed software, prior to installation, is virus-free. Contact Information Aprisma Management Technologies, Inc., 273 Corporate Drive, Portsmouth, NH USA Phone: U.S. toll-free: Web site: Page 2

3 Contents Notice... 2 Preface... 6 Intended Audience... 6 Text Conventions... 6 Document Feedback... 7 Online Documents... 7 Overview... 8 Licensing... 9 Installation and Upgrades... 9 Entering a Activation Key and Expiration Date...11 License Expiration...11 Use Case Scenarios Analyzing Impact of a Device Alarm on Customer Multicast Traffic...12 Troubleshooting - An Individual User is Not Receiving Multicast Traffic...14 Troubleshooting - Multiple Users are Not Receiving Multicast Traffic...16 Troubleshooting - A Threshold Violation has Occurred...17 Interface Accessing...19 Accessing Group Information...21 Accessing Source Information...22 Configuration Accessing Configuration Parameters...23 Model Information...24 Performance Analysis Configuration...25 Page 3

4 Discovery and Modeling Modeling the Multicast Network...26 Multicast Discovery...26 Running Multicast Discovery...27 Discovery Parameters...27 Managing the Multicast Network Searches...29 Group Searches...30 Source Searches...31 Performing a Search...31 Filtering on Search Results...32 Group Information...32 Component Detail for Groups...35 Information Tab...35 Model Information...35 Performance Analysis Configuration...36 Participating Devices...38 Source(s)...38 Rendezvous Point Router...39 Interfaces Tab...39 Performance Tab...40 Events Tab...41 Source Information...41 Component Detail for Sources...43 Information Tab...43 Model Information...43 Source Device...44 Group List...44 Events Tab...45 Trap Support Appendix A: Glossary of Terms Page 4

5 Appendix B: Known Anomalies Appendix C: Devices Supported Index Page 5

6 Preface In This Section Intended Audience [page 6] Text Conventions [page 6] Document Feedback [page 7] Online Documents [page 7] Intended Audience This guide is intended for Help Desk and NOC operators, network administrators, and Multicast administrators. Text Conventions The following text conventions are used in this document: Element Convention Used Example Variables (The user supplies a value for the variable.) The directory where you installed SPECTRUM (The user supplies a value for the variable.) Courier and Italic in angle brackets (<>) <$SPECROOT> Type the following: DISPLAY=<workstation name>:0.0 export display Navigate to: <$SPECROOT>/app-defaults Solaris and Windows directory paths Unless otherwise noted, directory paths are common to both operating systems, with the exception that slashes (/) should be used in Solaris paths, and backslashes (\) should be used in Windows paths. <$SPECROOT>/app-defaults on Solaris is equivalent to <$SPECROOT>\app-defaults on Windows. On-screen text Courier The following line displays: path= /audit User-typed text Courier Type the following path name: C:\ABC\lib\db Page 6

7 Element Convention Used Example Cross-references References to SPECTRUM documents (title and number) Underlined and hypertextblue Italic See Document Feedback [page 7]. SPECTRUM Installation Guide (0675) Document Feedback Please send feedback regarding SPECTRUM documents to the following address: Thank you for helping us improve our documentation. Online Documents SPECTRUM documents are available online at: Check this site for the latest updates and additions. Page 7

8 Overview SPECTRUM s is designed to provide management for multicast traffic within your network environment. This includes the identification and monitoring of all multicast groups, sources, receivers and other critical resources like rendezvous point routers. discovers and models Cisco devices that support multicast. Once these devices have been discovered, provides several views which allow you to monitor the connectivity and performance of these multicast elements. These views offer details relating to multicast groups, sources, receivers, routers, and rendezvous points and their relationships to each other. The information provided in these views makes troubleshooting multicast related outages much more efficient. You can pinpoint a problem quickly because you can determine the group a receiver belongs to, the rendezvous point of the group, the source for the group, the routers and interfaces a group uses, and the configuration and bandwidth limits of these interfaces. Based on this information, you can prioritize your troubleshooting efforts should multiple problems occur. is accessed through the SPECTRUM OneClick interface. The following chapters present various use cases for and introduce each of the views and their functionality. Page 8

9 Licensing This section contains licensing and installation information for the product. In This Section Installation and Upgrades Entering a Activation Key and Expiration Date [Page 11] License Expiration [Page 11] Installation and Upgrades A installation is comprised of both SpectroSERVER and OneClick components. can be installed as part of a SPECTRUM install or by adding it later to an existing installation of SPECTRUM. See the OneClick Console Installation Guide (5142) and the SPECTRUM Installation Guide for your version of SPECTRUM for more information. For distributed SPECTRUM installations see the SPECTRUM Installation Guide for your version of SPECTRUM. Install During SPECTRUM Installation To install as part of an installation of SPECTRUM, follow the appropriate installation procedure in the SPECTRUM Installation Guide for your version of SPECTRUM. Then, see Entering a Activation Key and Expiration Date [Page 11]. Your extraction key must include OneClick and. Page 9

10 Upgrade Existing SPECTRUM Installation to Include Adding to an existing SPECTRUM installation requires you to request a activation key from Aprisma support. To add to an existing installation of SPECTRUM, follow the Installing Additional Components procedure in the SPECTRUM Installation Guide (5136). To add during an in-place upgrade, select in the Components Available view as part of the upgrade. Then, see Entering a Activation Key and Expiration Date [Page 11]. SPECTRUM Installation Including and Latest Patch To install the latest patch over an existing SPECTRUM installation including, skip to the Step 2, and pay special attention to the warning concerning upgrading an existing installation. 1. Install SPECTRUM. 2. Install the latest patch for your version of SPECTRUM. Note: will not be selectable in the Components Available view if it was not previously installed. 3. Install OneClick. 4. Install the latest OneClick patch. 5. Enter your activation key and expiration date in the.vnmrc file (see Entering a Activation Key and Expiration Date [Page 11]). WARNING! Upgrading an existing installation of SPECTRUM with the latest patch overwrites any changes you have made to the.vnmrc file. You must manually re-enter your activation key and expiration date in the.vnmrc file after you install the patch, but before you start the SpectroSERVER. Failure to do this will result in the behavior described in License Expiration [Page 11]. Page 10

11 Entering a Activation Key and Expiration Date After you have installed, you must manually enter your activation key and expiration date in your.vnmrc file by following the procedure below. Procedure To activate your license, you must edit your.vnmrc file to reflect your activation key (different from your SPECTRUM activation key) and expiration date. To do this, after installing and prior to starting the SpectroSERVER, add the following values to the SpectroSERVER s.vnmrc file (located in <$SPECROOT>/SS/.vnmrc): mcastpassword=< Activation Key> mcastexpdate=<mm/dd/yyyy> Changes to the.vnmrc file take effect either the next time the SpectroSERVER is started or, in cases where you do not wish to cycle the SpectroSERVER, a maximum of 10 minutes after adding a valid mcastpassword and mcastexpdate to the.vnmrc file. License Expiration When you are within 10 days of the expiration of the license, the following message will appear at the bottom of the Modeling the Multicast Network [Page 26] view: Warning: The license will expire in 3 days. Please contact your SPECTRUM support representative. Once the license has expired, the following message will appear: The license has expired. Please contact your SPECTRUM support representative. In addition, a message indicating that the license has expired will appear in the event log. The Multicast Discovery [Page 26] functionality will be disabled once the license expires. You will still be able to click the start button for discovery, but the discovery process will not run. The background discovery (see Modeling the Multicast Network [Page 26]) process will also be disabled once the license expires. Page 11

12 Use Case Scenarios The following sections describe typical use case scenarios for employing the application. Scenarios Analyzing Impact of a Device Alarm on Customer Multicast Traffic [Page 12] Troubleshooting - An Individual User is Not Receiving Multicast Traffic [Page 14] Troubleshooting - Multiple Users are Not Receiving Multicast Traffic [Page 16] Troubleshooting - A Threshold Violation has Occurred [Page 17] Analyzing Impact of a Device Alarm on Customer Multicast Traffic Description Two unrelated trouble tickets against two core routers are generated at nearly the same time. The trouble tickets are routed based on the device class. They are sent to the level 2 operations group. This group focuses solely on maintaining the core routing infrastructure. The company's network management application has identified the routers in question and their offending components. The level 2 support group currently has a backlog of 25 open tickets for a variety of issues. The operators are currently using their knowledge of the core network to make decisions regarding issue prioritization. Results without The level 2 operators are unable to understand the impact a failed network device has on the multicast topology and therefore do not know which multicast groups (and consequently which applications) are no longer available. The operator cannot determine if the outage has a minor impact Page 12

13 (non-critical application) or a critical impact (such as real time market orders). As a result, the operator does not know how to prioritize the two trouble tickets. This potential inability to properly prioritize the correction of network faults may result in non-critical faults being addressed before critical faults. Results with The help desk is expected to diagnose a problem and contact the customer within five minutes (depending on the number of open trouble tickets). With SPECTRUM and, the relationship between physical layer faults and multicast streams is clear, and the highest priority problem can be addressed first. Assumptions 1. The customer has previously installed and configured Multicast Manager. 2. The customer has completed a discovery of their physical network. 3. The customer has completed a Multicast Discovery [Page 26]. 4. All multicast services have been modeled with SPECTRUM. 5. There are a couple of outages and the operator must analyze how these outages affect the multicast topology. 6. There is currently only one network administrator available to handle trouble tickets. Scenario with SPECTRUM and 1. The first router in the network goes down and is detected by SPECTRUM. Very shortly after this, the second router goes down. 2. SPECTRUM generates the an alarm for each of the routers that has gone down. 3. The network management system (NMS) operator receives the alarms in the OneClick console and verifies the SPECTRUM alarms by pinging the routers and not receiving a response. (See the OneClick Console (5130) for more information on managing alarms.) 4. The NMS operator receives an alarm generated on one of the multicast groups modeled by. Page 13

14 5. The NMS operator clicks on the multicast group in the OneClick console Alarms tab. 6. The NMS operator opens the Participating Devices [Page 38] section of the group s Information tab and sees that one of its routers has a Down (Red) condition. This router is one of the routers that an alarm was generated on in Step 2. The network operator now understands that this router is critical to the operation of this multicast group, and of a higher priority than the other router issue. 7. The network operator creates a trouble ticket for the router which is impacting the multicast group. This ticket will show that the problem is a high impact outage and will include information on the impacted groups and applications. The network operator assigns the ticket to the network administrator. 8. The network administrator receives the trouble ticket and begins troubleshooting this high impact problem. 9. The network operator creates a trouble ticket for the second router outage that does not affect the multicast topology and assigns it to the network administrator. 10. The network administrator receives the second trouble ticket and will begin work on it after the multicast problem is resolved. SPECTRUM has allowed the troubleshooting process to be prioritized to the most critical fault. Troubleshooting - An Individual User is Not Receiving Multicast Traffic Description When the stock market opens every day at 9:30 A.M., a multicast feed is established to send real time market data to all the brokers on the company's network. The multicast group uses PIM Sparse mode to communicate to the traders who are widely dispersed throughout the company's operations. Today one broker is not receiving the market data feed but is receiving other multicast traffic. Results without The network operator must consult with the applications group to identify the multicast group that the market data feed uses. Once the group has been determined, the network operator must find the group s IP address. Page 14

15 The operator then uses telnet to determine which router has stopped forwarding the multicast stream to this address. The time it takes to diagnose the problem is fairly significant due to the distribution of responsibility between the application support and network support staff and the time necessary to determine which router is causing the problem. Results with The help desk is expected to diagnose a problem and contact the customer within five minutes (depending on the number of open trouble tickets). The customer is able to diagnose the problem more quickly with Multicast Manager. Each of the application administrators saves a good deal of time because they are not duplicating each other s efforts by troubleshooting multiple symptoms of the same problem. Assumptions 1. The customer has previously installed and configured Multicast Manager. 2. The customer has completed a discovery of their physical network. 3. The customer has completed a Multicast Discovery [Page 26]. 4. All multicast services have been modeled with SPECTRUM. 5. The broker has reported that he is no longer receiving the market data feed. Scenario with SPECTRUM and 1. The Operator sees a SPECTRUM alarm in the OneClick console indicating that the router port has failed. (See the OneClick Console (5130) for more information on managing alarms.) 2. A trouble ticket is created and the operator begins troubleshooting the router port issue. 3. As part of his troubleshooting procedure the operator uses Multicast Manager Groups by Interface search (see Group Searches [Page 30]) to see all the groups that are affected. 4. This view shows all the affected groups and their priority. Groups 1-3 are affected by this router. 5. In addition, a broker reports that he is no longer receiving the multicast data feed for group 2. Page 15

16 6. The operator can tell the broker that he is part of the affected group (due to the router failure). A second trouble ticket does not need to be created. 7. The operator fixes the router interface. 8. The router interface is working and market data is now being received by the broker reporting an outage. 9. The operator confirms multicast traffic is being received by the broker and closes the trouble ticket. 10. Network operation is completely restored. The operator begins investigating why the port failed. Troubleshooting - Multiple Users are Not Receiving Multicast Traffic Description At the same time each day a single multicast stream is started. Today the source is started, but none of the users are seeing the multicast traffic, and consequently the business application used by everyone is not functioning. Results without It may take the network operator 1 to 2 hours to determine the actual cause of this failure. Results with It will take the network operator 1 minute to determine the cause of failure. Assumptions 1. The customer has previously installed and configured Multicast Manager. 2. The customer has completed a discovery of their physical network. 3. The customer has completed a Multicast Discovery [Page 26]. 4. All multicast services have been modeled with SPECTRUM. Scenario with SPECTRUM and 1. Several users contact the network operator saying they are not receiving multicast data. Page 16

17 2. The operator brings up in the OneClick console and does a search on All Groups (see Group Searches [Page 30]). 3. The results of the search are shown in the Contents panel (see Group Information [Page 32]) and all groups have a red condition. 4. The operator examines the source for each group in the Information section of the Component Detail panel (see Source(s) [Page 38]). 5. The operator finds no errors; all sources are operating properly. 6. The operator checks the Rendezvous Point Router for each group (see Rendezvous Point Router [Page 39]). 7. The operator finds that the condition of one of the rendezvous point routers is red, indicating that it is down. 8. The operator searches through open trouble tickets and finds a trouble ticket for a router, which is the rendezvous point for the group in question. 9. The Operator reboots the rendezvous point router and alarm is cleared. 10. Multicast traffic is restored to the network. The Operator confirms that the users have service and the trouble ticket is cleared. Troubleshooting - A Threshold Violation has Occurred Description At 10:00 A.M., users stop receiving multicast traffic and consequently the business application needed by these users is not functioning. Results without It may take the network operator 1 to 2 hours to determine the actual cause of this failure. Results with It will take the network operator a few minutes to research the cause of failure. Page 17

18 Assumptions 1. The customer has previously installed and configured Multicast Manager. 2. The customer has completed a discovery of their physical network. 3. The customer has completed a Multicast Discovery [Page 26]. 4. All multicast services have been modeled with SPECTRUM. 5. The performance monitor configuration has been set up to generate alarms when a performance threshold is violated (see the group model s Performance Analysis Configuration [Page 36]). 6. The Device Performance Alarms parameter must be set to enable (see the model s Performance Analysis Configuration [Page 25]). Scenario with SPECTRUM and 1. Several users contact the network operator saying they are not receiving multicast data. 2. The operator brings up in the OneClick console and does a search on All Groups (see Group Searches [Page 30]). 3. One of the groups shows an Orange condition, indicating a major alarm on one of the elements of the group. 4. The operator checks each of the devices in the group and finds an alarm on one of the routers. This alarm is also shown in the OneClick alarm console. 5. A trouble ticket is created. The operator begins troubleshooting the router issue and discovers that one of the interfaces on the router is dropping packets. This generated the alarm on the group model, because the traffic tracked by the performance monitor had fallen below the assigned threshold. 6. The operator resolves the port issue and closes the trouble ticket. 7. Multicast traffic is restored to the network. 8. Operator confirms service with users. Page 18

19 Interface This section provides an overview of the interface delivered on the OneClick platform. For additional information about OneClick, see the OneClick (5130). In This Section Accessing [Page 19] Accessing Group Information [Page 21] Accessing Source Information [Page 22] Accessing Once you have brought up the OneClick console, you can access the Explorer tab of the Navigation panel. This tab includes the Multicast Manager model (MCastManager) and device icons in its hierarchical view. The navigational hierarchy for is shown in Figure 1. This navigational hierarchy from the top down level is: (MCastManager) > Multicast Groups > Devices in the Multicast Group From the model you can access Configuration [Page 23] and Discovery and Modeling [Page 26]. Page 19

20 Figure 1: Model Multicast Group Routers and Switches in Multicast Group Page 20

21 Accessing Group Information Figure 2 shows the Locator tab, which allows you to access multicast searches. Results of a search are shown in the Contents panel. Detailed information about the model selected in the Contents panel is shown in the Component Detail panel. To view details about each section of the interface, click an area on the image below when your cursor changes to. Figure 2: Viewing Group Information in Page 21

22 Accessing Source Information Figure 3 shows the Locator tab, which allows you to access multicast searches. Results of a search are shown in the Contents panel and detailed information about the model selected in the Contents panel is shown in the Component Detail panel. To view details about each section of the interface, click an area on the image below when your cursor changes to. Figure 3: Viewing Source Information in Page 22

23 Configuration This section discusses the Configuration parameters available to users with administrative privileges. In This Section Accessing Configuration Parameters [Page 23] Model Information [Page 24] Accessing Configuration Parameters The multicast configuration parameters are available to all users with administrative privileges. To access these parameters, select the Multicast Manager model (MCastManager) from the Contents panel and choose the Information tab in the Component Detail panel as shown in Figure 4. Note: If you are working in a distributed environment, you will be asked to select the appropriate SpectroSERVER. The Model Information [Page 24] and Performance Analysis Configuration [Page 25] selections in the Component Detail panel give you access to configuration parameters. Page 23

24 Figure 4: Accessing Configuration Parameters Model Information The following parameter can be set in the Model Information section: Default Group Priority: This sets the default group priority value given to a group when it is created. This value defines the relative importance of the group and can be used by the network operator to prioritize troubleshooting resources when there are problems with multiple groups. This value can be changed for a specific group in the individual group model s Information Tab [Page 35]. Page 24

25 Performance Analysis Configuration The following parameters can be set in the Performance Analysis Configuration selection: Collection Interval (Seconds): This parameter determines the interval at which the devices are sampled to obtain performance information. The default value is 300 seconds (5 minutes). Lowering the interval may have a negative impact on the overall SpectroSERVER performance. Device Performance Alarms: This parameter is used to enable or disable the generation of multicast performance based alarms on the device. If enabled, alarms are produced on the device model(s) in the group causing the threshold violation. By default, this parameter is set to Disable. Performance Analysis: This attribute is used to enable or disable the entire Multicast Performance Monitoring system. By default, it is set to Enable. You can also enable or disable performance monitoring on a Group model basis. See the individual group model s Performance Analysis Configuration [Page 36] for more information. Page 25

26 Discovery and Modeling This section gives instructions on discovering and modeling your multicast network environment. In This Section Modeling the Multicast Network [Page 26] Multicast Discovery [Page 26] Modeling the Multicast Network SPECTRUM discovers and models the physical network infrastructure via AutoDiscovery, manual modeling, or the Modeling Gateway. Before using the Multicast Discovery [Page 26] functionality in, you must first model the physical components of your network in SPECTRUM using one of these methods. See the AutoDiscovery (0727), How to Manage Your Network with SPECTRUM (1909), and the Modeling Gateway Toolkit Guide (5069) for instructions on using these mechanisms to model your network. Multicast Discovery Once the physical network components have been discovered, network elements which implement the multicast MIBs supported by Multicast Manager can be discovered and modeled. This discovery is based on the MIBs specified in the table shown in Appendix C: Devices Supported [Page 50]. These MIBs provide the information required to identify all the primary multicast components. models multicast groups, sources, receivers, and rendezvous points. To do this, uses Group, Source, Receiver, and RP (rendezvous point) model types. Group models represent a domain-wide multicast data stream. The source and receiver models are used to represent the producer and consumer of information in a multicast network. The RP model will be used to represent the rendezvous point for a multicast group. Page 26

27 Running Multicast Discovery You must log in with administrator privileges to run Multicast Discovery. 1. Select the model (MCastManager) in the Contents panel. 2. Choose the Information tab in the Component Detail panel as shown in Figure If you are working in a distributed environment, you will be asked to select the appropriate SpectroSERVER. 4. Open the Multicast Discovery section (Figure 5) in the Information tab. 5. Set the appropriate Discovery Parameters [Page 27]. 6. Click the Run button to begin Multicast Discovery.The Discovery Status field shows the status of the discovery process. Figure 5: Multicast Discovery Discovery Parameters The following discovery parameters can be set: Discovery Polling Interval: This interval determines how often (in seconds) will poll the attribute in the CiscoIPMRoute MIB to determine if new multicast groups, sources, or routers exist. Enable Port Polling: If this parameter is set to true, will poll devices at the port level for multicast information. Enable Background Discovery: When background discovery is set to true, events are created when new multicast groups, sources or routers become active on the network. Events for new groups and Page 27

28 sources are asserted on the model. Events for new multicast routes are asserted on the applicable device model. To determine if a new entity has become active, polls an attribute in the Cisco IPMRoute MIB which counts the number of entries in the multicast routing table. Page 28

29 Managing the Multicast Network This section shows you how to access information and statistics to allow you to manage your multicast environment. In This Section Searches [Page 29] Group Information [Page 32] Component Detail for Groups [Page 35] Source Information [Page 41] Component Detail for Sources [Page 43] Searches The Locator view (Figure 6) allows you to access Group Searches [Page 30] and Source Searches [Page 31]. Page 29

30 Figure 6: Locator View Search Button Multicast Searches These searches allow you to find multicast groups and sources by specified criteria. Group Searches The following group searches are available: All Groups: This search locates all of the multicast groups on the network. Groups by Interface: This search allows you to find all groups that relate to a specific interface. The interface is identified by the model name. Groups by IP Address: This search locates the group whose IP address matches the IP address entered in the search field. Page 30

31 Groups by Name: This search locates all groups whose name contains the string entered in the search field. Groups by Receiver: This search allows you to find all groups that relate to a specific receiver. The receiver is identified by the model name. Groups by Rendezvous Point: This search allows you to find all groups that relate to a rendezvous point. The rendezvous point is identified by IP address. Groups by Router: This search allows you to find all groups that relate to a router. The router is identified by the model name. Groups by Source: This search allows you to find all groups that relate to a specific source. The source is identified by IP address. Source Searches The following source searches are available: All Sources: This search yields all of the multicast sources on the network. Sources by Group: This search allows you to find all sources that relate to a specific group. The group is identified by IP address. Sources by IP Address: This search locates the source whose IP address matches the IP address entered in the search field. Sources by Name: This search locates all sources whose name contains the string entered in the search field. Performing a Search To perform a search: 1. To select a search, double click on the name of the search that you would like to perform. 2. For searches other than All Groups or All Sources, enter the desired search criteria in the Search Field(s). The search criteria is case sensitive. 3. Click Ok to start the search. 4. The search results will be displayed in the Contents panel (see Group Information [Page 32] and Component Detail for Groups [Page 35]). These results can be further filtered (see Filtering on Search Results [Page 32]). Page 31

32 Filtering on Search Results A smaller sub-set of the search results can be identified by filtering the results that are currently displayed. To filter the results of a search: 1. Perform the desired search. See Performing a Search [Page 31]. 2. Type the filter criteria in the Filter field at the top of the Contents panel (Figure 7). This filter criteria will be applied to the first column of the search results. To change the column order, click on the appropriate column and drag it to the desired position. 3. To clear the filter, remove any criteria from the filter field. Group Information The results of Group Searches [Page 30] are displayed in the Contents panel (Figure 7). The following information is presented about each group: Condition: The group condition reflects the overall health of the group. It is calculated based on the condition of the rendezvous point routers, source, interconnecting routers, and router interfaces within the group. There are four possible conditions: Initial (blue), Normal (green), Degraded (orange), and Down (red). If the condition of the group is either Degraded or Down, an alarm will be generated on the group model. The condition displayed is based on the values in Table 1. Page 32

33 Table 1: Group Condition Group Condition Performance Monitor Alarm Condition RP Modeled RP Contact Status is Established Source Modeled Source Contact Status is Established Interface Contact Status is Established Router Contact Status is Established Good Good Y Y Y Y Y Y Minor Minor Y Y Y Y Y Y Major Major Y Y Y Y Y Y Critical Critical Y Y Y Y Y Y Good Initial Y Y Y Y Y Y Minor Good Y Y Y Y N N Minor Minor Y Y Y Y N N Major Major Y Y Y Y N N Critical Critical Y Y Y Y N N Minor Initial Y Y Y Y N N Critical Good Y N Y N Y Y Critical Minor Y N Y N Y Y Critical Major Y N Y N Y Y Critical Critical Y N Y N Y Y Critical Initial Y N Y N Y Y Good Good N N/A N N/A N/A N/A Minor Minor N N/A N N/A N/A N/A Major Major N N/A N N/A N/A N/A Critical Critical N N/A N N/A N/A N/A Initial Initial N N/A N N/A N/A N/A Note: In order for to determine the condition of a group, the group s source(s) and rendezvous point must be modeled in SPECTRUM and must be contained in the same SPECTRUM landscape. Name: The name of the group. This may be the actual name, or the IP address of the group. Page 33

34 Group Priority: The Group Priority value defines the relative importance of the group and can be used by the network operator to prioritize troubleshooting resources when there are problems with multiple groups. The smaller the number the higher the level of priority. Administrators can set this value in the Information Tab [Page 35]. Mode: The multicast mode of the group. The value can be either sparse or dense. Type: The model type of the group model. Model Class: The model class of the group model. For more information on a model type s model class, see the SPECTRUM Concepts Guide (0647). This list of groups can be further defined using the Filter button. See Filtering on Search Results [Page 32] for further instructions. Figure 7: Group Information in the Contents Panel Page 34

35 Component Detail for Groups The Component Detail panel (Figure 8) contains tabs that let you view additional information based on the Group model selected in the Contents panel. Figure 8: Component Detail Panel for Group Models Information Tab The information tab provides the following sections for the Group model chosen in the Contents panel: Model Information The following information is shown for the group model: Group Address: The IP address of the group. Rendezvous Point: The rendezvous point that the group is connected to. Group Priority: The Group Priority value defines the relative importance of the group and can be used by the network operator to prioritize troubleshooting resources when there are problems with multiple groups. The lower the value of Group Priority for a given multicast Page 35

36 group, the higher its priority. If you are signed on as an administrator, you may edit this field by clicking Set. Model Class: The model class of the Group model. For more information on a model type s model class, see the SPECTRUM Concepts Guide (0647). Creation Time: This shows the creation date and time of the group model. Landscape: The SPECTRUM landscape to which the Group model belongs. Notes: This field allows you to add new notes or view existing ones. To add a note, click Set. Type the appropriate information. When you have finished typing the note, click Save. If you do not want to save the note that you entered, click Cancel. Performance Analysis Configuration Performance analysis can tell you important information about the flow of multicast traffic on your network. In a properly functioning multicast network, each point of the network (where multicast is enabled for that group) should experience the same traffic flow in packets per second or bytes per second. Any deviation from the traffic level as measured at the source could indicate one or more of the following scenarios: - A change in group membership. - A change in routing where multicast traffic is taking a different path due to load balancing, a redundant failover, or a change from Shared to Source mode. - A change in the network s multicast configuration where multicast has been disabled on an interface or device. - A change in interface status. - Device or link instabilities. The following parameters allow you to configure how analyzes the performance of the Group model selected. A graphical representation of source traffic is also available (see the Performance Tab [Page 40]). Note: To access performance configuration parameters that apply across all Group models, see Performance Analysis Configuration [Page 25]. Page 36

37 Global Group Performance Analysis: This value indicates if the entire Multicast Performance Monitoring system is enabled or disabled. It can be set in the model s Performance Analysis Configuration [Page 25]. The value of this parameter must be set to enable in order for the Group Performance Analysis to function. Group Performance Analysis: Set this value to true to enable performance monitoring on a per group basis. Percent Degradation Threshold: This parameter defines the percent variation allowed in the monitoring of group performance. For example, if the source is measured at 100 pps, all other points in the network receiving this group should be within this percent threshold (+/-). Otherwise, a threshold violation is noted for the group on that device. The default value is 3 percent. Group Performance Alarms: Set this value to true if you want Multicast Manager to create an alarm in response to the violation of performance thresholds defined in the Minor, Major, and Critical Alarm Threshold parameters. Minor Alarm Threshold: This parameter sets the Minor Threshold Percent. This value is used to determine the severity of threshold violations on a group. For example, a group may have 100 interfaces sampled in the network. If more than the Minor Alarm Threshold percentage and less than the Major Alarm Threshold percentage of those samples are in violation of the Performance Degradation Threshold, a Minor event (and an alarm if Group Performance Alarms is set to true) is generated. Major Alarm Threshold: This parameter sets the Major Threshold Percent. This value is used to determine the severity of threshold violations on a group. For example, a group may have 100 interfaces sampled in the network. If more than the Major Alarm Threshold percentage and less than the Critical Alarm Threshold percentage of those samples are in violation of the Performance Degradation Threshold, a Major event (and an alarm if Group Performance Alarms is set to true) is generated. Critical Alarm Threshold: This parameter sets the Critical Threshold Percent. This value is used to determine the severity of threshold violations on a group. For example, a group may have 100 interfaces sampled in the network. If more than the Critical Alarm Threshold percentage of those samples are in violation of the Performance Page 37

38 Degradation Threshold, a Critical event (and an alarm if Group Performance Alarms is set to true) is generated. Participating Devices This list gives the following information for all of the devices that participate in the multicast group. Condition: The status of the participating device model. Possible conditions are initial (blue), normal (green), minor alarm (yellow), major alarm (orange), critical alarm (red), gray (unknown), and maintenance (brown). Name: The name of the participating device model. Network Address: The network address of the participating device model. Manufacturer: The manufacturer of the device that the device model represents. Model Class: The model class of the device model. For more information on a model type s model class, see the SPECTRUM Concepts Guide (0647). MAC Address: The MAC Address of the device model. Type: The model type of the device model. Landscape: The SPECTRUM landscape on which the device modeled. Source(s) This list shows all of the sources for the multicast group. Condition: The status of the Source model. Possible conditions are initial (blue), normal (green), minor alarm (yellow), major alarm (orange), critical alarm (red), gray (unknown), and maintenance (brown). Name: The name of the Source model. This may be the actual name, or the IP address of the source. Type: The model type of the Source model. Model Class: The model class of the Source model. For more information on a model type s model class, see the SPECTRUM Concepts Guide (0647). Landscape: The SPECTRUM landscape on which the Source is modeled. Page 38

39 Rendezvous Point Router This list shows the following information about the rendezvous point router for the multicast group. Condition: The status of the device model that represents the rendezvous point router. Possible conditions are blue (initial), green (normal), yellow (minor alarm), orange (major alarm), red (contact lost), gray (unknown), and brown (maintenance). Name: The model name of the model that represents the rendezvous point router. Network Address: The network address of the rendezvous point router. Manufacturer: The manufacturer of the rendezvous point router. Model Class: The model class of the model that represents the rendezvous point router. MAC Address: The MAC address of the rendezvous point router. Type: The model type of the model that represents the rendezvous point router. Landscape: The SPECTRUM landscape on which the rendezvous point router is modeled. Interfaces Tab This view shows the following information about all of the interfaces related to a group. Name: The model name of the interface model. Condition: The status of the interface model. Possible conditions are blue (initial), green (normal), yellow (minor alarm), orange (major alarm), red (contact lost), gray (unknown), and brown (maintenance). Status: The contact status of the link between this interface and the interface it is connected to. PIM Status: The configured mode of this PIM interface. A value of sparsedense is only valid for PIMv1. Mode: The PIM mode of the interface. This value can be sparse, dense or sparsedense. IGMP Version: The version of IGMP that is running on this interface. This object can be used to configure a router capable of running either Page 39

40 value. For IGMP to function correctly, all routers on a LAN must be configured to run the same version of IGMP on that LAN. Performance Tab Note: If an interface does not participate in a particular protocol, the column(s) pertaining to that protocol for that interface will not contain any data. The information provided in this tab is useful for monitoring multicast performance and faults within the multicast environment. It provides a real-time graphical view of source traffic. The graph in Figure 9 shows multicast source traffic over a period of time for the Group model chosen in the Contents panel. Up to three sources may be graphed in this view. In order for this graph to function properly the following must be true: The source must be modeled by SPECTRUM. SPECTRUM must be able to communicate with the source. The default gateway for the source must be modeled in SPECTRUM. SPECTRUM must be able to communicate with the default gateway for the source. The default gateway must support one of the IPM Route MIBs (draft or RFC). To set the configuration parameters that control how this view is displayed and the alarms that are triggered based on performances (see Multicast Manager Configuration [Page 23]). Page 40

41 Figure 9: Performance Events Tab This tab displays event information for events that occur on the Group model. Source Information The results of Source Searches [Page 31] are displayed in the Contents panel. The following information is presented about each source: Name: The name of the source. This may be the actual name, or the IP address of the source. Condition: The status of the Source model. Possible conditions are blue (initial), green (normal), yellow (minor alarm), orange (major alarm), red (contact lost), gray (unknown), and brown (maintenance). Type: The model type of the Source model. Source Address: The IP address of the source. Page 41

42 Model Class: The model class of the Source model. For more information on a model type s model class, see the SPECTRUM Concepts Guide (0647). This list of sources can be further defined using the Filter button. See Filtering on Search Results [Page 32] for further instructions. Figure 10: Source Information in the Contents Panel Page 42

43 Component Detail for Sources The Component Detail panel (Figure 9) contains tabs that let you view additional information for the Source model selected in the Contents panel. Figure 11: Component Detail Panel for Source Models Information Tab The information tab provides the following selections for the Source model chosen in the Contents panel: Model Information The following information is shown for the Source model. Condition: The status of the Source model. Possible conditions are blue (initial), green (normal), yellow (minor alarm), orange (major alarm), red (contact lost), gray (unknown), and brown (maintenance). Source Address: The IP address of the source. Page 43

44 Model Class: The model class of the Source model. For more information on a model type s model class, see the SPECTRUM Concepts Guide (0647). Creation Time: This shows the creation date and time of the Source model. Landscape: The SPECTRUM landscape to which the Source model belongs. Notes: This field allow you to add new or view existing notes that have been entered about this Source model. To add a note, click Set. Type the appropriate information. When you have finished typing the note, click Save. If you do not want to save the note that you entered, click Cancel. Source Device This following information is shown about the source device for the multicast Source model. Condition: The status of the device model that represents the source. Possible conditions are initial (blue), normal (green), minor alarm (yellow), major alarm (orange), critical alarm (red), gray (unknown), and maintenance (brown). Name: The model name of the model that represents the source. Network Address: The network address of the source device. Manufacturer: The manufacturer of the source device. Model Class: The model class of the model that represents the source. For more information on a model type s model class, see the SPECTRUM Concepts Guide (0647). MAC Address: The MAC address of the source device. Type: The model type of the model that represents the source device. Landscape: The SPECTRUM landscape on which the source device is modeled. Group List This section shows information on the Group model that the Source model sends information to. Condition: The status of the device model that represents the source. Possible conditions are initial (blue), normal (green), minor alarm Page 44

45 (yellow), major alarm (orange), critical alarm (red), gray (unknown), and maintenance (brown). Name: The model name of the model that represents the group. Group Priority: The Group Priority value defines the relative importance of the group and can be used by the network operator to prioritize troubleshooting resources when there are problems with multiple groups. The smaller the number the higher the level of priority. Administrators can set this value in the Group model s Information Tab [Page 35]. Mode: The multicast mode of the group. The value can be either sparse or dense. Type: The model type of the model that represents the group. Model Class: The model class of the model that represents the group. For more information on a model type s model class, see the SPECTRUM Concepts Guide (0647). Events Tab The Event tab displays event information for events that have occurred on the device model that represents the source. Page 45