In this case, we talked about the one-arm routing feature, he can solve the communication between the VLANs, but if there is more than one VLAN in a route data transfer
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/73/2E/wKioL1X3iXThy8kUAADWZdQxVhY390.jpg "title=" capture. PNG "alt=" Wkiol1x3ixthy8kuaadwzdqxvhy390.jpg "/>
The increase of VLAN leads to the increase of data volume, and the path between router and switch becomes the bottleneck of the whole network.
650) this.width=650; "src="/e/u261/themes/default/images/spacer.gif "alt=" * "style=" Background:url ("/e/u261/lang/ Zh-cn/images/localimage.png ") no-repeat center;border:1px solid #ddd;/> one-arm routing defect
1, 650) this.width=650; "src="/e/u261/themes/default/images/spacer.gif "alt=" * "style=" Background:url ("/e/u261/lang /zh-cn/images/localimage.png ") no-repeat center;border:1px solid #ddd;"/>"one-arm" network backbone link, easy to form network bottleneck
2, 650) this.width=650; "src="/e/u261/themes/default/images/spacer.gif "alt=" * "style=" Background:url ("/e/u261/lang /zh-cn/images/localimage.png ") no-repeat center;border:1px solid #ddd;"/> sub-interface still relies on the physical interface, the application is not flexible
3, 650) this.width=650; "src="/e/u261/themes/default/images/spacer.gif "alt=" * "style=" Background:url ("/e/u261/lang /zh-cn/images/localimage.png ") no-repeat center;border:1px solid #ddd;"/>inter-VLAN forwarding requires a view of the routing table and a serious waste of equipment resources
In order to solve this problem, we will use three layer switching technology to realize the communication between the VLAN, the three layer switch can do two-layer switching and three-layer forwarding.
We also use an experiment to look at the specific configuration implementation process
Experiment:
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/73/2E/wKioL1X3jNLCsPNbAAGmkKy_3H0742.jpg "title=" 1.PNG " alt= "Wkiol1x3jnlcspnbaagmkky_3h0742.jpg"/>
Description: sw3l is a layer three switch, sw2l is a two layer switch,
Configuration steps:
Configuration of SW3;
Enable
VLAN data
VLAN 1
VLAN 2
VLAN 3 enters VLAN configuration mode creation Vlan1 2 3
Exit
Config
int VLAN 1
IP Add 192.168.1.1 255.255.255.0 (1.0 network Segment Gateway)
No sh exit VLAN configuration mode Enter global configuration Enter VLAN 1 virtual interface Configure IP and subnets and enable
Exit
int VLAN 2
IP add 192.168.2.1 255.255.255.0 (2.0 network segment Gateway)
No sh enters VLAN 2 virtual interface to configure IP and subnets and enable
Exit
int VLAN 3
IP Add 192.168.3.1 255.255.255.0 (3.0 network segment Gateway)
No sh enters VLAN 3 virtual interface to configure IP and subnets and enable
The SW3 configuration is basically complete.
Configuration of the SW2:
Enable
VLAN data
VLAN 1
VLAN 2
Valn 3 Creating VLANs 1 2 3
Exit
Config
int F0/2
Switch Access VLAN 2
Exit
int F0/3
Switch Access VLAN 3 enters F0/2 F0/3 interface configuration mode respectively, F0/2 joins vlan2 F0/3 add vlan3 here to explain the default all physical connection The port belongs to Vlan1 so F0/1 don't need to be configured
The SW2 configuration is complete.
PC-side Configuration
PC1 IP 192.168.1.2 Gateway 192.168.1.1
PC2 IP 192.168.2.2 Gateway 192.168.2.1
PC3 IP 192.168.3.2 Gateway 192.168.3.1
So PC 1 2 3 can communicate with each other.
Have you ever thought that I created the VLAN on the SW3 and then went to the SW2 to create the VLAN, where the two-tier exchange only one, VLAN only 3, if there are more two-layer switches, and need to configure 10? 20 of them? Even more VLANs? is not a lot of work, very troublesome. In the next section we will talk about the VTP configuration, which can be easily solved.
This article from the "It Layman teahouse" blog, reproduced please contact the author!
"Ti layman" network knowledge note 53 Layer switching technology