Home » HP Manuals » Servers » HP 800 » Manual Viewer

HP 800 HP DLPI Programmer's Guide - Page 26

HP PPA Format, Data Link User Identification, HP DLSAP Address Format (802.3, Ethernet, Token Ring

Add to My Manuals
Save this manual to your list of manuals

Page 26 highlights

Introduction to DLPI The Data Link Layer HP PPA Format The PPA number passed in the DL_ATTACH_REQ primitive should correspond to one of the PPAs displayed by the lanscan(1M) command. This PPA must be supported by DLPI. Alternatively, you can obtain the PPA of the interface programmatically using the DL_HP_PPA_REQ primitive (see Chapter 2). Data Link User Identification A data link user's identity is established by associating it with a data link service access point (DLSAP). This is the point through which the user communicates with the data link provider. A DLSAP is identified by a DLSAP address. The DLSAP address identifies a particular data link service access point that is associated with a stream (communication endpoint). The DL_BIND_REQ and DL_SUBS_BIND_REQ service primitives enable a DLS user to specify a DLSAP address. The DLSAP address can be used by other DLS users to access a specific DLS user. The format of the DLSAP address is specific to the DLS provider. However, DLPI provides a mechanism for decomposing the DLSAP address into component pieces. A DLS user can use the DL_INFO_REQ service primitive to determine the DLSAP address bound by the stream.This results in the DL_INFO_ACK service primitive, which provides length of the SAP component of the DLSAP address, along with the total length of the DLSAP address. By defining the DLSAP address, the DLS user identifies the data messages that must be passed to the DLS user. It is invalid for a DLS provider to ever send upstream a data message, which is not requested by the DLS user on that stream. HP DLSAP Address Format (802.3, Ethernet, Token Ring, FDDI) Ethernet/IEEE802.3 and FDDI MAC addresses are presented in canonical format. Token Ring MAC addresses are presented in wire format. DLSAPs are what DLPI defines as an address through which the user communicates with a Data Link Service (DLS) provider. The content of the DLSAP address depends on the context in which it is used (that is, which primitive is being processed or acknowledged). The basic format of the DLSAP address is always the same. 26 Chapter 1

Section	Page
1 Introduction to DLPI	15
HP DLPI Features	17
Fine-grained Privileges	17
Device File Format	19
Header Files	19
The Data Link Layer	20
The Service Interface	20
Modes of Communication	22
Connection-mode Service	23
Connectionless-mode Service	24
DLPI Addressing	24
Physical Attachment Identification	25
HP PPA Format	26
Data Link User Identification	26
HP DLSAP Address Format (802.3, Ethernet, Token Ring, FDDI)	26
Promiscuous Mode Clarifications	29
DLPI Services	30
Local Management Services	34
Information Reporting Service	34
Attach Service	34
Bind Service	35
Binding	35
Reserved IEEESAPS/Ethertypes	36
Connection-mode Services	39
Connection Establishment Service	39
Connection Handoff	40
Data Transfer Service	44
Connection Release Service	44
Reset Service	46
Connectionless-mode Services	48
Connectionless Data Transfer	49
Error Reporting Service	49
Raw-mode Services	50
Raw-mode Data Transfer	50
Error Reporting Service	51
XID and TEST Service	51
XID and TEST Packet Handling	51
An Example	53
2 DLPI Primitives	55
Local Management Primitives	57
PPA Initialization and De-initialization	57
DL_HP_PPA_REQ	58
DL_HP_PPA_ACK	59
DL_INFO_REQ	62
DL_INFO_ACK	62
DL_HP_NOTIFY_EVENT_REQ	67
DL_LINK_DOWN_IND	69
DL_LINK_UP_IND	69
DL_ATTACH_REQ	70
DL_DETACH_REQ	72
DL_BIND_REQ	73
DL_BIND_ACK	76
DL_UNBIND_REQ	77
DL_SUBS_BIND_REQ	78
DL_SUBS_BIND_ACK	80
DL_SUBS_UNBIND_REQ	81
DL_ENABMULTI_REQ	82
DL_DISABMULTI_REQ	83
DL_PROMISCON_REQ	85
DL_PROMISCOFF_REQ	87
DL_HP_HW_RESET_REQ	89
DL_HP_RESET_STATS_REQ	90
DL_OK_ACK	92
DL_ERROR_ACK	92
Optional Primitives to Perform Essential Management Functions	93
DL_PHYS_ADDR_REQ	94
DL_PHYS_ADDR_ACK	95
DL_SET_PHYS_ADDR_REQ	96
DL_GET_STATISTICS_REQ	98
DL_GET_STATISTICS_ACK	99
DL_HP_GET_64BIT_STATS_REQ	100
DL_HP_GET_64BIT_STATS_ACK	101
DL_HP_MULTICAST_LIST_REQ	102
DL_HP_MULTICAST_LIST_ACK	104
Connectionless-mode Service Primitives	106
DL_UNITDATA_REQ	106
DL_UNITDATA_IND	108
DL_UDERROR_IND	109
Raw Mode Service Primitives	111
DL_HP_RAWDATA_REQ	111
DL_HP_RAWDATA_IND	112
Connection-mode Service Primitives	114
Connection-Oriented DLPI Extensions	114
DL_HP_INFO_REQ	114
DL_HP_INFO_ACK	115
DL_HP_SET_ACK_TO_REQ	119
DL_HP_SET_P_TO_REQ	120
DL_HP_SET_REJ_TO_REQ	121
DL_HP_SET_BUSY_TO_REQ	122
DL_HP_SET_SEND_ACK_TO_REQ	123
DL_HP_SET_MAX_RETRIES_REQ	124
DL_HP_SET_ACK_THRESH_REQ	124
DL_HP_SET_LOCAL_WIN_REQ	126
DL_HP_SET_REMOTE_WIN_REQ	127
DL_HP_CLEAR_STATS_REQ	128
DL_HP_SET_LOCAL_BUSY_REQ	129
DL_HP_CLEAR_LOCAL_BUSY_REQ	130
DL_CONNECT_REQ	130
DL_CONNECT_IND	132
DL_CONNECT_RES	134
DL_CONNECT_CON	137
DL_TOKEN_REQ	138
DL_TOKEN_ACK	139
DL_DATA_REQ	139
DL_DATA_IND	140
DL_DISCONNECT_REQ	140
DL_DISCONNECT_IND	142
DL_RESET_REQ	144
DL_RESET_IND	145
DL_RESET_RES	146
DL_RESET_CON	147
Primitives to Handle XID and TEST Operations	148
DL_TEST_REQ	148
DL_TEST_IND	150
DL_TEST_RES	151
DL_TEST_CON	152
DL_XID_REQ	153
DL_XID_IND	155
DL_XID_RES	156
DL_XID_CON	157
DLPI States	159
3 DLPI Input/Output Controls	167
ioctl Processing	169
Supported ioctls	171
DL_IOC_DRIVER_OPTIONS	171
DL_IOC_HDR_INFO	173
DL_HP_SET_DRV_PARAM_IOCTL	175
DL_HP_GET_DRV_PARAM_IOCTL	179
DLPI_SET_NOLOOPBACK	180
A Sample Programs	183
ioctl Example	184
Connection Mode Example	189
Connectionless Mode Example	203
Raw Mode Example	216

Match case Limit results 1 per page

Introduction to DLPI

The Data Link Layer

Chapter 1

HP PPA Format

The PPA number passed in the DL_ATTACH_REQ primitive should

correspond to one of the PPAs displayed by the

lanscan(1M)

command.

This PPA must be supported by DLPI.

Alternatively, you can obtain the PPA of the interface programmatically

using the DL_HP_PPA_REQ primitive (see Chapter 2).

Data Link User Identification

A data link user

’

s identity is established by associating it with a data

link service access point (DLSAP). This is the point through which the

user communicates with the data link provider. A DLSAP is identified by

a DLSAP address.

The DLSAP address identifies a particular data link service access point

that is associated with a stream (communication endpoint). The

DL_BIND_REQ and DL_SUBS_BIND_REQ service primitives enable a

DLS user to specify a DLSAP address. The DLSAP address can be used

by other DLS users to access a specific DLS user.

The format of the DLSAP address is specific to the DLS provider.

However, DLPI provides a mechanism for decomposing the DLSAP

address into component pieces. A DLS user can use the DL_INFO_REQ

service primitive to determine the DLSAP address bound by the

stream.This results in the DL_INFO_ACK service primitive, which

provides length of the SAP component of the DLSAP address, along with

the total length of the DLSAP address.

By defining the DLSAP address, the DLS user identifies the data

messages that must be passed to the DLS user. It is invalid for a DLS

provider to ever send upstream a data message, which is not requested

by the DLS user on that stream.

HP DLSAP Address Format (802.3, Ethernet, Token Ring, FDDI)

Ethernet/IEEE802.3 and FDDI MAC addresses are presented in

canonical format. Token Ring MAC addresses are presented in wire

format.

DLSAPs are what DLPI defines as an address through which the user

communicates with a Data Link Service (DLS) provider. The content of

the DLSAP address depends on the context in which it is used (that is,

which primitive is being processed or acknowledged). The basic format of

the DLSAP address is always the same.