|
Lesson 1 - LAN Protocols - IEEE 802 FamilyLAN ProtocolsThe Data Link Layer Protocols Diagram illustrates the two sublayers, 802.2 LLC and the various 802.n MAC technologies.
Data Link Layer ProtocolsThe following are sublayers of the Data Link Layer protocol:
Ethernet V2, or the original Ethernet, preceded the IEEE 802 specification. MAC functionality was discussed earlier in the addressing lesson and is primarily concerned with handling the mechanics of address recognition and framing while controlling user access to the medium. The LLC area of an 802.3 Ethernet frame is shown highlighted on the 802.2 LLC Header Diagram, which illustrates the LLC header as the first part of the Information field. The header contains reserved codes that are used to deliver the data to the proper Network Layer service. It does this by the use of service access points (SAPs), which indicate the protocol in the Network Layer for which the frame is destined. An IEEE 802.2-encoded frame uses SAPs, while the older Ethernet Version 2 frame uses a Type field to accomplish this function.
802.2 LLC HeaderThe LLC Frame Format Diagram shows the LLC header broken out into its respective fields.
LLC Frame FormatThe LLC Header field descriptions are as follows:
The following frame fragment illustrates the LLC portion of the frame in bolded text. Notice on the first line of the hexadecimal data (the line with ADDR 0000), the field immediately following the 81h (Length field) is the DSAP. Its value is F0h, indicating the frame is carrying Network Basic Input Output System (NetBIOS) and is to be delivered to the NetBIOS process in the layer above. The LLC portion of the trace is actually NetBEUI, which is an 802.2 LLC protocol. The command is an "I frame," which means a frame containing user information is being sent. DLC: ----- DLC Header ----- DLC: DLC: Frame 1 arrived at 09:18:37.3543; frame size is 143 (008F hex) bytes. DLC: Destination = Station 3Com 676974 DLC: Source = Station 3Com 741178 DLC: 802.3 length = 129 DLC: LLC: ----- LLC Header ----- LLC: LLC: DSAP = F0, SSAP = F0, Command, I frame, N(R) = 29, N(S) = 109 LLC: NETB: ----- NETBIOS Data Only Last ----- ADDR HEX ASCII 0000 02 60 8C 67 69 74 02 60 8C 74 11 78 00 81 F0 F0 .`.git.`.t.x.... 0010 DA 3A 0E 00 FF EF 16 00 00 00 00 00 6B 16 19 01 .:..........k... The NetBEUI receive count represents the next frame number the station that transmitted this Ethernet frame expects to get. That is, in the above trace the source station had previously gotten frame number 28, and now expects frame number 29. It shows this by the value in its N(R) count--N(R) = 29. It is important to note that the send and receive counts are the source station's send and receive counts, because the source station is the one transmitting. The N(S) count is 109, which means that this is frame number 109, but it does not necessarily indicate that it is the 109th frame that was sent (or 110th counting frame number 0). The reason for this is that the frame counts go from 0 to 127 and then wrap around to 0 again. There is no way to look at the trace and be able to tell how many times the count has wrapped. The window size is set for a large window (called modulo 128), which simply means the count goes from 0 to 127. A smaller window size (modulo 8) would mean the count goes from 0 to 7 and then wraps around to 0 again. With a small window size, only 7 frames can be transmitted at one time, and then the other end must acknowledge the frames before any more frames can be sent. With the larger window, 127 frames can be sent before an acknowledgment is required. The larger window size is more efficient, but on a "noisy" line a smaller window size may be required to keep the number of retransmitted frames to a minimum. Remember, more than one frame at a time can be sent, up to the maximum number represented by the modulo number minus one. [ Previous Section ] [ Unit Contents ] [ Next Lesson ]
|