H3C Technologies H3C S12500 Series Switches - Manual (Page 292)

276
* Copyright (c) 2004-2011 Hangzhou H3C Tech. Co., Ltd. All rights reserved. *
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
*********************************************************************************
**********************
# Telnet to Switch C (1.1.3.2/24) from Switch A. The operation fails.
telnet 1.1.3.2
Trying 1.1.3.2 ...
Press CTRL+K to abort
Can't connect to the remote host!
# Ping Switch C (1.1.3.2/24) from Switch A. The operation succeeds.
ping 1.1.3.2
PING 1.1.3.2: 56 data bytes, press CTRL_C to break
Reply from 1.1.3.2: bytes=56 Sequence=1 ttl=255 time=2 ms
Reply from 1.1.3.2: bytes=56 Sequence=2 ttl=255 time=1 ms
Reply from 1.1.3.2: bytes=56 Sequence=3 ttl=255 time=1 ms
Reply from 1.1.3.2: bytes=56 Sequence=4 ttl=255 time=1 ms
Reply from 1.1.3.2: bytes=56 Sequence=5 ttl=255 time=1 ms
--- 1.1.3.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 1/1/2 ms
Telnet uses TCP, and ping uses ICMP. The preceding results show that all TCP packets of Switch A
are forwarded to next hop 1.1.2.2, and other packets are forwarded through VLAN-interface 20.
The PBR configuration is effective.
Configuring interface PBR based on packet type
Network requirements
As shown in Figure 97 , configure PBR on Switch A, so all TCP packets arriving on VLAN-interface 10 are
forwarded to next hop 1.1.2.2, and other packets are forwarded according to the routing table.
Switch A is directly connected to Switch B and Switch C. Switch B and Switch C are unreachable to each
other.