Administer the NNM iSPI for IP Multicast

As an administrator, you can perform the following tasks:

• Discover Your IP Multicast Network
• Monitor Multicast Network Health
• Configure the NNM iSPI for IP Multicast
• Configure Multi-site Multicast Connectivity
• Control Access to the NNM iSPI for IP Multicast (Multi-tenancy)
• Configure with Address Translation Protocols
• Enable Single Sign-On with NNMi
• NNM iSPI for IP Multicast System Health Report
• Troubleshoot the NNM iSPI for IP Multicast

You can extend the NNMi capabilities and perform the following tasks for the NNM iSPI for IP Multicast:

Manage and Not Managed Nodes

You can manage and not manage the nodes by performing the specific tasks from the NNMi inventory views. For more information, see Actions provided by NNMi.

The NNM iSPI for IP Multicast discovery process does not discover any unmanaged nodes. However, if the unmanaged node is changed into the managed mode, the scheduled discovery process updates the management mode of the NNM iSPI for IP Multicast nodes.

The NNM iSPI for IP Multicast provides you an option to not manage the multicast nodes that are managed by NNMi. You can also manage or not manage the multicast flows.

Backup and Restore Actions

You can perform the Backup and Restore Actions for the NNM iSPI for IP Multicast from NNMi. The backup and restore command for NNMi does the backup and restore for the NNM iSPI for IP Multicast. This is supported only with the embedded database and the NNM iSPI for IP Multicast and NNMi are located in same management station.

You can check the multicast file in the location provided for backup and with the extension .pgd file.

Example: C:/tmp/nnm-bak-20080924095922-multicastdb.pgd.

For more information about the Back up and Restore operation, see Back Up and Restore NNMi. 

Configuration Poll

Select the node, and click Action -> Polling -> Configuration Poll. For more information, see the NNMi Help, Actions: Configuration Poll command.

Log on to IP Multicast Workspace

After installing NNMi, use the URL to log on to the NNMi console. For more information, see Configure Sign-In Access.

After installing NNMi, the NNM iSPI for IP Multicast installation process prompts you to set up the login and password for the Web Service Client user.

Updating the NNMi System Password

You can configure the NNM iSPI for IP Multicast to use same system password as NNMi. After installing the NNM iSPI for IP Multicast, if the system password for NNMi is modified, the NNM iSPI for IP Multicast should be updated with the new system password.

Run the following command to copy the NNMi password:

encryptmulticastpasswd.ovpl -c <domain>

where:

c - NNMi jboss to iSPI jboss communication

domain - multicast (case insensitive)

After updating the password, restart the NNM iSPI for IP Multicast to use the new system credentials.

Update the iSPI for IP Multicast

The NNM iSPI for IP Multicast should be configured with Web Service Client Username and Password to communicate with NNMi. Add the user in NNMi with the role of Web Service Client user and use the script to update the password.

Avoid system role for NNMi - NNM iSPI for IP Multicast communication. Only user having root permission can run this script.

Use the encryptmulticastpasswd.ovpl command to update the NNM iSPI for IP Multicast password. This script updates the NNM iSPI for IP Multicast password. Avoid using the Web Service Client password of NNMi.

$InstallDir/bin/encryptmulticastpasswd.ovpl -e <domain> <password>

where: -e - encrypt supplied string

domain - multicast (case insensitive)

password - string to be encrypted

After updating the password, restart the NNM iSPI for IP Multicast to use the new credentials.

Discover Your IP Multicast Network

You can monitor the IP Multicast nodes, interfaces, and flows from the IP Multicast inventory after you complete the IP Multicast discovery process.

You can discover the IP Multicast nodes and objects by the following:

• Install NNMi and iSPI for IP Multicast to monitor the network.
• Install the NNM iSPI for IP Multicast on an NNMi management server that is already managing the network.

After you install NNMi and NNM iSPI for IP Multicast, seed the nodes from the NNMi console. The NNMi discovery process starts and discovers the nodes in the network. The NNM iSPI for IP Multicast discovery process starts automatically after the completion of NNMi discovery process. When you add a Multicast node in the topology, NNMi discovery process detects the change in network and sends a notification to the NNM iSPI for IP Multicast discovery process to start. Similarly, when you delete a node, NNMi discovery process detects the interfaces residing on the node and deletes the corresponding dependencies for the deleted node in all the views. By default, the discovery schedule for NNMi and NNM iSPI for IP Multicast is set to 24 hours.

