HP Intelligent Management Center Licenses - Manual (Page 135)

When the networking scheme is Hub-Spoke, it is necessary to configure both hub and spoke
nodes in order to discover valid links.
8.25 If MVM daemon process terminates abnormally, for instance, electricity power off, MVM
may not work properly. What shall we do in this case?
elete all VPN and PEs in MVM. Import PE again and execute auto discovery.
8.26 Why is the audit result of CE-to-CE unconnective when CE-to-CE is connective actually?
MVM executes connectivity audit when it receives related alarms. Because of time delay,
such as device reboot or instantaneous power down and up, BGP is not steady. In this case
audit result may not be correct. If this happens, please audit the VPN manually.
8.27 Why can't MVM discover hierarchy relation in an existing VPN?
MVM cannot discover UPEs in an existing VPN if there are new UPE added into VPN
network. In this case, delete all PEs and execute auto discovery again.
8.28 Why does the auto discover process fail to finish sometimes?
During auto discovery process network connection may disconnected occasionally. In this
case, auto discovery page cannot receive auto discovery completion message. Hence it
does not finish. If this happens, click cancel auto discovery link in the page and redo auto
discovery again.
8.29 Why is there a VPN shown in topology after it has been delete in Web page.?
The reason is that the massage of VPN deletion is not received by topology due to network
problem. In this case please reload topology tree.
8.30 Why don't some SA links belong to any VPN but they are shown undeployment failure in
topology when undeploying some SA links in a slot?
When undeploying some SA links in a slot, some fail but their associated VPNs are marked
invalid because the system is busy and undeployment is not completed. In this case, remove
these SA links manually.
8.31 What's the restriction of importing a P device to an AS in MPLS global network topology?
A P device can only exist in one AS.
8.32 On a PE device, configure two VPN instances, associate them with two interfaces respectively,
and set the same IP address and mask for the interfaces. When I view the SA link information
of the PE device on the access topology, the IP address and mask of the interface on one
of the links are displayed as "N/A". Why?
The MVM module reads SA link information based on the standard MIB. The standard MIB
requires that the interfaces on the same device cannot have the same IP address. As a result,
the MVM cannot read duplicate IP address information and displays "N/A" instead. To
prevent such problems, do not configure two or more interfaces on a device with the same
IP address.
8.33 Why doesn't the global topology show the links between P devices and PE devices after I
import P devices? What should I do to solve this problem?
To solve this problem, you must add links between P devices and PE devices in the topology
in either of the following ways:
•
Use the Auto Link function in the global topology to add links between P devices and
PE devices.
•
If the IP address of an interface directly connecting the devices does not have a 30-bit
mask, you must manually add links in the topology.
8.34 When a VPN or SA was added as the monitor target of a PE interface (which is a VLAN
interface), a success message appears. However, the actual operation result is failure. Why?
The traffic monitor function allows you to map one physical interface to only one VLAN
interface. Otherwise, the system can give an inconsistent prompt message with the actual
monitor status.
8.35 In an MCE network, the MCE-CE link data is different from the actual traffic. Why?
135