VPLS [PDF]

Zitiervorschau

VPLS SYSTEM ADMINISTRATOR GUIDE

87/1543-CRA 119 1364/1 Uen A1

Copyright © Ericsson AB 2013–2014. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner. Disclaimer The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Contents

Contents 1

Overview

1

1.1

About VPLS

1

1.2

Prerequisites

3

1.3

Restrictions

3

2

Configuration

5

2.1

Configuration Command Hierarchy

5

2.2

Create a VPLS Pseudowire Peer Profile

6

2.3

Create a VPLS Pseudowire Instance

7

2.4

Associate a VPLS Pseudowire with a Qualified Bridge

8

2.5

Associate a VPLS Pseudowire with an Unqualified Bridge

8

2.6

Configure a Typical VPLS Topology

9

2.7

Configure a Hierarchical VPLS Topology

12

2.8

Configure VPLS Pseudowire Redundancy

15

2.9

Manually Switchover the VPLS Pseudowire

17

2.10

Associate a Split Horizon Group with a VPLS Pseudowire Instance

17

2.11

Configure Static MAC Addresses for a Pseudowire Instance

18

2.12

Configure Native VLAN for a Pseudowire Instance

19

2.13

Map an LSP to a VPLS Pseudowire Instance

20

2.14

Configure MAC Withdrawal

21

3

Operations

23

Reference List

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

25

VPLS

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Overview

1

Overview The document provides an overview of Virtual Private LAN Service (VPLS) and describes the tasks and commands used to configure, monitor, and administer VPLS functions.

1.1

About VPLS VPLS enables networks at separate geographical locations to communicate with each other across a WAN as if they were directly attached to each other in a LAN. Creating VPLS pseudowires makes the WAN transparent. A pseudowire emulates the attributes and function of Ethernet connectivity over a WAN. Switching functionality or service translation is outside the scope of the pseudowire and transport network. Pseudowires are carried over Multiprotocol Label Switching (MPLS) tunnels on the network. MPLS signaling protocols automatically provision a service on a pseudowire end-to-end, so you can provision a pseudowire by pointing to its two endpoints; and MPLS automatically negotiates the path. Figure 1 displays the network topology for a typical VPLS configuration.

Figure 1

Typical VPLS Network Topology

Customer Edge (CE) routers, which are on the edge of geographically separate customer networks, are connected by Ethernet to Provider Edge (PE) routers on an MPLS provider network. A pseudowire is established for each pair of CE routers to be connected into a virtual private LAN. In the given figure, the PW1 pseudowire is shown to connect the CE1 and CE3 routers. The CE4

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

1

VPLS

and CE5 routers connect with the CE1 router over the VPLS network, but not necessarily to each other. To create pseudowires, a VPLS-enabled bridge must first be configured on each PE router before establishing peering (neighbor) sessions across the bridge. The pseudowire is the circuit across which the peering session occurs. A VPLS-enabled bridge can have multiple peering sessions.

1.1.1

Qualified Bridging Qualified bridging refers to a situation where qualified source MAC address learning configuration is enabled on a bridge. When enabled, packets are forwarded based on their MAC address and VLAN ID. For more information about qualified source MAC address learning, see Bridging.

1.1.2

Unqualified Bridging Unqualified bridging refers to a situation where qualified source MAC address learning configuration is disabled on a bridge. When disabled, VLAN ID 4095 (untagged) is used as the default VLAN for all MAC entries. For more information about unqualified source MAC address learning, see Bridging.

1.1.3

Native VLAN When qualified source MAC address learning is enabled on a bridge, you can configure a native VLAN on a pseudowire to switch all untagged traffic to a tagged VLAN ID.

1.1.4

Hierarchical VPLS Through hierarchical connection, an HVPLS can effectively reduce the number of pseudowires between PEs and the replication and forwarding of packets in backbone networks. HVPLS improves the applicability of VPLS in large-scale deployments, for example when VPLS is extended to multitenant units or in instances where multiple VPLS areas are interconnected. To support HVPLS topologies, spoke connections are used between VPLS peers. The VPLS instances at the two ends of the peering assume the roles of MTU-s and PE-rs respectively.

1.1.5

MAC Withdrawal As an optional configuration, you can enable a PE-rs node (where spoke and hub pseudowires are connected) to send a zero MAC withdrawal message to all HUB pseudowires when the state of the spoke pseudowire changes from DOWN/STANDBY to UP.

2

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Overview

1.2

Prerequisites Before you can configure VPLS, you must complete the following:

1.3

•

Set up the MPLS backbone. To configure MPLS, see MPLS.

•

