Document ID: 5256
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Direct Encapsulation
FST Encapsulation
TCP Encapsulation
NetPro Discussion Forums - Featured Conversations
Related Information
Introduction
This document shows Remote Source-Route Bridging (RSRB) overhead information for direct, Fast Sequenced Transport (FST), and TCP encapsulations.
Prerequisites
Requirements
Readers of this document should have knowledge of these topics:
Components Used
This document is not restricted to specific software or hardware versions.
Conventions
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
Direct Encapsulation
|
Media Header |
RSRB Header |
Token Ring Frame |
|---|---|---|
|
(Cisco) |
||
|
See #1 |
16 bytes (see #2) |
See #3 |
-
Media header consists of one of these:
-
Serial = 4 bytes
-
Ethernet (802.3) = 22 bytes + padding, if needed
These 22 bytes contain the destination address (DA), source address (SA), length, destination service access point (DSAP), source service access point (SSAP), control, and frame check sequence (FCS).
-
Ethernet (Type 2) = 18 bytes + padding, if needed
These 18 bytes contain the DA, SA, type, and FCS.
-
Token Ring = maximum 39 bytes:
-
Physical header = 15 bytes
These 15 bytes contain the starting delimiter (SD), access control (AC), frame control (FC), DA, and SA.
-
Routing information = from 2 to 18 bytes
-
Physical trailer = 6 bytes
These 6 bytes contain the FCS, ending delimiter (ED), and frame status (FS).
-
-
FDDI = 18 bytes
These 18 bytes contain the SD, FC, DA, SA, FCS, ED, FS.
-
-
RSRB header:
Bytes
Descriptions
Notes
2
rhdr_version
rhdr_version and op must be the same.
2
op
For all RSRB versions
2
trn
Target ring number
2
vrn
Virtual ring number or ring group
2
offset
(As needed) pointer into packet
2
len
Length of this segment or packet
4
param
Miscellaneous parameter
-
The Token Ring frame is the frame that RSRB receives from the Token Ring interface. The whole frame will be encapsulated.
FST Encapsulation
|
Media Header |
IP Header |
RSRB Header |
Token Ring Frame |
|---|---|---|---|
|
(Cisco) |
|||
|
See #1 |
20 bytes (see #2) |
10 bytes (see #3) |
See #4 |
-
Media header = Same as under direct encapsulation.
-
IP header = 20 bytes, with no options.
-
RSRB header:
Bytes
Descriptions
Notes
2
rhdr_version
rhdr_version and op must be the same.
2
op
For all RSRB versions
2
trn
Target ring number
2
vrn
Virtual ring number or ring group
2
offset
(As needed) pointer into packet
-
The Token Ring frame is the frame that RSRB receives from the Token Ring interface. The whole frame will be encapsulated.
TCP Encapsulation
|
Media Header |
IP Header |
TCP Header |
RSRB Header |
Token Ring Frame |
|---|---|---|---|---|
|
(Cisco) |
||||
|
See #1 |
20 bytes (see #2) |
20 bytes (see #3) |
16 bytes (see #4) |
See #5 |
-
Media header = Same as under direct encapsulation.
-
IP header = 20 bytes, with no options.
-
TCP header = 20 bytes, with no options.
-
RSRB header:
Bytes
Descriptions
Notes
2
rhdr_version
rhdr_version and op must be the same.
2
op
For all RSRB versions
2
trn
Target ring number
2
vrn
Virtual ring number or ring group
2
offset
(As needed) pointer into packet
2
len
Length of this segment or packet
4
param
Miscellaneous parameter
-
The Token Ring frame is the frame that RSRB receives from the Token Ring interface. The frame will be fragmented—up to 1450 bytes each—if necessary.
NetPro Discussion Forums - Featured Conversations
| NetPro Discussion Forums - Featured Conversations for IBM |
| Network Infrastructure: Enterprise Data Centers |
Related Information
| Updated: Sep 09, 2005 | Document ID: 5256 |
