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

H3C S5130S-HI Series Configuration Manual

Mce configuration
Hide thumbs Also See for S5130S-HI Series:
Table of Contents

Advertisement

Quick Links

Download this manual
MCE Configuration Guide
This configuration guide is applicable to the following switches and software versions:
H3C S5130S-HI switch series (Release 6308 and later)
H3C S5130S-EI switch series (Release 6308 and later)
H3C S5130S-SI switch series (Release 6310 and later)
H3C S5120V2-SI switch series (Release 6310 and later)
H3C S3100V3-EI switch series (Release 6309P01 and later)
H3C E500C switch series (Release 6309P01 and later)
H3C E500D switch series (Release 6309P01 and later)
H3C E128C & E152C switches (Release 6310 and later)
New H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release 63xx
Document version: 6W103-20210730

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for H3C S5130S-HI Series

Summary of Contents for H3C S5130S-HI Series

  • Page 1 H3C S3100V3-EI switch series (Release 6309P01 and later) H3C E500C switch series (Release 6309P01 and later) H3C E500D switch series (Release 6309P01 and later) H3C E128C & E152C switches (Release 6310 and later) New H3C Technologies Co., Ltd. http://www.h3c.com Software version: Release 63xx...
  • Page 2 The information in this document is subject to change without notice. All contents in this document, including statements, information, and recommendations, are believed to be accurate, but they are presented without warranty of any kind, express or implied. H3C shall not be liable for technical or editorial errors or omissions contained herein.
  • Page 3 Preface This configuration guide describes the MCE fundamentals and configuration procedures. This preface includes the following topics about the documentation: • Audience • Conventions • Obtaining documentation • Technical support • Documentation feedback Audience This documentation is intended for: • Network planners.
  • Page 4 Convention Description Folder. Symbols Convention Description An alert that calls attention to important information that if not understood or followed WARNING! can result in personal injury. An alert that calls attention to important information that if not understood or followed CAUTION: can result in data loss, data corruption, or damage to hardware or software.
  • Page 5 Obtaining documentation To access the most up-to-date H3C product documentation, go to the H3C website at http://www.h3c.com.hk To obtain information about installation, configuration, and maintenance, click http://www.h3c.com.hk/Technical_Documents...

  • Page 6: Table Of Contents

    Contents Configuring MCE ··························································································· 1 About MCE ························································································································································· 1 MPLS L3VPN problems solved by MCE ···································································································· 1 Basic MPLS L3VPN architecture ··············································································································· 1 MCE-related MPLS L3VPN concepts ········································································································ 2 MCE working mechanism ·························································································································· 3 Restrictions and guidelines: MCE configuration································································································· 4 MCE tasks at a glance ·······································································································································...

  • Page 7: Configuring Mce

    Configuring MCE About MCE The Multi-VPN Instance Customer Edge (MCE) feature allows multiple VPNs to share a CE with ensured data security in an MPLS L3VPN network. MCE provides traffic separation between VPNs by distinguishing routes of the VPNs. MPLS L3VPN problems solved by MCE MPLS L3VPN is a L3VPN technology used to interconnect geographically dispersed VPN sites.

  • Page 8: Mce-Related Mpls L3Vpn Concepts

    Figure 1 Basic MPLS L3VPN architecture VPN 1 VPN 2 Site 1 Site 3 Site 2 VPN 2 Site 4 VPN 1 MCE-related 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 networks.

  • Page 9: Mce Working Mechanism

    VPN-IPv4 address Each VPN independently manages its address space. The address spaces of VPNs might overlap. For example, if both VPN 1 and VPN 2 use the addresses on subnet 10.110.10.0/24, address space overlapping occurs. Multiprotocol BGP (MP-BGP) can solve this problem by advertising VPN-IPv4 addresses (also called VPNv4 addresses).

  • Page 10: Restrictions And Guidelines: Mce Configuration

    • Route exchange between MCE and VPN site—Create VPN instances VPN 1 and VPN 2 on the MCE. Bind VLAN-interface 2 to VPN 1, and VLAN-interface 3 to VPN 2. The MCE adds a received route to the routing table of the VPN instance that is bound to the receiving interface. •...

  • Page 11: Configuring Vpn Instances

    Configuring routing between an MCE and a PE Configuring VPN instances Creating a VPN instance About VPN instances A VPN instance is a collection of the VPN membership and routing rules of its associated site. A VPN instance might correspond to more than one VPN. Procedure Enter system view.

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

    Configuring route related attributes for a VPN instance Restrictions and guidelines If you configure route related attributes in both VPN instance view and VPN instance IPv4 address family view, IPv4 VPN uses the configuration in VPN instance IPv4 address family view. Prerequisites Before you perform this task, create the routing policies to be used by this task.

  • Page 13: Configuring Rip Between An Mce And A Vpn Site

    Perform this configuration on the MCE. On the VPN site, configure a common static route. Procedure Enter system view. system-view Configure a static route for a VPN instance. 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 ] | vpn-instance d-vpn-instance-name next-hop-address } (Optional.) Configure the default preference for static routes.

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

    ospf [ process-id ] router-id router-id vpn-instance vpn-instance-name Keywords Usage guidelines An OSPF process that is bound to a VPN instance does not use the router-id public network router ID configured in system view. Therefore, you must router-id specify a router ID when creating a process or configure an IP address for a minimum of one interface in the VPN instance.

  • Page 15: Configuring Rip Between An Mce And A Pe

    Configuring RIP between an MCE and a PE Enter system view. system-view Create a RIP process for a VPN instance and enter RIP view. rip [ process-id ] vpn-instance vpn-instance-name Enable RIP on the interface attached to the specified network. network network-address [ wildcard-mask ] By default, RIP is disabled on an interface.

  • Page 16: Mce Configuration Examples

    For commands that display routing tables for VPN instances, see Layer 3—IP Routing Command Reference. MCE configuration examples Example: Configuring the MCE that uses OSPF to advertise VPN routes to the PE Network configuration As shown in Figure 4, VPN 2 runs OSPF. The edge devices of VPN 1 and VPN 2 are VR 1 and VR 2, respectively.
  • Page 17 [MCE-vpn-instance-vpn2] vpn-target 20:1 [MCE-vpn-instance-vpn2] quit # Bind VLAN-interface 10 to VPN instance vpn1, and configure an IP address for the VLAN interface. [MCE] interface vlan-interface 10 [MCE-Vlan-interface10] ip binding vpn-instance vpn1 [MCE-Vlan-interface10] ip address 10.214.10.3 24 [MCE-Vlan-interface10] quit # Bind VLAN-interface 20 to VPN instance vpn2, and configure an IP address for the VLAN interface.
  • Page 18 127.0.0.0/32 Direct 127.0.0.1 InLoop0 127.0.0.1/32 Direct 127.0.0.1 InLoop0 127.255.255.255/32 Direct 127.0.0.1 InLoop0 192.168.0.0/24 Static 10.214.10.2 Vlan10 224.0.0.0/4 Direct 0.0.0.0 NULL0 224.0.0.0/24 Direct 0.0.0.0 NULL0 255.255.255.255/32 Direct 127.0.0.1 InLoop0 The output shows that the MCE has a static route for VPN instance vpn1. # Run OSPF in VPN 2.
  • Page 19 Configure routing between the MCE and PE 1: # On the MCE, bind VLAN-interface 30 to VPN instance vpn1, and configure an IP address for the VLAN interface. [MCE] interface vlan-interface 30 [MCE-Vlan-interface30] ip binding vpn-instance vpn1 [MCE-Vlan-interface30] ip address 30.1.1.1 24 [MCE-Vlan-interface30] quit # Bind VLAN-interface 40 to VPN instance vpn2, and configure an IP address for the VLAN interface.
  • Page 20 # Use similar procedures to configure OSPF process 20 between MCE and PE 1 and redistribute VPN 2's routing information. (Details not shown.) Verifying the configuration # Verify that PE 1 has learned the static route of VPN 1 through OSPF. [PE1] display ip routing-table vpn-instance vpn1 Destinations : 13 Routes : 13...

  • Page 21: Configuring Ipv6 Mce

    Configuring IPv6 MCE About IPv6 MCE IPv6 MCE provides traffic separation between VPNs by distinguishing routes of the VPNs. It allows multiple VPNs to share the same CE with ensured data security in an IPv6 MPLS L3VPN network. IPv6 MPLS L3VPN uses BGP to advertise IPv6 VPN routes and uses MPLS to forward IPv6 VPN packets on the service provider backbone.

  • Page 22: Associating A Vpn Instance With A Layer 3 Interface

    By default, no RD is configured for a VPN instance. (Optional.) Configure a description for the VPN instance. description text By default, no description is configured for a VPN instance. The description should contain the VPN instance's related information, such as its relationship with a certain VPN.

  • Page 23: Configuring Routing Between An Mce And A Vpn Site

    Configure route targets. vpn-target vpn-target&<1-8> [ both | export-extcommunity | import-extcommunity ] By default, no route targets are configured. Set the maximum number of active routes. routing-table limit number { warn-threshold | simply-alert } By default, the number of active routes in a VPN instance is not limited. Setting the maximum number of active routes for a VPN instance can prevent the device from storing too many routes.

  • Page 24: Configuring Ripng Between An Mce And A Vpn Site

    Configuring RIPng between an MCE and a VPN site About RIPng between an MCE and a VPN site By 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.

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

    import-route protocol [ as-number ] [ process-id | all-processes ] [ allow-direct | cost cost-value | nssa-only | route-policy route-policy-name | tag tag | type type ] * By default, no routes are redistributed into OSPFv3. Return to system view. quit Enter interface view.

  • Page 26: Configuring Ospfv3 Between An Mce And A Pe

    Return to system view. quit Enter interface view. interface interface-type interface-number Enable the RIPng process on the interface. ripng process-id enable By default, RIPng is disabled on an interface. Configuring OSPFv3 between an MCE and a PE Enter system view. system-view Create an OSPFv3 process for an IPv6 VPN instance and enter OSPFv3 view.

  • Page 27: Ipv6 Mce Configuration Examples

    IPv6 MCE configuration examples Example: Configuring IPv6 MCE Network configuration As shown in Figure 5, RIPng runs in VPN 2. The edge routers of VPN 1 and VPN 2 are VR1 and VR2, respectively. Configure the MCE device to separate routes from different VPNs and advertise VPN routes to PE 1 through OSPFv3.
  • Page 28 [MCE-vpn-instance-vpn2] vpn-target 20:1 [MCE-vpn-instance-vpn2] quit # 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 # Bind VLAN-interface 20 to VPN instance vpn2, and configure an IPv6 address for the VLAN interface.
  • Page 29 [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 tables of VPN instances vpn1 and vpn2. [MCE] display ipv6 routing-table vpn-instance vpn1 Destinations : 6 Routes : 6 Destination: ::1/128 Protocol...
  • Page 30 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 Cost Destination: FF00::/8 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0...
  • Page 31 [MCE-ospf-10] quit # Enable OSPFv3 on VLAN-interface 30. [MCE] interface vlan-interface 30 [MCE-Vlan-interface30] ospfv3 10 area 0.0.0.0 [MCE-Vlan-interface30] quit # On PE 1, enable OSPFv3 process 10 and bind the process to VPN instance vpn1. [PE1] ospfv3 10 vpn-instance vpn1 [PE1-ospf-10] router-id 100.100.10.1 [PE1-ospf-10] quit # Enable OSPFv3 on VLAN-interface 30.
  • Page 32 Destinations : 6 Routes : 6 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 40::/64 Protocol : Direct NextHop : :: Preference: 0 Interface : Vlan40 Cost Destination: 40::2/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface...

This manual is also suitable for:

S5130s-ei seriesS5130s-si seriesS5120v2-si seriesS3100v3-ei seriesE500c seriesE500d series ... Show all

Table of Contents