Set up Label Distribution Protocol (LDP) between PE peers. To configure LDP, see LDP.

•

Create a bridge on each PE router. To configure transparent, self-learning bridges, see Bridging.

Restrictions Not all features described are supported on all platforms. Consult the Network Impact Report for your product release for details.

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

3

VPLS

4

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Configuration

2

Configuration To configure VPLS, refer to the examples in the following sections. Note:

2.1

The examples that follow might not show the complete command syntax. For more information, see the Command List.

Configuration Command Hierarchy Configure bridges, pseudowire instances, and pseudowire peer profiles in global configuration mode. The hierarchy of configuration commands is as follows: bridge vpls pseudowire instance (VPLS) native vlan neighbor mac-flush split-horizon-group pseudowire vlan pseudowire instance peer-profile backup-peer tunnel lsp label signaling-proto pseudowire peer-profile peer auto-revert-delay control-word ignore-mtu log-up-down mtu (peer) redundancy-mode

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

5

VPLS

tunnel lsp vc-type Note:

2.2

In addition to the commands above, you can also use standard configuration commands such as abort, comment, commit, default, exit and no.

Create a VPLS Pseudowire Peer Profile This example creates the pseudowire peer profile PE1. In this example: •

The peer IP address is 10.10.10.1.

•

The MTU size for packets sent over the pseudowire is 2000 bytes.

•

The router is configured to include the pseudowire control word in packet headers.

•

The router is configured to bring up the pseudowire when the router and its remote pseudowire peer have different MTU settings.

•

The pseudowire type is vlan (tagged Ethernet, type 0x0006).

To create a VPLS pseudowire peer profile, perform the following steps starting in global configuration mode. 1. Create the peer profile and enter pseudowire peer-profile configuration mode. [local]Ericsson(config)#pseudowire peer-profile PE1

2. Specify the pseudowire peer IP address and enter pseudowire profile peer configuration mode. [local]Ericsson(config-pw-peer-profile)#peer 10.10.10.1

3. Set the MTU for the pseudowire. [local]Ericsson(config-pw-profile-peer)#mtu 2000

4. Configure peer attributes. [local]Ericsson(config-pw-profile-peer)#control-word [local]Ericsson(config-pw-profile-peer)#ignore-mtu [local]Ericsson(config-pw-profile-peer)#vc-type vlan [local]Ericsson(config-pw-profile-peer)#commit

5. Confirm the configuration.

6

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Configuration

[local]Ericsson(config-pw-profile-peer)#show configuration pseudowire ... ! Pseudowire peer-profile configuration pseudowire peer-profile PE1 peer 10.10.10.1 control-word ignore-mtu mtu 2000 vc-type vlan ! ! ! end

2.3

Create a VPLS Pseudowire Instance The example creates pseudowire instance 12, and assigns the PE1 peer-profile to the instance. In this example: •

The pseudowire instance identifier is 100.

•

The signaling protocol used to establish the pseudowire link is LDP.

To create a VPLS pseudowire instance, perform the following steps starting in global configuration mode. 1. Create the VPLS pseudowire instance and enter pseudowire instance configuration mode. [local]Ericsson(config)#pseudowire instance 12

2. Set the pseudowire instance identifier. [local]Ericsson(config-pw-instance)#pw-id 100

3. Associate a peer profile with the pseudowire instance. [local]Ericsson(config-pw-instance)#peer-profile PE1

4. Set the signaling protocol. [local]Ericsson(config-pw-instance-peer-profile)#signaling-proto ldp [local]Ericsson(config-pw-instance-peer-profile)#commit

5. Confirm the configuration.

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

7

VPLS

[local]Ericsson(config-pw-instance-peer-profile)#show configuration pseudowire ... ! Pseudowire instance configuration pseudowire instance 12 pw-id 100 peer-profile PE1 signaling-proto ldp ! ! ! end

2.4

Associate a VPLS Pseudowire with a Qualified Bridge This example associates a VPLS pseudowire with the qualified bridge isp1. To associate a VPLS pseudowire with a qualified bridge, perform the following steps starting in global configuration mode. 1. Select the bridge.

[local]Ericsson(config)#bridge isp1

2. Enable VPLS. [local]Ericsson(config-bridge)#vpls

3. Configure the VLAN ID for the VPLS instance, and associate a pseudowire instance with the bridge. [local]Ericsson(config-bridge-vpls)#pseudowire vlan 10 [local]Ericsson(config-bridge-vpls)#pseudowire instance 12 [local]Ericsson(config-bridge-vpls)#commit