After installing the NNM iSPI for IP Multicast on an NNMi management server, you can wait for the next discovery cycle of NNMi, or you can perform the Configuration Poll to discover the IP Multicast nodes immediately. The NNM iSPI for IP Multicast discovery process does not automatically discover the nodes that are already discovered by NNMi until the next discovery cycle.

Monitor Multicast Network Health

The real-time monitoring of the network helps you to check and detect the faults in the network.

You can monitor the health of your multicast network by using the NNM iSPI for IP Multicast. Before you start monitoring the network, make sure that NNMi jboss and IP Multicast jboss are running. In addition, check all the Multicast-enabled nodes and PIM interfaces appear in the views. You can monitor and manage the network by using services such as State Poller and Causal Engine.

State Poller

The Multicast State Poller gathers information from the discovered multicast nodes and reports the state of the devices in the database. The State Poller starts the periodic polling of the Multicast nodes, interfaces and flows. The default polling interval is 10 minutes. 

You can configure the polling interval as per your requirement from the IP Multicast Configuration workspace.

Causal Engine

The Causal Engine gathers information about status of the multicast nodes, interfaces, flows and PIM neighbors in the Multicast topology. The Causal Engine evaluates network issues, determines the root cause, and sends the incidents to notify you of problems. Thus, Causal Engine helps you monitor the health of your network.  

Configure the NNM iSPI for IP Multicast

With the administrative privileges to NNMi console, you can access the IP Multicast Configuration formFrom the Workspaces navigation pane, click Configuration-> IP Multicast Configuration. The IP Multicast Configuration form opens. and perform the following tasks:

• Configure the polling interval for the multicast nodes and interfaces.
• Filter the multicast reserved groups by using the Group Discovery tab.
• Establish the communication between the NNM iSPI for IP Multicast Global Manager and Regional Managers.
• Configure the flow monitoring settings to create a baseline snapshotThe snapshot of the standard pattern of flow or the ideal flow., compare the subsequent flows against the baseline snapshot, and generate incidents when substantial deviations occur.

The IP Multicast Configuration workspace consists of the following tabs: 

Configuration Type	Description
Polling	Sets the time in minutes between the two consecutive polls for the NNM iSPI for IP Multicast. By default, the State Poller polls periodically every 10 minutes for the state of the multicast nodes, interfaces, and PIM neighbors.
Group Discovery	Filter the multicast reserved groups. If you filter these groups, they do not appear in the inventory.
IP Multicast Regional Manager Connections	Configure the Regional Manager connections from the NNM iSPI for IP Multicast Global Manager (GM). After you configure the Regional Manager connections, you can monitor the nodes, interfaces, and flows of the Regional Manager from the NNM iSPI for IP Multicast Inventory Global Manager (GM). For more information, see NNMi Help, Connecting Multiple NNMi Management Servers (NNMi Advanced).
Flow Monitor	Configure the monitoring parameters for the multicast flows. Use this tab to perform the following functions: Configure the time interval between two monitoring cycles to determine change in flow. Configure the percentage of flow rate deviation allowed for the flows while comparing with the baseline snapshot. If the deviation is more than the prescribed limits, the application generates an incident. Enable or disable the Auto Baselining option. Configure the days of week and time of the day when you want to monitor the flows.

Configure the Polling Interval

After the NNM iSPI for IP Multicast discovers the Multicast nodes and interfaces in the network, the polling of the Multicast nodes and interfaces occur with the default polling interval. You can set the polling interval with the help of the IP Multicast Configuration workspace.

To configure the polling for Multicast nodes and interfaces, follow these steps:

1. Navigate to the IP Multicast Configuration workspace.From the Workspaces navigation pane, click Configuration-> IP Multicast Configuration. The IP Multicast Configuration form opens.
2. Click the Polling tab and specify the following details:

Node Settings

Option	Description
Enable Polling	Set the checkbox to poll the Multicast nodes. If enabled, the NNM iSPI for IP Multicast monitors the status of the Multicast nodes. If you disable polling, the status of the node is No Status.
Interval	Type the interval (in minutes) to poll the Multicast nodes. The default polling interval is 10 minutes.

