Example For Configuring Bit-Error-Triggered Vpn Route Switching - Huawei NetEngine80E Configuration Manual - Reliability

HUAWEI NetEngine80E/40E Router
Configuration Guide - Reliability
l
10.10.5 Example for Configuring Bit-Error-Triggered VPN Route
Switching
This section provides an example of configuring bit-error-triggered VPN route switching.
Networking Requirements
On an IP radio access network (RAN), if a bidirectional Resource Reservation Protocol-Traffic
Engineering (RSVP-TE) tunnel (consisting of two unidirectional tunnels) carries L3VPN
services, you can configure traffic engineering (TE) hot-standby to provide tunnel-level
protection and configure VPN fast reroute (FRR) to provide service-level protection. However,
these protection mechanisms cannot trigger protection switching based on random bit errors
caused by optical fiber aging or optical signal jitter. Random bit errors may degrade on an IP
RAN or even interrupt services in extreme cases.
To resolve this problem, configure bit-error-triggered VPN route switching. On the network
shown in
(RNC) needs to be transmitted over a bidirectional RSVP-TE tunnel between the user-end
provider edge (UPE) and a superstratum provider edge (SPE). VPN FRR needs to be configured
on the UPE and network provider edge (NPE). After you configure bit-error-triggered VPN route
switching, the UPE and NPE can reroute traffic if a bit error event occurs on the working
bidirectional RSVP-TE tunnel between the UPE and an SPE.
Issue 02 (2014-09-30)
#
return
RNC configuration file
#
sysname
RNC
#
vlan batch
10
#
interface Eth-
Trunk10
portswitch
port trunk allow-pass vlan
10
mode lacp-
static
#
interface
GigabitEthernet1/0/1
undo
shutdown
eth-trunk
10
#
interface
GigabitEthernet1/0/2
undo
shutdown
eth-trunk
10
return
Figure 10-6, the VPN traffic sent from the NodeB to the radio network controller
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
10 Bit-Error-Triggered Protection Switching Configuration
1090