4. Confirm the configuration. [local]Ericsson(config-bridge-vpls)#show configuration bridge ... bridge isp1 description Bridge for all traffic to ISP1 aging-time 18000 vpls pseudowire vlan 10 pseudowire instance 12 ! end

2.5

Associate a VPLS Pseudowire with an Unqualified Bridge This example associates a VPLS pseudowire with the unqualified bridge isp2. To associate a VPLS pseudowire with an unqualified bridge, perform the following steps starting in global configuration mode.

8

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Configuration

1. Select the bridge. [local]Ericsson(config)#bridge isp2

2. Enable VPLS. [local]Ericsson(config-bridge)#vpls

3. Configure the untagged VPLS instance, and associate a pseudowire instance with the bridge. [local]Ericsson(config-bridge-vpls)#pseudowire vlan untagged [local]Ericsson(config-bridge-vpls)#pseudowire instance 2 [local]Ericsson(config-bridge-vpls)#commit

4. Confirm the configuration. [local]Ericsson(config-bridge-vpls)#show configuration bridge ... bridge isp2 description Bridge for all traffic to ISP2 aging-time 18000 no qualifed-learning vpls pseudowire vlan untagged pseudowire instance 2 ! end

2.6

Configure a Typical VPLS Topology This example configures three PE routers (PE1, PE2, and PE3) in a flat, full-mesh VPLS topology with unqualified bridging.

Figure 2

Full-Mesh VPLS Topology

In Figure 2, the routers are configured as follows: •

PE1 is configured with pseudowire connections to peer IP address 10.10.10.2 (PE2) and 10.10.10.3 (PE3).

•

PE2 is configured with pseudowire connections to peer IP address 10.10.10.1 (PE1) and 10.10.10.3 (PE3).

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

9

VPLS

•

PE3 is configured with pseudowire connections to peer IP address 10.10.10.1 (PE1) and 10.10.10.2 (PE2).

To configure a typical VPLS topology, configure the routers as shown in the following sections.

2.6.1

Configure the PE1 Router On router PE1, perform the following steps starting in global configuration mode. 1. Create peer profiles for pseudowire connections to PE2 and PE3.

[local]PE1(config)#pseudowire peer-profile PE2 [local]PE1(config-pw-peer-profile)#peer 10.10.10.2 [local]PE1(config-pw-profile-peer)#exit [local]PE1(config-pw-peer-profile)#exit [local]PE1(config)#pseudowire peer-profile PE3 [local]PE1(config-pw-peer-profile)#peer 10.10.10.3 [local]PE1(config-pw-profile-peer)#exit [local]PE1(config-pw-peer-profile)#exit

2. Create pseudowire instances for PE2 and PE3. [local]PE1(config)#pseudowire instance 1 [local]PE1(config-pw-instance)#pw-id 100 [local]PE1(config-pw-instance)#peer-profile PE2 [local]PE1(config-pw-instance-peer-profile)#exit [local]PE1(config-pw-instance)#exit [local]PE1(config)#pseudowire instance 2 [local]PE1(config-pw-instance)#pw-id 100 [local]PE1(config-pw-instance)#peer-profile PE3 [local]PE1(config-pw-instance)#exit

3. Configure the VPLS instance and associate the pseudowires with an existing bridge. [local]PE1(config)#bridge b1 [local]PE1(config-bridge)#vpls [local]PE1(config-bridge-vpls)#pseudowire vlan untagged [local]PE1(config-bridge-vpls)#pseudowire instance 1 [local]PE1(config-bridge-vpls)#pseudowire instance 2 [local]PE1(config-bridge-vpls)#commit

4. Confirm the configuration.

10

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Configuration

[local]PE1(config-bridge-vpls)#show configuration pseudowire ... ! Pseudowire peer-profile configuration pseudowire peer-profile PE2 peer 10.10.10.2 ! pseudowire peer-profile PE3 peer 10.10.10.3 ! ! Pseudowire instance configuration pseudowire instance 1 pw-id 100 peer-profile PE2 ! pseudowire instance 2 pw-id 100 peer-profile PE3 ! ! ! end [local]PE1(config-bridge-vpls)#show configuration bridge ... bridge b1 vpls pseudowire vlan untagged pseudowire instance 1 pseudowire instance 2 ! end

2.6.2

Configure the PE2 Router On router PE2, repeat the PE1 router configuration with pseudowires that provide connectivity to PE1 and PE3.

