H3C S12500-X Series Configuration Manual
  1. Manuals
  2. Brands
  3. H3C Manuals
  4. Switch
  5. S12500-X
  6. Configuration manual
H3C S12500-X Series Configuration Manual

H3C S12500-X Series Configuration Manual

Hide thumbs Also See for S12500-X Series:
Table of Contents

Advertisement

Quick Links

Download this manual
H3C S12500-X Switch Series
MCE
Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release 1109
Document version: 6W100-20141210

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the S12500-X Series and is the answer not in the manual?

Questions and answers

Related Manuals for H3C S12500-X Series

Summary of Contents for H3C S12500-X Series

  • Page 1 H3C S12500-X Switch Series Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Software version: Release 1109 Document version: 6W100-20141210...
  • Page 2 Copyright © 2014, 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 S12500-X documentation set includes 1 1 configuration guides. These guides describe the software features for the H3C S12500-X Switch Series running Release 1 109, and guide you through the software configuration procedures. These guides also provide configuration examples to help you apply software features to different network scenarios.
  • Page 4 Convention Description The argument or keyword and argument combination before the ampersand (&) sign can &<1-n> be entered 1 to n times. A line that starts with a pound (#) sign is comments. GUI conventions Convention Description Window names, button names, field names, and menu items are in Boldface. For Boldface example, the New User window appears;...
  • Page 5 Solutions]—Provides information about products and technologies, as well as solutions. [Technical Support & Documents > Software Download]—Provides the documentation released with the software version. 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 6: 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 7: Configuring Mce

    Configuring MCE This chapter describes MCE configuration. For information about the related routing protocols, see Layer IP Routing Configuration Guide. — Unless otherwise specified, the term "interface" in this document collectively refers to VLAN interfaces and Layer 3 Ethernet interfaces. You can set an Ethernet port as a Layer 3 interface by using the port link-mode route command (see Layer 2—LAN Switching Configuration Guide).

  • Page 8: Mpls L3Vpn Concepts

    Provider device—A P device is a core device on a service provider network. It is not directly • connected to any CE. A P device has only basic MPLS forwarding capability and does not handle VPN routing information. 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.

  • Page 9: Mce Overview

    Figure 2 VPN-IPv4 address structure Route Distinguisher (8 bytes) 2 bytes 6 bytes 4 bytes Type Administrator subfield Assigned number subfield IPv4 address prefix 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.

  • Page 10: Mce Configuration Task List

    can configure multiple VPNs to use the same CE and the same routing table, which sacrifices data security. You can use the Multi-VPN Instance CE (MCE) function in multi-VPN networks. MCE allows you to bind each VPN to a VLAN interface. The MCE creates and maintains a separate routing table for each VPN. This separates the forwarding paths of packets of different VPNs and, in conjunction with the PE, can correctly advertise the routes of each VPN to the peer PE, ensuring the normal transmission of VPN packets over the public network.

  • Page 11: Configuring Vpn Instances

    Tasks at a glance (Required.) Associating a VPN instance with an interface (Optional.) Configuring route related attributes for a VPN instance Configuring routing on an MCE: • (Required.) Configuring routing between an MCE and a VPN site • (Required.) Configuring routing between an MCE and a PE Configuring VPN instances VPN instances isolate VPN routes from public network routes and routes among VPNs.

  • Page 12: Configuring Route Related Attributes For A Vpn Instance

    Step Command Remarks By default, no VPN instance is associated with an interface. The ip binding vpn-instance Associate a VPN instance ip binding vpn-instance command deletes the IP address of with the interface. vpn-instance-name the current interface. You must re-configure an IP address for the interface after configuring the command.

  • Page 13: Configuring Routing On An Mce

    Step Command Remarks By default, all routes matching the import target attribute are accepted. Apply an import routing The specified routing policy must import route-policy route-policy policy. have been created. For information about routing policies, see Layer 3—IP Routing Configuration Guide. By default, routes to be advertised are not filtered.
  • Page 14 Step Command Remarks ip route-static vpn-instance s-vpn-instance-name By default, no static dest-address { mask-length | mask } { interface-type route is configured. interface-number [ next-hop-address ] | Perform this Configure a static route next-hop-address [ public ] [ track track-entry-number ] configuration on the for a VPN instance.
  • Page 15 VPN routes. loops. To avoid such routing loops, you can configure route tags for VPN instances on an MCE. H3C recommends that you configure the same route tag for the same VPN on the MCEs.
  • Page 16 Step Command Remarks Create an OSPF area and By default, no OSPF area is area area-id enter OSPF area view. created. 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.
  • Page 17 Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter BGP-VPN instance ip vpn-instance vpn-instance-name view. Configure an EBGP peer { group-name | ip-address } By default, no BGP peer is peer. as-number as-number configured. Enter BGP-VPN IPv4 unicast address family address-family ipv4 [ unicast ] view.
  • Page 18 Step Command Remarks Enter BGP-VPN IPv4 unicast address family address-family ipv4 [ unicast ] view. Enable BGP to exchange peer { group-name | By default, BGP does not exchange IPv4 unicast routes with ip-address } enable IPv4 unicast routes with any peer. the peer.

  • Page 19: Configuring Routing Between An Mce And A Pe

    Step Command Remarks (Optional.) Configure filter-policy { acl-number | By default, BGP does not filter filtering of advertised prefix-list prefix-list-name } advertised routes. routes. export [ protocol process-id ] filter-policy { acl-number | (Optional.) Configure By default, BGP does not filter prefix-list prefix-list-name } filtering of received routes.
  • Page 20 Step Command Remarks ip route-static vpn-instance s-vpn-instance-name dest-address { mask-length | mask } { interface-type interface-number [ next-hop-address ] | next-hop-address [ public ] [ track Configure a static route By default, no static track-entry-number ] | vpn-instance for a VPN instance. route is configured.
  • Page 21 VPN routes. loops. To avoid such routing loops, you can configure route tags for VPN instances on an MCE. H3C recommends that you configure the same route tag for the same VPN on the MCEs.
  • Page 22 Step Command Remarks Create an IS-IS process isis [ process-id ] vpn-instance for a VPN instance and vpn-instance-name enter IS-IS view. Configure a network network-entity net By default, no NET is configured. entity title. By default, IS-IS does not redistribute routes from any other import-route protocol [ process-id | routing protocol.

  • Page 23: Displaying And Maintaining Mce

    Configuring IBGP between an MCE and a PE Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number Enter BGP-VPN instance ip vpn-instance vpn-instance-name view. Configure the PE as an peer { group-name | ip-address } as-number IBGP peer. as-number Enter BGP-VPN IPv4 unicast address family...

  • Page 24: Mce Configuration Examples

    MCE configuration examples Configuring the MCE that uses OSPF to advertise VPN routes to the PE Network requirements As shown in Figure 4, the MCE device is connected to VPN 1 through VLAN-interface 10 and is connected with VPN 2 through VLAN-interface 20. RIP runs in VPN 2. Configure the MCE device to separate routes from different VPNs and to advertise the VPN routes to PE 1 through OSPF.
  • Page 25 [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 Ten-GigabitEthernet 1/0/1 to VLAN 10, and create VLAN-interface 10. [MCE] vlan 10 [MCE-vlan10] port ten-gigabitethernet 1/0/1 [MCE-vlan10] quit # Bind VLAN-interface 10 with VPN instance vpn1, and configure an IP address for VLAN-interface 10.
  • Page 26 # On the MCE, display the routing information maintained for VPN instance vpn1. [MCE] display ip routing-table vpn-instance vpn1 Destinations : 13 Routes : 13 Destination/Mask Proto Cost NextHop Interface 0.0.0.0/32 Direct 0 127.0.0.1 InLoop0 10.214.10.0/24 Direct 0 10.214.10.3 Vlan10 10.214.10.0/32 Direct 0 10.214.10.3...
  • Page 27 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 InLoop0 127.255.255.255/32 Direct 0 127.0.0.1 InLoop0 192.168.10.0/24 OSPF 10.214.20.2 Vlan20 224.0.0.0/4 Direct 0 0.0.0.0 NULL0...
  • Page 28 [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 vpn2, and configure an IP address for the VLAN interface. [PE1] vlan 40 [PE1-vlan40] quit [PE1] interface vlan-interface 40...

  • Page 29: Configuring The Mce That Uses Ebgp To Advertise Vpn Routes To The Pe

    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 InLoop0 192.168.0.0/24 OSPF 30.1.1.1 Vlan30 224.0.0.0/4 Direct 0 0.0.0.0 NULL0 224.0.0.0/24 Direct 0 0.0.0.0 NULL0 255.255.255.255/32 Direct 0 127.0.0.1 InLoop0...
  • Page 30 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 31 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 32 [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 33 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 34: Index

    Index MPLS L3VPN MCE-VPN site RIP, MPLS L3VPN MCE-VPN site routing, address MPLS L3VPN MCE-VPN site static routing, MPLS L3VPN address space overlapping, MPLS L3VPN VPN instance, architecture MPLS L3VPN VPN instance route related attribute, MPLS L3VPN, creating associating MPLS L3VPN VPN instance, MPLS L3VPN VPN instance with interface, customer edge device.
  • Page 35 MPLS L3VPN VPN-IPv4 address, MCE-PE static routing configuration, IS-IS MCE-VPN site configuration, MPLS L3VPN MCE-PE IS-IS configuration, MCE-VPN site EBGP configuration, MPLS L3VPN MCE-VPN site IS-IS MCE-VPN site IBGP configuration, configuration, MCE-VPN site IS-IS configuration, MCE-VPN site OSPF configuration, MCE-VPN site RIP configuration, maintaining MCE-VPN site routing configuration, MCE,...
  • Page 36 MPLS L3VPN VPN instance route related configuring MPLS L3VPN MCE-PE static routing, attribute configuration, configuring MPLS L3VPN MCE-VPN site, MPLS L3VPN VPN-IPv4 address, configuring MPLS L3VPN MCE-VPN site EBGP, VPN instance (MPLS L3VPN), configuring MPLS L3VPN MCE-VPN site IBGP, network management configuring MPLS L3VPN MCE-VPN site IS-IS, MCE configuration, configuring MPLS L3VPN MCE-VPN site OSPF,...
  • Page 37 MPLS L3VPN MCE-VPN site RIP configuration, MPLS L3VPN MCE-VPN site routing configuration, MPLS L3VPN MCE-VPN site static routing configuration, site MPLS L3VPN, static MPLS L3VPN MCE-PE static routing configuration, MPLS L3VPN MCE-VPN site static routing configuration, instance (MPLS L3VPN), MPLS L3VPN VPN-IPv4 address,...

Table of Contents