Interface Settings

Option	Description
Enable Polling	Set the checkbox to poll the Multicast interfaces. If enabled, the NNM iSPI for IP Multicast monitors the status of the Multicast interfaces on node. If you disable polling, the status of the interface is No Status.
Interval	Type the interval (in minutes) to poll the Multicast interfaces. The default polling interval is 10 minutes.

Performance Settings

Option	Description
Enable Polling	Set the checkbox to poll and collect the performance data for the Multicast nodes, interfaces, and flows. If enabled, the NNM iSPI for IP Multicast collects the data and sends to the NNM iSPI Performance for Metrics. The Performance data appears on the map views only if the NNM iSPI Performance for Metrics is installed and running.
Interval	Type the interval (in minutes) to poll and collect the performance data. The default polling interval is 10 minutes

3. Click (the Save icon).

Configure the Group Discovery

The multicast group IP addresses between 224.0.0.0 and 224.0.0.255 are reserved for the use of routing protocols, protocols involved in low-level topology discovery, and maintenance protocols. You can filter these multicast reserved groups .If you filter these groups, they do not appear in the inventory. All multicast reserved groups are filtered by default.

To disable the filtering of Multicast Reserve Groups:

1. Navigate to the IP Multicast Configuration.From the Workspaces navigation pane, click Configuration-> IP Multicast Configuration. The IP Multicast Configuration form opens.
2. Click the Group Discovery tab.
3. Disable the Filter Reserved Groups checkbox. If disabled, the NNM iSPI for IP Multicast does not filter the multicast reserved groups and these groups appear in the inventory.
4. Click (the Save icon).

Connect to the NNM iSPI for IP Multicast Regional Manager

The NNM iSPI for IP Multicast provides you IP Multicast Configuration workspace to connect the NNM iSPI for IP Multicast Regional Managers to the NNM iSPI for IP Multicast Global Manager. As an administrator, you configure the settings to establish communication between the NNM iSPI for IP Multicast Global Manager and Regional Managers.

For more information about NNMi Global Manager and Regional Manager connections, see NNMi Help, Connecting Multiple NNMi Management Servers.

To establish the NNM iSPI for IP Multicast Regional Managers connection, follow the steps:

1. Navigate to the Regional Manager form.
   

   1. From the workspace navigation panel, select the IP Multicast Configuration workspace.
   2. Select the IP Multicast Regional Manager Connections tab

2. Perform the following task as per your requirement:
• To create a new configuration, click the New icon.
• To edit a configuration, select a row, click the Open icon.
• DO NOT delete a configuration (the  Delete icon). For more information, see NNMi Help, Disconnect Communication with a Regional Manager.
3. Select the Regional Manager form, type the basic configuration settings.
4. From the Connections tab, navigate to the Regional Manager Connection form.
5. Click Save to return to the Regional Manager form.
6. Click Save. The NNM iSPI for IP Multicast Global Network Manager establishes communication with the specified Regional Manager.

 Basic Settings

Attribute	Description
Name	Type a meaningful name of the Regional Manager connection. This name appears in the IP Multicast Node inventory. The NNM iSPI for IP Multicast Regional Manager name should be same as the NNMi Regional Manager name.
Description	Provide any description that would be useful for communication purposes within your team.

Configure the NNM iSPI for IP Multicast Regional Manager

The NNM iSPI for IP Multicast provides you IP Multicast Configuration workspace to connect the NNM iSPI for IP Multicast Regional Managers to the NNM iSPI for IP Multicast Global Manager. As an administrator, configure the NNM iSPI for IP Multicast Global Manager to communicate with other Regional Managers across the globe.

Before you configure the iSPI Regional Manager connection, make sure that NNMi Regional Manager is already configured. The name of the NNM iSPI for IP Multicast Regional Manager should be same as NNMi Regional Manager to establish the connection.

To configure the NNM iSPI for IP Multicast Regional Manager connection, follow these steps:

1. Navigate to the Regional Manager Connection form.
   
   1. From the workspace navigation panel, select the IP Multicast Configuration workspace.
   2. Select the IP Multicast Regional Manager Connection tab.