[local]PE2(config)#pseudowire peer-profile PE1 [local]PE2(config-pw-peer-profile)#peer 10.10.10.1 [local]PE2(config-pw-profile-peer)#exit [local]PE2(config-pw-peer-profile)#exit [local]PE2(config)#pseudowire peer-profile PE3 [local]PE2(config-pw-peer-profile)#peer 10.10.10.3 [local]PE2(config-pw-profile-peer)#exit [local]PE2(config-pw-peer-profile)#exit [local]PE2(config)#pseudowire instance 1 [local]PE2(config-pw-instance)#pw-id 100 [local]PE2(config-pw-instance)#peer-profile PE1 [local]PE2(config-pw-instance)#exit [local]PE2(config)#pseudowire instance 2 [local]PE2(config-pw-instance)#pw-id 100 [local]PE2(config-pw-instance)#peer-profile PE3 [local]PE2(config-pw-instance)#exit [local]PE2(config)#bridge b1 [local]PE2(config-bridge)#vpls [local]PE2(config-bridge-vpls)#pseudowire instance 1 [local]PE2(config-bridge-vpls)#pseudowire instance 2 [local]PE2(config-bridge-vpls)#commit

2.6.3

Configure the PE3 Router To complete the example configuration, repeat the PE1 router configuration on the PE3 router with pseudowires that provide connectivity to PE1 and PE2.

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

11

VPLS

[local]PE3(config)#pseudowire peer-profile PE1 [local]PE3(config-pw-peer-profile)#peer 10.10.10.1 [local]PE3(config-pw-profile-peer)#exit [local]PE3(config-pw-peer-profile)#exit [local]PE3(config)#pseudowire peer-profile PE2 [local]PE3(config-pw-peer-profile)#peer 10.10.10.2 [local]PE3(config-pw-profile-peer)#exit [local]PE3(config-pw-peer-profile)#exit [local]PE3(config)#pseudowire instance 1 [local]PE3(config-pw-instance)#pw-id 100 [local]PE3(config-pw-instance)#peer-profile PE1 [local]PE3(config-pw-instance)#exit [local]PE3(config)#pseudowire instance 2 [local]PE3(config-pw-instance)#pw-id 100 [local]PE3(config-pw-instance)#peer-profile PE2 [local]PE3(config-pw-instance)#exit [local]PE3(config)#bridge b1 [local]PE3(config-bridge)#vpls [local]PE3(config-bridge-vpls)#pseudowire instance 1 [local]PE3(config-bridge-vpls)#pseudowire instance 2 [local]PE3(config-bridge-vpls)#commit

2.7

Configure a Hierarchical VPLS Topology This example configures four PE routers in an HVPLS topology.

Figure 3

HVPLS Topology

In Figure 3, the routers are configured as follows:

12

•

HUB_PE1, HUB_PE2, and HUB_PE3 are connected via hub pseudowires in a VPLS mesh network.

•

HUB_PE1 is configured with hub pseudowire connections to peer IP address 10.25.1.2 (HUB_PE2) and 10.25.1.3 (HUB_PE3), and a spoke pseudowire connection to peer IP address 10.25.1.4 (HUB_MTU-S).

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Configuration

•

HUB_PE2 is configured with hub pseudowire connections to peer IP address 10.25.1.1 (HUB_PE1) and 10.25.1.3 (HUB_PE3).

•

HUB_PE3 is configured with hub pseudowire connections to peer IP address 10.25.1.1 (HUB_PE1) and 10.25.1.2 (HUB_PE2).

•

MTU-S_PE4 is connected to the VPLS mesh network via spoke pseudowire to peer IP address 10.25.1.1 (HUB_PE1).

To configure an HVPLS topology, configure the routers as shown in the following sections.

2.7.1

Configure the HUB PE1 Router On the HUB_PE1 router, perform the following steps starting in global configuration mode. 1. Create peer profile for pseudowire connections to HUB_PE2, HUB_PE3, and MTU-S_PE4.

[local]HUB_PE1(config)#pseudowire peer-profile HUB_PE2 [local]HUB_PE1(config-pw-peer-profile)#peer 10.25.1.2 [local]HUB_PE1(config-pw-profile-peer)#exit [local]HUB_PE1(config-pw-peer-profile)#exit [local]HUB_PE1(config)#pseudowire peer-profile HUB_PE3 [local]HUB_PE1(config-pw-peer-profile)#peer 10.25.1.3 [local]HUB_PE1(config-pw-profile-peer)#exit [local]HUB_PE1(config-pw-peer-profile)#exit [local]HUB_PE1(config)#pseudowire peer-profile MTU-S_PE4 [local]HUB_PE1(config-pw-profile-peer)#peer 10.25.1.4 [local]HUB_PE1(config-pw-profile-peer)#exit [local]HUB_PE1(config-pw-peer-profile)#exit

