H3C S6800 Series Configuration Manual
H3C S6800 Series Configuration Manual

H3C S6800 Series Configuration Manual

Mce configuration guide
Hide thumbs Also See for S6800 Series:

Advertisement

Quick Links

H3C S6800 Switch Series
MCE Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release 2407
Document version: 6W100-20131205

Advertisement

Table of Contents
loading

Summary of Contents for H3C S6800 Series

  • Page 1 H3C S6800 Switch Series MCE Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Software version: Release 2407 Document version: 6W100-20131205...
  • Page 2 Copyright © 2013, Hangzhou H3C Technologies Co., Ltd. and its licensors All rights reserved No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Hangzhou H3C Technologies Co., Ltd.
  • Page 3 The H3C S6800 documentation set includes 9 configuration guides, which describe the software features for the H3C S6800 Switch Series and guide you through the software configuration procedures. These configuration guides also provide configuration examples to help you apply software features to different network scenarios.
  • Page 4 Convention Description Asterisk marked square brackets enclose optional syntax choices separated by vertical [ x | y | ... ] * bars, from which you select one choice, multiple choices, or none. The argument or keyword and argument combination before the ampersand (&) sign can &<1-n>...
  • Page 5 Release notes software upgrading. Obtaining documentation You can access the most up-to-date H3C product documentation on the World Wide Web at http://www.h3c.com. Click the links on the top navigation bar to obtain different categories of product documentation: [Technical Support & Documents > Technical Documents]—Provides hardware installation, software...
  • Page 6 Technical support service@h3c.com http://www.h3c.com Documentation feedback You can e-mail your comments about product documentation to info@h3c.com. We appreciate your comments.
  • Page 7: Table Of Contents

    Contents Configuring MCE ························································································································································· 1   MPLS L3VPN overview ····················································································································································· 1   Basic MPLS L3VPN architecture ······························································································································ 1   MPLS L3VPN concepts ············································································································································· 2   MCE overview ··································································································································································· 3   MCE configuration task list ·············································································································································· 4   Configuring VPN instances ·············································································································································· 5  ...
  • Page 8: Configuring Mce

    Configuring MCE This chapter describes MCE configuration. For information about the related routing protocols, see Layer IP Routing Configuration Guide. — MPLS L3VPN overview MPLS L3VPN is a L3VPN technology used to interconnect geographically dispersed VPN sites. MPLS L3VPN uses BGP to advertise VPN routes and uses MPLS to forward VPN packets over a service provider backbone.
  • Page 9: Mpls L3Vpn Concepts

    MPLS L3VPN concepts Site A site has the following features: • A site is a group of IP systems with IP connectivity that does not rely on any service provider network. The classification of a site depends on the topology relationship of the devices, rather than the •...
  • Page 10: Mce Overview

    As shown in Figure 2, a VPN-IPv4 address consists of 12 bytes. The first eight bytes represent the RD, followed by a four-byte IPv4 prefix. The RD and the IPv4 prefix form a unique VPN-IPv4 prefix. An RD can be in one of the following formats: When the Type field is 0, the Administrator subfield occupies two bytes, the Assigned number •...
  • Page 11: Mce Configuration Task List

    Figure 3 Network diagram for the MCE function As shown in Figure 3, the MCE device creates a routing table for each VPN. VLAN interface 2 binds to VPN 1 and VLAN-interface 3 binds to VPN 2. When receiving a route, the MCE device determines the source of the routing information according to the number of the receiving interface, and then adds it to the corresponding routing table.
  • Page 12: Configuring Vpn Instances

    Configuring VPN instances VPN instances isolate VPN routes from public network routes and routes among VPNs. You must configure VPN instances for an MCE network. Creating a VPN instance A VPN instance is a collection of the VPN membership and routing rules of its associated site. A VPN instance may not correspond to one VPN.
  • Page 13: Configuring Route Related Attributes For A Vpn Instance

    Configuring route related attributes for a VPN instance VPN routes are controlled and advertised on a PE by using the following process: When a VPN route learned from a site gets redistributed into BGP, BGP associates it with a route target extended community attribute list, which is usually the export target attribute of the VPN instance associated with the site.
  • Page 14: Configuring Routing On An Mce

    Configuring routing on an MCE MCE implements service isolation through route isolation. MCE routing configuration includes the following: MCE-VPN site routing configuration • MCE-PE routing configuration • On the PE, disable routing loop detection to avoid route loss during route calculation, and disable route redistribution between routing protocols to save system resources.
  • Page 15 Step Command Remarks Enter system view. system-view Perform this configuration on the MCE. On a VPN site, create a common OSPF process. An OSPF process bound to a VPN instance does not use the public Create an OSPF process for a ospf [ process-id | router-id network router ID configured in VPN instance and enter OSPF...
  • Page 16 Step Command Remarks By default, OSPF does not redistribute the default route. (Optional.) Configure OSPF default-route-advertise summary This command redistributes the to redistribute the default cost cost default route in a Type-3 LSA. The route. MCE advertises the default route to the site.
  • Page 17 Step Command Remarks By default, BGP discards incoming route updates that contain the local AS number. BGP detects routing loops by examining AS numbers. The Allow the local AS number routing information the MCE to appear in the AS_PATH advertises to a site carries the attribute of routes received peer { group-name | ip-address } local AS number.
  • Page 18 Configure the MCE: Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter BGP-VPN instance ip vpn-instance view. vpn-instance-name peer { group-name | ip-address } Configure an IBGP peer. as-number as-number Enter BGP-VPN IPv4 unicast address-family ipv4 [ unicast ] address family view.
  • Page 19: Configuring Routing Between An Mce And A Pe

    Step Command Remarks Enable BGP to exchange By default, BGP does not peer { group-name | ip-address } IPv4 unicast routes with the exchange IPv4 unicast routes enable peer. with any peer. By default, no routes are import-route protocol redistributed into BGP. [ { process-id | all-processes } Redistribute the IGP routes [ allow-direct | med med-value |...
  • Page 20 Step Command Remarks By default, routing loop detection is enabled. You must disable routing loop Disable routing loop vpn-instance-capability simple detection for a VPN OSPF process detection. on the MCE. Otherwise, the MCE cannot receive OSPF routes from the PE. (Optional.) Configure the domain-id domain-id [ secondary ] The default domain ID is 0.
  • Page 21: Displaying And Maintaining Mce

    Step Command Remarks Enable OSPF on the interface By default, an interface neither attached to the specified network ip-address wildcard-mask belongs to any area nor runs network in the area. OSPF. Configuring EBGP between an MCE and a PE Step Command Remarks Enter system view.
  • Page 22: Mce Configuration Examples

    For other MCE related displaying and maintaining commands, such as displaying routing table information for a VPN instance and maintaining routing sessions for a VPN instance, see Layer 3—IP Routing Command Reference. MCE configuration examples Configuring the MCE that uses OSPF to advertise VPN routes to the PE Network requirements As shown in...
  • Page 23 <MCE> system-view [MCE] ip vpn-instance vpn1 [MCE-vpn-instance-vpn1] route-distinguisher 10:1 [MCE-vpn-instance-vpn1] vpn-target 10:1 [MCE-vpn-instance-vpn1] quit [MCE] ip vpn-instance vpn2 [MCE-vpn-instance-vpn2] route-distinguisher 20:1 [MCE-vpn-instance-vpn2] vpn-target 20:1 [MCE-vpn-instance-vpn2] quit # Create VLAN 10, add port FortyGigE 1/0/1 to VLAN 10, and create VLAN-interface 10. [MCE] vlan 10 [MCE-vlan10] port fortygige 1/0/1 [MCE-vlan10] quit...
  • Page 24 [VR1] ip route-static 0.0.0.0 0.0.0.0 10.214.10.3 # On the MCE, configure a static route to 192.168.0.0/24, specify the next hop as 10.214.10.2, and bind the static route with VPN instance vpn1. [MCE] ip route-static vpn-instance vpn1 192.168.0.0 24 10.214.10.2 # On the MCE, display the routing information maintained for VPN instance vpn1. [MCE] display ip routing-table vpn-instance vpn1 Destinations : 13 Routes : 13...
  • Page 25 Destination/Mask Proto Cost NextHop Interface 0.0.0.0/32 Direct 0 127.0.0.1 InLoop0 10.214.20.0/24 Direct 0 10.214.20.3 Vlan20 10.214.20.0/32 Direct 0 10.214.20.3 Vlan20 10.214.20.3/32 Direct 0 127.0.0.1 InLoop0 10.214.20.255/32 Direct 0 10.214.20.3 Vlan20 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.0/32 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1...
  • Page 26 # On PE 1, create VLAN 30 and VLAN-interface 30, bind the VLAN interface with VPN instance vpn1, and configure an IP address for the VLAN interface. [PE1] vlan 30 [PE1-vlan30] quit [PE1] interface vlan-interface 30 [PE1-Vlan-interface30] ip binding vpn-instance vpn1 [PE1-Vlan-interface30] ip address 30.1.1.2 24 [PE1-Vlan-interface30] quit # On PE 1, create VLAN 40 and VLAN-interface 40, bind the VLAN interface with VPN instance...
  • Page 27: Configuring The Mce That Uses Ebgp To Advertise Vpn Routes To The Pe

    0.0.0.0/32 Direct 0 127.0.0.1 InLoop0 30.1.1.0/24 Direct 0 30.1.1.2 Vlan30 30.1.1.0/32 Direct 0 30.1.1.2 Vlan30 30.1.1.2/32 Direct 0 127.0.0.1 InLoop0 30.1.1.255/32 Direct 0 30.1.1.2 Vlan30 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.0/32 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 127.255.255.255/32 Direct 0 127.0.0.1...
  • Page 28 Figure 5 Network diagram Configuration procedure Create VPN instances on the MCE and PE 1, and bind the VPN instances with VLAN interfaces. For the configuration procedure, see "Configure the VPN instances on the MCE and PE 1:." Configure routing between the MCE and VPN sites: # Enable an OSPF process on the devices in the two VPNs, and advertise the subnets.
  • Page 29 10.214.10.0/32 Direct 0 10.214.10.3 Vlan10 10.214.10.3/32 Direct 0 127.0.0.1 InLoop0 10.214.10.255/32 Direct 0 10.214.10.3 Vlan10 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.0/32 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 127.255.255.255/32 Direct 0 127.0.0.1 InLoop0 192.168.0.0/24 OSPF 10.214.10.2 Vlan10 224.0.0.0/4 Direct 0 0.0.0.0 NULL0...
  • Page 30 [PE1] bgp 200 [PE1-bgp] ip vpn-instance vpn1 [PE1-bgp-vpn1] peer 30.1.1.1 as-number 100 [PE1-bgp-vpn1] address-family ipv4 [PE1-bgp-ipv4-vpn1] peer 30.1.1.1 enable [PE1-bgp-ipv4-vpn1] quit [PE1-bgp-vpn1] quit [PE1-bgp] quit # Use similar procedures to configure VPN 2 settings on MCE and PE 1. (Details not shown.) Verifying the configuration # Display the routing information for VPN 1 on PE 1.
  • Page 31 255.255.255.255/32 Direct 0 127.0.0.1 InLoop0 Now, the MCE has redistributed the OSPF routes of the two VPN instances into the EBGP routing tables of PE 1.
  • Page 32: Configuring Ipv6 Mce

    Configuring IPv6 MCE This chapter describes IPv6 MCE configuration. Overview In MPLS L3VPN networks, MCE uses static routes or dynamic routing protocols to advertise IPv4 routes between internal networks and PEs and forwards IPv4 packets. In IPv6 MPLS L3VPN networks, IPv6 MCE uses IPv6 static routes and dynamic routing protocols to advertise IPv6 routes between internal networks and PEs and forwards IPv6 packets.
  • Page 33: Associating A Vpn Instance With An Interface

    Step Command Remarks By default, no description is configured for a VPN instance. (Optional.) Configure a The description should contain the description for the VPN description text VPN instance's related instance. information, such as its relationship with a certain VPN. (Optional.) Configure an ID By default, no ID is configured for a vpn-id vpn-id...
  • Page 34: Configuring Routing On An Mce

    Step Command Remarks Configurations made in VPN • Enter VPN instance view: instance view apply to both IPv4 ip vpn-instance VPN and IPv6 VPN. Enter VPN instance view or vpn-instance-name IPv6 VPN prefers the IPv6 VPN view. • Enter IPv6 VPN view: configurations in IPv6 VPN view address-family ipv6 over the configurations in VPN...
  • Page 35: Configuring Routing Between An Mce And A Vpn Site

    On the MCE, configure VPN instances, and bind the VPN instances with the interfaces connected • to the VPN sites and those connected to the PE. Configure the link layer and network layer protocols on related interfaces to ensure IP connectivity. •...
  • Page 36 Step Command Remarks import-route protocol [ process-id | all-processes | allow-ibgp ] Redistribute remote site routes By default, no routes are [ allow-direct | cost cost | advertised by the PE. redistributed into OSPFv3. route-policy route-policy-name | type type ] * Return to system view.
  • Page 37 Step Command Remarks Enter BGP view. bgp as-number peer { group-name | Configure the MCE as an By default, no BGP peer is ipv6-address } as-number EBGP peer. configured. as-number Enter BGP IPv6 unicast address-family ipv6 [ unicast ] address family view. Enable BGP to exchange By default, BGP does not peer { group-name | ip-address }...
  • Page 38: Configuring Routing Between An Mce And A Pe

    Step Command Remarks import-route protocol Redistribute remote site [ process-id [ allow-direct | med By default, no routes are routes advertised by the PE med-value | route-policy redistributed into BGP. into BGP. route-policy-name ] * ] filter-policy { acl6-number | (Optional.) Configure By default, BGP does not filter prefix-list ipv6-prefix-name }...
  • Page 39 Step Command Remarks ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length { interface-type Configure an IPv6 static By default, no IPv6 interface-number [ next-hop-address ] | route for an IPv6 VPN nexthop-address [ public ] | vpn-instance static route is instance. d-vpn-instance-name nexthop-address } [ permanent ] configured.
  • Page 40: Displaying And Maintaining Ipv6 Mce

    Step Command Remarks Enable BGP to exchange IPv6 peer { group-name | ip-address } By default, BGP does not exchange unicast routes with the enable IPv6 unicast routes with any peer. specified peer. import-route protocol [ process-id By default, no routes are Redistribute VPN routes.
  • Page 41 Figure 6 Network diagram VPN 2 Site 1 PE 2 PE 1 FGE1/0/1 Vlan-int30: 30::2/64 Vlan-int40: 40::2/64 PE 3 Vlan-int10 VPN 1 FGE1/0/3 VPN 1 2001:1::2/64 Site 2 Vlan-int30: 30::1/64 2012:1::/64 FGE1/0/1 Vlan-int11 Vlan-int40: 40::1/64 Vlan-int10 FGE1/0/2 2012:1::2/64 VR 1 2001:1::1/64 Vlan-int20 2002:1::1/64...
  • Page 42 # Bind VLAN-interface 10 with VPN instance vpn1, and configure an IPv6 address for the VLAN interface. [MCE] interface vlan-interface 10 [MCE-Vlan-interface10] ip binding vpn-instance vpn1 [MCE-Vlan-interface10] ipv6 address 2001:1::1 64 [MCE-Vlan-interface10] quit # Configure VLAN 20, add port FortyGigE 1/0/2 to VLAN 20, bind VLAN-interface 20 with VPN instance vpn2, and assign an IPv6 address to VLAN-interface 20.
  • Page 43 [MCE-Vlan-interface20] ospfv3 30 area 0.0.0.0 [MCE-Vlan-interface20] quit # On VR 2, assign IPv6 address 2002:1::2/64 to the interface connected to the MCE, 2012::2/64 to the interface connected to VPN 2, and 102.102.10.1 to Loopback 0. (Details not shown.) # Enable OSPFv3 process 30, and enable OSPFv3 on VLAN-interface 20 and VLAN-interface 21. <VR2>...
  • Page 44 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 2002:1::/64 Protocol : Direct NextHop : :: Preference: 0 Interface : Vlan20 Cost Destination: 2002:1::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 2012::/64 Protocol...
  • Page 45 # On the MCE, create VLAN 40 and VLAN-interface 40, bind VLAN-interface 40 with VPN instance vpn2, and configure an IPv6 address for the VLAN-interface 40. [MCE] vlan 40 [MCE-vlan40] quit [MCE] interface vlan-interface 40 [MCE-Vlan-interface40] ip binding vpn-instance vpn2 [MCE-Vlan-interface40] ipv6 address 40::1 64 [MCE-Vlan-interface40] quit # On PE 1, create VLAN 30 and VLAN-interface 30, bind VLAN-interface 30 with VPN instance...
  • Page 46 Verifying the configuration # Display the routing table for VPN instance vpn1. The output shows that PE 1 has learned the private route of VPN 1 through OSPFv3. [PE1] display ipv6 routing-table vpn-instance vpn1 Destinations : 6 Routes : 6 Destination: ::1/128 Protocol : Direct...
  • Page 47 Destination: 2012::/64 Protocol : OSPFv3 NextHop : FE80::200:FF:FE0F:5 Preference: 150 Interface : Vlan40 Cost Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost Destination: FF00::/8 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost Now, the routing information for the two VPNs has been added into the routing tables on PE 1.
  • Page 48: Index

    Index IPv6 MPLS L3VPN MCE-VPN site routing, IPv6 MPLS L3VPN MCE-VPN site static routing, address IPv6 MPLS L3VPN VPN instance, MPLS L3VPN address space overlapping, IPv6 MPLS L3VPN VPN instance route related architecture attributes, MPLS L3VPN, MCE, associating MPLS L3VPN MCE, IPv6 MPLS L3VPN VPN instance with MPLS L3VPN MCE routing, interface,...
  • Page 49 MPLS L3VPN MCE-VPN site configuration, MCE-PE configuration, provider device. See P MCE-PE EBGP configuration, provider edge device. See MCE-PE IPv6 static routing configuration, displaying MCE-PE OSPFv3 configuration, IPv6 MCE, MCE-VPN site EBGP configuration, MCE, MCE-VPN site IBGP configuration, MCE-VPN site OSPFv3 configuration, MCE-VPN site routing configuration, EBGP MCE-VPN site static routing configuration,...
  • Page 50 MCE-VPN site routing configuration, IPv6 MPLS L3VPN MCE-VPN site EBGP configuration, MCE-VPN site static routing configuration, IPv6 MPLS L3VPN MCE-VPN site IBGP MPLS L3VPN MCE-PE configuration, configuration, MPLS L3VPN MCE-VPN site configuration, IPv6 MPLS L3VPN MCE-VPN site OSPFv3 multi-VPN instance, 1, configuration, routing configuration, IPv6 MPLS L3VPN MCE-VPN site routing...
  • Page 51 MPLS L3VPN MCE-PE configuration, associating IPv6 MPLS L3VPN VPN instance with interface, MPLS L3VPN MCE-VPN site configuration, associating MPLS L3VPN VPN instance with interface, OSPF configuring IPv6 MCE, MPLS L3VPN MCE-PE OSPF configuration, configuring IPv6 MPLS L3VPN MCE routing, MPLS L3VPN MCE-VPN site configuration, configuring IPv6 MPLS L3VPN MCE-PE, MPLS L3VPN MCE-VPN site OSPF configuring IPv6 MPLS L3VPN MCE-PE EBGP,...
  • Page 52 maintaining MCE, IPv6 MPLS L3VPN VPN instance route related attributes, provider MCE configuration, device. See P MPLS L3VPN BGP route target attributes, edge device. See MPLS L3VPN MCE, 1, MPLS L3VPN MCE routing configuration, redistributing MPLS L3VPN MCE-PE configuration, IPv6 MPLS L3VPN MCE-PE configuration, MPLS L3VPN MCE-PE EBGP configuration, IPv6 MPLS L3VPN MCE-PE EBGP MPLS L3VPN MCE-PE OSPF configuration,...

Table of Contents