Administer > Help for NNM iSPI for MPLS AdministratorAdminister the NNM iSPI for MPLS

Help for NNM iSPI for MPLS Administrator Administer the NNM iSPI for MPLS

This topics includes the following sections:

As an administrator, you can perform the following tasks by using MPLS Configuration workspace:

  • You can modify the default polling intervals for all the MPLS objects. See, Configure Polling Intervals
  • You can configure devices to support SSHv2 . See, Non-SNMP Framework and Blacklisted Devices
  • You can configure device credentials and enable services such as LSP Service Mapping . See, Configure Device Credentials
  • You can add or delete Route Targets (RTs) participating to form an L3 VPN. See, Configure Exclude Route Targets
  • You can create VPWS VPNs with multiple encapsulations. See, Configure VPWS VPN
  • You can configure Global Managers to communicate with Regional Managers. See, Configure Regional Manager

  • You can perform Backup and Restore Actions:

    You can perform the backup and restore actions for the NNM iSPI for MPLS by using NNMi Backup and Restore commands. For more information, see Back Up and Restore NNMi. Check the MPLS file in the location provided for backup. For example: C:/tmp/nnm-bak-20080924095922-mplsdb.pgd.

  • You can start the Configuration Poll Command:

    Use the Actions -> Configuration Poll to start the Configuration poll for the selected MPLS nodes. For more information, see Launch the Actions: Configuration Poll Command

  • You can log on to the iSPI for MPLS Configuration workspace:

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

    To access the MPLS Configuration workspace, no additional log on and password is required if your user role defines that you can access the NNMi configuration workspace. For more information about the user roles, see Help for NNMi, Determine Account Roles.

  • You can log on to the MPLS Configuration Workspace:

    1. Open the URL with Fully Qualified Name (FQDN), and log on as an admin user. You will be prompted to enter the login ID and password again.
    2. Open the URL with hostname/localhost and Single Sign On (SSO) works when you log on as a non-system admin privileged user. Follow the steps for the Single Sign On to work:
      1. From the User Configuration Interface, click the Enable URL Re-direct checkbox and save the settings.
      2. Log on again, and check the localhost and hostname automatically shows the FQDN in the URL. The MPLS Configuration opens. Do not type the username and password again.

    If you are using system as username to log on, SSO is disabled. You have to type the username and password again to view the MPLS Configuration.

In addition you can :

Discover Your Network

You can monitor the MPLS nodes and objects from the MPLS inventory after you complete the MPLS discovery process.

You can discover the MPLS nodes and objects by the following:

  • Install NNMi and then install the NNM iSPI for MPLS to monitor the network. The nodes are added after installing NNMi and the NNM iSPI for MPLS.
  • Install the NNM iSPI for MPLS on an NNMi management server that is already managing the network.

After you install NNMi and NNM iSPI for MPLS, seed the nodes from the NNMi console. The NNMi discovery process starts and discovers the nodes on the network. After every node is discovered, the NNM iSPI for MPLS discovery process starts automatically after the completion of NNMi discovery process .

When you add an MPLS node in the topology, NNMi discovery process detects the change in network and sends a notification to start the discovery process to the NNM iSPI for MPLS . 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 MPLS is set to 24 hours.

After installing the NNM iSPI for MPLS 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 MPLS nodes immediately.

To start the complete discovery for the NNM iSPI for MPLS, use nmsmplsdisco.ovpl -all. For more information, see MPLS reference pages (Help -> NNMi iSPI Documentation Library -> NNM iSPI for MPLS Reference Pages).

In addition, you can also choose to not discover certain MPLS nodes. By doing so, you can handle the load of your MPLS network and also exclude the nodes that may cause issues during network discovery. To exclude:

  1. Create a node group for MPLS-enabled devices with the name MPLSNoDiscover
  2. Add the devices that you do not want to be discovered to this group.

If you have a node in the MPLSNoDiscover group for regional then that node from the NNM iSPI for MPLS GNM will be removed automatically .

Also, to exclude nodes from the NNM iSPI for MPLS GNM, you must create a MPLSNoDiscover node group on the NNM iSPI for MPLS GNM for regional nodes.

For more information, see Create Node Groups in  NNMi Online Help for Administrators.

Configure the NNM iSPI for MPLS

With administrative privileges to NNMi console, you can use the MPLS Configuration workspace to perform the following tasks:

  • Configure Polling Intervals
  • Configure Device Authentication
  • Configure Route Targets
  • Configure VPWS VPN
  • Configure Regional Manager

The MPLS Configuration workspace consists of the following tabs:

Configuration Tab Description
Polling Frequencies Used to set the time in minutes or seconds between the two consecutive polls for the MPLS object. By default, the State Poller polls the MPLS nodes periodically for every five minutes for the status of the MPLS objects such as TE Tunnels.

Device Authentication

Used to add device credentials for non-SNMP framework
Exclude Route Targets Used to add, delete or edit the list of Route Targets (RTs) to be ignored for the discovery process.
VPWS VPN Configuration Used to add, delete or edit the PseudoWire VC attributes to form a VPWS VPN.
MPLS Regional Manager Connections Used to configure the Regional manager. This Regional manager configuration helps you to monitor the Regional manager inventory. After configuration, you can start communication between Global Network Manager and Regional Manager.

Configure the Polling Frequency

The MPLS State Poller service checks each discovered, managed, and monitored MPLS node, interface, VRFs, LSPs, TE tunnel, LDPs, VFIs, SDPs, and VC LSP that is monitored in the management station.

The MPLS State Poller gathers information about nodes, interfaces, and MPLS objects from the discovered devices and reports the results of the state of the devices in the database. The State Poller is configured to do periodic polling of devices. The State Poller identifies the topology changes and polls newly discovered devices and MPLS objects such as SDPs, VFIs, LDP peers, TE tunnels, VRFs, and VC LSPs. You can view the updated status information for the following MPLS objects:

  • L3 VPN status
  • MVPN status
  • VRF status
  • TE Tunnel status
  • PseudoWire VC status
  • VPWS VPN status
  • VPLS VPN status
  • Monitored LSP status
  • VFI Status
  • SDP Status

After the NNM iSPI for MPLS discovers the available MPLS nodes and interfaces on the network, you can modify the default polling interval by using the Polling Frequencies tab to keep your topology up-to-date.

To configure the polling frequencies for the MPLS objects, follow these steps:

  1. Navigate to the MPLS Configuration form.
    1. From the workspace navigation panel, select the iSPI for MPLS Configuration workspace.
    2. Select the Poller Frequencies tab.
  2. In the Poller Frequencies tab, specify the following details:
    • TE Tunnel Polling Frequency: Sets the time in minutes, seconds between the two consecutive polls for TE tunnel. By default, the State Poller polls periodically every 5 minutes for the status of TE tunnels.
    • VRF Polling Frequency: Sets the time in minutes, seconds between the two consecutive polls for VRF. By default, the State Poller polls periodically every 5 minutes for the status of VRFs.
    • PseudoWire VC Polling Frequency: Sets the interval (in minutes) between the two consecutive polls for PseudoWire VC. The default value is 5 minutes.
    • LSP Polling Frequency: Sets the interval (in minutes) between the two consecutive polls for LSPs. The default value is 5 minutes.
    • VFI Polling Frequency: Sets the time in minutes, seconds between the two consecutive polls for VFI. By default, the State Poller polls periodically every 5 minutes for the status of VFIs.
    • SDP Polling Frequency: The SDP polling frequency sets the time in minutes, seconds between the two consecutive polls for SDP. By default, the State Poller polls periodically every 5 minutes for the status of SDPs.
    • VRF Performance Polling: Sets the interval (in minutes) between the two consecutive polls for the selected VRF. The default value is 15 minutes. To enable Performance polling, check Enable Polling
    • LSR Performance Polling: Sets the interval (in minutes) between the two consecutive polls for the selected LSR node. The default value is 15 minutes. To enable Performance polling, check Enable Polling
    • TE Tunnel Performance Polling: Sets the interval (in minutes) between the two consecutive polls for the selected TE Tunnel. The default value is 15 minutes. To enable Performance polling, check Enable Polling
    • VFI Performance Polling: Sets the interval (in minutes) between the two consecutive polls for the selected VFI. The default value is 15 minutes. To enable Performance polling, check Enable Polling
    • PseudoWire Performance Polling: Sets the interval (in minutes) between the two consecutive polls for the selected PseudoWire. The default value is 15 minutes. To enable Performance polling, check Enable Polling
    • LSP Performance Polling: Sets the interval (in minutes) between the two consecutive polls for the selected LSP. The default value is 15 minutes. To enable Performance polling, check Enable Polling
  3. Click (the Save icon).

The default value of the State Poller is five minutes.

On-Demand Status Poll

The status poll command starts a real-time check of the state of the selected device. If the state is changed since the last monitoring cycle then the NNM iSPI for MPLS calculates an updated status reading for the selected device.

You can start the status poll for all the MPLS-enabled objects. You can start the polling for any node from NNMi views. The status poll starts the poll for NNMi nodes. This poll display does not contain the NNM iSPI for MPLS information explicitly but starts the discovery process for the MPLS-enabled nodes.

To start the status poll, see Help for NNMi console, Verify Current Status of a Device.

Configure the Exclude Route Targets

The Route Targets (RTs) that are responsible for the communication between two different VPNs are then identified and configured to exclude from the discovery of VPN. You can exclude RTs to terminate the communication between two or more VPNs. Whenever you update the list of RTs, the NNM iSPI for MPLS discovers and re-computes the L3 VPNs.

To configure the route targets:

  1. Navigate to the MPLS Configuration form.
    1. From the workspace navigation panel, select the MPLS Configuration workspace.
    2. Select the Exclude Route Targets tab.
  2. In the Exclude Route Targets tab, specify a list of Route Targets to be excluded, click Add. To update the database with the list of RTs to be ignored in the discovery process, click Save. The add or save action starts the L3 VPN topology recalculation.
  3. To delete a Route Target, click Remove. The remove action specifies the list of RTs to be ignored in the discovery process.
  4. Click Select All to select all the RTs to perform actions, such as remove or add.
  5. Click (the Save icon).

You can use wildcard characters in the NNM iSPI for MPLS. A wildcard character such as an asterisk (*) is used to exclude all the RTs.

For example, if you want to use a wildcard to exclude all the RTs from the RT list, you can specify an asterisk (*) in the Exclude Route Targets tab. Moreover, if you want to include few RTs from the RT list, you can use the include RT feature. The include RT feature can be helpful if you want to exclude all RTs except few.

Choose * Exclude to exclude all the RTs and then include the RTs you want to discover.

For example:

You have an RT list ranging from 100:1 - 100:98000. If you only want to include the following RTs:

  • 100:2
  • 100:49000
  • 100:88000
  • 100:90000
  • 100:98000

First perform a * Exclude that will exclude all the RTs and then, you can include the above RTs as:

  • 100:2INCLUDE
  • 100:49000INCLUDE
  • 100:88000INCLUDE
  • 100:90000INCLUDE
  • 100:98000INCLUDE
The NNM iSPI for MPLS does not support wildcards for the RT INCLUDE filter.

The NNM iSPI for MPLS then discovers and re-computes the L3 VPN. It will exclude the following list of RTs:

  • 100:1
  • 100:3, 100:4, 100:5, ..........., 100:48998, 100:48999
  • 100:49001, 100:49002, ..........., 100:87998, 100:87999
  • 100:88001, 100:88002, ..........., 100:89998, 100:89999
  • 100:90001, 100:90002, ..........., 100:97998, 100:97999

Configure the VPWS VPNs

To monitor a VPWS VPN, configure the PseudoWires VC attributes in the VPWS VPN Configuration tab. The VPWS VPNs appear in the inventory view only after you complete the configuration steps.

The Enable VC_ID based VPWS VPNs option enables the discovered PseudoWire VCs to be grouped with VC_Id to form a VPWS VPN. If the option is true, all the VPWS VPNs appear as VPWS_VCId. By default, the option is always false. To form a VPWS VPN with a unique name as provided by you, check if the option is disabled. If the PseudoWire VC does not participate in any of the VPWS VPNs, it appears as Default Group.

To add a new VPWS VPN in the MPLS Inventory:

  1. Navigate to the MPLS Configuration form.
    1. From the workspace navigation panel, select the MPLS Configuration workspace.
    2. Select the VPWS VPN Configuration tab.
  2. In the VPWS VPN Configuration section, click (the New icon) and specify the following details:
    • VPWS VPN Name: Type the name of the VPWS VPN. Do not use special characters in the name. This field is mandatory. This name is unique and the VPWS-VPNs names are used to identify the L2 VPN.
    • Include VC ID: Type the VC IDs of the Pseudo Wires VCs. Click Add. To remove the VC ID from the list, click Remove. To select all the VC IDs, click Select All.
    • Node Group Names: Select the name of the nodes forming the group.
    • Encapsulation Type: Select the mode of data transmission from the list box. You can select multiple encapsulation types.
  3. Click (the Save icon). To clear the configuration, click Clear. To close the configuration, click Close.

To edit or delete the configured VPWS VPNs, follow the steps:

  1. Navigate to the MPLS Configuration form.
    1. From the workspace navigation panel, select the MPLS Configuration workspace.
    2. Select the VPWS VPN Configuration tab.
  2. To update or delete a VPWS VPN, select a row, click the edit icon or delete icon.
  3. Click (the Save and Close icon). To clear the configuration, click Clear. To close the configuration, click Close.
    4.  

Non-SNMP Framework and Blacklisted Devices

The NNM iSPI for MPLS uses Simple Network Management Protocol (SNMP) for discovering and monitoring the health of MPLS-enabled nodes. However, for some of the MPLS features, management information is not available through SNMP interface. In such scenarios, the NNM iSPI for MPLS connects to Command Line Interface (CLI) of the supported devices participating in an MPLS network. Using the SSHv2Secure Shell protocol version 2 or Telnet, the NNM iSPI for MPLS gets information required to manage specific MPLS objects or services.

In order to use SSHv2 or Telnet, you have to get vendor specific installation support. For more information, see the vendor specific websites. The following is the list of conditions that should be met for non-SNMP framework support:

  • The device should support SSHv2 or Telnet, and have appropriate credentials in MPLS iSPI configuration to connect to the device. For more information see, Configure Device Credentials

  • Non-SNMP state should NOT be SESSION_FAULT. For more information see, Actions Available below.

  • You can connect through SSHv2 or Telnet only through standard ports. Make sure these ports are not blocked

Though the NNM iSPI for MPLS supports both, SSHv2 and Telnet, it uses SSHv2 protocol as the first preference. NNM iSPI for MPLS uses Telnet if SSHv2 fails.

When SSHv2 is enabled on a device, the vendor specific commands clear the SSHv2 session after it ends. However, on some devices, these sessions may not get cleared due to vendor or operating system specific issues. Number of these sessions, if not cleared, would continue to increase. To avoid accumulation of the SSHv2 sessions the NNM iSPI for MPLS blacklists (SESSION_FAULT) devices that have more than 4 such sessions accumulated for the same server. These devices are excluded from SSHv2 access in subsequent discoveries. Moreover, a device may get blacklisted if no session related data is available