2. Create pseudowire instances for HUB_PE2, HUB_PE3, and MTU-S_PE4. [local]HUB_PE1(config)#pseudowire instance 1 [local]HUB_PE1(config-pw-instance)#pw-id 100 [local]HUB_PE1(config-pw-instance)#peer-profile HUB_PE2 [local]HUB_PE1(config-pw-instance)#exit [local]HUB_PE1(config)#pseudowire instance 2 [local]HUB_PE1(config-pw-instance)#pw-id 100 [local]HUB_PE1(config-pw-instance)#peer-profile HUB_PE3 [local]HUB_PE1(config-pw-instance)#exit [local]HUB_PE1(config)#pseudowire instance 3 [local]HUB_PE1(config-pw-instance)#pw-id 1000 [local]HUB_PE1(config-pw-instance)#peer-profile MTU-S_PE4 [local]HUB_PE1(config-pw-instance)#exit

3. Configure the VPLS instance and associate the pseudowires with an existing bridge. [local]HUB_PE1(config)#bridge b1 [local]HUB_PE1(config-bridge)#vpls [local]HUB_PE1(config-bridge-vpls)#pseudowire instance 1 [local]HUB_PE1(config-bridge-vpls)#pseudowire instance 2 [local]HUB_PE1(config-bridge-vpls)#pseudowire instance 3 spoke [local]HUB_PE1(config-bridge-vpls)#commit

4. Confirm the configuration.

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

13

VPLS

[local]HUB_PE1(config-bridge-vpls)#show configuration pseudowire ... ! Pseudowire peer-profile configuration pseudowire peer-profile HUB_PE2 peer 10.25.1.2 ! pseudowire peer-profile HUB_PE3 peer 10.25.1.3 ! pseudowire peer-profile MTU-S_PE4 peer 10.25.1.4 ! Pseudowire instance configuration pseudowire instance 1 pw-id 100 peer-profile HUB_PE2 ! pseudowire instance 2 pw-id 100 peer-profile HUB_PE3 ! pseudowire instance 3 pw-id 1000 peer-profile MTU-S_PE4 ! ! ! end [local]HUB_PE1(config-bridge-vpls)#show configuration bridge ... bridge b1 vpls pseudowire instance 1 pseudowire instance 2 pseudowire instance 3 spoke ! end

2.7.2

Configure the HUB PE2 Router On the HUB_PE2 router, repeat the HUB_PE1 router configuration with pseudowires that provide connectivity to HUB_PE1 and HUB_PE3.

[local]HUB_PE2(config)#pseudowire peer-profile HUB_PE1 [local]HUB_PE2(config-pw-peer-profile)#peer 10.25.1.1 [local]HUB_PE2(config-pw-profile-peer)#exit [local]HUB_PE2(config-pw-peer-profile)#exit [local]HUB_PE2(config)#pseudowire peer-profile HUB_PE3 [local]HUB_PE2(config-pw-peer-profile)#peer 10.25.1.3 [local]HUB_PE2(config-pw-profile-peer)#exit [local]HUB_PE2(config-pw-peer-profile)#exit [local]HUB_PE2(config)#pseudowire instance 1 [local]HUB_PE2(config-pw-instance)#pw-id 100 [local]HUB_PE2(config-pw-instance)#peer-profile HUB_PE1 [local]HUB_PE2(config-pw-instance)#exit [local]HUB_PE2(config)#pseudowire instance 2 [local]HUB_PE2(config-pw-instance)#pw-id 100 [local]HUB_PE2(config-pw-instance)#peer-profile HUB_PE3 [local]HUB_PE2(config-pw-instance)#exit [local]HUB_PE2(config)#bridge b1 [local]HUB_PE2(config-bridge)#vpls [local]HUB_PE2(config-bridge-vpls)#pseudowire instance 1 [local]HUB_PE2(config-bridge-vpls)#pseudowire instance 2 [local]HUB_PE2(config-bridge-vpls)#commit

14

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Configuration

2.7.3

Configure the HUB PE3 Router On the HUB_PE3 router, repeat the HUB_PE1 router configuration with pseudowires that provide connectivity to HUB_PE1 and HUB_PE2.