2. Type the connection configuration settings for the NNM iSPI for IP Multicast Regional Manager connection. See connection configuration settings. If the Regional Manager is configured for high-availability, enter configuration settings for each server in the high-availability group (application fail-over).

3. Click (the Save icon) to return to the Regional Manager form.

4. Click (the Save icon) to return to the IP Multicast Configuration form. The NNM iSPI for IP Multicast establishes communication with the Regional NNM iSPI for IP Multicast management server. The Regional Manager forwards information about discovery and monitoring results.

To verify that the NNMi Regional Manager connection is working, see NNMi Help, Determine the State of the Connection to a Regional Manager.

Connection Configuration Settings for a Regional Manager of the NNM iSPI for IP Multicast

Attribute	Description
Hostname	The fully-qualified hostname of the Regional NNM iSPI for IP Multicast management server. The NNM iSPI for IP Multicast uses this hostname for communication with the Regional NNM iSPI for IP Multicast management server and to construct URL Actions. See NNMi Help, Authentication Requirements for launch URLs Access.  If you want NNMi to use secure sockets layer encryption (HTTPS) to access this Regional NNM iSPI for IP Multicast management server, the value is case-sensitive and must match the hostname as specified in that server's SSL Certificate.
Use Encryption	If disabled (), the NNM iSPI for IP Multicast uses hypertext transfer protocol (HTTP) and plain sockets to access the NNM iSPI for IP Multicast Regional management server. If enabled (), the NNM iSPI for IP Multicast uses secure sockets layer encryption (HTTPS/SSL) to access the NNM iSPI for IP Multicast Regional management server.
HTTP(S) Port	Default value for HTTP port for the NNM iSPI for IP Multicast is 8084. Default value for HTTPS port for the NNM iSPI for IP Multicast is 14443. If Use Encryption is disabled (previous attribute), type the port number for HTTP access to the NNM iSPI for IP Multicast console on the Regional management server. If Use Encryption is enabled (previous attribute), type the port number for HTTPS access to the NNM iSPI for IP Multicast console on the Regional management server. For IP Multicast ports, check the port numbers from the server.properties file. Open the server.properties file from the %NnmDataDir%\nmsas\multicast or $NnmDataDir/nmsas/multicast directory on the management server, and then note down the NNM iSPI for IP Multicast HTTP and HTTPS values if you are not using the default values.
User Name	Type the user name required for the NNM iSPI for IP Multicast sign-in for the system account on the NNM iSPI for IP Multicast Regional management server.
User Password	Type the password for the NNM iSPI for IP Multicastsystem account on the NNM iSPI for IP Multicast Regional management server.
Ordering	A numeric value. The NNM iSPI for IP Multicast checks for configuration settings in the order you define (lowest number first). The NNM iSPI for IP Multicast uses the first match found for each address. Provide a unique connection ordering number for each Regional Manager configuration.

Configure Flow Monitoring Settings

Based on the requirement, the NNM iSPI for IP Multicast provides you the flexibility to configure the flow monitoring by providing tunable parameters.

You can configure the flow monitoring at two levels:

• Global Settings:

Global settings act as the default flow monitoring settings for all the flows which are currently monitored and may be added for monitoring at a later stage. You can configure or modify the global settings using the Flow Monitor tab in the IP Multicast Configuration form. See Global Flow Monitoring Settings below.

• Flow Specific Settings:

Flow specific settings allow you to have distinct flow monitoring settings for each flow. You can configure or modify the flow specific settings by performing the action Customize Monitoring Settings from IP Multicast view. See Flow Specific Monitoring Settings.

Global Flow Monitoring Settings

You can use the Flow Monitor tab in the configuration form (Configuration -> iSPI for IP Multicast Configuration -> Flow Monitor) to configure the flow monitoring parameters. Use this tab to change the default flow monitoring parameters. The changes you make to the default parameters are applied to all flows that do not have any specific monitoring settings.

The Flow Monitor tab in the configuration form of the NNM iSPI for IP Multicast enables you to perform the following specific tasks:

• Configure the interval between the start times of two consecutive flow monitoring cyclesFlow monitoring cycle refers to an interval of time during which the process of start router population (if it is not already done), baseline snapshot creation (if it is not there), last sample snapshot calculation, comparison of these snapshots, and incident generation (for any issues identified) take place..
• Configure the percentage of flow rate deviation allowed for the flows while comparing with the baseline snapshot. If the deviation is more than the prescribed limits, the NNM iSPI for IP Multicast generates an incident.
• Enable or disable the Auto Baselining option.
• Configure the days of week and time of the day when you want to monitor the flows.

