Inter-Switch Link (ISL) is a Cisco proprietary trunking protocol for the encapsulation of Virtual LAN (VLAN) traffic. 802.1q is an Institute of Electrical and Electronics Engineers (IEEE) standard trunking protocol. Most Cisco LAN switches support both, but non-Cisco LAN switches that support VLAN trunking use 802.1q.
Most non-Cisco 802.1q switches maintain only a single instance of spanning tree, known as Mono Spanning Tree (MST), that defines the spanning-tree topology for all VLANs. When a Cisco switch is connected to a non-Cisco switch through an 802.1q trunk, the MST of the non-Cisco switch and the native VLAN spanning tree of the Cisco switch combine in order to form a single spanning tree topology, known as the Common Spanning Tree (CST).
Because the Cisco switches transmit Bridge Protocol Data Units (BPDUs) to the Spanning Tree Protocol (STP) multicast MAC address on VLANs other than the native VLAN of the trunk, the non-Cisco switches do not recognize these frames as BPDUs and flood them on all of the ports in the related VLAN. Other Cisco switches connected to the non-Cisco 802.1q cloud receive these flooded BPDUs. This allows the Cisco switches to maintain a spanning tree topology for each VLAN across a cloud of non-Cisco 802.1q switches. The non-Cisco 802.1q cloud that separates the Cisco switches is treated as a single broadcast segment between all of the switches that are connected to the non-Cisco 802.1q cloud through 802.1q trunks.
Verify that the trunking mode and encapsulation are configured correctly. Make certain that the native VLAN is the same on all of the 802.1q trunks that connect the Cisco switches to the non-Cisco 802.1q cloud.
If multiple Cisco switches are connected to a non-Cisco 802.1q cloud, all of the connections must be through 802.1q trunks. Do not connect Cisco switches to a non-Cisco 802.1q cloud through ISL trunks or through access ports. If this is done, it causes the switch to place the ISL trunk port or access port into the spanning tree port inconsistent state and no traffic passes through the port.
If the trunk does not pass specific VLAN traffic, the issue can potentially be that the VLAN has not been added in the database. Issue the vlan database privileged EXEC command in order to enter VLAN configuration mode. From this mode, it is possible to add, delete, and modify VLAN configurations for normal-range VLANs.
Note: The configurations of the VLAN IDs 1 to 1005 are saved in the VLAN database if the VLAN Trunking Protocol (VTP) is in the transparent or server modes. The extended-range VLAN configurations are not saved in the VLAN database.
Dear TeamI am a bit confuse with below terms while selecting product for one of my client. Please guide me a thorough knowledge of these terms or share the link which can guide me in a precise way.1) Switching Capacity with Stacking2) Forwarding rate with...
I'm slowly getting this together, but I keep tripping.I have an ISR4331 at our main office. There are two WAN connections (ISP1 and ISP2). ISP1 has 6 IP addresses, while ISP2 has only the one. In-house, I have a pretty large array of networked equipment, ...
please helpi need to go to vrf internet from global routing table in R6 need to ping 18.104.22.168 from R6 ??????????? R1!ip vrf Internetrd 65:65!interface FastEthernet0/0ip address 172.16.234.1 255.255.255.0!interface Fa...
I am trying to create a ROAS in Packet Tracer and have come up to a wall. In the attached file I can not ping the hosts of one VLAN to the other. I can ping hosts on the same VLAN and the gateway. I am really new at this and any help wil...