[local]HUB_PE3(config)#pseudowire peer-profile HUB_PE1 [local]HUB_PE3(config-pw-peer-profile)#peer 10.25.1.1 [local]HUB_PE3(config-pw-profile-peer)#exit [local]HUB_PE3(config-pw-peer-profile)#exit [local]HUB_PE3(config)#pseudowire peer-profile HUB_PE2 [local]HUB_PE3(config-pw-peer-profile)#peer 10.25.1.2 [local]HUB_PE3(config-pw-profile-peer)#exit [local]HUB_PE3(config-pw-peer-profile)#exit [local]HUB_PE3(config)#pseudowire instance 1 [local]HUB_PE3(config-pw-instance)#pw-id 100 [local]HUB_PE3(config-pw-instance)#peer-profile HUB_PE1 [local]HUB_PE3(config-pw-instance)#exit [local]HUB_PE3(config)#pseudowire instance 2 [local]HUB_PE3(config-pw-instance)#pw-id 100 [local]HUB_PE3(config-pw-instance)#peer-profile HUB_PE2 [local]HUB_PE3(config-pw-instance)#exit [local]HUB_PE3(config)#bridge b1 [local]HUB_PE3(config-bridge)#vpls [local]HUB_PE3(config-bridge-vpls)#pseudowire instance 1 [local]HUB_PE3(config-bridge-vpls)#pseudowire instance 2 [local]HUB_PE3(config-bridge-vpls)#commit

2.7.4

Configure the MTU-S PE4 Router To complete the example configuration, repeat the HUB_PE1 router configuration on router MTU-S_PE4, with a spoke pseudowire that provides connectivity to HUB_PE1.

[local]MTU-S_PE4(config)#pseudowire peer-profile HUB_PE1 [local]MTU-S_PE4(config-pw-peer-profile)#peer 10.25.1.1 [local]MTU-S_PE4(config-pw-profile-peer)#exit [local]MTU-S_PE4(config-pw-peer-profile)#exit [local]MTU-S_PE4(config)#pseudowire instance 1 [local]MTU-S_PE4(config-pw-instance)#pw-id 1000 [local]MTU-S_PE4(config-pw-instance)#peer-profile HUB_PE1 [local]MTU-S_PE4(config-pw-instance)#exit [local]MTU-S_PE4(config)#bridge b1 [local]MTU-S_PE4(config-bridge)#vpls [local]MTU-S_PE4(config-bridge-vpls)#pseudowire instance 1 spoke [local]MTU-S_PE4(config-bridge-vpls)#commit

2.8

Configure VPLS Pseudowire Redundancy This example configures a backup pseudowire for the bridge b1 on the MTU-S_PE4 router.

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

15

VPLS

Figure 4

HVPLS Topology with VPLS Pseudowire Redundancy

In Figure 4, the MTU-S_PE4 router is configured as follows: •

The backup peer IP address is 10.25.1.3.

•

The pseudowire redundancy mode is set to master-slave, which implies one endpoint of the redundant set of pseudowires is designated as master and is responsible for selecting which pseudowire both endpoints must use to forward traffic.

•

The router is configured to wait 100 seconds before it switches from the backup pseudowire to the primary pseudowire, after the primary comes back up, following a link failure.

To configure VPLS pseudowire redundancy, complete the following steps starting in global configuration mode. 1. Select the pseudowire peer profile and configure pseudowire redundancy attributes. [local]MTU-S_PE4(config)#pseudowire peer-profile HUB_PE1 [local]MTU-S_PE4(config-pw-peer-profile)#peer 10.25.1.1 [local]MTU-S_PE4(config-pw-profile-peer)#vc-type vlan [local]MTU-S_PE4(config-pw-profile-peer)#redundancy-mode master-slave [local]MTU-S_PE4(config-pw-profile-peer)#auto-revert-delay 100 [local]MTU-S_PE4(config-pw-profile-peer)#exit [local]MTU-S_PE4(config-pw-peer-profile)#exit

2. Select the pseudowire instance. [local]MTU-S_PE4(config)#pseudowire instance 1 [local]MTU-S_PE4(config-pw-instance)#peer-profile HUB_PE1

16

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Configuration

3. Create the backup pseudowire. [local]MTU-S_PE4(config-pw-instance-peer-profile)#backup-peer 10.25.1.3 pw-id 1000 [local]MTU-S_PE4(config-pw-instance-peer-profile)#commit [local]MTU-S_PE4(config-pw-instance-peer-profile)#exit [local]MTU-S_PE4(config-pw-instance)#exit

4. Confirm the configuration. [local]MTU-S_PE4(config)#show configuration bridge ... bridge b1 vpls pseudowire vlan 10 pseudowire instance 1 spoke ! end [local]MTU-S_PE4(config)#show configuration pseudowire ... ! Pseudowire peer-profile configuration pseudowire peer-profile HUB_PE1 peer 10.25.1.1 auto-revert-delay 100 redundancy-mode master-slave vc-type vlan ! ! Pseudowire instance configuration pseudowire instance 1 pw-id 1000 peer-profile HUB_PE1 backup-peer 10.25.1.3 pw-id 1000

