01-02 Comprehensive Configuration Examples PDF
01-02 Comprehensive Configuration Examples PDF
Series Switches
Typical Configuration Examples 2 Comprehensive Configuration Examples
NOTICE
The solution that uses VXLAN to build virtual networks on campus networks is a
large- and medium-sized campus network solution (virtualization scenario). For
details about the solution, see the CloudCampus Solution.
Configuration Notes
Switch configurations used in this example apply to all versions of all S series
switches.
This example uses firewall configurations of USG6650 V500R001C60. For other
firewall configurations, see the corresponding documentation.
Networking Requirements
In Figure 2-1, a company has multiple departments that belong to different
network segments, and each department needs to access the Internet. It is
required that users access the Internet through the Layer 2 switch and firewall and
that the firewall function as the gateway of users.
Figure 2-1 Configuring a Layer 2 switch to work with a firewall for Internet access
Internet
GE0/0/1
Switch
GE0/0/2 GE0/0/3
VLAN 2 VLAN 3
PC1 PC2
IP: 192.168.1.2/24 IP: 192.168.2.2/24
Configuration Roadmap
The configuration roadmap is as follows:
1. Configure interface-based VLAN assignment on the switch for Layer 2
forwarding.
2. Configure the firewall as the gateway of users to implement Layer 3
forwarding across network segments through sub-interfaces or VLANIF
interfaces.
3. Configure the firewall as the DHCP server to assign IP addresses to users.
4. Configure a security interzone policy for the firewall so that packets of
different zones can be forwarded.
5. Configure the PAT function on the firewall to enable intranet users to access
the Internet.
Procedure
Step 1 Configure the switch.
# Configure the interfaces connected to users.
<HUAWEI> system-view
[HUAWEI] sysname Switch
[Switch] vlan batch 2 3
[Switch] interface gigabitethernet 0/0/2
[Switch-GigabitEthernet0/0/2] port link-type access //Set the link type of the interface to access.
[Switch-GigabitEthernet0/0/2] port default vlan 2 //Add the interface to VLAN 2.
[Switch-GigabitEthernet0/0/2] quit
[Switch] interface gigabitethernet 0/0/3
[Switch-GigabitEthernet0/0/3] port link-type access
[Switch-GigabitEthernet0/0/3] port default vlan 3
[Switch-GigabitEthernet0/0/3] quit
----End
Configuration Files
● Switch configuration file
#
sysname Switch
#
vlan batch 2 to 3
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 2 to 3
#
interface GigabitEthernet0/0/2
port link-type access
port default vlan 2
#
interface GigabitEthernet0/0/3
port link-type access
port default vlan 3
#
return
● USG configuration file (used when the firewall performs Layer 3 forwarding
through sub-interfaces)
#
interface GigabitEthernet1/0/1
#
interface GigabitEthernet1/0/1.1
vlan-type dot1q 2
ip address 192.168.1.1 255.255.255.0
dhcp select interface
dhcp server dns-list 114.114.114.114 223.5.5.5
#
interface GigabitEthernet1/0/1.2
vlan-type dot1q 3
ip address 192.168.2.1 255.255.255.0
dhcp select interface
dhcp server dns-list 114.114.114.114 223.5.5.5
#
interface GigabitEthernet1/0/2
ip address 200.0.0.2 255.255.255.0
#
firewall zone trust
set priority 85
add interface GigabitEthernet1/0/1
add interface GigabitEthernet1/0/1.1
add interface GigabitEthernet1/0/1.2
#
action permit
#
nat-policy
rule name policy_nat1
source-zone trust
destination-zone untrust
source-address 192.168.0.0 mask 255.255.0.0
action nat address-group addressgroup1
#
return
Related Content
Videos
Connecting an S Series Switch Acting as a Layer 2 Switch to a Firewall
Configuration Notes
● This example uses firewall configurations of USG6650 V500R001C60. For
other firewall configurations, see the corresponding documentation.
● For the products and versions applicable when a switch functions as a DHCP
server, see Examples for Applicable Products and Versions.
Networking Requirements
In Figure 2-2, a company has multiple departments that belong to different
network segments, and each department needs to access the Internet. It is
required that users access the Internet through the Layer 3 switch and firewall and
that the Layer 3 switch function as the gateway of users.
Figure 2-2 Configuring a Layer 3 switch to work with a firewall for Internet access
Internet
Firewall
GE1/0/1
IP: 192.168.100.1/24 VLANIF 100
GE0/0/1 IP: 192.168.100.2/24
Switch functions as
the gateway of PCs
GE0/0/2 GE0/0/3
VLAN 2 VLAN 3
IP: 192.168.1.1/24 IP: 192.168.2.1/24
PC1 PC2
IP: 192.168.1.2/24 IP: 192.168.2.2/24
Configuration Roadmap
The configuration roadmap is as follows:
1. Configure the switch as the gateway of users to allow users to communicate
across network segments through VLANIF interfaces.
2. Configure the switch as the DHCP server to assign IP addresses to users.
3. Configure an interzone security policy for the firewall so that packets of
different zones can be forwarded.
4. Configure the PAT function on the firewall to enable intranet users to access
the Internet.
Procedure
Step 1 Configure the switch.
# Configure the interfaces connected to users and corresponding VLANIF
interfaces.
<HUAWEI> system-view
[HUAWEI] sysname Switch
[Switch] vlan batch 2 3
[Switch] interface gigabitethernet 0/0/2
[Switch-GigabitEthernet0/0/2] port link-type access //Set the link type of the interface to access.
[Switch-GigabitEthernet0/0/2] port default vlan 2 //Add the interface to VLAN 2.
[Switch-GigabitEthernet0/0/2] quit
[Switch] interface gigabitethernet 0/0/3
[Switch-GigabitEthernet0/0/3] port link-type access
[Switch-GigabitEthernet0/0/3] port default vlan 3
[Switch-GigabitEthernet0/0/3] quit
[Switch] interface vlanif 2
[Switch-Vlanif2] ip address 192.168.1.1 24
[Switch-Vlanif2] quit
[Switch] interface vlanif 3
[Switch-Vlanif3] ip address 192.168.2.1 24
[Switch-Vlanif3] quit
----End
Configuration Files
● Switch configuration file
#
sysname Switch
#
vlan batch 2 to 3 100
#
dhcp enable
#
interface Vlanif2
ip address 192.168.1.1 255.255.255.0
dhcp select interface
dhcp server dns-list 114.114.114.114 223.5.5.5
#
interface Vlanif3
ip address 192.168.2.1 255.255.255.0
dhcp select interface
S3700-HI V200R001C00
S6730S-H V200R019C10
Layer 2 Switch
Layer 2 switches perform only Layer 2 forwarding instead of Layer 3 forwarding.
That is, Layer 2 switches support only Layer 2 switches instead of Layer 3 features
such as routing.
Layer 2 switches are typically deployed at the access layer and cannot function as
gateways of users.
Configuration Notes
Switch configurations used in this example apply to all versions of all S series
switches.
Networking Requirements
In Figure 2-3, a company has multiple departments that belong to different
network segments, and each department needs to access the Internet. It is
required that users access the Internet through the Layer 2 switch and router and
that the router function as the gateway of users.
Figure 2-3 Configuring a Layer 2 switch to work with a router for Internet access
Internet
GE0/0/1
Switch
GE0/0/2 GE0/0/3
VLAN 2 VLAN 3
PC1 PC2
IP: 192.168.1.2/24 IP: 192.168.2.2/24
Configuration Roadmap
The configuration roadmap is as follows:
Procedure
Step 1 Configure the switch.
<HUAWEI> system-view
[HUAWEI] sysname Switch
[Switch] vlan batch 2 3
[Switch] interface gigabitethernet 0/0/2
[Switch-GigabitEthernet0/0/2] port link-type access //Set the link type of the interface to access.
[Switch-GigabitEthernet0/0/2] port default vlan 2 //Add the interface to VLAN 2.
[Switch-GigabitEthernet0/0/2] quit
[Switch] interface gigabitethernet 0/0/3
[Switch-GigabitEthernet0/0/3] port link-type access
[Switch-GigabitEthernet0/0/3] port default vlan 3
[Switch-GigabitEthernet0/0/3] quit
# Configure the NAT function to enable intranet users to access the Internet.
[Router] acl number 2001
[Router-acl-basic-2001] rule 5 permit source 192.168.0.0 0.0.255.255 //NAT takes effect only for
source IP addresses on the network segment 192.168.0.0/16 and translates only source IP addresses of
outgoing packets on GE0/0/2.
[Router-acl-basic-2001] quit
[Router] interface gigabitethernet 0/0/2
[Router-GigabitEthernet0/0/2] nat outbound 2001
[Router-GigabitEthernet0/0/2] quit
Configuration Files
● Switch configuration file
#
sysname Switch
#
vlan batch 2 to 3
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk allow-pass vlan 2 to 3
#
interface GigabitEthernet0/0/2
port link-type access
port default vlan 2
#
interface GigabitEthernet0/0/3
port link-type access
port default vlan 3
#
return
● Router configuration file (used when the router performs Layer 3 forwarding
through sub-interfaces)
#
sysname Router
#
vlan batch 2 to 3
#
dhcp enable
#
acl number 2001
rule 5 permit source 192.168.0.0 0.0.255.255
#
interface GigabitEthernet0/0/1
#
interface GigabitEthernet0/0/1.1
dot1q termination vid 2
ip address 192.168.1.1 255.255.255.0
arp broadcast enable
dhcp select interface
dhcp server dns-list 114.114.114.114 223.5.5.5
#
interface GigabitEthernet0/0/1.2
dot1q termination vid 3
ip address 192.168.2.1 255.255.255.0
arp broadcast enable
dhcp select interface
dhcp server dns-list 114.114.114.114 223.5.5.5
#
interface GigabitEthernet0/0/2
ip address 200.0.0.2 255.255.255.0
nat outbound 2001
#
ip route-static 0.0.0.0 0.0.0.0 200.0.0.1
#
return
● Router configuration file (used when the router performs Layer 3 forwarding
through VLANIF interfaces)
#
sysname Router
#
vlan batch 2 to 3
#
dhcp enable
#
acl number 2001
rule 5 permit source 192.168.0.0 0.0.255.255
#
interface Vlanif2
ip address 192.168.1.1 255.255.255.0
dhcp select interface
dhcp server dns-list 114.114.114.114 223.5.5.5
#
interface Vlanif3
ip address 192.168.2.1 255.255.255.0
dhcp select interface
dhcp server dns-list 114.114.114.114 223.5.5.5
#
interface GigabitEthernet0/0/1
portswitch
port link-type trunk
port trunk allow-pass vlan 2 to 3
#
interface GigabitEthernet0/0/2
ip address 200.0.0.2 255.255.255.0
nat outbound 2001
#
ip route-static 0.0.0.0 0.0.0.0 200.0.0.1
#
return
Related Content
Videos
Connecting an S Series Switch Acting as a Layer 2 Switch to a Router
Configuration Notes
● This example uses router configurations of AR3600 V200R007C00SPCc00. For
other router configurations, see the corresponding documentation.
● For the products and versions applicable when a switch functions as a DHCP
server, see Examples for Applicable Products and Versions.
Networking Requirements
In Figure 2-4, a company has multiple departments that belong to different
network segments, and each department needs to access the Internet. It is
required that users access the Internet through the Layer 3 switch and router and
that the Layer 3 switch function as the gateway of users.
Figure 2-4 Configuring a Layer 3 switch to work with a router for Internet access
Internet
Router
GE0/0/1
IP: 192.168.100.1/24 VLANIF 100
GE0/0/1 IP: 192.168.100.2/24
Switch functions as
the gateway of PCs
GE0/0/2 GE0/0/3
VLAN 2 VLAN 3
IP: 192.168.1.1/24 IP: 192.168.2.1/24
PC1 PC2
IP: 192.168.1.2/24 IP: 192.168.2.2/24
Configuration Roadmap
The configuration roadmap is as follows:
1. Configure the switch as the gateway of users to allow users to communicate
across network segments through VLANIF interfaces.
2. Configure the switch as the DHCP server to assign IP addresses to users.
3. Configure the NAT function on the router to enable intranet users to access
the Internet.
Procedure
Step 1 Configure the switch.
# Configure the interfaces connected to users and corresponding VLANIF
interfaces.
<HUAWEI> system-view
[HUAWEI] sysname Switch
[Switch] vlan batch 2 3
[Switch] interface gigabitethernet 0/0/2
[Switch-GigabitEthernet0/0/2] port link-type access //Set the link type of the interface to access.
[Switch-GigabitEthernet0/0/2] port default vlan 2 //Add the interface to VLAN 2.
[Switch-GigabitEthernet0/0/2] quit
[Switch] interface gigabitethernet 0/0/3
[Switch-GigabitEthernet0/0/3] port link-type access
# Configure the NAT function to enable intranet users to access the Internet.
[Router] acl number 2001
[Router-acl-basic-2001] rule 5 permit source 192.168.0.0 0.0.255.255 //NAT takes effect only for source
IP addresses on the network segment 192.168.0.0/16 and translates only source IP addresses of outgoing
packets on GE0/0/2.
[Router-acl-basic-2001] quit
[Router] interface gigabitethernet 0/0/2
[Router-GigabitEthernet0/0/2] nat outbound 2001
[Router-GigabitEthernet0/0/2] quit
----End
Configuration Files
● Switch configuration file
#
sysname Switch
#
vlan batch 2 to 3 100
#
dhcp enable
#
interface Vlanif2
ip address 192.168.1.1 255.255.255.0
dhcp select interface
dhcp server dns-list 114.114.114.114 223.5.5.5
#
interface Vlanif3
ip address 192.168.2.1 255.255.255.0
dhcp select interface
dhcp server dns-list 114.114.114.114 223.5.5.5
#
interface Vlanif100
ip address 192.168.100.2 255.255.255.0
#
interface GigabitEthernet0/0/1
port link-type access
port default vlan 100
#
interface GigabitEthernet0/0/2
port link-type access
port default vlan 2
#
interface GigabitEthernet0/0/3
port link-type access
port default vlan 3
#
ip route-static 0.0.0.0 0.0.0.0 192.168.100.1
#
return
interface GigabitEthernet0/0/1
ip address 192.168.100.1 255.255.255.0
#
interface GigabitEthernet0/0/2
ip address 200.0.0.2 255.255.255.0
nat outbound 2001
#
ip route-static 0.0.0.0 0.0.0.0 200.0.0.1
ip route-static 192.168.0.0 255.255.0.0 192.168.100.2
#
return
S3700-HI V200R001C00
S6730S-H V200R019C10
● Provide the network address translation (NAT) outbound and NAT server
functions to translate between private and public network addresses, so that
internal users can access the Internet and Internet users can access internal
servers.
● Support the construction of VPNs through the Internet so that branches of the
enterprise can communicate over VPNs.
● Encrypt data to protect data integrity and confidentiality, ensuring service
transmission security.
● Egress devices of small- and medium-scale campus networks must be reliable,
secure, low-cost, and easy to maintain.
Configuration Notes
This configuration example:
Networking Requirements
The headquarters and branch of an enterprise are located in different cities and
far from each other. The headquarters has two departments (A and B), and the
branch has only one department. A cross-regional enterprise campus network
needs to be constructed to meet the following requirements:
● Both users in the headquarters and branch have access to the Internet. In the
headquarters, users in Department A can access the Internet, but users in
Department B are not allowed to access the Internet. In the branch, all users
can access the Internet.
● The headquarters has a web server to provide WWW service so that external
users can access the internal server.
● The headquarters and branch need to communicate through VPNs over the
Internet and communication contents must be protected.
● The headquarters' campus network egress requires link-level reliability and
device-level reliability.
● The branch does not need high reliability.
redundant, and secure design and applies to small- and medium-scale enterprise
or branch campus networks.
Figure 2-5 Configuring egress devices for small- and medium-sized campus
networks or branch networks
Eth0/0/2
GE0/0/1 SwitchA
GE2/0/0
Enterprise
branch RouterC
GE1/0/0
A
Internet
RouterE
l
l
e
e
Tunn
Tunn
RouterD
c
c
IPSe
B C
IPSe
Enterprise
GE1/0/0 GE1/0/0
headquarters
OSPF
RouterA RouterB
Area 0
Eth-Trunk1 Eth-Trunk1
VRRP VRID1
Web Server Eth-Trunk3 Eth-Trunk4
GE0/0/5 CORE
Eth-Trunk1 Eth-Trunk2
Eth-Trunk1
Eth-Trunk1
Solution Overview
● Deploy Huawei S2700&S3700 switches (ACC1, ACC2, and SwitchA) at the
access layer, deploy Huawei S5700 switches (CORE) at the core layer, and
deploy Huawei AR3200 routers (RouterA, RouterB, and RouterC) at the
campus network egress.
● In the headquarters, use redundancy between two AR egress routers (RouterA
and RouterB) to ensure device-level reliability. In the branch, deploy one AR
router as the egress router.
● In the headquarters, set up a stack (CORE) between two S5700 core switches
to ensure device-level reliability.
● In the headquarters, deploy Eth-Trunks between access switches, the CORE,
and egress routers to ensure link-level reliability.
● In the headquarters, assign a VLAN to each department and transmit services
between departments at Layer 3 through VLANIF interfaces of the CORE.
● Use the CORE of the headquarters as the gateway for users and servers, and
deploy a DHCP server to assign IP addresses to users.
● Deploy the gateway for branch users on the egress router.
● Deploy VRRP between the two egress routers of the headquarters to ensure
reliability.
● Construct an Internet Protocol Security (IPSec) VPN between the
headquarters and branch over the Internet to enable communication while
ensuring data transmission security.
● Deploy Open Shortest Path First (OSPF) between the two egress routers and
CORE of the headquarters to advertise user routes for future capacity
expansion and maintenance.
Configuration Roadmap
The configuration roadmap is as follows:
3. Deploy routes.
To steer uplink traffic of devices, configure a default route with the VRRP
virtual address as the next hop on the CORE of the headquarters, and
configure a default route on each egress router of the headquarters and
branch, with the next hop pointing to the IP address of the connected carrier
network device (public network gateway address).
To steer the return traffic of two egress routers of the headquarters, configure
OSPF between the two egress routers and CORE, and advertise all user
network segments on the CORE into OSPF and then to the two egress routers.
On RouterD, to steer traffic generated by access to the web server from
external networks, configure two static routes of which the destination
address is the public network address of the web server and next-hop
addresses are uplink interface addresses of the two egress routers. To ensure
simultaneous route switchover and VRRP switchover, set the route with next
hop pointing to RouterA as the preferred one. When this route fails, the route
with next hop pointing to RouterB takes effect.
4. Configure NAT outbound.
To enable internal users to access the Internet, configure NAT on the uplink
interfaces of the two egress routers for translation between private network
addresses and public network addresses. Use an ACL to permit the source IP
address of packets from Department A so that users in Department A can
access the Internet while users in Department B cannot.
5. Configure a NAT server.
To enable external users to access the internal web server, configure a NAT
server on the uplink interfaces of the two egress routers to translate between
the public and private network addresses of the server.
6. Deploy IPSec VPN.
To enable users in the headquarters and branch to communicate through a
VPN, configure IPSec VPN between the egress routers of the headquarters
and branch for secure communication.
For the enterprise internal network configuration, see "Small- and Mid-Sized Campus
Networks" in the HUAWEI S Series Campus Switches Quick Configuration.
Data Plan
Table 2-3, Table 2-4, and Table 2-5 provide the data plan.
Eth-Trunk2 GE0/0/2
GE1/0/2
Eth-Trunk3 GE0/0/3
GE1/0/3
Eth-Trunk4 GE0/0/4
GE1/0/4
All Eth-Trunk interfaces work in Link Aggregation Control Protocol (LACP) mode.
Procedure
Step 1 Configure Eth-Trunks between the CORE and two egress routers of the
headquarters.
# Configure the CORE.
<HUAWEI> system-view
[HUAWEI] sysname CORE
[CORE] interface eth-trunk 3
[CORE-Eth-Trunk3] mode lacp
[CORE-Eth-Trunk3] quit
[CORE] interface eth-trunk 4
[CORE-Eth-Trunk4] mode lacp
[CORE-Eth-Trunk4] quit
[CORE] interface gigabitethernet 0/0/3
[CORE-GigabitEthernet0/0/3] eth-trunk 3
[CORE-GigabitEthernet0/0/3] quit
[CORE] interface gigabitethernet 1/0/3
[CORE-GigabitEthernet1/0/3] eth-trunk 3
[CORE-GigabitEthernet1/0/3] quit
[CORE] interface gigabitethernet 0/0/4
[CORE-GigabitEthernet0/0/4] eth-trunk 4
[CORE-GigabitEthernet0/0/4] quit
[CORE] interface gigabitethernet 1/0/4
[CORE-GigabitEthernet1/0/4] eth-trunk 4
[CORE-GigabitEthernet1/0/4] quit
[RouterA-GigabitEthernet2/0/1] eth-trunk 1
[RouterA-GigabitEthernet2/0/1] quit
Step 3 Deploy VRRP. Configure VRRP between RouterA and RouterB of the headquarters,
and configure RouterA as the master device and RouterB as the backup device.
# Configure RouterA.
[RouterA] interface Eth-Trunk 1.100
[RouterA-Eth-Trunk1.100] vrrp vrid 1 virtual-ip 10.10.100.1
[RouterA-Eth-Trunk1.100] vrrp vrid 1 priority 120
[RouterA-Eth-Trunk1.100] vrrp vrid 1 track interface GigabitEthernet1/0/0 reduced 40
[RouterA-Eth-Trunk1.100] quit
//To prevent service interruption in the case of an uplink failure on RouterA, associate the VRRP status with
the uplink interface of RouterA. The association ensures a fast VRRP switchover when the uplink fails.
# Configure RouterB.
[RouterB] interface Eth-Trunk 1.100
[RouterB-Eth-Trunk1.100] vrrp vrid 1 virtual-ip 10.10.100.1
[RouterB-Eth-Trunk1.100] quit
After the configuration is complete, a VRRP group should have been set up
between RouterA and RouterB. You can run the display vrrp command to view
the VRRP status of the two egress routers.
2. Deploy OSPF. Configure OSPF between two egress routers (RouterA and
RouterB) and CORE of the headquarters so that the two egress routers can
learn return routes from user network segments.
# Configure RouterA (egress router) of the headquarters.
[RouterA] ospf 1 router-id 10.1.1.1
[RouterA-ospf-1] area 0
[RouterA-ospf-1-area-0.0.0.0] network 10.10.100.0 0.0.0.255
[RouterA-ospf-1-area-0.0.0.0] quit
When the uplink of RouterA is interrupted, the following actions are triggered:
a. VRRP master/backup switchover between two egress routers (RouterA
and RouterB) is implemented through association between the VRRP
status and uplink interface status of the two egress routers.
# Configure RouterB.
[RouterB] interface GigabitEthernet1/0/0
[RouterB-GigabitEthernet1/0/0] nat server protocol tcp global 202.10.100.3 www inside 10.10.30.2 8080
[RouterB-GigabitEthernet1/0/0] quit
# After the configuration is complete, run the display nat server command to
view NAT server configuration. The following uses the display on RouterA as an
example.
[RouterA] display nat server
Total : 1
Step 7 Deploy IPSec VPN so that the headquarters and branch can communicate through
the VPN over the Internet and data communication can be protected.
1. Configure ACLs to permit the data flows to be protected by IPSec.
# Configure RouterA (egress router) of the headquarters.
[RouterA] acl 3001
[RouterA-acl-adv-3001] rule 5 permit ip source 10.10.10.0 0.0.0.255 destination 10.10.200.0
0.0.0.255 //Configure an ACL to permit the data flow to be protected by IPSec.
[RouterA-acl-adv-3001] rule 10 permit ip source 10.10.20.0 0.0.0.255 destination 10.10.200.0
0.0.0.255 //Configure an ACL to permit the data flow to be protected by IPSec.
[RouterA-acl-adv-3001] quit
Flag Description:
RD--READY ST--STAYALIVE RL--REPLACED FD--FADING TO--TIMEOUT
HRT--HEARTBEAT LKG--LAST KNOWN GOOD SEQ NO. BCK--BACKED UP
===============================
Interface: GigabitEthernet1/0/0
Path MTU: 1500
===============================
-----------------------------
IPSec policy name: "ipsec_vpn"
Sequence number : 10
Acl Group : 3001
Acl rule :5
Mode : ISAKMP
-----------------------------
Connection ID :5
Encapsulation mode: Tunnel
Tunnel local : 203.10.1.2
Tunnel remote : 202.10.1.2
Flow source : 10.10.200.0/255.255.255.0 0/0
Flow destination : 10.10.10.0/255.255.255.0 0/0
Qos pre-classify : Disable
-----------------------------
IPSec policy name: "ipsec_vpn"
Sequence number : 10
Acl Group : 3001
Acl rule : 10
Mode : ISAKMP
-----------------------------
Connection ID :6
Encapsulation mode: Tunnel
Tunnel local : 203.10.1.2
Tunnel remote : 202.10.1.2
Flow source : 10.10.200.0/255.255.255.0 0/0
Flow destination : 10.10.20.0/255.255.255.0 0/0
Qos pre-classify : Disable
-----------------------------
IPSec policy name: "ipsec_vpn"
Sequence number : 20
Acl Group : 3001
Acl rule :5
Mode : ISAKMP
-----------------------------
Connection ID :4
-----------------------------
IPSec policy name: "ipsec_vpn"
Sequence number : 20
Acl Group : 3001
Acl rule : 10
Mode : ISAKMP
-----------------------------
Connection ID :7
Encapsulation mode: Tunnel
Tunnel local : 203.10.1.2
Tunnel remote : 202.10.2.2
Flow source : 10.10.200.0/255.255.255.0 0/0
Flow destination : 10.10.20.0/255.255.255.0 0/0
Qos pre-classify : Disable
# Run the ping command to test the connectivity between the headquarters and
branch.
PC1>ping 10.10.200.2
The preceding command output shows that PC1 and PC5, and PC3 and PC5 can
communicate with each other, and the headquarters and branch can communicate
through the VPN over the Internet.
# Verify the connectivity between departments of the headquarters and the
Internet. In the following example, ping the public network gateway 202.10.1.1 of
the headquarters from PC1 and PC3.
PC1>ping 202.10.1.1
The preceding command output shows that users (such as PC1) in Department A
can access the public network but users (such as PC3) in Department B cannot.
----End
Configuration Files
● Core switch configuration file
#
sysname CORE
#
vlan batch 100
#
interface Vlanif100
#
interface Eth-Trunk4
port link-type trunk
port trunk allow-pass vlan 100
mode lacp
#
interface GigabitEthernet0/0/3
eth-trunk 3
#
interface GigabitEthernet0/0/4
eth-trunk 4
#
interface GigabitEthernet1/0/3
eth-trunk 3
#
interface GigabitEthernet1/0/4
eth-trunk 4
#
ospf 1 router-id 10.3.3.3
area 0.0.0.0
network 10.10.100.0 0.0.0.255
network 10.10.10.0 0.0.0.255
network 10.10.20.0 0.0.0.255
network 10.10.30.0 0.0.0.255
#
ip route-static 0.0.0.0 0.0.0.0 10.10.100.1
#
return
● RouterA configuration file
#
sysname RouterA
#
acl number 3000
rule 5 deny ip source 10.10.10.0 0.0.0.255 destination 10.10.200.0 0.0.0.255
rule 10 deny ip source 10.10.20.0 0.0.0.255 destination 10.10.200.0 0.0.0.255
rule 15 permit ip source 10.10.10.0 0.0.0.255
acl number 3001
rule 5 permit ip source 10.10.10.0 0.0.0.255 destination 10.10.200.0 0.0.0.255
rule 10 permit ip source 10.10.20.0 0.0.0.255 destination 10.10.200.0 0.0.0.255
#
ipsec proposal tran1
esp authentication-algorithm sha2-256
esp encryption-algorithm aes 128
#
ike proposal 5
encryption-algorithm aes-cbc-128
#
ike peer vpn v1
pre-shared-key cipher "@J*U2S*(7F,YWX*NZ55OA!!
ike-proposal 5
dpd type periodic
dpd idle-time 10
remote-address 203.10.1.2
#
ipsec policy ipsec_vpn 10 isakmp
security acl 3001
ike-peer vpn
proposal tran1
#
interface Eth-Trunk1
undo portswitch
mode lacp-static
#
interface Eth-Trunk1.100
dot1q termination vid 100
ip address 10.10.100.2 255.255.255.0
vrrp vrid 1 virtual-ip 10.10.100.1
vrrp vrid 1 priority 120
vrrp vrid 1 track interface GigabitEthernet1/0/0 reduced 40
arp broadcast enable
#
interface GigabitEthernet1/0/0
ip address 202.10.1.2 255.255.255.0
ipsec policy ipsec_vpn
nat server protocol tcp global 202.10.100.3 www inside 10.10.30.2 8080
nat outbound 3000
#
interface GigabitEthernet2/0/0
eth-trunk 1
#
interface GigabitEthernet2/0/1
eth-trunk 1
#
ospf 1 router-id 10.1.1.1
area 0.0.0.0
network 10.10.100.0 0.0.0.255
#
ip route-static 0.0.0.0 0.0.0.0 202.10.1.1
#
return
● RouterB configuration file
#
sysname RouterB
#
acl number 3000
rule 5 deny ip source 10.10.10.0 0.0.0.255 destination 10.10.200.0 0.0.0.255
rule 10 deny ip source 10.10.20.0 0.0.0.255 destination 10.10.200.0 0.0.0.255
rule 15 permit ip source 10.10.10.0 0.0.0.255
acl number 3001
rule 5 permit ip source 10.10.10.0 0.0.0.255 destination 10.10.200.0 0.0.0.255
rule 10 permit ip source 10.10.20.0 0.0.0.255 destination 10.10.200.0 0.0.0.255
#
ipsec proposal tran1
esp authentication-algorithm sha2-256
esp encryption-algorithm aes 128
#
ike proposal 5
encryption-algorithm aes-cbc-128
#
ike peer vpn v1
pre-shared-key cipher "@J*U2S*(7F,YWX*NZ55OA!!
ike-proposal 5
dpd type periodic
dpd idle-time 10
remote-address 203.10.1.2
#
ipsec policy ipsec_vpn 10 isakmp
security acl 3001
ike-peer vpn
proposal tran1
#
interface Eth-Trunk1
undo portswitch
mode lacp-static
#
interface Eth-Trunk1.100
dot1q termination vid 100
ip address 10.10.100.3 255.255.255.0
vrrp vrid 1 virtual-ip 10.10.100.1
arp broadcast enable
#
interface GigabitEthernet1/0/0
ip address 202.10.2.2 255.255.255.0
ipsec policy ipsec_vpn
nat server protocol tcp global 202.10.100.3 www inside 10.10.30.2 8080
nat outbound 3000
#
interface GigabitEthernet2/0/0
eth-trunk 1
#
interface GigabitEthernet2/0/1
eth-trunk 1
#
ospf 1 router-id 10.2.2.2
area 0.0.0.0
network 10.10.100.0 0.0.0.255
#
ip route-static 0.0.0.0 0.0.0.0 202.10.2.1
#
return
● Configuration file of the branch egress router RouterC
#
sysname RouterC
#
acl number 3000
rule 5 deny ip source 10.10.200.0 0.0.0.255 destination 10.10.10.0 0.0.0.255
rule 10 deny ip source 10.10.200.0 0.0.0.255 destination 10.10.20.0 0.0.0.255
rule 15 permit ip source 10.10.200.0 0.0.0.255
acl number 3001
rule 5 permit ip source 10.10.200.0 0.0.0.255 destination 10.10.10.0 0.0.0.255
rule 10 permit ip source 10.10.200.0 0.0.0.255 destination 10.10.20.0 0.0.0.255
#
ipsec proposal tran1
esp authentication-algorithm sha2-256
esp encryption-algorithm aes 128
#
ike proposal 5
encryption-algorithm aes-cbc-128
#
ike peer vpnr1 v1
pre-shared-key cipher "@J*U2S*(7F,YWX*NZ55OA!!
ike-proposal 5
dpd type periodic
dpd idle-time 10
remote-address 202.10.1.2
#
ike peer vpnr2 v1
pre-shared-key cipher "@J*U2S*(7F,YWX*NZ55OA!!
ike-proposal 5
dpd type periodic
dpd idle-time 10
remote-address 202.10.2.2
#
ipsec policy ipsec_vpn 10 isakmp
security acl 3001
ike-peer vpnr1
proposal tran1
#
ipsec policy ipsec_vpn 20 isakmp
security acl 3001
ike-peer vpnr2
proposal tran1
#
interface GigabitEthernet1/0/0
ip address 203.10.1.2 255.255.255.0
ipsec policy ipsec_vpn
nat outbound 3000
#
ip route-static 0.0.0.0 0.0.0.0 203.10.1.1
#
return
Internet
Access Access
point point
GE0/0/2 GE0/0/2
Router 1 Router 2
GE0/0/1 GE0/0/1
OSPF 0
GE1/0/1 GE1/0/1
GE1/0/7 GE1/0/7
FW 1 FW 2
GE2/0/4 GE2/0/4
GE2/0/3 GE2/0/3
Eth-Trunk 10 Eth-Trunk 20
Swich1 Swich2
(master) (standby)
CSS
HTTP server
Department A Department B
AGG1 AGG2
Device Selection
This example applies to the following products and versions. If other products or
versions are used, the configurations may vary. For details, see a related
configuration manual.
Deployment Overview
● Routing deployment
– Configure a loopback interface address as the router ID on each device.
– Add egress routers, firewalls, and core switches to OSPF area 0. Configure
egress routers as Autonomous System Border Routers (ASBRs) and core
switches as Area Border Routers (ABRs).
– Configure Open Shortest Path First (OSPF) areas 1 and 2 for departments
A and B, respectively, and configure the two OSPF areas as Not-So-
Stubby Areas (NSSAs) to reduce the number of LSAs transmitted between
OSPF areas.
– To guide uplink traffic on each device, configure a default route pointing
to the firewall on the core switch, configure a default route pointing to
the egress router on the firewall, and configure a default route pointing
to the address of the interconnected interface (public gateway address)
of the carrier's device.
● Reliability deployment
You are advised to use CSS+iStack+Eth-Trunk to build a loop-free
Ethernet.
– Deploy cluster switch system (CSS) on core switches and intelligent Stack
(iStack) on aggregation switches to ensure device-level reliability.
– To improve link reliability, use Eth-Trunks between core switches and
firewalls, between core switches and aggregation switches, and between
aggregation switches and access switches.
– Deploy the Huawei Redundancy Protocol (HRP) on firewalls to
implement load balancing.
● Dynamic Host Configuration Protocol (DHCP) deployment
– Configure the core switch as the DHCP server to allocate IP addresses to
users.
– Configure the DHCP relay function on the aggregation switch to ensure
that the DHCP server can allocate IP addresses to users.
● Network Address Translation (NAT) deployment
– To ensure that users on the internal network can access the Internet,
configure NAT on uplink interfaces of the two egress routers to translate
private addresses into public addresses. Configure an access control list
(ACL) to match the source IP address of department A so that users of
department A can access the Internet and users of department B cannot
access the Internet.
– To ensure that users on the external network can access the HTTP server,
configure the NAT server on two egress routers.
● Security deployment
Configure security policies on firewalls to filter traffic and ensure network
security.
Data Plan
Device Interfac Membe VLANIF IP Remote Remote
e r Interfac Address Device Interface
Number Interfac e Number
e
GE2/1/0
/3
GE2/1/0
/4
Configuration Roadmap
The configuration roadmap is as follows:
Step Configuration Roadmap Involved Product
Procedure
Step 1 Configure CSS on core switches.
1. Connect cables of CSS cards. CSS card EH1D2VS08000 is used as an example.
– One CSS card can only be connected to one CSS card in the other chassis but not
the local chassis.
– An interface in group 1 of a CSS card can be connected to any interface in group 1
of the CSS card on the other chassis. The requirements for interfaces in group 2 are
the same.
– CSS cards have the same number of cluster cables connected. (If the CSS cards
have different numbers of cluster cables connected, the total cluster bandwidth is
limited to the cluster with the least cluster cables connected.) In addition,
interfaces on CSS cards are connected sequentially based on the interface number.
2. Configure the CSS function on Switch1 and use CSS card connection (the
default value does not need to be configured). Use the default CSS ID 1 (the
default value does not need to be configured) and set the CSS priority to 100.
<HUAWEI> system-view
[HUAWEI] set css mode css-card //Default setting. You do not need to run this command. The step
is used for reference.
[HUAWEI] set css id 1 //Default setting. You do not need to run this command. The step is used for
reference.
[HUAWEI] set css priority 100 //The default CSS priority is 1. Change the priority of the master
switch to be higher than that of the standby switch.
[HUAWEI] css enable
Warning: The CSS configuration takes effect only after the system is rebooted. The next CSS mode is
CSS-Card. Reboot now? [Y/N]:Y //Restart the switch.
3. Configure the CSS function on Switch2. Use CSS card connection (the default
value does not need to be configured). Set the CSS ID to 2 and use default
CSS priority 1 (the default value does not need to be configured).
<HUAWEI> system-view
[HUAWEI] set css id 2 //The default CSS ID is 1. Change the CSS ID to 2.
[HUAWEI] css enable
Warning: The CSS configuration takes effect only after the system is rebooted. The next CSS mode is
CSS-Card. Reboot now? [Y/N]:Y //Restart the switch.
After the CSS is established, subsequent operations will be performed on the master
switch and data will be automatically synchronized to the standby switch. In a CSS,
the physical interface number is in the format of interface type chassis ID/slot ID/
interface card ID/interface sequence number, for example, 10GE1/1/0/9.
Step 2 Configure iStack on aggregation switches. S5720-EI series switches are used as an
example. Service interface stacking is used.
Switch3 and Switch4 are used as an example. The configurations of Switch5 and Switch6
are similar, and are not mentioned here.
Connect cables after the iStack configuration is complete.
1. Configure logical stack interfaces and add physical member interfaces to
them.
Physical member interfaces of logical stack interface stack-port n/1 on one switch can
only be connected to the interfaces of stack-port n/2 on a neighboring switch.
Warning: Enabling stack function may cause configuration loss on the interface, continue?[Y/
N]:Y
Info: This operation may take a few seconds. Please wait for a moment.......
[Switch4-stack-port0/2] quit
3. Power off Switch3 and Switch4 and connect GE0/0/28 interfaces using the SFP
+ stack cable.
Run the save command to save the configurations before you power off the switches.
Stack-port 0/1 of one switch must be connected to stack-port 0/2 of another switch.
Otherwise, the stack cannot be set up.
iStack Link
Switch3 Switch4
You can check the master and standby switches, that is, the stack is set up
successfully.
Step 3 Configure inter-chassis Eth-Trunks between the CSS and firewalls and between the
CSS and aggregation switches.
# In the CSS, create Eth-Trunk 100 to connect to AGG1 and add member
interfaces to Eth-Trunk 100.
[CSS] interface eth-trunk 100 //Create Eth-Trunk 100 to connect to AGG1.
[CSS-Eth-Trunk100] quit
[CSS] interface gigabitethernet 1/2/0/3
[CSS-GigabitEthernet1/2/0/3] eth-trunk 100
[CSS-GigabitEthernet1/2/0/3] quit
[CSS] interface gigabitethernet 2/2/0/3
[CSS-GigabitEthernet2/2/0/3] eth-trunk 100
[CSS-GigabitEthernet2/2/0/3] quit
# In the CSS, create Eth-Trunk 200 to connect to AGG2 and add member
interfaces to Eth-Trunk 200.
[CSS] interface eth-trunk 200 //Create Eth-Trunk 200 to connect to AGG2.
[CSS-Eth-Trunk200] quit
[CSS] interface gigabitethernet 1/2/0/4
[CSS-GigabitEthernet1/2/0/4] eth-trunk 200
[CSS-GigabitEthernet1/2/0/4] quit
# Configure AGG2.
[AGG2] interface eth-trunk 200 //Create Eth-Trunk 200 to connect to the CSS.
[AGG2-Eth-Trunk200] quit
[AGG2] interface gigabitethernet 1/0/1
[AGG2-GigabitEthernet1/0/1] eth-trunk 200
[AGG2-GigabitEthernet1/0/1] quit
[AGG2] interface gigabitethernet 2/0/1
[AGG2-GigabitEthernet2/0/1] eth-trunk 200
[AGG2-GigabitEthernet2/0/1] quit
[AGG2] interface eth-trunk 600 //Create Eth-Trunk 600 to connect to the access switch.
[AGG2-Eth-Trunk600] quit
[AGG2] interface gigabitethernet 1/0/5
[AGG2-GigabitEthernet1/0/5] eth-trunk 600
[AGG2-GigabitEthernet1/0/5] quit
[AGG2] interface gigabitethernet 2/0/5
[AGG2-GigabitEthernet2/0/5] eth-trunk 600
[AGG2-GigabitEthernet2/0/5] quit
# Configure Router2.
[Router2] interface loopback 0
[Router2-LoopBack0] ip address 2.2.2.2 32 //Configure the IP address as the router ID.
[Router2-LoopBack0] quit
[Router2] interface gigabitethernet 0/0/2
[Router2-GigabitEthernet0/0/2] ip address 202.10.2.1 24 //Configure an IP address for the interface
connected to the external network.
[Router2-GigabitEthernet0/0/2] quit
[Router2] interface gigabitethernet 0/0/1
[Router2-GigabitEthernet0/0/1] ip address 10.2.1.1 24 //Configure an IP address for the interface
connected to FW2.
[Router2-GigabitEthernet0/0/1] quit
# Configure FW1.
[FW1] interface loopback 0
[FW1-LoopBack0] ip address 3.3.3.3 32 //Configure the IP address as the router ID.
[FW1-LoopBack0] quit
[FW1] interface gigabitethernet 1/0/1
[FW1-GigabitEthernet1/0/1] ip address 10.1.1.2 24 //Configure an IP address for the interface connected
to Router1.
[FW1-GigabitEthernet1/0/1] quit
[FW1] interface gigabitethernet 1/0/7
[FW1-GigabitEthernet1/0/7] ip address 10.10.1.1 24 //Configure an IP address for the heartbeat interface
enabled with HSB.
[FW1-GigabitEthernet1/0/7] quit
[FW1] interface eth-trunk 10
[FW1-Eth-Trunk10] ip address 10.3.1.1 24 //Configure an IP address for the Eth-Trunk connected to the
CSS.
[FW1-Eth-Trunk10] quit
# Configure FW2.
[FW2] interface loopback 0
[FW2-LoopBack0] ip address 4.4.4.4 32 //Configure the IP address as the Router ID.
[FW2-LoopBack0] quit
[FW2] interface gigabitethernet 1/0/1
[FW2-GigabitEthernet1/0/1] ip address 10.2.1.2 24 //Configure an IP address for the interface connected
to Router2.
[FW2-GigabitEthernet1/0/1] quit
[FW2] interface gigabitethernet 1/0/7
[FW2-GigabitEthernet1/0/7] ip address 10.10.1.2 24 //Configure an IP address for the heartbeat interface
enabled with HSB.
[FW2-GigabitEthernet1/0/7] quit
[FW2] interface eth-trunk 20
[FW2-Eth-Trunk20] ip address 10.4.1.1 24 //Configure an IP address for the Eth-Trunk connected to the
CSS.
[FW2-Eth-Trunk20] quit
# Configure CSS.
[CSS] interface loopback 0
[CSS-LoopBack0] ip address 5.5.5.5 32 //Configure the IP address as the Router ID.
[CSS-LoopBack0] quit
[CSS] interface eth-trunk 10
[CSS-Eth-Trunk10] undo portswitch //By default, an Eth-Trunk works in Layer 2 mode. To use an Eth-
Trunk as a Layer 3 interface, run the undo portswitch command to switch the Eth-Trunk to Layer 3 mode.
[CSS-Eth-Trunk10] ip address 10.3.1.2 24 //Configure an IP address for the Eth-Trunk connected to FW1.
[CSS-Eth-Trunk10] quit
[CSS] interface eth-trunk 20
[CSS-Eth-Trunk20] undo portswitch //By default, an Eth-Trunk works in Layer 2 mode. To use an Eth-
Trunk as a Layer 3 interface, run the undo portswitch command to switch the Eth-Trunk to Layer 3 mode.
[CSS-Eth-Trunk20] ip address 10.4.1.2 24 //Configure an IP address for the Eth-Trunk connected to FW2.
[CSS-Eth-Trunk20] quit
[CSS] vlan batch 100 200 300 //Create VLANs in a batch.
[CSS] interface eth-trunk 100
[CSS-Eth-Trunk100] port link-type hybrid
[CSS-Eth-Trunk100] port hybrid pvid vlan 100
[CSS-Eth-Trunk100] port hybrid untagged vlan 100
[CSS-Eth-Trunk100] quit
[CSS] interface vlanif 100
[CSS-Vlanif100] ip address 10.5.1.1 24 //Configure an IP address for the interface connected to
aggregation switch AGG1.
[CSS-Vlanif100] quit
[CSS] interface eth-trunk 200
[CSS-Eth-Trunk200] port link-type hybrid
[CSS-Eth-Trunk200] port hybrid pvid vlan 200
[CSS-Eth-Trunk200] port hybrid untagged vlan 200
[CSS-Eth-Trunk200] quit
[CSS] interface vlanif 200
[CSS-Vlanif200] ip address 10.6.1.1 24 //Configure an IP address for the interface connected to
aggregation switch AGG2.
[CSS-Vlanif200] quit
[CSS] interface gigabitethernet 1/1/0/10 //Enter the view of the interface connected to the HTTP server.
[CSS-GigabitEthernet1/1/0/10] port link-type access
[CSS-GigabitEthernet1/1/0/10] port default vlan 300 //Add the access interface to VLAN 300.
[CSS-GigabitEthernet1/1/0/10] quit
[CSS] interface vlanif 300
[CSS-Vlanif300] ip address 10.100.1.1 24 //Configure an IP address for the interface connected to the
HTTP server.
[CSS-Vlanif300] quit
# Configure AGG1.
[AGG1] interface loopback 0
[AGG1-LoopBack0] ip address 6.6.6.6 32 //Configure the IP address as the router ID.
[AGG1-LoopBack0] quit
[AGG1] vlan batch 100 500
[AGG1] interface eth-trunk 100
[AGG1-Eth-Trunk100] port link-type hybrid
[AGG1-Eth-Trunk100] port hybrid pvid vlan 100
[AGG1-Eth-Trunk100] port hybrid untagged vlan 100
[AGG1-Eth-Trunk100] quit
[AGG1] interface vlanif 100
[AGG1-Vlanif100] ip address 10.5.1.2 24 //Configure an IP address for the interface connected to the CSS.
[AGG1-Vlanif100] quit
[AGG1] interface eth-trunk 500
[AGG1-Eth-Trunk500] port link-type hybrid
[AGG1-Eth-Trunk500] port hybrid pvid vlan 500
[AGG1-Eth-Trunk500] port hybrid untagged vlan 500
[AGG1-Eth-Trunk500] quit
[AGG1] interface vlanif 500
[AGG1-Vlanif500] ip address 192.168.1.1 24 //Configure an IP address for the interface connected to the
access switch and configure it as the gateway address of department A.
[AGG1-Vlanif500] quit
# Configure AGG2.
[AGG2] interface loopback 0
[AGG2-LoopBack0] ip address 7.7.7.7 32 //Configure the IP address as the router ID.
[AGG2-LoopBack0] quit
[AGG2] vlan batch 200 600
[AGG2] interface eth-trunk 200
[AGG2-Eth-Trunk200] port link-type hybrid
[AGG2-Eth-Trunk200] port hybrid pvid vlan 200
[AGG2-Eth-Trunk200] port hybrid untagged vlan 200
[AGG2-Eth-Trunk200] quit
[AGG2] interface vlanif 200
[AGG2-Vlanif200] ip address 10.6.1.2 24 //Configure an IP address for the interface connected to the CSS.
[AGG2-Vlanif200] quit
[AGG2] interface eth-trunk 600
[AGG2-Eth-Trunk600] port link-type hybrid
[AGG2-Eth-Trunk600] port hybrid pvid vlan 600
[AGG2-Eth-Trunk600] port hybrid untagged vlan 600
[AGG2-Eth-Trunk600] quit
[AGG2] interface vlanif 600
[AGG2-Vlanif600] ip address 192.168.2.1 24 //Configure an IP address for the interface connected to the
access switch and configure it as the gateway address of department B.
[AGG2-Vlanif600] quit
Step 5 On firewalls, configure security policies and zones that interfaces belong to.
trusted zone.
[FW2-zone-trust] quit
[FW2] firewall zone untrust
[FW2-zone-untrust] add interface gigabitethernet 1/0/1 //Add GE1/0/1 connected to the external
network to an untrusted zone.
[FW2-zone-untrust] quit
[FW2] firewall zone dmz
[FW2-zone-dmz] add interface gigabitethernet 1/0/7 //Add GE1/0/7 to the DMZ.
[FW2-zone-dmz] quit
# Configure Router1.
[Router1] router id 1.1.1.1
[Router1] ospf 1 //Configure OSPF.
[Router1-ospf-1] area 0 //Configure a backbone area.
[Router1-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 //Configure the device to advertise the
network segment connected to FW1 to the OSPF backbone area.
[Router1-ospf-1-area-0.0.0.0] quit
[Router1-ospf-1] quit
# Configure Router2.
[Router2] router id 2.2.2.2
[Router2] ospf 1 //Configure OSPF.
[Router2-ospf-1] area 0 //Configure a backbone area.
[Router2-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 //Configure the device to advertise the
network segment connected to FW2 to the OSPF backbone area.
[Router2-ospf-1-area-0.0.0.0] quit
[Router2-ospf-1] quit
# Configure FW1.
[FW1] router id 3.3.3.3
[FW1] ospf 1 //Configure OSPF.
[FW1-ospf-1] area 0 //Configure a backbone area.
[FW1-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255 //Configure the device to advertise the
network segment connected to Router1 to the OSPF backbone area.
[FW1-ospf-1-area-0.0.0.0] network 10.3.1.0 0.0.0.255 //Configure the device to advertise the
network segment connected to the CSS to the OSPF backbone area.
[FW1-ospf-1-area-0.0.0.0] quit
[FW1-ospf-1] quit
# Configure FW2.
[FW2] router id 4.4.4.4
[FW2] ospf 1 //Configure OSPF.
[FW2-ospf-1] area 0 //Configure a backbone area.
[FW2-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255 // //Configure the device to advertise the
network segment connected to Router2 to the OSPF backbone area.
[FW2-ospf-1-area-0.0.0.0] network 10.4.1.0 0.0.0.255 //Configure the device to advertise the
network segment connected to the CSS to the OSPF backbone area.
[FW2-ospf-1-area-0.0.0.0] quit
[FW2-ospf-1] quit
[CSS-ospf-1-area-0.0.0.1] quit
[CSS-ospf-1] area 2 //Configure OSPF area 2.
[CSS-ospf-1-area-0.0.0.2] network 10.6.1.0 0.0.0.255 //Configure the device to advertise the
network segment connected to AGG2 to OSPF area 2.
[CSS-ospf-1-area-0.0.0.2] nssa //Configure OSPF area 1 as an NSSA.
[CSS-ospf-1-area-0.0.0.2] quit
[CSS-ospf-1] quit
# Configure AGG1.
[AGG1] ospf 1 //Configure OSPF.
[AGG1-ospf-1] area 1 //Configure OSPF area 1.
[AGG1-ospf-1-area-0.0.0.1] network 10.5.1.0 0.0.0.255 //Configure the device to advertise the
network segment connected to the CSS to OSPF area 1.
[AGG1-ospf-1-area-0.0.0.1] network 192.168.1.0 0.0.0.255 //Configure the device to advertise the
user network segment to OSPF area 1.
[AGG1-ospf-1-area-0.0.0.1] nssa //Configure OSPF area 1 as an NSSA.
[AGG1-ospf-1-area-0.0.0.1] quit
[AGG1-ospf-1] quit
# Configure AGG2.
[AGG2] ospf 1 //Configure OSPF.
[AGG2-ospf-1] area 2 //Configure OSPF area 2.
[AGG2-ospf-1-area-0.0.0.2] network 10.6.1.0 0.0.0.255 //Configure the device to advertise the
network segment connected to the CSS to OSPF area 2.
[AGG2-ospf-1-area-0.0.0.2] network 192.168.2.0 0.0.0.255 //Configure the device to advertise the
user network segment to OSPF area 1.
[AGG2-ospf-1-area-0.0.0.2] nssa //Configure OSPF area 2 as an NSSA.
[AGG2-ospf-1-area-0.0.0.2] quit
[AGG2-ospf-1] quit
Check the routing table of the stack. AGG1 is used as an example. You can
see that routes are generated for network segments on the internal network
and one default route is generated for traffic going out of the NSSA.
[AGG1] display ip routing-table
Route Flags: R - relay, D - download to fib, T - to vpn-instance
------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 14 Routes : 14
# Check the routing table in the CSS. You can see routes are generated for
network segments on the internal network and the costs of routes to firewalls
are the same, indicating that load balancing is used.
[CSS] display ip routing-table
Route Flags: R - relay, D - download to fib, T - to vpn-instance
------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 18 Routes : 19
Configure clients to obtain IP addresses through the DHCP server and check the
address pool in the CSS. You can see that two IP addresses (Used: 2) have been
allocated and there are 503 remaining IP addresses (Idle: 503). That is, IP
addresses are allocated successfully.
[CSS] display ip pool
-----------------------------------------------------------------------
Pool-name : poola
Pool-No :0
Position : Local Status : Unlocked
Gateway-0 : 192.168.1.1
Mask : 255.255.255.0
VPN instance : --
-----------------------------------------------------------------------
Pool-name : poolb
Pool-No :1
Position : Local Status : Unlocked
Gateway-0 : 192.168.2.1
Mask : 255.255.255.0
VPN instance : --
IP address Statistic
Total :506
Used :2 Idle :503
Expired :0 Conflict :1 Disable :0
Users on the internal network use private IP addresses. To meet the requirements,
perform NAT configurations:
● To allow users of department A to access the Internet, configure NAT on
egress routers to translate private IP addresses into public IP addresses.
● To allow users on the external network to access the HTTP server, configure
the NAT server on egress routers.
Assume that the carrier allocates the following public IP addresses to enterprise users:
202.10.1.2 to 202.10.1.10 and 202.10.2.2 to 202.10.2.10. The IP addresses of 202.10.1.2 and
202.10.2.2 are used by Router1 and Router 2 respectively to connect to the external
network. The IP address 202.10.1.10 and 202.10.2.10 is used by users on the external
network to access the HTTP server. Users on the internal network use the remaining public
IP addresses to access the Internet.
# Configure the NAT server on Router1 and Router2 so that users on the external
network can access the HTTP server.
[Router1] interface gigabitethernet 0/0/2
[Router1-GigabitEthernet0/0/2] nat server protocol tcp global 202.10.1.10 http inside 10.100.1.10
http //Configure the device to allow Internet users to access the HTTP server of the company.
[Router1-GigabitEthernet0/0/2] quit
[Router2] interface gigabitethernet 0/0/2
[Router2-GigabitEthernet0/0/2] nat server protocol tcp global 202.10.2.10 http inside 10.100.1.10
http //Configure the device to allow Internet users to access the HTTP server of the company.
[Router2-GigabitEthernet0/0/2] quit
After HRP is configured, the configuration and session of the active device are automatically
backed up to the standby device.
[FW2] hrp interface gigabitethernet 1/0/7 remote 10.10.1.1 //Configure a heartbeat interface and
enable HRP.
[FW2] hrp enable //Enable HRP.
HRP_B[FW2] hrp mirror session enable //Enable quick session backup. In HRP networking, if packets are
received and sent along different paths, the quick session backup function ensures that session information
on the active firewall is immediately synchronized to the standby firewall. When the active firewall fails,
packets can be forwarded by the standby firewall. This function ensures nonstop sessions of internal and
external users.
The local and remote firewalls have the same priority and are both in active state,
indicating that the two firewalls are in load balancing state.
Step 10 Configure attack defense on firewalls.
To protect internal servers against potential SYN Flood attacks and HTTP Flood
attacks, enable defense against SYN Flood attacks and HTTP Flood attacks on
firewalls.
The attack defense threshold is used for reference. Set this value according to actual
network traffic.
HRP_M[FW1] firewall defend syn-flood enable
HRP_M[FW1] firewall defend syn-flood zone untrust max-rate 20000
HRP_M[FW1] firewall defend udp-flood enable
HRP_M[FW1] firewall defend udp-flood zone untrust max-rate 1500
HRP_M[FW1] firewall defend icmp-flood enable
HRP_M[FW1] firewall defend icmp-flood zone untrust max-rate 20000
HRP_M[FW1] firewall blacklist enable
HRP_M[FW1] firewall defend ip-sweep enable
HRP_M[FW1] firewall defend ip-sweep max-rate 4000
HRP_M[FW1] firewall defend port-scan enable
HRP_M[FW1] firewall defend port-scan max-rate 4000
HRP_M[FW1] firewall defend ip-fragment enable
HRP_M[FW1] firewall defend ip-spoofing enable
----End
Configuration Files
● Router1 configuration file
#
sysname Router1
#
acl number 2000
rule permit source 192.168.1.0 0.0.0.255
#
nat address-group 1 202.10.1.3 202.10.1.9
#
interface GigabitEthernet 0/0/1
ip address 10.1.1.1 255.255.255.0
#
interface GigabitEthernet 0/0/2
ip address 202.10.1.1 255.255.255.0
nat outbound 2000 address-group 1
nat server protocol tcp global 202.10.1.10 http inside 10.100.1.10 http
#
interface LoopBack0
set priority 85
add interface Eth-Trunk10
#
firewall zone dmz
set priority 50
add interface GigabitEthernet1/0/7
#
firewall zone untrust
set priority 5
add interface GigabitEthernet 1/0/1
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.3.1.0 0.0.0.255
#
ip route-static 0.0.0.0 0.0.0.0 10.1.1.1
#
policy interzone local trust outbound
policy 1
action permit
policy source 10.3.1.0 mask 24
policy source 10.5.1.0 mask 24
policy source 192.168.1.0 mask 24
#
policy interzone local untrust inbound
policy 2
action permit
policy source 10.1.1.0 mask 24
#
policy interzone trust untrust inbound
policy 3
action permit
policy source 10.1.1.0 mask 24
#
policy interzone trust untrust outbound
policy 4
action permit
policy source 192.168.1.0 mask 24
#
firewall defend syn-flood enable
firewall defend syn-flood zone untrust max-rate 20000
firewall defend udp-flood enable
firewall defend udp-flood zone untrust max-rate 1500
firewall defend icmp-flood enable
firewall defend icmp-flood zone untrust max-rate 20000
firewall blacklist enable
firewall defend ip-sweep enable
firewall defend ip-sweep max-rate 4000
firewall defend port-scan enable
firewall defend port-scan max-rate 4000
firewall defend ip-fragment enable
firewall defend ip-spoofing enable
#
return
#
sysname CSS
#
vlan batch 100 200 300
#
dhcp enable
#
ip pool poola
gateway-list 192.168.1.1
network 192.168.1.0 mask 255.255.255.0
#
ip pool poolb
gateway-list 192.168.2.1
network 192.168.2.0 mask 255.255.255.0
#
interface Vlanif 100
ip address 10.5.1.1 255.255.255.0
dhcp select global
#
interface Vlanif 200
ip address 10.6.1.1 255.255.255.0
dhcp select global
#
interface Vlanif 300
ip address 10.100.1.100 255.255.255.0
#
interface Eth-Trunk 10
undo portswitch
ip address 10.3.1.2 255.255.255.0
#
interface Eth-Trunk 20
undo portswitch
ip address 10.4.1.2 255.255.255.0
#
interface Eth-Trunk 100
port link-type hybrid
port hybrid pvid vlan 100
port hybrid untagged vlan 100
#
interface Eth-Trunk 200
port link-type hybrid
port hybrid pvid vlan 200
port hybrid untagged vlan 200
#
interface GigabitEthernet 1/1/0/1
port link-type access
port default vlan 300
#
interface GigabitEthernet 1/1/0/3
eth-trunk 10
#
interface GigabitEthernet 1/1/0/4
eth-trunk 20
#
interface GigabitEthernet 1/2/0/3
eth-trunk 100
#
interface GigabitEthernet 1/2/0/4
eth-trunk 200
#
interface GigabitEthernet 2/1/0/3
eth-trunk 10
#
interface GigabitEthernet 2/1/0/4
eth-trunk 20
#
interface GigabitEthernet 2/2/0/3
eth-trunk 100
#
#
sysname AGG2
#
vlan batch 200 600
#
interface Vlanif 200
ip address 10.6.1.2 255.255.255.0
#
interface Vlanif 600
ip address 192.168.2.1 255.255.255.0
dhcp select relay
dhcp relay server-ip 10.6.1.1
#
interface Eth-Trunk 200
port link-type hybrid
port hybrid pvid vlan 200
port hybrid untagged vlan 200
#
interface Eth-Trunk 600
port link-type hybrid
port hybrid pvid vlan 600
port hybrid untagged vlan 600
#
interface GigabitEthernet 1/0/1
eth-trunk 200
#
interface GigabitEthernet 2/0/1
eth-trunk 200
#
interface GigabitEthernet 1/0/5
eth-trunk 600
#
interface GigabitEthernet 2/0/5
eth-trunk 600
#
interface LoopBack0
ip address 7.7.7.7 255.255.255.255
#
ospf 1 router-id 7.7.7.7
area 0.0.0.2
network 10.6.1.0 0.0.0.255
network 192.168.2.0 0.0.0.255
nssa
#
return
Networking Requirements
At the egress of a large-sized campus network, core switches connect to routers to
access the Internet through upstream interfaces. Firewalls connect to the core
switches in bypass mode to filter service traffic.
To simplify network and improve reliability, a switch cluster is deployed at the core
layer.
HRP (active/standby mode) is deployed on firewalls. If one firewall fails, services
are switched to another firewall.
Each of the core switches is dual homed to two egress routers, and VRRP is
configured between routers to ensure reliability.
To improve link reliability, Eth-Trunks are configured between core switches and
egress routers, core switches and firewalls, and two firewalls.
The networking diagram is as follows:
Campus egress
Router 1 Router 2
VRRP VRID 1
FW 1
CSS HRP
FW 2
Aggregation Aggregation
switch switch
Service Service
network 1 network 2
In Layer 3 forwarding environment, traffic inside and outside the campus network
is directly forwarded by switches, but does not pass through FW1 and FW2. When
traffic needs to be filtered by FWs, the VRF function must be configured on
switches. The CSS is divided into a virtual switch VRF-A and a root switch Public,
which are separated from each other.
Public is connected to the egress routers, and forwards traffic from the Internet to
FWs for filtering and traffic from FWs to the egress routers.
VRF-A is connected to the intranet, and forwards traffic from FWs to the intranet
and traffic from intranet to FWs for filtering.
The following logical network diagram shows the traffic forwarding paths.
Router 1 Router 2
10GE1/0/1 10GE1/0/2 10GE1/0/1 10GE1/0/2
Eth-Trunk1 Eth-Trunk1
Eth-Trunk1 Eth-Trunk2
Switch 1 Switch 2
(master) CSS
(backup)
Internet-side
Public
GE1/1/0/7 GE1/2/0/7 GE2/1/0/7 GE2/2/0/7
Eth-Trunk4 Eth-Trunk6
Eth-Trunk4 Eth-Trunk6
GE1/0/0 GE1/0/1 GE1/0/0 GE1/0/1
GE2/0/0 GE2/0/0
FW 1 GE2/0/1 GE2/0/1 FW 2
Eth-Trunk1 Eth-Trunk1
GE1/1/0 GE1/1/1 GE1/1/0 GE1/1/1
Eth-Trunk5 Eth-Trunk7
Eth-Trunk5 Eth-Trunk7
Intranet-side
GE1/3/0/1 GE1/3/0/2 VRF-A GE2/3/0/1 GE2/3/0/2
Eth-Trunk8 Eth-Trunk9
Aggregation Aggregation
switch switch
Service Service
network 1 network 2
In this example, the core switches work in Layer 3 mode. The firewalls connect to
Layer 3 switches through upstream and downstream interfaces. VRRP needs to be
configured on both upstream and downstream service interfaces of firewalls, as
shown below.
Router 1 Router 2
Eth-Trunk1 Eth-Trunk1
10.10.4.2/24 10.10.4.3/24
VRRP VRID 1
CSS
1OSPF
Virtual IP
Eth-Trunk1
3 Static route
10.10.4.100/24
Eth-Trunk2
OSPF VLANIF10
Eth-Trunk1 Eth-Trunk2
100 10.10.4.1/24
Area 0
CSS
Internet-side
Public CSS
2 Static route
Eth-Trunk4
Eth-Trunk6
Eth-Trunk4 Eth-Trunk6
2 Static route
VLANIF20
Virtual IP 10.10.2.1/24
10.10.2.5/24
Virtual IP CSS
1 Static route
10.10.3.5/24 Eth-Trunk5
Eth-Trunk7
Eth-Trunk5 Eth-Trunk7 VLANIF30
10.10.3.1/24
Intranet-side
VRF-A
CSS
Eth-Trunk8 Eth-Trunk9
VLANIF100 VLANIF200
10.10.100.1/24 10.10.200.1/24
Aggregation Aggregation
switch switch
Service Service
network 1 network 2
The traffic (in blue) from the intranet to the Internet is forwarded as follows:
1. When traffic from the intranet to the Internet reaches VRF-A, it is then
forwarded to the firewalls based on the static route (next hop is the
downstream VRRP virtual IP address of firewalls) configured on VRF-A.
2. After filtering the traffic, the firewalls forward traffic to Public based on the
static route (next hop is the CSS's VLANIF 20).
3. Public forwards traffic to routers based on the static route (next hop is the
router VRRP virtual IP address).
The traffic (in red) from the Internet to the intranet is forwarded as follows:
1. The traffic from the Internet to the intranet reaches the routers, and is then
forwarded to Public based on the OSPF routing table.
2. Public forwards the traffic to firewalls based on the static route (next hop is
the upstream VRRP virtual IP address of firewalls).
3. After filtering the traffic, the firewalls forward traffic to VRF-A based on the
static route (next hop is the CSS's VLANIF 30).
4. VRF-A forwards the traffic to aggregation switches based on OSPF routing
table, and then the aggregation switches forward the traffic to service
networks.
Device Selection
This example applies to the following products and versions. If other products or
versions are used, the configurations may vary. For details, see a related
configuration manual.
Data Plan
VRR - - - 10.10.4.100 - -
P of /24
Rout
er 1
and
Rout
er 2
VRR - - - 10.10.2.5/2 - -
P1 4
of
FW
1
and
FW
2
(ups
trea
m)
VRR - - - 10.10.3.5/2 - -
P2 4
of
FW
1
and
FW
2
(dow
nstre
am)
Configuration Roadmap
The configuration roadmap is as follows:
Procedure
Step 1 On switch 1 and switch 2: Configure CSSs.
1. Connect CSS cards through cables.
In the following figure, the S12700 switches have the CSS cards
EH1D2VS08000 installed. An S12700 has a maximum number of MPUs, SFUs,
and CSS cards installed. Each chassis must have at least one MPU and one
SFU installed. You are advised to install two SFUs and two CSS cards in each
chassis.
Step 2 Configure the inter-chassis Eth-Trunks between CSS and FWs and between CSS
and routers. Configure VLANIF interfaces on the CSS and assign IP addresses to
them.
1. Configure an inter-chassis Eth-Trunk between switches and routers. Configure
VLANIF interfaces and assign IP addresses to them.
# In the CSS, create Eth-Trunk1 to connect to Router1 and add member
interfaces to Eth-Trunk1.
<HUAWEI> system-view
[HUAWEI] sysname CSS //Rename the CSS.
[CSS] interface Eth-Trunk 1
[CSS-Eth-Trunk1] quit
[CSS] interface XGigabitethernet 1/4/0/0 //Add an interface on the master switch to Eth-Trunk1.
[CSS-XGigabitEthernet1/4/0/0] Eth-Trunk 1
[CSS-XGigabitEthernet1/4/0/0] quit
[CSS] interface XGigabitethernet 2/4/0/0 //Add an interface on the backup switch to Eth-Trunk1.
[CSS-XGigabitEthernet2/4/0/0] Eth-Trunk 1
[CSS-XGigabitEthernet2/4/0/0] quit
[CSS-XGigabitEthernet1/4/0/1] Eth-Trunk 2
[CSS-XGigabitEthernet1/4/0/1] quit
[CSS] interface XGigabitethernet 2/4/0/1 //Add an interface on the backup switch to Eth-Trunk2.
[CSS-XGigabitEthernet2/4/0/1] Eth-Trunk 2
[CSS-XGigabitEthernet2/4/0/1] quit
# In the CSS, create Eth-Trunk5 to connect VRF-A to FW1 and add member
interfaces to Eth-Trunk5.
[CSS] interface Eth-Trunk 5
[CSS-Eth-Trunk5] quit
[CSS] interface Gigabitethernet 1/1/0/8 //Add an interface on the master switch to Eth-Trunk5.
[CSS-Gigabitethernet1/1/0/8] Eth-Trunk 5
[CSS-Gigabitethernet1/1/0/8] quit
[CSS] interface Gigabitethernet 2/1/0/8 //Add an interface on the backup switch to Eth-Trunk5.
[CSS-Gigabitethernet2/1/0/8] Eth-Trunk 5
[CSS-Gigabitethernet2/1/0/8] quit
# In the CSS, create Eth-Trunk6 to connect Public to FW2 and add member
interfaces to Eth-Trunk6.
[CSS] interface Eth-Trunk 6
[CSS-Eth-Trunk6] quit
[CSS] interface Gigabitethernet 1/2/0/7 //Add an interface on the master switch to Eth-Trunk6.
[CSS-Gigabitethernet1/2/0/7] Eth-Trunk 6
[CSS-Gigabitethernet1/2/0/7] quit
[CSS] interface Gigabitethernet 2/2/0/7 //Add an interface on the backup switch to Eth-Trunk6.
[CSS-Gigabitethernet2/2/0/7] Eth-Trunk 6
[CSS-Gigabitethernet2/2/0/7] quit
# In the CSS, create Eth-Trunk7 to connect VRF-A to FW2 and add member
interfaces to Eth-Trunk7.
[FW1] interface Eth-Trunk 5 //Configure the interface connected to CSS and assign an IP address to it.
[FW1-Eth-Trunk5] ip address 10.10.3.2 24
[FW1-Eth-Trunk5] quit
[FW1] interface Gigabitethernet 1/1/0 //Add an interface to Eth-Trunk5.
[FW1-GigabitEthernet1/1/0] Eth-Trunk 5
[FW1-GigabitEthernet1/1/0] quit
[FW1] interface Gigabitethernet 1/1/1 //Add an interface to Eth-Trunk5.
[FW1-GigabitEthernet1/1/1] Eth-Trunk 5
[FW1-GigabitEthernet1/1/1] quit
[FW2] interface Eth-Trunk 7 //Configure the interface connected to CSS and assign an IP address to it.
[FW2-Eth-Trunk7] ip address 10.10.3.3 24
[FW2-Eth-Trunk7] quit
[FW2] interface Gigabitethernet 1/1/0 //Add an interface to Eth-Trunk7.
[FW2-GigabitEthernet1/1/0] Eth-Trunk 7
[FW2-GigabitEthernet1/1/0] quit
[FW2] interface Gigabitethernet 1/1/1 //Add an interface to Eth-Trunk7.
[FW2-GigabitEthernet1/1/1] Eth-Trunk 7
[FW2-GigabitEthernet1/1/1] quit
[FW2] interface Eth-Trunk 1 //Configure the interface between FW2 and FW1.
[FW2-Eth-Trunk1] ip address 10.1.1.2 24
[FW2-Eth-Trunk1] quit
[FW2] interface Gigabitethernet 2/0/0 //Add an interface to Eth-Trunk1.
[FW2-GigabitEthernet2/0/0] Eth-Trunk 1
[FW2-GigabitEthernet2/0/0] quit
[FW2] interface Gigabitethernet 2/0/1 //Add an interface to Eth-Trunk1.
[FW2-GigabitEthernet2/0/1] Eth-Trunk 1
[FW2-GigabitEthernet2/0/1] quit
Step 5 On routers: Configure VRRP. Configure Router1 as the VRRP master and Router2
as the VRRP backup.
# Configure Router1.
# Configure Router2.
[Router2] interface Eth-Trunk 1.100
[Router2-Eth-Trunk1.100] vrrp vrid 1 virtual-ip 10.10.4.100 //Configure the VRRP virtual IP address.
[Router2-Eth-Trunk1.100] quit
After the configuration is complete, a VRRP group should have been set up
between Router1 and Router2. You can run the display vrrp command to view the
VRRP status of Router1 and Router2.
# Check the VRRP status of Router1. The status is master.
[Router1] display vrrp
Eth-Trunk1.100 | Virtual Router 1
State : Master
Virtual IP : 10.10.4.100
Master IP : 10.10.4.2
PriorityRun : 120
PriorityConfig : 120
MasterPriority : 120
Preempt : YES Delay Time : 0 s
TimerRun : 1 s
TimerConfig : 1 s
Auth type : NONE
Virtual MAC : 0000-5e00-0101
Check TTL : YES
Config type : normal-vrrp
Create time : 2015-05-18 06:53:47 UTC-05:13
Last change time : 2015-05-18 06:54:14 UTC-05:13
Step 6 Configure routes between CSS and FWs and between CSS and routers.
1. Configure OSPF between switches and routers.
# Create VPN instance Public on CSS and bind the interfaces connected to
routers and firewalls to Public.
[CSS] ip vpn-instance Public //Create the VPN instance Public.
[CSS-vpn-instance-Public] ipv4-family
[CSS-vpn-instance-Public-af-ipv4] route-distinguisher 100:2
[CSS-vpn-instance-Public-af-ipv4] vpn-target 222:2 both
[CSS-vpn-instance-Public-af-ipv4] quit
[CSS-vpn-instance-Public] quit
# Configure a static route in Public to forward upstream traffic. Set the next
hop of the route to the VRRP virtual IP address of routers.
[CSS] ip route-static vpn-instance Public 0.0.0.0 0.0.0.0 10.10.4.100 //Configure a default route
for Public and set the next hop as the VRRP virtual IP address of the router.
# Configure Router2.
[Router2] ospf 100 router-id 3.3.3.3
[Router2-ospf-100] area 0
[Router2-ospf-100-area-0.0.0.0] network 10.10.4.0 0.0.0.255 //Advertise the routes on the network
segment connected to CSS to OSPF.
[Router2-ospf-100-area-0.0.0.0] quit
[Router2-ospf-100] quit
# After the configurations are complete, CSS, Router1, and Router2 can set up
neighbor relationships. For example, when you view OSPF neighbor
information on the CSS, you can find that Router1 and Router2 have set up
OSPF neighbor relationships with CSS and the neighbor status is Full.
[CSS] display ospf peer
OSPF Process 100 with Router ID 1.1.1.1
Neighbors
# Configure a default route in VRF-A. The next hop is the downstream VRRP 2
virtual IP address (VRID2) of firewalls.
[CSS] ip route-static vpn-instance VRF-A 0.0.0.0 0.0.0.0 10.10.3.5
[FW2] ip route-static 10.10.100.0 255.255.255.0 10.10.3.1 //For downstream traffic, the destination
address is on service network 1 and the next hop is the IP address of VLANIF 30 on VRF-A.
[FW2] ip route-static 10.10.200.0 255.255.255.0 10.10.3.1 //For downstream traffic, the destination
address is on service network 2 and the next hop is the IP address of VLANIF 30 on VRF-A.
In the routing table on VRF-A, the first line indicates that the next hop for the
traffic destined for the Internet is the VRRP VRID 2 virtual IP address
(10.10.3.5) of firewalls. This indicates that upstream traffic is forcibly directed
to firewalls for filtering.
[CSS] display ip routing-table vpn-instance Public
Route Flags: R - relay, D - download to fib, T - to vpn-instance
------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 7 Routes : 7
In the routing table on Public, the first line indicates that the next hop for the
traffic destined for the Internet is the VRRP VRID 1 virtual IP address
(10.10.4.100) of routers.
The fifth and sixth lines indicate that the next hop for the traffic destined for
service networks is the VRRP VRID 1 virtual IP address (10.10.3.5) of firewalls.
This indicates that downstream traffic is forcibly directed to firewalls for
filtering.
Step 7 Configure HRP on firewalls.
# Configure HRP on FW1 and set FW1 as master.
[FW1] interface Eth-Trunk 4
[FW1-Eth-Trunk4] vrrp vrid 1 virtual-ip 10.10.2.5 24 master //Configure VRRP group 1 on the upstream
# Check VRRP status. FW1 is the master and FW2 is the slave.
HRP_M[FW1] display vrrp
Eth-Trunk4 | Virtual Router 1
VRRP Group : Master
State : Master
Virtual IP : 10.10.2.5
Virtual MAC : 0000-5e00-0101
Primary IP : 10.10.2.2
PriorityRun : 120
PriorityConfig : 100
MasterPriority : 120
Preempt : YES Delay Time : 0 s
Advertisement Timer : 1
Auth type : NONE
Check TTL : YES
After HRP is configured, the configurations and sessions on the active firewall are
synchronized to the standby firewall; therefore, you only need to perform the following
configurations on the active firewall FW1.
You can find that the CSS and Router1 can ping each other.
# Ping the VRF-A VLANIF 100 on the CSS from Router1 to check the downlink
connectivity.
You can find that Router1 and CSS VLANIF 100 can ping each other.
----End
Configuration Files
● Router1 configuration file
#
sysname Router1
#
interface Eth-Trunk1
#
interface Eth-Trunk1.100
dot1q termination vid 10
ip address 10.10.4.2 255.255.255.0
vrrp vrid 1 virtual-ip 10.10.4.100
vrrp vrid 1 priority 120
#
interface XGigabitEthernet1/0/1
eth-trunk 1
#
interface XGigabitEthernet1/0/2
eth-trunk 1
#
ospf 100 router-id 2.2.2.2
area 0.0.0.0
network 10.10.4.0 0.0.0.255
#
return
#
interface Vlanif1
#
interface Vlanif10
ip binding vpn-instance Public
ip address 10.10.4.1 255.255.255.0
#
interface Vlanif20
ip binding vpn-instance Public
ip address 10.10.2.1 255.255.255.0
#
interface Vlanif30
ip binding vpn-instance VRF-A
ip address 10.10.3.1 255.255.255.0
#
interface Vlanif100
ip binding vpn-instance VRF-A
ip address 10.10.100.1 255.255.255.0
#
interface Vlanif200
ip binding vpn-instance VRF-A
ip address 10.10.200.1 255.255.255.0
#
interface Eth-Trunk1
port link-type trunk
port trunk allow-pass vlan 10
#
interface Eth-Trunk2
port link-type trunk
port trunk allow-pass vlan 10
#
interface Eth-Trunk4
port link-type trunk
port trunk allow-pass vlan 20
#
interface Eth-Trunk5
port link-type trunk
port trunk allow-pass vlan 30
#
interface Eth-Trunk6
port link-type trunk
port trunk allow-pass vlan 20
#
interface Eth-Trunk7
port link-type trunk
port trunk allow-pass vlan 30
#
interface Eth-Trunk8
port link-type trunk
port trunk allow-pass vlan 100
#
interface Eth-Trunk9
port link-type trunk
port trunk allow-pass vlan 200
#
interface Eth-Trunk1.100
dot1q termination vid 100
ip address 10.10.100.3 255.255.255.0
vrrp vrid 1 virtual-ip 10.10.100.1
arp broadcast enable
#
interface GigabitEthernet1/1/0/7
eth-trunk 4
#
interface GigabitEthernet1/1/0/8
eth-trunk 5
#
interface GigabitEthernet1/2/0/7
eth-trunk 6
#
interface GigabitEthernet1/2/0/8
eth-trunk 7
#
interface GigabitEthernet1/3/0/1
eth-trunk 8
#
interface GigabitEthernet1/3/0/2
eth-trunk 9
#
interface GigabitEthernet2/1/0/7
eth-trunk 4
#
interface GigabitEthernet2/1/0/8
eth-trunk 5
#
interface GigabitEthernet2/2/0/7
eth-trunk 6
#
interface GigabitEthernet2/2/0/8
eth-trunk 7
#
interface GigabitEthernet2/3/0/1
eth-trunk 8
#
interface GigabitEthernet2/3/0/2
eth-trunk 9
#
interface XGigabitEthernet1/4/0/0
eth-trunk 1
#
interface XGigabitEthernet1/4/0/1
eth-trunk 2
#
interface XGigabitEthernet2/4/0/0
eth-trunk 1
#
interface XGigabitEthernet2/4/0/1
eth-trunk 2
#
ospf 100 router-id 1.1.1.1 vpn-instance Public
import-route static
area 0.0.0.0
network 10.10.4.0 0.0.0.255
#
ip route-static vpn-instance VRF-A 0.0.0.0 0.0.0.0 10.10.3.5
ip route-static vpn-instance Public 0.0.0.0 0.0.0.0 10.10.4.100
ip route-static vpn-instance Public 10.10.100.0 255.255.255.0 10.10.2.5
ip route-static vpn-instance Public 10.10.200.0 255.255.255.0 10.10.2.5
#
return
set priority 50
add interface Eth-Trunk1
#
ip route-static 0.0.0.0 0.0.0.0 10.10.2.1
ip route-static 10.10.100.0 255.255.255.0 10.10.3.1
ip route-static 10.10.200.0 255.255.255.0 10.10.3.1
#
sysname FW2
#
hrp enable
hrp interface Eth-Trunk1 remote 10.1.1.1
#
firewall packet-filter default permit interzone local trust direction inbound
firewall packet-filter default permit interzone local trust direction outbound
firewall packet-filter default permit interzone local untrust direction outbound
On agile networks, flexible and fast agile switches replace traditional switches. For
example, administrators can flexibly and fast configure, manage, and maintain
devices. They do not need to modify configurations for devices one by one to
change a service or take a long time to locate a network fault. Users can flexibly
and fast access an agile network and enjoy the same network experience at any
locations using any access mode.
● Users in different areas of the main campus can access the campus network
and connect to the Internet through the campus network. Wired users use
802.1X authentication and wireless users use Web authentication to access
the network.
The following figure shows only the network deployment for teaching and
office areas. The network deployment for other areas is similar and is not
shown in the figure.
● The network provides the Voice over Internet Protocol (VoIP), network printer,
and multimedia services.
● Users in branch campuses can access the main campus network through the
Intranet.
● Users outside the campuses can access the main campus network through the
Internet.
Figure 2-15 Campus networking diagram for the main campus (with no agile
network deployed)
Intranet Internet
Independent
AC
S5700LI
Teaching Office AP
S5700LI area area Teaching Office
area area
The service deployment on the current campus network faces the following
problems:
Intranet Internet
External
eSight Core switch website server
S12708
S5700LI
AP S5700LI
Teacher Lee is
in the office area
at 8:00 a.m.
Teacher Lee is in
the teaching area
at 10:00 a.m.
Teacher Lee is
in the canteen
at 12:00 a.m.
Teacher Lee is
in the library at
4:00 p.m.
Teacher Lee is in the
residential community
at 8:00 p.m.
● Core switch
Agile switches are used at the core layer. If modular switches are used as agile
switches, X series cards need to be installed on the switches to implement
wired and wireless convergence.
● Aggregation and access switches
To support the agile feature Super Virtual Fabric (SVF), see "SVF hardware
and software requirements" in SVF Technical Characteristics.
● Agile Controller
The Agile Controller integrates functions of the RADIUS server, Portal server,
and free mobility controller, facilitating service adjustment. When a user
connects to the network from different locations, the free mobility controller
uniformly delivers network access rights to ensure that the user can have the
same network access rights at different locations.
● eSight network management system (NMS)
eSight provides a graphical user interface (GUI) to help manage network
devices, perform configurations, and facilitate convenient and visual
management.
● Wired and wireless convergence: Wired and wireless networks are uniformly
managed and maintained.
Agile switches at the core layer provide native capabilities on their line cards,
so no independent AC devices or AC cards (such as ACU2) are required.
Administrators do not need to configure and deploy user access services on
the wired and wireless networks respectively and can manage wired and
wireless networks simply as managing one device. The high switching
capability and scalability of agile switches eliminate bottlenecks in centralized
traffic forwarding when independent ACs or AC cards are used.
● Free mobility: Service control policies can be migrated with users, delivering
consistent experience for users.
For example, in 2.6.2 Networking Requirements, teacher Lee connects to the
campus network from the office area, teaching area, library, and residential
community every day. He may be granted different access rights on a
traditional network. For example, he can access the essay database only in
the office area, teaching area, and library, but not in public areas in the
campus.
The free mobility solution enables users to have the same network access
rights at different locations. Network access policies are configured centrally
on the Agile Controller and delivered to all associated access devices. In this
way, users can obtain the same network access policies and enjoy consistent
network access experience at any locations and using any IP addresses.
Table 2-7 lists the access policies that are configured on the Agile Controller
and delivered to three user groups: guest, student, and teacher.
After the preceding policies are configured, users have the same network
access rights and network experience after passing authentication.
● Super Virtual Fabric (SVF): Agile switches deliver configurations to devices at
the aggregation and access layers.
The SVF solution virtualizes core, aggregation, and access switches on a
network into one switch. The core switch manages the aggregation and
access switches, and uses configuration templates to complete batch
configuration of aggregation and access switches. In this way, administrators
do not need to configure switches one by one.
Table 2-8 describes the roles in an SVF system. The agile switch functions as a
parent to manage all access switches (ASs) and APs. In the SVF system, wired
and wireless users are all managed on the parent.
Role Device
Services on ASs are configured on the parent, and the key states of ASs and
APs are maintained on the parent. Administrators can complete service
configurations for aggregation and access switches by simply connecting
unconfigured aggregation and access switches to the parent. The aggregation
and access layers realize zero-touch configuration, automatic upgrade, and
plug-and-play deployment, simplifying network configuration, management,
and maintenance.
An SVF system supports at most two levels of ASs and one level of APs. When eSight is
deployed to manage the SVF system, SVF can better simplify device management.
● Packet Conservation Algorithm for Internet (iPCA): iPCA allows an agile
network to be aware of the service quality and to locate network failures.
An agile switch with iPCA configured can monitor packet loss in real time.
Table 2-9 lists packet loss measurement modes. If a link fails, an iPCA-
capable switch can quickly detect the fault and sends an alarm to
administrators immediately. iPCA allows the network to be aware of the
service quality, reducing impact of network failures. eSight can display packet
loss measurement results on a GUI, so administrators can easily monitor the
network quality.
Table 2-10 lists the minimum versions supporting agile features and precautions
for configuring these features.
This case uses S series switches in V200R009C00 as an example. The configuration may
slightly vary depending on the product and version. Refer to the configuration manual
accordingly.
Branch campus
WAN
Agile Controller
Parent_1 GE1/1/0/2 Parent_2
GE1/1/0/1 GE2/1/0/2
GE2/1/0/1
Libarary
(S5700LI) (S5700LI)
AS_1 AS_2
Teaching area 1
(S5700LI)
AS_3
GE0/0/24 (AP5010DN)
GE0/0/23
PC_2 AP_2
(AP5010DN)
PC_1 AP_1 STA_2
STA_1
Table 2-11 and Table 2-12 describe the data planning based on the preceding
networking diagram.
VLAN that wired users in Service VLAN accessed by wired users in teaching
teaching area 1 belong to. area 1, such as the VLAN that PC_1 belongs to.
ID: 100
IP address: 192.168.100.1/24
VLAN that wired users in the Service VLAN accessed by wired users in the
library belong to. library, such as the VLAN that PC_2 belongs to.
ID: 200
IP address: 192.168.200.1/24
VLAN that mobile terminals Service VLAN accessed by STAs in teaching area
in teaching area 1 belong to. 1, such as the VLAN that STA_1 belongs to.
ID: 202
IP address: 192.168.202.1/24
VLAN that mobile terminals Service VLAN accessed by STAs in the library,
in the library belong to. such as the VLAN that STA_2 belongs to.
ID: 204
IP address: 192.168.204.1/24
When enabling the SVF function, ensure that the current and next startup NAC
configuration modes are the unified mode.
You can run the display authentication mode command to check whether the current
and next startup NAC configuration modes are the unified mode. If not, set the modes to
the unified mode.
After the traditional and unified modes are switched, restart the device to make the
configuration take effect. By default, the NAC configuration mode is unified mode.
3. Configure access parameters for ASs.
# Configure ASs' names, and specify the device models and management
MAC addresses for the ASs.
[HUAWEI-um] as name as1 model S5700-52X-PWR-LI-AC mac-address 0200-0000-0011
[HUAWEI-um-as-as1] quit
[HUAWEI-um] as name as2 model S5700-52X-PWR-LI-AC mac-address 0200-0000-0022
[HUAWEI-um-as-as2] quit
[HUAWEI-um] as name as3 model S5700-28X-PWR-LI-AC mac-address 0200-0000-0033
[HUAWEI-um-as-as3] quit
# Configure the fabric ports that connect the parent to level-1 ASs (AS_1 and
AS_2). The following example configures the fabric port that connects the
parent to AS_1. The configuration of the fabric port that connects the parent
to AS_2 is similar and is not mentioned here.
[HUAWEI-um] interface fabric-port 1
[HUAWEI-um-fabric-port-1] port member-group interface eth-trunk 1
[HUAWEI-um-fabric-port-1] quit
[HUAWEI-um] quit
[HUAWEI] interface gigabitethernet 1/1/0/1
[HUAWEI-GigabitEthernet1/1/0/1] eth-trunk 1
[HUAWEI-GigabitEthernet1/1/0/1] quit
[HUAWEI] interface gigabitethernet 2/1/0/1
[HUAWEI-GigabitEthernet2/1/0/1] eth-trunk 1
[HUAWEI-GigabitEthernet2/1/0/1] quit
4. Clear the configurations of ASs, restart the ASs, and then connect the ASs to
the parent using cables. Subsequently, an SVF system is set up.
Before connecting an AS to the parent, ensure that the AS has no configuration file or
input on the console port.
# Clear the configurations of ASs and restart the ASs. (This process takes 5
minutes. During the process, ensure that the AS has no input on the console
port. If the ASs are unconfigured, you can directly connect the ASs to the
parent with no need to restart the ASs.)
<HUAWEI> reset saved-configuration
Warning: The action will delete the saved configuration in the device.
The configuration will be erased to reconfigure. Continue? [Y/N]:y
# After connecting the cables, run the display as all command to check
whether all ASs have connected to the SVF system successfully.
<HUAWEI> display as all
------------------------------------------------------------------------------
No. Type Mac IP State Name
------------------------------------------------------------------------------
0 S5700-52X-PWR-LI-AC 0200-0000-0011 192.168.11.254 normal as1
1 S5700-52X-PWR-LI-AC 0200-0000-0022 192.168.11.253 normal as2
2 S5700-28X-PWR-LI-AC 0200-0000-0033 192.168.11.252 normal as3
------------------------------------------------------------------------------
Total: 3
1. Create a network basic profile, and specify a pass-VLAN for mobile terminals
connected to AP_1.
<HUAWEI> system-view
[HUAWEI] uni-mng
[HUAWEI-um] network-basic-profile name profile_ap
[HUAWEI-um-net-basic-profile_ap] pass-vlan 202
[HUAWEI-um-net-basic-profile_ap] quit
# After connecting the cables, run the display ap all command to check
whether AP_1 has connected to the SVF system successfully.
[HUAWEI] display ap all
Total AP information:
nor : normal [1]
-------------------------------------------------------------------------------------------------
ID MAC Name Group IP Type State STA Uptime
-------------------------------------------------------------------------------------------------
1 00e0-0001-0005 00e0-0001-0005 default 192.168.11.254 AP5010DN-AGN nor 0 6H:3M:
40S
-------------------------------------------------------------------------------------------------
Total: 1
3. Create a group, and bind the network basic profile and user access profile to
the group.
[HUAWEI-um] port-group name group1
[HUAWEI-um-portgroup-group1] network-basic-profile profile_1
[HUAWEI-um-portgroup-group1] user-access-profile pro1
[HUAWEI-um-portgroup-group1] as name as3 interface GigabitEthernet 0/0/23
[HUAWEI-um] commit as name as3
[HUAWEI-um] quit
# Configure a global default domain isp1. If a user name does not contain a
domain name or contains an invalid domain name, the user is authenticated
in the default domain.
[HUAWEI] domain isp1
# Enable the free mobility function, and configure an IP address for the Agile
Controller server and a password used for communicating with the Agile
Controller.
[HUAWEI] group-policy controller 192.168.2.31 password Huawei@123
Table 2-13 Security groups and access control policies configured on the Agile
Controller
example describes how the S12708 assigns IP addresses to the PCs and STAs
in teaching area 1.
# Configure the S12708 to assign an IP address to PC_1 from the global
address pool.
<HUAWEI> system-view
[HUAWEI] dhcp enable
[HUAWEI] vlan batch 100 202
[HUAWEI] interface vlanif 100
[HUAWEI-Vlanif100] ip address 192.168.100.1 24
[HUAWEI-Vlanif100] dhcp select global
[HUAWEI-Vlanif100] quit
[HUAWEI] ip pool 100
[HUAWEI-ip-pool-100] gateway-list 192.168.100.1
[HUAWEI-ip-pool-100] network 192.168.100.0 mask 24
[HUAWEI-ip-pool-100] quit
# Configure the S12708 to assign IP addresses to STAs from the global
address pool. The IP addresses in the address pool 202 are assigned to the
STAs connected to AP_1, and the IP addresses in the address pool 204 are
assigned to the STAs connected to AP_2.
The following example describes how the S12708 assigns IP addresses to the
STAs connected to AP_1.
[HUAWEI] interface vlanif 202
[HUAWEI-Vlanif202] ip address 192.168.202.1 24
[HUAWEI-Vlanif202] dhcp select global
[HUAWEI-Vlanif202] quit
[HUAWEI] ip pool 202
[HUAWEI-ip-pool-202] gateway-list 192.168.202.1
[HUAWEI-ip-pool-202] network 192.168.202.0 mask 24
[HUAWEI-ip-pool-202] quit
2. Configure an AP to go online.
# Create an AP group to which the APs with the same configuration can be
added.
[HUAWEI] wlan
[HUAWEI-wlan-view] ap-group name ap-group1
[HUAWEI-wlan-ap-group-ap-group1] quit
# Create a regulatory domain profile, configure the AC country code in the
profile, and apply the profile to the AP group.
[HUAWEI-wlan-view] regulatory-domain-profile name domain1
[HUAWEI-wlan-regulate-domain-domain1] country-code cn
[HUAWEI-wlan-regulate-domain-domain1] quit
[HUAWEI-wlan-view] ap-group name ap-group1
[HUAWEI-wlan-ap-group-ap-group1] regulatory-domain-profile domain1
Warning: Modifying the country code will clear channel, power and antenna gain configurations of
the radio and reset the AP. Continu
e?[Y/N]:y
[HUAWEI-wlan-ap-group-ap-group1] quit
[HUAWEI-wlan-view] quit
# Configure the AC's source interface.
[HUAWEI] capwap source interface vlanif 11
# Add an AP to the AP group ap-group1. In this example, the AP's MAC
address is 00e0-0001-0005.
[HUAWEI] wlan
[HUAWEI-wlan-view] ap-id 1 ap-mac 00e0-0001-0005
[HUAWEI-wlan-ap-1] ap-name area_1
[HUAWEI-wlan-ap-1] ap-group ap-group1
Warning: This operation may cause AP reset. If the country code changes, it will clear channel, power
and antenna gain configuration
s of the radio, Whether to continue? [Y/N]:y
[HUAWEI-wlan-ap-1] quit
# After the AP is powered on, run the display ap all command to check the
AP state. If the State field displays nor, the AP has gone online.
[HUAWEI-wlan-view] display ap all
Total AP information:
nor : normal [1]
-------------------------------------------------------------------------------------
ID MAC Name Group IP Type State STA Uptime
-------------------------------------------------------------------------------------
1 00e0-0001-0005 area_1 ap-group1 192.168.11.254 AP5010DN-AGN nor 0 10S
-------------------------------------------------------------------------------------
Total: 1
# Create the SSID profile area1 and set the SSID name to area1.
[HUAWEI-wlan-view] ssid-profile name area1
[HUAWEI-wlan-ssid-prof-area1] ssid area1
Warning: This action may cause service interruption. Continue?[Y/N]y
[HUAWEI-wlan-ssid-prof-area1] quit
# Create the VAP profile wlan-vap, set the data forwarding mode and service
VLAN, and apply the security profile and SSID profile to the VAP profile.
[HUAWEI-wlan-view] vap-profile name wlan-vap
[HUAWEI-wlan-vap-prof-wlan-vap] forward-mode direct-forward
Warning: This action may cause service interruption. Continue?[Y/N]y
[HUAWEI-wlan-vap-prof-wlan-vap] service-vlan vlan-id 202
[HUAWEI-wlan-vap-prof-wlan-vap] security-profile security
[HUAWEI-wlan-vap-prof-wlan-vap] ssid-profile area1
[HUAWEI-wlan-vap-prof-wlan-vap] quit
# Bind the VAP profile wlan-vap to radio 0 and radio 1 of the AP group.
[HUAWEI-wlan-view] ap-group name ap-group1
[HUAWEI-wlan-ap-group-ap-group1] vap-profile wlan-vap wlan 1 radio 0
[HUAWEI-wlan-ap-group-ap-group1] vap-profile wlan-vap wlan 1 radio 1
[HUAWEI-wlan-ap-group-ap-group1] quit
iPCA can be performed to detect packet loss on agile switches and between agile switches. If
you want to detect packet loss between the main campus and branch campus networks, agile
switches need to be deployed on both networks.
[HUAWEI] iplpm global loss-measure alarm enable //Enable the packet loss alarm and clear
alarm on a device.
[HUAWEI] iplpm global loss-measure enable //Enable the packet loss measurement
2. Run the display iplpm loss-measure statistics global command to check the
packet loss measurement results on a device. You can check the values of
Loss Packets and LossRatio to know whether packet loss occurs on a device.
[HUAWEI] display iplpm loss-measure statistics global
Latest global loss statistics:
--------------------------------------------------------------------------------
StartTime(DST) Loss Packets LossRatio ErrorInfo
--------------------------------------------------------------------------------
2015-06-12 18:47:30 344127 4.513519% OK
2015-06-12 18:47:20 381085 4.513196% OK
2015-06-12 18:47:10 381192 4.513290% OK
2015-06-12 18:47:00 381339 4.513341% OK
2015-06-12 18:46:50 381465 4.513392% OK
2015-06-12 18:46:40 381444 4.513487% OK
2015-06-12 18:46:30 381129 4.513309% OK
--------------------------------------------------------------------------------
Overview
The Hierarchy of VPN (HoVPN)-based High-Speed Self Recovery (HSR) solution is
designed to ensure network reliability, scalability, maintainability, and multi-
service supporting capability, provide a hierarchical network structure, and reduce
networking costs. Figure 2-18 shows the network topology in the HSR solution.
Site1_UPE1 Site3_UPE6
CE1 CE3
vpna vpna
BFD for Core_SPE1 BFD for
VRRP VRRP
TE HSB TE HSB
VPN FRR VPN FRR
TE HSB
VPN FRR
BFD for
VRRP
Site2_UPE3 Site2_UPE4
CE2
vpna
Metro site 1
In Figure 2-18,
● Three S9700 switches are fully connected on the core layer to form a core
ring, while the data center site and two subway sites exchange data across
the core ring.
● Two S5720-HIs are deployed as aggregation switches in each subway site and
form square networking with two S9700s on the core ring. Alternatively,
S5720-HIs in multiple sites are connected in serial networking and then form
square networking with two S9700s on the core ring. S5720-HIs have VRRP
configured to function as user gateways of each subway site. The data center
site uses two S9700s as aggregation switches and has the same services as
S5720-HIs deployed.
● Layer 2 switches are deployed on the access layer in each site to form an
access ring and are dual-homed to two S5720-HIs in subway sites or two
S9700s in the data center site.
This network transmits all service traffic of the subway system, including traffic of
daily work, advertising media, and train control management.
Service Deployment
IGP Use OSPF as an IGP and run OSPF between aggregation and core
switches to ensure that these switches can be reached through routes
and set up Multiprotocol Label Switching (MPLS) Label Distribution
Protocol (LDP) and MPLS Traffic Engineering (TE) over OSPF routes.
Routin Use routing policies to set the preferred value, and community
g attribute to filter, select, and back up routes.
policy
MPLS Run LDP between aggregation and core switches to transmit L3VPN
LDP data on links for label switching. Configure BFD for label switched
paths (LSPs) to implement fast link switchovers.
MPLS Deploy MPLS TE tunnels to transmit L3VPN traffic. That is, establish
TE the primary and backup TE tunnels between each S5720-HI and its
directly connected S9700, and establish the primary and backup
tunnels between each S9700 and its directly connected S5720-HI.
Enable TE HSB and configure BFD for TE HSB to allow traffic to be
switched from the faulty primary TE tunnel to the backup TE tunnel
within 50 ms.
L3VPN Configure different VPNs for services such as daily office, advertising
media, and train control management to isolate these services. In this
scenario, one VPN is configured as an example.
BFD Use BFD on each node to detect faults and implement fast traffic
switchovers in case of faults. In this example, you need to deploy
multiple services, including BFD for VRRP, BFD for LSP, and BFD for TE,
to complete end-to-end switchovers within 50 ms.
Item Solution
Hybrid Enable IP+VPN hybrid FRR on S5720-HIs. When a fault occurs on the
fast downlink access link, the connected interface on one S5720-HI will
rerout detect the fault and fast switch traffic to the peer S5720-HI, which
e then forwards traffic to access devices.
(FRR)
Core nodes Use S9706s or S9712s as core nodes and data center
and data aggregation nodes, and install SRUDs and X series cards on
center these switches.
aggregation To provide high reliability, ensure that:
nodes
● Eth-Trunk member interfaces reside on the same LPU.
● On the same device, any two interfaces connected to other
devices reside on different LPUs.
Version Mapping
Version Device
Network Topology
Construct a network based on the topology shown in Figure 2-19, name network
devices, and configure IP addresses for network devices, service interfaces, and
user interfaces on the devices.
XGE0/0/1 XGE0/0/1
XGE0/0/4
Site2_UPE3 Site2_UPE4
XGE0/0/4
XGE0/0/2.150 XGE0/0/2.150
CE2
vpna
Eth-Trunk5 XGigabitEthernet1/0/0
XGigabitEthernet1/0/1
XGigabitEthernet1/0/2
XGigabitEthernet1/0/3
Eth-Trunk17 XGigabitEthernet6/0/0
XGigabitEthernet6/0/1
XGigabitEthernet6/0/2
XGigabitEthernet6/0/3
Eth-Trunk2 XGigabitEthernet3/0/4
XGigabitEthernet3/0/5
XGigabitEthernet3/0/6
XGigabitEthernet3/0/7
Eth-Trunk17 XGigabitEthernet5/0/0
XGigabitEthernet5/0/1
XGigabitEthernet5/0/2
XGigabitEthernet5/0/3
Eth-Trunk2 XGigabitEthernet2/0/4
XGigabitEthernet2/0/5
XGigabitEthernet2/0/6
XGigabitEthernet2/0/7
Eth-Trunk7 XGigabitEthernet4/0/4
XGigabitEthernet4/0/5
XGigabitEthernet4/0/6
XGigabitEthernet4/0/7
Eth-Trunk7 XGigabitEthernet6/0/4
XGigabitEthernet6/0/5
XGigabitEthernet6/0/6
XGigabitEthernet6/0/7
Data Plan
The data provided in this section is used as an example, which may vary depending on the
network scale and topology.
Device information includes the site name, device role, and device number. Each
device is named in the format of AA_BBX.
Procedure
● Configure the device name.
The following uses the configuration of Site1_UPE1 as an example. The
configurations of other devices are similar to the configuration of Site1_UPE1,
and are not mentioned here.
sysname Site1_UPE1
----End
Procedure
Step 1 Add physical interfaces to Eth-Trunks.
The following uses the configuration of Core_SPE1 as an example. The
configurations of other devices are similar to the configuration of Core_SPE1, and
are not mentioned here.
#
interface XGigabitEthernet1/0/0
eth-trunk 5
#
interface XGigabitEthernet1/0/1
eth-trunk 5
#
interface XGigabitEthernet1/0/2
eth-trunk 5
#
interface XGigabitEthernet1/0/3
eth-trunk 5
#
interface XGigabitEthernet5/0/4
eth-trunk 4
#
interface XGigabitEthernet5/0/5
eth-trunk 4
#
interface XGigabitEthernet5/0/6
eth-trunk 4
#
interface XGigabitEthernet5/0/7
eth-trunk 4
#
interface XGigabitEthernet6/0/0
eth-trunk 17
#
interface XGigabitEthernet6/0/1
eth-trunk 17
#
interface XGigabitEthernet6/0/2
eth-trunk 17
#
interface XGigabitEthernet6/0/3
eth-trunk 17
#
Step 4 Create Eth-Trunk load balancing profiles and apply the profiles to Eth-Trunks.
Configure load balancing based on the source and destination port numbers. The
following uses the configuration of Core_SPE1 as an example. The configurations
of other devices are similar to the configuration of Core_SPE1, and are not
mentioned here.
#
load-balance-profile CUSTOM
----End
Context
To implement protection switching within 50 ms, set the minimum interval at
which BFD packets are sent and received to 3.3 ms. The restraints on switches are
as follows:
● For the S12700, the MPU must be an ET1D2MPUA000/ET1D2MPUDC00 card.
● For the S12700E, the MPU must be an LST7MPUE0000 card.
● For the S9700, the MPU must be an EH1D2SRUDC00/EH1D2SRUDC01 card.
● For the S7700, the MPU must have an ES0D00FSUA00 card installed or be an
EH1D2SRUDC00/EH1D2SRUDC01 card.
● For the S7706/S7706 PoE or S7712, the assign system-resource-mode static
command must be run to set the resource allocation mode to static so that
the BFD detection duration can be controlled within 50 ms.
● For the S5720-HI, S5730-HI, S5731-H, S5731-S, S5731S-H, S5731S-S, and
S6720-HI, the set service-mode command must be run to configure the
switch to work in enhanced mode.
● For the S5732-H, S6730-H, S6730S-H, S6730-S, and S6730S-S, the set service-
mode command must be run to configure the switch to work in enhanced—
bfd mode.
Procedure
● Configure SPEs.
The following uses the configuration of Core_SPE1 on the core ring as an
example. The configurations of Core_SPE2 and Core_SPE3 are similar to the
configuration of Core_SPE1, and are not mentioned here.
#
bfd
#
● Configure UPEs.
The following uses the configuration of Site1_UPE1 as an example. The
configurations of Site1_UPE2, Site2_UPE3, Site2_UPE4, Site3_UPE5, and
Site3_UPE6 are similar to the configuration of Site1_UPE1, and are not
mentioned here.
#
bfd
#
----End
OS
OS
PF
PF
OS
OS
OS
PF
PF
PF
OS
Site1_UPE2 Site3_UPE5
OSPF
Core_SPE2 Core_SPE3
OSPF
OSPF
OSPF
Site2_UPE3 Site2_UPE4
CE2 OSPF
vpna
Configuration Roadmap
Use OSPF as an IGP to ensure that network-wide devices can be reached through
routes and set up MPLS LDP and MPLS TE over OSPF routes. The configuration
roadmap is as follows:
1. Add all devices to area 0 and advertise the directly connected network
segment and the address of loopback interface 1.
2. Configure all interfaces that do not run OSPF as OSPF silent interfaces to
disable the interfaces from sending or receiving OSPF packets. The
configuration makes the OSPF network more adaptive and saves network
resources.
3. Considering the impact of 31-bit subnet masks, configure the OSPF network
type to point-to-point on the main interoperation interface.
4. Configure synchronization between OSPF and LDP to prevent traffic loss
caused by switchovers of the primary and backup LSPs.
Context
Configuring OSPF ensures that user-end provider edges (UPEs) and superstratum
provider edges (SPEs) can be reached through public network routes.
Procedure
● Configure SPEs.
The following uses the configuration of Core_SPE1 on the core ring as an
example. The configurations of Core_SPE2 and Core_SPE3 are similar to the
configuration of Core_SPE1, and are not mentioned here.
router id 172.16.0.5 //Configure a router ID.
#
interface Eth-Trunk4
ospf network-type p2p //Set the OSPF network type to P2P on the interfaces using IP addresses
with 31-bit subnet masks.
#
interface Eth-Trunk5
ospf network-type p2p
#
interface Eth-Trunk17
ospf network-type p2p
#
interface XGigabitEthernet6/0/4
ospf network-type p2p
#
ospf 1
silent-interface all //Prohibit all interfaces from receiving and sending OSPF packets.
undo silent-interface Eth-Trunk4 //Allow interfaces to receive and send OSPF packets.
undo silent-interface Eth-Trunk5
undo silent-interface Eth-Trunk17
undo silent-interface XGigabitEthernet6/0/4
spf-schedule-interval millisecond 10 //Set the route calculation interval to 10 ms to speed up route
convergence.
lsa-originate-interval 0 //Set the LSA update interval to 0.
lsa-arrival-interval 0 //Set the interval for receiving LSAs to 0 so that topology or route changes
can be immediately detected to speed up route convergence.
graceful-restart period 600 //Enable OSPF GR.
flooding-control //Enable flooding-control to stabilize neighbor relationships.
area 0.0.0.0
authentication-mode md5 1 cipher %^%#NInJJ<oF9VXb:BS~~9+JT'suROXkVHNG@8+*3FyB%^
%# //Set the authentication mode and password for the OSPF area.
network 172.16.0.5 0.0.0.0
network 172.17.4.2 0.0.0.0
network 172.17.4.8 0.0.0.0
network 172.17.4.10 0.0.0.0
network 172.17.10.2 0.0.0.0
#
● Configure UPEs.
The following uses the configuration of Site1_UPE1 as an example. The
configurations of Site1_UPE2, Site2_UPE3, Site2_UPE4, Site3_UPE5, and
----End
Neighbors
Neighbors
Authentication Sequence: [ 0 ]
Neighbors
8
1
6 9
Site1_UPE2 Site3_UPE5
3
Core_SPE2 Core_SPE3
10
12
11
Site2_UPE3 Site2_UPE4
Configuration Roadmap
The configuration roadmap is as follows:
1. Configure an LSR ID and enable MPLS LDP globally and on each interface.
2. Configure synchronization between LDP and OSPF to prevent traffic loss
caused by switchovers of the primary and backup LSPs.
3. Configure LDP GR so that traffic forwarding is not interrupted upon primary/
backup switchovers and protocol restarts.
4. Configure BFD for LSP to quickly detect LDP LSP faults on the core ring.
The data provided in this section is used as an example, which may vary depending on the
network scale and topology.
Procedure
● Configure SPEs.
The following uses the configuration of Core_SPE1 on the core ring as an
example. The configurations of Core_SPE2 and Core_SPE3 are similar to the
configuration of Core_SPE1, and are not mentioned here.
mpls lsr-id 172.16.0.5 //Configure an MPLS LSR ID. The IP address of a loopback interface is
recommended.
mpls //Enable MPLS globally.
label advertise non-null //Disable PHP so that the egress node assigns labels to the penultimate
hop properly.
#
mpls ldp //Enable MPLS LDP globally.
#
interface Eth-Trunk4
mpls
mpls ldp //Enable MPLS LDP on an interface.
#
interface Eth-Trunk5
mpls
mpls ldp //Enable MPLS LDP on an interface.
#
interface Eth-Trunk17
mpls
mpls ldp //Enable MPLS LDP on an interface.
#
interface XGigabitEthernet6/0/4
mpls
mpls ldp //Enable MPLS LDP on an interface.
#
● Configure UPEs.
The following uses the configuration of Site1_UPE1 as an example. The
configurations of Site1_UPE2, Site2_UPE3, Site2_UPE4, Site3_UPE5, and
Site3_UPE6 are similar to the configuration of Site1_UPE1, and are not
mentioned here.
mpls lsr-id 172.16.2.51 //Configure an MPLS LSR ID. The IP address of a loopback interface is
recommended.
mpls //Enable MPLS globally.
label advertise non-null //Disable PHP so that the egress node assigns labels to the penultimate
hop properly.
#
mpls ldp //Enable MPLS LDP globally.
#
interface Eth-Trunk7
mpls
mpls ldp //Enable MPLS LDP on an interface.
#
interface Eth-Trunk17
mpls
mpls ldp //Enable MPLS LDP on an interface.
#
----End
Context
LDP LSRs set up LSPs using OSPF. When an LDP session fault (non-link fault)
occurs on the primary LSP or the primary LSP recovers from a fault,
synchronization between LDP and OSPF can prevent traffic loss caused by
switchovers of the primary and backup LSPs.
Procedure
● Configure SPEs.
● Configure UPEs.
----End
Context
LDP GR can be configured so that traffic forwarding is not interrupted upon
primary/backup switchovers and protocol restarts.
Procedure
● Configure SPEs.
The following uses the configuration of Core_SPE1 on the core ring as an
example. The configurations of Core_SPE2 and Core_SPE3 are similar to the
configuration of Core_SPE1, and are not mentioned here.
mpls ldp
graceful-restart //Enable LDP GR.
#
● Configure UPEs.
The following uses the configuration of Site1_UPE1 as an example. The
configurations of Site1_UPE2, Site2_UPE3, Site2_UPE4, Site3_UPE5, and
Site3_UPE6 are similar to the configuration of Site1_UPE1, and are not
mentioned here.
mpls ldp
graceful-restart
#
----End
Context
To ensure reliability of LDP LSPs between SPEs on the core ring, configure BFD to
detect LDP LSPs quickly.
Procedure
● Configure SPEs.
The following uses the configuration of Core_SPE1 on the core ring as an
example. The configurations of Core_SPE2 and Core_SPE3 are similar to the
configuration of Core_SPE1, and are not mentioned here.
bfd SPE1toSPE2 bind ldp-lsp peer-ip 172.16.0.3 nexthop 172.17.4.9 interface Eth-Trunk4 //Enable
static BFD to detect the LDP LSP between SPE1 and SPE2.
discriminator local 317 //Set the local discriminator. The local discriminator of the local system
must be the same as the remote discriminator of the remote system.
discriminator remote 137 //Set the remote discriminator.
detect-multiplier 8 //Set the local detection multiplier of BFD.
min-tx-interval 3 //Set the minimum interval at which the local device sends BFD packets to 3.3 ms.
min-rx-interval 3 //Set the minimum interval at which the local device receives BFD packets to 3.3
ms.
process-pst //Allow BFD sessions to change the PST to speed up switchovers.
commit //Commit the BFD session configuration.
#
bfd SPE1toSPE3 bind ldp-lsp peer-ip 172.16.0.4 nexthop 172.17.4.3 interface Eth-Trunk5 //Enable
static BFD to detect the LDP LSP between SPE1 and SPE3.
discriminator local 32
discriminator remote 23
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
----End
Core_SPE2 Core_SPE3
Primary TE1
Primary TE3
2 Ba
3 1 TE ck
up 5 7
up TE
ck
Ba 4
6
2
Site2_UPE3 4 Site2_UPE4
8
The data provided in this section is used as an example, which may vary depending on the
network scale and topology.
Procedure
● Configure SPEs.
The following uses the configuration of Core_SPE1 on the core ring as an
example. The configurations of Core_SPE2 and Core_SPE3 are similar to the
configuration of Core_SPE1, and are not mentioned here.
mpls
mpls te //Enable MPLS TE globally.
mpls rsvp-te //Enable RSVP-TE.
mpls te cspf //Enable the CSPF algorithm.
#
interface Eth-Trunk4
mpls te //Enable MPLS TE on an interface.
mpls te link administrative group c //Configure the link management group attribute for the TE
tunnel to select primary and backup paths.
mpls rsvp-te //Enable RSVP-TE on an interface.
#
interface Eth-Trunk5
mpls te
mpls te link administrative group 30
mpls rsvp-te
#
interface Eth-Trunk17
mpls te
mpls te link administrative group 4
mpls rsvp-te
#
interface XGigabitEthernet6/0/4
mpls te
mpls te link administrative group 20
mpls rsvp-te
#
ospf 1
opaque-capability enable //Enable the Opaque capability of OSPF.
area 0.0.0.0
mpls-te enable //Enable MPLS TE in the OSPF area.
#
interface Tunnel611 //Specify the tunnel from Core_SPE1 to Site1_UPE1.
description Core_SPE1 to Site1_UPE1 //Configure the interface description.
ip address unnumbered interface LoopBack1 //Configure a tunnel interface to borrow the IP
address of a loopback interface.
tunnel-protocol mpls te //Set the tunnel protocol to MPLS TE.
destination 172.16.2.51 //Configure IP address of Site1_UPE1 as the tunnel destination IP address.
mpls te tunnel-id 71 //Configure a tunnel ID, which must be valid and unique on the local device.
mpls te record-route //Configure the tunnel to record detailed route information for maintenance.
mpls te affinity property 4 mask 4 //Configure the affinity attribute of the primary CR-LSP for
selecting the optimal forwarding path.
mpls te affinity property 8 mask 8 secondary //Configure the affinity attribute of the backup CR-
LSP.
mpls te backup hot-standby //Configure the hot standby mode of tunnels.
mpls te commit //Commit all the MPLS TE configuration of the tunnel for the configuration to take
effect.
#
interface Tunnel622
description Core_SPE1 to Site1_UPE2
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.2.50
mpls te tunnel-id 82
mpls te record-route
mpls te affinity property 8 mask 8
mpls te affinity property 4 mask 4 secondary
mpls te backup hot-standby
mpls te commit
#
interface Tunnel711
description Core_SPE1 to Site3_UPE6
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.2.86
mpls te tunnel-id 311
mpls te record-route
mpls te affinity property 20 mask 20
mpls te affinity property 10 mask 10 secondary
mpls te backup hot-standby
mpls te commit
#
interface Tunnel721
description Core_SPE1 to Site3_UPE5
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.2.87
mpls te tunnel-id 312
mpls te record-route
mpls te affinity property 10 mask 10
mpls te affinity property 20 mask 20 secondary
mpls te backup hot-standby
mpls te commit
#
tunnel-policy TSel //Configure a tunnel policy.
tunnel select-seq cr-lsp lsp load-balance-number 1 //Configure the CR-LSP to be preferentially
selected.
#
tunnel-policy TE
tunnel select-seq cr-lsp load-balance-number 1
#
● Configure UPEs.
----End
● Run the display mpls te hot-standby state all command to view status of all
HSB tunnels.
Using Core_SPE1 as an example, if all HSB tunnels of Core_SPE1 are in
Primary LSP state, traffic has been switched to primary CR-LSPs.
[Core_SPE1]display mpls te hot-standby state all
---------------------------------------------------------------------
No. tunnel name session id switch result
---------------------------------------------------------------------
1 Tunnel611 71 Primary LSP
2 Tunnel622 82 Primary LSP
3 Tunnel711 311 Primary LSP
4 Tunnel721 312 Primary LSP
--- FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel611 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 2/3/5 ms
[Core_SPE1] ping lsp te Tunnel611 hot-standby
LSP PING FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel611 : 100 data bytes, press CTRL_C to break
Reply from 172.16.2.51: bytes=100 Sequence=1 time=2 ms
Reply from 172.16.2.51: bytes=100 Sequence=2 time=2 ms
Reply from 172.16.2.51: bytes=100 Sequence=3 time=3 ms
Reply from 172.16.2.51: bytes=100 Sequence=4 time=2 ms
Reply from 172.16.2.51: bytes=100 Sequence=5 time=3 ms
--- FEC: TE TUNNEL IPV4 SESSION QUERY Tunnel611 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 2/2/3 ms
Procedure
● Configure SPEs.
The following uses the configuration of Core_SPE1 on the core ring as an
example. The configurations of Core_SPE2 and Core_SPE3 are similar to the
configuration of Core_SPE1, and are not mentioned here.
mpls
mpls rsvp-te hello //Enable the RSVP Hello extension mechanism globally.
mpls rsvp-te hello full-gr //Enable the RSVP GR and RSVP GR Helper capabilities.
#
interface Eth-Trunk4
mpls rsvp-te hello //Enable the RSVP Hello extension mechanism on an interface.
#
interface Eth-Trunk5
mpls rsvp-te hello
#
interface Eth-Trunk17
mpls rsvp-te hello
#
interface XGigabitEthernet6/0/4
mpls rsvp-te hello
#
● Configure UPEs.
The following uses the configuration of Site1_UPE1 as an example. The
configurations of Site1_UPE2, Site2_UPE3, Site2_UPE4, Site3_UPE5, and
Site3_UPE6 are similar to the configuration of Site1_UPE1, and are not
mentioned here.
mpls
mpls rsvp-te hello //Enable the RSVP Hello extension mechanism globally.
mpls rsvp-te hello full-gr //Enable the RSVP GR and RSVP GR Helper capabilities.
#
interface Eth-Trunk7
mpls rsvp-te hello //Enable the RSVP Hello extension mechanism on an interface.
#
interface Eth-Trunk17
mpls rsvp-te hello
#
----End
Procedure
● Configure SPEs.
The following uses the configuration of Core_SPE1 on the core ring as an
example. The configurations of Core_SPE2 and Core_SPE3 are similar to the
configuration of Core_SPE1, and are not mentioned here.
bfd SPE1toUPE1_b bind mpls-te interface Tunnel611 te-lsp backup //Enable static BFD to detect the
backup CR-LSP of TE tunnel 611.
discriminator local 6116 //Set the local discriminator. The local discriminator of the local system
must be the same as the remote discriminator of the remote system.
discriminator remote 6115 //Set the remote discriminator.
detect-multiplier 8 //Set the local detection multiplier of BFD.
min-tx-interval 3 //Set the minimum interval at which the local device sends BFD packets to 3.3 ms.
min-rx-interval 3 //Set the minimum interval at which the local device receives BFD packets to 3.3
ms.
process-pst //Allow BFD sessions to change the PST to speed up switchovers.
commit //Commit the BFD session configuration.
#
bfd SPE1toUPE1_m bind mpls-te interface Tunnel611 te-lsp //Enable static BFD to detect the
primary CR-LSP of TE tunnel 611.
discriminator local 6112
discriminator remote 6111
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE1toUPE2_b bind mpls-te interface Tunnel622 te-lsp backup //Enable static BFD to detect the
backup CR-LSP of TE tunnel 622.
discriminator local 6226
discriminator remote 6225
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE1toUPE2_m bind mpls-te interface Tunnel622 te-lsp //Enable static BFD to detect the
primary CR-LSP of TE tunnel 622.
discriminator local 6222
discriminator remote 6221
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE1toUPE5_b bind mpls-te interface Tunnel721 te-lsp backup //Enable static BFD to detect the
backup CR-LSP of TE tunnel 721.
discriminator local 7216
discriminator remote 7215
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE1toUPE5_m bind mpls-te interface Tunnel721 te-lsp //Enable static BFD to detect the
primary CR-LSP of TE tunnel 721.
discriminator local 7212
discriminator remote 7211
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE1toUPE6_b bind mpls-te interface Tunnel711 te-lsp backup //Enable static BFD to detect the
backup CR-LSP of TE tunnel 711.
discriminator local 7116
discriminator remote 7115
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE1toUPE6_m bind mpls-te interface Tunnel711 te-lsp //Enable static BFD to detect the
primary CR-LSP of TE tunnel 711.
discriminator local 7112
discriminator remote 7111
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
● Configure UPEs.
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
----End
L3VPN
te
rou
L3
ific
N
VP
VP
ec
L3
Sp
N
Site1_UPE2 Site3_UPE5
Core_SPE2 Core_SPE3
VPN FRR
Specific route
Default route
L3VPN
L3
L3VPN
VP
N
Site2_UPE3 Site2_UPE4
IP+VPN hybrid FRR
CE2
vpna
1. Deploy MP-BGP.
– Set up MP-IBGP peer relationships between UPEs and SPEs and between
SPEs.
– Configure routing rules to enable traffic from UPEs to SPEs is forwarded
through the default route and traffic from SPEs to UPEs is forwarded
through specific routes.
– Configure route priority policies to enable UPEs to forward traffic to other
sites preferentially through SPEs directly connected to the UPEs.
– Configure route priority policies to enable SPEs to forward traffic to other
sites preferentially through UPEs directly connected to the SPEs.
– Configure route filtering policies to disable SPEs from advertising ARP
Vlink direct routes at the local sites to UPEs at other sites.
– Configure route filtering policies to disable SPEs from receiving route
information about sites directly connected to them from other SPEs,
preventing route loops. For example, disable Core_SPE2 from receiving
routes of Site1 from Core_SPE1 and routes of Site2 from Core_SPE3.
2. Deploy VPN services.
– Deploy VPN instances on UPEs and SPEs, and bind interfaces to the VPN
instances on UPEs, but not on SPEs.
The data provided in this section is used as an example, which may vary depending on the
network scale and topology.
Site1_UPE1 interface -
XGigabitEthernet1/0/4.20
0: 172.18.200.66/26
Site1_UPE2 interface -
XGigabitEthernet1/0/4.20
0: 172.18.200.67/26
Site2_UPE3 interface -
XGigabitEthernet0/0/2.15
0: 172.18.150.2/26
Site2_UPE4 interface -
XGigabitEthernet0/0/2.15
0: 172.18.150.3/26
Site3_UPE5 interface -
XGigabitEthernet0/0/2.10
0: 172.18.100.2/26
Site3_UPE6 interface -
XGigabitEthernet0/0/2.10
0: 172.18.100.3/26
BGP 6500 6500 6500 6500 6500 6500 6500 6500 6500
proce 0 0 0 0 0 0 0 0 0
ss ID
Para Core_ Core_ Core_ Site1 Site1 Site2 Site2 Site3 Site3
mete SPE1 SPE2 SPE3 _UPE _UPE _UPE _UPE _UPE _UPE
r 1 2 3 4 5 6
Route 172.1 172.1 172.1 172.1 172.1 172.1 172.1 172.1 172.1
r ID 6.0.5 6.0.3 6.0.4 6.2.51 6.2.50 6.2.75 6.2.76 6.2.87 6.2.86
Peer devC devC devC devC devC devC devC devC devC
group ore: ore: ore: ore: ore: ore: ore: ore: ore:
172.1 172.1 172.1 172.1 172.1 172.1 172.1 172.1 172.1
6.0.3, 6.0.4, 6.0.3, 6.0.3, 6.0.3, 6.0.3, 6.0.3, 6.0.4, 6.0.4,
172.1 172.1 172.1 172.1 172.1 172.1 172.1 172.1 172.1
6.0.4 6.0.5 6.0.5 6.0.5 6.0.5 6.0.4 6.0.4 6.0.5 6.0.5
devH devH devH devH devH devH devH devH devH
ost: ost: ost: ost: ost: ost: ost: ost: ost:
172.1 172.1 172.1 172.1 172.1 172.1 172.1 172.1 172.1
6.2.50 6.2.50 6.2.75 6.2.50 6.2.51 6.2.76 6.2.75 6.2.86 6.2.87
, , ,
172.1 172.1 172.1
6.2.51 6.2.51 6.2.76
, , ,
172.1 172.1 172.1
6.2.86 6.2.75 6.2.86
, , ,
172.1 172.1 172.1
6.2.87 6.2.76 6.2.87
policy Enabl Enabl Enabl Enabl Enabl Enabl Enabl Enabl Enabl
vpn- e e e e e e e e e
target
Para Core_ Core_ Core_ Site1 Site1 Site2 Site2 Site3 Site3
mete SPE1 SPE2 SPE3 _UPE _UPE _UPE _UPE _UPE _UPE
r 1 2 3 4 5 6
200
200
200 200
Site1_UPE2 30
0 0 Site3_UPE5
30
20 00
12 0:200 0:3
57 :12 30 13:13
20 20
:57 :57
20 7 20
5
Core_SPE2 Core_SPE3
5720:5720
5720:5720
300
300
20
200:200
300:300
0
20 0
23:23
23:23
Site2_UPE3 Site2_UPE4
Community Attribute
Procedure
● Configure SPEs.
The following uses the configuration of Core_SPE1 on the core ring as an
example. The configurations of Core_SPE2 and Core_SPE3 are similar to the
configuration of Core_SPE1, and are not mentioned here.
tunnel-selector TSel permit node 9
if-match ip next-hop ip-prefix core_nhp //Configure a tunnel policy selector to enable Core_SPE1 to
select any tunnel to be iterated when the next-hop address of a VPNv4 route has the prefix of
another SPE.
#
tunnel-selector TSel permit node 10 //Configure a tunnel policy selector to iterate a route received
from an IBGP peer to a TE tunnel when the route needs to be forwarded to another IBGP peer and
Core_SPE1 needs to modify the next hop of the route to itself.
apply tunnel-policy TE
#
bgp 65000
group devCore internal //Create an IBGP peer group.
peer devCore connect-interface LoopBack1 //Specify loopback interface 1 and its address as the
source interface and address of BGP packets.
peer 172.16.0.3 as-number 65000 //Set up a peer relationship between SPEs.
peer 172.16.0.3 group devCore //Add SPEs to the IBGP peer group.
peer 172.16.0.4 as-number 65000
peer 172.16.0.4 group devCore
group devHost internal
peer devHost connect-interface LoopBack1
peer 172.16.2.50 as-number 65000
● Configure UPEs.
----End
Context
VPN instances need to be configured to advertise VPNv4 routes and forward data
to achieve communication over a L3VPN.
Procedure
● Configure SPEs.
The following uses the configuration of Core_SPE1 on the core ring as an
example. The configurations of Core_SPE2 and Core_SPE3 are similar to the
configuration of Core_SPE1, and are not mentioned here.
ip vpn-instance vpna //Create a VPN instance.
ipv4-family
route-distinguisher 5:1 //Configure an RD.
tnl-policy TSel //Configure a TE tunnel for the VPN instance.
vpn-target 0:1 export-extcommunity //Configure the extended community attribute VPN target.
vpn-target 0:1 import-extcommunity
#
bgp 65000
#
ipv4-family vpnv4
nexthop recursive-lookup delay 10 //Set the next-hop iteration delay to 10s.
route-select delay 120 //Set the route selection delay to 120s, preventing traffic interruption
caused by fast route switchback.
#
ipv4-family vpn-instance vpna
default-route imported //Import the default route to VPN instance vpna.
nexthop recursive-lookup route-policy delay_policy //Configure BGP next-hop iteration based on
the routing policy delay_policy.
----End
Configuration Roadmap
The configuration roadmap is as follows:
If the number of VRRP groups exceeds the device default value, run the set vrrp max-
group-number max-group-number command on the UPEs to set the maximum
number of allowed VRRP groups.
CE1
vpna
D
Master
BF
ck
tra
RP
VR
Backup
Configure the backup device
to forward service traffic.
Site1_UPE2 Upstream
2. Deploy VPN FRR on a UPE. If the TE tunnel between the UPE and an SPE is
faulty, traffic is automatically switched to the TE tunnel between the UPE and
another SPE at the same site. Site1_UPE1 is used as an example, as shown in
Figure 2-25.
Site1_UPE1 has two TE tunnels to Core_SPE1 and Core_SPE2 respectively.
Deploying VPN FRR on Site1_UPE1 ensures that traffic is quickly switched to
Core_SPE2 if Core_SPE1 is faulty.
Core_SPE1
L3VPN
Backup
path
Site1_UPE2
Upstream
Core_SPE2
Core_SPE1
VPN FRR
N
L3
VP
L3
Core_SPE2 Core_SPE3
Downstream
4. Deploy VPN FRR on an SPE. If the TE tunnel between the SPE and a UPE is
faulty, traffic is automatically switched to the TE tunnel between the SPE and
another UPE at the same site. Core_SPE2 is used as an example, as shown in
Figure 2-27.
Core_SPE2 has two TE tunnels to Site2_UPE3 and Site2_UPE4 respectively.
Deploying VPN FRR on Core_SPE2 ensures that traffic is quickly switched to
Site2_UPE4 if Site2_UPE3 is faulty.
Core_SPE2 Core_SPE3
VPN FRR
Primary path
Ba
L3VPN
ck L3V
up P
pa N
th
Site2_UPE3 Site2_UPE4
CE2 Downstream
vpna
5. Deploy IP+VPN hybrid FRR on UPEs. If the interface of a UPE detects a fault
on the link between the UPE and its connected CE, the UPE quickly switches
traffic to its peer UPE, and the peer UPE then forwards the traffic to the CE.
Site2 is used as an example, as shown in Figure 2-28.
If the link from Site2_UPE3 to CE2 is faulty, traffic is forwarded to Site2_UPE4
through an LSP and then to CE2 using a private IP address, improving
network reliability.
MPLD LDP
Site2_UPE3 Site2_UPE4
IP+VPN hybrid FRR
CE2 Downstream
vpna
6. Deploy VPN GR on all UPEs and SPEs to ensure uninterrupted VPN traffic
forwarding during a master/backup switchover on the device transmitting
VPN services.
Procedure
● Configure SPEs.
● Configure UPEs.
----End
Destination: 172.18.150.0/26
Protocol: IBGP Process ID: 0
Preference: 255 Cost: 0
NextHop: 172.16.2.75 Neighbour: 172.16.2.75
State: Active Adv Relied Age: 21h55m50s
Tag: 0 Priority: low
Label: 1025 QoSInfo: 0x0
IndirectID: 0x185
RelayNextHop: 0.0.0.0 Interface: Tunnel111
TunnelID: 0x2 Flags: RD
BkNextHop: 172.16.2.76 BkInterface: Tunnel121
BkLabel: 1024 SecTunnelID: 0x0
BkPETunnelID: 0x3 BkPESecTunnelID: 0x0
BkIndirectID: 0xd
Destination: 172.18.150.4/32
Protocol: Direct Process ID: 0
Preference: 0 Cost: 0
NextHop: 172.18.150.4 Neighbour: 0.0.0.0
State: Active Adv Age: 1d02h36m21s
Tag: 0 Priority: high
Label: NULL QoSInfo: 0x0
IndirectID: 0x0
RelayNextHop: 0.0.0.0 Interface: XGigabitEthernet0/0/2.150
TunnelID: 0x0 Flags: D
BkNextHop: 172.16.2.76 BkInterface: XGigabitEthernet0/0/4
BkLabel: 1024 SecTunnelID: 0x0
BkPETunnelID: 0x4800001b BkPESecTunnelID: 0x0
BkIndirectID: 0x0
Destination: 172.18.150.4/32
Protocol: IBGP Process ID: 0
Preference: 255 Cost: 0
NextHop: 172.16.2.76 Neighbour: 172.16.2.76
State: Inactive Adv Relied Age: 1d02h36m21s
Tag: 0 Priority: low
graceful-restart
#
load-balance-profile CUSTOM
ipv6 field l4-sport l4-dport
ipv4 field l4-sport l4-dport
#
interface Eth-Trunk4
undo portswitch
description Core_SPE1 to Core_SPE2
ip address 172.17.4.8 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group c
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
least active-linknumber 4
load-balance enhanced profile CUSTOM
#
interface Eth-Trunk5
undo portswitch
description Core_SPE1 to Core_SPE3
ip address 172.17.4.2 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group 30
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
least active-linknumber 4
load-balance enhanced profile CUSTOM
#
interface Eth-Trunk17
undo portswitch
description Core_SPE1 to Site1_UPE1
ip address 172.17.4.10 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group 4
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
least active-linknumber 4
load-balance enhanced profile CUSTOM
#
interface XGigabitEthernet1/0/0
eth-trunk 5
#
interface XGigabitEthernet1/0/1
eth-trunk 5
#
interface XGigabitEthernet1/0/2
eth-trunk 5
#
interface XGigabitEthernet1/0/3
eth-trunk 5
#
interface XGigabitEthernet5/0/4
eth-trunk 4
#
interface XGigabitEthernet5/0/5
eth-trunk 4
#
interface XGigabitEthernet5/0/6
eth-trunk 4
#
interface XGigabitEthernet5/0/7
eth-trunk 4
#
interface XGigabitEthernet6/0/0
eth-trunk 17
#
interface XGigabitEthernet6/0/1
eth-trunk 17
#
interface XGigabitEthernet6/0/2
eth-trunk 17
#
interface XGigabitEthernet6/0/3
eth-trunk 17
#
interface XGigabitEthernet6/0/4
undo portswitch
description Core_SPE1 to Site3_UPE6
ip address 172.17.10.2 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group 20
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
#
interface LoopBack1
description ** GRT Management Loopback **
ip address 172.16.0.5 255.255.255.255
#
interface Tunnel611
description Core_SPE1 to Site1_UPE1
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.2.51
mpls te tunnel-id 71
mpls te record-route
mpls te affinity property 4 mask 4
mpls te affinity property 8 mask 8 secondary
mpls te backup hot-standby
mpls te commit
#
interface Tunnel622
description Core_SPE1 to Site1_UPE2
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.2.50
mpls te tunnel-id 82
mpls te record-route
mpls te affinity property 8 mask 8
mpls te affinity property 4 mask 4 secondary
mpls te backup hot-standby
mpls te commit
#
interface Tunnel711
description Core_SPE1 to Site3_UPE6
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.2.86
mpls te tunnel-id 311
mpls te record-route
mpls te affinity property 20 mask 20
mpls te affinity property 10 mask 10 secondary
mpls te backup hot-standby
mpls te commit
#
interface Tunnel721
description Core_SPE1 to Site3_UPE5
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.2.87
mpls te tunnel-id 312
mpls te record-route
mpls te affinity property 10 mask 10
mpls te affinity property 20 mask 20 secondary
mpls te backup hot-standby
mpls te commit
#
bgp 65000
graceful-restart
group devCore internal
peer devCore connect-interface LoopBack1
peer 172.16.0.3 as-number 65000
peer 172.16.0.3 group devCore
peer 172.16.0.4 as-number 65000
peer 172.16.0.4 group devCore
group devHost internal
peer devHost connect-interface LoopBack1
peer 172.16.2.50 as-number 65000
peer 172.16.2.50 group devHost
peer 172.16.2.51 as-number 65000
peer 172.16.2.51 group devHost
peer 172.16.2.86 as-number 65000
peer 172.16.2.86 group devHost
peer 172.16.2.87 as-number 65000
peer 172.16.2.87 group devHost
#
ipv4-family unicast
undo synchronization
undo peer devCore enable
undo peer devHost enable
undo peer 172.16.2.50 enable
undo peer 172.16.2.51 enable
undo peer 172.16.0.3 enable
undo peer 172.16.0.4 enable
undo peer 172.16.2.86 enable
undo peer 172.16.2.87 enable
#
ipv4-family vpnv4
policy vpn-target
auto-frr
nexthop recursive-lookup delay 10
tunnel-selector TSel
bestroute nexthop-resolved tunnel
route-select delay 120
peer devCore enable
peer devCore route-policy core-import import
peer devCore advertise-community
peer 172.16.0.3 enable
peer 172.16.0.3 group devCore
peer 172.16.0.4 enable
peer 172.16.0.4 group devCore
peer devHost enable
peer devHost route-policy p_iBGP_RR_in import
peer devHost advertise-community
peer devHost upe
peer devHost default-originate vpn-instance vpna
peer 172.16.2.50 enable
peer 172.16.2.50 group devHost
graceful-restart
#
load-balance-profile CUSTOM
ipv6 field l4-sport l4-dport
ipv4 field l4-sport l4-dport
#
interface Eth-Trunk2
undo portswitch
description Core_SPE2 to Core_SPE3
ip address 172.17.4.0 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group 3
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
least active-linknumber 4
load-balance enhanced profile CUSTOM
#
interface Eth-Trunk4
undo portswitch
description Core_SPE2 to Core_SPE1
ip address 172.17.4.9 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group c
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
least active-linknumber 4
load-balance enhanced profile CUSTOM
#
interface Eth-Trunk17
undo portswitch
description Core_SPE2 to Site1_UPE2
ip address 172.17.4.12 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group 8
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
least active-linknumber 4
load-balance enhanced profile CUSTOM
#
interface XGigabitEthernet3/0/4
eth-trunk 2
#
interface XGigabitEthernet3/0/5
eth-trunk 2
#
interface XGigabitEthernet3/0/6
eth-trunk 2
#
interface XGigabitEthernet3/0/7
eth-trunk 2
#
interface XGigabitEthernet5/0/0
eth-trunk 17
#
interface XGigabitEthernet5/0/1
eth-trunk 17
#
interface XGigabitEthernet5/0/2
eth-trunk 17
#
interface XGigabitEthernet5/0/3
eth-trunk 17
#
interface XGigabitEthernet5/0/5
undo portswitch
description Core_SPE2 to Site2_UPE3
ip address 172.16.8.178 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group 1
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
#
interface XGigabitEthernet6/0/4
eth-trunk 4
#
interface XGigabitEthernet6/0/5
eth-trunk 4
#
interface XGigabitEthernet6/0/6
eth-trunk 4
#
interface XGigabitEthernet6/0/7
eth-trunk 4
#
interface LoopBack1
description ** GRT Management Loopback **
ip address 172.16.0.3 255.255.255.255
#
interface Tunnel111
description Core_SPE2 to Site2_UPE3
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.2.75
mpls te tunnel-id 111
mpls te record-route
mpls te affinity property 1 mask 1
mpls te affinity property 2 mask 2 secondary
mpls te backup hot-standby
mpls te commit
#
interface Tunnel121
description Core_SPE2 to Site2_UPE4
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.2.76
mpls te tunnel-id 121
mpls te record-route
mpls te affinity property 1 mask 1
mpls te affinity property 2 mask 2 secondary
mpls te backup hot-standby
mpls te commit
#
interface Tunnel612
description Core_SPE2 to Site1_UPE1
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.2.51
mpls te tunnel-id 72
mpls te record-route
mpls te affinity property 4 mask 4
mpls te affinity property 8 mask 8 secondary
mpls te backup hot-standby
mpls te commit
#
interface Tunnel621
description Core_SPE2 to Site1_UPE2
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.2.50
mpls te tunnel-id 81
mpls te record-route
mpls te affinity property 8 mask 8
mpls te affinity property 4 mask 4 secondary
mpls te backup hot-standby
mpls te commit
#
bgp 65000
graceful-restart
group devCore internal
peer devCore connect-interface LoopBack1
peer 172.16.0.4 as-number 65000
peer 172.16.0.4 group devCore
peer 172.16.0.5 as-number 65000
peer 172.16.0.5 group devCore
group devHost internal
peer devHost connect-interface LoopBack1
peer 172.16.2.50 as-number 65000
peer 172.16.2.50 group devHost
peer 172.16.2.51 as-number 65000
peer 172.16.2.51 group devHost
peer 172.16.2.75 as-number 65000
peer 172.16.2.75 group devHost
peer 172.16.2.76 as-number 65000
peer 172.16.2.76 group devHost
#
ipv4-family unicast
undo synchronization
undo peer devCore enable
undo peer devHost enable
undo peer 172.16.2.50 enable
undo peer 172.16.2.51 enable
undo peer 172.16.2.75 enable
undo peer 172.16.2.76 enable
#
ipv4-family vpnv4
policy vpn-target
auto-frr
nexthop recursive-lookup delay 10
tunnel-selector TSel
bestroute nexthop-resolved tunnel
route-select delay 120
peer devCore enable
peer devCore route-policy core-import import
peer devCore advertise-community
peer 172.16.0.4 enable
peer 172.16.0.4 group devCore
peer 172.16.0.5 enable
peer 172.16.0.5 group devCore
peer devHost enable
peer devHost route-policy p_iBGP_RR_in import
peer devHost advertise-community
peer devHost upe
peer devHost default-originate vpn-instance vpna
peer 172.16.2.50 enable
peer 172.16.2.50 group devHost
peer 172.16.2.51 enable
peer 172.16.2.51 group devHost
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE2toUPE3_m bind mpls-te interface Tunnel111 te-lsp
discriminator local 1112
discriminator remote 1111
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE2toUPE4_b bind mpls-te interface Tunnel121 te-lsp backup
discriminator local 1216
discriminator remote 1215
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE2toUPE4_m bind mpls-te interface Tunnel121 te-lsp
discriminator local 1212
discriminator remote 1211
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
return
load-balance-profile CUSTOM
ipv6 field l4-sport l4-dport
ipv4 field l4-sport l4-dport
#
interface Eth-Trunk2
undo portswitch
description Core_SPE3 to Core_SPE2
ip address 172.17.4.1 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group 3
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
least active-linknumber 4
load-balance enhanced profile CUSTOM
#
interface Eth-Trunk5
undo portswitch
description Core_SPE3 to Core_SPE1
ip address 172.17.4.3 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group 30
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
least active-linknumber 4
load-balance enhanced profile CUSTOM
#
interface XGigabitEthernet1/0/0
eth-trunk 5
#
interface XGigabitEthernet1/0/1
eth-trunk 5
#
interface XGigabitEthernet1/0/2
eth-trunk 5
#
interface XGigabitEthernet1/0/3
eth-trunk 5
#
interface XGigabitEthernet2/0/4
eth-trunk 2
#
interface XGigabitEthernet2/0/5
eth-trunk 2
#
interface XGigabitEthernet2/0/6
eth-trunk 2
#
interface XGigabitEthernet2/0/7
eth-trunk 2
#
interface XGigabitEthernet6/0/1
undo portswitch
description Core_SPE3 to Site3_UPE5
ip address 172.16.8.213 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
ospf 1
silent-interface all
undo silent-interface Eth-Trunk5
undo silent-interface Eth-Trunk2
undo silent-interface XGigabitEthernet6/0/1
undo silent-interface XGigabitEthernet6/0/3
spf-schedule-interval millisecond 10
lsa-originate-interval 0
lsa-arrival-interval 0
opaque-capability enable
graceful-restart period 600
flooding-control
area 0.0.0.0
authentication-mode md5 1 cipher %^%#N@WU@i600:_5W!%F!L~9%7ui(!x:VP5<mJ:z>zJX%^%#
network 172.16.0.4 0.0.0.0
network 172.16.8.183 0.0.0.0
network 172.16.8.213 0.0.0.0
network 172.17.4.1 0.0.0.0
network 172.17.4.3 0.0.0.0
mpls-te enable
#
route-policy delay_policy permit node 0
#
route-policy p_iBGP_RR_in deny node 5
if-match ip-prefix deny_host
if-match community-filter all_site
#
route-policy p_iBGP_RR_in permit node 11
if-match community-filter site1
apply preferred-value 200
#
route-policy p_iBGP_RR_in permit node 12
if-match community-filter site2
apply preferred-value 200
#
route-policy p_iBGP_RR_in permit node 13
if-match community-filter site3
apply preferred-value 300
#
route-policy p_iBGP_RR_in permit node 20
#
route-policy core-import deny node 5
if-match community-filter site13
#
route-policy core-import deny node 6
if-match community-filter site23
#
route-policy core-import permit node 10
#
ip ip-prefix deny_host index 10 permit 0.0.0.0 0 greater-equal 32 less-equal 32
ip ip-prefix core_nhp index 10 permit 172.16.0.3 32
ip ip-prefix core_nhp index 20 permit 172.16.0.5 32
#
ip community-filter basic site1 permit 100:100
ip community-filter basic site2 permit 200:200
ip community-filter basic site3 permit 300:300
ip community-filter basic all_site permit 5720:5720
ip community-filter basic site13 permit 13:13
ip community-filter basic site23 permit 23:23
#
tunnel-policy TSel
tunnel select-seq cr-lsp lsp load-balance-number 1
#
tunnel-policy TE
tunnel select-seq cr-lsp load-balance-number 1
#
bfd SPE3toSPE1 bind ldp-lsp peer-ip 172.16.0.5 nexthop 172.17.4.2 interface Eth-Trunk5
discriminator local 23
discriminator remote 32
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE3toSPE2 bind ldp-lsp peer-ip 172.16.0.3 nexthop 172.17.4.0 interface Eth-Trunk2
discriminator local 217
discriminator remote 127
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE3toUPE3_b bind mpls-te interface Tunnel112 te-lsp backup
discriminator local 1126
discriminator remote 1125
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE3toUPE3_m bind mpls-te interface Tunnel112 te-lsp
discriminator local 1122
discriminator remote 1121
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE3toUPE4_b bind mpls-te interface Tunnel122 te-lsp backup
discriminator local 1226
discriminator remote 1225
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE3toUPE4_m bind mpls-te interface Tunnel122 te-lsp
discriminator local 1222
discriminator remote 1221
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE3toUPE5_b bind mpls-te interface Tunnel722 te-lsp backup
discriminator local 7226
discriminator remote 7225
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd SPE3toUPE5_m bind mpls-te interface Tunnel722 te-lsp
discriminator local 7222
discriminator remote 7221
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
undo portswitch
description Site1_UPE1 to Core_SPE1
ip address 172.17.4.11 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group 4
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
least active-linknumber 4
#
interface XGigabitEthernet1/0/0
eth-trunk 17
#
interface XGigabitEthernet1/0/1
eth-trunk 17
#
interface XGigabitEthernet1/0/2
eth-trunk 17
#
interface XGigabitEthernet1/0/3
eth-trunk 17
#
interface XGigabitEthernet1/0/4
port link-type trunk
undo port trunk allow-pass vlan 1
#
interface XGigabitEthernet1/0/4.200
dot1q termination vid 200
ip binding vpn-instance vpna
arp direct-route enable
ip address 172.18.200.66 255.255.255.192
vrrp vrid 1 virtual-ip 172.18.200.65
vrrp vrid 1 preempt-mode timer delay 250
vrrp vrid 1 track bfd-session 2200 peer
vrrp vrid 1 backup-forward
arp broadcast enable
vrrp track bfd gratuitous-arp send enable
#
interface XGigabitEthernet4/0/4
eth-trunk 7
#
interface XGigabitEthernet4/0/5
eth-trunk 7
#
interface XGigabitEthernet4/0/6
eth-trunk 7
#
interface XGigabitEthernet4/0/7
eth-trunk 7
#
interface LoopBack1
description ** GRT Management Loopback **
ip address 172.16.2.51 255.255.255.255
#
interface Tunnel611
description Site1_UPE1 to Core_SPE1
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.0.5
mpls te tunnel-id 71
mpls te record-route
mpls te affinity property 4 mask 4
mpls te affinity property 8 mask 8 secondary
mpls te backup hot-standby
mpls te commit
#
interface Tunnel612
description Site1_UPE1 to Core_SPE2
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.0.3
mpls te tunnel-id 72
mpls te record-route
mpls te affinity property 4 mask 4
mpls te affinity property 8 mask 8 secondary
mpls te backup hot-standby
mpls te commit
#
bfd vrrp-1 bind peer-ip 172.18.200.67 vpn-instance vpna interface XGigabitEthernet1/0/4.200 source-ip
172.18.200.66
discriminator local 2200
discriminator remote 1200
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
commit
#
bgp 65000
graceful-restart
group devCore internal
peer devCore connect-interface LoopBack1
peer 172.16.0.3 as-number 65000
peer 172.16.0.3 group devCore
peer 172.16.0.5 as-number 65000
peer 172.16.0.5 group devCore
group devHost internal
peer devHost connect-interface LoopBack1
peer 172.16.2.50 as-number 65000
peer 172.16.2.50 group devHost
#
ipv4-family unicast
undo synchronization
undo peer devCore enable
undo peer devHost enable
undo peer 172.16.2.50 enable
undo peer 172.16.0.3 enable
undo peer 172.16.0.5 enable
#
ipv4-family vpnv4
policy vpn-target
route-select delay 120
peer devCore enable
peer devCore route-policy p_iBGP_host_ex export
peer devCore advertise-community
peer 172.16.0.3 enable
peer 172.16.0.3 group devCore
peer 172.16.0.3 preferred-value 200
peer 172.16.0.5 enable
peer 172.16.0.5 group devCore
peer 172.16.0.5 preferred-value 300
peer devHost enable
peer devHost advertise-community
peer 172.16.2.50 enable
peer 172.16.2.50 group devHost
#
ipv4-family vpn-instance vpna
default-route imported
import-route direct route-policy p_iBGP_RR_ex
auto-frr
route-select delay 120
#
#
ospf 1
silent-interface all
commit
#
bgp 65000
graceful-restart
group devCore internal
peer devCore connect-interface LoopBack1
peer 172.16.0.3 as-number 65000
peer 172.16.0.3 group devCore
peer 172.16.0.5 as-number 65000
peer 172.16.0.5 group devCore
group devHost internal
peer devHost connect-interface LoopBack1
peer 172.16.2.51 as-number 65000
peer 172.16.2.51 group devHost
#
ipv4-family unicast
undo synchronization
undo peer devCore enable
undo peer devHost enable
undo peer 172.16.2.51 enable
undo peer 172.16.0.3 enable
undo peer 172.16.0.5 enable
#
ipv4-family vpnv4
policy vpn-target
route-select delay 120
peer devCore enable
peer devCore route-policy p_iBGP_host_ex export
peer devCore advertise-community
peer 172.16.0.3 enable
peer 172.16.0.3 group devCore
peer 172.16.0.3 preferred-value 300
peer 172.16.0.5 enable
peer 172.16.0.5 group devCore
peer 172.16.0.5 preferred-value 200
peer devHost enable
peer devHost advertise-community
peer 172.16.2.51 enable
peer 172.16.2.51 group devHost
#
ipv4-family vpn-instance vpna
default-route imported
import-route direct route-policy p_iBGP_RR_ex
auto-frr
route-select delay 120
#
#
ospf 1
silent-interface all
undo silent-interface Eth-Trunk7
undo silent-interface Eth-Trunk17
opaque-capability enable
graceful-restart period 600
bandwidth-reference 100000
flooding-control
area 0.0.0.0
authentication-mode md5 1 cipher %^%#GUPhWw-[LH2O6#NMxtJAl!Io8W~iF'![mQF[\9GI%^%#
network 172.16.2.50 0.0.0.0
network 172.16.2.92 0.0.0.0
network 172.17.4.13 0.0.0.0
network 172.17.4.15 0.0.0.0
mpls-te enable
#
route-policy mixfrr permit node 0
apply backup-nexthop 172.16.2.51
#
route-policy p_iBGP_host_ex permit node 0
apply community 200:200 5720:5720 12:12
#
#
mpls lsr-id 172.16.2.75
mpls
mpls te
label advertise non-null
mpls rsvp-te
mpls rsvp-te hello
mpls rsvp-te hello full-gr
mpls te cspf
#
mpls ldp
graceful-restart
#
interface XGigabitEthernet0/0/1
undo portswitch
description Site2_UPE3 to Core_SPE2
ip address 172.16.8.179 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group 1
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
#
interface XGigabitEthernet0/0/2
port link-type trunk
undo port trunk allow-pass vlan 1
#
interface XGigabitEthernet0/0/2.150
dot1q termination vid 150
ip binding vpn-instance vpna
arp direct-route enable
ip address 172.18.150.2 255.255.255.192
vrrp vrid 1 virtual-ip 172.18.150.1
vrrp vrid 1 preempt-mode timer delay 250
vrrp vrid 1 track bfd-session 2150 peer
vrrp vrid 1 backup-forward
arp broadcast enable
vrrp track bfd gratuitous-arp send enable
#
interface XGigabitEthernet0/0/4
undo portswitch
description Site2_UPE3 to Site2_UPE4
ip address 172.16.8.180 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group 3
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
#
interface LoopBack1
description ** GRT Management Loopback **
ip address 172.16.2.75 255.255.255.255
#
interface Tunnel111
description Site2_UPE3 to Core_SPE2
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.0.3
mpls te tunnel-id 111
mpls te record-route
mpls te affinity property 1 mask 1
ospf 1
silent-interface all
undo silent-interface XGigabitEthernet0/0/1
undo silent-interface XGigabitEthernet0/0/4
opaque-capability enable
graceful-restart period 600
bandwidth-reference 100000
flooding-control
area 0.0.0.0
authentication-mode md5 1 cipher %^%#zJm-P{(FiMrB0bLa^ST'z[!(UezNNTx\CQ6@N\,K%^%#
network 172.16.2.75 0.0.0.0
network 172.16.8.179 0.0.0.0
network 172.16.8.180 0.0.0.0
mpls-te enable
#
route-policy mixfrr permit node 0
apply backup-nexthop 172.16.2.76
#
route-policy p_iBGP_host_ex permit node 10
apply community 200:200 5720:5720 23:23
#
route-policy p_iBGP_RR_ex permit node 0
apply community 200:200 5720:5720 23:23
#
arp expire-time 62640
arp static 172.18.150.4 0000-0001-0003 vid 150 interface XGigabitEthernet0/0/2.150
#
tunnel-policy TSel
tunnel select-seq cr-lsp lsp load-balance-number 1
#
bfd UPE3toSPE2_b bind mpls-te interface Tunnel111 te-lsp backup
discriminator local 1115
discriminator remote 1116
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd UPE3toSPE2_m bind mpls-te interface Tunnel111 te-lsp
discriminator local 1111
discriminator remote 1112
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd UPE3toSPE3_b bind mpls-te interface Tunnel112 te-lsp backup
discriminator local 1125
discriminator remote 1126
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd UPE3toSPE3_m bind mpls-te interface Tunnel112 te-lsp
discriminator local 1121
discriminator remote 1122
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
return
policy vpn-target
route-select delay 120
peer devCore enable
peer devCore route-policy p_iBGP_host_ex export
peer devCore advertise-community
peer 172.16.0.3 enable
peer 172.16.0.3 group devCore
peer 172.16.0.3 preferred-value 200
peer 172.16.0.4 enable
peer 172.16.0.4 group devCore
peer 172.16.0.4 preferred-value 300
peer devHost enable
peer devHost advertise-community
peer 172.16.2.75 enable
peer 172.16.2.75 group devHost
#
ipv4-family vpn-instance vpna
default-route imported
import-route direct route-policy p_iBGP_RR_ex
auto-frr
route-select delay 120
#
ospf 1
silent-interface all
undo silent-interface XGigabitEthernet0/0/1
undo silent-interface XGigabitEthernet0/0/4
opaque-capability enable
graceful-restart period 600
bandwidth-reference 100000
flooding-control
area 0.0.0.0
authentication-mode md5 1 cipher %^%#"sZy-UeQ88(kmb#.o"Y8*@/_9D[_<-3ET`+!1no4%^%#
network 172.16.2.76 0.0.0.0
network 172.16.8.181 0.0.0.0
network 172.16.8.182 0.0.0.0
mpls-te enable
#
route-policy mixfrr permit node 0
apply backup-nexthop 172.16.2.75
#
route-policy p_iBGP_host_ex permit node 0
apply community 300:300 5720:5720 23:23
#
route-policy p_iBGP_RR_ex permit node 0
apply community 300:300 5720:5720 23:23
#
arp expire-time 62640
arp static 172.18.150.4 0000-0001-0003 vid 150 interface XGigabitEthernet0/0/2.150
#
tunnel-policy TSel
tunnel select-seq cr-lsp lsp load-balance-number 1
#
bfd UPE4toSPE2_b bind mpls-te interface Tunnel121 te-lsp backup
discriminator local 1215
discriminator remote 1216
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd UPE4toSPE2_m bind mpls-te interface Tunnel121 te-lsp
discriminator local 1211
discriminator remote 1212
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd UPE4toSPE3_b bind mpls-te interface Tunnel122 te-lsp backup
discriminator local 1225
discriminator remote 1226
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd UPE4toSPE3_m bind mpls-te interface Tunnel122 te-lsp
discriminator local 1221
discriminator remote 1222
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
return
#
bfd UPE5toSPE1_b bind mpls-te interface Tunnel721 te-lsp backup
discriminator local 7215
discriminator remote 7216
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd UPE5toSPE1_m bind mpls-te interface Tunnel721 te-lsp
discriminator local 7211
discriminator remote 7212
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd UPE5toSPE3_b bind mpls-te interface Tunnel722 te-lsp backup
discriminator local 7225
discriminator remote 7226
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
bfd UPE5toSPE3_m bind mpls-te interface Tunnel722 te-lsp
discriminator local 7221
discriminator remote 7222
detect-multiplier 8
min-tx-interval 3
min-rx-interval 3
process-pst
commit
#
return
mpls te cspf
#
mpls ldp
graceful-restart
#
interface XGigabitEthernet0/0/2
port link-type trunk
undo port trunk allow-pass vlan 1
#
interface XGigabitEthernet0/0/2.100
dot1q termination vid 100
ip binding vpn-instance vpna
arp direct-route enable
ip address 172.18.100.3 255.255.255.192
vrrp vrid 1 virtual-ip 172.18.100.1
vrrp vrid 1 priority 90
vrrp vrid 1 preempt-mode timer delay 250
vrrp vrid 1 track bfd-session 2150 peer
vrrp vrid 1 backup-forward
arp broadcast enable
vrrp track bfd gratuitous-arp send enable
#
interface XGigabitEthernet0/0/1
undo portswitch
description Site3_UPE6 to Site3_UPE5
ip address 172.17.10.1 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group 3
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
#
interface XGigabitEthernet0/0/4
undo portswitch
description Site3_UPE6 to Core_SPE1
ip address 172.17.10.3 255.255.255.254
ospf network-type p2p
ospf ldp-sync
ospf timer ldp-sync hold-down 20
mpls
mpls te
mpls te link administrative group 1
mpls rsvp-te
mpls rsvp-te hello
mpls ldp
#
interface LoopBack1
description ** GRT Management Loopback **
ip address 172.16.2.86 255.255.255.255
#
interface Tunnel711
description Site3_UPE6 to Core_SPE1
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.0.5
mpls te tunnel-id 311
mpls te record-route
mpls te affinity property 1 mask 1
mpls te affinity property 2 mask 2 secondary
mpls te backup hot-standby
mpls te commit
#
interface Tunnel712
description Site3_UPE6 to Core_SPE3
ip address unnumbered interface LoopBack1
tunnel-protocol mpls te
destination 172.16.0.4
mpls te tunnel-id 321
mpls te record-route
mpls te affinity property 2 mask 2
mpls te affinity property 1 mask 1 secondary
mpls te backup hot-standby
mpls te commit
#
bfd vrrp-1 bind peer-ip 172.18.100.2 vpn-instance vpna interface XGigabitEthernet0/0/2.100 source-ip
172.18.100.3 auto
min-tx-interval 3
min-rx-interval 3
commit
#
bgp 65000
graceful-restart
group devCore internal
peer devCore connect-interface LoopBack1
peer 172.16.0.4 as-number 65000
peer 172.16.0.4 group devCore
peer 172.16.0.5 as-number 65000
peer 172.16.0.5 group devCore
group devHost internal
peer devHost connect-interface LoopBack1
peer 172.16.2.87 as-number 65000
peer 172.16.2.87 group devHost
#
ipv4-family unicast
undo synchronization
undo peer devCore enable
undo peer devHost enable
undo peer 172.16.0.4 enable
undo peer 172.16.0.5 enable
undo peer 172.16.2.87 enable
#
ipv4-family vpnv4
policy vpn-target
route-select delay 120
peer devCore enable
peer devCore route-policy p_iBGP_host_ex export
peer devCore advertise-community
peer 172.16.0.4 enable
peer 172.16.0.4 group devCore
peer 172.16.0.4 preferred-value 200
peer 172.16.0.5 enable
peer 172.16.0.5 group devCore
peer 172.16.0.5 preferred-value 300
peer devHost enable
peer devHost advertise-community
peer 172.16.2.87 enable
peer 172.16.2.87 group devHost
#
ipv4-family vpn-instance vpna
default-route imported
import-route direct route-policy p_iBGP_RR_ex
auto-frr
route-select delay 120
#
ospf 1
silent-interface all
undo silent-interface XGigabitEthernet0/0/1
undo silent-interface XGigabitEthernet0/0/4
opaque-capability enable
graceful-restart period 600
bandwidth-reference 100000
flooding-control
area 0.0.0.0
authentication-mode md5 1 cipher %#%#<3.TS63Ml*_Gn]2$}@O/G8llX)VNvDY\kT;4E9-A%#%#
Configuration Notes
On the NGFW side, two fixed internal Ethernet interfaces are GE1/0/0 and
GE1/0/1. On the switch side, the internal Ethernet interface numbers depend on
the slot ID of the NGFW module. For example, when the NGFW module is
installed in slot 1, the interface numbers are XGE1/0/0 and XGE1/0/1.
On the ACU2 side, two fixed internal Ethernet interfaces are XGE0/0/1 and
XGE0/0/2. On the switch side, the internal Ethernet interface numbers depend on
the slot ID of the ACU2. For example, when the ACU2 is installed in slot 2, the
interface numbers are XGE2/0/0 and XGE2/0/1.
Table 2-26 lists the products and versions to which this configuration example is
applicable.
Networking Requirements
Two switches are located on the network shown in Figure 2-29. Switch_1 has
NGFW and ACU2 configured. Traffic policies are configured on NGFW.
The customer wants to use ACU2 to manage the wireless network, providing
stable wireless service to STAs.
Network
GE1
/0/0 XG
NGFW_1 E1/0 XGE3/0/1
GE1 /0
/0/1 XG
E1/0
/1 Switch_1
1
trunk
Eth_ trunk
1 Eth_trunk0
Eth_
ACU2_1
Eth_trunk0
Switch_2
GE0/0/1
AP
Data Plan
Table 2-27, Table 2-28, and Table 2-29 provide the data plan.
Eth-trunk1 XGE2/0/0
XGE2/0/1
Configuration Roadmap
The configuration roadmap is as follows:
1. Configure Eth-Trunk on each switch and add interfaces to VLANs. Configure
the interfaces connecting Switch_2 to the DHCP server and AP to implement
network connectivity.
2. Implement connections between ACU2 and Switch_1.
3. Implement connections between NGFW and Switch_1.
4. Configure wireless service on ACU2. Wireless service traffic is forwarded
through tunnels, and ACU2_1 functions as a DHCP server to assign IP
addresses to APs and STAs.
5. Configure traffic policies on each interface of Switch_1 and Switch_2 to ensure
that STAs can successfully go online. The configurations include:
– Configure a redirection policy for the inbound traffic on Eth-Trunk 1,
which is the internal interface between switch and ACU2, to redirect the
upstream wireless traffic to XGE1/0/1, which is the internal interface
between switch and NGFW. When traffic is forwarded from NGFW to
XGE1/0/0, the traffic matches the inbound redirection policy again, and is
forwarded to upstream interface XGE3/0/1.
– Configure a redirection policy for the inbound traffic on XGE3/0/1 to
redirect the downstream wireless traffic to XGE1/0/0, which is the internal
interface between switch and NGFW. When traffic is forwarded from
NGFW to XGE1/0/1, the traffic matches the inbound redirection policy
again, and is forwarded to Eth-Trunk 0, which is the internal interface
between switch and ACU2.
Procedure
Step 1 Configure Eth-Trunks between Switch_1 and Switch_2.
# Configure Switch_1.
<HUAWEI> system-view
[HUAWEI] sysname Switch_1
[Switch_1] vlan batch 42 428
[Switch_1] interface Eth-Trunk 0
[Switch_1-Eth-Trunk0] port link-type trunk
[Switch_1-Eth-Trunk0] port trunk allow-pass vlan 42
[Switch_1-Eth-Trunk0] quit
[Switch_1] interface XGigabitEthernet 3/0/2
[Switch_1-XGigabitEthernet3/0/2] eth-trunk 0
[Switch_1-XGigabitEthernet3/0/2] quit
[Switch_1] interface XGigabitEthernet 3/0/3
[Switch_1-XGigabitEthernet3/0/3] eth-trunk 0
[Switch_1-XGigabitEthernet3/0/3] quit
<HUAWEI> system-view
[HUAWEI] sysname Switch_2
[Switch_2] vlan batch 42 428
[Switch_2] interface Eth-Trunk 0
[Switch_2-Eth-Trunk0] port link-type trunk
[Switch_2-Eth-Trunk0] port trunk allow-pass vlan 42
[Switch_2-Eth-Trunk0] quit
[Switch_2] interface XGigabitEthernet 0/0/1
[Switch_2-XGigabitEthernet0/0/1] eth-trunk 0
[Switch_2-XGigabitEthernet0/0/1] quit
[Switch_2] interface XGigabitEthernet 0/0/2
[Switch_2-XGigabitEthernet0/0/2] eth-trunk 0
[Switch_2-XGigabitEthernet0/0/2] quit
To facilitate verification, all packets within VLAN 428 are allowed in this example. Modify the
IPSec policy after verification if necessary.
[NGFW_1] security-policy
[NGFW_1-policy-security] rule name policy1
[NGFW_1-policy-security-rule-policy1] source-zone trust
[NGFW_1-policy-security-rule-policy1] destination-zone untrust
[NGFW_1-policy-security-rule-policy1] action permit
[NGFW_1-policy-security-rule-policy1] quit
[NGFW_1-policy-security] rule name policy2
[NGFW_1-policy-security-rule-policy2] source-zone untrust
[NGFW_1-policy-security-rule-policy2] destination-zone trust
[NGFW_1-policy-security-rule-policy2] action permit
[NGFW_1-policy-security-rule-policy2] quit
[NGFW_1-policy-security] quit
# Check that the Eth-Trunk 1 status between ACU2 and Switch_1 is normal.
<ACU2_1> display interface brief | include up
PHY: Physical
*down: administratively down
(l): loopback
(s): spoofing
(b): BFD down
(e): ETHOAM down
InUti/OutUti: input utility/output utility
Interface PHY Protocol InUti OutUti inErrors outErrors
Eth-Trunk1 up up 0.01% 0.01% 0 0
XGigabitEthernet0/0/1 up up 0.01% 0.01% 0 0
XGigabitEthernet0/0/2 up up 0% 0% 0 0
Total Error: 0
CRC: 0, Giants: 0
Jabbers: 0, Fragments: 0
Runts: 0, DropEvents: 0
Alignments: 0, Symbols: 0
Ignoreds: 0, Frames: 0
Total Error: 0
Collisions: 0, ExcessiveCollisions: 0
Late Collisions: 0, Deferreds: 0
Buffers Purged: 0
Total Error: 0
CRC: 0, Giants: 0
Jabbers: 0, Fragments: 0
Runts: 0, DropEvents: 0
Alignments: 0, Symbols: 0
Ignoreds: 0, Frames: 0
Total Error: 0
Collisions: 0, ExcessiveCollisions: 0
Late Collisions: 0, Deferreds: 0
Buffers Purged: 0
----End
Configuration Files
● Switch_1 configuration file
sysname Switch_1
#
vlan batch 42 428
#
traffic classifier service_vlan operator or precedence 50
if-match vlan-id 428
#
traffic behavior Redirect_to_XGE3/0/1
permit
redirect interface XGigabitEthernet3/0/1
traffic behavior Redirect_to_ETH1
permit
redirect interface Eth-Trunk1
traffic behavior Redirect_to_XGE1/0/0
permit
redirect interface XGigabitEthernet1/0/0
traffic behavior Redirect_to_XGE1/0/1
permit
redirect interface XGigabitEthernet1/0/1
#
traffic policy Redirect_to_XGE3/0/1 match-order config
classifier service_vlan behavior Redirect_to_XGE3/0/1
traffic policy Redirect_to_ETH1 match-order config
classifier service_vlan behavior Redirect_to_ETH1
traffic policy Redirect_to_XGE1/0/0 match-order config
classifier service_vlan behavior Redirect_to_XGE1/0/0
traffic policy Redirect_to_XGE1/0/1 match-order config
classifier service_vlan behavior Redirect_to_XGE1/0/1
#
interface Eth-Trunk0
description to Core
port link-type trunk
port trunk allow-pass vlan 42
#
interface Eth-Trunk1
description to ACU_1 Slot2
port link-type trunk
port trunk allow-pass vlan 42 428
traffic-policy Redirect_to_XGE1/0/1 inbound
#
interface XGigabitEthernet1/0/0
port link-type trunk
mac-address learning disable
port trunk allow-pass vlan 428
stp disable
traffic-policy Redirect_to_XGE3/0/1 inbound
carrier up-hold-time 10000
am isolate XGigabitEthernet1/0/1
#
interface XGigabitEthernet1/0/1
port link-type trunk
mac-address learning disable
port trunk allow-pass vlan 428
stp disable
traffic-policy Redirect_to_ETH1 inbound
carrier up-hold-time 10000
am isolate XGigabitEthernet1/0/0
#
interface XGigabitEthernet2/0/0
eth-trunk 1
#
interface XGigabitEthernet2/0/1
eth-trunk 1
#
interface XGigabitEthernet3/0/1
port link-type trunk
port trunk allow-pass vlan 428
traffic-policy Redirect_to_XGE1/0/0 inbound
#interface XGigabitEthernet3/0/2
eth-trunk 0
#
interface XGigabitEthernet3/0/3
eth-trunk 0
#
return
● Switch_2 configuration file
#
sysname Switch_2
#
vlan batch 42
#
interface Eth-Trunk0
port link-type trunk
port trunk allow-pass vlan 42
#
interface XGigabitEthernet0/0/1
eth-trunk 0
#
interface XGigabitEthernet0/0/2
eth-trunk 0
#
interface GigabitEthernet0/0/1
port link-type trunk
port type pvid vlan 42
port type allow vlan 42
#
return
● ACU2_1 configuration file
#
sysname ACU2_1
#
vlan batch 42 428
#
wlan ac-global carrier id other ac id 1
#
dhcp enable
#
interface Vlanif42
ip address 172.18.255.240 255.255.255.0
dhcp select interface
#
interface Vlanif428
ip address 172.16.29.1 255.255.255.0
dhcp select interface
#
interface Eth-Trunk1
port link-type trunk
port trunk allow-pass vlan 42
#
interface XGigabitEthernet0/0/1
eth-trunk 1
#
interface XGigabitEthernet0/0/2
eth-trunk 1
#
interface Wlan-Ess1
port hybrid pvid vlan 428
port hybrid untagged vlan 428
#
capwap source interface vlanif42
#
wlan
ap-region id 0
ap-auth-mode mac-auth
ap id 1 type-id 19 mac 9c37-f48c-0c40 sn 21023585619WF6000564
region-id 0
Background
The IPS module is a card providing the intrusion defense function. It provides
intrusion defense, antivirus, and anti-DDoS for IP networks.
Deploying IPS modules and The NGFW modules work in the interface pair
NGFW modules on a Layer 2 mode, and the flows from switches are received
dual-node system and by a Layer 2 Eth-Trunk.
importing flows through The IP address of the firewall subinterface is the
redirection gateway address for upstream and downstream
networks.
Deploying IPS modules at The NGFW modules work in the routing mode,
Layer 2 and NGFW modules and the flows from switches are received by a
on a Layer 3 dual-node Layer 3 Eth-Trunk subinterface.
system, and importing flows The VLANIF interface address on a switch is the
based on policy routing gateway address for upstream and downstream
networks.
Table 2-31 lists the products and versions to which this configuration example is
applicable.
Networking Requirements
Two S12700s are deployed on a network shown in Figure 2-30. An NGFW module
and an IPS module are installed in slot 4 and slot 5 respectively on each S12700.
The two S12700s set up a cluster and work in hot standby mode. The IPS modules
and NGFW modules work at Layer 2. That is, they access the network
transparently.
The customer has the following requirements:
● The inter-client flows and inter-server flows within a subnet are directly
forwarded by the switches.
● The inter-client flows on different subnets and the flows between clients and
the extranet are checked by the NGFW modules.
● The flows between clients/extranet and servers and the inter-server flows on
different subnets are filtered by the IPS modules and then checked by the
NGFW modules.
Each IPS/NGFW module is connected to a switch through two 20GE Ethernet links. The ports on
the two ends of each internal Ethernet link are on the switch and IPS or NGFW module.
When the IPS module and NGFW module are connected to the switch, the internal Ethernet
interfaces used by the two modules are fixed as GE1/0/0 and GE1/0/1. The internal Ethernet
interfaces on the switch depend on the slot IDs of the IPS module and NGFW module. For
example, when the IPS module is installed in slot 1, the numbers of interfaces connected to the
IPS module on the switch are XGE1/0/0 and XGE1/0/1.
Figure 2-30 Deploying IPS module and NGFW module on a Layer 2 dual-node
system and importing flows through redirection
Extranet
VLAN 2001
Eth-Trunk0 Eth-Trunk0
192.168.213.5/30 192.168.213.6/30
1/0
GE Heartbeat line /0
1/0
GE /0 X G E
1/0 GE
/0/
0 /0/1
/1 1 E1
IPS XG /5/0/0 E2
/ 5
/1
G IPS
Module_A E1/ XG 2/5/0 Module_B
5/0 CSS E
/1
XG
XG
/0 /0 E2
1 /4 1 Switch_A Switch_B XG /4
NGFW G E /0 / E2 /0/0
X / 4 /4 NGFW
Module_A 0 G E1 /0
/ GE Module_B
/ X 1
1/0 1
GE /0/0
GE /0/1 1/0
1
GE /1
Heartbeat line
Eth-Trunk0 Eth-Trunk0
192.168.213.1/30 192.168.213.2/30
Client Server
VLAN 101,
VLAN 100,300
102,103 ... 126
Extranet
10.54.1.251/29
IPS
Module
NGFW
CSS Module
Client
10.55.1.10/24 10.55.2.10/24
10.55.1.20/24
Ø Inter-client flow within a subnet
directly forwarded by switch
Ø Inter-client flow between subnets
checked by the NGFW Module
Ø Flow between clients and extranet
checked by the NGFW Module
Extranet Extranet
10.54.1.251/29 10.54.1.251/29
IPS
NGFW
Module
Module
NGFW IPS
CSS Module CSS Module
Extranet Extranet
10.54.1.251/29 10.54.1.251/29
IPS NGFW
Module Module
NGFW IPS
CSS Module CSS Module
Server Server
10.55.0.10/24 10.55.200.10/24 10.55.0.10/24 10.55.200.10/24
10.55.0.20/24 10.55.0.20/24
Extranet Extranet
10.54.1.251/29 10.54.1.251/29
IPS NGFW
Module Module
NGFW IPS
CSS Module CSS Module
Server Server
10.55.0.20/24 10.55.0.20/24
Ø Flow between extranet and servers
filter by IPS Module first, and then
checked by NGFW Module
Data Plan
Table 2-32, Table 2-33, and Table 2-34 provide the data plan.
Data Remarks
Configuration Roadmap
1. Configure interfaces on NGFW Module_A and NGFW Module_B and set basic
parameters.
2. Configure NGFW Module_A and NGFW Module_B as a Layer 2 hot standby
system working in load balancing mode.
3. Configure the security service on NGFW Module_A to allow the flows from
clients, servers, and extranet to pass and prevent intrusion. The configurations
on NGFW Module_A can be automatically backed up to NGFW Module_B.
4. Configure interfaces on IPS Module_A and IPS Module_B and set basic
parameters.
5. Configure IPS Module_A and IPS Module_B as a Layer 2 hot standby system
working in load balancing mode.
6. Configure the security service on IPS Module_A, for example, antivirus. The
configurations on IPS Module_A can be automatically backed up to IPS
Module_B.
7. Configure the two S12700s as a cluster.
8. Implement connectivity between S12700 cluster, NGFW modules, and IPS
modules.
9. Configure a traffic policy on the S12700 cluster and apply the policy to
interfaces to implement redirection.
Procedure
Step 1 Configure interfaces on NGFW modules and set basic parameters.
# Log in to the CLI of NGFW Module_A from Switch_A.
<sysname> connect slot 4
# Create Layer 2 Eth-Trunk 1 on NGFW Module_A and allow the packets from
upstream and downstream VLANs to pass.
[NGFW Module_A] interface Eth-Trunk 1
[NGFW Module_A-Eth-Trunk1] description To-master-trunk101
[NGFW Module_A-Eth-Trunk1] portswitch
[NGFW Module_A-Eth-Trunk1] port link-type trunk
[NGFW Module_A-Eth-Trunk1] undo port trunk permit vlan 1
[NGFW Module_A-Eth-Trunk1] port trunk permit vlan 100 to 126 300 2001
[NGFW Module_A-Eth-Trunk1] quit
Only the Layer 3 physical interfaces with empty configuration can be added to Eth-Trunks. For
example, if LLDP has been enabled on a physical interface of the NGFW module, run the undo
lldp enable command on the interface before adding it to an Eth-Trunk.
[NGFW Module_A] interface GigabitEthernet 1/0/0
[NGFW Module_A-GigabitEthernet1/0/0] portswitch
[NGFW Module_A-GigabitEthernet1/0/0] port link-type access
[NGFW Module_A-GigabitEthernet1/0/0] Eth-Trunk 1
[NGFW Module_A-GigabitEthernet1/0/0] quit
[NGFW Module_A] interface GigabitEthernet 1/0/1
[NGFW Module_A-GigabitEthernet1/0/1] portswitch
[NGFW Module_A-GigabitEthernet1/0/1] port link-type access
[NGFW Module_A-GigabitEthernet1/0/1] Eth-Trunk 1
[NGFW Module_A-GigabitEthernet1/0/1] quit
2. Choose Network > Interface, click of interface GE1/0/0 and set the
connection type of GE1/0/0 to access.
The configurations on the two IPS Modules are the same. The following part
provides the configuration on one IPS Module.
5. Choose Network > Interface Pair, click Add, and configure an interface pair.
The configurations on the two IPS Modules are the same. The following part
provides the configuration on one IPS Module.
6. Click Add and bundle GE 0/0/1 and GE 0/0/2 into an Eth-Trunk interface as
the heartbeat interface and backup channel.
– The IP addresses of heartbeat interfaces on the IPS Modules must be in the same
network segment.
– The Eth-Trunk member interfaces on the IPS Modules must be the same.
7. Choose System > Dual-System Hot Backup, click Edit, and configure hot
standby.
The configurations on the two IPS Modules are the same. The following part
provides the configuration on one IPS Module.
After hot standby is configured, the configurations and sessions on the active
device are automatically synchronized to the standby device; therefore, you only
need to configure the security service on IPS Module_A.
3. Click OK.
4. Repeat the previous steps to set the parameters of AV_ftp profile.
After hot standby is configured, the configurations and sessions on the active
device are automatically synchronized to the standby device; therefore, you only
need to configure the security policy on IPS Module_A.
Name policy_av_1
Description Intranet-User
Action permit
Content Security
Anti-Virus AV_http_pop3
Step 7 Configure the security policy in the direction from the external to internal servers.
After hot standby is configured, the configurations and sessions on the active
device are automatically synchronized to the standby device; therefore, you only
need to configure the security policy on IPS Module_A.
Refer to the method of configuring the security policy in the direction from
internal clients to external servers. The parameters are as follows.
Name policy_av_2
Description Intranet-Server
Action permit
Content Security
Anti-Virus AV_ftp
Chassis Id CSS Enable CSS Status CSS Mode Priority Master Force
------------------------------------------------------------------------------
1 On Master CSS card 100 Off
2 On Standby CSS card 10 Off
The preceding information includes the cluster IDs, priorities, cluster
enablement status, and cluster status, indicating that the cluster is
successfully established.
# Check whether cluster links work normally.
[Switch_A] display css channel
The command output shows that all the cluster links are working normally,
indicating that the cluster is established successfully.
[CSS-classifier-from-office] quit
[CSS] traffic classifier to-office operator or precedence 85
[CSS-classifier-to-office] if-match acl 3011
[CSS-classifier-to-office] quit
[CSS] traffic classifier from-server operator or precedence 75
[CSS-classifier-from-server] if-match acl 3020
[CSS-classifier-from-server] quit
[CSS] traffic classifier to-server operator or precedence 60
[CSS-classifier-to-server] if-match acl 3021
[CSS-classifier-to-server] quit
[CSS] traffic classifier office-office operator or precedence 40
[CSS-classifier-office-office] if-match acl 3012
[CSS-classifier-office-office] quit
[CSS] traffic classifier server-server operator or precedence 65
[CSS-classifier-server-server] if-match acl 3022
[CSS-classifier-server-server] quit
# Check the status of Eth-Trunks between IPS/NGFW modules and S12700 cluster.
[IPS Module] display interface brief | include up
2016/5/31 10:49
PHY: Physical
*down: administratively down
^down: standby down
(s): spoofing
InUti/OutUti: input utility/output utility
Interface PHY Protocol InUti OutUti inErrors outErrors
Eth-Trunk0 up up 0.01% 0.01% 0 0
GigabitEthernet0/0/1 up up 0.01% 0.01% 0 0
GigabitEthernet0/0/2 up up 0% 0% 0 0
Eth-Trunk1 up up 0.01% 0.01% 0 0
GigabitEthernet1/0/0(XGE) up up 0.01% 0.01% 0 0
GigabitEthernet1/0/1(XGE) up up 0% 0% 0 0
NULL0 up up(s) 0% 0% 0 0
[NGFW Module_B] display interface brief | include up
10:56:34 2016/05/31
PHY: Physical
*down: administratively down
^down: standby down
(s): spoofing
InUti/OutUti: input utility/output utility
Interface PHY Protocol InUti OutUti inErrors outErrors
Eth-Trunk0 up up 0.01% 0.01% 0 0
GigabitEthernet0/0/1 up up 0.01% 0.01% 0 0
GigabitEthernet0/0/2 up up 0% 0.01% 0 0
Eth-Trunk1 up up 0.01% 0.01% 0 0
GigabitEthernet1/0/0(XGE) up up 0.01% 0.01% 0 0
GigabitEthernet1/0/1(XGE) up up 0% 0% 0 0
NULL0 up up(s) 0% 0% 0 0
----End
Configuration Files
● NGFW module configuration files
eth-trunk 101
#
interface XGigabitEthernet1/5/0/0
eth-trunk 100
#
interface XGigabitEthernet1/5/0/1
eth-trunk 100
#
interface XGigabitEthernet2/4/0/0
eth-trunk 101
#
interface XGigabitEthernet2/4/0/1
eth-trunk 101
#
interface XGigabitEthernet2/5/0/0
eth-trunk 100
#
interface XGigabitEthernet2/5/0/1
eth-trunk 100
#
return
Networking Requirements
Two S12700s are deployed on a network shown in Figure 2-32. An NGFW module
and an IPS module are installed in slot 4 and slot 5 respectively on each S12700.
The two S12700s set up a cluster and work in hot standby mode. The IPS modules
work at Layer 2. That is, they access the network transparently. The NGFW
modules work at Layer 3 (flows imported at Layer 3) in active/standby mode.
The customer has the following requirements:
● The inter-client flows and inter-server flows within a subnet are directly
forwarded by the switches.
● The inter-client flows on different subnets and the flows between clients and
the extranet are checked by the NGFW modules.
● The flows between clients/extranet and servers and the inter-server flows on
different subnets are filtered by the IPS modules and then checked by the
NGFW modules.
Figure 2-33 shows the flow directions.
Each IPS/NGFW module is connected to a switch through two 20GE Ethernet links. The ports on
the two ends of each internal Ethernet link are on the switch and IPS or NGFW module.
When the IPS module and NGFW module are connected to the switch, the internal Ethernet
interfaces used by the two modules are fixed as GE1/0/0 and GE1/0/1. The internal Ethernet
interfaces on the switch depend on the slot IDs of the IPS module and NGFW module. For
example, when the IPS module is installed in slot 1, the numbers of interfaces connected to the
IPS module on the switch are XGE1/0/0 and XGE1/0/1.
Figure 2-32 Deploying IPS modules at Layer 2 and NGFW modules on a Layer 3
dual-node system, and importing flows based on policy routing
Extranet
VLAN 2001
Eth-Trunk0 Eth-Trunk0
192.168.213.5/30 192.168.213.6/30
GE
1/0
Heartbeat line /0
1/0
GE /0 X GE 0/1
1/0 GE 0 /
/1 1 /0/ E1
IPS XG /5/0/0 E 2/5 /1 G IPS
Module_A E1/5 XG 2/5/0 Module_B
/0/1 CSS E
XG
XG
0/0 E
1 /4/ 1 Switch_A Switch_B XG 2/4/
NGFW E 0 / E 0
XG 1/4/ 2/ /0 NGFW
Module_A 0 E 4/0
/ X G / 1 G E1Module_B
E 1/0 1 /0
G / 0 / G E1 /0
1 /0/
GE 1
Heartbeat line
Eth-Trunk0 Eth-Trunk0
192.168.213.1/30 192.168.213.2/30
Client Server
VLAN 101,
VLAN 100,300
102,103 ... 126
Extranet
10.54.1.251/29
IPS
Module
NGFW
CSS Module
Client
10.55.1.10/24 10.55.2.10/24
10.55.1.20/24
Ø Inter-client flow within a subnet
directly forwarded by switch
Ø Inter-client flow between subnets
checked by the NGFW Module
Ø Flow between clients and extranet
checked by the NGFW Module
Extranet Extranet
10.54.1.251/29 10.54.1.251/29
IPS
NGFW
Module
Module
NGFW IPS
CSS Module CSS Module
Extranet Extranet
10.54.1.251/29 10.54.1.251/29
IPS NGFW
Module Module
NGFW IPS
CSS Module CSS Module
Server Server
10.55.0.10/24 10.55.200.10/24 10.55.0.10/24 10.55.200.10/24
10.55.0.20/24 10.55.0.20/24
Extranet Extranet
10.54.1.251/29 10.54.1.251/29
IPS NGFW
Module Module
NGFW IPS
CSS Module CSS Module
Server Server
10.55.0.20/24 10.55.0.20/24
Ø Flow between extranet and servers
filter by IPS Module first, and then
checked by NGFW Module
Data Plan
Table 2-35, Table 2-36, and Table 2-37 provide the data plan.
Configuration Roadmap
1. Configure interfaces and static routes on NGFW Module_A and NGFW
Module_B and set basic parameters.
2. Configure NGFW Module_A and NGFW Module_B as a Layer 3 VRRP group
working in hot standby mode.
3. Configure the security service on NGFW Module_A to allow the flows from
clients, servers, and extranet to pass and prevent intrusion. The configurations
on NGFW Module_A can be automatically backed up to NGFW Module_B.
4. Configure interfaces on IPS Module_A and IPS Module_B and set basic
parameters.
5. Configure IPS Module_A and IPS Module_B as a Layer 2 hot standby system
working in load balancing mode.
6. Configure the security service on IPS Module_A, for example, antivirus. The
configurations on IPS Module_A can be automatically backed up to IPS
Module_B.
7. Configure the two S12700s as a cluster.
8. Implement connectivity between S12700 cluster, NGFW modules, and IPS
modules.
9. Configure a routing policy on the S12700 cluster to implement redirection.
Procedure
Step 1 Configure interfaces on NGFW modules and set basic parameters.
# Log in to the CLI of NGFW Module_A from Switch_A.
<sysname> connect slot 4
Only the Layer 3 physical interfaces with empty configuration can be added to Eth-Trunks. For
example, if LLDP has been enabled on a physical interface of the NGFW module, run the undo
lldp enable command on the interface before adding it to an Eth-Trunk.
[NGFW Module_A] interface GigabitEthernet 1/0/0
[NGFW Module_A-GigabitEthernet1/0/0] Eth-Trunk 1
[NGFW Module_A-GigabitEthernet1/0/0] quit
[NGFW Module_A] interface GigabitEthernet 1/0/1
[NGFW Module_A-GigabitEthernet1/0/1] Eth-Trunk 1
[NGFW Module_A-GigabitEthernet1/0/1] quit
After hot standby is configured, the configurations and sessions on the active
device are automatically synchronized to the standby device; therefore, you only
need to configure the security service on NGFW Module_A.
# Configure the security policy on NGFW Module_A to allow the flows from
clients, servers, and extranet to pass and prevent intrusion.
HRP_M[NGFW Module_A] security-policy
HRP_M[NGFW Module_A-policy-security] rule name policy_to_wan
HRP_M[NGFW Module_A-policy-security-rule_policy-policy_to_wan] source-address 10.55.0.0 16 //Subnet
where clients and servers reside
HRP_M[NGFW Module_A-policy-security-rule_policy-policy_to_wan] source-address 10.54.1.248 29 //
Subnet of the extranet
HRP_M[NGFW Module_A-policy-security-rule-policy_policy_to_wan] profile ips default
HRP_M[NGFW Module_A-policy-security-rule-policy_policy_to_wan] action permit
HRP_M[NGFW Module_A-policy-security-rule-policy_policy_to_wan] quit
HRP_M[NGFW Module_A-policy-security] quit
2. Choose Network > Interface, click of interface GE1/0/0 and set the
connection type of GE1/0/0 to access.
The configurations on the two IPS Modules are the same. The following part
provides the configuration on one IPS Module.
5. Choose Network > Interface Pair, click Add, and configure an interface pair.
The configurations on the two IPS Modules are the same. The following part
provides the configuration on one IPS Module.
6. Click Add and bundle GE 0/0/1 and GE 0/0/2 into an Eth-Trunk interface as
the heartbeat interface and backup channel.
– The IP addresses of heartbeat interfaces on the IPS Modules must be in the same
network segment.
– The Eth-Trunk member interfaces on the IPS Modules must be the same.
7. Choose System > Dual-System Hot Backup, click Edit, and configure hot
standby.
The configurations on the two IPS Modules are the same. The following part
provides the configuration on one IPS Module.
After hot standby is configured, the configurations and sessions on the active
device are automatically synchronized to the standby device; therefore, you only
need to configure the security service on IPS Module_A.
3. Click OK.
4. Repeat the previous steps to set the parameters of AV_ftp profile.
After hot standby is configured, the configurations and sessions on the active
device are automatically synchronized to the standby device; therefore, you only
need to configure the security policy on IPS Module_A.
Name policy_av_1
Description Intranet-User
Action permit
Content Security
Anti-Virus AV_http_pop3
Step 7 Configure the security policy in the direction from the external to internal servers.
After hot standby is configured, the configurations and sessions on the active
device are automatically synchronized to the standby device; therefore, you only
need to configure the security policy on IPS Module_A.
Refer to the method of configuring the security policy in the direction from
internal clients to external servers. The parameters are as follows.
Name policy_av_2
Description Intranet-Server
Action permit
Content Security
Anti-Virus AV_ftp
Chassis Id CSS Enable CSS Status CSS Mode Priority Master Force
------------------------------------------------------------------------------
1 On Master CSS card 100 Off
2 On Standby CSS card 10 Off
The preceding information includes the cluster IDs, priorities, cluster
enablement status, and cluster status, indicating that the cluster is
successfully established.
# Check whether cluster links work normally.
[Switch_A] display css channel
The command output shows that all the cluster links are working normally,
indicating that the cluster is established successfully.
3. Configure VLANIF interfaces. In this example, the VLANs of clients are VLAN
101, VLAN 102, and VLAN 126.
[CSS] interface vlanif 2001
[CSS-Vlanif2001] ip address 10.54.1.253 255.255.255.248
[CSS-Vlanif2001] quit
[CSS] interface vlanif 100
[CSS-Vlanif100] ip address 10.55.0.1 255.255.255.0
[CSS-Vlanif100] quit
[CSS] interface vlanif 300
[CSS-Vlanif300] ip address 10.55.200.1 255.255.255.0
[CSS-Vlanif300] quit
[CSS] interface Vlanif 101
[CSS-Vlanif101] ip address 10.55.1.1 255.255.255.0
[CSS-Vlanif101] quit
[CSS] interface vlanif 102
[CSS-Vlanif102] ip address 10.55.2.1 255.255.255.0
[CSS-Vlanif102] quit
[CSS] interface vlanif 126
[CSS-Vlanif126] ip address 10.55.26.1 255.255.255.0
[CSS-Vlanif126] quit
[CSS] interface vlanif 128 //Layer 3 interface connected to the NGFW module
[CSS-Vlanif128] ip address 10.55.28.4 255.255.255.0
[CSS-Vlanif128] quit
4. Add the eight interfaces between the switches and NGFW/IPS modules to
Eth-Trunk 105, Eth-Trunk 106, and Eth-Trunk 100.
[CSS] interface eth-trunk 105
[CSS-Eth-Trunk105] description to-ngfw-a
[CSS-Eth-Trunk105] port link-type trunk
[CSS-Eth-Trunk105] undo port trunk allow-pass vlan 1
[CSS-Eth-Trunk105] port trunk allow-pass vlan 128
[CSS-Eth-Trunk105] trunkport xgigabitethernet 1/4/0/0 to 1/4/0/1
[CSS-Eth-Trunk105] quit
[CSS] interface eth-trunk 106
[CSS-Eth-Trunk106] description to-ngfw-b
[CSS-Eth-Trunk106] port link-type trunk
[CSS-Eth-Trunk106] undo port trunk allow-pass vlan 1
[CSS-Eth-Trunk106] port trunk allow-pass vlan 128
[CSS-Eth-Trunk106] trunkport xgigabitethernet 2/4/0/0 to 2/4/0/1
[CSS-Eth-Trunk106] quit
[CSS] interface eth-trunk 100
[CSS-Eth-Trunk100] description to-ips
# Create ACLs.
[CSS] acl 3010 //Match the flows sent from clients
[CSS-acl-adv-3010] rule 5 permit ip source 10.55.1.0 0.0.0.255
[CSS-acl-adv-3010] rule 10 permit ip source 10.55.2.0 0.0.0.255
[CSS-acl-adv-3010] rule 15 permit ip source 10.55.26.0 0.0.0.255
[CSS-acl-adv-3010] quit
[CSS] acl 3011 //Match the flows destined for clients
[CSS-acl-adv-3011] rule 5 permit ip destination 10.55.1.0 0.0.0.255
[CSS-acl-adv-3011] rule 10 permit ip destination 10.55.2.0 0.0.0.255
[CSS-acl-adv-3011] rule 15 permit ip destination 10.55.26.0 0.0.0.255
[CSS-acl-adv-3011] quit
[CSS] acl 3020 //Match the flows sent from servers
[CSS-acl-adv-3020] rule 5 permit ip source 10.55.0.0 0.0.0.255
[CSS-acl-adv-3020] rule 10 permit ip source 10.55.200.0 0.0.0.255
[CSS-acl-adv-3020] quit
[CSS] acl 3021 //Match the flows destined for servers
[CSS-acl-adv-3021] rule 5 permit ip destination 10.55.0.0 0.0.0.255
[CSS-acl-adv-3021] rule 10 permit ip destination 10.55.200.0 0.0.0.255
[CSS-acl-adv-3021] quit
[CSS] acl 3012 //Match inter-client flows within a subnet
[CSS-acl-adv-3012] rule 5 permit ip source 10.55.1.0 0.0.0.255 destination 10.55.1.0 0.0.0.255
[CSS-acl-adv-3012] rule 10 permit ip source 10.55.2.0 0.0.0.255 destination 10.55.2.0 0.0.0.255
[CSS-acl-adv-3012] rule 15 permit ip source 10.55.26.0 0.0.0.255 destination 10.55.26.0 0.0.0.255
[CSS-acl-adv-3012] quit
[CSS] acl 3022 //Match inter-server flows within a subnet
[CSS-acl-adv-3022] rule 5 permit ip source 10.55.0.0 0.0.0.255 destination 10.55.0.0 0.0.0.255
[CSS-acl-adv-3022] rule 10 permit ip source 10.55.200.0 0.0.0.255 destination 10.55.200.0 0.0.0.255
[CSS-acl-adv-3022] quit
# Check the status of Eth-Trunks between IPS/NGFW modules and S12700 cluster.
[IPS Module] display interface brief | include up
2016/5/31 10:49
PHY: Physical
*down: administratively down
^down: standby down
(s): spoofing
InUti/OutUti: input utility/output utility
Interface PHY Protocol InUti OutUti inErrors outErrors
Eth-Trunk0 up up 0.01% 0.01% 0 0
GigabitEthernet0/0/1 up up 0.01% 0.01% 0 0
GigabitEthernet0/0/2 up up 0% 0% 0 0
Eth-Trunk1 up up 0.01% 0.01% 0 0
GigabitEthernet1/0/0(XGE) up up 0.01% 0.01% 0 0
GigabitEthernet1/0/1(XGE) up up 0% 0% 0 0
NULL0 up up(s) 0% 0% 0 0
[NGFW Module_B] display interface brief | include up
10:56:34 2016/05/31
PHY: Physical
*down: administratively down
^down: standby down
(s): spoofing
InUti/OutUti: input utility/output utility
Interface PHY Protocol InUti OutUti inErrors outErrors
Eth-Trunk0 up up 0.01% 0.01% 0 0
GigabitEthernet0/0/1 up up 0.01% 0.01% 0 0
GigabitEthernet0/0/2 up up 0% 0.01% 0 0
Eth-Trunk1 up up 0.01% 0.01% 0 0
GigabitEthernet1/0/0(XGE) up up 0.01% 0.01% 0 0
GigabitEthernet1/0/1(XGE) up up 0% 0% 0 0
Eth-Trunk1.1 up up 0.01% 0% 0 0
Eth-Trunk1.2 up up 0.01% 0% 0 0
NULL0 up up(s) 0% 0% 0 0
Vlanif300 up up -- -- 0 0
Vlanif2001 up up -- -- 0 0
----End
Configuration Files
● NGFW module configuration files
am isolate Eth-Trunk100
#
interface XGigabitEthernet1/4/0/0
eth-trunk 105
#
interface XGigabitEthernet1/4/0/1
eth-trunk 105
#
interface XGigabitEthernet1/5/0/0
eth-trunk 100
#
interface XGigabitEthernet1/5/0/1
eth-trunk 100
#
interface XGigabitEthernet2/4/0/0
eth-trunk 106
#
interface XGigabitEthernet2/4/0/1
eth-trunk 106
#
interface XGigabitEthernet2/5/0/0
eth-trunk 100
#
interface XGigabitEthernet2/5/0/1
eth-trunk 100
#
return
Service Requirements
As shown in Figure 2-34, two switches form a CSS, and two NGFW Modules are
installed in slot 1 of the switches respective and implement hot standby. The
NGFW Modules work at Layer 2 and are transparently connected to the network.
The NGFW Modules implement security check on traffic sent by intranet users to
the Internet. The traffic exchanged between different VLANs does not pass the
NGFW modules. Instead, the traffic is directly forwarded by the switches.
This example uses NGFW modules running V100R001C30 and switches running
V200R008C00. For the configuration examples of NGFW Modules running other
versions, see Deployment Guide. You can search for "Deployment Guide" in the
search bar.
Figure 2-34 Networking for Layer-2 dual-NGFW Module deployment and switch
CSS
Internet/WAN
10.3.0.5/24
The NGFW Module has two fixed internal Ethernet interfaces: GE1/0/0 to GE1/0/1. The
numbering of internal Ethernet interfaces on the switch is determined by the slot in which the
NGFW Module is installed. For example, when the NGFW Module is installed in slot 1 on the
switch, the internal Ethernet interfaces used by the switch are XGE1/1/0/0 to XGE1/1/0/1.
Eth-Trunk2 and Eth-Trunk3 are interfaces of the switches in the CSS.
Deployment Solution
The four interfaces connecting the switches to the NGFW modules are bundled
into an Eth-Trunk interface, and traffic is distributed among the two NGFW
Modules. The two NGFW Modules implement hot standby in Layer-2 load
balancing mode.
1. Add the four interfaces on the switches to Eth-Trunk 10 and four interfaces on
the NGFW Modules to Eth-Trunk 1.
2. Redirection is configured on the switches to direct traffic exchanged between
intranet users and the Internet to the NGFW Modules. Eth-Trunk 1 is
configured as an interface pair (packets entering the interface are forwarded
out of the same interface after being processed) on the NGFW Modules to
send traffic back to the switches.
When the NGFW Module works in interface pair mode, the switch cannot have the loop-
detection function enabled. If the switch has the loop-detection function enabled,
broadcast packets are sent out at the interface. Because the NGFW Module works in
interface pair mode, all packets received by the interface are sent out from this interface.
This causes the switch to detect traffic loops and disable the interface.
3. The NGFW Modules implement hot standby in Layer-2 load balancing mode.
Therefore, configure the VLANs to be tracked of the upstream and
downstream interfaces.
Figure 2-35 provides logical networking for easy understanding.
Internet
VLANIF 200
10.3.0.1
Eth-Trunk10 Eth-Trunk10
Eth-Trunk1 Eth-Trunk1
Eth-Trunk0
10.10.0.1/24
Eth-Trunk0
10.10.0.2/24
Eth-Trunk1 Eth-Trunk1
Eth-Trunk10 Eth-Trunk10
Figure 2-35 provides information only interfaces related to the switches and NGFW
Modules.
4. Bundle GE0/0/1 and GE0/0/2 interfaces on the panel of each NGFW Module
into an Eth-Trunk0 interface, which functions as the heartbeat interface and
backup channel and enable hot standby.
Procedure
Step 1 Complete interface and basic network configurations on NGFW Modules.
# Configure device name on NGFW Module_A.
<sysname> system-view
[sysname] sysname Module_A
# Create Layer-2 Eth-Trunk 1 on NGFW Module_A and permit packets from the
upstream and downstream VLANs.
[Module_A] interface Eth-Trunk 1
[Module_A-Eth-Trunk1] description To_SwitchA_trunk10
[Module_A-Eth-Trunk1] portswitch
[Module_A-Eth-Trunk1] port link-type trunk
[Module_A-Eth-Trunk1] port trunk permit vlan 200 301 to 302
[Module_A-Eth-Trunk1] quit
# Add the interfaces connecting NGFW Module_A to its connected switch to Eth-
Trunk 1.
[Module_A] interface GigabitEthernet 1/0/0
[Module_A-GigabitEthernet1/0/0] portswitch
[Module_A-GigabitEthernet1/0/0] Eth-Trunk 1
[Module_A-GigabitEthernet1/0/0] quit
[Module_A] interface GigabitEthernet 1/0/1
[Module_A-GigabitEthernet1/0/1] portswitch
[Module_A-GigabitEthernet1/0/1] Eth-Trunk 1
[Module_A-GigabitEthernet1/0/1] quit
<sysname> system-view
[sysname] sysname Module_B
# Create Layer-2 Eth-Trunk 1 on NGFW Module_B and permit packets from the
upstream and downstream VLANs.
[Module_B] interface Eth-Trunk 1
[Module_B-Eth-Trunk1] description To_SwitchB_trunk10
[Module_B-Eth-Trunk1] portswitch
[Module_B-Eth-Trunk1] port link-type trunk
[Module_B-Eth-Trunk1] port trunk permit vlan 200 301 to 302
[Module_B-Eth-Trunk1] quit
# Add the interfaces connecting NGFW Module_B to its connected switch to Eth-
Trunk 1.
[Module_B] interface GigabitEthernet 1/0/0
[Module_B-GigabitEthernet1/0/0] portswitch
[Module_B-GigabitEthernet1/0/0] Eth-Trunk 1
[Module_B-GigabitEthernet1/0/0] quit
[Module_B] interface GigabitEthernet 1/0/1
[Module_B-GigabitEthernet1/0/1] portswitch
[Module_B-GigabitEthernet1/0/1] Eth-Trunk 1
[Module_B-GigabitEthernet1/0/1] quit
# Specify the heartbeat interface and enable hot standby on NGFW Module_A.
[Module_A] hrp interface Eth-Trunk 0
[Module_A] hrp enable
[Module_A] hrp loadbalance-device //This command is required only in versions earlier than
V100R001C30SPC300.
# Specify the heartbeat interface and enable hot standby on NGFW Module_B.
[Module_B] hrp interface Eth-Trunk 0
[Module_B] hrp enable
[Module_B] hrp loadbalance-device //This command is required only in versions earlier than
V100R001C30SPC300.
After hot standby is configured, the configurations and sessions on the active device are
synchronized to the standby device; therefore, you only need to perform the following
configurations on the active NGFW Module_A.
Before configuring intrusion prevention, ensure that the required license is loaded and the
intrusion prevention signature database is the latest version.
When configuring intrusion prevention, use the default intrusion prevention profile default.
In this example, the configured security policy allows intranet users to access the Internet.
To enable the Internet to access the intranet, configure a rule whose the destination
address is an intranet address.
# Configure the CSS on SwitchA. In the example, the CSS connection mode is
CSS card connection mode, the CSS ID is 1, and the CSS priority is 100.
<Huawei> system-view
[Huawei] sysname SwitchA
[SwitchA] set css mode css-card //Set the CSS connection mode. The default mode is CSS
card connection mode.
[SwitchA] set css id 1 //Set the CSS ID. The default value is 1.
[SwitchA] set css priority 100 //Set the CSS priority. The default value is 1.
# Configure the CSS on SwitchB. In the example, the CSS connection mode is
CSS card connection mode, the CSS ID is 2, and the CSS priority is 10.
<Huawei> system-view
[Huawei] sysname SwitchB
[SwitchB] set css mode css-card
[SwitchB] set css id 2
[SwitchB] set css priority 10
3. Enable the CSS function.
# To use SwitchA as the active switch, enable CSS on SwitchA and then restart
SwitchA.
[SwitchA] css enable
Warning: The CSS configuration will take effect only after the system is rebooted. T
he next CSS mode is CSS card. Reboot now? [Y/N]:y
Chassis Id CSS Enable CSS Status CSS Mode Priority Master Force
------------------------------------------------------------------------------
1 On Master CSS card 100 Off
2 On Standby CSS card 10 Off
If the CSS IDs, CSS priorities, CSS enabling status, and CSS status of the two
member switches are displayed, as shown in the preceding information, the
CSS has been established.
You are advised to configure MAD to minimize the impact of a CSS split on
services. Detailed configurations will not be described here.
5. Rename the cluster system to CSS.
<SwitchA> system-view
[SwitchA] sysname CSS
[CSS]
Step 5 Configure switch interfaces and VLANs. This example describes how to configure
interoperation between the switch and NGFW modules.
1. Create VLANs.
[CSS] vlan batch 200 301 to 302
2. Configure upstream and downstream interfaces, isolate the upstream and
downstream interfaces from Eth-Trunk10 unidirectionally. Adding the
interfaces to Eth-Trunk interfaces is not mentioned here.
When traffic is forwarded from the switches to the NGFW Modules, the cross-board Eth-
Trunk distributes the traffic. To ensure that forward and return packets are forwarded by
the same NGFW Module, set the enhanced load balancing mode. In the example, the
source and destination IP addresses are used for illustration.
[CSS] load-balance-profile module
[CSS-load-balance-profile-module] ipv4 field sip dip
[CSS-load-balance-profile-module] quit
[CSS] interface Eth-Trunk 10
[CSS-Eth-Trunk10] load-balance enhanced profile module
[CSS-Eth-Trunk10] quit
# Create ACLs.
[CSS] acl 3001 //Match traffic exchanged between intranet users of different VLANs.
[CSS-acl-adv-3001] rule permit ip source 10.1.0.0 0.0.0.255 destination 10.2.0.0 0.0.0.255
[CSS-acl-adv-3001] rule permit ip source 10.2.0.0 0.0.0.255 destination 10.1.0.0 0.0.0.255
[CSS-acl-adv-3001] quit
[CSS] acl 3002 //Match traffic sent by intranet users to access the Internet.
[CSS-acl-adv-3002] rule permit ip source 10.1.0.0 0.0.0.255
[CSS-acl-adv-3002] rule permit ip source 10.2.0.0 0.0.0.255
[CSS-acl-adv-3002] quit
[CSS] acl 3004 //Match traffic from the Internet to the intranet.
[CSS-acl-adv-3004] rule permit ip destination 10.1.0.0 0.0.0.255
[CSS-acl-adv-3004] rule permit ip destination 10.2.0.0 0.0.0.255
[CSS-acl-adv-3004] quit
# Configure the switch not to direct the traffic exchanged between intranet
users but to direct traffic sent by the intranet to access the Internet to the
NGFW Modules.
[CSS] traffic classifier classifier1 precedence 5
[CSS-classifier-classifier1] if-match acl 3001
[CSS-classifier-classifier1] quit
[CSS] traffic behavior behavior1 //Permit traffic exchanged between intranet users.
[CSS-behavior-behavior1] permit
[CSS-behavior-behavior1] quit
[CSS] traffic classifier classifier2 precedence 10
[CSS-classifier-classifier2] if-match acl 3002
[CSS-classifier-classifier2] quit
[CSS] traffic behavior behavior2 //Redirect the traffic from the intranet to the Internet to the
interface connecting the switch to the NGFW Module.
[CSS-behavior-behavior2] redirect interface Eth-Trunk 10
[CSS-behavior-behavior2] quit
[CSS] traffic policy policy1 //Configure a traffic policy.
[CSS-trafficpolicy-policy1] classifier classifier1 behavior behavior1
[CSS-trafficpolicy-policy1] classifier classifier2 behavior behavior2
[CSS-trafficpolicy-policy1] quit
[CSS] interface Eth-Trunk 2
[CSS-Eth-Trunk2] traffic-policy policy1 inbound
[CSS-Eth-Trunk2] quit
[CSS] interface Eth-Trunk 3
[CSS-Eth-Trunk3] traffic-policy policy1 inbound
[CSS-Eth-Trunk3] quit
# Configure the switch to redirect the traffic from the Internet to the intranet
to the NGFW Module.
[CSS] traffic classifier classifier4
[CSS-classifier-classifier4] if-match acl 3004
[CSS-classifier-classifier4] quit
[CSS] traffic behavior behavior4 //Redirect the traffic from the Internet to the intranet to the
interface connecting the switch to the NGFW Module.
[CSS-behavior-behavior4] redirect interface Eth-Trunk 10
[CSS-behavior-behavior4] quit
[CSS] traffic policy policy2 //Configure a traffic policy.
[CSS-trafficpolicy-policy2] classifier classifier4 behavior behavior4
[CSS-trafficpolicy-policy2] quit
[CSS] interface Eth-Trunk 5
[CSS-Eth-Trunk5] traffic-policy policy2 inbound
[CSS-Eth-Trunk5] quit
After receiving packets, the switch looks up the routing table to complete Layer-3
forwarding although redirection policies are configured. However, the outgoing interfaces
of packets are still determined by the redirection policies.
In the example, when receiving a packet from the intranet to the Internet, the switch first
looks up the routing table, changes the VLAN tag from 301 or 302 to 200 based on the
default route, and then forwards the packet to the NGFW Module. After receiving a packet
from the Internet to the intranet, the switch changes the VLAN tag from 200 to 301 or 302
based on the direct route and then forwards the packet to the NGFW Module.
If no routing entry is matched, the switch forwards the packet based on the redirection
policy without changing the VLAN tag.
----End
Verification
1. Run the display hrp state command on NGFW Module_A to check the
current HRP status. If the following output is displayed, an HRP relationship is
successfully established.
HRP_A[Module_A] display hrp state
The firewall's config state is: ACTIVE
2. Check whether the access from the intranet to the Internet succeeds and
check the session table of each NGFW Module.
HRP_A[Module_A] display firewall session table
Current Total Sessions : 1
http VPN: public --> public 10.1.0.10:22048 --> 3.3.3.3:80
HRP_S[Module_B] display firewall session table
Current Total Sessions : 1
http VPN: public --> public Remote 10.1.0.10:22048 --> 3.3.3.3:80
Configuration Scripts
Configuration scripts of the NGFW Modules:
am isolate Eth-Trunk 10
traffic-policy policy1 inbound
#
interface Eth-Trunk5
port default vlan 200
am isolate Eth-Trunk 10
traffic-policy policy2 inbound
#
interface Eth-Trunk10
description To_Module
port link-type trunk
undo port trunk allow-pass vlan 1
port trunk allow-pass vlan 200 301 to 302
mac-address learning disable
stp disable
load-balance enhanced profile module
undo local-preference enable
#
interface XGigabitEthernet1/1/0/0
eth-trunk 10
#
interface XGigabitEthernet1/1/0/1
eth-trunk 10
#
interface xgigabitethernet1/1/0/2
eth-trunk 2
#
interface xgigabitethernet1/1/0/3
eth-trunk 3
#
interface xgigabitethernet1/1/0/5
eth-trunk 5
#
interface XGigabitEthernet2/1/0/0
eth-trunk 10
#
interface XGigabitEthernet2/1/0/1
eth-trunk 10
#
interface xgigabitethernet2/1/0/2
eth-trunk 2
#
interface xgigabitethernet2/1/0/3
eth-trunk 3
#
interface xgigabitethernet2/1/0/5
eth-trunk 5
#
ip route-static 0.0.0.0 0.0.0.0 10.3.0.5
#
return
Service Requirements
As shown in Figure 2-36, two switches are deployed in a CSS and two NGFW
Modules are installed in slot 1 on the two switches. The two NGFW Modules are
required to implement hot standby and perform security detection on traffic
passing through the switches. Two NGFW Modules work in active/standby mode.
This example uses NGFW modules running V100R001C30 and switches running
V200R008C00. For the configuration examples of NGFW Modules running other
versions, see Deployment Guide. You can search for "Deployment Guide" in the
search bar.
Figure 2-36 Networking for Layer-3 dual-NGFW Module deployment and switch
CSS
Internet/WAN
Eth-Trunk0 Eth-Trunk0
10.10.0.1/24 Eth-Trunk 4 Heartbeat link 10.10.0.2/24
Eth-Trunk1.1(untrust) Eth-Trunk1.1(untrust)
CSS
Eth-Trunk1.2(trust) Eth-Trunk1.2(trust)
Eth-Trunk1.3(dmz) SwitchB Eth-Trunk1.3(dmz)
SwitchA
NGFW Module_A Eth-Trunk 5 NGFW Module_B
Eth-Trunk 6
Eth-Trunk 2 Eth-Trunk 3
192.168.1.0/24 192.168.2.0/24
trust dmz
The NGFW Module has two fixed internal Ethernet interfaces: GE1/0/0 to GE1/0/1. The
numbering of internal Ethernet interfaces on the switch is determined by the slot in which the
NGFW Module is installed. For example, when the NGFW Module is installed in slot 1 on the
switch, the internal Ethernet interfaces used by the switch are XGE1/1/0/0 to XGE1/1/0/1.
Eth-Trunk2 and Eth-Trunk3 are interfaces of the switches in the CSS.
Data Planning
Item Data Description
Deployment Solution
1. Two NGFW Modules form hot standby networking. The switch diverts the
passing traffic to the NGFW Module through a static route. After performing
security check on the traffic, the NGFW Module rejects the traffic to the
switch through a static route.
Configure VRF on the switches to virtualize the switches as virtual switch
Public connecting to the public network (no VPN instance needs to be
configured) and virtual switches trust and dmz respectively connecting to the
Trust zone and DMZ. Figure 2-37 shows the networking. The virtual switches
are separated. Therefore, traffic will be forwarded to the NGFW Modules.
Public
trust dmz
2. Figure 2-37 can be abstracted as Figure 2-38. The NGFW Modules run static
routes with upstream and downstream devices. Therefore, you need to
configure VRRP groups on the NGFW Modules, so that the switches
communicate with the virtual IP addresses of VRRP groups on the NGFW
Modules.
Configure a default route to the Internet on the NGFW Module, and set the
next-hop address to the IP address of VLANIF201. Configure a specific route
to the intranet on the NGFW Module, and set the next-hop address to the IP
address of VLANIF202. Figure 2-38 shows the networking. On the virtual
switch Public, configure static routes to the Trust zone and DMZ and set the
next-hop address to the IP address of VRRP group 1. On the virtual switch
trust, configure a default route to the Internet and set the next-hop address
to the IP address of VRRP group 2. On the virtual switch dmz, configure a
default route to the Internet and set the next-hop address to the IP address of
VRRP group 3.
Figure 2-38 Configuring VRRP groups on the NGFW Modules and static
routes on the switches
Public Public
trust dmz
Static route
trust zone traffic
Figure 2-38 lists only the switch interfaces involved in the connection with the NGFW
Modules.
3. Bundle GE0/0/1 and GE0/0/2 interfaces on the panel of each NGFW Module
into an Eth-Trunk0 interface, which functions as the heartbeat interface and
backup channel and enable hot standby.
4. Configure security functions, such as security policies, nat policies, and IPS on
NGFW Module_A. NGFW Module_A will automatically synchronize its
configurations to NGFW Module_B.
Procedure
Step 1 Complete interface and basic network configurations on NGFW Modules.
# Configure device name on NGFW Module_A.
<sysname> system-view
[sysname] sysname Module_A
# On NGFW Module_A, configure a downstream static route to the DMZ, with the
destination address being the address of the DMZ and next-hop address being the
address of VLANIF203 on the connected switch.
[Module_A] ip route-static 192.168.2.0 255.255.255.0 10.3.3.4
# On NGFW Module_B, configure a downstream static route to the DMZ, with the
destination address being the address of the DMZ and next-hop address being the
address of VLANIF203 on the connected switch.
[Module_B] ip route-static 192.168.2.0 255.255.255.0 10.3.3.4
# Specify the heartbeat interface and enable hot standby on NGFW Module_A.
[Module_A] hrp interface Eth-Trunk 0
[Module_A] hrp enable
# Specify the heartbeat interface and enable hot standby on NGFW Module_B.
[Module_B] hrp interface Eth-Trunk 0
[Module_B] hrp enable
[Module_B] hrp standby-device //This command is required only in versions earlier than
V100R001C30SPC300.
After hot standby is configured, the configurations and sessions on the active device are
synchronized to the standby device; therefore, you only need to perform the following
configurations on the active NGFW Module_A.
Before configuring intrusion prevention, ensure that the required license is loaded and the
intrusion prevention signature database is the latest version.
When configuring intrusion prevention, use the default intrusion prevention profile default.
# On NGFW Module_A, configure a security policy to allow users in the Trust zone
(network segment 192.168.1.0/24) to access the Internet.
HRP_A[Module_A] security-policy
HRP_A[Module_A-policy-security] rule name policy_sec1
HRP_A[Module_A-policy-security-rule-policy_sec1] source-zone trust
HRP_A[Module_A-policy-security-rule-policy_sec1] destination-zone untrust
HRP_A[Module_A-policy-security-rule-policy-sec1] source-address 192.168.1.0 24
HRP_A[Module_A-policy-security-rule-policy_sec1] action permit
HRP_A[Module_A-policy-security-rule-policy_sec1] quit
# Configure a source NAT policy for Internet access from the specified private
subnet.
HRP_A[Module_A] nat-policy
HRP_A[Module_A-policy-nat] rule name policy_nat1
HRP_A[Module_A-policy-nat-rule-policy_nat1] source-zone trust
HRP_A[Module_A-policy-nat-rule-policy_nat1] destination-zone untrust
HRP_A[Module_A-policy-nat-rule-policy_nat1] source-address 192.168.1.0 24
HRP_A[Module_A-policy-nat-rule-policy_nat1] action nat address-group addressgroup1
HRP_A[Module_A-policy-nat-rule-policy_nat1] quit
HRP_A[Module_A-policy-nat] quit
# Configure the NAT server function to translate the private address of a specific
server in the DMZ into a public address for user access. In this example, private
address 192.168.2.8:80 of the web server in the DMZ is translated into public
address 1.1.1.3:8000.
HRP_A[Module_A] nat server policy_web protocol tcp global 1.1.1.3 8000 inside 192.168.2.8 80
# Configure the CSS on SwitchB. In the example, the CSS connection mode is
CSS card connection mode, the CSS ID is 2, and the CSS priority is 10.
<Huawei> system-view
[Huawei] sysname SwitchB
[SwitchB] set css mode css-card
[SwitchB] set css id 2
[SwitchB] set css priority 10
3. Enable the CSS function.
# To use SwitchA as the active switch, enable CSS on SwitchA and then restart
SwitchA.
[SwitchA] css enable
Warning: The CSS configuration will take effect only after the system is rebooted. T
he next CSS mode is CSS card. Reboot now? [Y/N]:y
Chassis Id CSS Enable CSS Status CSS Mode Priority Master Force
------------------------------------------------------------------------------
1 On Master CSS card 100 Off
2 On Standby CSS card 10 Off
If the CSS IDs, CSS priorities, CSS enabling status, and CSS status of the two
member switches are displayed, as shown in the preceding information, the
CSS has been established.
You are advised to configure MAD to minimize the impact of a CSS split on
services. Detailed configurations will not be described here.
5. Rename the cluster system to CSS.
<SwitchA> system-view
[SwitchA] sysname CSS
[CSS]
Step 6 Configure interfaces and VLANs for core switches. This example describes how to
configure interoperation between the switch and NGFW modules.
[CSS] vlan batch 201 to 205 //Create VLANs.
[CSS] interface eth-trunk 5
[CSS-Eth-Trunk5] description To_NGFW_Module_A
[CSS-Eth-Trunk5] trunkport xgigabitethernet 1/1/0/0 to 1/1/0/1 //Create Eth-Trunk5 on the CSS and
add internal Ethernet interfaces to Eth-Trunk5.
[CSS-Eth-Trunk5] port link-type trunk
[CSS-Eth-Trunk5] undo port trunk allow-pass vlan 1
[CSS-Eth-Trunk5] port trunk allow-pass vlan 201 to 205 //Configure Eth-Trunk5 to permit traffic from
VLANs 201, 202, 203, 204, and 205.
[CSS-Eth-Trunk5] quit
[CSS] interface eth-trunk 6
[CSS-Eth-Trunk6] description To_NGFW_Module_B
[CSS-Eth-Trunk6] trunkport xgigabitethernet 2/1/0/0 to 2/1/0/1 //Create Eth-Trunk6 on the CSS and
add internal Ethernet interfaces to Eth-Trunk6.
[CSS-Eth-Trunk6] port link-type trunk
[CSS-Eth-Trunk6] undo port trunk allow-pass vlan 1
[CSS-Eth-Trunk6] port trunk allow-pass vlan 201 to 205 //Configure Eth-Trunk6 to permit traffic from
VLANs 201, 202, 203, 204, and 205.
[CSS-Eth-Trunk6] quit
[CSS] interface eth-trunk 2 //Configure the switch interface Eth-Trunk2 that connects to the
Trust zone, add the interfaces to Eth-Trunk2 is not mentioned here.
[CSS-Eth-Trunk2] description To_TRUST
[CSS-Eth-Trunk2] port link-type trunk
[CSS-Eth-Trunk2] undo port trunk allow-pass vlan 1
[CSS-Eth-Trunk2] port trunk allow-pass vlan 204 //Enable Eth-Trunk2 to permit traffic from VLAN204.
[CSS-Eth-Trunk2] quit
[CSS] interface eth-trunk 3 //Configure the switch interface Eth-Trunk3 that connects to the
DMZ, add the interfaces to Eth-Trunk3 is not mentioned here.
[CSS-Eth-Trunk3] description To_DMZ
[CSS-Eth-Trunk3] port link-type trunk
[CSS-Eth-Trunk3] undo port trunk allow-pass vlan 1
[CSS-Eth-Trunk3] port trunk allow-pass vlan 205 //Enable Eth-Trunk3 to permit traffic from VLAN205.
[CSS-Eth-Trunk3] quit
[CSS] ip vpn-instance trust //Create VPN instance trust.
[CSS-vpn-instance-trust] ipv4-family
[CSS-vpn-instance-trust-af-ipv4] route-distinguisher 100:1
[CSS-vpn-instance-trust-af-ipv4] vpn-target 111:1 both
[CSS-vpn-instance-trust-af-ipv4] quit
[CSS-vpn-instance-trust] quit
[CSS] ip vpn-instance dmz //Create VPN instance dmz.
[CSS-vpn-instance-dmz] ipv4-family
[CSS-vpn-instance-dmz-af-ipv4] route-distinguisher 200:1
[CSS-vpn-instance-dmz-af-ipv4] vpn-target 211:1 both
[CSS-vpn-instance-dmz-af-ipv4] quit
[CSS-vpn-instance-dmz] quit
[CSS] interface vlanif 201
[CSS-Vlanif201] ip address 10.3.1.4 24
[CSS-Vlanif201] quit //Configure an IP address for VLANIF201.
In the example, NAT is configured on the NGFW Modules. Therefore, configure static routes
from the Public virtual switch to the Trust zone and DMZ, and the destination IP addresses in
the routes should be post-NAT public IP addresses. If NAT is not configured on the NGFW
Modules, the destination IP addresses in the routes must be private IP addresses respectively in
the Trust zone and DMZ when you configure static routes from the Public virtual switch to the
two zones.
In the example, communication packets between the Trust zone and DMZ are not processed by
the NGFW Modules. If the enterprise requires that the NGFW Modules process the
communication packets between the Trust zone and DMZ, set the next hop to the IP address of
the downlink VRRP group on the NGFW Modules when you configure the route for the
communications between the Trust zone and DMZ.
----End
Verification
1. Run the display hrp state command on NGFW Module_A to check the
current HRP status. If the following output is displayed, an HRP relationship is
successfully established.
HRP_A[Module_A] display hrp state
The firewall's config state is: ACTIVE
(GigabitEthernet1/0/1) : up
Eth-Trunk1.2 vrid 2 : active
(GigabitEthernet1/0/0) : up
(GigabitEthernet1/0/1) : up
Eth-Trunk1.1 vrid 1 : active
(GigabitEthernet1/0/0) : up
(GigabitEthernet1/0/1) : up
2. Check whether the access from the intranet to the Internet succeeds and
check the session table of each NGFW Module.
HRP_A[Module_A] display firewall session table
Current Total Sessions : 1
http VPN: public --> public 192.168.1.8:22048[1.1.1.2:2106] --> 3.3.3.3:80
HRP_S[Module_B] display firewall session table
Current Total Sessions : 1
http VPN: public --> public Remote 192.168.1.8:22048[1.1.1.2:2106] --> 3.3.3.3:80
4. Configure a PC in the Trust zone to constantly ping the public address and run
the shutdown command on Eth-trunk1 of NGFW Module_A. Then check the
status switchover of the NGFW Module and discarded ping packets. If the
status switchover is normal, NGFW Module_B becomes the active and carries
services. The command prompt of NGFW Module_B is changed from HRP_S to
HRP_A, and the command prompt of NGFW Module_A is changed from
HRP_A to HRP_S. No or several ping packets (1 to 3 packets, depending on
actual network environments) are discarded.
Run the undo shutdown command on Eth-trunk1 of NGFW Module_A and
check the status switchover of the NGFW Module and discarded ping packets.
If the status switchover is normal, NGFW Module_A becomes the active and
starts to carry service after the preemption delay (60s by default) expires. The
command prompt of NGFW Module_A is changed from HRP_S to HRP_A, and
the command prompt of NGFW Module_B is changed from HRP_A to HRP_S.
No or several ping packets (1 to 3 packets, depending on actual network
environments) are discarded.
Configuration Scripts
Configuration scripts of the NGFW Modules:
Service Requirements
As shown in Figure 2-39, two switches are deployed in a CSS and two NGFW
Modules are installed in slot 1 on the two switches. The two NGFW Modules are
required to implement hot standby and perform security detection on traffic
passing through the switches. Two NGFW Modules work in active/standby mode.
This example uses NGFW modules running V100R001C30 and switches running
V200R008C00. For the configuration examples of NGFW Modules running other
versions, see Deployment Guide. You can search for "Deployment Guide" in the
search bar.
Figure 2-39 Networking for Layer-3 dual-NGFW Module deployment and switch
CSS
Internet/WAN
Eth-Trunk0 Eth-Trunk0
10.10.0.1/24 Eth-Trunk 4 Heartbeat link 10.10.0.2/24
Eth-Trunk1.1(untrust) Eth-Trunk1.1(untrust)
CSS
Eth-Trunk1.2(trust) Eth-Trunk1.2(trust)
Eth-Trunk1.3(dmz) SwitchB Eth-Trunk1.3(dmz)
SwitchA
NGFW Module_A Eth-Trunk 5 NGFW Module_B
Eth-Trunk 6
Eth-Trunk 2 Eth-Trunk 3
192.168.1.0/24 192.168.2.0/24
trust dmz
The NGFW Module has two fixed internal Ethernet interfaces: GE1/0/0 to GE1/0/1. The
numbering of internal Ethernet interfaces on the switch is determined by the slot in which the
NGFW Module is installed. For example, when the NGFW Module is installed in slot 1 on the
switch, the internal Ethernet interfaces used by the switch are XGE1/1/0/0 to XGE1/1/0/1.
Eth-Trunk2 and Eth-Trunk3 are interfaces of the switches in the CSS.
Data Planning
Item Data Description
Deployment Solution
1. Figure 2-39 can be abstracted as Figure 2-40. You can understand the
mapping between the two figures based on interface numbers and actual
traffic directions.
As shown in Figure 2-40, a default route (next hop: VLANIF201) to the public
network, a specific route (next hop: VLANIF202) to the Trust zone, and a
specific route (next hop: VLANIF203) to the DMZ need to be configured on
the NGFW modules. PBR needs to be configured on the switches to direct
traffic to the firewalls.
Figure 2-40 Configuring VRRP on the NGFW modules and PBR on the
switches
Static route
trust zone traffic
Figure 2-40 lists only the switch interfaces involved in the connection with the NGFW
Modules.
2. Specify Eth-trunk0 as the heartbeat interface and enable hot standby on each
NGFW Module.
3. Configure security functions, such as security policies, nat policies, and IPS on
NGFW Module_A. NGFW Module_A will automatically synchronize its
configurations to NGFW Module_B.
Procedure
Step 1 Complete interface and basic network configurations on NGFW Modules.
# On NGFW Module_A, configure a downstream static route to the DMZ, with the
destination address being the address of the DMZ and next-hop address being the
address of VLANIF203 on the connected switch.
[Module_A] ip route-static 192.168.2.0 255.255.255.0 10.3.3.4
# On NGFW Module_B, configure a downstream static route to the DMZ, with the
destination address being the address of the DMZ and next-hop address being the
address of VLANIF203 on the connected switch.
[Module_B] ip route-static 192.168.2.0 255.255.255.0 10.3.3.4
# Specify the heartbeat interface and enable hot standby on NGFW Module_A.
[Module_A] hrp interface Eth-Trunk 0
[Module_A] hrp enable
# Specify the heartbeat interface and enable hot standby on NGFW Module_B.
[Module_B] hrp interface Eth-Trunk 0
[Module_B] hrp enable
[Module_B] hrp standby-device //This command is required only in versions earlier than
V100R001C30SPC300.
After hot standby is configured, the configurations and sessions on the active device are
synchronized to the standby device; therefore, you only need to perform the following
configurations on the active NGFW Module_A.
Before configuring intrusion prevention, ensure that the required license is loaded and the
intrusion prevention signature database is the latest version.
When configuring intrusion prevention, use the default intrusion prevention profile default.
# Configure a source NAT policy for Internet access from the specified private
subnet.
HRP_A[Module_A] nat-policy
HRP_A[Module_A-policy-nat] rule name policy_nat1
HRP_A[Module_A-policy-nat-rule-policy_nat1] source-zone trust
HRP_A[Module_A-policy-nat-rule-policy_nat1] destination-zone untrust
HRP_A[Module_A-policy-nat-rule-policy_nat1] source-address 192.168.1.0 24
HRP_A[Module_A-policy-nat-rule-policy_nat1] action nat address-group addressgroup1
HRP_A[Module_A-policy-nat-rule-policy_nat1] quit
HRP_A[Module_A-policy-nat] quit
# Configure the NAT server function to translate the private address of a specific
server in the DMZ into a public address for user access. In this example, private
address 192.168.2.8:80 of the web server in the DMZ is translated into public
address 1.1.1.3:8000.
HRP_A[Module_A] nat server policy_web protocol tcp global 1.1.1.3 8000 inside 192.168.2.8 80
2. Set the CSS connection mode (such as the CSS card connection mode), CSS
ID, and CSS priority.
# Configure the CSS on SwitchA. In the example, the CSS connection mode is
CSS card connection mode, the CSS ID is 1, and the CSS priority is 100.
<Huawei> system-view
[Huawei] sysname SwitchA
[SwitchA] set css mode css-card //Set the CSS connection mode. The default mode is CSS
card connection mode.
[SwitchA] set css id 1 //Set the CSS ID. The default value is 1.
[SwitchA] set css priority 100 //Set the CSS priority. The default value is 1.
# Configure the CSS on SwitchB. In the example, the CSS connection mode is
CSS card connection mode, the CSS ID is 2, and the CSS priority is 10.
<Huawei> system-view
[Huawei] sysname SwitchB
[SwitchB] set css mode css-card
[SwitchB] set css id 2
[SwitchB] set css priority 10
3. Enable the CSS function.
# To use SwitchA as the active switch, enable CSS on SwitchA and then restart
SwitchA.
[SwitchA] css enable
Warning: The CSS configuration will take effect only after the system is rebooted. T
he next CSS mode is CSS card. Reboot now? [Y/N]:y
Chassis Id CSS Enable CSS Status CSS Mode Priority Master Force
------------------------------------------------------------------------------
1 On Master CSS card 100 Off
2 On Standby CSS card 10 Off
If the CSS IDs, CSS priorities, CSS enabling status, and CSS status of the two
member switches are displayed, as shown in the preceding information, the
CSS has been established.
You are advised to configure MAD to minimize the impact of a CSS split on
services. Detailed configurations will not be described here.
5. Rename the cluster system to CSS.
<SwitchA> system-view
[SwitchA] sysname CSS
[CSS]
Step 6 Configure interfaces and VLANs for switches. This example describes how to
configure interoperation between the switch and NGFW modules.
[CSS] vlan batch 201 to 203 //Create VLANs.
[CSS] interface eth-trunk 5
[CSS-Eth-Trunk5] description To_NGFW_Module_A
[CSS-Eth-Trunk5] trunkport xgigabitethernet 1/1/0/0 to 1/1/0/1 //Create Eth-Trunk5 on the CSS and add
internal Ethernet interfaces to Eth-Trunk5.
[CSS-Eth-Trunk5] port link-type trunk
[CSS-Eth-Trunk5] undo port trunk allow-pass vlan 1
[CSS-Eth-Trunk5] port trunk allow-pass vlan 201 to 203 //Configure Eth-Trunk5 to permit traffic from
VLANs 201, 202, and 203.
[CSS-Eth-Trunk5] quit
[CSS] interface eth-trunk 6
[CSS-Eth-Trunk6] description To_NGFW_Module_B
[CSS-Eth-Trunk6] trunkport xgigabitethernet 2/1/0/0 to 2/1/0/1 //Create Eth-Trunk6 on the CSS and add
internal Ethernet interfaces to Eth-Trunk6.
[CSS-Eth-Trunk6] port link-type trunk
[CSS-Eth-Trunk6] undo port trunk allow-pass vlan 1
[CSS-Eth-Trunk6] port trunk allow-pass vlan 201 to 203 //Configure Eth-Trunk6 to permit traffic from
VLANs 201, 202, and 203.
[CSS-Eth-Trunk6] quit
[CSS] interface vlanif 201
[CSS-Vlanif201] ip address 10.3.1.4 24
[CSS-Vlanif201] quit //Configure an IP address for VLANIF201.
[CSS] interface vlanif 202
[CSS-Vlanif202] ip address 10.3.2.4 24
[CSS-Vlanif202] quit //Configure an IP address for VLANIF202.
[CSS] interface vlanif 203
[CSS-Vlanif203] ip address 10.3.3.4 24
[CSS-Vlanif203] quit //Configure an IP address for VLANIF203.
Step 7 Configure traffic diversion on the switch. This example describes how to configure
interoperation between the switch and NGFW modules.
[CSS] acl 3001 //Create ACL3001.
[CSS-acl-adv-3001] rule 5 permit ip source 192.168.1.0 0.0.0.255 destination 192.168.2.0 0.0.0.255 //
Configure a rule for ACL3001: source network segment 192.168.1.0 and destination network segment
192.168.2.0.
[CSS-acl-adv-3001] rule 10 permit ip source 192.168.2.0 0.0.0.255 destination 192.168.1.0 0.0.0.255 //
Configure a rule for ACL3001: source network segment 192.168.2.0 and destination network segment
192.168.1.0.
[CSS-acl-adv-3001] quit
[CSS] traffic classifier c1 precedence 5 //Create traffic classifier c1.
[CSS-classifier-c1] if-match acl 3001 //Match packets exchanged between the Trust zone and DMZ with
the ACL3001 rule.
[CSS-classifier-c1] quit
[CSS] traffic behavior b1 //Create traffic behavior b1.
[CSS-behavior-b1] permit //Permit the matching packets.
[CSS-behavior-b1] quit
[CSS] acl 3002 //Create ACL3002.
[CSS-acl-adv-3002] rule 5 permit ip source 192.168.1.0 0.0.0.255 //Configure a rule for ACL3002: source
network segment 192.168.1.0.
[CSS-acl-adv-3002] quit
[CSS] traffic classifier c2 precedence 10 //Create traffic classifier c2.
[CSS-classifier-c2] if-match acl 3002 //Match the packets from network segment 192.168.1.0, namely,
packets from the Trust zone to the Internet, with ACL3002.
[CSS-classifier-c2] quit
[CSS] traffic behavior b2 //Create traffic behavior b2.
[CSS-behavior-b2] redirect ip-nexthop 10.3.2.1 //Redirect the matching packets to address 10.3.2.1,
namely, the connected NGFW Module.
[CSS-behavior-b2] quit
[CSS] traffic policy p1 //Create traffic policy p1.
[CSS-trafficpolicy-p1] classifier c1 behavior b1 //Bind traffic classifier c1 and traffic behavior b1 with
traffic policy p1. All packets exchanged between the Trust zone and DMZ are directly forwarded by the
switch, without being forwarded to the NGFW Module.
[CSS-trafficpolicy-p1] classifier c2 behavior b2 //Bind traffic classifier c2 and traffic behavior b2 with
traffic policy p1. All packets from the Trust zone to the Internet are redirected to the NGFW Module.
[CSS-trafficpolicy-p1] quit
[CSS] interface eth-trunk 2 //Access the interface connecting the switch to the Trust zone.
[CSS-Eth-Trunk2] traffic-policy p1 inbound //Apply traffic policy P1 in the inbound direction of the
interface connecting the switch to the Trust zone.
[CSS-Eth-Trunk2] quit
[CSS] acl 3003 //Create ACL3003.
[CSS-acl-adv-3003] rule 5 permit ip source 192.168.2.0 0.0.0.255 //Configure a rule for ACL3003: source
network segment 192.168.2.0.
[CSS-acl-adv-3003] quit
[CSS] traffic classifier c3 precedence 15 //Create traffic classifier c3.
[CSS-classifier-c3] if-match acl 3003 //Match all packets from network segment 192.168.2.0, namely, all
packets from the DMZ to the Internet, with the ACL3003 rule.
[CSS-classifier-c3] quit
[CSS] traffic behavior b3 //Create traffic behavior b3.
[CSS-behavior-b3] redirect ip-nexthop 10.3.3.1 //Redirect the matching packets to address 10.3.3.1,
namely the NGFW Module.
[CSS-behavior-b3] quit
[CSS] traffic policy p3 //Create traffic policy p3.
[CSS-trafficpolicy-p3] classifier c1 behavior b1 //Bind traffic classifier c1 and traffic behavior b1 with
traffic policy p3. All packets exchanged between the Trust zone and DMZ are directly forwarded by the
switch, without being forwarded to the NGFW Module.
[CSS-trafficpolicy-p3] classifier c3 behavior b3 //Bind traffic classifier c3 and traffic behavior b3 with
traffic policy p3. All traffic from the DMZ to the Internet are directed to the NGFW Module.
[CSS-trafficpolicy-p3] quit
[CSS] interface eth-trunk 3 //Access the view of the interface connecting the switch to the Trust zone.
[CSS-Eth-Trunk3] traffic-policy p3 inbound //Apply traffic policy p3 in the inbound direction of the
interface connecting the switch to the DMZ.
[CSS-Eth-Trunk3] quit
[CSS] ip route-static 1.1.1.1 32 10.3.1.1 //Configure a static route to an address in the NAT address pool
of the NGFW and set the next-hop address of the route to the IP address of the upstream VRRP group on
the NGFW Module.
[CSS] ip route-static 1.1.1.2 32 10.3.1.1 //Configure a static route to an address in the NAT address pool
of the NGFW and set the next-hop address of the route to the IP address of the upstream VRRP group on
the NGFW Module.
[CSS] ip route-static 1.1.1.3 32 10.3.1.1 //Configure a static route to the global address of the NAT server
configured on the NGFW Module and set the next-hop address of the route to the IP address of the
upstream VRRP group on the NGFW Module.
In this example, the source NAT and NAT server functions are configured on the NGFW Module.
For the switch, the destination address of traffic sent from the public network the private
network is a post-NAT address. Therefore, you can configure a static route on the switch to
direct the traffic sent from the public address to the private network to the NGFW Module.
If no source NAT or NAT server function is configured on the NGFW Module, for the switch, the
destination address of traffic sent from the public network to the private network is still a
private network. In this case, you need to configure a traffic policy on the upstream interface of
the switch to direct the traffic to the NGFW Module.
[CSS] acl 3004 //Create ACL3004.
[CSS-acl-adv-3004] rule 5 permit ip destination 192.168.1.0 0.0.0.255 //Configure a rule for ACL3004:
destination network segment 192.168.1.0.
[CSS-acl-adv-3004] rule 10 permit ip destination 192.168.2.0 0.0.0.255 //Configure a rule for ACL3004:
destination network segment 192.168.2.0.
[CSS-acl-adv-3004] quit
[CSS] traffic classifier c4 precedence 20 //Create traffic classifier c4.
[CSS-classifier-c4] if-match acl 3004 //Match the packets whose destination network segments are
192.168.1.0 and 192.168.2.0, namely, all packets from the Internet to the intranet, with the ACL3004 rule.
[CSS-classifier-c4] quit
[CSS] traffic behavior b4 //Create traffic behavior b4.
[CSS-behavior-b4] redirect ip-nexthop 10.3.1.1 //Redirect the matching packets to address 10.3.1.1,
namely, the NGFW Module.
[CSS-behavior-b4] quit
[CSS] traffic policy p4 //Create traffic policy p4.
[CSS-trafficpolicy-p4] classifier c4 behavior b4 precedence 20 //Bind traffic classifier c4 and traffic
behavior b4 with traffic policy p4. All traffic from the Internet to the intranet is directed to the NGFW
Module.
[CSS-trafficpolicy-p4] quit
[CSS] interface eth-trunk 4 //Access the view of the interface connecting the switch to the Internet.
[CSS-Eth-Trunk4] traffic-policy p4 inbound //Apply traffic policy p4 in the inbound direction of the
interface connecting the switch to the Internet.
[CSS-Eth-Trunk4] quit
----End
Verification
1. Run the display hrp state command on NGFW Module_A to check the
current HRP status. If the following output is displayed, an HRP relationship is
successfully established.
HRP_A[Module_A] display hrp state
The firewall's config state is: ACTIVE
2. Check whether the access from the intranet to the Internet succeeds and
check the session table of each NGFW Module.
HRP_A[Module_A] display firewall session table
Current Total Sessions : 1
http VPN: public --> public 192.168.1.8:22048[1.1.1.1:2106] --> 3.3.3.3:80
HRP_S[Module_B] display firewall session table
Current Total Sessions : 1
http VPN: public --> public Remote 192.168.1.8:22048[1.1.1.1:2106] --> 3.3.3.3:80
4. Configure a PC in the Trust zone to constantly ping the public address and run
the shutdown command on Eth-trunk1 of NGFW Module_A. Then check the
status switchover of the NGFW Module and discarded ping packets. If the
status switchover is normal, NGFW Module_B becomes the active and carries
services. The command prompt of NGFW Module_B is changed from HRP_S to
HRP_A, and the command prompt of NGFW Module_A is changed from
HRP_A to HRP_S. No or several ping packets (1 to 3 packets, depending on
actual network environments) are discarded.
Run the undo shutdown command on Eth-trunk1 of NGFW Module_A and
check the status switchover of the NGFW Module and discarded ping packets.
If the status switchover is normal, NGFW Module_A becomes the active and
starts to carry service after the preemption delay (60s by default) expires. The
command prompt of NGFW Module_A is changed from HRP_S to HRP_A, and
the command prompt of NGFW Module_B is changed from HRP_A to HRP_S.
No or several ping packets (1 to 3 packets, depending on actual network
environments) are discarded.
Configuration Scripts
Configuration scripts of the NGFW Modules:
traffic behavior b2
permit
redirect ip-nexthop 10.3.2.1
traffic behavior b3
permit
redirect ip-nexthop 10.3.3.1
traffic behavior b4
permit
redirect ip-nexthop 10.3.1.1
#
traffic policy p1 match-order config
classifier c1 behavior b1
classifier c2 behavior b2
traffic policy p3 match-order config
classifier c1 behavior b1
classifier c3 behavior b3
traffic policy p4 match-order config
classifier c4 behavior b4
#
interface Vlanif201
ip address 10.3.1.4 255.255.255.0
#
interface Vlanif202
ip address 10.3.2.4 255.255.255.0
#
interface Vlanif203
ip address 10.3.3.4 255.255.255.0
#
interface Eth-Trunk2
traffic-policy p1 inbound
#
interface Eth-Trunk3
traffic-policy p3 inbound
#
interface Eth-Trunk4
traffic-policy p4 inbound
#
interface Eth-Trunk5
description To_NGFW_Module_A
port link-type trunk
undo port trunk allow-pass vlan 1
port trunk allow-pass vlan 201 to 203
#
interface Eth-Trunk6
description To_NGFW_Module_B
port link-type trunk
undo port trunk allow-pass vlan 1
port trunk allow-pass vlan 201 to 203
#
interface XGigabitEthernet1/1/0/0
eth-trunk 5
#
interface XGigabitEthernet1/1/0/1
eth-trunk 5
#
interface XGigabitEthernet2/1/0/0
eth-trunk 6
#
interface XGigabitEthernet2/1/0/1
eth-trunk 6
#
ip route-static 1.1.1.1 255.255.255.255 10.3.1.1
ip route-static 1.1.1.2 255.255.255.255 10.3.1.1
ip route-static 1.1.1.3 255.255.255.255 10.3.1.1
#
return
Service Requirements
As shown in Figure 2-41, two switches form a CSS, and two NGFW Modules are
installed in slot 1 of the switches respective and implement hot standby. The
NGFW modules implement security check on traffic sent by intranet users to
access the server area or the Internet.
This example uses NGFW modules running V100R001C30 and switches running
V200R008C00. For the configuration examples of NGFW Modules running other
versions, see Deployment Guide. You can search for "Deployment Guide" in the
search bar.
Figure 2-41 Switch CSS and NGFW Module hot standby networking
Internet/WAN
10.3.0.5/24
The NGFW Module has two fixed internal Ethernet interfaces: GE1/0/0 to GE1/0/1. The
numbering of internal Ethernet interfaces on the switch is determined by the slot in which the
NGFW Module is installed. For example, when the NGFW Module is installed in slot 1 on the
switch, the internal Ethernet interfaces used by the switch are XGE1/1/0/0 to XGE1/1/0/1.
Eth-Trunk2 and Eth-Trunk3 are interfaces of the switches in the CSS.
Deployment Solution
The NGFW Modules work at Layer 3, and the upstream and downstream network
gateways point to the NGFW Modules. The switches work at Layer 2.
1. The interfaces connecting each NGFW Module and switch are bundled into an
Eth-Trunk interface. The Eth-Trunk interface is Eth-Trunk 1 on each NGFW
Module, Eth-Trunk 10 on the SwitchA, and Eth-Trunk 11 on the SwitchB.
2. The Eth-Trunk at the switch side is configured to work in Trunk mode and
allows packets from VLANs 301, 302, and 200 to pass. Configure three Eth-
Trunk subinterfaces at the NGFW Module side to carry out dot1q termination
for packets from VLANs 301, 302, and 200 respectively and perform Layer-3
forwarding.
3. Two NGFW modules form hot standby in active/standby mode. Therefore, a
VRRP group needs to be configured on the upstream and downstream
subinterfaces of each NGFW Module. One NGFW Module is added to an
active VGMP group, and the other NGFW Module is added to a standby
VGMP group.
The virtual gateway IP addresses of the VRRP group are the gateway
addresses of the downstream and upstream networks.
Figure 2-42 provides logical networking.
Server area
Internet
10.2.0.0/24
VLAN 302
VLAN 200
Figure 2-42 provides information only interfaces related to the switches and NGFW
Modules.
4. Bundle GE0/0/1 and GE0/0/2 interfaces on the panel of each NGFW Module
into an Eth-Trunk0 interface, which functions as the heartbeat interface and
backup channel and enable hot standby.
5. Configure security functions, such as security policies and IPS on NGFW
Module_A. NGFW Module_A will automatically synchronize its configurations
to NGFW Module_B.
Procedure
Step 1 Complete interface and basic network configurations on NGFW Modules.
# Add the interfaces connecting NGFW Module_A to its connected switch to Eth-
Trunk 1.
[Module_A] interface Eth-Trunk 1
[Module_A-Eth-Trunk1] description To_SWITCHA_trunk10
[Module_A-Eth-Trunk1] quit
[Module_A] interface GigabitEthernet 1/0/0
[Module_A-GigabitEthernet1/0/0] Eth-Trunk 1
[Module_A-GigabitEthernet1/0/0] quit
[Module_A] interface GigabitEthernet 1/0/1
[Module_A-GigabitEthernet1/0/1] Eth-Trunk 1
[Module_A-GigabitEthernet1/0/1] quit
<sysname> system-view
[sysname] sysname Module_B
# Add the interfaces connecting NGFW Module_B to its connected switch to Eth-
Trunk 1.
[Module_B] interface Eth-Trunk 1
[Module_B-Eth-Trunk1] description To_SWITCHB_trunk11
[Module_B-Eth-Trunk1] quit
[Module_B] interface GigabitEthernet 1/0/0
[Module_B-GigabitEthernet1/0/0] Eth-Trunk 1
[Module_B-GigabitEthernet1/0/0] quit
[Module_B] interface GigabitEthernet 1/0/1
[Module_B-GigabitEthernet1/0/1] Eth-Trunk 1
[Module_B-GigabitEthernet1/0/1] quit
# Specify the heartbeat interface and enable hot standby on NGFW Module_A.
[Module_A] hrp interface Eth-Trunk 0
[Module_A] hrp enable
# Specify the heartbeat interface and enable hot standby on NGFW Module_B.
[Module_B] hrp interface Eth-Trunk 0
[Module_B] hrp enable
[Module_B] hrp standby-device //This command is required only in versions earlier than
V100R001C30SPC300.
After hot standby is configured, the configurations and sessions on the active device are
synchronized to the standby device; therefore, you only need to perform the following
configurations on the active NGFW Module_A.
Before configuring intrusion prevention, ensure that the required license is loaded and the
intrusion prevention signature database is the latest version.
When configuring intrusion prevention, use the default intrusion prevention profile default.
# Configure the CSS on SwitchA. In the example, the CSS connection mode is
CSS card connection mode, the CSS ID is 1, and the CSS priority is 100.
<Huawei> system-view
[Huawei] sysname SwitchA
[SwitchA] set css mode css-card //Set the CSS connection mode. The default mode is CSS
card connection mode.
[SwitchA] set css id 1 //Set the CSS ID. The default value is 1.
[SwitchA] set css priority 100 //Set the CSS priority. The default value is 1.
# Configure the CSS on SwitchB. In the example, the CSS connection mode is
CSS card connection mode, the CSS ID is 2, and the CSS priority is 10.
<Huawei> system-view
[Huawei] sysname SwitchB
[SwitchB] set css mode css-card
[SwitchB] set css id 2
[SwitchB] set css priority 10
# To use SwitchA as the active switch, enable CSS on SwitchA and then restart
SwitchA.
[SwitchA] css enable
Warning: The CSS configuration will take effect only after the system is rebooted. T
he next CSS mode is CSS card. Reboot now? [Y/N]:y
# Log in to the CSS from the console port of any MPU and run the following
command to view the CSS status.
<SwitchA> display css status
CSS Enable switch On
Chassis Id CSS Enable CSS Status CSS Mode Priority Master Force
------------------------------------------------------------------------------
1 On Master CSS card 100 Off
2 On Standby CSS card 10 Off
If the CSS IDs, CSS priorities, CSS enabling status, and CSS status of the two
member switches are displayed, as shown in the preceding information, the
CSS has been established.
You are advised to configure MAD to minimize the impact of a CSS split on
services. Detailed configurations will not be described here.
5. Rename the cluster system to CSS.
<SwitchA> system-view
[SwitchA] sysname CSS
[CSS]
----End
Verification
1. Run the display hrp state command on NGFW Module_A to check the
current HRP status. If the following output is displayed, an HRP relationship is
successfully established.
HRP_A[Module_A] display hrp state
The firewall's config state is: ACTIVE
2. Check whether the access from the intranet to the Internet succeeds and
check the session table of each NGFW Module.
HRP_A[Module_A] display firewall session table
Current Total Sessions : 1
http VPN: public --> public 10.1.0.10:22048 --> 3.3.3.3:80
HRP_S[Module_B] display firewall session table
Current Total Sessions : 1
http VPN: public --> public Remote 10.1.0.10:22048 --> 3.3.3.3:80
3. Check whether the access from users in the intranet to servers succeeds and
check the session table of each NGFW Module.
HRP_A[Module_A] display firewall session table
Current Total Sessions : 1
http VPN: public --> public 10.1.0.10:22048 --> 10.2.0.8:80
HRP_S[Module_A] display firewall session table
Current Total Sessions : 1
http VPN: public --> public Remote 10.1.0.10:22048 --> 10.2.0.8:80
4. Configure a PC in the Trust zone to constantly ping the public address and run
the shutdown command on Eth-trunk1 of NGFW Module_A. Then check the
status switchover of the NGFW Module and discarded ping packets. If the
status switchover is normal, NGFW Module_B becomes the active device and
carries services. The command prompt of NGFW Module_B is changed from
HRP_S to HRP_A, and the command prompt of NGFW Module_A is changed
from HRP_A to HRP_S. No or several ping packets (1 to 3 packets, depending
on actual network environments) are discarded.
Run the undo shutdown command on Eth-trunk1 of NGFW Module_A and
check the status switchover of the NGFW Module and discarded ping packets.
If the status switchover is normal, NGFW Module_A becomes the active device
and starts to carry service after the preemption delay (60s by default) expires.
The command prompt of NGFW Module_A is changed from HRP_S to HRP_A,
and the command prompt of NGFW Module_B is changed from HRP_A to
HRP_S. No or several ping packets (1 to 3 packets, depending on actual
network environments) are discarded.
Configuration Scripts
Configuration scripts of the NGFW Modules: