| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
4.0b.
From customer:
There appears to be a problem with the Token Ring driver for 4.0b which
doesn't happen with the Token Ring driver for 3.2. Basically, the
protocol handshake for local ring connections are different. Here are
the two examples:
Example 1
3.2 driver - Works OK
"mac addr" "mac addr" sap sap c2 30 bf
where the first byte after the second sap is suppose to be a valid
route
control field as follows:
bbblllll dfffrrrr
where:
bbb broadcast indicator
lllll length bits
d direction bit
fff largest frame bit
rrrr reserved
Example 2
4.0 b
"mac addr" "mac addr" sap sap 00 04 03 bf
doesn't work not a valid routing, 00 04, control field. Btw the 03 is
extraneous as well.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 9717.1 | bummer | CSC32::PITT | Thu May 08 1997 14:15 | 5 | |
Looks like I have to IPMT this. Customer is stating that it is causing
a DOWN situation for him.
8-{
| |||||
| 9717.2 | ordering is important | SMURF::GILLUM | Kirt Gillum | Mon May 12 1997 17:27 | 10 |
RI (routing information) fields come immediately after the source
address. That's never changed. What you're calling a sap is actually
a RI field (if source routing is being used -- which is indicated by
bit0 in the source address -- watch out! Token Ring addresses are
bit-reversed).
If this isn't working, then filing a problem report is the best way to
go.
| |||||