HCNA Intermediate Lab Guide
HCNA Intermediate Lab Guide
HCNA Intermediate Lab Guide
HCNA-HNTD
INTERMEDIATE
Huawei Networking Technology and Device
Lab Guide
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of
their respective holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but all
statements, information, and recommendations in this manual do not constitute the
warranty of any kind, express or implied.
Huawei Certification
Version 2.2
Huawei Certification System
Relying on its strong technical and professional training and certification system
and in accordance with customers of different ICT technology levels, Huawei
certification is committed to providing customers with authentic, professional
certification, and addresses the need for the development of quality engineers that
are capable of supporting enterprise networks in the face of an ever changing ICT
industry. The Huawei certification portfolio for routing and switching (R&S) is
comprised of three levels to support and validate the growth and value of customer
skills and knowledge in routing and switching technologies.
The Huawei Certified Network Associate (HCNA) certification validates the skills
and knowledge of IP network engineers to implement and support small to
medium-sized enterprise networks. The HCNA certification provides a rich
foundation of skills and knowledge for the establishment of such enterprise
networks, along with the capability to implement services and features within
existing enterprise networks, to effectively support true industry operations.
HCNA certification covers fundamental skills for TCP/IP, routing, switching and
related IP network technologies, together with Huawei data communications
products, and skills for versatile routing platform (VRP) operation and
management.
LAB 3-1 FILTERING ENTERPRISE DATA WITH ACCESS CONTROL LISTS. .............................................................. 102
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Topology
Scenario
Total Error: 0
CRC: 0, Giants: 0
Jabbers: 0, Fragments: 0
Runts: 0, DropEvents: 0
Alignments: 0, Symbols: 0
Ignoreds: 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
Total Error: 0
Collisions: 0, ExcessiveCollisions: 0
Late Collisions: 0, Deferreds: 0
Buffers Purged: 0
Set the rate of G0/0/9 and G0/0/10 on S1 to 100 Mbit/s. Before changing the
interface rate, disable auto-negotiation.
[S1]interface GigabitEthernet 0/0/9
[S1-GigabitEthernet0/0/9]undo negotiation auto
[S1-GigabitEthernet0/0/9]speed 100
[S1-GigabitEthernet0/0/9]quit
[S1]interface GigabitEthernet 0/0/10
[S1-GigabitEthernet0/0/10]undo negotiation auto
[S1-GigabitEthernet0/0/10]speed 100
Confirm that the rate of G0/0/9 and G0/0/10 have been set on S1.
[S1]display interface GigabitEthernet 0/0/9
Create Eth-Trunk 1 on S1 and S2. Delete the default configuration from G0/0/9 and
G0/0/10 on S1 and S2, and then add G0/0/9 and G0/0/10 to Eth-Trunk 1.
[S1]interface Eth-Trunk 1
[S1-Eth-Trunk1]quit
[S1]interface GigabitEthernet 0/0/9
[S1-GigabitEthernet0/0/9]eth-trunk 1
[S1-GigabitEthernet0/0/9]quit
[S1]interface GigabitEthernet 0/0/10
[S1-GigabitEthernet0/0/10]eth-trunk 1
[S2]interface Eth-Trunk 1
[S2-Eth-Trunk1]quit
[S2]display eth-trunk 1
Eth-Trunk1's state information is:
WorkingMode: NORMAL Hash arithmetic: According to SIP-XOR-DIP
Least Active-linknumber: 1 Max Bandwidth-affected-linknumber: 8
Operate status: up Number Of Up Port In Trunk: 2
----------------------------------------------------------------------------
PortName Status Weight
GigabitEthernet0/0/9 Up 1
GigabitEthernet0/0/10 Up 1
The greyed lines in the preceding information indicate that the Eth-Trunk works
properly.
Create Eth-Trunk 1 and set the load balancing mode of the Eth-Trunk to static LACP
mode.
[S1]interface Eth-Trunk 1
[S1-Eth-Trunk1]mode lacp
[S1-Eth-Trunk1]quit
[S1]interface GigabitEthernet 0/0/9
[S1-GigabitEthernet0/0/9]eth-trunk 1
[S1-GigabitEthernet0/0/9]quit
[S1]interface GigabitEthernet 0/0/10
[S1-GigabitEthernet0/0/10]eth-trunk 1
[S2]interface Eth-Trunk 1
[S2-Eth-Trunk1]mode lacp
[S2-Eth-Trunk1]quit
[S2]interface GigabitEthernet 0/0/9
[S2-GigabitEthernet0/0/9]eth-trunk 1
[S2-GigabitEthernet0/0/9]interface GigabitEthernet 0/0/10
[S2-GigabitEthernet0/0/10]eth-trunk 1
Verify that the LACP-static mode has been enabled on the two links.
[S1]display eth-trunk
Eth-Trunk1's state information is:
Local:
LAG ID: 1 WorkingMode: LACP
Preempt Delay: Disabled Hash arithmetic: According to SIP-XOR-DIP
System Priority: 32768 System ID: d0d0-4ba6-aab0
Least Active-linknumber: 1 Max Active-linknumber: 8
Operate status: up Number Of Up Port In Trunk: 2
--------------------------------------------------------------------------------
ActorPortName Status PortType PortPri PortNo PortKey PortState Weight
GigabitEthernet0/0/9 Selected 100M 32768 1 289 10111100 1
GigabitEthernet0/0/10 Selected 100M 32768 2 289 10111100 1
Partner:
--------------------------------------------------------------------------------
ActorPortName SysPri SystemID PortPri PortNo PortKey PortState
Set the priority of the interface and determine active links on S1.
[S1]interface GigabitEthernet 0/0/9
[S1-GigabitEthernet0/0/9]lacp priority 100
[S1-GigabitEthernet0/0/9]quit
[S1]interface GigabitEthernet 0/0/10
[S1-GigabitEthernet0/0/10]lacp priority 100
Partner:
--------------------------------------------------------------------------------
ActorPortName SysPri SystemID PortPri PortNo PortKey PortState
GigabitEthernet0/0/9 32768 d0d0-4ba6-ac20 32768 1 289 10111100
GigabitEthernet0/0/10 32768 d0d0-4ba6-ac20 32768 2 289 10111100
[S2]display eth-trunk 1
Eth-Trunk1's state information is:
Local:
LAG ID: 1 WorkingMode: LACP
Preempt Delay: Disabled Hash arithmetic: According to SIP-XOR-DIP
System Priority: 32768 System ID: d0d0-4ba6-ac20
Partner:
--------------------------------------------------------------------------------
ActorPortName SysPri SystemID PortPri PortNo PortKey PortState
GigabitEthernet0/0/9 100 d0d0-4ba6-aab0 100 1 289 10111100
GigabitEthernet0/0/10 100 d0d0-4ba6-aab0 100 2 289 10111100
Final Configuration
[S1]display current-configuration
#
!Software Version V200R008C00SPC500
sysname S1
#
lacp priority 100
#
interface Eth-Trunk1
mode lacp
#
interface GigabitEthernet0/0/9
eth-trunk 1
lacp priority 100
undo negotiation auto
speed 100
#
interface GigabitEthernet0/0/10
eth-trunk 1
lacp priority 100
undo negotiation auto
speed 100
#
return
[S2]display current-configuration
#
!Software Version V200R008C00SPC500
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Create VLANs.
Configure VLAN tagging over ports using the hybrid port link type.
Configure the default VLAN for an interface using the Port VLAN ID.
Topology
Scenario
If you are starting this section with a non-configured device, begin here and then
move to step 2. For those continuing from previous labs, begin at step 2.
Establish an Eth-trunk link between S1 and S2.
<Quidway>system-view
[Quidway]sysname S1
[S1]interface Eth-trunk 1
[S1-Eth-Trunk1]mode lacp
[S1-Eth-Trunk1]quit
[S1]interface GigabitEthernet0/0/9
[S1-Gigabitethernet0/0/9]eth-trunk 1
[S1-Gigabitethernet0/0/9]interface GigabitEthernet0/0/10
[S1-Gigabitethernet0/0/10]eth-trunk 1
Unused interfaces must be disabled to ensure test result accuracy. In this lab,
interfaces Ethernet 0/0/1 and Ethernet 0/0/7 on S3, Ethernet0/0/1 and
Ethernet0/0/14 on S4 need to be shut down.
<Quidway>system-view
Enter system view, return user view with Ctrl+Z.
[Quidway]sysname S3
[S3]interface Ethernet 0/0/1
[S3-Ethernet0/0/1]shutdown
[S3-Ethernet0/0/1]quit
[S3]interface Ethernet 0/0/7
[S3-Ethernet0/0/7]shutdown
The link type of a switch port interface is hybrid by default. Configure the port
link-type for Eth-Trunk 1 to become a trunk port. Additionally, allow all VLANS to be
permitted over the trunk port.
[S1]interface Eth-Trunk 1
[S1-Eth-Trunk1]port link-type trunk
[S1-Eth-Trunk1]port trunk allow-pass vlan all
[S2]interface Eth-Trunk 1
[S2-Eth-Trunk1]port link-type trunk
[S2-Eth-Trunk1]port trunk allow-pass vlan all
Use S3, R1, R3, and S4 as non-VLAN aware hosts. There are two methods to create
VLANs, and two methods to bind interfaces to the created VLANs, S1 and S2 are
used to demonstrate the two methods. All interfaces associated with hosts should be
configured as access ports.
On S1, associate interface Gigabit Ethernet 0/0/13 with VLAN 3, and interface Gigabit
Ethernet 0/0/1 with VLAN 4.
On S2, associate interface Gigabit Ethernet 0/0/3 with VLAN4, and Gigabit Ethernet
0/0/6 with VLAN 2.
[S1]interface GigabitEthernet0/0/13
[S1-GigabitEthernet0/0/13]port link-type access
[S1-GigabitEthernet0/0/13]quit
[S1]interface GigabitEthernet0/0/1
[S1-GigabitEthernet0/0/1]port link-type access
[S1-GigabitEthernet0/0/1]quit
[S1]vlan 2
[S1-vlan2]vlan 3
[S1-vlan3]port GigabitEthernet0/0/13
Verify that the VLAN configuration has been correctly applied to S1 and S2.
<S1>display vlan
The total number of vlans is : 4
----------------------------------------------------------------------------
U: Up; D: Down; TG: Tagged; UT: Untagged;
MP: Vlan-mapping; ST: Vlan-stacking;
#: ProtocolTransparent-vlan; *: Management-vlan;
----------------------------------------------------------------------------
The highlighted entries confirm the binding of the interfaces to each created VLAN.
All VLANs are permitted over the trunk (TG) port Eth-Trunk 1.
Configure IP addresses on hosts, R1, S3, R3, and S4 as part of the respective VLANs.
Physical port interfaces on switches cannot be configured with IP addresses,
therefore configure the native management interface Vlanif1 with the IP address for
the switch.
<Huawei>system-view
[Huawei]sysname R1
[R1]interface GigabitEthernet0/0/1
[R1-GigabitEthernet0/0/1]ip address 10.0.4.1 24
[S3]interface vlanif 1
[S3-vlanif1]ip address 10.0.4.2 24
[S4]interface vlanif 1
[S4-vlanif1]ip address 10.0.4.4 24
Use the ping command. R1 and R3 in VLAN 4 should be able to communicate with
one another. Devices in other VLANs should be unable to communicate.
[R1]ping 10.0.4.3
PING 10.0.4.3: 56 data bytes, press CTRL_C to break
Reply from 10.0.4.3: bytes=56 Sequence=1 ttl=255 time=6 ms
Reply from 10.0.4.3: bytes=56 Sequence=2 ttl=255 time=2 ms
Reply from 10.0.4.3: bytes=56 Sequence=3 ttl=255 time=2 ms
Reply from 10.0.4.3: bytes=56 Sequence=4 ttl=255 time=2 ms
Reply from 10.0.4.3: bytes=56 Sequence=5 ttl=255 time=2 ms
[R1]ping 10.0.4.4
PING 10.0.4.4: 56 data bytes, press CTRL_C to break
Request time out
Request time out
Request time out
Request time out
Request time out
You may wish to also try between R1 and S3, and between R3 and S4.
Use the hybrid port link type to allow VLAN tagging to be closely managed at a port
interface level. We shall use hybrid ports to allow tagged frames from VLAN 4 to be
received by VLAN 2 and vice versa.
Set the port link type of port interface Gigabit Ethernet 0/0/1 of port S1 and the
interfaces Gigabit Ethernet 0/0/3 and 0/0/6 of S2 as hybrid ports. Additionally set the
hybrid ports to untag all frames associated with VLAN 2 and 4.
[S1]interface GigabitEthernet 0/0/1
[S1-GigabitEthernet0/0/1]undo port default vlan
[S1-GigabitEthernet0/0/1]port link-type hybrid
[S1-GigabitEthernet0/0/1]port hybrid untagged vlan 2 4
[S1-GigabitEthernet0/0/1]port hybrid pvid vlan 4
The port hybrid pvid vlan command will ensure frames received from the host are
tagged with the appropriate VLAN tag. Frames received from VLAN 2 or 4 will be
untagged at the interface before being forwarded to the host.
Use the ping command to verify that R3 in VLAN 4 is still reachable.
<R1>ping 10.0.4.3
PING 10.0.4.3: 56 data bytes, press CTRL_C to break
Reply from 10.0.4.3: bytes=56 Sequence=1 ttl=255 time=1 ms
Reply from 10.0.4.3: bytes=56 Sequence=2 ttl=255 time=1 ms
Reply from 10.0.4.3: bytes=56 Sequence=3 ttl=255 time=1 ms
Reply from 10.0.4.3: bytes=56 Sequence=4 ttl=255 time=10 ms
Reply from 10.0.4.3: bytes=56 Sequence=5 ttl=255 time=1 ms
Use the ping command to test whether S4 in VLAN 2 is now reachable from R1 in
VLAN 4.
<R1>ping 10.0.4.4
PING 10.0.4.4: 56 data bytes, press CTRL_C to break
Reply from 10.0.4.4: bytes=56 Sequence=1 ttl=255 time=41 ms
Reply from 10.0.4.4: bytes=56 Sequence=2 ttl=254 time=2 ms
Reply from 10.0.4.4: bytes=56 Sequence=3 ttl=254 time=3 ms
Reply from 10.0.4.4: bytes=56 Sequence=4 ttl=254 time=2 ms
Reply from 10.0.4.4: bytes=56 Sequence=5 ttl=254 time=2 ms
In using the hybrid port link type, frames originating from VLAN 4 are now able to be
received by VLAN 2 and vice versa, whilst still being unable to reach the host address
of 10.0.4.2 in VLAN 3.
Final Configuration
[R1]display current-configuration
[V200R007C00SPC600]
#
sysname R1
#
interface GigabitEthernet0/0/1
ip address 10.0.4.1 255.255.255.0
#
return
[S3]display current-configuration
[S1]display current-configuration
#
!Software Version V200R008C00SPC500
sysname S1
#
vlan batch 2 to 4
#
lacp priority 100
#
interface Eth-Trunk1
port link-type trunk
port trunk allow-pass vlan 2 to 4094
mode lacp
#
interface GigabitEthernet0/0/1
port link-type hybrid
port hybrid pvid vlan 4
port hybrid untagged vlan 2 4
#
interface GigabitEthernet0/0/9
undo negotiation auto
speed 100
eth-trunk 1
lacp priority 100
#
interface GigabitEthernet0/0/10
undo negotiation auto
[S2]display current-configuration
#
!Software Version V200R008C00SPC500
sysname S2
#
vlan batch 2 to 4
#
interface Eth-Trunk1
port link-type trunk
port trunk allow-pass vlan 2 to 4094
mode lacp
#
interface GigabitEthernet0/0/3
port link-type hybrid
port hybrid pvid vlan 4
port hybrid untagged vlan 2 4
#
interface GigabitEthernet0/0/9
undo negotiation auto
speed 100
eth-trunk 1
#
interface GigabitEthernet0/0/10
undo negotiation auto
speed 100
eth-trunk 1
#
interface GigabitEthernet0/0/6
port link-type hybrid
port hybrid pvid vlan 2
port hybrid untagged vlan 2 4
#
[R3]display current-configuration
[V200R007C00SPC600]
#
sysname R3
#
interface GigabitEthernet0/0/2
ip address 10.0.4.3 255.255.255.0
#
return
[S4]display current-configuration
#
!Software Version V100R006C05
sysname S4
#
interface Vlanif1
ip address 10.0.4.4 255.255.255.0
#
interface Ethernet0/0/1
shutdown
#
interface Ethernet0/0/14
shutdown
#
return
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Configuration of GVRP.
Scenario
If you are starting this section with a non-configured device, begin here and then
move to step 3. For those continuing from previous labs, begin at step 2.
<Quidway>system-view
[Quidway]sysname S1
[S1]interface GigabitEthernet 0/0/9
[S1-GigabitEthernet0/0/9]shutdown
[S1-GigabitEthernet0/0/9]quit
[S1]interface GigabitEthernet 0/0/10
[S1-GigabitEthernet0/0/10]shutdown
<Quidway>system-view
[Quidway]sysname S2
[S2]interface GigabitEthernet 0/0/9
[S2-GigabitEthernet0/0/9]shutdown
[S2-GigabitEthernet0/0/9]quit
[S2]interface GigabitEthernet 0/0/10
[S2-GigabitEthernet0/0/10]shutdown
<Quidway>system-view
[Quidway]sysname S3
[S3-Ethernet0/0/7]shutdown
<Quidway>system-view
[Quidway]sysname S4
[S4-Ethernet0/0/14]shutdown
Remove the unsed VLANs and disable the Eth-Trunk interface on S1 and S2. Remove
Vlanif1 on S3 and S4 and bring up interface Ethernet 0/0/1 on S3.
[S1]undo vlan batch 2 to 4
Warning: The configurations of the VLAN will be deleted. Continue?[Y/N]:y
Info: This operation may take a few seconds. Please wait for a moment...done.
[S1]interface Eth-Trunk 1
[S1-Eth-Trunk1]shutdown
[S3]gvrp
[S3]interface Ethernet 0/0/13
[S3-Ethernet0/0/13]gvrp
[S3-Ethernet0/0/13]quit
[S3]interface Ethernet 0/0/1
[S3-Ethernet0/0/1]gvrp
[S4]gvrp
[S4]interface Ethernet0/0/6
[S4-Ethernet0/0/6]gvrp
[S4-Ethernet0/0/6]quit
[S4]interface Ethernet 0/0/1
[S4-Ethernet0/0/1]gvrp
Create VLAN 100 on S1, VLAN 200 on S2 and VLAN 2 on S1, S2, S3 and S4.
[S1]vlan batch 2 100
[S2]vlan batch 2 200
[S3]vlan 2
[S4]vlan 2
Run the display gvrp statistics command on S3 and S4 to view the GVRP statistics.
[S3]display gvrp statistics
GVRP statistics on port Ethernet0/0/1
GVRP status : Enabled
The registration type is set as normal by default. Use the display vlan command to
verify the VLAN configuration on S3 and S4.
[S3]display vlan
The total number of vlans is : 4
----------------------------------------------------------------------------
U: Up; D: Down; TG: Tagged; UT: Untagged;
MP: Vlan-mapping; ST: Vlan-stacking;
#: ProtocolTransparent-vlan; *: Management-vlan;
----------------------------------------------------------------------------
[S4]display vlan
The total number of vlans is : 4
----------------------------------------------------------------------------U: Up;
D: Down; TG: Tagged; UT: Untagged;
MP: Vlan-mapping; ST: Vlan-stacking;
#: ProtocolTransparent-vlan; *: Management-vlan;
----------------------------------------------------------------------------
VID Type Ports
----------------------------------------------------------------------------
1 common UT:Eth0/0/1(U) Eth0/0/2(D) Eth0/0/3(D) Eth0/0/4(D)
Eth0/0/5(D) Eth0/0/7(D) Eth0/0/8(D) Eth0/0/9(D)
Eth0/0/10(D) Eth0/0/11(D) Eth0/0/12(D) Eth0/0/13(D)
Eth0/0/14(D) Eth0/0/15(D) Eth0/0/16(D) Eth0/0/17(D)
Eth0/0/18(D) Eth0/0/19(D) Eth0/0/20(D) Eth0/0/21(D)
Eth0/0/22(D) Eth0/0/23(D) Eth0/0/24(D) GE0/0/1(D)
GE0/0/2(D) GE0/0/3(D) GE0/0/4(D)
2 common TG:Eth0/0/1(U) Eth0/0/6(U)
100 dynamic TG:Eth0/0/1(U)
200 dynamic TG:Eth0/0/6(U)
…output omitted…
S3 and S4 are learning VLAN 100 and VLAN 200 dynamically, but only in one
direction. VLAN 2 has been statically defined. Create VLAN 200 on S1 and VLAN 100
on S2 to enable 2-way propagation.
[S1]vlan 200
[S2]vlan 100
[S4]display vlan
…output omitted…
VID Type Ports
----------------------------------------------------------------------------
1 common UT:Eth0/0/1(U) Eth0/0/2(D) Eth0/0/3(D) Eth0/0/4(D)
Eth0/0/5(D) Eth0/0/7(D) Eth0/0/8(D) Eth0/0/9(D)
Eth0/0/11(D) Eth0/0/12(D) Eth0/0/10(D) Eth0/0/13(D)
Eth0/0/14(D) Eth0/0/15(D) Eth0/0/16(D) Eth0/0/17(D)
Eth0/0/18(D) Eth0/0/19(D) Eth0/0/20(D) Eth0/0/21(D)
Eth0/0/22(D) Eth0/0/23(D) Eth0/0/24(U) GE0/0/1(D)
GE0/0/2(D) GE0/0/3(D) GE0/0/4(D)
2 common TG:Eth0/0/1(U) Eth0/0/6(U)
100 dynamic TG:Eth0/0/1(U) Eth0/0/6(U)
200 dynamic TG:Eth0/0/1(U) Eth0/0/6(U)
…output omitted…
The highlighted entries indicate the interfaces that have been added to VLAN100
and VLAN200 on both S3 and S4.
Change the registration type of Ethernet 0/0/1 on S3 to fixed. The same steps can be
performed on Ethernet 0/0/1 of S4.
[S3]interface Ethernet 0/0/1
[S3-Ethernet0/0/1]gvrp registration fixed
Run the display gvrp statistics command on S3 and S4 to view the changes.
[S3]display gvrp statistics interface Ethernet 0/0/1
GVRP statistics on port Ethernet0/0/1
GVRP status : Enabled
GVRP registrations failed : 11
GVRP last PDU origin : e028-6120-36f0
GVRP registration type : Fixed
The GVRP registration type is verified as fixed on Ethernet 0/0/1 interface. Dynamic
VLANs are not allowed to register on this interface.
The highlighted entries show that interface Ethernet 0/0/1 is not in registering
dynamic VLANs 100 and 200.
Configure interface Ethernet 0/0/1 of S3 to use the forbidden registration type. The
same steps can be performed on Ethernet 0/0/1 of S4.
[S3]interface Ethernet 0/0/1
[S3-Ethernet0/0/1]gvrp registration forbidden
Run the display gvrp statistics command to view the changes to GVRP.
[S3]display gvrp statistics interface Ethernet 0/0/1
GVRP statistics on port Ethernet0/0/1
GVRP status : Enabled
GVRP registrations failed : 18
GVRP last PDU origin : 5489-98ec-f012
GVRP registration type : Forbidden
The GVRP registration type is set to forbidden on the Ethernet 0/0/1 interface.
Forbidden mode only allows VLAN1 pass over interface Ethernet 0/0/1, all other
VLANS are restricted.
Final Configuration
[S1]display current-configuration
#
!Software Version V200R008C00SPC500
sysname S1
#
vcmp role silent
#
vlan batch 2 100 200
#
gvrp
#
interface GigabitEthernet0/0/9
shutdown
#
interface GigabitEthernet0/0/10
shutdown
#
interface GigabitEthernet0/0/13
port link-type trunk
[S2]display current-configuration
#
!Software Version V200R008C00SPC500
sysname S2
#
vcmp role silent
vlan batch 2 100 200
#
gvrp
#
interface GigabitEthernet0/0/6
port link-type trunk
port trunk allow-pass vlan 2 to 4094
gvrp
#
interface GigabitEthernet0/0/9
shutdown
#
interface GigabitEthernet0/0/10
shutdown
#
return
[S3]display current-configuration
#
!Software Version V100R006C05
sysname S3
#
vlan batch 2
#
gvrp
#interface Ethernet0/0/1
port link-type trunk
port trunk allow-pass vlan 2 to 4094
gvrp
gvrp registration forbidden
#
[S4]display current-configuration
#
!Software Version V100R006C05
sysname S4
#
vlan batch 2
#
gvrp
#
interface Ethernet0/0/1
port link-type trunk
port trunk allow-pass vlan 2 to 4094
gvrp
gvrp registration forbidden
#
interface Ethernet0/0/6
port link-type trunk
port trunk allow-pass vlan 2 to 4094
gvrp
#
interface Ethernet0/0/14
shutdown
#
return
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Topology
Scenario
Tasks
If you are starting this section with a non-configured device, begin here and then move to
step 3. For those continuing from previous labs, begin at step 2.
Configure the system name for R1, R3 and S1. Configure the IP address 10.0.4.1/24 on
interface Gigabit Ethernet 0/0/1.
<Huawei>system-view
Enter system view, return user view with Ctrl+Z.
[Huawei]sysname R1
[R1]interface GigabitEthernet 0/0/1
[R1-GigabitEthernet0/0/1]ip address 10.0.4.1 24
<Huawei>system-view
Enter system view, return user view with Ctrl+Z.
[Huawei]sysname R3
<Quidway>system-view
[Quidway]sysname S1
Remove the IP address 10.0.4.3 from R3, and disable the swich interfaces between S1 and
S3 and S2 and S4 respectively.
[S1]undo gvrp
Warning: All information about the GVRP will be deleted . Continue?[Y/N]:y
Info: This operation may take a few seconds. Please wait for a moment...done.
[S2]undo gvrp
Warning: All information about the GVRP will be deleted . Continue?[Y/N]:y
Info: This operation may take a few seconds. Please wait for a moment...done.
[S2]interface GigabitEthernet 0/0/6
[S2-GigabitEthernet0/0/6]undo port trunk allow-pass vlan 2 to 4094
[S2-GigabitEthernet0/0/6]shutdown
[S2-GigabitEthernet0/0/6]quit
[S2]interface GigabitEthernet 0/0/3
[S2-GigabitEthernet0/0/3]undo port hybrid vlan 2 4
[S2-GigabitEthernet0/0/3]quit
[S2]undo vlan batch 2 100 200
Warning: The configurations of the VLAN will be deleted. Continue?[Y/N]:y
Info: This operation may take a few seconds. Please wait for a moment...done.
[S3]undo gvrp
Warning: All information about the GVRP will be deleted . Continue?[Y/N]:y
Info: This operation may take a few seconds. Please wait for a moment...done.
[S3]interface Ethernet 0/0/13
[S3-Ethernet0/0/13]undo port trunk allow-pass vlan 2 to 4094
[S3-Ethernet0/0/13]port link-type hybrid
[S3-Ethernet0/0/13]quit
[S3]interface Ethernet 0/0/1
[S3-Ethernet0/0/1]undo port trunk allow-pass vlan 2 to 4094
[S3-Ethernet0/0/1]quit
[S3]undo vlan 2
[S4]undo gvrp
Warning: All information about the GVRP will be deleted . Continue?[Y/N]:y
Info: This operation may take a few seconds. Please wait for a moment...done.
[S4]interface Ethernet 0/0/6
[S4-Ethernet0/0/6]undo port trunk allow-pass vlan 2 to 4094
[S1]vlan batch 4 8
Info: This operation may take a few seconds. Please wait for a moment...done.
[S1]interface GigabitEthernet 0/0/1
[S1-GigabitEthernet0/0/1]port link-type access
[S1-GigabitEthernet0/0/1]port default vlan 4
[S1-GigabitEthernet0/0/1]quit
[S1]interface GigabitEthernet0/0/3
[S1-GigabitEthernet0/0/3]port link-type access
[S1-GigabitEthernet0/0/3]port default vlan 8
[S1-GigabitEthernet0/0/3]quit
Set interface Gigabit Ethernet 0/0/2 as a trunk link for VLANs 4 and 8.
[S1]interface GigabitEthernet0/0/2
[S1-GigabitEthernet0/0/2]port link-type trunk
[S1-GigabitEthernet0/0/2]port trunk allow-pass vlan 4 8
<R1>ping 10.0.8.1
PING 10.0.8.1: 56 data bytes, press CTRL_C to break
Request time out
Request time out
Request time out
Request time out
Request time out
<R1>ping 10.0.8.1
PING 10.0.8.1: 56 data bytes, press CTRL_C to break
Reply from 10.0.8.1: bytes=56 Sequence=1 ttl=254 time=10 ms
Reply from 10.0.8.1: bytes=56 Sequence=2 ttl=254 time=1 ms
Reply from 10.0.8.1: bytes=56 Sequence=3 ttl=254 time=1 ms
Reply from 10.0.8.1: bytes=56 Sequence=4 ttl=254 time=10 ms
Reply from 10.0.8.1: bytes=56 Sequence=5 ttl=254 time=1 ms
Final Configuration
[R1]display current-configuration
[V200R007C00SPC600]
#
sysname R1
#
interface GigabitEthernet0/0/1
ip address 10.0.4.1 255.255.255.0
#
ip route-static 0.0.0.0 0.0.0.0 10.0.4.254
#
user-interface con 0
authentication-mode password
set authentication password cipher %$%$dD#}P<HzJ;Xs%X>hOkm!,.+Iq61QK`K6tI}cc-;k_o`C.+
L,%$%$
user-interface vty 0 4
[R2]display current-configuration
[V200R007C00SPC600]
#
sysname R2
#
interface GigabitEthernet0/0/1
#
interface GigabitEthernet0/0/1.1
dot1q termination vid 4
ip address 10.0.4.254 255.255.255.0
arp broadcast enable
#
interface GigabitEthernet0/0/1.3
dot1q termination vid 8
ip address 10.0.8.254 255.255.255.0
arp broadcast enable
#
user-interface con 0
authentication-mode password
set authentication password cipher %$%$|nRPL^hr2IXi7LHDID!/,.*%.8%h;3:,hXO2dk#ikaWI.*
(,%$%$
user-interface vty 0 4
#
return
[R3]dis current-configuration
[V200R007C00SPC600]
#
sysname R3
#
interface GigabitEthernet0/0/1
ip address 10.0.8.1 255.255.255.0
#
ip route-static 0.0.0.0 0.0.0.0 10.0.8.254
#
user-interface con 0
authentication-mode password
set authentication password cipher %$%$W|$)M5D}v@bY^gK\;>QR,.*d;8Mp>|+EU,:~D~8b59~..*
g,%$%$
user-interface vty 0 4
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Topology
Scenario
The introduction of layer three switches into the enterprise network opened up
opportunities for streamlining the current VLAN routing configuration. The network
administrator has been given the task to implement VLAN routing using only the
layer three switches to support communication between the VLANs in the network
as displayed in the topology. VLANs should be capable of inter VLAN
Tasks
If you are starting this section with a non-configured device, begin here and then
move to step 3. For those continuing from previous labs, begin at step 2.
Configure R1 with the address 10.0.4.1/24 on interface Gigabit Ethernet 0/0/1.
Establish an Eth-Trunk beween S1 an S2. Disable any unnecessary interfaces on S1
and S2 to S3 and S4.
<Huawei>system-view
Enter system view, return user view with Ctrl+Z.
[Huawei]sysname R1
[R1]interface GigabitEthernet 0/0/1
[R1-GigabitEthernet0/0/1]ip address 10.0.4.1 24
<Huawei>system-view
Enter system view, return user view with Ctrl+Z.
[Huawei]sysname R3
<Quidway>system-view
[Quidway]sysname S1
[S1]interface Eth-Trunk 1
[S1-Eth-Trunk1]mode lacp
[S1-Eth-Trunk1]port link-type trunk
[S1-Eth-Trunk1]port trunk allow-pass vlan all
[S1-Eth-Trunk1]quit
[S1]interface GigabitEthernet 0/0/9
[S1-GigabitEthernet0/0/9]eth-trunk 1
[S1-GigabitEthernet0/0/9]interface GigabitEthernet 0/0/10
[S1-GigabitEthernet0/0/10]eth-trunk 1
<Quidway>system-view
[Quidway]sysname S2
[S2]interface Eth-Trunk 1
[S2-Eth-Trunk1]mode lacp
[S2-Eth-Trunk1]port link-type trunk
[S2-Eth-Trunk1]port trunk allow-pass vlan all
<Quidway>system-view
[Quidway]sysname S3
[S3]interface Ethernet 0/0/7
[S3-Ethernet0/0/7]shutdown
<Quidway>system-view
[Quidway]sysname S4
[S4]interface Ethernet 0/0/14
[S4-Ethernet0/0/14]shutdown
[S2]interface GigabitEthernet0/0/6
[S2-GigabitEthernet0/0/6]undo shutdown
[S1]interface Eth-Trunk 1
[S1-Eth-Trunk1]undo shutdown
[S2]interface Eth-Trunk 1
[S2-Eth-Trunk1]undo shutdown
[S1]vlan batch 3 to 7
Info: This operation may take a few seconds. Please wait for a moment...done.
[S2]vlan batch 3 to 7
Info: This operation may take a few seconds. Please wait for a moment...done.
[S2]display vlan
The total number of vlans is : 6
…output omitted…
[S2]interface Eth-Trunk 1
[S2-Eth-Trunk1]port trunk pvid vlan 5
[S2-Eth-Trunk1]quit
[S2]interface GigabitEthernet 0/0/3
[S2-GigabitEthernet0/0/3]port link-type access
[S2-GigabitEthernet0/0/3]port default vlan 6
[S2-GigabitEthernet0/0/3]quit
[S2]interface GigabitEthernet 0/0/6
[S2-GigabitEthernet0/0/6]port link-type access
[S2-GigabitEthernet0/0/6]port default vlan 7
<S2>display vlan
The total number of vlans is : 6
…output omit…
VID Type Ports
----------------------------------------------------------------------------
1 common UT:GE0/0/1(U) GE0/0/2(D) GE0/0/4(U) GE0/0/5(U)
GE0/0/6(D) GE0/0/7(D) GE0/0/8(D) GE0/0/11(U)
GE0/0/12(U) GE0/0/13(U) GE0/0/14(D) GE0/0/15(D)
GE0/0/16(D) GE0/0/17(D) GE0/0/18(D) GE0/0/19(D)
GE0/0/20(D) GE0/0/21(D) GE0/0/22(D) GE0/0/23(D)
TG:Eth-Trunk1(U)
3 common TG:Eth-Trunk1(U)
4 common TG:Eth-Trunk1(U)
5 common TG:Eth-Trunk1(U)
6 common UT:GE0/0/3(U)
TG:Eth-Trunk1(U)
7 common UT:GE0/0/6(U)
TG:Eth-Trunk1(U)
…output omit…
Configure IP addresses for Vlanif3, Vlanif4, and Vlanif5 on S1, and for Vlanif5, Vlanif6,
and Vlanif7 on S2.
[S1]interface Vlanif 3
[S1-Vlanif3]ip address 10.0.3.254 24
[S1-Vlanif3]interface Vlanif 4
[S1-Vlanif4]ip address 10.0.4.254 24
[S1-Vlanif4]interface Vlanif 5
[S1-Vlanif5]ip address 10.0.5.1 24
[S2]interface Vlanif 5
[S2-Vlanif5]ip address 10.0.5.2 24
[S2-Vlanif5]interface Vlanif 6
[S2-Vlanif6]ip address 10.0.6.254 24
[S2-Vlanif6]interface Vlanif 7
[S2-Vlanif7]ip address 10.0.7.254 24
[S3]interface Vlanif 1
[S3-Vlanif1]ip address 10.0.3.3 24
[S3-Vlanif1]quit
[S3]ip route-static 0.0.0.0 0.0.0.0 10.0.3.254
[S4]interface Vlanif 1
[S4-Vlanif1]ip address 10.0.7.4 24
[S4-Vlanif1]quit
The connectivity between R1 and R3 fails. Use the tracert command to troubleshoot
the fault:
[R1]tracert 10.0.6.3
traceroute to 10.0.6.3(10.0.6.3), max hops: 30 ,packet length: 40,press CTRL_C to break
1 10.0.4.254 17 ms 4 ms 4 ms
2 * * *
According to the command output, S1 does not have a route to the network
segment 10.0.6.0 because the network segment is not directly connected to S1. In
addition, no static route or dynamic routing protocol has been configured to
advertise the routes.
[S1]ospf
[S1-ospf-1]area 0
[S1-ospf-1-area-0.0.0.0]network 10.0.0.0 0.255.255.255
[S2]ospf
[S2-ospf-1]area 0
[S2-ospf-1-area-0.0.0.0]network 10.0.0.0 0.255.255.255
After the configuration, wait until S1 and S2 exchange OSPF routes and complete the
link state database, then view the resulting routing table of S1.
S1 has learned two routes using OSPF. Test connectivity between R1 and R3.
[R1]ping 10.0.6.3
PING 10.0.6.3: 56 data bytes, press CTRL_C to break
Reply from 10.0.6.3: bytes=56 Sequence=1 ttl=253 time=11 ms
Reply from 10.0.6.3: bytes=56 Sequence=2 ttl=253 time=1 ms
Reply from 10.0.6.3: bytes=56 Sequence=3 ttl=253 time=10 ms
Reply from 10.0.6.3: bytes=56 Sequence=4 ttl=253 time=1 ms
Reply from 10.0.6.3: bytes=56 Sequence=5 ttl=253 time=1 ms
[R1]ping 10.0.7.4
PING 10.0.7.4: 56 data bytes, press CTRL_C to break
Reply from 10.0.7.4: bytes=56 Sequence=1 ttl=253 time=30 ms
Reply from 10.0.7.4: bytes=56 Sequence=2 ttl=252 time=2 ms
Reply from 10.0.7.4: bytes=56 Sequence=3 ttl=252 time=3 ms
Reply from 10.0.7.4: bytes=56 Sequence=4 ttl=252 time=2 ms
Final Configuration
[R1]display current-configuration
[V200R007C00SPC600]
#
sysname R1
#
interface GigabitEthernet0/0/1
ip address 10.0.4.1 255.255.255.0
#
ip route-static 0.0.0.0 0.0.0.0 10.0.4.254
#
return
[S1]display current-configuration
!Software Version V200R008C00SPC500
#
sysname S1
#
vlan batch 3 to 7
#
interface Vlanif3
ip address 10.0.3.254 255.255.255.0
#
interface Vlanif4
ip address 10.0.4.254 255.255.255.0
#
interface Vlanif5
ip address 10.0.5.1 255.255.255.0
#
interface Eth-Trunk1
port link-type trunk
port trunk pvid vlan 5
port trunk allow-pass vlan 2 to 4094
[S2]display current-configuration
!Software Version V200R008C00SPC500
#
sysname S2
#
vlan batch 3 to 7
#
interface Vlanif5
ip address 10.0.5.2 255.255.255.0
#
interface Vlanif6
ip address 10.0.6.254 255.255.255.0
#
interface Vlanif7
ip address 10.0.7.254 255.255.255.0
#
interface Eth-Trunk1
port link-type trunk
port trunk pvid vlan 5
port trunk allow-pass vlan 2 to 4094
[S3]display current-configuration
#
!Software Version V100R006C05
sysname S3
#
interface Vlanif1
ip address 10.0.3.3 255.255.255.0
#
interface Ethernet0/0/7
shutdown
#
ip route-static 0.0.0.0 0.0.0.0 10.0.3.254
#
return
[S4]display current-configuration
#
!Software Version V100R006C05
sysname S4
#
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Topology
Scenario
Tasks
If you are starting this section with a non-configured device, begin here and then move to
step 3. For those continuing from previous labs, begin at step 2.
<Huawei>system-view
Enter system view, return user view with Ctrl+Z.
[Huawei]sysname R1
<Huawei>system-view
Enter system view, return user view with Ctrl+Z.
[Huawei]sysname R2
<Huawei>system-view
Enter system view, return user view with Ctrl+Z.
[Huawei]sysname R3
Remove the static routes to R2 and disable the Ethernet interfaces to avoid creating
alternative routes. Remove any unnecessary VLAN configuration.
After HDLC is enabled on the serial interfaces, view the serial interface status. The
displayed information for R1 should be used as an example.
[R1]display interface Serial1/0/0
Serial1/0/0 current state : UP
Line protocol current state : UP
Last line protocol up time : 2016-3-10 11:25:08
Description:HUAWEI, AR Series, Serial1/0/0 Interface
Route Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec)
Internet Address is 10.0.12.1/24
Link layer protocol is nonstandard HDLC
Last physical up time : 2016-3-10 11:23:55
Last physical down time : 2016-3-10 11:23:55
Current system time: 2016-3-10 11:25:46
Physical layer is synchronous, Baudrate is 64000 bps
Interface is DCE, Cable type is V24, Clock mode is DCECLK
Last 300 seconds input rate 3 bytes/sec 24 bits/sec 0 packets/sec
Last 300 seconds output rate 3 bytes/sec 24 bits/sec 0 packets/sec
Alignments: 0, Overruns: 0
Dribbles: 0, Aborts: 0
No Buffers: 0, Frame Error: 0
Test connectivity of the directly connected link after verifying that the physical status
and protocol status of the interface are Up.
<R2>ping 10.0.12.1
PING 10.0.12.1: 56 data bytes, press CTRL_C to break
Reply from 10.0.12.1: bytes=56 Sequence=1 ttl=255 time=44 ms
Reply from 10.0.12.1: bytes=56 Sequence=2 ttl=255 time=39 ms
Reply from 10.0.12.1: bytes=56 Sequence=3 ttl=255 time=39 ms
Reply from 10.0.12.1: bytes=56 Sequence=4 ttl=255 time=40 ms
Reply from 10.0.12.1: bytes=56 Sequence=5 ttl=255 time=39 ms
[R2]ping 10.0.23.3
PING 10.0.23.3: 56 data bytes, press CTRL_C to break
Reply from 10.0.23.3: bytes=56 Sequence=1 ttl=255 time=44 ms
Reply from 10.0.23.3: bytes=56 Sequence=2 ttl=255 time=39 ms
Reply from 10.0.23.3: bytes=56 Sequence=3 ttl=255 time=39 ms
Reply from 10.0.23.3: bytes=56 Sequence=4 ttl=255 time=40 ms
Reply from 10.0.23.3: bytes=56 Sequence=5 ttl=255 time=39 ms
Enable the RIP routing protocol to advertise the remote networks of R1 & R3.
[R1]rip
[R2]rip
[R2-rip-1]version 2
[R2-rip-1]network 10.0.0.0
[R3]rip
[R3-rip-1]version 2
[R3-rip-1]network 10.0.0.0
After the configuration is complete, check that all the routes have been learned.
Verify that corresponding routes are learned by RIP.
<R1>display ip routing-table
Route Flags: R - relay, D - download to fib
----------------------------------------------------------------------------
Routing Tables: Public
Destinations : 8 Routes : 8
On R1, run the ping command to test connectivity between R1 and R3.
<R1>ping 10.0.23.3
PING 10.0.23.3: 56 data bytes, press CTRL_C to break
Reply from 10.0.23.3: bytes=56 Sequence=1 ttl=254 time=44 ms
Reply from 10.0.23.3: bytes=56 Sequence=2 ttl=254 time=39 ms
Reply from 10.0.23.3: bytes=56 Sequence=3 ttl=254 time=39 ms
Reply from 10.0.23.3: bytes=56 Sequence=4 ttl=254 time=40 ms
Reply from 10.0.23.3: bytes=56 Sequence=5 ttl=254 time=39 ms
View the type of the cable connected to the serial interface, interface status, and
clock frequency, and change the clock frequency.
<R1>display interface Serial1/0/0
Serial1/0/0 current state : UP
Line protocol current state : UP
Last line protocol up time : 2016-03-10 11:25:08
Description:HUAWEI, AR Series, Serial1/0/0 Interface
Route Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec)
Internet Address is 10.0.12.1/24
Link layer protocol is nonstandard HDLC
Last physical up time : 2016-03-10 11:23:55
Last physical down time : 2016-03-10 11:23:55
Current system time: 2016-03-10 11:51:12
Physical layer is synchronous, Baudrate is 64000 bps
Interface is DCE, Cable type is V35, Clock mode is DCECLK1
Last 300 seconds input rate 5 bytes/sec 40 bits/sec 0 packets/sec
Last 300 seconds output rate 2 bytes/sec 16 bits/sec 0 packets/sec
…output omit…
The preceding information shows that S1/0/0 on R1 connects to a DCE cable and the
clock frequency is 64000 bit/s. The DCE controls the clock frequency and bandwidth.
Change the clock frequency on the link between R1 and R2 to 128000 bit/s. This
operation must be performed on the DCE, R1.
[R1]interface Serial 1/0/0
[R1-Serial1/0/0]baudrate 128000
Configure PPP between R1 and R2, as well as R2 and R3. Both ends of the link must
use the same encapsulation mode. If different encapsulation modes are used,
interfaces may display as ‘Down’.
[R1]interface Serial 1/0/0
[R1-Serial1/0/0]link-protocol ppp
Warning: The encapsulation protocol of the link will be changed. Continue? [Y/N]:y
[R2-Serial1/0/0]quit
[R2]interface Serial 2/0/0
[R2-Serial2/0/0]link-protocol ppp
Warning: The encapsulation protocol of the link will be changed. Continue? [Y/N]:y
If the ping operation fails, check the interface status and whether the link layer
protocol type is correct.
<R1>display interface Serial1/0/0
Serial1/0/0 current state : UP
Line protocol current state : UP
Last line protocol up time : 2016-03-10 12:35:41
Description:HUAWEI, AR Series, Serial1/0/0 Interface
Route Port,The Maximum Transmit Unit is 1500, Hold timer is 10(sec)
Internet Address is 10.0.12.1/24
Link layer protocol is PPP
LCP opened, IPCP opened
Last physical up time : 2016-03-10 11:57:20
Last physical down time : 2016-03-10 11:57:19
Current system time: 2016-03-10 13:38:03
Physical layer is synchronous, Baudrate is 128000 bps
Interface is DCE, Cable type is V35, Clock mode is DCECLK1
Last 300 seconds input rate 7 bytes/sec 56 bits/sec 0 packets/sec
Last 300 seconds output rate 4 bytes/sec 32 bits/sec 0 packets/sec
…output omit…
After PPP configuration is complete, routers establish connections at the data link
layer. The local device sends a route to the peer device. The route contains the
interface IP address and a 32-bit mask.
The following information uses R2 as an example, for which the routes to R1 and R3
can be seen.
[R2]display ip routing-table
Route Flags: R - relay, D - download to fib
----------------------------------------------------------------------------
Routing Tables: Public
Destinations : 12 Routes : 12
Think about the origin and functions of the two routes. Check the following items:
If HDLC encapsulation is used, do these two routes exist?
Can R1 and R2 communicate using HDLC or PPP when the IP addresses of S1/0/0
interfaces on R1 and R2 are located on different network segments?
[R1-Serial1/0/0]return
<R1>undo debugging all
After the configuration is complete, the interface changes to an Up state. The ping
command output is as follows:
<R2>ping 10.0.23.3
PING 10.0.23.3: 56 data bytes, press CTRL_C to break
Reply from 10.0.23.3: bytes=56 Sequence=1 ttl=255 time=35 ms
Reply from 10.0.23.3: bytes=56 Sequence=2 ttl=255 time=41 ms
Reply from 10.0.23.3: bytes=56 Sequence=3 ttl=255 time=41 ms
Run the debug command to view negotiation of the PPP connection between R2
and R3. The PPP connection is established using CHAP. Disable interface Serial 2/0/0
on R2, run the debug command, and enable Serial 2/0/0 on R2.
[R2]interface Serial 2/0/0
[R2-Serial2/0/0]shutdown
Run the debugging ppp chap all and the terminal debugging commands to
display the debugging information.
[R2-Serial2/0/0]return
<R2>debugging ppp chap all
<R2>terminal debugging
Info: Current terminal debugging is on.
<R2>display debugging
PPP CHAP packets debugging switch is on
PPP CHAP events debugging switch is on
PPP CHAP errors debugging switch is on
PPP CHAP state change debugging switch is on
The highlighted debugging information shows the key CHAP behavior. Disable the
debugging process.
[R2-Serial2/0/0]return
Why is the PPP Challenge Handshake Authentication Protocol (CHAP) more secure
than the PPP Password Authentication Protocol (PAP)?
Final Configuration
[R1]display current-configuration
[V200R007C00SPC600]
#
sysname R1
#
aaa
authentication-scheme default
authorization-scheme default
accounting-scheme default
domain default
domain default_admin
local-user admin password cipher %$%$=i~>Xp&aY+*2cEVcS-A23Uwe%$%$
local-user admin service-type http
local-user huawei password cipher %$%$B:%I)Io0H8)[%SB[idM3C/!#%$%$
local-user huawei service-type ppp
#
interface Serial1/0/0
link-protocol ppp
ppp authentication-mode pap
ip address 10.0.12.1 255.255.255.0
baudrate 128000
#
rip 1
version 2
network 10.0.0.0
#
user-interface con 0
authentication-mode password
set authentication password cipher %$%$dD#}P<HzJ;Xs%X>hOkm!,.+Iq61QK`K6tI}cc-;k_o`C.+L,%$%
$
user-interface vty 0 4
[R2]display current-configuration
[V200R007C00SPC600]
#
sysname R2
#
interface Serial1/0/0
link-protocol ppp
ppp pap local-user huawei password cipher %$%$u[hr6d<JVHR@->T7xr1<$.iv%$%$
ip address 10.0.12.2 255.255.255.0
#
interface Serial2/0/0
link-protocol ppp
ppp chap user huawei
ppp chap password cipher %$%$e{5h)gh"/Uz0mUC%vEx3$4<m%$%$
ip address 10.0.23.2 255.255.255.0
#
rip 1
version 2
network 10.0.0.0
#
user-interface con 0
authentication-mode password
set authentication password cipher %$%$|nRPL^hr2IXi7LHDID!/,.*%.8%h;3:,hXO2dk#ikaWI.*(,%$%
$
user-interface vty 0 4
#
return
[R3]display current-configuration
[V200R007C00SPC600]
#
sysname R3
#
aaa
authentication-scheme default
authorization-scheme default
accounting-scheme default
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Topology
Scenario
The enterprise network has existing frame relay virtual circuits between the HQ and
some branch offices. A recent change in equipment requires that these frame relay
Tasks
If you are starting this section with a non-configured device, begin here and then
move to step 3. For those continuing from previous labs, begin at step 2.
<Huawei>system-view
Enter system view, return user view with Ctrl+Z.
[Huawei]sysname R1
<Huawei>system-view
Enter system view, return user view with Ctrl+Z.
[Huawei]sysname R2
<Huawei>system-view
Enter system view, return user view with Ctrl+Z.
[Huawei]sysname R3
Disable the serial interfaces used for establishing the HDLC & PPP networks.
Set basic parameters, including IP addresses. Manually define the mapping between
the peer and DLCI. The inverse ARP function should be disabled. Ensure that the
broadcast parameter is used in the fr map command to allow the network on the
loopback interface to be advertised using RIP.
[R1]interface Serial 2/0/0
[R1-Serial2/0/0]link-protocol fr
Warning: The encapsulation protocol of the link will be changed. Continue? [Y/N]:y
[R1-Serial2/0/0]ip address 10.0.123.1 24
[R1-Serial2/0/0]undo fr inarp
[R1-Serial2/0/0]fr map ip 10.0.123.2 102 broadcast
[R1-Serial2/0/0]fr map ip 10.0.123.3 103 broadcast
[R1-Serial2/0/0]interface loopback 0
[R1-LoopBack0]ip address 10.0.1.1 24
Run the following commands to view the FR encapsulation information for the R1
interfaces.
<R1>display fr interface Serial 2/0/0
Serial2/0/0, DTE, physical up, protocol up
Configure RIPv2 on R1, R2 and R3. If you are continuing from the previous
HDLC/PPP lab, the RIP routes for network 10.0.0.0 may have already been configured,
however the automatic summary must still be disabled to uniquely identify the
routes of the peers.
In addition, split horizon is disabled by default on frame relay networks, and so It is
not necessary for the split horizon parameters to be modified in this exercise.
[R1]rip 1
[R1-rip-1]version 2
[R1-rip-1]network 10.0.0.0
[R1-rip-1]undo summary
[R2]rip 1
[R2-rip-1]version 2
[R2-rip-1]network 10.0.0.0
[R2-rip-1]undo summary
[R3]rip 1
[R3-rip-1]version 2
[R3-rip-1]network 10.0.0.0
[R3-rip-1]undo summary
View the routing tables on R1, R2, and R3 to check the learned routes.
<R1>display ip routing-table protocol rip
Route Flags: R - relay, D - download to fib
----------------------------------------------------------------------------
Public routing table : RIP
Destinations : 2 Routes : 2
Perform the same test to network 10.0.2.2 of R2 from network 10.0.3.3 of R3.
The RIP routing protocol has enabled a route between the loopback interfaces of R2
and R3 to be established via R1.
Attempt the same procedure to network 10.0.2.2 of R2 from the S2/0/0 (10.0.123.3)
interface of R3.
[R3]ping 10.0.2.2
PING 10.0.2.2: 56 data bytes, press CTRL_C to break
Request time out
The preceding test results indicate that R3 is unable to communicate with R2 (and
vice versa) when the serial interface is the source. Check the routes to find out why
R3 and R2 are disconnected. The procedure for diagnosing this fault is as follows:
View the R3 routing table and check whether any route is destined for the IP address
10.0.2.2.
If there is such a route, find out the next hop IP address of this route. Then check
whether R3 can reach the next hop and whether there is mapping between the
layer-3 IP addresses and layer-2 PVCs.
If R3 can reach the next hop and there is mapping between Layer-3 IP addresses and
Layer-2 PVCs, check the devices on the route to determine whether there is any
route that can reach IP address 10.0.2.2, whether the next hop of this route is
reachable, and whether there is mapping between Layer-3 IP addresses and Layer-2
PVCs.
If there is a route that can reach IP address 10.0.2.2 and there is mapping between
Layer-3 IP addresses and Layer-2 PVCs, check R2 to determine whether there is any
route that reaches the destination IP address of the response packets and whether
the next hop of this route is reachable.
If the next hop of this route is unreachable and the destination IP address of the
response packets is 10.0.123.3, R2 has the route that reaches this address but there is
no mapping between Layer-3 IP addresses and Layer-2 PVCs.
The following is the output of the commands used in the preceding fault diagnosis
procedure.
<R3>display ip routing-table
Route Flags: R - relay, D - download to fib
----------------------------------------------------------------------------
Routing Tables: Public
Destinations : 13 Routes : 13
<R1>display ip routing-table
Route Flags: R - relay, D - download to fib
----------------------------------------------------------------------------
Routing Tables: Public
Destinations : 14 Routes : 14
<R2>display ip routing-table
Route Flags: R - relay, D - download to fib
----------------------------------------------------------------------------
Routing Tables: Public
Destinations : 13 Routes : 13
The conclusion is that there is no PVC that allows R2 to reach IP address 10.0.123.3.
between R2 and R3
The fault diagnosis results from step 2 indicate that communication fails since there
is no virtual circuit between the frame relay interfaces on R2 and R3. In order to
resolve this, configure a frame relay PVC between the interfaces on R2 and R3.
[R2]interface Serial 3/0/0
[R2-Serial3/0/0]fr map ip 10.0.123.3 201
After the mapping has been configured between IP addresses and PVCs, check the IP
address-PVC mapping tables on R2 and R3 and detect network connectivity.
<R3>display fr lmi-info inter Serial 1/0/0
Frame relay LMI statistics for interface Serial1/0/0 (DTE, Q933)
T391DTE = 10 (hold timer 10)
N391DTE = 6, N392DTE = 3, N393DTE = 4
out status enquiry = 326, in status = 324
status timeout = 0, discarded messages = 0
<R3>ping 10.0.2.2
PING 10.0.2.2: 56 data bytes, press CTRL_C to break
Reply from 10.0.2.2: bytes=56 Sequence=1 ttl=254 time=118 ms
Delete the RIP configurations referenced in step 2 and the frame relay mapping
between R2 and R3 that was established during step 3.
[R1]undo rip 1
Warning: The RIP process will be deleted. Continue?[Y/N]y
After the basic parameters are set, OSPF cannot establish neighbor adjacencies.
When using frame relay for data link layer encapsulation, OSPF will set the network
type to NBMA by default. As a result, OSPF does not support broadcasts, and
therefore cannot automatically discover neighbors.
While R3 is the DR, R2 is unable to establish a full adjacency with the DR since R3 is
not reachable via the PVC between R2 and R1. Therefore the DR must be set on R1.
Additionally OSPF hello messages are unicast in an NBMA network. Peers must be
manually specified to allow hello packet forwarding.
[R1]ospf
[R2]ospf
[R2-ospf-1]peer 10.0.123.1
[R3]ospf
[R3-ospf-1]peer 10.0.123.1
Optionally the DR priority for R2 and R3 can be set to 0 to force their exemption
from any DR election.
If R1 is not the designated router, reset the ospf process on all routers using the
following command and reattempt the above display command.
Display the routing table to confirm that OSPF has been established over the frame
relay network.
Attempts to establish a connection between 10.0.2.2 and 10.0.3.3 when using the
NBMA network type will fail unless a virtual circuit (PVC) is established between R2
and R3. Alternatively the point-to-multipoint network type can be applied.
OSPF configuration can also use the point-to-multipoint OSPF network type over
frame relay networks. First remove the manual peering and change the network type
to point-to-multipoint.
[R1]ospf
[R1-ospf-1]undo peer 10.0.123.2
[R1-ospf-1]undo peer 10.0.123.3
[R2]ospf
[R2-ospf-1]undo peer 10.0.123.1
[R3]ospf
[R3-ospf-1]undo peer 10.0.123.1
After setting the OSPF network type, wait until the neighbor relationship is
established, then check the neighbor relationship and route information.
<R1>display ip routing-table
Route Flags: R - relay, D - download to fib
----------------------------------------------------------------------------
Routing Tables: Public
Destinations : 14 Routes : 14
<R2>display ip routing-table
Route Flags: R - relay, D - download to fib
----------------------------------------------------------------------------
Routing Tables: Public
Destinations : 14 Routes : 14
<R3>display ip routing-table
Route Flags: R - relay, D - download to fib
----------------------------------------------------------------------------
Routing Tables: Public
Destinations : 14 Routes : 14
Final Configuration
[R1]display current-configuration
[V200R007C00SPC600]
#
sysname R1
#
interface Serial2/0/0
link-protocol fr
undo fr inarp
fr map ip 10.0.123.2 102 broadcast
fr map ip 10.0.123.3 103 broadcast
ip address 10.0.123.1 255.255.255.0
ospf network-type p2mp
ospf dr-priority 255
#
interface LoopBack0
ip address 10.0.1.1 255.255.255.0
#
ospf 1 router-id 10.0.1.1
area 0.0.0.0
network 10.0.0.0 0.255.255.255
#
user-interface con 0
authentication-mode password
set authentication password cipher %$%$dD#}P<HzJ;Xs%X>hOkm!,.+Iq61QK`K6tI}cc-;k_o`C.+L,%$%
$
user-interface vty 0 4
#
return
[R2]display current-configuration
[V200R007C00SPC600]
#
sysname R2
[R3]display current-configuration
[V200R007C00SPC600]
#
sysname R3
#
interface Serial1/0/0
link-protocol fr
undo fr inarp
fr map ip 10.0.123.1 301 broadcast
ip address 10.0.123.3 255.255.255.0
ospf network-type p2mp
#
interface LoopBack0
ip address 10.0.3.3 255.255.255.0
#
ospf 1 router-id 10.0.3.3
area 0.0.0.0
network 10.0.0.0 0.255.255.255
#
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Topology
Scenario
The enterprise subscribes to a (typically high speed) DSL service from the service
provider over which WAN services are supported. R1 and R3 are enterprise edge
routers of different offices, and establish a connection to the service provider
through the PPPoE server (R2). The enterprise is required to establish a PPPoE dialer
on the edge routers to allow hosts in the local area network to access external
resources transparently via the service provider network over PPPoE.
Tasks
If you are starting this section with a non-configured device, begin here and then
<Huawei>system-view
Enter system view, return user view with Ctrl+Z.
[Huawei]sysname R2
<Huawei>system-view
Enter system view, return user view with Ctrl+Z.
[Huawei]sysname R3
Disable the serial interfaces to avoid routing over the frame relay network.
The PPPoE server is not part of the enterprise network, however it is required to
allow the enterprise edge routers R1 and R3 to be authenticated.
[R2]ip pool pool1
Info: It's successful to create an IP address pool.
[R2-ip-pool-pool1]network 119.84.111.0 mask 255.255.255.0
[R2-ip-pool-pool1]gateway-list 119.84.111.254
[R2-ip-pool-pool1]quit
[R2]interface Virtual-Template 1
[R2-Virtual-Template1]ppp authentication-mode chap
[R2-Virtual-Template1]ip address 119.84.111.254 255.255.255.0
[R2-Virtual-Template1]remote address pool pool1
[R2-Virtual-Template1]quit
Configure R1 as a PPPoE client, for which the dialer interface needs to be created,
and PPP authentication enabled. The PPP authenticated username and password
[R1]dialer-rule
[R1-dialer-rule]dialer-rule 1 ip permit
[R1-dialer-rule]quit
[R1]interface Dialer 1
[R1-Dialer1]dialer user user1
[R1-Dialer1]dialer-group 1
[R1-Dialer1]dialer bundle 1
[R1-Dialer1]ppp chap user huawei1
[R1-Dialer1]ppp chap password cipher huawei123
[R1-Dialer1]dialer timer idle 300
[R1-Dialer1]dialer queue-length 8
[R1-Dialer1]ip address ppp-negotiate
[R1-Dialer1]quit
Configure R3 as a PPPoE client, for which the dialer interface needs to be created,
and PPP authentication enabled. The PPP authenticated username and password
Execute the command display pppoe-server session all command to view the
Check the dialer interface of R1 and R3, and ensure both can obtain an IP address
Final Configuration
[R1]display current-configuration
[V200R007C00SPC600]
#
sysname R1
#
aaa
authentication-scheme default
authorization-scheme default
accounting-scheme default
domain default
domain default_admin
local-user admin password cipher %$%$=i~>Xp&aY+*2cEVcS-A23Uwe%$%$
local-user admin service-type http
local-user huawei password cipher %$%$B:%I)Io0H8)[%SB[idM3C/!#%$%$
local-user huawei service-type ppp
#
interface Dialer1
link-protocol ppp
ppp chap user huawei1
ppp chap password cipher %$%$A8E~UjX}@;bhCL*C4w#<%"Ba%$%$
ip address ppp-negotiate
dialer user user1
dialer bundle 1
dialer queue-length 8
dialer timer idle 300
dialer-group 1
#
interface GigabitEthernet0/0/0
pppoe-client dial-bundle-number 1
#
dialer-rule
dialer-rule 1 ip permit
#
[R2]dis current-configuration
[V200R007C00SPC600]
#
sysname R2
#
ip pool pool1
gateway-list 119.84.111.254
network 119.84.111.0 mask 255.255.255.0
#
aaa
authentication-scheme default
authorization-scheme default
accounting-scheme default
domain default
domain default_admin
local-user admin password cipher %$%$=i~>Xp&aY+*2cEVcS-A23Uwe%$%$
local-user admin service-type http
local-user huawei1 password cipher %$%$MjCY6,a82N4W`]F]3LMAKG9+%$%$
local-user huawei1 service-type ppp
local-user huawei2 password cipher %$%$Ctq55RX:]R,8Jc13{|,)KH!m%$%$
local-user huawei2 service-type ppp
#
interface Virtual-Template1
ppp authentication-mode chap
remote address pool pool1
ip address 119.84.111.254 255.255.255.0
#
interface GigabitEthernet0/0/0
pppoe-server bind Virtual-Template 1
#
return
[R3]display current-configuration
[V200R007C00SPC600]
#
sysname R3
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Topology
Figure 3.1 Filtering enterprise network data with Access Control Lists
Scenario
Assume that you are a network administrator of a company that has three networks
belonging to three sites. R2 is deployed at the border of the network for the main
site, while R1 and R3 are deployed at the boundary of the remaining sites. The
routers are interconnected over a private WAN connection. The company needs to
control the access of employees to telnet and FTP services. Only site R1 has
permission to access the telnet server in the main site. Only site R3 has permission to
Tasks
If you are starting this section with a non-configured device, begin here and then
move to step 3. For those continuing from previous labs, begin at step 2.
[Huawei]sysname R1
[Huawei]sysname R2
[Huawei]sysname R3
[Huawei]sysname S1
[S1]vlan 4
[S1-vlan4]quit
[S1]interface vlanif 4
[S1-Vlanif4]ip address 10.0.4.254 24
[Huawei]sysname S2
[S2]vlan 6
[S2-vlan6]quit
[S2]interface vlanif 6
[S2-Vlanif6]ip address 10.0.6.254 24
Remove the current network being advertised in OSPF, the PPPoE dialer interfaces,
as well as the PPPoE server virtual template configuration from R2.
[R1]ospf
[R1-ospf-1]area 0
[R1-ospf-1-area-0.0.0.0]undo network 10.0.0.0 0.255.255.255
[R1-ospf-1-area-0.0.0.0]quit
[R1-ospf-1]quit
[R1]undo ip route-static 0.0.0.0 0
[R1]interface GigabitEthernet 0/0/0
[R1-GigabitEthernet0/0/0]undo pppoe-client dial-bundle-number 1
[R1]interface Dialer 1
[R2]ospf
[R2-ospf-1]area 0
[R2-ospf-1-area-0.0.0.0]undo network 10.0.0.0 0.255.255.255
[R2-ospf-1-area-0.0.0.0]quit
[R2-ospf-1]quit
[R2]interface GigabitEthernet 0/0/0
[R2-GigabitEthernet0/0/0]undo pppoe-server bind
Warning:All PPPoE sessions on this interface will be deleted, continue?[Y/N]:y
[R2-GigabitEthernet0/0/0]quit
[R2]undo interface Virtual-Template 1
[R2]undo ip pool pool1
[R2]aaa
[R2-aaa]undo local-user huawei1
[R2-aaa]undo local-user huawei2
[R3]ospf
[R3-ospf-1]area 0
[R3-ospf-1-area-0.0.0.0]undo network 10.0.0.0 0.255.255.255
[R3-ospf-1-area-0.0.0.0]quit
[R3-ospf-1]quit
[R3]undo ip route-static 0.0.0.0 0
[R3]interface GigabitEthernet 0/0/0
[R3-GigabitEthernet0/0/0]undo pppoe-client dial-bundle-number 1
[R3-GigabitEthernet0/0/0]quit
[R3]interface Dialer 1
[R3-Dialer1]undo dialer user
[R3-Dialer1]quit
[R3]undo interface Dialer 1
[R3]dialer-rule
[R3-dialer-rule]undo dialer-rule 1
Establish VLAN trunks on S1 and S2. The port link type should already be configured
for interface GigabitEthernet 0/0/2 on S1.
Configure OSPF for R1, R2, and R3. Ensure that all are part of the same OSPF area
and advertise the networks that have been created.
[R1]ospf
[R1-ospf-1]area 0
[R1-ospf-1-area-0.0.0.0]network 10.0.13.0 0.0.0.255
[R2]ospf
[R2-ospf-1]area 0
[R2-ospf-1-area-0.0.0.0]network 10.0.13.0 0.0.0.255
[R3]ospf
[R3-ospf-1]area 0
[R3-ospf-1-area-0.0.0.0]network 10.0.13.0 0.0.0.255
Configure a static route on S1 and S2, the nexthop as the private network’s
gateway.
<R1>ping 10.0.4.254
PING 10.0.4.254: 56 data bytes, press CTRL_C to break
Reply from 10.0.4.254: bytes=56 Sequence=1 ttl=253 time=2 ms
Reply from 10.0.4.254: bytes=56 Sequence=2 ttl=253 time=10 ms
Reply from 10.0.4.254: bytes=56 Sequence=3 ttl=253 time=1 ms
Reply from 10.0.4.254: bytes=56 Sequence=4 ttl=253 time=2 ms
Reply from 10.0.4.254: bytes=56 Sequence=5 ttl=253 time=2 ms
<R1>ping 10.0.6.254
PING 10.0.6.254: 56 data bytes, press CTRL_C to break
Reply from 10.0.6.254: bytes=56 Sequence=1 ttl=253 time=10 ms
Reply from 10.0.6.254: bytes=56 Sequence=2 ttl=253 time=2 ms
Reply from 10.0.6.254: bytes=56 Sequence=3 ttl=253 time=2 ms
Reply from 10.0.6.254: bytes=56 Sequence=4 ttl=253 time=10 ms
Reply from 10.0.6.254: bytes=56 Sequence=5 ttl=253 time=2 ms
<R3>ping 10.0.4.254
PING 10.0.4.254: 56 data bytes, press CTRL_C to break
Reply from 10.0.4.254: bytes=56 Sequence=1 ttl=253 time=10 ms
Reply from 10.0.4.254: bytes=56 Sequence=2 ttl=253 time=2 ms
Reply from 10.0.4.254: bytes=56 Sequence=3 ttl=253 time=2 ms
Reply from 10.0.4.254: bytes=56 Sequence=4 ttl=253 time=10 ms
Reply from 10.0.4.254: bytes=56 Sequence=5 ttl=253 time=2 ms
<R3>ping 10.0.6.254
PING 10.0.6.254: 56 data bytes, press CTRL_C to break
Reply from 10.0.6.254: bytes=56 Sequence=1 ttl=253 time=10 ms
Reply from 10.0.6.254: bytes=56 Sequence=2 ttl=253 time=2 ms
Reply from 10.0.6.254: bytes=56 Sequence=3 ttl=253 time=2 ms
Reply from 10.0.6.254: bytes=56 Sequence=4 ttl=253 time=10 ms
Reply from 10.0.6.254: bytes=56 Sequence=5 ttl=253 time=2 ms
Configure an access control list on R2 to allow R1 to access the telnet server, and R3
to access the FTP server.
[R2]acl 3000
[R2-acl-adv-3000]rule 5 permit tcp source 10.0.13.1 0.0.0.0 destination 10.0.4.254 0.0.0.0
destination-port eq 23
[R2-acl-adv-3000]rule 10 permit tcp source 10.0.13.3 0.0.0.0 destination 10.0.6.254 0.0.0.0
destination-port range 20 21
[R2-acl-adv-3000]rule 15 permit ospf
[R2-acl-adv-3000]rule 20 deny ip source any
[R2-acl-adv-3000]quit
<R1>telnet 10.0.4.254
Press CTRL_] to quit telnet mode
Trying 10.0.4.254 ...
Connected to 10.0.4.254 ...
Login authentication
Password:
Info: The max number of VTY users is 5, and the number
of current VTY users on line is 1.
<S1>
<R1>ftp 10.0.6.254
Trying 10.0.6.254 ...
Press CTRL+K to abort
Error: Failed to connect to the remote host.
Note: The FTP connection may take a while to respond (approx 60 seconds).
<R3>telnet 10.0.4.254
Press CTRL_] to quit telnet mode
Trying 10.0.4.254 ...
Error: Can't connect to the remote host
<R3>ftp 10.0.6.254
Trying 10.0.6.254 ...
Press CTRL+K to abort
Connected to 10.0.6.254.
220 FTP service ready.
User(10.0.6.254:(none)):huawei
331 Password required for huawei.
Enter password:
230 User logged in.
[R3-ftp]
Note: The bye command can be used to close the FTP connection
FTP requires two ports to be defined in the access control list, why is this?
Should basic ACL and advanced ACL be deployed near the source network or target
network, and why?
Final Configuration
<R1>display current-configuration
<R2>display current-configuration
[V200R007C00SPC600]
#
sysname R2
#
acl number 3000
rule 5 permit tcp source 10.0.13.1 0 destination 10.0.4.254 0 destination-port eq telnet
rule 10 permit tcp source 10.0.13.3 0 destination 10.0.6.254 0 destination-port range ftp-data
ftp
rule 15 permit ospf
<R3>display current-configuration
[V200R007C00SPC600]
#
sysname R3
#
interface GigabitEthernet0/0/0
ip address 10.0.13.3 255.255.255.0
#
ospf 1 router-id 10.0.3.3
area 0.0.0.0
network 10.0.13.0 0.0.0.255
#
user-interface con 0
authentication-mode password
set authentication password cipher %$%$W|$)M5D}v@bY^gK\;>QR,.*d;8Mp>|+EU,:~D~8b59~..*g,%$%
<S1>display current-configuration
#
!Software Version V200R008C00SPC500
sysname S1
#
vlan batch 3 to 4
#
interface Vlanif4
ip address 10.0.4.254 255.255.255.0
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk pvid vlan 4
port trunk allow-pass vlan 2 to 4094
#
ip route-static 0.0.0.0 0.0.0.0 10.0.4.2
#
user-interface con 0
user-interface vty 0 4
authentication-mode password
set authentication password cipher N`C55QK<`=/Q=^Q`MAF4<1!!
Protocol inbound all
#
return
<S2>dis current-configuration
#
!Software Version V200R008C00SPC500
sysname S2
#
FTP server enable
#
vlan batch 6
#
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Scenario
Tasks
If you are starting this section with a non-configured device, begin here and then
move to step 3. For those continuing from previous labs, begin at step 2.
[Huawei]sysname R3
[R3]interface GigabitEthernet0/0/2
[R3-GigabitEthernet0/0/2]ip address 10.0.6.3 24
[Huawei]sysname S1
[S1]vlan 4
[S1-vlan3]quit
[S1]interface vlanif 4
[S1-Vlanif4]ip address 10.0.4.254 24
[S1-Vlanif4]quit
[Huawei]sysname S2
[S2]vlan 6
[S2-vlan6]quit
[S2]interface vlanif 6
[S2-Vlanif6]ip address 10.0.6.254 24
[S2-Vlanif6]quit
[R2]undo ospf 1
Warning: The OSPF process will be deleted. Continue? [Y/N]:y
[R3-GigabitEthernet0/0/0]undo ip address
[R3]interface GigabitEthernet 0/0/2
[R3-GigabitEthernet0/0/2]undo shutdown
[R3]undo ospf 1
[R1]interface GigabitEthernet0/0/0
[R1-GigabitEthernet0/0/0]ip address 119.84.111.1 24
[R3]interface GigabitEthernet0/0/0
[R3-GigabitEthernet0/0/0]ip address 119.84.111.3 24
<R1>ping 119.84.111.3
PING 119.84.111.3: 56 data bytes, press CTRL_C to break
Reply from 119.84.111.3: bytes=56 Sequence=1 ttl=255 time=1 ms
Reply from 119.84.111.3: bytes=56 Sequence=2 ttl=255 time=10 ms
Reply from 119.84.111.3: bytes=56 Sequence=3 ttl=255 time=1 ms
Reply from 119.84.111.3: bytes=56 Sequence=4 ttl=255 time=1 ms
Reply from 119.84.111.3: bytes=56 Sequence=5 ttl=255 time=10 ms
Configure an advanced ACL on R1 and select the data flow with the source of S1, the
destination of R3, and destined for the telnet service port.
[R1]acl 3000
[R1-acl-adv-3000]rule 5 permit tcp source 10.0.4.254 0.0.0.0 destination 119.84.111.3
0.0.0.0 destination-port eq 23
[R1-acl-adv-3000]rule 10 permit ip source 10.0.4.0 0.0.0.255 destination any
[R1-acl-adv-3000]rule 15 deny ip
Configure a basic ACL on R3 and select the data flow whose source IP address is
10.0.6.0/24.
[R3]acl 2000
[R3-acl-basic-2000]rule permit source 10.0.6.0 0.0.0.255
Configure static route on S1 and S2,the nexthop as the private network’s gateway.
[S1]ip route-static 0.0.0.0 0.0.0.0 10.0.4.1
[S2]ip route-static 0.0.0.0 0.0.0.0 10.0.6.3
Test connectivity to the gateway of the remote peer from the internal network.
<S1>ping 119.84.111.3
PING 119.84.111.3: 56 data bytes, press CTRL_C to break
Request time out
Reply from 119.84.111.3: bytes=56 Sequence=2 ttl=254 time=1 ms
Reply from 119.84.111.3: bytes=56 Sequence=3 ttl=254 time=1 ms
Reply from 119.84.111.3: bytes=56 Sequence=4 ttl=254 time=1 ms
Reply from 119.84.111.3: bytes=56 Sequence=5 ttl=254 time=1 ms
Login authentication
Password:
<R3>
Do not exit the telnet session, instead open a second session window to R1 and view
the results of the ACL and NAT session translation.
Protocol : ICMP(1)
SrcAddr Vpn : 10.0.4.254
DestAddr Vpn : 119.84.111.3
Type Code IcmpId : 8 0 44003
NAT-Info
New SrcAddr : 119.84.111.242
New DestAddr : ----
New IcmpId : 10247
Protocol : TCP(6)
SrcAddr Port Vpn : 10.0.4.254 49646
DestAddr Port Vpn : 119.84.111.3 23
NAT-Info
New SrcAddr : 119.84.111.242
New SrcPort : 10249
New DestAddr : ----
New DestPort : ----
Total : 2
The ICMP session has a lifetime of only 20 seconds and therefore may not appear to
Configure easyIP on the Gigabit Ethernet 0/0/0 interface of R3, associating the
easyIP configuration with ACL 2000 that had been configured earlier.
<R1>display current-configuration
[V200R007C00SPC600]
#
sysname R1
#
firewall-nat session icmp aging-time 300
#
acl number 3000
rule 5 permit tcp source 10.0.4.254 0 destination 119.84.111.3 0 destination-port eq telnet
rule 10 permit ip source 10.0.4.0 0.0.0.255
rule 15 deny ip
#
nat address-group 1 119.84.111.240 119.84.111.243
#
interface GigabitEthernet0/0/0
ip address 119.84.111.1 255.255.255.0
nat outbound 3000 address-group 1
#
interface GigabitEthernet0/0/1
ip address 10.0.4.1 255.255.255.0
#
user-interface con 0
authentication-mode password
set authentication password cipher %$%$dD#}P<HzJ;Xs%X>hOkm!,.+Iq61QK`K6tI}cc-;k_o`C.+L,%$%
$
user-interface vty 0 4
#
return
<R3>display current-configuration
[V200R007C00SPC600]
#
sysname R3
#
telnet server enable
#
acl number 2000
rule 5 permit source 10.0.6.0 0.0.0.255
#
<S1>display current-configuration
#
!Software Version V200R008C00SPC500
sysname S1
#
vlan batch 4
#
interface Vlanif4
ip address 10.0.4.254 255.255.255.0
#
interface GigabitEthernet0/0/1
port link-type trunk
port trunk pvid vlan 4
port trunk allow-pass vlan 2 to 4094
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk pvid vlan 4
port trunk allow-pass vlan 2 to 4094
#
interface GigabitEthernet0/0/14
shutdown
#
<S2>display current-configuration
#
!Software Version V200R008C00SPC500
sysname S2
#
vlan batch 6
#
interface Vlanif6
ip address 10.0.6.254 255.255.255.0
#
interface GigabitEthernet0/0/2
port link-type trunk
port trunk pvid vlan 6
port trunk allow-pass vlan 2 to 4094
#
interface GigabitEthernet0/0/3
port link-type trunk
port trunk pvid vlan 6
port trunk allow-pass vlan 2 to 4094
#
interface GigabitEthernet0/0/23
shutdown
#
ip route-static 0.0.0.0 0.0.0.0 10.0.6.3
#
user-interface con 0
user-interface vty 0 4
#
return
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Topology
Scenario
R1 and R3 have been deployed on the network and are to provide remote
authentication services using AAA. The company requires that both routers are
made part of the huawei domain and that the telnet service is made available to
users, with limited privileges given once authenticated.
If you are starting this section with a non-configured device, begin here and then
move to step 3. For those continuing from previous labs, begin at step 2.
[Huawei]sysname R1
[R1]interface GigabitEthernet0/0/0
[R1-GigabitEthernet0/0/0]ip address 119.84.111.1 24
[Huawei]sysname R3
[R3]inter GigabitEthernet0/0/0
[R3-GigabitEthernet0/0/0]ip address 119.84.111.3 24
Remove the previous NAT and ACL configuration from R1 and R3.
Configure the domain huawei on R1, then create a user and apply the user to this
domain.
[R1]user-interface vty 0 4
[R1-ui-vty0-4]authentication-mode aaa
Login authentication
Username:user1@huawei
Password:
<R1>system-view
^
Error: Unrecognized command found at '^' position.
<R1>quit
Operations are restricted as user privileges are limited to privilege level 0 for
user1@huawei.
[R3]aaa
[R3-aaa]authentication-scheme auth1
Info: Create a new authentication scheme.
[R3-aaa-authen-auth1]authentication-mode local
[R3-aaa-authen-auth1]quit
[R3-aaa]authorization-scheme auth2
Info: Create a new authorization scheme.
[R3-aaa-author-auth2]authorization-mode local
[R3-aaa-author-auth2]quit
Configure the domain huawei on R3, then create a user and apply the user to this
domain.
[R3]user-interface vty 0 4
[R3-ui-vty0-4]authentication-mode aaa
<R1>telnet 119.84.111.3
Press CTRL_] to quit telnet mode
Trying 119.84.111.1 ...
Connected to 119.84.111.1 ...
Login authentication
Username:user3@huawei
Password:
<R3>system-view
^
Error: Unrecognized command found at '^' position.
<R3>
Operations are restricted as user privileges are set to privilege level 0 for
user3@huawei.
Domain-name : huawei
Domain-name : huawei
Domain-state : Active
Authentication-scheme-name : auth1
Accounting-scheme-name : default
Authorization-scheme-name : auth2
Service-scheme-name : -
RADIUS-server-template : -
HWTACACS-server-template : -
User-group : -
Final Configuration
<R1>display current-configuration
[V200R007C00SPC600]
#
sysname R1
#
telnet server enable
#
aaa
authentication-scheme default
authentication-scheme auth1
authorization-scheme default
authorization-scheme auth2
accounting-scheme default
domain default
domain default_admin
domain huawei
authentication-scheme auth1
authorization-scheme auth2
local-user admin password cipher %$%$=i~>Xp&aY+*2cEVcS-A23Uwe%$%$
local-user admin service-type http
local-user huawei password cipher %$%$B:%I)Io0H8)[%SB[idM3C/!#%$%$
local-user huawei service-type ppp
local-user user1@huawei password cipher %$%$^L*5IP'0^A!;R)R*L=LFcXgv%$%$
local-user user1@huawei privilege level 0
local-user user1@huawei service-type telnet
#
interface GigabitEthernet0/0/0
ip address 119.84.111.1 255.255.255.0
nat outbound 3000 address-group 1 //may remain from previous labs
#
user-interface con 0
authentication-mode password
set authentication password cipher %$%$dD#}P<HzJ;Xs%X>hOkm!,.+Iq61QK`K6tI}cc-;k_o`C.+L,%$%
$
user-interface vty 0 4
<R3>dis current-configuration
[V200R007C00SPC600]
#
sysname R3
#
telnet server enable
#
aaa
authentication-scheme default
authentication-scheme auth1
authorization-scheme default
authorization-scheme auth2
accounting-scheme default
domain default
domain default_admin
domain huawei
authentication-scheme auth1
authorization-scheme auth2
local-user admin password cipher %$%$=i~>Xp&aY+*2cEVcS-A23Uwe%$%$
local-user admin service-type http
local-user huawei password cipher %$%$fZsyUk1=O=>:L4'ytgR~D*Im%$%$
local-user huawei service-type ppp
local-user user3@huawei password cipher %$%$WQt.;bEsR<8fz3LCiPY,che_%$%$
local-user user3@huawei privilege level 0
local-user user3@huawei service-type telnet
#
interface GigabitEthernet0/0/0
ip address 119.84.111.3 255.255.255.0
nat outbound 2000 //may remain from previous labs
#
user-interface con 0
authentication-mode password
set authentication password cipher %$%$W|$)M5D}v@bY^gK\;>QR,.*d;8Mp>|+EU,:~D~8b59~..*g,%$%
$
user-interface vty 0 4
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Topology
Scenario
In the interests of protecting both the integrity and confidentiality of company data,
it is required that the communication between the offices of the enterprise secure
specific private data as it is transmitted over the public network infrastructure. As the
network administrator of the company, the task has been assigned to implement
IPSec VPN solutions between the HQ edge router (R1) and the branch office (R3).
Currently only select departments within the HQ require secured communication
over the public network (R2). The administrator should establish IPSec using tunnel
mode between the two offices for all traffic originating from the department.
<Huawei>system-view
[Huawei]sysname R2
[R2]interface Serial 1/0/0
[R2-Serial1/0/0]ip address 10.0.12.2 24
[R2-Serial1/0/0]interface serial 2/0/0
[R2-Serial2/0/0]ip address 10.0.23.2 24
[R2-Serial2/0/0]interface loopback 0
[R2-LoopBack0]ip address 10.0.2.2 24
<Huawei>system-view
[Huawei]sysname R3
[R3]interface Serial 2/0/0
[R3-Serial2/0/0]ip address 10.0.23.3 24
[R3-Serial2/0/0]interface loopback 0
[R3-LoopBack0]ip address 10.0.3.3 24
[R1-LoopBack0]interface loopback 1
[R1-LoopBack1]ip address 10.0.11.11 24
[R3-LoopBack0]interface loopback 1
[R3-LoopBack1]ip address 10.0.33.33 24
Use the IP address of Loopback 0 as the router ID, use the default OSPF process (1),
and specify the public network segments 10.0.12.0/24, and 10.0.23.0/24 as part of
OSPF area 0.
[R1]ospf router-id 10.0.1.1
[R1-ospf-1]area 0
[R1-ospf-1-area-0.0.0.0]network 10.0.12.0 0.0.0.255
[R1-ospf-1-area-0.0.0.0]network 10.0.1.0 0.0.0.255
[R1-ospf-1-area-0.0.0.0]network 10.0.11.0 0.0.0.255
<R1>display ip routing-table
Route Flags: R - relay, D - download to fib
----------------------------------------------------------------------------
Routing Tables: Public
Destinations : 17 Routes : 17
If the baudrate is maintained as 128000 from lab 6-1, the OSPF cost will be set as
shown, and thus may vary due to the the metric calculation used by OSPF.
An advanced ACL is created to identify interesting traffic for which the IPSec VPN will
be applied. The advanced ACL is capable of filtering based on specific parameters for
selective traffic filtering.
[R1]acl 3001
[R1-acl-adv-3001]rule 5 permit ip source 10.0.1.0 0.0.0.255 destination 10.0.3.0 0.0.0.255
[R3]acl 3001
[R3-acl-adv-3001]rule 5 permit ip source 10.0.3.0 0.0.0.255 destination 10.0.1.0 0.0.0.255
Create an IPSec proposal and enter the IPSec proposal view to specify the security
Number of proposals: 1
Number of proposals: 1
Create an IPSec policy and define the parameters for establishing the SA.
[R1]ipsec policy P1 10 manual
[R1-ipsec-policy-manual-P1-10]security acl 3001
[R1-ipsec-policy-manual-P1-10]proposal tran1
[R1-ipsec-policy-manual-P1-10]tunnel remote 10.0.23.3
[R1-ipsec-policy-manual-P1-10]tunnel local 10.0.12.1
[R1-ipsec-policy-manual-P1-10]sa spi outbound esp 54321
[R1-ipsec-policy-manual-P1-10]sa spi inbound esp 12345
===========================================
IPSec policy group: "P1"
Using interface:
===========================================
Sequence number: 10
Security data flow: 3001
Tunnel local address: 10.0.12.1
Tunnel remote address: 10.0.23.3
Qos pre-classify: Disable
Proposal name:tran1
Inbound AH setting:
AH SPI:
AH string-key:
AH authentication hex key:
Inbound ESP setting:
ESP SPI: 12345 (0x3039)
ESP string-key: huawei
ESP encryption hex key:
ESP authentication hex key:
Outbound AH setting:
AH SPI:
AH string-key:
AH authentication hex key:
Outbound ESP setting:
ESP SPI: 54321 (0xd431)
===========================================
IPSec policy group: "P1"
Using interface:
===========================================
Sequence number: 10
Security data flow: 3001
Tunnel local address: 10.0.23.3
Tunnel remote address: 10.0.12.1
Qos pre-classify: Disable
Proposal name:tran1
Inbound AH setting:
AH SPI:
AH string-key:
AH authentication hex key:
Inbound ESP setting:
ESP SPI: 54321 (0xd431)
ESP string-key: huawei
ESP encryption hex key:
ESP authentication hex key:
Outbound AH setting:
AH SPI:
AH string-key:
AH authentication hex key:
Outbound ESP setting:
ESP SPI: 12345 (0x3039)
ESP string-key: huawei
ESP encryption hex key:
ESP authentication hex key:
Apply the policy to the physical interface upon which traffic will be subjected to
IPSec processing.
[R1]interface Serial 1/0/0
[R1-Serial1/0/0]ipsec policy P1
Observe and verity that non-interesting traffic bypasses the IPSec processing.
<R1>ping -a 10.0.11.11 10.0.33.33
PING 10.0.33.33: 56 data bytes, press CTRL_C to break
Reply from 10.0.33.33: bytes=56 Sequence=1 ttl=254 time=60 ms
Reply from 10.0.33.33: bytes=56 Sequence=2 ttl=254 time=50 ms
Reply from 10.0.33.33: bytes=56 Sequence=3 ttl=254 time=50 ms
Reply from 10.0.33.33: bytes=56 Sequence=4 ttl=254 time=60 ms
Reply from 10.0.33.33: bytes=56 Sequence=5 ttl=254 time=50 ms
--- 10.0.33.33 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 50/54/60 ms
Final Configuration
<R1>display current-configuration
[V200R007C00SPC600]
#
sysname R1
#
acl number 3001
rule 5 permit ip source 10.0.1.0 0.0.0.255 destination 10.0.3.0 0.0.0.255
<R3>display current-configuration
[V200R007C00SPC600]
#
sysname R3
#
acl number 3001
rule 5 permit ip source 10.0.3.0 0.0.0.255 destination 10.0.1.0 0.0.0.255
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Topology
Scenario
A requirement has been made to allow networks from other offices to be advertised
to the HQ. Following the implementation of IPSec VPN solutions, it was discovered
that this was not possible. After some consultation the administrator has been
advised to implement a GRE solution over the existing IPSec network to enable the
enterprise offices to truly operate as a single administrative domain.
Tasks
Note: It is a prerequisite that lab 3-4 be completed before attempting this lab.
Reconfigure the access control list establish GRE encapsulation over IPSec.
[R1]acl 3001
[R1-acl-adv-3001]rule 5 permit gre source 10.0.12.1 0 destination 10.0.23.3 0
[R3]acl 3001
[R3-acl-adv-3001]rule 5 permit gre source 10.0.23.3 0 destination 10.0.12.1 0
Create a tunnel interface and specify GRE as the encapsulation type. Set the tunnel
source address or source interface, and set the tunnel destination address.
[R1]interface Tunnel 0/0/1
[R1-Tunnel0/0/1]ip address 100.1.1.1 24
[R1-Tunnel0/0/1]tunnel-protocol gre
[R1-Tunnel0/0/1]source 10.0.12.1
[R1-Tunnel0/0/1]destination 10.0.23.3
Add the tunnel interface network to OSPF 1 process, and create a second OSPF
instance of the link state database (process 2) for the 10.0.12.0 and 10.0.23.0
networks, be sure to remove these networks from OSPF 1.
[R1]ospf 1
[R1-ospf-1]area 0
[R1-ospf-1-area-0.0.0.0]network 100.1.1.0 0.0.0.255
[R1-ospf-1-area-0.0.0.0]undo network 10.0.12.0 0.0.0.255
[R3]ospf 1
[R3-ospf-1]area 0
[R3-ospf-1-area-0.0.0.0]network 100.1.1.0 0.0.0.255
[R3-ospf-1-area-0.0.0.0]undo network 10.0.23.0 0.0.0.255
[R3]ospf 2 router-id 10.0.3.3
[R3-ospf-2]area 0
[R3-ospf-2-area-0.0.0.0]network 10.0.23.0 0.0.0.255
OSPF LSDB are significant only to the local router, therefore allowing routes from
OSPF LSDB 2 of R1 and R3 to reach OSPF LSDB 1 of R2.
Run the display interface Tunnel 0/0/1 command to verify the configuration.
<R1>display interface Tunnel 0/0/1
Tunnel0/0/1 current state : UP
Line protocol current state : UP
Last line protocol up time : 2016-03-17 17:10:16
Description:HUAWEI, AR Series, Tunnel0/0/1 Interface
Route Port,The Maximum Transmit Unit is 1500
Internet Address is 100.1.1.1/24
Encapsulation is TUNNEL, loopback not set
Tunnel source 10.0.12.1 (Serial1/0/0), destination 10.0.23.3
Tunnel protocol/transport GRE/IP, key disabled
keepalive disabled
Checksumming of packets disabled
Current system time: 2016-03-17 17:35:39
Last 300 seconds input rate 0 bytes/sec, 0 packets/sec
Last 300 seconds output rate 9 bytes/sec, 0 packets/sec
Realtime 0 seconds input rate 0 bytes/sec, 0 packets/sec
Realtime 0 seconds output rate 0 bytes/sec, 0 packets/sec
0 packets input, 0 bytes, 0 drops
145 packets output, 14320 bytes, 0 drops
Input bandwidth utilization : --
Output bandwidth utilization : --
Step 4 Verify that the routes are being carried via GRE
Run the display ip routing-table command to check the IPv4 routing table.
<R1>display ip routing-table
Route Flags: R - relay, D - download to fib
----------------------------------------------------------------------------
Routing Tables: Public
Destinations : 21 Routes : 21
<R3>display ip routing-table
Route Flags: R - relay, D - download to fib
----------------------------------------------------------------------------
Routing Tables: Public
Destinations : 21 Routes : 21
After a GRE tunnel is set up, the router can exchange OSPF packets through the GRE
GRE encapsulates all OSPF traffic including the hello packets over IPSec, the gradual
increment of the IPSec esp statistics verifies this.
Final Configuration
<R1>display current-configuration
[V200R007C00SPC600]
#
sysname R1
#
acl number 3001
rule 5 permit gre source 10.0.12.1 0 destination 10.0.23.3 0
#
ipsec proposal tran1
esp authentication-algorithm sha1
esp encryption-algorithm 3des
#
<R2>display current-configuration
[V200R007C00SPC600]
#
sysname R2
#
interface Serial1/0/0
link-protocol ppp
ppp pap local-user huawei password cipher %$%$u[hr6d<JVHR@->T7xr1<$.iv%$%$
ip address 10.0.12.2 255.255.255.0
#
interface Serial2/0/0
link-protocol ppp
ppp chap user huawei
ppp chap password cipher %$%$e{5h)gh"/Uz0mUC%vEx3$4<m%$%$
ip address 10.0.23.2 255.255.255.0
#
interface LoopBack0
ip address 10.0.2.2 255.255.255.0
#
ospf 1 router-id 10.0.2.2
area 0.0.0.0
network 10.0.2.0 0.0.0.255
network 10.0.12.0 0.0.0.255
network 10.0.23.0 0.0.0.255
#
user-interface con 0
authentication-mode password
set authentication password cipher %$%$|nRPL^hr2IXi7LHDID!/,.*%.8%h;3:,hXO2dk#ikaWI.*(,%$%
$
user-interface vty 0 4
#
return
Learning Objectives
As a result of this lab section, you should achieve the following tasks:
Topology
In line with plans for deployment of solutions for next generation networks, it has
been decided that the enterprise network should implement an IPv6 design to the
existing infrastructure. As the administrator you have been tasked with the job of
implementing the addressing scheme and routing for IPv6, as well as providing
stateful addressing solutions for IPv6.
Tasks
If you are starting this section with a non-configured device, begin here and then
move to step 2. For those continuing from previous labs, begin at step 2.
<huawei>system-view
[huawei]sysname R1
<huawei>system-view
[huawei]sysname R2
<huawei>system-view
[huawei]sysname R3
Establish IPv6 global unicast addressing on the loopback interfaces and manually
configure link local addressing on interface Gigabit Ethernet 0/0/0 of all routers.
[R1]ipv6
[R1]interface loopback 0
[R1-LoopBack0]ipv6 enable
[R1-LoopBack0]ipv6 address 2001:1::A 64
[R1]interface GigabitEthernet 0/0/0
[R1-GigabitEthernet0/0/0]ipv6 enable
[R1-GigabitEthernet0/0/0]ipv6 address fe80::1 link-local
[R3]ipv6
[R3]interface loopback 0
[R3-LoopBack0]ipv6 enable
[R3-LoopBack0]ipv6 address 2001:3::C 64
[R3]interface GigabitEthernet 0/0/0
[R3-GigabitEthernet0/0/0]ipv6 enable
[R3-GigabitEthernet0/0/0]ipv6 address fe80::3 link-local
IPv6 interfaces become part of various multicast groups for support of stateless
address auto-configuration (SLAAC). The Network Discovery (ND) Duplicate Address
Detection (DAD) verifies the link local address is unique.
Enable the OSPFv3 process and specify its router ID on R1, R2 and R3. OSPFv3 must
then be enabled on the interface.
[R1]ospfv3 1
[R1-ospfv3-1]router-id 1.1.1.1
[R1-ospfv3-1]quit
[R1]interface GigabitEthernet 0/0/0
[R1-GigabitEthernet0/0/0]ospfv3 1 area 0
[R1-GigabitEthernet0/0/0]quit
[R1]interface loopback 0
[R1-LoopBack0]ospfv3 1 area 0
[R2]ospfv3 1
[R2-ospfv3-1]router-id 2.2.2.2
[R2-ospfv3-1]quit
[R2]interface GigabitEthernet 0/0/0
[R2-GigabitEthernet0/0/0]ospfv3 1 area 0
[R2-GigabitEthernet0/0/0]quit
[R2]interface loopback 0
[R2-LoopBack0]ospfv3 1 area 0
[R3]ospfv3 1
[R3-ospfv3-1]router-id 3.3.3.3
[R3-ospfv3-1]quit
[R3]interface GigabitEthernet 0/0/0
[R3-GigabitEthernet0/0/0]ospfv3 1 area 0
[R3-GigabitEthernet0/0/0]quit
[R3]interface loopback 0
[R3-LoopBack0]ospfv3 1 area 0
Run the display ospfv3 peer command on R1 and R3 to verify the OSPFv3 peering
If 1.1.1.1 is not currently the DR, the following command can be used to reset the
OSPFv3 process.
Test connectivity to the peer link local address and the global unicast address of
interface LoopBack 0.
Enable the DHCPv6 Server function on R2 so that devices can be assigned IPv6
addresses using DHCPv6.
[R2]dhcp enable
[R2] dhcpv6 duid ll
Warning: The DHCP unique identifier should be globally-unique and stable. Are you sure to change
it? [Y/N]y
[R2]dhcpv6 pool pool1
[R2-dhcpv6-pool-pool1]address prefix 2001:FACE::/64
[R2-dhcpv6-pool-pool1]dns-server 2001:444e:5300::1
[R2-dhcpv6-pool-pool1]excluded-address 2001:FACE::1
[R2-dhcpv6-pool-pool1]quit
[R1]dhcp enable
[R1] dhcpv6 duid ll
Warning: The DHCP unique identifier should be globally-unique and stable. Are you sure to change
it? [Y/N]y
[R1]interface Gigabitethernet 0/0/0
[R1-GigabitEthernet0/0/0]ipv6 address auto dhcp
[R3]dhcp enable
[R3] dhcpv6 duid ll
Warning: The DHCP unique identifier should be globally-unique and stable. Are you sure to change
it? [Y/N]y
[R3]interface GigabitEthernet 0/0/0
[R3-GigabitEthernet0/0/0]ipv6 address auto dhcp
Run the display dhcpv6 pool command on R2 to check information about the
DHCPv6 address pool.
Run the display ipv6 interface brief command on R1 and R3 to check the IPv6
address information.
Final Configuration
<R1>display current-configuration
[V200R007C00SPC600]
#
sysname R1
#
ipv6
#
dhcp enable
#
ospfv3 1
router-id 1.1.1.1
#
interface GigabitEthernet0/0/0
ipv6 enable
ip address 10.0.13.1 255.255.255.0
ipv6 address FE80::1 link-local
ospfv3 1 area 0.0.0.0
ipv6 address auto dhcp
#
interface LoopBack0
ipv6 enable
ip address 10.0.1.1 255.255.255.0
ipv6 address 2001:1::A/64
<R2>display current-configuration
[V200R007C00SPC600]
#
sysname R2
#
ipv6
#
dhcp enable
#
dhcpv6 pool pool1
address prefix 2001:FACE::/64
excluded-address 2001:FACE::1
dns-server 2001:444E:5300::1
#
ospfv3 1
router-id 2.2.2.2
#
interface GigabitEthernet0/0/0
ipv6 enable
ip address 10.0.13.2 255.255.255.0
ipv6 address 2001:FACE::1/64
ipv6 address FE80::2 link-local
ospfv3 1 area 0.0.0.0
traffic-filter inbound acl 3000
dhcpv6 server pool1
#
interface LoopBack0
ipv6 enable
ip address 10.0.2.2 255.255.255.0
<R3>display current-configuration
[V200R007C00SPC600]
#
sysname R3
#
ipv6
#
dhcp enable
#
ospfv3 1
router-id 3.3.3.3
#
interface GigabitEthernet0/0/0
ipv6 enable
ip address 10.0.13.3 255.255.255.0
ipv6 address FE80::3 link-local
ospfv3 1 area 0.0.0.0
ipv6 address auto dhcp
#
interface LoopBack0
ipv6 enable
ip address 10.0.3.3 255.255.255.0
ipv6 address 2001:3::C/64
ospfv3 1 area 0.0.0.0
#
user-interface con 0
authentication-mode password
set authentication password cipher %$%$W|$)M5D}v@bY^gK\;>QR,.*d;8Mp>|+EU,:~D~8b59~..*g,%$%