The CLI commands for Cisco device are as follows:

  • show ip cef vrf <vrf_name> detail
  • show mpls l2transport vc detail
  • show mpls l2transport vc
  • show vfi <VFI_NAME>
  • show mpls forwarding-table <Destination prefix>
  • show configuration

For more information on these commands, see vendor specific guides.

The CLI commands for Juniper device are as follows:

  • show route table <route_table_name> detail
  • show bgp neighbor
  • route table bgp.l3vpn.0 next-hop <next_hop_ip_address> detail
  • show route table l2circuit.0 protocol l2circuit active-path detail
  • show route table <VRF_NAME> detail
  • show route table l2circuit.0 protocol l2circuit active-path detail
  • show route <destination> detail active-path
  • show route <destination> detail table inet.3 active-path

For more information on these commands, see vendor specific guides.

Actions Available

  • To get a list of blacklisted or SESSION_FAULT devices,use the command script: /opt/OV/support/nmsmplsDiagnostics.ovpl–printBlacklistedDevices

In case of session faults, you can set time for automatic clearance of the SSHv2 sessions and reset the marking.

  • To reset the blacklisted devices to normal, use:

/opt/OV/support/nmsmplsDiagnostics.ovpl -resetNonSnmpState <Device host name>

You can disable the session checks if you are sure that the SSHv2 session clearing is not required for the devices.

  • To disable session checking, use:

/opt/OV/support/nmsmplsDiagnostics.ovpl -setNonSnmpStateOK <Device host name>

It is recommended that you keep maximum sessions open for SHH2 with minimum 8 sessions at all times to avoid blacklisting of the devices. Maximum sessions open ensure that even after a device is blacklisted, there is session available for an administrator to debug the machine remotely and terminate the sessions.

The above rule is not applicable for Telnet.

Configure Device Credentials

The NNM iSPI for MPLS can connect to Command Line Interface (CLI) the supported devices (for more information on supported devices, see Non-SNMP Framework) participating in an MPLS network, using the SSHv2Secure Shell protocol version 2or Telnet protocol to get information required to manage specific MPLS elements or services. This is required for some features such as LSP Service mapping, when information is not available through SNMP interface.

To use this function, users have to enter authentication information for these devices (device credentials). These credentials are encrypted and stored in the database

To add a new device credential in the MPLS Inventory, follow the steps:

  1. Navigate to the MPLS Configuration form:
    1. From the workspace navigation panel, select the iSPI for MPLS Configuration workspace.
    2. Select the Device Authentication tab.
  2. Click (the New icon) and specify the following details:
    • Management IP address of the device
    • User name and password of the device
  3. Click (the Save icon).

Repeat these steps for each device you want to add.

To Enable Telnet Access:

The NNM iSPI for MPLS uses SSHv2 protocol as the first preference. You can enable or disable Telnet access. When enabled, NNM iSPI for MPLS uses Telnet if SSHv2 fails. To enable Telnet access, select the Enable Telnet Access check box. Similarly, to disable telnet access for the devices, you can clear the Enable Telnet Access check box.

Enabling or disabling Telnet access is applicable for the entire list of configured devices. You can switch between SSHv2 and Telnet for individual devices by switching Device Access Mode.

Wildcard Support for Device Authentication

You can use wildcard characters; an asterisk (*) and hyphen (-) in the NNM iSPI for MPLS. You can add authentication parameters to multiple devices by using wildcard characters in the IP addresses.

Address Range Definition Attribute
Attribute Description
IP Range

