HP Intelligent Management Center — MVM User Guide Abstract This guide contains basic information for network administrators, engineers, and operators who use the MVM product.
© Copyright 2012, 2012 Hewlett-Packard Development Company, L.P. 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. The information contained herein is subject to change without notice.
Contents 1 MVM Introduction.......................................................................................7 2 L2VPN Manager........................................................................................8 L2VPN Manager Overview........................................................................................................8 Usage Summary.....................................................................................................................11 Typical Applications..........
Managed objects..........................................................................................................42 Relationship between managed objects............................................................................43 Usage summary.....................................................................................................................45 VPN discovery...................................................................................................................
Manage CE.................................................................................................................78 Import CE................................................................................................................78 Add non-managed CE..............................................................................................79 Remove CE..............................................................................................................80 Modify non-managed CE.....
Query device features.............................................................................................113 Configure device RSVP............................................................................................113 Configure device RSVP HELLO extension information...................................................114 Interface features.........................................................................................................114 Query interface RSVP TE information...........
1 MVM Introduction The four MVM modules covered in this book are L2VPN Manager, MPLS Manager, and MPLS TE Manager. Each module contains an overview of capabilities and applications followed by a detailed explanation of each function and associated devices.
2 L2VPN Manager L2VPN Manager is used to manage the Layer 2 VPN networks, including MPLS-based VPLS networks and link layer-based PBB networks. The L2VPN Manager provides four functions: VPN devices, VPN resources, VPN deployment, and automatic discovery. For more information about these functions, see Operation Guide. L2VPN Manager allows administrators to assign operation rights to operators. For further details, see VPN Privilege Management.
The figure shown above illustrates a typical H-VPLS network, which involves the following basic concepts: • UPE (User Facing-Provider Edge): User facing provider edge device that functions as the user access convergence device. • NPE (Network Provider Edge): Network provider edge device that functions as the network core PE. An NPE resides at the edge of a VPLS network core domain and provides transparent VPLS transport services between core networks. • U-PW: PW link between a UPE and an NPE.
Basic VLL concepts VLL(Virtual Leased Line): VLL provides point-to-point L2VPN services over the public network. With VLL, two sites can communicate as if they were directly connected. VLL is a form of MPLS L2VPN. It uses inner labels to identify virtual lines (Layer 2 tunnels), hereinafter referred to as virtual circuits (VCs), and uses outer labels to identify public tunnels.
The above figure shows a typical PBB networking scenario. In a typical PBBN, there are two types of devices, BEB and BCB. • BEB (Backbone Edge Bridge): Like a PE in an MPLS network. It performs MAC-in-MAC encapsulation for the incoming packets and then delivers the encapsulated packets to subsequent devices, which will forward the packets according to the B-MAC and B-VID.
Deployment flow NOTE: You can add PEs and CEs to a VPN through VPLS deployment, VLL deployment, and PBB deployment. You can also remove the PEs and CEs from a VPN or remove a whole VPN through the function. VPN privilege management The system allows administrators to authorize different operators to manage different VPNs. When adding or modifying an operator account, an administrator can authorize the operator to manage certain VPNs or change which VPNs the operator can manage.
2. Import PE devices to the L2VPN Manager. a. Select the Service tab to enter the L2VPN manager system. b. Select VPN Devices > PE Devices from the navigation tree to enter the PE device list page. c. Click Import PE to enter the page for importing PE devices. d. Click Select Device. On the pop-up page, select PE 1 and PE 2. You can query the devices by specifying the device label, IP, or status. e. Click OK to return to the page for importing PE devices. f. Click OK. 3.
VLL Instance Configuration Application scenario Company H locates in city B and uses PE 1 and CE 1; company Z locates in city N and uses PE 2 and CE 2. PE 1 and PE 2 are enabled with MPLS and MPLS L2VPN, and each configured with an LSR ID. The two companies are going to undertake corporate restructuring through merge into a new group for the need of business development and strategic planning.
a. b. c. d. On the local PE configuration page, click the Select button behind the UNI Interface text box. On the pop-up page, select the PE interface connecting CE 1. Type the service instance and encapsulation VLAN for the UNI interface, and select the encapsulation type. Click the Select button behind the CE Device text box. On the pop-up page, select a CE device (CE 1). Click Next to enter the remote PE configuration page. 6. Configure the remote PE (PE2). a.
a. b. 16 Select the Homepage tab, and then click Add Devices in the navigation tree. Enter the IP addresses of the devices (PE 1, PE 2, CE 1, and CE 2) to be managed, specify the corresponding Telnet and SNMP parameters, and then click OK to add these devices to the platform. 2. Import PE devices to the L2VPN Manager. a. Click the Service tab on the navigation bar. b. Select VPN Devices > PE Devices in the navigation tree. c. Click Import PE to enter the page for importing PE devices. d.
Precautions On the configuration summary page, you can configure to deploy the configuration to the devices immediately. Otherwise, the links will appear only on the topology diagram, with the status being Undeployed. Using L2VPN Manager The L2VPN Manager provides four functions: VPN devices, VPN resources, VPN deployment, and automatic discovery. • VPN Devices—VPN devices include PE devices and CE devices. CE devices include managed CEs and non-managed CEs.
Import PE Use this function to import one or more PEs from the platform to the L2VPN Manager. For VPLS and VLL networking, a device can be imported as a PE only if it is enabled with MPLS and MPLS L2VPN and configured with an LSR ID. For PBB networking, a device can be imported as a PE if it is enabled with L2VPN. Operation procedure 1. 2. 3. 4. Click the Service tab on the top navigation bar, and then select VPN Devices > PE Devices in the navigation tree to enter the PE list page.
Synchronize PEs immediately Use this function to synchronize the configuration of a PE to that on the L2VPN Manager. From the PE device list, check the last synchronization time and synchronization status of a PE to determine whether the current configuration of the PE is valid. Operation Procedure 1. 2. 3. Click the Service tab on the top navigation bar, and then select VPN Devices > PE Devices in the navigation tree to enter the PE list page. Enter query criteria. Click Query.
Delete CE Use this function to delete existing CE devices in the L2VPN Manager, including managed CE devices and non-managed CE devices. When this operation succeeds, the corresponding managed CEs, non-managed CEs, and links are deleted from the L2VPN Manager. Operation Procedure 1. 2. 3. Click the Service tab on the top navigation bar, and then select VPN DevicesCE Devices in the navigation tree to enter the CE list page. Select one or more CEs you want to delete. Click Delete.
Operation procedure 1. 2. Click the Servicetab on the top navigation bar, and then select VPN Devices > CE Devices in the navigation tree to enter the CE list page. Click the VLAN Mapping icon of a CE to enter the page for VLAN mapping list. Add VLAN mapping Use this function to add the VLAN mapping relation for all interfaces of a CE. Operation Procedure 1. 2. 3. 4. 5. 6. 7. 8.
Configuration procedure 1. Define VPN. This function allows you to configure a VPN's basic information, including VPLS VPN networking type (PE Type), VPN name, VSI ID, PW transport mode, audit interval, VPN description, and contact information. Precautions 2. • Valid characters in a VPN name are letters, digits, and underscores. • VSI ID is generated randomly. You can modify it in the range 1 to 4294967295. • PW transport mode can be VLAN or Ethernet. VLAN is the default.
UNI interface, service instance, bandwidth, encapsulation type, encapsulation VLAN, access type, and CE device. Steps to configure AC information a. b. c. d. Click Add in the AC list area, and then on the pop-up page, select a PE interface. Type the service instance, encapsulation VLAN and bandwidth, and select the encapsulation type and access type. ClickSelect behind the CE Device text box, and then on the pop-up page, select a CE device. Click OK. Steps to configure PE information a. b. c.
VLL Deployment This function helps you configure and deploy a VPN of VLL type. After you configure a VLL VPN, if you do not deploy the VPN configuration immediately, a deployment task in state of "undeployed" is added on the deployment task list. If you deploy the VPN configuration immediately, a deployment task in state of "deploying" is added on the deployment task list. After the deployment, you can view the deployment result. Configuration procedure 1. Define VPN.
encapsulation type, and CE device. Refer to the "local PE configuration" part for the operation procedure and precautions. 4. Configuration summary. This function displays the configuration commands to be deployed to PE devices. a. On the remote PE configuration page, click Next to enter the summary page. Precautions • The configuration commands are generated by the system automatically. You cannot modify them.
Steps to configure the PE information a. b. Click the Add button in the PE device list area, and then on the pop-up page, select one or multiple PE devices. Click the Modify icon in the Configuration column, and then on the pop-up page, select one or multiple PE interfaces. Precautions 3. • For service instance, you can only type a number in the range 1 to 4094. • For bandwidth, you can only type a number in the range 1 to 1000. • Encapsulation VLAN IDs are in the range 1 to 4094.
c. d. 2. Select Undeploy VPN from the Undeploy Operation drop-down list. Click Next. Configuration summary. This step displays the commands to be deployed to devices. a. Click OK to deploy the commands to devices. If you also selected Also Delete VPN, the VPN will be removed from the VPN list; If you do not select this option, the VPN will be kept on the VPN list and only the devices and links in the VPN will be deleted. Undeploy PEs 1. Select VPN. a.
list. After the task is deployed, you can refresh the deployment task list to view the deployment status. Deployment task management This function allows authorized operators to view all VPN deployment tasks, delete and modify deployment tasks, view task details and task deployment failure reasons. Query deployment task This function allows you to query deployment tasks by VPN name, deployment status, VPN type, and deployment operation type. Configuration procedure 1. 2. 3.
Configuration procedure 1. 2. 3. Click the Service tab on the top navigation bar, and then select VPN Deployment > Deployment Tasks in the navigation tree to enter the deployment task list page. Click the Modify icon of the deployment task that you want to modify. You will enter the deployment flow of the task and do the modifications. The deployment flow may be VPLS Deployment VLL Deployment PBB Deployment or Undeployment, depending on the deployment operation type of the task.
Parameters • Synchronize PE devices before auto discovery: If you select this parameter, the system will synchronize PE devices before performing automatic discovery, so that the automatic discovery process can use the updated configuration. • Status: Displays the status information of the discovered VPNs. The status can be one of the following: ◦ Existed: Indicates that system finds new links that belong to the VPN. ◦ New VPN: Indicates that the VPN is newly discovered this time.
3 MPLS Manager The MPLS manager focuses on basic concepts, principals and applications of VPN, MPLS, and BGP/MPLS VPN.
1. 2. 3. 4. Classified by networking model • Virtual Private Dialup Network (VPDN): Point to point VPN • Leased line VPN (VPRN, VPLS, VLL) Classified by service application • Access VPN: Allows users and small offices to establish private network connections with the intranet and extranet of their enterprise over a public network. • Intranet VPN: Interconnects points distributed inside an enterprise. • Extranet VPN: Extends an enterprise network to cooperators by using VPN.
LER and then forwarded along an LSP to the egress LER. All the intermediate LSRs are called transit LSRs. The following describes how MPLS operates: 1. First, the LDP protocol and the traditional routing protocol (such as OSPF and ISIS) work together on each LSR to establish the routing table and the label information base (LIB) for intended FECs. 2.
In the basic structure of an MPLS-based VPN a CE (Customer Edge) can be a router, switch, or host. All PEs (Provider Edge) are on the backbone network. PE is responsible for managing VPN users, establishing LSP connections between PEs, and allocating routes among different branches of the same VPN. 2.
The classification of CEs and PEs mainly depends on the range for the management of the provider and the customers, and CEs and PEs mark the boundary between them. The following are the basic concepts of BGP/MPLS VPN: • Site Site is often mentioned in the VPN. Its meanings are described as follows: 1. A site is a group of IP systems with IP connectivity being implemented without relying on any service provider network. 2.
RD (Route Distinguisher) • 1. 2. You are recommended to configure a distinct RD for each VPN instance on a PE, guaranteeing that routes to the same CE use the same RD. The VPN-IPv4 address with an RD of 0 is in fact a globally unique IPv4 address. RD code format is as follows: Type: two bytes. Value: six bytes.
BGP/MPLS VPN Packet Forwarding For basic BGP/MPLS VPN applications in a single AS, VPN packets are forwarded with two layers of labels: Layer 1 labels: Outer labels, used for label switching inside the backbone. They indicate Label Switch Path (LSPs) from the local PEs to the remote PEs. Based on layer 1 labels, VPN packets can be label switched along the LSPs to the remote PEs. Layer 2 labels: Inner labels, used for forwarding packets from the remote PEs to the CEs.
simplest case, all users in a VPN form a closed user group. They can forward traffic to each other but cannot communicate with any user outside the VPN. For this networking scheme, you need to assign a VPN target to each VPN for identifying the export target attribute and import target attribute of the VPN. Moreover, this VPN target cannot be used by any other VPNs. 1. Full-Mesh VPN or Simple VPN In the simplest case, all users in a VPN form a closed user group.
MPLS VPN Manager overview System Description MVM aims at providing solutions for MPLS VPNs of enterprises of various scales. The devices involved can be VPN network devices of H3C, Cisco and Huawei. MVM provides management functions such as service discovery, topology display, status monitoring, connectivity audit, performance management and service deploy. MVM is developed based on the next generation network management platform—Intelligent Management Center.
topology in real time. You can further use the VPN connectivity audit function to verify your deployment. • VPN device management—To manage a VPN in MVM, administrators must first import to MVM all devices that the VPN contains. MVM then displays the VPN topology based on the devices. The VPN devices can be classified into PEs and CEs. • Auto discovery—MVM detects the entire VPN network through auto discovery, which requires no manual intervention.
MPLS VPN Manager overview 41
Example 2: If CEs are to be managed by MVM, two networking schemes are available: • Manage CEs through management VPN MVM manages PEs through links; manages CEs through establishing a management VPN between Management CE and Management PE, and the CEs to be managed are added to the management VPN, as shown in the following figure. • Manage CEs: In this networking scheme, you do not need to create a management VPN.
MVM manages the following objects: • Service VPN In MVM, the VPN used to carry user service data is called service VPN. The VPN in MVM defaults to service VPN unless otherwise specified. • Management VPN The purpose of building a management VPN is to manage CEs. To prevent building of management VPN from interrupting service VPN discovery and management, MVM provides setting and filtering of the management VPN.
The following is the relationship between every two objects: 1. One to one mapping between CE and SA, that is, one CE maps one SA. If a CE is dual-homed, one CE can map multiple SAs. 2. Multiple to multiple mapping between SA and SC, that is, one SA can map one or multiple SCs and one SC can map one or multiple SAs. 3. One to one mapping between SA and Interface, that is, one SA can map one interface on a PE. 4. One to multiple mapping between VPN and SC, that is, one VPN can include multiple SCs. 5.
Usage summary Depending on the situation, you can use MVM differently. Below is a list of the various situation: • • • • VPN network discovery ◦ MVM has just been installed and a network topology needs to be displayed. ◦ VPN configuration is changed. VPN maintenance ◦ To know whether a VPN works normally. ◦ To know whether inter-CE communication in a VPN is normal. ◦ To know whether VPN configuration changes. VPN deployment ◦ To deploy a VPN network. ◦ To adust VPN network structure.
Audit • VPN link connectivity audit MVM can audit connectivity between CEs in the VPN that has been created, helping you find out connectivity in a VPN network in time. After connectivity audit, MVM can provide detailed results of audit for VPN links. If VPN services are interrupted, you can find, locate and troubleshoot the fault links by viewing audit results for connectivity between CEs. For details, refer to Connectivity Audit.
VPN Performance management • Set default threshold You can set traffic default thresholds to view traffic load of a VPN, and you can set two levels of default thresholds to know network running status on time. For details, refer to Set Default Thresholds. • VPN traffic monitoring setting MVM allows you to monitor traffic of the whole VPN or separate SAs and collect related statistics. For details, refer to traffic monitoring setting.
Scenario analysis As related parameters have been configured on the devices, MVM can monitor and manage the VPN on real time. Operation procedure 48 1. Add device to the platform. a. Select Resource on the platform, click Resource Management > Add Device in the navigation tree, type the IP addresses of PE 1 through PE 3 and CE 1 through CE 3 and the corresponding Telnet and SNMP parameters, and then click OK. 2. Import the PE devices to the MPLS VPN Manager system. a.
d. e. Under SC List, click Add to add an SC. On the Add SC page, type the SC name SC(1000:1.1000:2), select Hub-Spoke from the SC Networking Type drop-down list, type the Hub Import RT 1000:1 and the Hub Export RT 1000:2, and then click OK. 5. Auto discover VPN. a. Click MPLS VPN Manager > Auto Discovery in the navigation tree. b. Click Select PE Device and select PE 1, PE 2, and PE 3, which can be queried by device name, IP address, contact, location, device status and device category. c.
Scenario analysis As related parameters have been configured on the devices, MVM can monitor and manage the VPN on real time. Operation procedure 50 1. Add device to the platform. a. Select Resource on the platform, click Resource Management > Add Device in the navigation tree, and type the IP addresses of PE 1 through PE 3 and CE 1 through CE 3 and the corresponding Telnet and SNMP parameters. b. Click OK. 2. Import the PEs to the MPLS VPN Manager system. a.
c. d. e. In the VPN lwhich can be queried by device name, IP address, contact, location, device status and device categoryist, click the link with VPN name as VPN(1000:1.1000:1) to enter the page of the basic information of the VPN. Under SC List, click Add to add an SC. On the Add SC page, type the SC name SC(1000:1.1000:1), select Full-Mesh from the SC Networking Type drop-down list, and type the Hub RT 1000:1. Then click OK. 5. Auto discover VPN. a.
• CE 3: The management IP address is 10.172.6.1/32. • CE 4: The management IP address is 10.172.7.1/32. Scenario analysis MVM can monitor device roles in HoVPN on real time. Suppose that CE 1 and CE 3 need to communicate with each other after MVM manages all the devices. Add Import RT value 1000:2 to the VRF instance vpnHub associated with interface Eth 1/0 on UPE 1 and add Import RT value 1000:2 to the VRF instance vpnHub1 associated with interface Eth 5/1 on UPE 2.
d. e. On the Import Device page, click Select Device, and then select CE 1, CE 2 and CE 3, which can be queried by device name, IP address, contact, location, device status and device category. Click OK. On the Import Device page, click OK. 4. Create VPN. a. Click VPN Resources > VPN Management in the navigation tree and click Add. b. Type the VPN name VPN(1000:1.1000:2) on the Add VPN page, and the system defaults to selecting periodic audit. Click OK. c. In the VPN list, click VPN(1000:1.
transmission of data in the internal network, the company hopes to add the VPNs to the current network, keeping the original VPN network independent. Since company H accesses the Internet through carrier, if you connect company Z to the Internet by renting PE from carrier, resources will be wasted. After feasibility analysis of the link from the shared PE in city S to CE, VMCE is taken as the intermediate device to connect the two branches in city S to the Internet.
Operation procedure 1. Add device to the platform. a. Select Resource on the platform, click Resource Management > Add Device in the navigation tree, type the IP addresses of PE 1 through PE 4 and CE 1 through CE 5 and the corresponding Telnet and SNMP parameters. Then click OK. 2. Import PEs to the MPLS VPN Manager system. a. Select the Service tab on the platform page to enter MPLS VPN Manager system. b.
7. Query topology. a. Enter the MPLS VPN group list area, select the newly added VPN(1000:1,1000:1) and VPN(2000:1,2000:1) to query its access topology and service topology. 8. Audit configuration changes on PE1. a. Click PE Device in the navigation tree, select PE 1, and then click Synchronize. b. Or, in access topology, select UPE 1 and UPE 2, and right-click to select Synchronize. 9. Query audit result of configuration changes. a.
Scenario analysis Scenario Analysis As all the devices have been configured, you can manage the VPN network through MVM, and thus manage and control the data centers. You can also use MVM to perform Connectivity Audit on the network. Operation procedure 1. Add device to the platform. a. Select Resource on the platform, click Resource Management > Add Device in the navigation tree, type the IP addresses of PE 1 through PE 4 and CE 1 through CE 5 and the corresponding Telnet and SNMP parameters.
a. b. c. d. e. Click VPN Resources > VPN Management in the navigation tree and click Add. Type the VPN name VPN(50:50.50:50) on the Add VPN page, and the system defaults to selecting periodic audit. Click OK. In the VPN list, click VPN(50:50.50:50) to enter the page of the basic information of the VPN. Under SC List, click Add to add an SC. On the Add SC page, type the SC name SC(50:50.50:50), select Full-Mesh from the SC Networking Type drop-down list, and type the Hub RT 50:50. Then click OK 5.
Scenario analysis The headquarter requires that the branches cannot communicate with one another, but can communicate with the headquarter. To achieve this purpose, Hub-Spoke networking scheme is adopted. CE 1 is the headquarter of the company, that is, it is the hub site; CE 2, CE 3 and CE 4 are the three branches, that is, they are spoke sites. Suppose that the BGP/MPLS VPN backbone where the PEs reside has been established and the MPLS function has been enabled on the PEs and PE interfaces.
Operation procedure 60 1. Add device to the platform. a. Select Resource on the platform, click Resource Management > Add Device in the navigation tree, and type the IP addresses of PE 1 through PE 4 and CE 1 through CE 4 and the corresponding Telnet and SNMP parameters. Then click OK. 2. Import PEs to the MPLS VPN Manager system. a. Select the Service tab on the platform page to enter MPLS VPN Manager system. b.
j. k. Under CE route, type destination IP/mask 0.0.0.0/0, click Add, and click Next. Select Deploy Immediately, and click OK. 6. Deploy spoke sites in a VPN. a. Click VPN Resources >SA Management in the navigation tree and click Add. b. Click PE Device List and then select PE 2. Click OK. c. Click Select VPN. Select the newly added VPN VPN(100:1,100:2) in step 4, and click OK. d. Click Next, and select the newly added SC(100:1,100:2). Add by Spoke, and click Next. e.
Suppose the VPN works normally and MVM can manage the VPN normally. The company hopes to remove CE 3 connected to PE 3 from the VPN, not affecting other networks. Scenario analysis Based on the company's requirements, you can use the Remove VPN link function provided by MVM to remove PE 3-CE 3 link from the topology, supposing that the VPN works normally in MVM. Operation procedure 1. Select VPN link. Approach 1—Click MPLS VPN Manager > Global Topology in the navigation tree to enter global topology.
Using MPLS VPN manager MPLS VPN manager operation There are six functions and operation modes of MVM in detail. The functions include VPN resource management, VPN device management, auto discovery, VPN monitoring, alarm TopN, and traffic monitoring. VPN resource management Resource management in MVM includes device resource management, VPN and SC management, customized group management, and management VPN configuration. VPN and SC are core resources of MVM.
Parameters • SC Networking Type: SC networking falls into two types Hub-Spoke and Full-Mesh based on the RT value. • Hub's Import RT: Represented in two formats. • ◦ 16-bit AS number:32-bit user-defined number. For example, 101:3. The two numbers are in the range of [0, 65535] and [0, 4294967295] respectively, but cannot be 0 simultaneously, namely 0:0. ◦ 32-bit IP address:16-bit user-defined number, such as 192.168.122.15:1. The two numbers are in the range of [0.0.0.0, 255.255.255.
Functions • Query VPN • Add VPN • Remove VPN • Modify VPN • Modify VPN audit interval • Audit VPN • VPN details • Troubleshooting Query VPN In MVM, operators can query VPN through inputing the conditions. Operation procedure 1. 2. 3. Click the Service tab, click MPLS VPN Manager, and then click VPN ResourcesVPN Management in the navigation tree. In the of VPN List Page, type the VPN name, VPN status, audit status and audit result. Click Query.
Parameters • VPN Name: Uniquely identifies the VPN. "--" is a reserved name. It cannot be used. • Connectivity Audit: You can select Periodic audit or Not Audit. If you select Periodic audit, you need to type the period and select whether to audit the inter-Spoke unconnectivity. Remove VPN In MVM, you can remove one or more VPNs simultaneously Operation procedure 1. 2. 3. Click the Service tab, click MPLS VPN Manager, and then click VPN ResourcesVPN Management in the navigation tree.
Operation procedure • Approach 1 1. Enter VPN details page. 2. 3. 4. ◦ Method 1: Click the Service tab, click MPLS VPN Manager, and then click VPN ResourcesVPN Management in the navigation tree, and then click the VPN to be modified on the VPN list page. ◦ Method 2: Click the Service tab, click MPLS VPN Manager, and then click the VPN name in the VPN ResourcesVPN Management menu in the navigation tree.
Operation procedure 1. 2. 3. 4. 5. Click the Service tab, click MPLS VPN Manager, and then click the group name in the VPN Resources > Group Management menu in the navigation tree. Click Import VPN on the customized group page. Type the VPN name on the pop-up Import VPN window, and then click Query. Select one or more VPNs in the query result. Click OK. Verification The imported VPN is displayed in the VPN list of the current customized group page.
Remove customized group In MVM, you can remove only one customized group at a time. Operation procedure 1. Take the following methods to enter the Customized Group list page of an AS or Region view: a. Click the Service tab, click MPLS VPN Manager, and then click VPN Resources > Group Management in the navigation tree to enter the Customized Group List page. b. On Customized Group list page, click an group name link in the list to enter the lower-level Customized Group list page. 2.
3. 4. Input the AS name and number. Click OK. Verification • The newly added AS is listed in the Region Management List. • The newly added AS is displayed on the Region Management menu. • The newly added AS is displayed in the global topology. Parameters • AS Name: The unique identification of an AS. The names of different ASs cannot be the same. • AS Number: The unique number identification of an AS.
Parameters • AS Name: The unique identification of an AS. The names of different ASs cannot be the same. • AS Number: The unique number identification of an AS. The valid value ranges from 1 to 4294967295 and the numbers of different ASs cannot be the same. Add region You can add a reguin to the system with the add region function on MVM. Operation procedure 1. Take the following methods to enter the Sub-region/PE Device list page of an AS or Region view: a.
Precautions Do not remove a region containing a subregion or PE. Modify a region You can modify the name of a region existing in the system with the modify region function on MVM. Operation procedure 1. Use the following methods to enter the Sub-region/PE Device list page of an AS or Region view: a. Click the Service tab, click MPLS VPN Manager, and then click VPN Resources > Region Management in the navigation tree to enter the AS List page. b.
Verification • On the AS Information or the Region Information page, you can see the successfully imported P devices. • In the global topology, you can see the successfully imported P devices. Precautions • MVM allows only one device import operation (P, PE, CE, MCE or VMCE import) at a time. During device importing, you can quit the operation. However, the started import operation is still running on the server background.
the Service tab, click MPLS VPN Manager, and then click VPN Devices > PE Device List in the navigation tree to enter the PE device list page. • Check the last synchronization time and synchronization status of a PE to determine whether the current configuration on the PE is valid. • Switch to the platform to view the basic information about the PE. • View SA information and PE-related alarm information. • View the latest synchronized VRF configuration information on the PE.
Precautions • MVM allows only one device import operation (PE, CE, MCE or VMCE import) at a time. During device importing, you can quit the operation. However, the started import operation is still running on the server background. If you start a new import operation before the system completes the previous one on the server background, the system prompts that an import operation is running. • Each device can be imported as one type at a time.
Parameters • Synchronization Status: Last synchronization status of a PE, including "Succeeded", "Failed", "Synchronization is running", and "--". "--" means PE device synchronization status is unknown. It may be caused by during PE synchronization stop MPLS VPN daemon process. In this case please synchronize PE device manually. Synchronize PE immediately Operation procedure Approach 1 Click the Service tab, click MPLS VPN Manager, and then click VPN Devices > PE Device List in the navigation tree.
After a PE is removed, all links related with this PE are removed from the network topology. If removing the PE results in disconnection between two CEs in a VPN, the link between the two CEs are removed from the VPN topology. If you import the PE again, you must execute the auto discovery function to regain the SA information of the PE, and reconstruct the VPN links in both the network topology and the VPN topology.
PE VPN information Click the View link on the PE device list page to enter the PE VPN information page, which includes all the SA information about the PE and latest ten unacknowledged alarms of the PE. The SA information of the PE lists all the SAs that have accessed to the current PE, including the binding interfaces, the connected VMCEs, the connected CEs, and the SA configuration audit status. You can view the detailed information about the above items through corresponding links.
if a device serves as MCE in the VPN network, the device must be imported as a MCE; otherwise, MVM cannot discover links with MCE in the network. Operation procedure 1. 2. 3. 4. Click the Service tab, click MPLS VPN Manager, and then click VPN DevicesCE Device List in the navigation tree to enter the CE device list page, and then click Import on the page. Click Select to select the device to be imported, and then click OK.
Verification • The added non-managed CE is listed in the CE device list, and the status is Unmanaged. Precautions • In MVM, you need to configure interfaces for non-managed CEs. • If the interface IP address of a non-managed CE is null, the connectivity of the non-managed CE is audited through the status of the PE interface that connects with the non-managed CE. • Non-managed VMCEs can be automatically associated to the VMCE attribute of the links during auto discovery.
Parameters • The type of the non-managed device cannot be modified. The interfaces that have already connected to the device cannot be removed. Auto discovery The auto discovery function provides you an easy way to analyze and combine SCs to discover all the VPNs and VPN links in the network by using device parameters in the current networking. VPN auto discovery The VPN auto discovery function discovers VPNs and VPN links existing on a network through collected VRF information of PEs.
Add link You can select all the VPN links and add them to MVM after finishing the link configuration Operation Procedure Approach 1: 1. Select the VPNs to add links to. Then click Next. 2. Select VPN links one by one for the selected VPN, and click the Configure link to add or modify CE information for the VPN links with incomplete information. 3. Click OK. Approach 2: 1. Select the VPNs to add links to. Then click Next. 2. Select VPN links one by one for the selected VPN. 3.
Access topology and service topology Access topology Access topology includes global topology and VPN Access Toplogy. Network structures of all VPN resources including all the PEs, Ces, and AS Core can be displayed in global topology. VPN access topology displays network structures of all VPNresources. After the NTA is installed, the access topology also allows you to monitor the traffic on access links, PE devices, and VPNs, and view the monitored traffic information.
Operation Procedure 1. Click the Service tab, click MPLS VPN Manager, and then click VPN Resources > VPN Management in the navigation tree, and click the Service Topology link in the VPN list. Functions • Connectivity audit. Select a VPN link in the topology and right-click to select Connectivity Audit to start auditing link connectivity. • Whole VPN connectivity audit.
Operation Procedure 1. 2. 3. 4. 5. Click the Service tab, and then click MPLS VPN Manager > Global Topology in the navigation tree. In the popped up window, open MPLS VPN global topology; or click the Access Topology or Service Topology link of a VPN to open its access or service topology. Click Filter on the toolbar on this page, and the Filtering in Topology View window pops up. Select the regions and devices to be filtered in the By Device tab. Then click OK.
Operation procedure 1. 2. 3. Click the Service tab, click MPLS VPN Manager, and then click VPN Resources > VPN Management in the navigation tree and click the link of the intended VPN. Query unacknowledged alarm information on the VPN Details page. You can query all the unacknowledged alarms related to the VPN in the area for unacknowledged alarms information. These alarms include alarms generated by all the PEs and generated by the VPN.
Precautions • By default, the connectivity audit report displays only the failed VPN links connecting CEs. To display the normal links in addition to the failed links in the connectivity audit report, select the Display all links option at the upper right corner. Modify audit parameters This function allows you to modify VPN connectivity audit parameters such as audit period and whether to perform unconnectivity audit. Operation procedure 1. 2.
• Ping the peer CE device on the local PE device to decide whether the link between them is connected. • If all the above are connected, inter-CE link is connected; otherwise, inter-CE link is not connected. Operation procedure 1. 2. 3. Click the Service tab, click MPLS VPN Manager, and then click VPN Resources > VPN Management in the navigation tree, and click the Audit Status link or the Audit Result link of the intended VPN.
Parameters • Link configuration: Configuration information of the SA on the PE, including interface information and information of the bound VRF. • Manager configuration: Current configuration of the MVM. • Current configuration of the device: Configuration obtained from the latest synchronization. Service deployment MVM provides an easy way to deploy VPN services, with simple and friendly operation procedures.
Deploy SA Deploying SA for the specified PE device can implement both immediate deployment of SA configuration and deployment of configurations of all SAs. SA configurations cannot only be deployed on PEs but also on managed CEs. Follow these approaches to enter the SA Management page. • Approach 1: Click the Service tab, click MPLS VPN Manager, and then click VPN Resources > SA Managementin the navigation tree, and click Add on the SA Management page.
Precautions If you select Non-managed CE, the configuration information of the CE will not be deployed. 4. Configure VRF on PEs, including VRF name and RD value. The RT value of the selected SC will be configured on this VRF. VRFs existing on all the devices are listed in MVM, and you can re-use them with ease. Parameters • Existing VRF list: VRF information of all the devices. It is the latest information of the latest synchronization of the device.
Precautions If the VPN link to be deployed is connected with Non-managed CEs, configuration commands of the CEs will not be provided. Remove deployment This function enables you to undeploy an SA, and only the normal links can be undeployed. Operation procedure 1. 2. 3. Enter the Remove Deployment page. • Approach 1: Click the Service tab, click MPLS VPN Manager, and then click VPN Resources > SA Management in the navigation tree, select and click Undeploy on the SA Management page.
Parameters • Alarm TopN: Helps you view the VPNs, PEs, and CEs' fault information ranking TopN. • N must be one of 5, 10, 15, 20 in the TopN. The records in VPN, PE, CE list are no more than N respectively. Performance management Performance management allows you to collect and query VPN performance data, thus helping you monitor the running status of a VPN network.
Operation procedure 1. 2. 3. 4. Click the Service tab, click MPLS VPN Manager, and then click Traffic Monitor > VPN Traffic Monitor Setting in the navigation tree to enter the VPN Traffic Monitor Setting page. Select the query type and set query condition. Then click Query to query the corresponding VPN monitor information. You can perform the following operations on the selected VPNs in batches: • Click Add Monitor to set the selected VPNs as monitored.
Operation procedure 1. 2. 3. 4. 5. Click the Service tab, click MPLS VPN Manager, and then click Traffic Monitor > VPN Traffic Report to enter the VPN Traffic Report page. Set query type and query condition, and then click Query to view the latest data of VPN traffic. Click the View Details icon to view details of VPN traffic. Set time range and click OK. Select a display mode: • Click Table to display traffic data in table. • Click Line Chart to display traffic data in line chart.
• This year: The average performance data collected from 00:00:00 on January 1st of this year to the current time. If the current time is 24.12.06 15:30:30, the performance data of this year is the average data collected from 01.01.06 00:00:00 to 24.12.06 15:30:30. • Customized data: The average performance data collected from start time of Customized data to end time of Customized data. SA traffic report SA traffic report displays traffic data of a single SA.
Parameters • Level 1 and level 2 thresholds: You can set level 2 threshold only when level 1 threshold is valid. If the performance level exceeds the threshold, the system generates alarm information. The alarm severity of level 2 threshold is higher that of level 1 threshold. When the alarm severity of a performance data goes down from level 2 to level 1, the system generates alarm restore information. • Today: The average performance data collected from 00:00:00 to the current time.
4 MPLS TE manager Welcome to use this MPLS TE manager help, through which you can know about the functions provided by the MPLS TE manager and how to use these functions. Manager overview Functions of MPLS TE Network congestion is one of the major problems that can degrade network performance. It may occur when network resources are inadequate or when load distribution is unbalanced. Traffic Engineering (TE) is intended to avoid the latter situation, that is, congestion caused by load imbalance.
path, MPLS TE checks whether the cost value of the path is the lowest, whether the path satisfies the specified bandwidth and routing requirements, and so on. 3. Establishing tunnels. The headend node establishes a tunnel to the tailend node through a signaling protocol. The RSVP-TE signaling is commonly used to set up tunnels. The tunnels are unidirectional. 4. Forwarding packets. The system assigns different traffic to different TE tunnels to forward the traffic over the established tunnels.
• Advanced RSVP TE Features ◦ Device Features This function allows you to perform device RSVP TE configurations on MPLS TE devices. ◦ Interface Features This function allows you to perform interface RSVP TE configurations on MPLS TE devices. • MPLS TE Tunnel Management This function helps you establish MPLS TE tunnels, including static and dynamic tunnels. • Explicit Path Management This function allows you to configure explicit paths for dynamic tunnels.
adjust the path of the TE tunnel according to the network performance, and supports advanced features such as backup and Fast ReRoute (FRR). For the detailed configuration procedure, refer to MPLS TE Tunnel Management 5. Configure protection (optional). The MPLS TE manager allows you to configure backup path and FRR protection for a network node or link. Thus, once the node or link fails, traffic can be rerouted to the backup path for forwarding.
Operation Procedure 1. Import devices to the MPLS TE manager. a. Select the Service tab, select ResourceDevice from the navigation tree to enter the MPLS TE device management page. b. Click Import Device to import devices. For details, refer to Resource Manager. 2. Configure static MPLS TE tunnel. a. Select the Service tab, click MPLS TE Tunnel Management in the navigation tree to enter the MPLS TE tunnel list page. b. Click Add to enter the page for adding an MPLS TE tunnel. c.
Scenario Analysis Configure dynamic MPLS TE tunnel Router A -> Router B -> Router C -> Router D through a dynamic signaling protocol (such as RSVP-TE) and reserve resources on the devices along the tunnel, so that data from Route A to Router D is always serviced. Operation Procedure 1. Import devices to the MPLS TE manager. a. Select the Service tab, select ResourceDevice from the navigation tree to enter the MPLS TE device management page. b. Click Import Device to import devices.
Scenario Analysis You can create two tunnels through a dynamic signaling protocol: tunnel A (Router A -> Router B -> Router C) and tunnel B (Router A -> Router D -> Router C). The two tunnels have the same headend and tailend. Thus you can configure tunnel B as the CR-LSP backup tunnel of tunnel A. Note: You cannot configure CR-LSP backup for MPLS TE tunnels configured through the static CR-LSP protocol. Operation Procedure 1. Import devices to the MPLS TE manager. a.
• Router D: LSR ID address is 4.4.4.4/32; address of Ethernet 1/0 is 4.2.1.2/24. • Router E: LSR ID address is 5.5.5.5/32; address of POS 5/0 is 5.2.1.2/24; address of POS 5/1 is 6.2.1.2/24. Scenario Analysis Create tunnel A through a dynamic signaling protocol. The tunnel path is Router A -> Router B -> Router C -> Router D. In this tunnel, the link between Router B and Router C is to transmit important service data, therefore required to be protected.
Assume that the routers are reachable to each other after being configured with IS-IS or OSPF and are properly configured with basic MPLS and MPLS TE capabilities, as shown in the following figure: • Router A: LSR ID address is 1.1.1.1/32; address of Ethernet 1/0 is 2.1.1.1/24. • Router B: LSR ID address is 2.2.2.2/32; address of Ethernet 1/0 is 2.1.1.2/24; address of Ethernet 1/1 is 3.2.1.1/24; address of POS 5/0 is 5.2.1.1/24. • Router C: LSR ID address is 3.3.3.3/32; address of Ethernet 1/0 is 4.2.
c. d. e. Select Node Protection from the Protection Type drop-down list. Click Next to enter the tunnel's node list page. Select the node you want to protect, and then click Next to enter the backup tunnel list page. Select an unbound backup tunnel, and then click Bind. Add explicit path Application Scenario A company has five offices, office A through office E, which are connected with one another through networks.
a. b. c. d. e. Select the Service tab, and then click Explicit Path Management in the navigation tree to enter the explicit path management page. Click Add to enter the Add Explicit Path page to configure the basic parameters of an explicit path. Set the basic parameters and click Next to enter the next hop list page. On the next hop list page, you can perform the following operations: • Add: To add a next hop record, click Add.
Precautions When the traffic access type is Forwarding Adjacency, a reverse tunnel is required. A reverse tunnel must start from the tailend of the forward tunnel and terminate at the headend of the forward tunnel but can traverse any intermediate nodes. Using the MPLS TE manager TE topology This function is used to display the MPLS TE network topology.
Operation Procedure 1. 2. 3. Select the Service tab, and then select Resource ManagementDevice Management from the navigation tree to enter the device management page. Type the query values. Click Query. Import devices This function allows you to import one or more devices. Note that you cannot import a device repeatedly. Operation Procedure 1. 2. 3. 4. 5. Select the Service tab, and then select Resource ManagementDevice Management from the navigation tree to enter the device management page.
Precautions • Deleting a device from the system will delete the interfaces related to the device as well. • Devices referenced by MPLS TE tunnels cannot be deleted.
Precautions • The interface to be queried must be an MPLS TE interface. Configure interfaces This function is used to configure the MPLS TE interface information, including the management group information, maximum connection bandwidth and maximum reservation bandwidth. Operation Procedure 1. 2. 3. 4. Select the Service tab, and then select Resource ManagementInterface Management from the navigation tree to enter the interface management page.
Operation procedure • Approach 1: 1. Select the Service tab, and then select Resource Management > Interface Management from the navigation tree to enter the interface management page. 2. Select the interface to be enabled, and click Enable. • Approach 2: 1. Select the Service tab, and then select Resource Management > Interface Management from the navigation tree to enter the interface management page. 2. Click the icon for a disabled interface. 3. Click Enable Interface.
Operation procedure 1. 2. 3. 4. Select the Service tab, and then select RSVP TE Advanced Features > Device Features from the navigation tree to enter the device features page. Click the Edit icon of a record to enter the RSVP configuration page of the device. Configure the parameters. Click OK. Configure device RSVP HELLO extension information The RSVP Hello extension is used to test the reachability of RSVP neighbor nodes.
Operation Procedure 1. 2. 3. Select the Service tab, and then click MPLS TE Tunnel Management in the navigation tree to enter the MPLS TE tunnel list page. Select the query type and input the query value. Click Query. Precautions • The input query value must match the selected query type. If you select to query by tunnel name, you need to input the name or part of the name of a tunnel. Add/modify tunnel This function is used to add/modify an MPLS TE tunnel. Operation Procedure 1. 2. 3.
Precautions • When you delete a tunnel, the association between the tunnel and the explicit path bound with it will be removed, but the explicit path still exists. • Deleting different types of tunnels will affect different types of data. ◦ Normal Tunnel: Tunnels that are not configured with protection. Deleting such tunnels will also delete the related traffic access configuration. ◦ Main Tunnel: Tunnels that are configured to be protected.
Precautions • The Explicit Path Name, Device Name and Device LSR ID fields support fuzzy match. Add/modify explicit path This function helps you add/modify an explicit path. Only unbound explicit paths can be modified. For a bound explicit path, you can only view its detailed formation. Operation Procedure 1. 2. 3. 4. 5. Select the Service tab, and then click Explicit Path Management in the navigation tree to enter the explicit path management page.
Operation Procedure 1. 2. 3. Select the Service tab, and then click Explicit Path Management in the navigation tree to enter the explicit path management page. Select the explicit path(s) you want to delete and click Delete. Click OK on the pop-up dialog box. Precautions • Explicit paths that are in bound state cannot be deleted. Protection management The idea of protection is to use a bypass tunnel to avoid the invalid link or node, so as to protect the primary path.
Configure FRR node protection This function helps you configure FRR node protection. Operation Procedure 1. 2. 3. 4. 5. 6. Select the Service tab, and then click Protection Management in the navigation tree to enter the protection management page. Select a tunnel record, click the FRR Protection button to enter the FRR protection page. Select Node Protection from the Protection Type drop-down list. Click Next to enter the tunnel's node list page. Select a node record.
Cancel FRR link protection This function is used to cancel the protection relationship between a primary tunnel and its link protection backup tunnel. Operation Procedure 1. 2. 3. 4. 5. 6. Select the Service tab, and then click Protection Management in the navigation tree to enter the protection management page. Select a tunnel record, click the FRR Protection button to enter the FRR protection page. Select Link Protection from the Protection Type drop-down list.
Operation Procedure 1. 2. 3. 4. 5. Select the Service tab, and then click Traffic Access Mng in the navigation tree to enter the traffic access management page. Click Add to enter the traffic access configuration page. Click the Select button of the Device Name field to select the device for which you want to configure traffic access. Click the Select button of the Tunnel Name field to select the tunnel for traffic forwarding. Select a traffic access type from the Traffic Access Type drop-down list.
5 MPLS management MPLS management includes an overview, quick start instructions, typical application, and using MPLS management. MPLS management overview System overview iMC MPLS Management provides a comprehensive MPLS network management solution for metropolitan area networks. It can cooperate with H3C devices to manage MPLS networks. MPLS Management provides various functions, including device management, LDP management, LSP management, topology management, label statistics, and LSP traffic statistics.
Common operators in MPLS management include: • View device label statistics. • Highlight an LSP on the topology. MPLS management typical application Application scenario A corporation has two data centers, one primary and one backup. To connect the two data centers at Layer 2 using the MPLS technology, build an MPLS network based on the current network structure, and create a static LSP for label forwarding and label statistics.
3. 4. View label statistics. Select MPLS Management > Label Statistics from the navigation tree. On the page, you can view the top 5 devices by static labels used, top 5 devices by dynamic labels used, and device label usage percentage. For configuration procedures, see Label Statistics. View LSP traffic statistics. a. Select MPLS Management > LSP Traffic Statistics from the navigation tree. On the Default Threshold Settings page, set the alert thresholds for outgoing LSP traffic.
Precautions • Only the LSPs whose deployment status is Undeployed or Deployment failed can be directly deleted from the system. To delete LSPs in Normal and Undeployment failed status, you must first undeploy them. • For LSPs whose deployment status is Undeployed or Deployment failed, you can modify their configuration, delete them, or immediately deploy them to devices. • The deployment status of a successfully deployed LSP is Normal.
6 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
Prerequisites Prerequisites for [installing or using] this product include: • IMC v5.0 or higher installed and deployed on your enterprise network or lab environment Typographic conventions Table 1 Document conventions Convention Element Blue text: Table 1 (page 127) Cross-reference links and email addresses Blue, underlined text: http://www.hp.
Table 2 About the HP IMC documentation set (continued) Category Documents Purposes SQL Server 2005 Installation and Configuration Guide Guides you through installing SQL Server 2005 for IMC. SQL Server 2008 Installation and Configuration Guide Guides you through installing SQL Server 2008 for IMC. SQL Server 2008 R2 Installation Guides you through installing SQL Server 2008 R2 for IMC.
7 Icons and color coding This chapter includes a list of all device status color codes, synchronization and peer statuses, and label check results.
Table 7 Device icons (continued) Icon Device icon description CE MCE VMCE Table 8 Device sync status Icon Device sync status Synchronizing Synchronization failed! Table 9 Link deployment status Icon Link deployment status Deployed Not deployed Table 10 Link operation status Icon Link operation status Configuration changed Audit is running Link invalid Deployment failed or undeployment failed Deployment or undeployment is being processed Table 11 TE toplogy icons Icon TE topology Topology Filter Ta
Table 13 Resource management: Interface management icons Icon Interface management View available bandwidth Table 14 MPLS TE tunnel management icons Icon MPLS TE tunnel management Topology information Protection information 131
8 FAQ 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 132 FAQ What should I do if the configuration comparison result for a PE is Different Config? This result indicates that the L2VPN configuration maintained in IMC for a PE is different than the L2VPN configuration on the PE. If the configuration on the PE is trustworthy, you can use the auto discovery function of the L2VPN Manager to update IMC with the configuration on the PE.
There are three types of PEs that exist in a VPN: • Superstratum PEs (SPE) • Underlayer PEs (UPEs) • Middle-Level PEs (MPE) The following rules apply: 8.9 8.10 • If you import an SPE and a UPE, they exist as common PEs. • If you import an SPE and an MPE or import an MPE and a UPE, they exist as an SPE and a UPE respectively. • If you import an MPE when an SPE and a UPE exist, these three devices exist as SPE, MPE, and UPE respectively.
When you associate VPN with a PE interface, the interface automatically becomes down and generates a Down alarm. Therefore, the iMC considers this a failed link. • If you have configured a PE to send Traps to the iMC, the iMC displays the link as normal because it received an interface up alarm when the interface automatically becomes up.
8.25 8.26 8.27 8.28 8.29 8.30 8.31 8.32 8.33 When the networking scheme is Hub-Spoke, it is necessary to configure both hub and spoke nodes in order to discover valid links. 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.
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.
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.
LDP Label Distribution Protocol. It establishes virtual circuits by establishing point-to-point sessions between a pair of PEs. LDP Session LDP sessions are established between LSRs based on TCP connections and are used to exchange messages for label binding, label releasing, and error notification. Link Invalid If association lost or RT value change on a VPN link results in the link not belonging to the original VPN, MVM considers it invalid.
RSVP-TE RSVP Traffic Engineering extension protocol. RSVP-TE is an extension to the RSVP. It supports MPLS label distribution and allow resource reservation information to be transmitted with label bindings. It can be used as a signaling protocol for LSP tunnel setup in MPLS TE. SA Service Access, equals to a PE-CE link, indicating an access from a CE in the VPN. SC Service Community, basic element in constructing a VPN, including Full-Mesh and Hub-Spoke networking schemes.
Index C contacting HP, 126 conventions document, 127 text symbols, 127 D document conventions, 127 prerequisites, 127 documentation about the HP IMC set, 127 H help obtaining, 126 HP technical support, 126 P prerequisites, 127 S symbols in text, 127 T technical support HP, 126 text symbols, 127 typographic conventions, 127 140 Index
