HP 800 HP DLPI Programmer's Guide - Page 36

Reserved IEEESAPS/Ethertypes, DL_BIND_REQ or the DL_SUBS_BIND_REQ DL_PEER_BIND class

Page 36 highlights

Introduction to DLPI DLPI Services • IEEE802.2 SAPS • ethernet types • SNAP Valid IEEE802.2 SAPS include even numbers from 0-255, excluding reserved SAPS (see "Reserved IEEESAPS/Ethertypes" on page 36). Valid ethernet types range from 0x600 to 0xFFFF, excluding reserved ethertypes (see "Reserved IEEESAPS/Ethertypes" on page 36). The SNAP protocol values contain three bytes of organization ID and two bytes of additional data. If the first three bytes are 0, the following two bytes are an ethernet type with valid values from 0x0-0xFFFF. If the first three bytes are non-zero, the following two bytes are organization specific with valid values from 0x0-0xFFFF. IEEE802.2 SAPS and ethernet types are bound to the driver via the DL_BIND_REQ or the DL_SUBS_BIND_REQ (DL_PEER_BIND class only). SNAP protocol values can be logged in two ways. The first method requires you to first bind the SNAP SAP 0xAA via the DL_BIND_REQ primitive. Then, you must issue a DL_SUBS_BIND_REQ (must be DL_HIERARCHICAL_BIND class) with five bytes of SNAP data. The second method requires you to bind any non-SNAP protocol value via the DL_BIND_REQ primitive, and then issue a DL_SUBS_BIND_REQ (must be DL_PEER_BIND class) with six bytes of data. The first byte must be the SNAP SAP 0xAA followed by five bytes of SNAP data. Reserved IEEESAPS/Ethertypes Refer to the IETF RFC 1010 (or superseding version) "Assigned Numbers". The DLS provider indicates success with a DL_BIND_ACK or a DL_SUBS_BIND_ACK message and failure with a DL_ERROR_ACK message. 36 Chapter 1

  • 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
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226

Introduction to DLPI
DLPI Services
Chapter 1
36
IEEE802.2 SAPS
ethernet types
SNAP
Valid IEEE802.2 SAPS include even numbers from 0-255, excluding
reserved SAPS (see
Reserved IEEESAPS/Ethertypes
on page 36). Valid
ethernet types range from 0x600 to 0xFFFF, excluding reserved
ethertypes (see
Reserved IEEESAPS/Ethertypes
on page 36). The
SNAP protocol values contain three bytes of organization ID and two
bytes of additional data. If the first three bytes are 0, the following two
bytes are an ethernet type with valid values from 0x0-0xFFFF. If the
first three bytes are non-zero, the following two bytes are organization
specific with valid values from 0x0-0xFFFF.
IEEE802.2 SAPS and ethernet types are bound to the driver via the
DL_BIND_REQ or the DL_SUBS_BIND_REQ (DL_PEER_BIND class
only). SNAP protocol values can be logged in two ways. The first method
requires you to first bind the SNAP SAP 0xAA via the DL_BIND_REQ
primitive. Then, you must issue a DL_SUBS_BIND_REQ (must be
DL_HIERARCHICAL_BIND class) with five bytes of SNAP data. The
second method requires you to bind any non-SNAP protocol value via the
DL_BIND_REQ primitive, and then issue a DL_SUBS_BIND_REQ
(must be DL_PEER_BIND class) with six bytes of data. The first byte
must be the SNAP SAP 0xAA followed by five bytes of SNAP data.
Reserved IEEESAPS/Ethertypes
Refer to the IETF RFC 1010 (or superseding version)
Assigned
Numbers
.
The DLS provider indicates success with a DL_BIND_ACK or a
DL_SUBS_BIND_ACK message and failure with a DL_ERROR_ACK
message.