To configure global flow monitoring settings, follow these steps:

1. From the Workspaces navigation pane, click Configuration -> IP Multicast Configuration. The IP Multicast Configuration form opens.
2. Click the Flow Monitor tab and specify the following details:

Flow Monitor Settings

Option	Description
Auto Baselining	Select the Auto Baselining check box to enable the NNM iSPI for IP Multicast to create the baseline snapshot automatically when a flow is marked for monitoring. By default, the snapshot collected in the first monitoring cycle is taken as the baseline snapshot, but you can change the baseline snapshot at any time to the last monitored flow. If you clear the Auto Baselining check box, the baseline snapshot is not created by the NNM iSPI for IP Multicast. In that case, you have to create the baseline snapshot by performing the Overwrite Snapshot action.
Monitoring Days	Select the days of a week for which you want to monitor the flows. All days are selected by default. For example, if you want to monitor the flows only on Mondays and Tuesdays, clear the check boxes of all days except Monday and Tuesday. You have to select at least one day for monitoring.
Monitoring Time	Type the start time and end time of monitoring time in the 24 hour clock format of hh:mm. The default start time and end time are 00.00 hours and 24.00 hours respectively. The flows are monitored only during the period between the start time and the end time. The start time and end time must be based on NNMi management server's time. The actual start time and end time may slightly vary depending upon the monitoring interval. The NNM iSPI for IP Multicast starts calculating monitoring time from the time when the flow gets scheduled for monitoring. For example, if you configure monitoring settings at 06.20 hours with the following parameters: Start time at 07.00 hours Monitoring interval is 15 minutes In this case, the NNM iSPI for IP Multicast tries to monitor the flows at 06.35, 06.50, 07.05, 07.20, and so on, based on the monitoring interval, which is 15 minutes. You have specified the start time for monitoring as 7.00 hours, hence the actual monitoring starts at 7.05 hours, the first monitoring cycle after 7.00 hours.
Monitoring Interval	Type the interval (in minutes) between the start times of two consecutive flow monitoring cycles. The default flow monitoring interval is 15 minutes. The value should be between 5 minutes and 60 minutes.
Rate Deviation	Type the percentage of deviation in the flow rate allowed from the baseline snapshot. Flow rate refers to the amount of multicast data passing per second through a PIM interface for a particular multicast flow. The default rate deviation is 20 percentage. When the deviation takes place more than the value specified here, the NNM iSPI for IP Multicast generates an incident. The flow rate data is available only if the NNM iSPI Performance for Metrics is installed and running.

3. Click (the Save icon).

Flow Specific Monitoring Settings

You can have flow specific monitoring settings for monitored flows. Use the action Customize Monitoring Settings from the IP Multicast view to customize the flow monitoring settings of each monitored flow. If you apply the flow specific monitoring settings to a flow, these settings override the global flow monitoring settings for the flow.

Flow specific monitoring settings enable you to change the starting router manually. When you change the starting router, the baseline snapshot of the flow changes and the NNM iSPI for IP Multicast closes all incidents associated with the previous baseline snapshot automatically.

Use the Customize Monitoring Settings action to:

• Change the starting router of the flow.
• Configure monitoring interval for the flow
• Configure rate deviation thresholds for each flow.

• Specify the flow to be monitored only on specific days for specific intervals. For example, you can monitor a flow only from Mondays to Fridays from 9.00 hours to 17.00 hours. You can configure flow specific monitoring settings only for the monitored flows.

To enable flow specific monitoring settings: 

1. From the Workspaces navigation pane, click IP Multicast -> IP Multicast Flows. The IP Multicast flow view appears.
2. In the IP Multicast Flow view, select a monitored flow whose monitoring settings you want to change and click Actions -> IP Multicast -> Customize Monitoring Settings. Flow Specific Monitoring Settings form opens.
3. Change the Starting Router if needed. Delete the IP address of the starting router and type the IP address of the new starting router. Alternatively, you can type the hostname of the starting router as well, but the flow specific monitoring settings form displays only the IP address of the starting router.

   You may not see the IP address of the starting router, if the flow has not completed a monitoring cycle. In that situation, type the IP address of the starting router or wait until a monitoring cycle is completed.

