HP Intelligent Management Center Licenses - Manual (Page 136)

When MVM monitors traffic for an MCE-CE link, it actually monitors the VPN traffic on the
sub-interfaces bound to PE-MCE. As a result, the data is different from the actual traffic.
8.36 Why does the system prompt Telenet failure when I import a device?
The Telnet parameters on the iMC platform are inconsistent with those configured on the
device. To resolve this, view and modify the Telnet parameters for the device on the Device
Details page in the iMC platform.
8.37 Why does the system prompt synchronization failure when I synchronize a device on the
Device Management page or in the MPLS topology?
Possible reasons for the synchronization failure include device unreachability, inconsistency
of Telnet parameters on the iMC platform and those on the device, and device model not
supported by the MPLS management. To resolve this, check the following:
•
Check and modify the network configuration if needed to make sure the device and
iMC can reach other.
•
View and modify Telnet parameters on the device details page of the iMC platform.
•
See the Release Notes to check whether MPLS management supports the device model.
8.38 I want to add a dynamic RSVP-TE tunnel. If I just configure part of the configuration
parameters, what will happen?
In the tunnel adding process, the system will use the default settings for the configuration
parameters that you do not configure.
8.39 How will affinity and affinity mask configurations of a dynamic RSVP-TE tunnel affect the
displaying of topology information?
The topology function module displays only topology information that matches the specified
affinity and affinity mask when you select to filter topology by affinity.
8.40 In the process of adding or modifying dynamic RSVP-TE tunnels, the configuration items on
the advanced attributes configuration page are not always the same, why?
Some commands for configuring an MPLS TE tunnel are mutually exclusive. For such
commands, the system provides the hiding function. If you select one command, the
commands exclusive with the command will not appear on the interface.
8.41 After I configured FRR protection, the system prompted that the configuration succeeded,
but there's no related record in the iMC database, why?
Because of time delay, the FRR configuration has not taken effect on the device. Therefore,
there is no related record on the device and in the iMC database. You are recommended
to use automatic discovery or perform device synchronization.
8.42 During the traffic forwarding configuration process, why did I fail to configure forwarding
adjacency after I configured IGP shortcut?
IGP shortcut and forwarding adjacency configurations are mutually exclusive.
8.43 In the process of configuring traffic forwarding, IGP shortcut or forwarding adjacency
configuration is successful, but there's no related record in the iMC database, why?
The MPLS TE manager can obtain only the configuration currently used by the device.
However, the device may not be using the traffic forwarding configuration that you made.
Therefore, there is no record of your configuration in the iMC database.
8.44 Configuring multiple protection for the same interface, why TE manager only show one
protection information?
Even multiple protections are configured, only one protection can be active when tunnel
down. Other protection will not take effect. TE manager displays the one which will be
active. Others are not of use.
136 FAQ