H3C S6300 Series Configuration Manual
  1. Manuals
  2. Brands
  3. H3C Manuals
  4. Switch
  5. S6300 Series
  6. Configuration manual
H3C S6300 Series Configuration Manual

H3C S6300 Series Configuration Manual

Hide thumbs Also See for S6300 Series:
Table of Contents

Advertisement

Quick Links

Download this manual
H3C S6300 Switch Series
MCE
Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: 6W100-20160323
Document version: Release 2422P01

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the S6300 Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for H3C S6300 Series

Summary of Contents for H3C S6300 Series

  • Page 1 H3C S6300 Switch Series Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Software version: 6W100-20160323 Document version: Release 2422P01...
  • Page 2 , H3CS, H3CIE, H3CNE, Aolynk, Care, , IRF, NetPilot, Netflow, SecEngine, SecPath, SecCenter, SecBlade, Comware, ITCMM and HUASAN are trademarks of Hangzhou H3C Technologies Co., Ltd. All other trademarks that may be mentioned in this manual are the property of their respective owners Notice The information in this document is subject to change without notice.
  • Page 3 Preface The H3C S6300 documentation set describes the software features for the H3C S6300 Switch Series 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 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; click OK. Multi-level menus are separated by angle brackets. For example, File > Create > >...
  • Page 5 Provide information about the product release, Operations and including the version history, hardware and maintenance Release notes software compatibility matrix, version upgrade information, technical support information, and software upgrading. Obtaining documentation Access the most up-to-date H3C product documentation on the World Wide Web at http://www.h3c.com.
  • Page 6 [Products & Solutions]—Provides information about products and technologies, as well as solutions. [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 7: Table Of Contents

    Contents Configuring MCE ····························································································· 1     MPLS L3VPN overview ······································································································································ 1   Basic MPLS L3VPN architecture ··············································································································· 1   MPLS L3VPN concepts ······························································································································ 1   MCE overview ···················································································································································· 3   MCE configuration task list ································································································································ 4   Configuring VPN instances ································································································································ 4  ...

  • Page 8: Configuring Mce

    Configuring MCE This chapter describes MCE configuration. For information about the related routing protocols, see — Layer 3 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 • 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 geographical positions. However, the devices at a site are, in most cases, adjacent to each other geographically.

  • Page 10: Mce Overview

    • When the Type field is 1, the Administrator subfield occupies four bytes, the Assigned number subfield occupies two bytes, and the RD format is 32-bit IPv4 address:16-bit user-defined number. For example, 172.1.1.1:1. • When the Type field is 2, the Administrator subfield occupies four bytes, the Assigned number subfield occupies two bytes, and the RD format is 32-bit AS number:16-bit user-defined number, where the minimum value of the AS number is 65536.

  • Page 11: Mce Configuration Task List

    As shown in Figure 3, the MCE exchanges private routes with VPN sites and PE 1, and adds the private routes to the routing tables of corresponding VPN instances. • Route exchange between MCE and VPN site—Create VPN instances VPN 1 and VPN 2 on the MCE.

  • Page 12: Associating A Vpn Instance With An Interface

    Step Command Remarks description for the VPN configured for a VPN instance. instance. (Optional.) Configure a VPN By default, no VPN ID is vpn-id vpn-id ID for the VPN instance. configured for a VPN instance. Associating a VPN instance with an interface After creating and configuring a VPN instance, associate the VPN instance with the MCE's interface connected to the site and the interface connected to the PE.

  • Page 13: 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, do the following: • Disable routing loop detection to avoid route loss during route calculation. •...
  • Page 14 Step Command Remarks Enter system view. system-view Create a RIP process for a Perform this configuration on the rip [ process-id ] vpn-instance VPN instance and enter RIP MCE. On a VPN site, create a vpn-instance-name view. common RIP process. Enable RIP on the interface By default, RIP is disabled on an attached to the specified...
  • Page 15 Step Command Remarks When one MCE advertises the routes learned from BGP to the VPN, the other MCEs might learn the routes, resulting in routing loops. To avoid such routing loops, you can configure route tags for VPN instances on an MCE.
  • Page 16 Step Command Remarks Enable the IS-IS process on isis enable [ process-id ] By default, IS-IS is disabled. the interface. Configuring EBGP between an MCE and a VPN site To run EBGP between an MCE and a VPN site, you must configure a BGP peer for each VPN instance on the MCE, and redistribute the IGP routes of each VPN instance on the VPN site.
  • Page 17 Step Command Remarks Enter BGP IPv4 unicast address-family ipv4 [ unicast ] address family view. Enable BGP to exchange By default, BGP does not peer { group-name | ip-address IPv4 unicast routes with the exchange IPv4 unicast routes [ mask-length ] } enable peer.

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

    Configure a VPN site: Step Command Remarks Enter system view. system-view Enter BGP view. bgp as-number peer { group-name | ip-address Configure the MCE as an [ mask-length ] } as-number IBGP peer. as-number Enter BGP IPv4 unicast address-family ipv4 [ unicast ] address family view.
  • Page 19 Configuring RIP between an MCE and a PE Step Command Remarks Enter system view. system-view Create a RIP process rip [ process-id ] vpn-instance for a VPN instance and vpn-instance-name enter RIP view. Enable RIP on the By default, RIP is disabled on interface attached to network network-address an interface.
  • Page 20 Step Command Remarks nssa-only | tag tag | type type ] * By default, OSPF does not redistribute the default route. (Optional.) Configure OSPF default-route-advertise This command redistributes the to redistribute the default summary cost cost default route in a Type-3 LSA. The route.

  • Page 21: Displaying And Maintaining Mce

    Step Command Remarks Enter BGP-VPN ip vpn-instance vpn-instance-name instance view. Configure the PE as an peer { group-name | ip-address EBGP peer. [ mask-length ] } as-number as-number Enter BGP-VPN IPv4 unicast address family address-family ipv4 [ unicast ] view. Enable BGP to By default, BGP does not peer { group-name | ip-address...

  • Page 22: Mce Configuration Examples

    Task Command Display information about a specified or display ip vpn-instance [ instance-name vpn-instance-name ] all VPN instances. Display BGP peer group information for display bgp group ipv4 [ unicast ] vpn-instance a VPN instance. vpn-instance-name [ group-name group-name ] display bgp peer ipv4 [ unicast ] vpn-instance Display BGP peer information for a VPN vpn-instance-name [ ip-address mask-length | { ip-address |...
  • Page 23 Figure 4 Network diagram Configuration procedure Assume that the system name of the MCE device is MCE, the system names of the edge devices of VPN 1 and VPN 2 are VR1 and VR2, respectively, and the system name of PE 1 is PE1. Configure the VPN instances on the MCE and PE 1: # On the MCE, configure VPN instances vpn1 and vpn2, and specify an RD and route targets for each VPN instance.
  • Page 24 [MCE-Vlan-interface10] quit # Configure VLAN 20, add port Ten-GigabitEthernet 1/0/2 to VLAN 20. [MCE] vlan 20 [MCE-vlan20] port ten-gigabitethernet 1/0/2 [MCE-vlan20] quit # Bind VLAN-interface 20 to VPN instance vpn2. [MCE] interface vlan-interface 20 [MCE-Vlan-interface20] ip binding vpn-instance vpn2 # Specify an IP address for VLAN-interface 20. [MCE-Vlan-interface20] ip address 10.214.20.3 24 [MCE-Vlan-interface20] quit # On PE 1, configure VPN instances vpn1 and vpn2, and specify an RD and route targets for...
  • Page 25 127.255.255.255/32 Direct 0 127.0.0.1 InLoop0 192.168.0.0/24 Static 60 10.214.10.2 Vlan10 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 The output shows that the MCE has a static route for VPN instance vpn1. # Run OSPF in VPN 2. Create OSPF process 20 and bind it to VPN instance vpn2 on the MCE, so that the MCE can learn the routes of VPN 2 and add them to the routing table of the VPN instance vpn2.
  • Page 26 # The MCE uses port Ten-GigabitEthernet 1/0/3 to connect to PE's port Ten-GigabitEthernet 1/0/1. Configure the two ports as trunk ports, and configure them to permit packets carrying VLAN tags 30 and 40 to pass. [MCE] interface ten-gigabitethernet 1/0/3 [MCE-Ten-GigabitEthernet1/0/3] port link-type trunk [MCE-Ten-GigabitEthernet1/0/3] port trunk permit vlan 30 40 [MCE-Ten-GigabitEthernet1/0/3] quit # Configure port Ten-GigabitEthernet 1/0/1 on the PE.
  • Page 27 # Disable OSPF routing loop detection. [MCE-ospf-10] vpn-instance-capability simple # Set the domain ID to 10. [MCE-ospf-10] domain-id 10 # On the MCE, advertise subnet 30.1.1.0 in area 0, and redistribute the static route of VPN 1. [MCE-ospf-10] area 0 [MCE-ospf-10-area-0.0.0.0] network 30.1.1.0 0.0.0.255 [MCE-ospf-10-area-0.0.0.0] quit [MCE-ospf-10] import-route static...

  • Page 28: 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 40.1.1.0/24 Direct 0 40.1.1.2 Vlan40 40.1.1.0/32 Direct 0 40.1.1.2 Vlan40 40.1.1.2/32 Direct 0 127.0.0.1 InLoop0 40.1.1.255/32 Direct 0 40.1.1.2 Vlan40 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 29 Configuration procedure Create VPN instances on the MCE and PE 1, and bind the VPN instances to 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 30 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 224.0.0.0/24 Direct 0 0.0.0.0 NULL0 255.255.255.255/32 Direct 0 127.0.0.1 InLoop0 Configure routing between the MCE and PE 1: # Configure the ports between the MCE and PE 1 as trunk ports.
  • Page 31 127.255.255.255/32 Direct 0 127.0.0.1 InLoop0 192.168.0.0/24 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 # Display the routing information for VPN 2 on PE 1. [PE1] display ip routing-table vpn-instance vpn2 Destinations : 13 Routes : 13 Destination/Mask...

  • 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 relationship with a certain VPN. (Optional.) Configure an ID By default, no ID is configured for vpn-id vpn-id for the VPN instance. a VPN instance. Associating a VPN instance with an interface After creating and configuring a VPN instance, associate the VPN instance with the MCE's interface connected to the site and the interface connected to the PE.

  • Page 34: Configuring Routing On An Mce

    Step Command Remarks By default, the maximum number of active routes for the VPN instance is not limited. Set the maximum number of routing-table limit number Setting the maximum number of active routes supported. { warn-threshold | simply-alert } active routes for a VPN instance can prevent the PE from storing too many routes.
  • Page 35 configuring RIPng process-to-IPv6 VPN instance bindings on a MCE, you allow routes of different VPNs to be exchanged between the MCE and the sites through different RIPng processes, ensuring the separation and security of IPv6 VPN routes. For more information about RIPng, see Layer 3—IP Routing Configuration Guide. To configure RIPng between an MCE and a VPN site: Step Command...
  • Page 36 Step Command Remarks import-route protocol Redistribute remote site [ process-id | all-processes | By default, no routes are routes advertised by the PE. allow-ibgp ] [ cost cost | redistributed into OSPFv3. nssa-only | tag tag | type type ] * Return to system view.
  • Page 37 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 | Specify an IPv6 BGP peer By default, no BGP peer is ipv6-address [ prefix-length ] } in an AS. configured.
  • Page 38 Step Command Remarks Enter BGP view. bgp as-number Enter BGP-VPN instance ip vpn-instance view. vpn-instance-name peer { group-name | Configure an IBGP peer. ipv6-address [ prefix-length ] } as-number as-number Enter BGP-VPN IPv6 unicast address family address-family ipv6 [ unicast ] view.

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

    Configuring routing between an MCE and a PE MCE-PE routing configuration includes these tasks: • Binding the MCE-PE interfaces to IPv6 VPN instances. • Performing routing configurations. • Redistributing IPv6 VPN routes into the routing protocol running between the MCE and the PE. Perform the following configuration tasks on the MCE.
  • Page 40 Configuring OSPFv3 between an MCE and a PE Step Command Remarks Enter system view. system-view Create an OSPFv3 process ospfv3 [ process-id | for an IPv6 VPN instance vpn-instance and enter OSPFv3 view. vpn-instance-name ] * Set the router ID. router-id router-id By default, routing loop detection is enabled.
  • Page 41 Step Command Remarks export [ protocol [ process-id ] ] of advertised routes. filter advertised routes. Return to system view. quit interface interface-type Enter interface view. interface-number Enable the IPv6 IS-IS By default, IPv6 IS-IS is disabled isis ipv6 enable [ process-id ] process on the interface.

  • Page 42: Displaying And Maintaining Ipv6 Mce

    Step Command Remarks routes. process-id ] advertised routes. (Optional.) Configure By default, BGP does not filter filtering of received filter-policy acl6-number import received routes. routes. Displaying and maintaining IPv6 MCE Execute display commands in any view. Task Command Display information about a specified VPN instance or all VPN display ip vpn-instance [ instance-name vpn-instance-name ] instances.
  • Page 43 Figure 6 Network diagram VPN 2 Site 1 PE 2 PE 1 XGE1/0/1 Vlan-int30: 30::2/64 Vlan-int40: 40::2/64 PE 3 Vlan-int10 VPN 1 XGE1/0/3 VPN 1 2001:1::2/64 Site 2 Vlan-int30: 30::1/64 2012:1::/64 XGE1/0/1 Vlan-int11 Vlan-int40: 40::1/64 Vlan-int10 XGE1/0/2 2012:1::2/64 VR 1 2001:1::1/64 Vlan-int20 2002:1::1/64...
  • Page 44 # Bind VLAN-interface 10 to 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 Ten-GigabitEthernet 1/0/2 to VLAN 20. [MCE] vlan 20 [MCE-vlan20] port ten-gigabitethernet 1/0/2 [MCE-vlan20] quit...
  • Page 45 <VR2> system-view [VR2] ripng 20 [VR2-ripng-20] quit [VR2] interface vlan-interface 20 [VR2-Vlan-interface20] ripng 20 enable [VR2-Vlan-interface20] quit [VR2] interface vlan-interface 21 [VR2-Vlan-interface21] ripng 20 enable [VR2-Vlan-interface21] quit # On the MCE, display the routing table of VPN instance vpn1. [MCE] display ipv6 routing-table vpn-instance vpn1 Destinations : 6 Routes : 6 Destination: ::1/128 Protocol...
  • Page 46 Interface : Vlan20 Cost Destination: 2002:1::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 2012::/64 Protocol : RIPng NextHop : FE80::20C:29FF:FE40:701 Preference: 100 Interface : Vlan20 Cost Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0...
  • Page 47 # On PE 1, create VLAN 30 and VLAN-interface 30, bind VLAN-interface 30 to VPN instance vpn1, and configure an IPv6 address for the VLAN-interface 30. [PE1] vlan 30 [PE1-vlan30] quit [PE1] interface vlan-interface 30 [PE1-Vlan-interface30] ip binding vpn-instance vpn1 [PE1-Vlan-interface30] ipv6 address 30::2 64 [PE1-Vlan-interface30] quit # On PE 1, create VLAN 40 and VLAN-interface 40, bind VLAN-interface 40 to VPN instance...
  • Page 48 Interface : InLoop0 Cost Destination: 30::/64 Protocol : Direct NextHop : :: Preference: 0 Interface : Vlan30 Cost Destination: 30::2/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 2012:1::/64 Protocol : OSPFv3 NextHop : FE80::202:FF:FE02:2 Preference: 150 Interface : Vlan30...
  • Page 49 NextHop : :: Preference: 0 Interface : NULL0 Cost The routing information for the two VPNs has been added into the routing tables on PE 1.

  • Page 50: Index

    Index IPv6 MPLS L3VPN MCE-VPN site EBGP, IPv6 MPLS L3VPN MCE-VPN site IBGP, advertising IPv6 MPLS L3VPN MCE-VPN site IPv6 IS-IS, MPLS L3VPN MCE EBGP VPN route IPv6 MPLS L3VPN MCE-VPN site OSPFv3, advertising, IPv6 MPLS L3VPN MCE-VPN site RIPng, MPLS L3VPN MCE OSPF VPN route advertising, IPv6 MPLS L3VPN VPN instance,...
  • Page 51 IPv6 MPLS L3VPN VPN instance route IPv6 MCE related attributes, configuration, MCE configuration, displaying, MPLS L3VPN architecture, maintaining, MPLS L3VPN MCE, multi-VPN instance, provider device. See P IPv6 MPLS L3VPN provider edge device. See MCE routing, displaying MCE/VPN site EBGP, IPv6 MCE, MCE/VPN site IBGP, MCE,...
  • Page 52 IPv6 MPLS L3VPN MCE-PE RIPng, VPN instance route related attribute configuration, IPv6 MPLS L3VPN MCE-PE routing, VPN-IPv4 address, maintaining, MPLS QoS MCE-PE EBGP, MPLS L3VPN MCE EBGP VPN route MCE-PE IBGP configuration, advertising, MCE-PE IS-IS, MPLS L3VPN MCE OSPF VPN route MCE-PE OSPF, advertising, MCE-PE RIP,...
  • Page 53 MPLS L3VPN MCE-VPN site IBGP, IPv6 MPLS L3VPN MCE/VPN site static routing, MPLS L3VPN MCE-VPN site IS-IS, IPv6 MPLS L3VPN MCE-PE EBGP, MPLS L3VPN MCE-VPN site OSPF, IPv6 MPLS L3VPN MCE-PE IBGP, MPLS L3VPN MCE-VPN site RIP, IPv6 MPLS L3VPN MCE-PE IPv6 IS-IS, MPLS L3VPN MCE-VPN site routing, IPv6 MPLS L3VPN MCE-PE IPv6 static MPLS L3VPN MCE-VPN site static routing,...
  • Page 54 configuring IPv6 MPLS L3VPN MCE-VPN site MPLS L3VPN MCE-PE RIP, OSPFv3, MPLS L3VPN MCE-VPN site RIP, configuring IPv6 MPLS L3VPN MCE-VPN site RIPng RIPng, IPv6 MPLS L3VPN MCE/VPN site RIPng, configuring IPv6 MPLS L3VPN VPN IPv6 MPLS L3VPN MCE-PE RIPng, instance, route configuring IPv6 MPLS L3VPN VPN instance...
  • Page 55 MPLS L3VPN MCE-VPN site EBGP, MPLS L3VPN MCE-VPN site IBGP, MPLS L3VPN MCE-VPN site IS-IS, MPLS L3VPN MCE-VPN site OSPF, MPLS L3VPN MCE-VPN site RIP, MPLS L3VPN MCE-VPN site routing, MPLS L3VPN MCE-VPN site static routing, site MPLS L3VPN, static IPv6 MPLS L3VPN MCE/VPN site static routing, IPv6 MPLS L3VPN MCE-PE IPv6 static...

Table of Contents