4. Change the monitoring settings for the flow.
5. Click (the Save icon).

When you disable monitoring of a flow with specific monitoring settings, the specific settings are lost. If you enable monitoring of the same flow again, the flow takes the global flow monitoring settings, not the previous specific settings.

Configure Multi-site Multicast Connectivity

The NNM iSPI for IP Multicast can display the connectivity between nodes and interfaces that are distributed over multiple WANs, sites, or geographical locations. To enable the NNM iSPI for IP Multicast to do this, you must configure the PIM interfaces on WANs that connect to each other. After this configuration, you can monitor the multicast connectivity across different WANs. The NNM iSPI for IP Multicast displays the nodes and interfaces spread across multiple WANs, sites, or geographical locations in the neighbor view, forwarding tree, and reverse path. In all these views, a cloud represents the connectivity between two interfaces connected across WANs.

To activate this feature in the NNM iSPI for IP Multicast, for each PIM interface you must add the information of the neighbor PIM interface which is connected to this interface across a WAN network. To add this neighbor PIM interface information, you can use the Custom Attributes functionality provided by NNMi.

You must configure custom attributes on all interfaces that are linked across WANs. If you do not configure the custom attributes properly, you cannot get correct neighbor views, forwarding trees, and reverse path views.

You can define the custom attributes only on NNMi objects, so you must configure the custom attributes on PIM interface objects from the NNMi inventory.

You can create custom attributes using any of the following methods:

• Open a particular interface form (see below).
• Use NNMi's nnmloadattributes.ovpl command line tool. For more information, see NNMi Help, Add Custom Attributes to Multiple Nodes or Interfaces.

To configure WAN neighbors to an interface object in NNMi inventory, follow these steps:

1. From the workspace navigation panel, select Inventory and click Interfaces.
2. Click (the Open icon) in the row representing the interface with settings you want to edit.
3. Select the Custom Attributes tab.
4. Click (the New icon) to create a Custom Attribute.
5. Type the name and the value for the new custom attribute in the respective boxes as follows:
   1. Type com.hp.nnm.customattributes.iface.wan.nbrs as the Name. The name remains constant. 
   2. In the Value field, type the name of the neighbor node (on which the neighbor interface is hosted) and the interface index (ifindex) of the neighbor interface separated by a colon. You can type the details of multiple neighbors in this field separated by a semicolon.
      For example, you can type node1:ifIndex1;node2:ifIndex2, when you have to enter the details of two neighbors. Node1 is the name of the node on which the first interface is hosted and ifindex1 is the ifindex of the first interface. Similarly, node2 is the name of the node on which the second interface is hosted and ifindex2 is the ifindex of the second interface.
6. Click (the Save and Close icon) to return to the Interface form.
7. Click (the Save and Close icon) to save your changes. Follow the same steps to configure the custom attributes on the interface, which is on the other side of the WAN.

Addition of custom attribute does not change the existing status of the PIM interface.

For more information, see NNMi Help, Add Custom Attributes to a Node or Interface Object.

Add Multicast WAN Neighbors to Multiple interfaces

You can add multicast WAN neighbors to multiple interfaces using nnmloadattributes.ovpl command line tool. This command line tool also enables you to add custom attributes to multiple interfaces from a comma-separated values (CSV) file. This feature is useful if you have information about PIM interfaces on a large number of WANs that connect to each other. You can define this information in an external data storage and load that information into the NNM iSPI for IP Multicast.

For example, the command line tool nnmloadattributes.ovpl -t interface -s "router1,Fa0/0,com.hp.nnm.customattributes.iface.wan.nbrs,node2:ifIndex2" creates a custom attribute for the interface Fa0/0 hosted on node router1with the following features:

• com.hp.nnm.customattributes.iface.wan.nbrs as the custom attribute name
• node2:ifIndex2 as the value

The NNM iSPI for IP Multicast treats the interface with ifindex2 on node2 as the neighbor of interface Fa0/0 on node router1.

For more information, see NNMi Help, Add Custom Attributes to Multiple Nodes or Interfaces.