2.9

Manually Switchover the VPLS Pseudowire This example forces a switchover from the active to the backup pseudowire on the MTU-S_PE4 router. To manually force a switchover from the active to backup pseudowire, enter the switchover pseudowire command in exec mode.

[local]MTU-S_PE4#switchover pseudowire 1000 peer 10.25.1.3

2.10

Associate a Split Horizon Group with a VPLS Pseudowire Instance You can use split horizon groups to restrict traffic between spoke pseudowires on the same bridge. Once configured, traffic is not forwarded to pseudowires belonging to the same group. Note:

All hub pseudowires associated with a bridge are part of an implicit split horizon group by default.

This example associates the shg1 split horizon group with the VPLS pseudowire instance 2. It assumes that the bridge, split horizon group, and the pseudowire instance already exist.

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

17

VPLS

To associate a split horizon group with a spoke VPLS pseudowire instance, perform the following steps starting in global configuration mode. 1. Select the bridge. [local]Ericsson(config)#bridge isp1 [local]Ericsson(config-bridge)#vpls

2. Select the pseudowire instance, and associate the split horizon group with the pseudowire instance. [local]Ericsson(config-bridge-vpls)#pseudowire instance 2 [local]Ericsson(config-bridge-vpls-pw-instance)#split-horizon-group shg1 [local]Ericsson(config-bridge-vpls-pw-instance)#commit

3. Confirm the configuration. [local]Ericsson(config-bridge-vpls-pw-instance)#show configuration bridge ... bridge isp1 description Bridge for all traffic to ISP2 split-horizon-group shg1 aging-time 18000 vpls pseudowire vlan untagged pseudowire instance 2 split-horizon-group shg1 ! end

2.11

Configure Static MAC Addresses for a Pseudowire Instance This example configures a list of static MAC address for pseudowire instance 12 on the VPLS enabled bridge isp1. Once configured, the bridge forwards all packets matching the configured MAC addresses to the pseudowire. To configure static MAC addresses for a pseudowire, perform the following steps starting in global configuration mode. 1. Select an existing bridge.

[local]Ericsson(config)#bridge isp1 [local]Ericsson(config-bridge)#vpls

2. Configure the pseudowire VLAN ID. [local]Ericsson(config-bridge-vpls)#pseudowire vlan 10

3. Associate an existing pseudowire instance with the bridge. [local]Ericsson(config-bridge-vpls)#pseudowire instance 12

4. Associate a bridge profile with the pseudowire instance.

18

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Configuration

[local]Ericsson(config-bridge-vpls-pw-instance)#bridge-profile ericsson

5. Configure static MAC addresses for the pseudowire instance. [local]Ericsson(config-bridge-vpls-pw-instance)#mac-entry static vlan 10 mac 01:02:03:04:0:06 [local]Ericsson(config-bridge-vpls-pw-instance)#mac-entry static vlan 10 mac 01:02:03:06:0:06 [local]Ericsson(config-bridge-vpls-pw-instance)#mac-entry static vlan 10 mac 01:02:03:06:0:07 [local]Ericsson(config-bridge-vpls-pw-instance)#commit

6. Confirm the configuration. [local]Ericsson(config-bridge-vpls-pw-instance)#show configuration bridge ... bridge isp1 description Bridge for all traffic to ISP1 aging-time 18000 vpls pseudowire vlan 10 pseudowire instance 12 mac-entry static vlan 10 mac 01:02:03:04:00:06 mac-entry static vlan 10 mac 01:02:03:06:00:06 mac-entry static vlan 10 mac 01:02:03:06:00:07

2.12

Configure Native VLAN for a Pseudowire Instance This example configures native VLAN 100 for pseudowire instance 1 on the VPLS enabled bridge isp1. Once configured, all untagged ingress packets are prepended with VLAN 100, and all ingress packets with a VLAN tag value of 0 get the tag rewritten to VLAN 100. To configure a native VLAN for a pseudowire instance, perform the following steps starting in global configuration mode. 1. Select the bridge and enter VPLS configuration mode.

[local]Ericsson(config)#bridge isp1 [local]Ericsson(config-bridge)#vpls

2. Configure the VLAN ID for the VPLS instance. [local]Ericsson(config-bridge-vpls)#pseudowire vlan 10

3. Select the pseudowire instance. [local]Ericsson(config-bridge-vpls)#pseudowire instance 12