To specify a range of IP addresses, use one of the following. Pick one address notation style, combinations of wildcards:

  • ClosedIPv4 address wildcard notation

    An IPv4 Address range is a modified dotted-notation where each octet is one of the following:

    • A specific octet value between 0 and 255
    • A low-high range specification for the octet value (for example, "112-119")
    • An asterisk (*) wildcard character which is equivalent to the range expression "0-255"

    The following two IPv4 addresses are considered invalid:

    0.0.0.0 and 127.0.0.0.

    Examples of valid IPv4 address wildcards include:

    10.1.1.*

    10.*.*.*

    10.1.1.1-99

    10.10.50-55.*

    10.22.*.4

    10.1-9.1-9.1-9

    1.2*-3*.33.4. While (-) is used between octets, you can use (*) to specify a particular range. This example is a valid pattern for IP addresses with second octet ranging from 20-39

  • ClosedIPv6 address wildcard notation

    Separate each 16-bit value of the IPv6 with a colon. The 16-bit value can be any of the following:

    • A specific hexadecimal value between 0 and FFFF (case insensitive)
    • A low-high range specification of the hexadecimal value (for example, 1-1fe)
    • An asterisk (*) wildcard character (equivalent to the range expression 0-ffff)

    The standard IPv6 short-hand notation (::) is allowed to express one or more 16-bit elements of zero (0) values. However, the mixed IPv6/IPv4 dot-notation (for example, 2001:d88::1.2.3.4) is not allowed as an IPv6 address range.

    Valid examples of ranges in modified IPv6 address notation include the following:

    2001:D88:0:A00-AFF:*:*:*:*

    2001:D88:1:*:*:*:*:*

    2001:D88:2:0:a07:ffff:0a01:3200-37ff

Take a note that:

  • The NNM iSPI for MPLS does not support CIDR notations while configuring device authentication.
  • If a configured device matches more than one wildcard pattern, the one that is first encountered will be used to get device credentials. For example, if you enter 1.22-25.33.4 and 1.*.33.4; then for a device with IP 1.23.33.4, credential for 1.22-25.33.4 is used.
  • You have to use a specific IP address and its credentials. For example, if you configure 192.165-170.1.4 and 192.168.1.4, credentials for 192.168.1.4 is used. This way, you can have exception for specific devices in configuring credentials.
  • In addition, if you enter 192.*.1.4 and 192.168.1.4, credentials for 192.168.1.4 is used.

Configure an MPLS Regional Manager Connection

As an administrator, you can configure the NNM iSPI for MPLS Global Manager to communicate with other Regional Managers across the globe by using the MPLS Configuration workspace. For more information about NNMi Global Manager and Regional Manager connections, see NNMi Help, Connecting Multiple NNMi Management Servers.

To enable the NNM iSPI for MPLS Regional Manager connection, follow the steps:

  1. ClosedNavigate to the Regional Manager form.
    1. From the workspace navigation panel, select the MPLS Configuration workspace.
    2. Select the MPLS 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).
    • For more information, see NNMi Help, Disconnect Communication with a Regional Manager.
  3. Select the Regional Manager Configuration form, type the basic configuration settings.
  4. From the Connections tab, navigate to the Regional Manager Connections form.
  5. Select the Regional Manager Configuration form, type the basic configuration settings.
  6. From the Connections tab, navigate to the Regional Manager Connections form.
  7. Click (the Save and Close icon) to close the Regional Manager form.
  8. Click (save and activate). The NNM iSPI for MPLS Global Network Manager establishes communication with the specified Regional Manager.
 BasicSettings
Attributes Description
Name

Type a name for this configuration record about the Regional MPLS management server.

The NNM iSPI for MPLS Regional Manager name should be same as NNMi Regional Manager name.
Description Provide relevant information about your Regional Manager connection. This field is optional.

Configure the NNM iSPI for MPLS Regional Manager Connection

As an administrator, you can configure the NNM iSPI for MPLS Global Manager to communicate with other Regional Managers across the globe by using the MPLS Configuration workspace. You can only configure the Regional Manager connection if the NNM iSPI for MPLS is already up and running.

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

To configure the Regional Manager connection, follow the steps:

  1. ClosedNavigate to the NNM iSPI for MPLS Regional Manager Connection form.
    1. From the workspace navigation panel, select the MPLS Configuration workspace.
    2. Select the Regional Manager Connections tab.
  2. Type the connection configuration settings for the NNM iSPI for MPLS 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 and Close icon) to return to the Regional Manager form.

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

To verify that the 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 MPLS
Attribute Description
Hostname

The fully-qualified hostname of the Regional NNM iSPI for MPLS management server. The NNM iSPI for MPLS uses this hostname for communication with the Regional NNM iSPI for MPLS management server and to construct URL Actions. See NNMi Help, Authentication Requirements for launch URLs . 

Note: If you want NNM iSPI for MPLS to use secure sockets layer encryption (HTTPS) to access this Regional MPLS 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 MPLS uses hypertext transfer protocol (HTTP) and plain sockets to access the NNM iSPI for MPLS Regional management server.

If  enabled, the NNM iSPI for MPLS uses secure sockets layer encryption (HTTPS / SSL) to access the the NNM iSPI for MPLS Regional management server.
HTTP(S) Port

Default value for HTTP is 24040.

Default value for HTTPS 24043.

If  Use Encryption is disabled, enter the port number for HTTP access to the NNMi and MPLS console on the Regional NNMi management server.

If  Use Encryption is enabled (previous attribute), enter the port number for HTTPS access to the NNMi console on the Regional NNMi management server.

For MPLS ports, check the port numbers from the nms-mpls-ports.properties file. Open the nms-mpls-ports.properties file from the %NnmDataDir%\shared\mpls\conf or $NnmDataDir/shared/mpls/conf directory on the management server, and then note down the NNM iSPI for MPLS HTTP and HTTPS values if you are not using the default values.
User Name Type the user name required for the NNM iSPI for MPLS sign-in for the account on the NNM iSPI for MPLS Regional management server. The user name should be same as the name provided while installing the NNM iSPI for MPLS.
User Password

Type the password for the NNM iSPI for MPLS account on the NNM iSPI for MPLS Regional management server.

Note: The NNM iSPI for MPLS encrypts the password and displays asterisks for this attribute. If you want to change the password, first clear the asterisks displayed in the Password attribute and enter the new Password value.
Ordering

A numeric value. The NNM iSPI for MPLS checks for configuration settings in the order you define (lowest number first). The NNM iSPI for MPLS uses the first match found for each address. Provide a unique connection ordering number for each Regional Manager configuration.

Manage Nodes

The NNM iSPI for MPLS discovers the MPLS-enabled nodes and interfaces. The nodes or interfaces that are not managed by NNMi are not discovered by the NNM iSPI for MPLS.

You can manage or stop managing all the MPLS objects such as VPNs, PseudoWires, and so on. However, if a node is not managed, all the MPLS objects on that node such as VRFs, VC LSPs, VFIs, SDPs and SDPBinds are Not Managed .

In addition, The state of a 'Not Managed' MPLS object is set to Not Polled and the status is set to No Status if the corresponding Node is not managed. The state of the MPLS object is set to Not Polled and the status is set to No Status.

If a 'Not Managed' node returns into a managed mode in NNMi inventory, the MPLS discovery process starts and updates the management mode of the MPLS objects. Also, a notification is sent to the State Poller about the updated management mode.

NNM iSPI for MPLS System Health Report

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

Launch the MPLS Health Report

Select Help-> Help for NNM iSPIs -> iSPI for MPLS System Health

The user interface displays six tabs; Memory Details, CPU Usage Details, System load Avg, Swap and other Details, Database Connection Details, State Poller Health and 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.

Use Single Sign-On with NNM iSPI for MPLS

By default Single Sign-On is disabled. To enable the Single Sign-On feature, follow these steps after installing the NNM iSPI for MPLS.

Edit /var/opt/OV/shared/nnm/conf/props/nms-ui.properties:

  • Set com.hp.nms.ui.sso.isEnabled = true
  • Run nnmsso.ovpl –reload
  • Run mplsssoreload.ovpl