After the configuration of the neighbor information on PIM interfaces on WANs that connect to each other, the NNM iSPI for IP Multicast discovers these neighbors in the next discovery cycle. After the completion of the discovery cycle, the NNM iSPI for IP Multicast can display the connectivity between the nodes spread across WANs in the neighbor views, forwarding trees and reverse paths. In all these views, a cloud represents the connectivity between interfaces connected across WANs.

Control Access to the NNM iSPI for IP Multicast (Multi-tenancy)

As an administrator of the NNM iSPI for IP Multicast, you can control the access to multicast inventory, forwarding trees, reverse paths, neighbor views, and incidents. This feature helps to maintain privacy and security of each organization. For example, the operators must see the details of only those multicast nodes to which they have access in the inventory.

As an administrator, you can limit visibility and control to some or all operators. To do so, you must configure user groups, security groups, and optionally, tenants.

• A user group is a set of users or operators who have similar interests, goals, or concerns. Each operator account is associated with one or more user groups.
• Each multicast node is associated with a Security Group. Security Groups enable you to group objects that require the same access level.
• A tenant is the top-level organization to which a multicast node belongs.

An operator can access and control a multicast node only if one of the operator's user groups has access to the node’s security group. Multicast interfaces inherit the access control from the multicast nodes. So, if the operator does not have access to a particular node, the operator cannot access the interfaces on that particular node.

As an administrator you can create, modify, or delete user groups, security groups and tenants. You can also change the security group assigned to a tenant as the default security group. You can configure user groups, security groups, and tenants from the NNMi workspace by clicking Configuration -> Security. Alternatively, you can also use nnmsecurity.ovpl command provided by NNMi to configure the user groups, security groups, and tenants.

For more information about configuring User Groups, Security Groups, and Tenants, see NNMi Help ->Configuring Security.

An operator can see a multicast flow if the operator has access to at least one of the nodes through which the flow passes. In the forwarding tree view, the reverse path view, and the neighbor path view, the NNM iSPI for IP Multicast displays the entire connections if the operator has access to at least a single node involved in these views, but the operator cannot see the details of the nodes that are not accessible to the operator. However, the operators can see the connecting interfaces and the names of the nodes.

In the forwarding tree view, the reverse path view, and the neighbor path view, the NNM iSPI for IP Multicast displays the nodes associated with a single tenant. if your multicast network supports multiple tenants, you may have to launch these views separately for each tenant.

The operators can see the multicast incidents only if they have access to the start router. In the case of flow monitoring, if the operators do not have access to the starting router of a multicast flow, the operators cannot see the incidents related to that particular flow.

Configure with Address Translation Protocols

The NNM iSPI for IP Multicast supports the networks with Network Address Translation (NAT) protocols and Port Address Translation (PAT) protocols. If your network supports NAT or PAT protocols, you must follow the instructions provided in the NNMi Online Help, Address Translation Protocols.

In the forwarding tree view, the reverse path view, and the neighbor path view, the NNM iSPI for IP Multicast always displays the network connectivity within a single tenant. The NNM iSPI for IP Multicast does not support the neighboring relationship across multiple tenants.

You should not have two or more nodes with the same internal (private) IP addresses in a single tenant.

Enable Single Sign-On with NNMi

You can configure Network Node Manager i Software (NNMi) Single Sign-On (SSO) to facilitate access to the NNM iSPI for IP Multicast Configuration workspace from the NNMi console without needing to log on again. SSO is not enabled during installation.

To enable SSO, follow these steps:

• For Windows:

1. Edit the %NnmDataDir%\shared\nnm\conf\props\nms-ui.properties file.
2. Change com.hp.nms.ui.sso.isEnabled= "false" to com.hp.nms.ui.sso.isEnabled = "true”.
3. Run the nnmsso.ovpl -reload script.
4. Run the nmsmulticastssoreload.ovpl script.

• For UNIX:

1. Edit the $NnmDataDir/shared/nnm/conf/props/nms-ui.properties file.
2. Change com.hp.nms.ui.sso.isEnabled="false" to com.hp.nms.ui.sso.isEnabled = "true”.
3. Run the nnmsso.ovpl -reload script.
4. Run the nmsmulticastssoreload.ovpl script.

