HP 6125XLG Configuration Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Switch
  5. 6125XLG
  6. Configuration manual
HP 6125XLG Configuration Manual

HP 6125XLG Configuration Manual

Blade switch mce configuration guide
Hide thumbs Also See for 6125XLG:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual, Installation Manual
HP 6125XLG Blade Switch
MCE

Configuration Guide

Part number: 5998-3721
Software version: Release 2306
Document version: 6W100-20130912

Advertisement

Table of Contents
loading

Related Manuals for HP 6125XLG

Summary of Contents for HP 6125XLG

  • Page 1: Configuration Guide

    HP 6125XLG Blade Switch Configuration Guide Part number: 5998-3721 Software version: Release 2306 Document version: 6W100-20130912...
  • Page 2 HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

  • Page 3: Table Of Contents

    Contents Configuring MCE ························································································································································· 1   Overview ············································································································································································ 1   MPLS L3VPN overview ············································································································································· 1   MPLS L3VPN concepts ············································································································································· 2   MCE ··········································································································································································· 3   How MCE works ······················································································································································ 4   Configuring VPN instances on an MCE device ············································································································· 4  ...

  • Page 4: Configuring Mce

    Configuring MCE This chapter describes only Multi-VPN-Instance CE (MCE) configuration. For information about routing protocols, see Layer 3—IP Services Configuration Guide. Overview MPLS L3VPN overview MPLS L3VPN is a PE-based L3VPN technology. It uses BGP to advertise VPN routes and uses MPLS to forward VPN packets over the service provider backbone.

  • Page 5: Mpls L3Vpn Concepts

    After a CE establishes an adjacency with a directly connected PE, it advertises its VPN routes to the PE and learns remote VPN routes from the PE. A CE and a PE can use BGP, an IGP, or static routing to exchange routing information.

  • Page 6: Mce

    Figure 2 VPN-IPv4 address structure The MCE device does not support advertising VPN routes through MP-BGP. However, to run BGP VPN instances on the MCE device, you must configure a unique RD for each VPN instance to distinguish between the VPN instances. An RD can be in one of the following formats distinguished by a 2-byte Type field: When the value of the Type field is 0, the Administrator subfield occupies two bytes, the Assigned •...

  • Page 7: How Mce Works

    For better services and higher security, a private network is usually divided into multiple VPNs to isolate services. To meet these requirements, you can configure a CE for each VPN, which increases device expenses and maintenance costs. Or, you can configure multiple VPNs to use the same CE and the same routing table, which sacrifices data security.
  • Page 8 Creating a VPN instance You can configure a description for a VPN instance to record its related information, such as its relationship with a certain VPN. To create and configure a VPN instance: Step Command Remarks Enter system view. system-view Create a VPN instance and By default, no VPN instance is ip vpn-instance vpn-instance-name...

  • Page 9: Configuring Routing On An Mce Device

    Step Command Remarks Enter system view. system-view Enter VPN instance view. ip vpn-instance vpn-instance-name (Optional.) Enter IPv4 VPN ipv4-family view. vpn-target vpn-target&<1-8> Configure route targets for the By default, no route target is [ both | export-extcommunity | VPN instance. configured for the VPN instance.

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

    Configuring the link layer and network layer protocols on related interfaces to ensure IP • connectivity. Configuring routing between an MCE and a VPN site Configuring static routing between an MCE and a VPN site An MCE can reach a VPN site through a static route. Static routing on a traditional CE is globally effective and thus does not support address overlapping among VPNs.
  • Page 11 Step Command Remarks (Optional.) Configure the If you do not specify a default cost default cost value for the default cost value value, the default cost value is 0. redistributed routes. For more information about RIP, see Layer 3—IP Routing Configuration Guide. Configuring OSPF between an MCE and a VPN site An OSPF process can belong to a single VPN instance.
  • Page 12 Step Command Remarks The defaults are as follows: (Optional.) Configure the type ext-community-type { domain-id • 0x0005 for Domain ID. codes of OSPF extended type-code1 | router-id type-code2 • 0x0107 for Router ID. community attributes. | route-type type-code3 } • 0x0306 for Route Type.
  • Page 13 Step Command Remarks import-route { isis [ process-id ] | By default, IS-IS does not ospf [ process-id ] | rip redistribute routes of any other [ process-id ] | bgp [ allow-ibgp ] | routing protocol. (Optional.) Redistribute direct | static } [ cost cost | remote site routes advertised If you do not specify the route level cost-type { external | internal } |...

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

    Step Command Remarks filter-policy { acl-number | (Optional.) Configure a prefix-list ip-prefix-name } export By default, BGP does not filter filtering policy to filter [ direct | isis process-id | ospf advertised routes. advertised routes. process-id | rip process-id | static ] (Optional.) Configure a filter-policy { acl-number |...
  • Page 15 Configuring static routing between an MCE and a PE Step Command Remarks Enter system view. system-view ip route-static vpn-instance s-vpn-instance-name dest-address { mask | mask-length } { next-hop-address [ public ] [ track track-entry-number ] | interface-type Configure a static route By default, no static route is interface-number [ next-hop-address ] | for a VPN instance.
  • Page 16 Step Command Remarks (Optional.) Configure the domain-id domain-id [ secondary ] By default, the domain ID is 0. OSPF domain ID. The defaults are as follows: (Optional.) Configure the type ext-community-type { domain-id • 0x0005 for Domain ID. codes of OSPF extended type-code1 | router-id type-code2 •...
  • Page 17 Configuring IS-IS between an MCE and a PE Step Command Remarks Enter system view. system-view 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.

  • Page 18: Displaying Information About Mce

    Step Command Remarks (Optional.) Configure a filter-policy { acl-number | By default, BGP does not filter the filtering policy to filter the prefix-list ip-prefix-name } import received routes. received routes. For more information about BGP, see Layer 3—IP Routing Configuration Guide. Displaying information about MCE Execute display commands in any view.

  • Page 19: Configuration Procedure

    Figure 4 Network diagram VPN 2 Site 1 CE 1 PE 2 PE 1 XGE1/0/1 Vlan-int30: 30.1.1.2/24 Vlan-int40: 40.1.1.2/24 PE 3 CE 2 XGE1/0/3 VPN 1 VPN 1 Vlan-int30: 30.1.1.1/24 XGE1/0/1 192.168.0.0/24 Site 2 Vlan-int40: 40.1.1.1/24 Vlan-int10 XGE1/0/2 VR 1 10.214.10.3/24 Vlan-int20 10.214.20.3/24...
  • Page 20 [MCE-Vlan-interface10] ip binding vpn-instance vpn1 [MCE-Vlan-interface10] ip address 10.214.10.3 24 # Configure VLAN 20, add port Ten-GigabitEthernet 1/0/2 to VLAN 20, bind VLAN-interface 20 with VPN instance vpn2, and specify an IP address for VLAN-interface 20. [MCE-Vlan-interface10] quit [MCE] vlan 20 [MCE-vlan20] port Ten-GigabitEthernet 1/0/2 [MCE-vlan20] quit [MCE] interface vlan-interface 20...
  • Page 21 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 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.
  • Page 22 The output shows that the MCE has learned the private routes of VPN 2. The MCE maintains the routes of VPN 1 and those of VPN 2 in two routing tables. In this way, routes from different VPNs are separated. Configure routing between MCE and PE 1: # The MCE uses port Ten-GigabitEthernet 1/0/3 to connect to PE's port Ten-GigabitEthernet 1/0/1.
  • Page 23 [PE1-Vlan-interface40] quit # Configure the IP address of the interface Loopback 0 as 101.101.10.1 for the MCE and as 100.100.10.1 for PE 1. Specify the loopback interface address as the router ID for the MCE and PE 1. (Details not shown) # Enable OSPF process 10 on the MCE, bind the process to VPN instance vpn1, disable OSPF routing loop detection, and set the domain ID to 10.

  • Page 24: Using Bgp To Advertise Vpn Routes To The Pe

    [PE1] display ip routing-table vpn-instance vpn2 Destinations : 13 Routes : 13 Destination/Mask Proto Cost NextHop Interface 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...
  • Page 25 Figure 5 Network diagram VPN 2 Site 1 CE 1 PE 2 PE 1 XGE1/0/1 Vlan-int30: 30.1.1.2/24 Vlan-int40: 40.1.1.2/24 PE 3 CE 2 XGE1/0/3 VPN 1 VPN 1 Vlan-int30: 30.1.1.1/24 XGE1/0/1 192.168.0.0/24 Site 2 Vlan-int40: 40.1.1.1/24 Vlan-int10 XGE1/0/2 VR 1 10.214.10.3/24 Vlan-int20 10.214.20.3/24...
  • Page 26 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 27 # On PE 1, enable BGP in AS 200 and specify the MCE as its EBGP peer. [PE1] bgp 200 [PE1-bgp] ip vpn-instance vpn1 [PE1-bgp-vpn1] peer 30.1.1.1 as-number 100 [PE1-bgp-vpn1] ipv4-family [PE1-bgp-ipv4-vpn1] peer 30.1.1.1 enable [PE1-bgp-ipv4-vpn1] quit [PE1-bgp-vpn1] quit [PE1-bgp] quit # On PE 1, display the routing information for VPN instance vpn1.
  • Page 28 255.255.255.255/32 Direct 0 127.0.0.1 InLoop0 The output shows that PE 1 has learned the private route of VPN 2 through BGP. Now, the MCE has redistributed the OSPF routes of the two VPN instances into the EBGP routing tables of PE 1.

  • Page 29: Configuring Ipv6 Mce

    Configuring IPv6 MCE This chapter describes how to configure the IPv6 MCE function. 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 30: Configuring Route Attributes For A Vpn Instance

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Associate the current interface ip binding vpn-instance By default, no VPN instance is with a VPN instance. vpn-instance-name associated with an interface. NOTE: The ip binding vpn-instance command deletes the IPv6 address of the current interface. You must reconfigure an IPv6 address for the interface after configuring the command.

  • Page 31: Configuring Routing On An Ipv6 Mce Device

    Step Command Remarks By default, routes to be advertised are not filtered. (Optional.) Apply an export Make sure the routing policy export route-policy route-policy routing policy. already exists. Otherwise, the device does not filter routes to be advertised. NOTE: • Route related attributes configured in VPN instance view are applicable to both IPv4 VPNs and IPv6 VPNs.
  • Page 32 Step Command Remarks ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address By default, no IPv6 static prefix-length { interface-type route is configured. interface-number [ next-hop-address ] | Configure an IPv6 static route Perform this configuration nexthop-address [ public ] | vpn-instance for an IPv6 VPN instance. on the IPv6 MCE.
  • Page 33 For more information about OSPFv3, see Layer 3—IP Routing Configuration Guide. To configure OSPFv3 between IPv6 MCE and VPN site: Step Command Remarks Enter system view. system-view Create an OSPFv3 process for Perform this configuration on the ospfv3 [ process-id ] vpn-instance a VPN instance and enter IPv6 MCE.
  • Page 34 Step Command Remarks By default, no routes from any other routing protocol are ipv6 import-route protocol redistributed to IPv6 IS-IS. (Optional.) Redistribute [ process-id ] [ allow-ibgp ] [ cost remote site routes advertised cost | [ level-1 | level-1-2 | If you do not specify the route level by the PE.

  • Page 35: Configuring Routing Between An Ipv6 Mce And A Pe

    NOTE: After you configure an IPv6 BGP VPN instance, the IPv6 BGP route exchange for the IPv6 VPN instance is the same as the normal IPv6 BGP VPN route exchange. For more information about IPv6 Layer 3—IP Routing Configuration Guide BGP, see Configure the VPN site: Step...
  • Page 36 Step Command Remarks If you do not specify a default (Optional.) Configure ipv6 route-static default-preference preference value, the default precedence default-preference-value the default for IPv6 static routes. preference value is Configuring RIPng between an IPv6 MCE and a PE Step Command Remarks Enter system view.
  • Page 37 Step Command Remarks Enable the OSPFv3 ospfv3 process-id area area-id By default, OSPFv3 is disabled process on the interface. [ instance instance-id ] on an interface. For more information about OSPFv3, see Layer 3—IP Routing Configuration Guide. Configuring IPv6 IS-IS between an IPv6 MCE and a PE Step Command Remarks...

  • Page 38: Displaying Information About Ipv6 Mce

    Step Command Remarks Create and enter BGP IPv6 ipv6-family [ unicast ] unicast instance view. Enable BGP to exchange IPv6 By default, BGP cannot unicast routing information with peer ipv6-address enable exchange IPv6 unicast routing the EBGP peer. information with a peer. import-route protocol [ process-id By default, no route Redistribute VPN routes.
  • Page 39 Figure 6 Network diagram Configuration procedure Assume that the system name of the IPv6 MCE device is MCE, the system names of the edge devices of VPN 1 and VPN 2 are VR1 and VR2, 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 40 # 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 Ten-GigabitEthernet 1/0/2 to VLAN 20, bind VLAN-interface 20 with VPN instance vpn2, and assign an IPv6 address to VLAN-interface 20.
  • Page 41 # On VR 2, assign IPv6 address 2002:1::2/64 to the interface connected to the MCE and 2012::2/64 to the interface connected to VPN 2. (Details not shown.) # Configure RIPng, and advertise subnets 2012::/64 and 2002:1::/64. <VR2> system-view [VR2] ripng 20 [VR2-ripng-20] quit [VR2] interface vlan-interface 20 [VR2-Vlan-interface20] ripng 20 enable...
  • Page 42 Interface : Vlan20 Cost Destination: 2002:1::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 2012::/64 Protocol : RIPng NextHop : FE80::20F:E2FF:FE3E:9CA2 Preference: 100 Interface : Vlan20 Cost Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0...
  • Page 43 [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 with VPN instance vpn2 and configure an IPv6 address for the VLAN-interface 40. [PE1] vlan 40 [PE1-vlan40] quit [PE1] interface vlan-interface 40...
  • Page 44 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 Cost Destination: FE80::/10 Protocol : Direct NextHop : :: Preference: 0 Interface : NULL0 Cost The output shows that PE 1 has learned the private route of VPN 1 through OSPFv3.

  • Page 45: Support And Other Resources

    Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: • Product model names and numbers Technical support registration number (if applicable) • Product serial numbers •...

  • Page 46: Conventions

    Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
  • Page 47 Network topology icons Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.

  • Page 48: Index

    Index OSPF between MCE and VPN site, OSPFv3 between IPv6 MCE and PE, address OSPFv3 between IPv6 MCE and VPN site, address space overlapping (MPLS L3VPN), RIP between MCE and PE, associating RIP between MCE and VPN site, VPN instance with interface (IPv6 MCE), RIPng between IPv6 MCE and PE, VPN instance with interface (MCE), RIPng between IPv6 MCE and VPN site,...
  • Page 49 creating VPN (IPv6 MCE), creating VPN (MCE), L3VPN technology VPN (MPLS L3VPN), MPLS L3VPN, interface associating VPN instance (IPv6 MCE), associating VPN instance (MCE), associating instance with interface, IPv6 IS-IS configuring IPv6 MCE, configuring IPv6 IS-IS between IPv6 MCE and configuring MCE, configuring, configuring IPv6 IS-IS between IPv6 MCE and...
  • Page 50 configuring VPN instance (MCE), configuring VPN instance route related attribute (IPv6 MCE), multi-VPN network configuring VPN instance route related attribute MCE, (MCE), creating VPN instance (IPv6 MCE), network creating VPN instance (MCE), address space overlapping (MPLS L3VPN), route target attribute (BGP extended attribute), associating VPN instance with interface (IPv6 site (MPLS L3VPN), MCE),...
  • Page 51 configuring IPv6 static routing between IPv6 configuring EBGP between IPv6 MCE and PE, MCE and VPN site, configuring EBGP between IPv6 MCE and VPN configuring IS-IS between MCE and PE, site, configuring IS-IS between MCE and VPN site, configuring EBGP between MCE and PE, configuring MCE, configuring EBGP between MCE and VPN site, configuring OSPF between MCE and PE,...
  • Page 52 configuring IPv6 static routing between IPv6 configuring RIPng between IPv6 MCE and VPN MCE and PE, site, configuring IPv6 static routing between IPv6 configuring static routing between MCE and PE, MCE and VPN site, configuring static routing between MCE and VPN configuring static routing between MCE and site, creating instance (IPv6 MCE),...

Table of Contents