for the HP-UX, Linux, Solaris,
and Windows® Operating Systems
Release Notes
Software version: 9.21 / June
2013
This document provides an
overview of the HP Network Node Manager
iSPI for MPLS Software (NNM iSPI for MPLS) for the 9.21 release. It
contains important information not included in the manuals or in online
help.
For a list of supported
hardware platforms, operating systems, and
database, see the Support Matrix. You can find both the Support
Matrix and the Release
Notes at the root directory of
the
installation media.
The HP Network Node Manager
iSPI for MPLS Software (NNM iSPI for
MPLS) provides real-time data that enables you to monitor the health of
MPLS Virtual Private Network (L3 VPN), Layer 2 VPNs (L2 VPNs),
Multicast-VPNs (MVPNs), MPLS PseudoWire VC, Traffic Engineering (TE)
tunnels, and Label Switch Paths (LSPs)
After you install (and
configure) the NNM iSPI for MPLS on the NNMi
management station, you can monitor and troubleshoot the problems on
your network by using the MPLS workspace. The NNM iSPI for MPLS
presents additional views to indicate the status of the discovered MPLS
devices and the overall health of the network.
NNM iSPI for MPLS 9.21
The NNM iSPI for MPLS includes
the following features:
RT Include Filter
You can choose to include the Route Targets that you want than specifying the list of Route Targets to be excluded.
This feature can be helpful to exclude all Route Targets except few that you want.
Public Key Infrastructure
You can configure the NNM iSPI for MPLS to map with the Public Key Infrastructure (PKI) authentication..
You can log on to the NNM iSPI for MPLS Configuration Console without having to type in the username and password.
You can also run the command-line utilities without typing -u and -p parameters.
To use the PKI authentication feature in the NNM iSPI for MPLS, you must configure NNMi to use the PKI authentication.
The [-silent] option has been added to run
the nmsmplsmanagementmode.ovpl script silently. For more information, see NNM iSPI for MPLS Reference Pages.
NNM iSPI for MPLS 9.20
The NNM iSPI for MPLS includes
the following features:
User
Interface and Navigation
Service centric Layer 2
VPN maps for VPWS (Virtual Private
Wire Service)
Service centric Layer 2
VPN maps for VPLS (Virtual Private
LAN Service)
Details & status
of PWs (Pseudo Wires) forming VPWS group
and VPLS in the Analysis pane of Layer 2 VPN maps
Service oriented launch
of LSP (Label Switch Path) for L3 VPN
& L2 VPN
Note: 'Service
centric' or
'service
oriented' refers to the
mapping that is done between the
services residing on the node and NOT the node itself.
Non SNMP interface,
where the NNM iSPI for MPLS can connect
to devices using SSH2 protocol
Service oriented LSP
maps with intermediate hops and links
for chosen service
Incidents
and Alerts
LSP Reroute Alerts for
any change in the path of LSP
LSP Down Alerts
correlated with service impact incidents
either L3 or L2 VPN
Reports
- Quick Launch for MPLS report views.
The
following environments are no longer supported by NNM iSPI
for MPLS
Microsoft Windows 2003
Internet Explorer 7
Before you begin the NNM iSPI
for MPLS 9.20 installation, follow
these steps:
Install NNMi 9.20. Make
sure that NNMi is installed and running
on the management server.
Install the latest NNMi
patches, if any.
Start the NNM iSPI for MPLS,
9.20 migration process, as mentioned
in NNM iSPI for MPLS 9.20
Installation Guide.
Note:HP-UX and Linux users;
there are
additional steps that you have to follow for successful migration from
version 9.10 to version 9.20. For more information, see the NNM
iSPI for MPLS 9.20 Installation Guide.
NNM iSPI for MPLS 9.10
The NNM iSPI for MPLS includes
the following features:
Support for Alcatel and
Redback devices
Support for inter-provider
VPN by implementation of back-to-back
VRF
Support for automatic
migration of configuration data from
version 9.00
Support for Multi-Tenancy
Capability to discover IPv6
enabled PEs.
Note:
Cisco devices support IPv6 only in a dual stack
scenario, when it is configured for IPv4 as well.
Capability
to
discover VRF-lite enabled nodes
Capability
to monitor the PE-CE, PE-PE, and CE-CE link
connectivity on the network
Capability
to monitor PE – PE, PE – CE,
and CE – CE reachability in the L3VPN by integrating the NNM
iSPI
for MPLS with iSPI Performance for Quality Assurance (QA)
NNM iSPI for MPLS 9.00
The NNM iSPI for MPLS includes
the following features:
Support for Cisco and
Juniper devices.
Capability to discover and
monitor the MPLS LSR nodes configured
on the network.
Capability to discover and
monitor the L3 VPNs, L2 VPNs, and
Multicast-VPN (MVPN).
Capability to discover and
monitor the TE tunnels configured on
the network.
Capability to discover and
monitor the PseudoWire VCs configured
on the network.
Capability to monitor the
status of the L3VPNs, L2VPNs, MVPNs,
VRFs, TE tunnels, and PseudoWire VCs.
Capability to monitor the
health of the MPLS objects on the
network.
Capability to monitor the
PE-CE link connectivity on the network.
Capability to distribute the
NNM iSPI for MPLS network management
using NNMi's GNM environment.
Capability to monitor and
troubleshoot the L3VPNs and TE Tunnels
by using the map views.
Capability to investigate
the problems of the network by viewing
the MPLS incidents and new service impact incidents.
Capability to monitor and
troubleshoot L3VPNs by integrating the
NNM iSPI for MPLS with Route Analytics Management System (RAMS).
Capability to monitor and
troubleshoot MVPNs by integrating the
NNM iSPI for MPLS with the iSPI for IP Multicast.
Capability to monitor PE
– PE reachability in the L3VPN by
integrating the NNM iSPI for MPLS with iSPI Performance for Quality
Assurance (QA).
Troubleshooting the network
by viewing the MPLS reports. This is
only possible after you install the HP NNMi iSPI Performance for
Metrics and NPS. The NNM iSPI for MPLS introduces the
extension
packs such as
MPLS_LSR_Node, MPLS_LSR_Interface, and L3_VPN_VRF.
NNM iSPI for MPLS 8.xx
The NNM iSPI for MPLS includes
the following features:
Support for Cisco and
Juniper devices
Capability to discover and
monitor MPLS LSR devices configured in
the network
Capability to discover and
monitor L3 VPNs configured in the
provider edge devices of the network
Capability to discover and
monitor TE tunnels configured in the
network
Capability to discover and
monitor PseudoWire VCs configured in
network
Capability to monitor the
status of discovered VPNs, VRFs, TE
tunnels, and PseudoWire VCs in the network
Capability to generate the
incidents for the fault or the changes
in the topology
Display the VPNs, VRFs, TE
tunnels, and PseudoWire VCs details in
the MPLS views
NOTE:
To view files in PDF format (*.pdf), Adobe
Acrobat Reader must be installed on your system. To download Adobe
Acrobat Reader, go to official site of Adobe.
Installation requirements, as
well as instructions for installing
the NNM iSPI for MPLS, are documented in the installation guide
provided in Adobe Acrobat (.pdf) format. The document file is included
on the product's installation media as: MPLS_install_guide_en.pdf.
The NNM iSPI for MPLS 9.21 does not support uninstallation. HP recommends you to take a backup of the NNMi and MPLS 9.20 database before you proceed with the installation.
Note:
You cannot upgrade the NNM iSPI for MPLS 9.0x
to the version 9.20 directly. For more information about upgrading the
NNM iSPI for MPLS 9.00 to the version 9.20. For more information, see MPLS_install_guide_en.pdf
For a list of supported
hardware platforms, operating systems, and
databases, see the NNMi 9.20
Support Matrix.
The ovstart process
stops
responding and fails to start the mplsjboss
process after you install the NNM iSPI for MPLS. You might get the
following error messages when you use the ovstart
-c and the ovstatus -c
commands:
ovstart -c
mplsjboss - FAILED Unable to start
process using start command. ovspmd:
Attempt to start HP OpenView
services is complete.
ovstatus -c
ovspmd: Could not successfully run the
status command for process mplsjboss
mplsjboss - FAILED The LRF-specified status command failed.
Workaround
This problem might occur if there is a conflict in the port numbers.
You can perform the following steps to resolve this problem:
Make sure that you have
installed all the necessary patches
for NNMi. See the NNMi
Installation Guide for more
information.
Verify the mpls.log
file present
in the
mpls log folder for any
entry
specified as ROOT
CAUSE in the deployment
of Java MBeans. If there are any port conflicts, you can edit the
values in the following files:
server.properties
file present in the:
For Unix: /var/opt/OV/nmsas/mpls/
directory
For Windows: %NNMDataDir%\nmsas\mpls
directory
nnm.extended.properties
file
present in the:
For Unix: /var/opt/OV/shared/mpls/conf
directory
For Windows: %NNMDataDir%\shared\mpls\conf
directory
Check the mplsjboss
startup process
by running the nmsmplsstart.ovpl
script
present under the following directory: %NNMInstallDir%\bin.
Verify the spiOvspmd.log
file in
the mpls log folder. This file includes the results of the twiddle
commands that invoke the mplsjboss
process. This file lists the connection exceptions (ConnectionExceptions)
at the beginning of the process and displays the messages at the end of
the file indicating that the process is started.
If the listed steps do not
resolve the problem, you might have
to uninstall and re-install the NNM iSPI for MPLS.
After starting the mplsjboss
process, the process displays its status as RUNNING
even after the process has failed to start. This problem might occur if
the mplsjboss fails to start due to installation issues, port
conflicts, or authentication issues.
Workaround
You can perform the
following steps to resolve this problem:
Check if the mplsjboss
process
is running as follows:
Using the ps
command on
HP-UX, Solaris, or Linux operating systems
Using the Task
Manager on Microsoft Windows operating
systems
Use the nmsmplsstart.ovpl
, nmsmplsstatus.ovpl
, and nmsmplsstop.ovpl
scripts present in the NNM_BIN
directory
to verify the problem
Verify the jbossServer.log
file
present at the following location %NNMDataDir%\log\mpls
for any entry specified as ROOT CAUSE
in
the deployment of Java MBeans. Also, make sure that there are no
port-related exceptions in the log file.
Verify the spiOvspmd.log
file
present in the mpls
log folder for any
authentication problem logged while running the twiddle commands to
start the mplsjboss
process. If you see
any error messages in the log file from the following scripts: nmsmplsstart.ovpl, nmsmplsstop.ovpl,
or nmsmplsstatus.ovpl
for issues related
to authentication or port numbers, you must update the correct user
name and password using the encryptmplspassword.ovpl
script and update the port numbers in the following files:
server.properties
file in the
For Unix: /var/opt/OV/nmsas/mpls/
directory
For Windows: %NNMDataDir%\nmsas\mpls\ directory
nnm.extended.properties
file
in the
For Unix: /var/opt/OV/shared/conf/mpls
For Windows: %NNMDataDir%\shared\conf\mpls
directory.
The mplsjboss
process stops
responding to the OVsPMD commands (ovstart,
ovstop, and ovstatus) when
the system resource usage is high.
The process stops responding to further OVsPMD commands and the process
state changes to FAILED.
Workaround:
This problem might occur due to a failure by the twiddle commands to
invoke the mplsjboss
process due to the
high system resource usage. You can resolve this problem as follows:
Stop the mplsjboss
process
using the nmsmplststop.ovpl
command and
check for the shutdown complete message for the process in the jbossServer.log
file to see if the process is
stopped.
If you are unable to
stop the
mplsjboss
process with the steps listed, you can end the process as follows and
then perform the step to start the process:
End the process from
the Task Manager for Microsoft
Windows operating systems.
Kill the process
using the kill
<process_id>
where <process_id>
is the process ID of the Java instance for the mplsjboss
process.
Run the nmsmplsstart.ovpl
script to start the mplsjboss
process.
Run the ovstatus -c
command
to confirm that the OVsPMD commands now use the current status of the mplsjboss
process
ovstatus
shows two instances of mplsjboss
running. For example,
mplsjboss
-
Running
Initialization complete
mplsjboss
-
Running
Initialization complete
This is an error. However, displaying multiple entries in
ovstatus have no functional impact and can be ignored safely.
Multiple instances of the mplsjboss
process result in the mplsjboss process not working as expected.
Workaround:
This problem might occur when you restart all the processes including
the NNMi processes after you encounter a FAILED
state for the mplsjboss process. The ovstop
command does not stop the underlying Java processes when you execute
this command after encountering a FAILED
state for the mplsjboss
process. The ovstart
command executed, creates another
instance of the mplsjboss
process, thus
resulting in multiple mplsjboss
processes.
This causes port conflicts and the mplsjboss process does not work as
expected. You can resolve this problem as follows:
Stop the mplsjboss
process by
using the nmsmplsstop.ovpl
command and
check for the shutdown complete message for the process in the jbossServer.log
file to see if the process is
stopped.
If you are unable to
stop themplsjboss
process with the steps listed, you can
end the process as follows and then perform the step to start the
process:
End the process from
the Task Manager for Microsoft
Windows operating systems
Kill the process
using the kill
<process_id>
where <process_id>
is the process ID of the Java instance for the mplsjboss
process.
Run the nmsmplsstart.ovpl
script to start the mplsjboss
process.
Run the ovstatus -c
command
to confirm that the OVsPMD commands now use the current status of the mplsjboss
process.
The Data MDT appears as the Default
MDT if you
open the MVPN form for the first time.
Workaround:
Refresh the MVPN form to
view the correct information.
The NNM iSPI for MPLS may
display an error message, “A
problem occurred while loading the data from the NNMi management server
for this component”.
This error occurs if MPLS web service
client is not created before installing the NNM iSPI for MPLS.
Workaround
Take a backup of %NNMDataDir%/shared/mpls/conf/nnm.extended.properties
file.
Create a new web service
client user as follows:
Go to Configuration
-> Security -> User Account
Click New
icon to open the User Account
view
Enter a Username and
password
Select External
Account if applicable
Use the 'click here'
option from the view for more
information on 'External
Account'.
Click Save
and close icon
Assign a user group
Go to Configuration
-> Security -> User Account
Mappings
Click New icon to open
the User Account Mapping view
Select a User
account from the User Account
list
Select NNMi
Web Service Clients from the User
Group list
Click Save
and close icon
Stop the NNMi processes
using ovstop
-c.
In the nnm.extended.properties
file, edit com.hp.ov.nms.spi.mpls.Nnm.username.
Replace the username
with the web service
client username created in step b.
Run /opt/OV/bin/encryptmplspasswd.ovpl
-e mpls. This command will
update the nnm.extended.properties
file with the encrypted password for the web service client.
Start all the processes
using ovstart
-c.
Execute nmsmplsdisco.ovpl –all.
This step will start a fresh MPLS discovery. The iSPI discovery happens
automatically if the web service client is created before the MPLS SPI
installation.
NNM iSPI for MPLS may
display an error if the extension packs are
not installed properly by the performance SPI. There are two scenarios
in which this error occurs:
If NPS is installed over
NNM/MPLS and no tabs related to MPLS
extension packs is displayed on the reports page.
Workaround
Delete the MPLS_LSR_Interface.tar.gz.processed,
MPLS_LSR_Node.tar.gz.processed,
and L3_VPN_VRF.tar.gz.processed
from $NNM_DATA/shared/perfSpi/datafiles/extension/final
This will trigger the perf process to reinstall the extension packs.
NPS is installed over
NNM/MPLS, and MPLS SPI extension pack
tabs are displayed on the reports page, but when you launch of any
particular report from any of these tabs for the first time, a message,
"Unable to verify if data
exists for this package. If this is newly
configured custom collection then try again in a few minutes."
is
displayed.
Workaround
Delete the
MPLS_LSR_Interface.tar.gz.processed, MPLS_LSR_Node.tar.gz.processed,
and L3_VPN_VRF.tar.gz.processed
from $NNM_DATA/shared/perfSpi/datafiles/extension/final.
This
will trigger the perf process to reinstall the extension packs.
During NNM iSPI for MPLS
Global Network Management (GNM)
configuration in a Linux environment, after the 'Successfully
created new connection. Please activate regional manager'
message,
an alert message "Failed to add
connection <connection_name>
for regional manager <regional_manager>."
may be displayed. This alert message is displayed if you add NNM iSPI
for MPLS Regional manager on Linux and use Internet Explorer for
configuration.
Workaround
Ignore the alert message and
close the last two child browser
windows namely, 'Add Regional
Manager connection' and ' Creating
New Regional Manager'. Refresh
the main window, 'Configuration
for NNM iSPI for MPLS'
containing the Configured
Regional
Managers tab to see the
newly configured Regional Manager.
This message will not be displayed if you are using Firefox version
3.6.9.
The NNM iSPI for MPLS
automatically refreshes node status on a
map view. If you open more than one MPLS L3VPN Topology map view on the
console, the node status gets refreshed only for the most-recent map
view. All the other MPLS L3VPN Topology map views that were opened
earlier appear in the disabled state (grey color).
After you change
configuration of attachment circuits discovery
for VPLS PW, rediscovery of the associated nodes still continue to show
old attachment circuits.
Workaround
This problem occurs when you
make changes in the router
configuration but not save. After the configuration is saved, next
discovery cycle will discover the changes.
Limitations
For all the MPLS forms, the StatusTab
does not appear with the ordered time stamps.
Filters options are
available in all the MPLS views and forms.
The filter option is not working for some MPLS-specific tabs such as
VRF Neighbor tab, PseudoWire VC tab, and Monitored LSP tab.
The trap-driven polling and
correlation rules do not work for
Juniper nodes participating to form an L3VPN.
The source object of the
PseudoWire VC traps does not get
resolved in the incident view of the Global Network Manager. The source
object appears as none.
The CE routers without SNMP
access only appears in the NNM iSPI
for MPLS Regional Manager.
Trap and Incident
correlation rules do not work in the NNM iSPI
for MPLS Global Network Manager (GNM).
TE Tunnel Path View and TE
Hops tab occasionally times-out for
some TE Tunnels in the NNM iSPI for MPLS Global Network Manager (GNM).
The NNM iSPI for
MPLS supports only Cisco devices for MPLS_LSR_Node and
MPLS_LSR_Interface reports.
In the MPLS
LSR Node Top N report, an
error
appears when you select a metric (TE
Tunnel Head (distinct
count)).
All the NNM iSPI for MPLS
commands do not work for the following:
Non-root users with the
administrative rights and permissions.
Any user with
administrator role different from Administrator
user.
Occasionally, when you
unmanage or manage multiple MPLS-enabled
nodes, the management mode of the corresponding MPLS objects does not
change.
VPN computation algorithm
may take time to complete in case of
complex topologies with large number of VPNs and VRFs. While
computation, L3 VPN inventory may display a large number of isolated
VRFs. This is just a transient state and can be safely ignored to wait
for the VPN computation algorithm to complete. After completion, the
inventory will display correct number of VPNs with appropriate
topology.
During a discovery poll,
for a managed node, all the associated
VRFs will be discovered irrespective of their Management mode. This
happens because managed or unmanaged state of a VRF does not impact its
discovery. However, any VRF which was Unmanaged shall remain unmanaged
after the discovery process is complete.
A TE Tunnel in 'Down' state
is not supported in the NNM iSPI for
MPLS Topology View.
A TE Tunnel with status as
Critical
will throw an exception if opened in the Topology view.
If NNM iSPI for MPLS is not
integrated with NNM iSPI for IP
Multicast, an 'HTTP status 404' error while opening Multicast Path
view.
Management Mode setting does
not recognize user privileges.
Irrespective of the operator level, an operator 2 can Manage and
Unmanage the underlying objects which do not belong to operator 2. For
example, if the operator unmanages a VPN, participant VRFs that are not
accessible to the user will also get unmanaged.
An additional IP subnet icon
is shown in the Inter-Provider VPN
topology view when multiple CEs are connected to a single PE through
multiple third-party VPN clouds (AS numbers).
NNM iSPI for MPLS does not
support default routes. NNM iSPI for
MPLS will not discover Remote CEs configured with default routes.
Cross launch for QA probes
on double-click from the VRF form is
not supported by NNM iSPI for MPLS.
For Alcatel devices, VPN
grouped on basis of service IDs will not
appear in the L3 VPN Topology View.
After discovering VRFs for
the first time, duplicate entries are
created. These duplicate entries are removed from the next discovery
onwards.
If there are multiple paths
existing between a Provider Edge (PE)
and a Provider router, there is a possibility that the service traffic
may take more than one path to balance the traffic load. However, these
multiple paths are not shown.
"Could
not complete construction of directed graph for
presentation: null" message is
displayed when a VPWS map is
launched if more than 100 pseudowires are loaded on the default VPWS
group.
If an LSP is not monitored
at Regional Manager but monitored at
the Global Manager, the status of the LSP will always be shown as
normal.
Monitoring of LSPs across
Regional Managers is not supported.
LSP path is not computed
completely if cisco IOS-XR device is in
the intermediate hop. This is because a cisco IOS-XR device reports an
IP address in an inverted order. For example, IP address
192.168.255.255 is reports as 255.255.168.192.
Some PE-PE or PE-CE entries
in the QA Probe Category may be shown
as PE-UNKNOWN when the same destination IP address has entries for
multiple nodes belonging to different VRFs. This happens because iSPI
Performance for QA does not support same IP addresses for multiple
nodes.
When you take backup MPLS
database and restore it in a freshly
installed machine, the configured device credentials will not work
without the .keyfile. This file is available at:
For Windows:
%NNMDataDir%\shared\mpls\conf\.keyfile
For Unix:
/var/opt/OV/shared/mpls/conf/.keyfile
You should manually copy this .keyfile to the same location on the
freshly installed machine.
If you update a license
after the expiry, the MPLS workspace
takes substantial time to come up. Restart NNMi in this case.
The LSP map may not be
displayed in case of same IP addresses for
two different nodes.
Status of Pseudowires, are
computed based on cpwVcMIB and
CISCO-IETF-PW-MIB and not based on status of Virtual Circuits.
An LSP down incident is
generated instead of LSP Re-route if the
new path changes a Provider router (P router) to a Penultimate Hop
router (PHP router).
A pseudowire is built up of two virtual circuit (VC)
label-switched paths (LSPs)—each LSP representing a one-way L2
connection. When the NNM iSPI for MPLS is able to discover only one VC
LSP of a pseudowire, the L2VPN type of the pseudowire is shown as
Unknown in the NNMi console irrespective of the L2VPN type of the
underlying discovered VC LSP.
HP Software online support
provides an efficient way to access
interactive technical support tools. As a valued customer, you benefit
by being able to do the following:
Search for knowledge
documents of interest
Submit and track progress on
support cases
Submit enhancement requests
online
Download software patches
Manage a support contract
Look up HP support contacts
Review information about
available services
Enter discussions with other
software customers
Research and register for
software training
NOTE:
Most of the support areas require that you
register as an HP Passport user and sign in. Many also require an
active support contract. To find more information about support access
levels and HP Passport, go to the following URL: support.openview.hp.com/new_access_levels.jsp
The only warranties for HP
products and services are set forth in
the express warranty statements accompanying such products and
services. Nothing herein should be construed as constituting an
additional warranty. HP shall not be liable for technical or editorial
errors or omissions contained herein. The information contained herein
is subject to change without notice.
Restricted Rights
Legend
Confidential computer software.
Valid license from HP required for
possession, use or copying. Consistent with FAR 12.211 and 12.212,
Commercial Computer Software, Computer Software Documentation, and
Technical Data for Commercial Items are licensed to the U.S. Government
under vendor's standard commercial license.
For information about
third-party license agreements, see the
license-agreements directory on the product installation media.
Acrobat® is a trademark
of Adobe Systems Incorporated.
HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in
both 32 and 64-bit
configurations) on all HP 9000 computers are Open Group UNIX 95 branded
products.
Oracle and Java are registered trademarks of Oracle and/or its
affiliates.
Microsoft® and Windows® are U.S. registered trademarks
of
Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Oracle Technology
— Notice of
Restricted Rights
Programs delivered subject to
the DOD FAR Supplement are
‘commercial computer software’ and use,
duplication, and
disclosure of the programs, including documentation, shall be subject
to the licensing restrictions set forth in the applicable Oracle
license agreement. Otherwise, programs delivered subject to the Federal
Acquisition Regulations are ‘restricted computer
software’
and use, duplication, and disclosure of the programs, including
documentation, shall be subject to the restrictions in FAR 52.227-19,
Commercial Computer Software-Restricted Rights (June 1987). Oracle
America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
For the full Oracle license
text, see the license-agreements
directory on the NNMi product DVD.