For more information about SSO, see NNMi Deployment Reference, Using Single Sign-On.

NNM iSPI for IP Multicast System Health Report

You can check the health of the NNM iSPI for IP Multicast by viewing the IP Multicast Health Report.

Launch the IP Multicast Health Report

When you launch the IP Multicast helath report (Select Help-> Help for NNM iSPIs -> iSPI for IP Multicast System Health), the user interface displays the following tabs:

• Memory Details
• CPU Usage Details
• System load Avg
• Swap and other Details
• Database Connection Details
• State Poller Health
• GNM Health

The Memory Details tab contains the following information:

• Name
• Status
• Used(%)
• Max(MB)
• Committed(MB)

The CPU Usage tab contains the following information:

• CPU Usage Details
• Load Average

The System load Avg, Swap and other details tab contains the following information:

• Available Processors
• Free Physical Memory
• Physical Memory
• Committed Virtual Memory
• Free Swap Space
• Total Swap Space

The Database Connection Details tab contains the following information:

• Connections Available
• Total Connections
• Maximum Connections in Use
• Connection created
• Connection Destroyed
• Connections in Use

The State Poller Health tab contains the following information:

• Collections requested in last 5 minutes
• Collections completed in last 5 minutes
• Collections in process
• Time to execute skips in last 5 minutes
• Collector Collection State Count In Last 5 minutes
• Poller result queue length 5 min(avg)

The GNM Health tab contains the details of the Regional Managers configured.

Troubleshoot the NNM iSPI for IP Multicast

The following list helps you troubleshoot and monitor the network by using the IP Multicast inventory:

The NNM iSPI for IP Multicast jboss (mcastjboss) is not working.

• Check that NNMi is running.
• Check the installation log file (HPOvMcastiSPI_08.10, 9.00, 9.10_HPOvInstaller.txt).
• Check system configuration as specified in the IP Multicast Support Matrix.
• Check NNMi port and NNMi JNDI port are the same as specified at the time of NNMi installation in the nnm.extended.properties file and nms-multicast.ports.properties file.
• Check NNMi username and password are same as specified at the time of NNMi installation.

The NNM iSPI for IP Multicast jboss (mcastjboss) is not able to connect to the Oracle database.

Check the Oracle database instance name, username, and password in the nnm-ds.xml and multicast-oracle-ds.xml file.

The NNM iSPI for IP Multicast jboss (mcastjboss) is not running and the log error message is Out of Memory.

Verify the system virtual memory. Increase Xmxparameter for jboss.

The NNM iSPI for IP Multicast is not discovering the Multicast devices.  

• Check that the device is responding to the SNMP queries.
• Check an SNMP configuration for NNMi such as community string and SNMP interval based on your network latency. Run nnmsnmpwalk command to verify that the device responds to SNMP. For further details on how to configure SNMP parameters on NNMi, see NNMi Help.

The multicast-enabled nodes are missing or deleted or unmanaged  

Check if the nodes are deleted or unmanaged by NNMi. In addition, verify that the nodes are not responding to Internet /SNMP queries.

 The IP Multicast Incidents are not appearing on the console.  

• Check the Management Event configuration. For more information, see Help for NNMi.
• Check the SNMP trap service. If the service is stopped, restart the service and NNMi processes.

Remove all the NNM iSPI for IP Multicast devices (only for an embedded database)  

The following command removes all the nodes and configurations from the current installation. Avoid using the command unless required urgently.

Only for Embedded database

• Use OV_BIN/nnmresetembdb.ovpl to clear the NNM iSPI for IP Multicast and NNMi topology.
• Re-seed all the nodes. This action starts the discovery process but takes significant time.

Rediscover a set of multicast nodes

Select the nodes from NNMi inventory and click Actions -> Polling -> Configuration Poll.

In the IP Multicast Flows view, one of the flows managed by you appears as critical, but you cannot see any incidents.

Reason: The starting router belongs to another security group to which you do not have access.

Solution: Request your administrator to give you access to the starting router.

Baseline creation failed.

Reason 1: The starting router has stale multicast group data.

Reason 2: The starting router is not actively participating in the flow.

Solution 1: Troubleshoot the starting router to remove the stale data.

Solution 2: Disable the monitoring and enable monitoring so that a new router is selected as the starting router.