HP Intelligent Management Center Licenses - Manual (Page 137)

Glossary of Terms
AC Attachment circuit that connects a CE to a PE. It can use physical interfaces or virtual interfaces.
Usually, all user packets on an AC, including Layer 2 and Layer 3 protocol messages, must be
forwarded to the peer site without being changed.
Access Topology Access topology involves global topology and VPN access topology. Global topology displays
the network structure of all VPN resources, including all PEs, CEs and the AS Core; while the
VPN access topology displays network structure of all VPN resources in a VPN.
AS Core An Autonomous System (AS). It can contain different regions and devices. In the global topology
of an MPLS VPN network, AS Core can also represent a network composed of a set of core
devices. MVM does not manage the devices in the network.
Auto Discovery Based on VPN resources, auto discovery enables you to discover VPNs and VPN links existing
in a network by using the VPN instance RT value of a PE device.
BGP Border Gateway Protocol. It establishes signaling sessions through route reflectors (RRs) and
supports networking across multiple autonomous systems (ASs).
BGP/MPLS VPN Border Gateway Protocol/Multiprotocol Label Switching VPN, uses BGP to advertise VPN routes
and uses MPLS to forward VPN packets on service provider backbones.
BSB Blockade State Block.
CE Customer edge device that is directly connected with the service provider network.
CE Dual-Homing A CE router is connected to two Provider Edge (PE) routers, and the binding VRF information of
their interfaces connecting to the two CEs belongs to the same Virtual Routing and Forwarding
(VRF) instance, such kind of network scheme is called CE dual-homing.
Configuration
Audit Compare the latest configuration that MVM synchronized from the device with the device
configuration saved in the MVM. The results are displayed in the PE device list and the network
topology.
Configuration
Changed Compare the latest configuration that MVM synchronized from the device with the device
configuration saved in the MVM. If they are not consistent, the device is considered as
configuration changed. If not consistent, it is considered as configuration changed.
Connectivity Audit Connectivity between CEs in the same VPN (Inter-Spoke connectivity is not audited by default,
unless otherwise specified.) is audited and the connectivity or unconnectivity between CEs is listed
in detail.
Customized Group With this function, you can divide VPNs into manageable groups as needed.
Export RT Export RT defines which sites can receive VPN-IPv4 routes. A local PE sets this type of VPN target
attribute for VPN-IPv4 routes learnt from directly connected sites before advertising them to other
PEs.
Full mesh network A full mesh network has a fully connected mesh topology. For a VPLS VPN network, it means that
every PE on the network has a direct connection to every other PE on the network, logically.
Full-Mesh In this networking scheme, each site contains a group of RT attributes with values of Import RT
and Export RT being the same, and all sites are hub sites.
H-VPLS network In an H-VPLS network, all NPE devices are fully meshed logically, and a UPE device establishes
a virtual connection with only the nearest NPE device.
HoPE MVM includes three types of HoPEs: SPE, MPE and UPE, with no limit on the number of levels.
A one-level PE is called a general PE, a two-level HoPE includes SPE and UPE. If there is an HoPE
of three-level or more than three level, the lowest level is UPE, the highest is SPE, and the PEs in
the middle are MPEs.
Hub-Spoke In this networking scheme, the site in the center is called the hub site, which knows routes to all
the other sites in the same VPN; the sites that are not in the center are called spoke sites, traffic
from which reaches the destination through the hub site. Hub site is the central site of spoke sites;
therefore this type of networking scheme is called Hub-Spoke networking.
Import RT Import RT defines from which sites a PE can receive routes. A PE checks the Export RT of VPN-IPv4
routes advertised by other PEs. If the Export RT matches the Import RT of the VPN instance, the
PE adds the routes to the VPN routing table.
137