This time we made is to configure the Ethernet channels and experimental Trunk link
Experimental environment: the software is ready article mentioned before my GNS3, CRT and Wireshark
First we enter GNS3 interface, click on the icon on the left side of the router, the two routers to get dragged topology operating area, then click on the PC icon, select VPC drag the PC to take four topologies operating area; while the two routers configuration settings ( change the icon for the switch, change device called sw1 / 2, add Layer 2 services board, set the disk space to 128Mb)
Next is wired as follows:
1.PC1 SW1 to the F1 / 0
2.PC2 SW1 to the F1 / 1
3.SW1 of F1 / 2 to SW2, F1 / 2
4.PC3 SW2 to the F1 / 0
5.PC4 SW2 to the F1 / 1
After setting all clicks on, and then displays all ports, and the results of operations as shown below:
Next we want to divide VLAN:
1.PC1 and PC3 is vlan10
2.PC2 and PC4 is vlan20
IP address is set to:
PC1：192.168.10.10/24
PC2：192.168.10.20/24
PC3: 192.168.10.30/24
PC4: 192.168.10.40/24
Next we conduct interoperability testing conducted after the corresponding configuration if you can communicate, then PC1 and PC3 can communicate, PC2 and PC4 can communicate, but PC1 and PC2 is not communication, PC3 and PC4 is not communication .
Then we double-click to open SW1 and SW2, respectively, to jump to the CRT interface to configure:
SW1：
1. Enter conf t
2. Enter the no ip routing exit route mode
3. Enter the vlan 10,20
4. Enter the ex exit
5. Enter do show vlan-sw b view vlan
FIG operation and results are as follows:
Next, configure the port:
1. Enter int f1 / 0
2. Enter sw mo acc
3. Enter sw acc vlan 10
4. Enter ex
5. Enter int f1 / 1
6. Enter sw mo acc
7. Enter sw acc vlan 20
8. Enter do show vlan-sw b
FIG operation and results are as follows:
SW2:
1. Enter conf t
2. Enter the no ip routing
3. Enter the vlan 10,20
4. Enter ex
5. Enter int f1 / 0
6. Enter sw mo acc
7. Enter sw acc vlan 10
8. Enter ex
9. Enter int f1 / 1
10. Enter sw mo acc
11. Enter sw acc vlan 20
12. Enter do show vlan-sw b
FIG operation and results are as follows:
Vlan on all this time the addition is complete, the next step is to configure the relay link, where our F1 / 2 is relay
In the absence of setting F1 / 2 is active in the default vlan1
1. Enter ex Exit
2. Enter the end enter the privileged mode
3. Enter show int fa1 / 0 switchport view port, port access mode display case
FIG operation and results are as follows:
Next we SW1 with the F1 / 2 to Trunk mode:
1. Enter int f1 / 2
2. Enter the switchport mode trunk to trunk mode
3. Enter the switchport trunk encapsulation dot1q protocol encapsulation dot1q
4. Enter the ex exit
5. Enter do show int f1 / 2 switchport
Display mode trunk, perform encapsulation protocol dot1q, you can take all vlan
FIG operation and results are as follows:
SW2:
1. Enter int f1 / 2
2. Enter sw mo t
3. Enter sw t en dot
4. Enter do show int f1 / 2 switchport
FIG operation and results are as follows:
Then we open the PC to write four IP addresses:
1.PC1：192.168.10.10
2.PC2：192.168.10.20
3.PC3: 192.168.10.30
4.PC4: 192.168.10.40
At this point we can test for continuity, if the configuration is no problem, then PC1 and PC3 can pass, PC2 and PC4 can pass
Entering PC1: ping 192.168.10.30 hit enter, this time may be in communication, results as shown below:
Then were ping 192.168.10.30 and hit enter ping 192.168.10.40, this time is not in communication (since different vlan), the results as shown below:
Entering PC2: ping 192.168.10.40 hit enter, this time may be in communication, results as shown below:
Then were ping 192.168.10.10 and hit enter ping 192.168.10.30, this time is not in communication (since different vlan), the results as shown below:
The results are the results of the above experiment in communication is successful.
At this point we can exchange data capture task specific analysis with Wireshark:
It will fetch data from the 1/1 port on SW1, PC2 enter, enter: ping 192.168.10.40 while communicating, the capture of data will be communicated, as shown below:
We crawl from one data, double-click to open the get the following figure shows, one of the important data and meaning in the following figure:
At this time, since we are captured in the access link data, and therefore not visible vlan tag, then if we fetch the data on the relay link, should be able to get to see the vlan tag data packet .
Your choices are:
We re-entering the PC2 knockout round display input ping 192.168.10.40 interworking, packet capture tool simultaneously acquire data, as shown below:
We grab one of the Double-click to open, then we will see will be above a 802.1q vlan ID 20
We then crawled into the PC1 and PC3 of its data exchange, after we crawl to double click to open one of our two data at this time to open on to do some comparison with the same vlan intercepted a label, it is the only different links interworking proof results as shown below:
The following is supplemental content:
Ethernet channel: at least more than two links composition, trunk ports must be
Characterized by increased link bandwidth, link reliability increases
In order to solve the problem of link bandwidth, link generated sufficiently stable, so that the current network environment is not a cable connected to the two switches as a relay link, if the line disconnection occurs, instability, then the ends of the contact the communication link will not, so the two switches in a real scene with two lines, even if such a problem, a still further work.
Next we look at how to turn the Ethernet channel, it is first necessary to make Trunk.
SW1：
1. Enter int f1 / 3
2. Enter sw mo t
3. Enter sw t en dot
4. Enter do show int f1 / 3 switchport
5. Enter no shut open
FIG operation and results are as follows:
SW1 and SW2 in the operation of the same operation and results as shown below:
The next step is tying them together into an Ethernet channel, enter SW1:
1. Enter ex Exit
2. Enter int range f1 / 2 -3
3. Enter the channel-group 1 mode on Ethernet channel opening (1 Ethernet channel ID)
FIG operation of the process and results are as follows:
At this time, the Ethernet channel ID SW2 and SW1 is should be the same, so we SW2 into the same settings as shown below:
In this case links are interoperable with each other, then the fault can be simulated to 1/2 line disconnection, can continue to see if the interworking
1. Go to PC1, ping 192.168.10.30 -t input for length measurement
2. Go SW1:
Enter ex Exit
Input int f1 / 2
Enter the shutdown off
3. Enter SW2:
Enter ex Exit
Input int f1 / 2
Enter the shutdown off
In this case the process will automatically link switch as shown below:
Zhengzhou infertility hospital: http: //yyk.39.net/zz3/zonghe/1d427.html/ Zhengzhou infertility hospital Which is good: http: //yyk.39.net/zz3/zonghe/1d427 .html / Zhengzhou infertility hospital rankings: http: //yyk.39.net/zz3/zonghe/1d427.html/
We re-entering the PC2 to see if the link should be interrupted or can be connected, the result is still the following figure can communicate:
So this time the experiment Ethernet channel will be successful!