peer

Configures a peer IP address in a bridge domain. A corresponding pseudowire (PW) interface is created when the peer IP address is configured.

Syntax

peer ip-address [ control-word ] [ cos num ] [ flow-label ] [ load-balance ] [ lsp lsp-name1, lsp-name2, . . . lsp-name32 ]

no peer [ ip-address [ lsp lsp-name1, lsp-name2, . . . lsp-name32 ] ]

Command Default

No PW interfaces are configured.

Parameters

ip-address: A PW IP address for a remote peer.
control-word: Enables control word for routing of pseudowire (PW) traffic to the peer.
cos num: Specifies a Class of Service (CoS) value for selecting a label-switched path to reach the peer. The value ranges is from 0 through 7.
flow-label: Enables flow label to support PW load balancing.
load-balance: Specifies load balancing. As many as16 alternate paths are used for load balancing.
lsp lsp-name1, lsp-name2, . . . lsp-name32: Specifies the name of a label-switched path. As many as 32 label-switched path names can be configured.

Modes

Bridge-domain configuration mode.

Usage Guidelines

The virtual connection identifier (VC ID) must be configured by using the vc-id command prior to configuring the peer IP address to create a PW interface.

The no form of the command deletes the peer IP address configuration and the PW interface that corresponds to the specified peer IP address.

The following are examples of configuration combinations that are allowed:

peer ip-address control-word
peer ip-address cos num
peer ip-address flow-label
peer ip-address load-balance
peer ip-address control-word flow-label
peer ip-address control-word cos num flow-label
peer ip-address control-word cos num flow-label load-balance
peer ip-address control-word cos num flow-label
peer ip-address control-word flow-label load-balance
peer ip-address cos num load-balance
peer ip-address cos num flow-label
peer ip-address load-balance cos
peer ip-address load-balance lsp lsp-name1, lsp-name2,...lsp-name32
no peer ip-address
no peer ip-address lsp lsp-name1, lsp-name2, . . . lsp-name32

Note

When a peer is already configured, you cannot add a CoS or load balancing configuration. To configure a CoS value or load-balancing, the peer must be removed by using the no peer command and reconfigured by specifying the required cos or load-balance options.

To remove the CoS or load-balance configuration, the peer configuration must be removed by using the no peer command.

Examples

The following example shows how to configure a peer IP address (10.12.12.12) for bridge domain 1 with the load-balance option.

device# configure terminal
device(config)# bridge-domain 1
device(config-bridge-domain-1)# peer 10.12.12.12 load-balance

The following example shows how to configure a peer IP address (10.12.12.12) for bridge domain 1 specifying two label-switched paths (lsp1 and lsp2).

device# configure terminal
device(config)# bridge-domain 1
device(config-bridge-domain-1)# peer 10.12.12.12 lsp lsp1 lsp2

The following example shows how to configure a peer IP address (10.1.1.1) for bridge domain 1 specifying load balancing and four label-switched paths (lsp1, lsp2, lsp3 and lsp4).

device# configure terminal
device(config)# bridge-domain 1
device(config-bridge-domain-1)# peer 10.1.1.1 load-balance lsp lsp1 lsp2 lsp3 lsp4

The following example shows the error message that is displayed when you try to configure the load-balance option for an existing peer. The peer configuration must be removed and reconfigured to specify the load-balance option, as shown in the example.

device# configure terminal
device(config)# bridge-domain 1
device(config-bridge-domain-1)# peer 15.15.15.15
device(config-bridge-domain-1)# peer 15.15.15.15 load-balance
Error: can not configure load-balance on existing peer. 
device(config-bridge-domain-1)#no peer 15.15.15.15
device(config-bridge-domain-1)# peer 15.15.15.15 load-balance