So you have more than one multiple VLAN on the switch, but how do you transport passes between these exchangers no crossover cable into the port, this may be a huge waste of port density in each VLAN exists? The answer is so simple that it is called a trunk link. First trunk link can be very difficult to grasp, but the trunk is the essence of 2 or more for a single link multiple VLAN traffic between switches. This is Cisco proprietary converter link (ISL) trunking wrappers or IEEE standard 802.1 q (dot1q) trunk encapsulation protocols.
Trunk encapsulation protocols, and you will need to know how to configure the operation of CCNA, validation and troubleshooting using Dot1q or ISL trunk link.
Switch link (ISL) as previously mentioned is a Cisco proprietary protocol which encapsulates the trunk into a 26-byte header and 4 bytes of frame check sequence of frames as a whole (FCS) and transport 10 bit is added in front of the trunk link to ensure that the traffic from SW1 to VLAN 10, VLAN ID the VLAN 10 o'clock, SW2.
IEEE standard 802.1 q (Dot1q) but does not encapsulate Ethernet frames as a whole, but 32-bit fields, but into the Ethernet MAC address of the frame between the original frames and Ethernet type/length field.
Dot1q 32-bit in the field is divided into 4 specific sections. TPID, pentachlorophenol, the first 16 bits of the next 3 followed by the Court of first instance and the last VID.
Tag protocol identifier (TPID) is a 16-bit field. To determine if IEEE 802.1 q-frame is set to a value of 0x8100-frame with a label.
Priority code point (PCP) refers to the IEEE 802.1 p priority 3-bit field. Field indicates the frame priority level, the priorities can be used to transport. The value of the field to 8 (0 to 7).
Standard format indicator (CFI) is a 1 bit value; opens or closes, and determine whether or not MAC addresses are in normalized format.
VLAN identifier (VID) is a 12-bit field. It uniquely identifies the VLAN to which the frame belongs. The field can have a value between 0 per cent.
This is used by the Cisco recommends that all deployments of IEEE 802.1 q standards because this is dealer, actionable link between Cisco switches that are specific to only the Cisco switch.
In this lab, you will familiarize yourself with the following command;
(F) using GNS3 CCNA free load Binder-GNS3 topology than a starter, SW1, SW2, R1 and R2.
SW1, SW2, the establishment and equipment of R1 and R2 to configure a device console session respects the hostname (s).
10.1.1.2/24 configure R1 ′ s IP address the IP address of the interface 10.1.1.1/24 and s ′ R2 FastEthernet0/1 interface FastEthernet0/0
2 create a VLAN VLAN 10 on SW1 and SW2. (Layer 2 VLAN is not VLAN interface 3 layer their VLAN; i.e., no interface Vlan10.)
Static access SW1 and SW2 ′ s ′ s FastEthernet0/1 FastEthernet0/2 interface is configured as VLAN 10.
Lab Objectives:
- (F) using GNS3 CCNA free load Binder GNS3 topology than the starter, SW1, SW2, R1 and R2.
- SW1, SW2, creation and design of the R1 and the R2 configuration console session komfort respects the host (s).
- Configure R1 ′ 10.1.1.2/24 IP IP and s ′ R2 FastEthernet0/1 interface 10.1.1.1/24 interface FastEthernet0/0
- 2 create a VLAN VLAN 10 on SW1 and SW2. (Layer 2 VLAN is not VLAN interface VLAN 3 layer; that is, no interface Vlan10. )
- SW1 and SW2 TV static ′ ′ FastEthernet0/1 FastEthernet0/2 interface configured for VLAN 10.
Lab Instruction:
Step 1. Shutting down FastEthernet0/11 and FastEthernet0/12 in the SW1 and SW2 interface FastEthernet0/10 interface and configure IEEE 802.1 q on SW1 and SW2 on the trunk.
To configure an interface as a static trunk, you will first need to configure the package for the first time as its trunk encapsulation is "automatic" interface may not be configured to "trunk" modes.
SW1 con0 is now available
Press RETURN to get started.
SW1>enable
SW1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
SW1(config-if)#interface range Fa0/11 - 12
SW1(config-if-range)#shutdown
SW1(config-if-range)#interface fa0/10
SW1(config-if)#switchport trunk encapsulation dot1q
SW1(config-if)#switchport mode trunk
SW1(config-if)#no shut
SW1(config-if)#end
SW1#
Step 2. Verify that the R1 to R2 accessibility IP ping command on R1.
Now, you have a trunk link between SW1 and SW2, SW1 built on traffic in VLAN 10 should be able to spread to VLAN 10 on SW2. To test this, ping R2 ' s FastEthernet zero-first interface (IP address 10.1.1.2) R1 as shown;
R1#ping 10.1.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 4/29/60 ms
R1#
When you ping from R1 FastEthernet0/1 ′ s IP address of the interface, know that the destination IP address of the router is on the same local subnet to its ARP for host 10.1.1.2 MAC address, ARP-request received are SW1, SW2 on on R2 and answer "Hey 10.1.1.2, my MAC address is ABCD. EF 12.3456. 。 R1 now know MAC address of 10.1.1.2 direction SW1 with the correct destination MAC address, then forwarded the ICMP datagrams. Originally because so and so he will be forwarding interfaces in addition to the frame of the machine not local VLAN interfaces that switch SW1 will not know the location of the MAC address. When the frame switch SW2 has received is the correct port as its MAC address MAC that already exists in the table. R2 datagram ICMP response SW1 the opposite way. SW1, receives a response with R2 R1 after seeing SW1 not learn new source MAC-address MAC-address will then be set in the CAM table (Mac address) for future use.
SW2#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
SW2(config)#interface FastEthernet0/2
SW2(config-if)#switchport access vlan 5
% Access VLAN does not exist. Creating vlan 5
SW2(config-if)#end
SW2#
R1#ping 10.1.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R1#
As shown in the lab using can span multiple switches in a single reference to the barrel link to send traffic to more than one VLAN.
NM and Cisco 16ESW 2,950 does not support ISL encapsulation provides the boot configuration example below. Please note that ISL ISL and Dot1q encapsulation exchanger port |dot1q the only difference between trunk configuration command options.
c3560-Switch1>enable
c3560-Switch1#configure terminal
c3560-Switch1(config)#interface fa0/10
c3560-Switch1(config-if)#switchport trunk encap isl
c3560-Switch1(config-if)#switchport mode trunk
c3560-Switch1(config-if)#end
c3560-Switch1#sh int fa0/10 trunk
Port Mode Encapsulation Status Native vlan
Fa0/10 on isl trunking 1
Port Vlans allowed on trunk
Fa0/10 none
Port Vlans allowed and active in management domain
Fa0/10 none
Port Vlans in spanning tree forwarding state and not pruned
Fa0/10 none
c3560-Switch1#
0 comments:
Post a Comment