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

HP 800 HP DLPI Programmer's Guide - Page 164

state DL_PROV_RESET_PENDING i.e. after a DL_RESET_IND

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

Page 164 highlights

DLPI Primitives DLPI States 164 • The close of a stream is considered an abortive action by the DLS user, and may be executed from any state. The DLS provider must issue appropriate indications to the remote DLS user when a close occurs. For example, if the DLPI state is DL_DATAXFER, a DL_DISCONNECT_IND should be sent to the remote DLS user. The DLS provider should free any resources associated with that stream and reset the stream to its unopened condition. The following points clarify the state transition table. • If the DLS provider supports connection-mode service, the value of the outcnt state variable must be initialized to zero for each stream when that stream is first opened. • The initial and final state for a style 2 DLS provider is DL_UNATTACHED. However, because a style 1 DLS provider implicitly attaches a PPA to a stream when it is opened, the initial and final DLPI state for a style 1 provider is DL_UNBOUND. The DLS user should not issue DL_ATTACH_REQ or DL_DETACH_REQ primitives to a style 1 DLS provider. • A DLS provider may have multiple connect indications outstanding (i.e. the DLS user has not responded to them) at one time. As the state transition table points out, the stream on which those indications are outstanding will remain in the DL_INCON_PENDING state until the DLS provider receives a response for all indications. • The DLPI state associated with a given stream may be transferred to another stream only when the DL_CONNECT_RES primitive indicates this behavior. In this case, the responding stream (where the connection will be established) must be in the DL_IDLE state. • The labeling of the states DL_PROV_RESET_PENDING and DL_USER_RESET_PENDING indicate the party that started the local interaction, and does not necessarily indicate the originator of the reset procedure. • A DL_DATA_REQ primitive received by the DLS provider in the state DL_PROV_RESET_PENDING (i.e. after a DL_RESET_IND has been passed to the DLS user) or the state DL_IDLE (i.e. after a data link connection has been released) should be discarded by the DLS provider. • A DL_DATA_IND primitive received by the DLS user after the user has issued a DL_RESET_REQ should be discarded. Chapter 2

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

DLPI Primitives

DLPI States

Chapter 2

164

•

The close of a stream is considered an abortive action by the DLS

user, and may be executed from any state. The DLS provider must

issue appropriate indications to the remote DLS user when a close

occurs. For example, if the DLPI state is DL_DATAXFER, a

DL_DISCONNECT_IND should be sent to the remote DLS user. The

DLS provider should free any resources associated with that stream

and reset the stream to its unopened condition.

The following points clarify the state transition table.

•

If the DLS provider supports connection-mode service, the value of

the outcnt state variable must be initialized to zero for each stream

when that stream is first opened.

•

The initial and final state for a style 2 DLS provider is

DL_UNATTACHED. However, because a style 1 DLS provider

implicitly attaches a PPA to a stream when it is opened, the initial

and final DLPI state for a style 1 provider is DL_UNBOUND. The

DLS user should not issue DL_ATTACH_REQ or

DL_DETACH_REQ primitives to a style 1 DLS provider.

•

A DLS provider may have multiple connect indications outstanding

(i.e. the DLS user has not responded to them) at one time. As the

state transition table points out, the stream on which those

indications are outstanding will remain in the

DL_INCON_PENDING state until the DLS provider receives a

response for all indications.

•

The DLPI state associated with a given stream may be transferred to

another stream only when the DL_CONNECT_RES primitive

indicates this behavior. In this case, the responding stream (where

the connection will be established) must be in the DL_IDLE state.

•

The labeling of the states DL_PROV_RESET_PENDING and

DL_USER_RESET_PENDING indicate the party that started the

local interaction, and does not necessarily indicate the originator of

the reset procedure.

•

A DL_DATA_REQ primitive received by the DLS provider in the

state DL_PROV_RESET_PENDING (i.e. after a DL_RESET_IND

has been passed to the DLS user) or the state DL_IDLE (i.e. after a

data link connection has been released) should be discarded by the

DLS provider.

•

A DL_DATA_IND primitive received by the DLS user after the user

has issued a DL_RESET_REQ should be discarded.