For more information, see Using Single Sign-On with NNMi in NNMi 9.20 Deployment Reference.

Integrate the NNM iSPI for MPLS with Route Analytics Management Software (RAMS)

The Route Analytics Management Software (RAMS) integrates with NNMi to provide the routing protocol path for the layer 3 topology. You can use the RAMS features to monitor the L3 VPNs that use the mBGP protocol. In addition, you can use the RAMS capabilities to draw the MPLS path within the PE - PE cloud that helps you to monitor the network over the MPLS cloud.

The NNM iSPI for MPLS 10.00 supports integration only with RAMS 9.21.

To monitor the L3 VPNs in the NNM iSPI for MPLS using RAMS, follow these steps:

  1. The NNM iSPI for MPLS shares and sends the L3 VPN information such as L3 VPN name and RT list to RAMS appliances by using the following script:

    /opt/OV/bin/nmsmplsvpnandrtlist.ovpl

    To use the script, follow these steps:

    1. Click the Application button
    2. Click Accessories
    3. Open Terminal
    4. Type the script and hit Enter

    With an administrative privilege to the NNMi console, send the L3 VPN name and RT list to the RAMS appliance.

  2. After the integration with RAMS, you can monitor and view the SNMP traps from the RAMS appliance. To view the traps from the RAMS appliances navigate to the L3 VPN form and click the RAMS tab. The trap list shows the most recent 100 traps.
  3. To monitor the L3 VPN inventory using RAMS, the L3 VPN names should be same as sent to the RAMS appliance.

If you modify the L3 VPN names, send the names again to the RAMS appliance by using the nmsmplsvpnandrtlist.ovpl.

For more information, see MPLS reference pages.

Integrate the NNM iSPI for MPLS with the iSPI for IP Multicast

The NNM iSPI for MPLS helps you to monitor the Provider Edge (PE) routers discovered in an MVPN topology. The PE routers are configured with the multicast-enabled VRF (MVRF) capabilities and use the multicast services to transmit data. The iSPI for IP Multicast helps you monitor the multicast traffic flows in the core network over the MPLS cloud.

Navigate to the iSPI for IP Multicast to view the multicast tree used by multicast traffic in the core network (cloud between the PE routers). The multicast tree shows the Default and Data MDTs. For more information about MVPN, see Overview of the Multicast VPN (MVPN).

Monitoring the network using the NNM iSPI for MPLS and NNM iSPI for IP Multicast

In the example, the NNM iSPI for MPLS monitors the PE routers (PE1, PE2 and PE3) and the PE-CE link (PE1-CE1, PE2-CE2, and PE3-CE3). The core network consists of the PE1, PE2, and PE3 and provider routers (P1, P2, P3, and P4). The iSPI for IP Multicast monitors the traffic flowing from and into the core routers. View the downstream path and upstream path to find multicast flow on the network.

Integrate the NNM iSPI for MPLS with the NNM iSPI Performance for QA (Quality Assurance)

The NNM iSPI for MPLS helps you to monitor the traffic passing through the VRFs on the network. The iSPI Performance for Quality Assurance measures the network traffic performance by configuring various tests on the VRFs. After installing the iSPI Performance for Quality Assurance, the NNM iSPI for MPLS uses the performance capabilities for the following tasks:

  • Find the delay or packet loss for the traffic passing through the selected VRF.
  • Troubleshoot the connectivity for the selected VRFs on basis of the configured tests.
  • Troubleshoot the PE-PE connectivity.
  • Helps in site management.

You can monitor the tests configured for the selected VRF by using the VRF form. The attributes in the QA probes tab helps you to find out the delay for data packet to reach the destination or the packet loss. For more information, see Help for NNM iSPI Performance for QA.

For more information about the iSPI Performance for QA, see Help for NNM iSPI Performance for QA.

Send Help Center feedback