target-board

Function

The target-board command configures the mapping between a Layer 3 interface and a GRE service board.

The undo target-board command deletes the mapping.

By default, no mapping from a Layer 3 interface to a GRE service board is configured.

Format

target-board slot-number [ backup slave-slot-number ]

undo target-board

Parameters

Parameter	Description	Value
slot-number	Specifies the number of the slot where a GRE service board resides.	-
backup slave-slot-number	Specifies the number of the slot where the slave GRE service board resides.	-

Parameter

Description

Value

slot-number

Specifies the number of the slot where a GRE service board resides.

backup slave-slot-number

Specifies the number of the slot where the slave GRE service board resides.

Views

100GE interface view, 400GE interface view, 40GE interface view, Eth-Trunk sub-interface view, Eth-Trunk interface view, Layer 3 GE interface view, GE sub-interface view, Loopback interface view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
forwarding	write

Usage Guidelines

Usage Scenario

As a Layer 3 tunnel protocol for VPNs, GRE uses the tunneling technology. A tunnel is a virtual P2P connection and can be regarded as a virtual interface supporting only P2P connections. This virtual interface provides a channel for encapsulated data packets.

The following types of GRE tunnels are supported

GRE tunnel with the one-dimensional tunnel interface: also called distributed GRE tunnel. The tunnel interface is one-dimensional (named only by the interface number). GRE packets are encapsulated and decapsulated directly on the inbound interface board. If the multi-field classification and CAR services are configured simultaneously, bandwidth that services consume may double.
GRE tunnel with the three-dimensional tunnel interface: also called integrated GRE tunnel. The tunnel interface is three-dimensional (named by the slot ID, subcard ID, and interface number). GRE packets are encapsulated and decapsulated directly on a service processing board.
For an integrated GRE tunnel, whose tunnel interface must be three-dimensional (named by the slot ID, subcard ID, and interface number), the target-board command must be run before GRE is bound to the interface using the binding tunnel gre command. After the configuration is complete, the GRE tunnel sends packets received from the source tunnel interface to the corresponding GRE service boards for processing. If the target-board command is not run, the GRE tunnel interface must be one-dimensional.
If multiple tunnel service boards are configured on a device, the backup parameter can be run to specify a slave GRE tunnel service board for 1:1 protection, enhancing GRE service reliability. After 1:1 protection is configured, configure two GRE tunnels with the same source and destination on the master and slave GRE tunnel service boards. If the GRE tunnel on the master GRE tunnel service board works, the GRE tunnel on the slave GRE tunnel service board does not work. If the GRE tunnel on the master GRE tunnel service board fails, services are switched to the slave GRE tunnel service board.
The target-board [ backup ] applies only to the integrated GRE mode.
In integrated GRE mode, you can run the binding tunnel gre command to bind GRE to a source tunnel interface only after running the target-board [ backup ] command. specified in the target-board command must be the same as x of interface x/y/z bound to a tunnel.
After the interface is bound to LMP, the target-board command can still be configured but does not take effect for any service.

Precautions

The device working in 1:1 mode does not support the integrated GRE mode.

The target-board [ backup ] applies only to the integrated GRE mode.

In integrated GRE mode, you can run the binding tunnel gre command to bind GRE to a source tunnel interface only after running the target-board [ backup ] command. specified in the target-board command must be the same as x of interface x/y/z bound to a tunnel.

After the interface is bound to LMP, the target-board command can still be configured but does not take effect for any service.

Example

# Configure the mapping from GE 0/1/0 to the GRE service board in 1.

<HUAWEI> system-view
[~HUAWEI] interface GigabitEthernet 0/1/0
[*HUAWEI-GigabitEthernet0/1/0] target-board 1