4. Set the native VLAN ID. [local]Ericsson(config-bridge-vpls-pw-instance)#native vlan 100 [local]Ericsson(config-bridge-vpls-pw-instance)#commit

5. Confirm the configuration.

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

19

VPLS

[local]Ericsson(config-bridge-vpls-pw-instance)#show configuration bridge ... bridge isp1 description Bridge for all traffic to ISP1 aging-time 18000 vpls pseudowire vlan 10 pseudowire instance 12 native vlan 100

2.13

Map an LSP to a VPLS Pseudowire Instance This example maps the LSP to_pe1 to the VPLS pseudowire instance 1. To map an LSP to a VPLS pseudowire instance, complete the following steps starting in global configuration mode. 1. Create the peer-profile.

[local]Ericsson(config)#pseudowire peer-profile PE1 [local]Ericsson(config-pw-peer-profile)#peer 1.1.1.1 [local]Ericsson(config-pw-profile-peer)#vc-type vlan

2. Specify the pseudowire-to-LSP mapping. [local]Ericsson(config-pw-profile-peer)#tunnel lsp rsvp to_pe1 [local]Ericsson(config-pw-profile-peer)#exit

3. Create the pseudowire instance, set the pseudowire ID, and assign the peer-profile to the instance. [local]Ericsson(config)#pseudowire instance 1 [local]Ericsson(config-pw-instance)#pw-id 1000 [local]Ericsson(config-pw-instance)#peer-profile PE1 [local]Ericsson(config-pw-instance)#exit

4. Select an existing bridge and assign the pseudowire to the bridge. [local]Ericsson(config)#bridge b1 [local]Ericsson(config-bridge)#vpls [local]Ericsson(config-bridge-vpls)#pseudowire instance 1 spoke [local]Ericsson(config-bridge-vpls)#commit

5. Confirm the configuration. [local]Ericsson(config-bridge-vpls)#show configuration pseudowire ... ! Pseudowire peer-profile configuration pseudowire peer-profile PE1 peer 1.1.1.1 tunnel lsp rsvp to_pe1 vc-type vlan ! ! Pseudowire instance configuration pseudowire instance 1 pw-id 1000 peer-profile PE1

20

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Configuration

2.14

Configure MAC Withdrawal This example configures MAC withdrawal for pseudowire instance 1 on bridge isp1. Once configured, the router sends a MAC withdrawal message to VPLS hub peers when the pseudowire state changes to the UP state. To configure MAC withdrawal, complete the following steps starting in global configuration mode. 1. Select the bridge and enter bridge VPLS configuration mode.

[local]Ericsson(config)#bridge isp1 [local]Ericsson(config-bridge)#vpls

2. Select an existing spoke pseudowire instance. [local]Ericsson(config-bridge-vpls)#pseudowire instance 4 spoke

3. Configure MAC withdrawal. [local]Ericsson(config-bridge-vpls-pw-instance)#neighbor mac-flush [local]Ericsson(config-bridge-vpls-pw-instance)#commit

4. Confirm the configuration. [local]Ericsson(config-bridge-vpls-pw-instance)#show configuration bridge ... bridge isp1 description Bridge for all traffic to ISP1 aging-time 18000 vpls pseudowire instance 4 spoke neighbor mac-flush

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

21

VPLS

22

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Operations

3

Operations To monitor, troubleshoot, and administer VPLS features, perform the operations tasks described in Table 1. You can enter the show commands in any mode. The command syntax table displays only the root command. For the complete syntax, see the Command List.

Table 1

Operations Tasks for VPLS

Tasks

Root Command

Tests the status of a pseudowire.

ping mpls pw

Display the bridge forwarding table for one or more bridges.

show bridge table vlan

Display the number of VPLS pseudowire instances (hub and spoke) associated with a specific bridge.

show bridge table vlan

Display bridging-related configuration information including the number of associated pseudowires, configured VLANs, and pseudowire circuit types.

show configuration bridge

Display the current pseudowire configuration.

show configuration pseudowire

Display packet counter information for VPLS circuits.

show circuit counters vpls

Display the current status of a VPLS pseudowire instance.

show pseudowire

Force a switchover from the active to the backup pseudowire in a redundant configuration.

switchover pseudowire

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

23

VPLS

24

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

Reference List

Reference List

RFCs [1]

RFC 4446, Numeric Values of MPLS PW Types

[2]

RFC 4447, Distribution Mechanism for VC Labels

[3]

RFC 4448, Encapsulation of Ethernet using MPLS

[4]

RFC 4762, VPLS Using LDP Signalling

87/1543-CRA 119 1364/1 Uen A1 | 2014-04-08

25