D-Link DGS-3208F Product Manual - Page 29

VLANs Over 802.1Q-compliant Switches, Port-Based VLANs

Get D-Link DGS-3208F - Switch PDF manuals and user guides
UPC - 790069222092
View all D-Link DGS-3208F manuals
Add to My Manuals
Save this manual to your list of manuals

Page 29 highlights

Gigabit Ethernet Switch User's Guide forwarding decisions (this allows VLANs to span multiple switches). If an egress connection is to a noncompliant switch or end-station, tags should be stripped so the (now normal Ethernet) packet can be read by the receiving device. VLANs Over 802.1Q-compliant Switches When switches maintaining the same VLANs are 802.1Q-compliant, it is possible to use tagging. Tagging puts 802.1Q VLAN information into each packet header, enabling other 802.1Q-compliant switches that receive the packet to know how to treat it. Upon receiving a tagged packet, an 802.1Q-compliant switch can use the information in the packet header to maintain the integrity of VLANs, carry out priority forwarding, etc. Data transmissions between 802.1Q-compliant switches take place as shown below. 1 Tx Rx 2 Tx Rx 3 Tx Rx 4 Tx Rx 5 Tx Rx 6 Tx Rx 7 Tx Rx 8 Tx Rx Figure 5-5. Data transmissions between 802.1Q-compliant Switches In the above example, step 4 is the key element. Because the packet has 802.1Q VLAN data encoded in its header, the ingress port can make VLAN-based decisions about its delivery: whether server #2 is attached to a port that is a member of VLAN 2 and, thus, should the packet be delivered; the queuing priority to give to the packet, etc. It can also perform these functions for VLAN 1 packets as well, and, in fact, for any tagged packet it receives regardless of the VLAN number. If the ingress port in step 4 were connected to a non-802.1Q-compliant device and was thus receiving untagged packets, it would tag its own PVID onto the packet and use this information to make forwarding decisions. As a result, the packets coming from the non-compliant device would automatically be placed on the ingress ports VLAN and could only communicate with other ports that are members of this VLAN. Port-Based VLANs Port-based VLANs are a simplified version of the 802.1Q VLANs described in the previous section. In portbased VLANs, all the 802.1Q settings are pre-configured allowing you to quickly and easily setup and maintain port-based VLANs on your network. 22

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
Gigabit Ethernet Switch User’s Guide
22
forwarding decisions (this allows VLANs to span multiple switches). If an egress connection is to a non-
compliant switch or end-station, tags should be stripped so the (now normal Ethernet) packet can be read
by the receiving device.
VLANs Over 802.1Q-compliant Switches
When switches maintaining the same VLANs are 802.1Q-compliant, it is possible to use tagging. Tagging puts
802.1Q VLAN information into each packet header, enabling other 802.1Q-compliant switches that receive the
packet to know how to treat it. Upon receiving a tagged packet, an 802.1Q-compliant switch can use the
information in the packet header to maintain the integrity of VLANs, carry out priority forwarding, etc.
Data transmissions between 802.1Q-compliant switches take place as shown below.
1
2
3
4
5
6
7
8
Tx
Rx
Tx
Rx
Tx
Rx
Tx
Rx
Tx
Rx
Tx
Rx
Tx
Rx
Tx
Rx
Figure 5-5.
Data transmissions between 802.1Q-compliant Switches
In the above example, step 4 is the key element. Because the packet has 802.1Q VLAN data encoded in its
header, the ingress port can make VLAN-based decisions about its delivery: whether server #2 is attached to a
port that is a member of VLAN 2 and, thus, should the packet be delivered; the queuing priority to give to the
packet, etc. It can also perform these functions for VLAN 1 packets as well, and, in fact, for any tagged packet
it receives
regardless of the VLAN number.
If the ingress port in step 4 were connected to a non-802.1Q-compliant device and was thus receiving
untagged packets, it would tag its own PVID onto the packet and use this information to make forwarding
decisions. As a result, the packets coming from the non-compliant device would automatically be placed on the
ingress ports VLAN and could only communicate with other ports that are members of this VLAN.
Port-Based VLANs
Port-based VLANs are a simplified version of the 802.1Q VLANs described in the previous section. In port-
based VLANs, all the 802.1Q settings are pre-configured allowing you to quickly and easily setup and
maintain port-based VLANs on your network.