 |
» |
|
|
|
DEFINE_LS is used to define a new link station (LS) or modify
an existing one. Before issuing this verb, you must issue the DEFINE_PORT
verb to define the port that this LS uses. Link specific data is
concatenated to the basic structure. You cannot use DEFINE_LS to modify the port used by an existing
LS; the port_name specified on the verb must match the previous definition of
the LS. The LS can be modified only if it is not started. VCB
Structure | |
typedef struct define_ls
{
AP_UINT16 opcode; /* verb operation code */
unsigned char reserv2; /* reserved */
unsigned char format; /* reserved */
AP_UINT16 primary_rc; /* primary return code */
AP_UINT32 secondary_rc; /* secondary return code */
unsigned char ls_name[8]; /* name of link station */
LS_DEF_DATA def_data; /* LS defined data */
} DEFINE_LS;
|
|
|
typedef struct ls_def_data
{
unsigned char description[32]; /* resource description */
unsigned char initially_active; /* is this LS initially active? */
AP_UINT16 reserv2; /* reserved */
AP_UINT16 react_timer; /* timer for retrying failed LS */
AP_UINT16 react_timer_retry; /* retry count for failed LS */
unsigned char reserv3[10]; /* reserved */
unsigned char port_name[8]; /* name of associated port */
unsigned char adj_cp_name[17]; /* adjacent CP name */
unsigned char adj_cp_type; /* adjacent node type */
LINK_ADDRESS dest_address; /* destination address */
unsigned char auto_act_supp; /* auto-activate supported */
unsigned char tg_number; /* pre-assigned TG number */
unsigned char limited_resource; /* limited resource */
unsigned char solicit_sscp_sessions; /* solicit SSCP sessions */
unsigned char pu_name[8]; /* Local PU name (reserved if */
/* solicit_sscp_sessions is set */
/* to AP_NO) */
unsigned char disable_remote_act; /* disable remote activation */
unsigned char dspu_services; /* services provided for downstream
PU */
unsigned char dspu_name[8]; /* Downstream PU name (reserved if
dspu_service AP_NONE) */
unsigned char dlus_name[17]; /* DLUS name if dspu_services */
/* set to AP_DLUR */
unsigned char bkup_dlus_name[17]; /* Backup DLUS name if */
/* dspu_services set to AP_DLUR */
unsigned char hpr_supported; /* reserved */
unsigned char hpr_link_lvl_error; /* reserved */
AP_UINT16 link_deact_timer; /* link deactivation timer */
unsigned char reserv1; /* reserved */
unsigned char default_nn_server; /* default LS to NN server? */
unsigned char ls_attributes[4]; /* LS attributes */
unsigned char adj_node_id[4]; /* adjacent node ID */
unsigned char local_node_id[4]; /* local node ID */
unsigned char cp_cp_sess_support; /* CP-CP session support */
unsigned char use_default_tg_chars; /* Use the default tg_chars */
TG_DEFINED_CHARS tg_chars; /* TG characteristics */
AP_UINT16 target_pacing_count; /* target pacing count */
AP_UINT16 max_send_btu_size; /* maximum send BTU size */
AP_UINT16 ls_role; /* link station role */
unsigned char max_ifrm_rcvd; /* no. before acknowldgement */
AP_UINT16 dlus_retry_timeout; /* seconds to recontact a DLUS */
AP_UINT16 dlus_retry_limit; /* attempts to recontact a DLUS */
AP_UINT16 reserv4[30]; /* reserved */
AP_UINT16 link_spec_data_len; /* length of link specific data */
} LS_DEF_DATA;
|
|
|
typedef struct tg_defined_chars
{
unsigned char effect_cap; /* effective capacity */
unsigned char reserve1[5]; /* reserved */
unsigned char connect_cost; /* connection cost */
unsigned char byte_cost; /* byte cost */
unsigned char reserve2; /* reserved */
unsigned char security; /* security */
unsigned char prop_delay; /* propagation delay */
unsigned char modem_class; /* reserved */
unsigned char user_def_parm_1; /* user-defined parameter 1 */
unsigned char user_def_parm_2; /* user-defined parameter 2 */
unsigned char user_def_parm_3; /* user-defined parameter 3 */
} TG_DEFINED_CHARS;
typedef struct link_address
{
AP_UINT16 reserve1; /* reserved */
AP_UINT16 length; /* length */
unsigned char address[32]; /* address */
} LINK_ADDRESS;
|
DLC-specific data for SDLC: |
typedef struct sdl_link_spec_data
{
V0_MUX_INFO mux_info; /* Streams config info */
AP_UINT16 reserve8; /* reserved */
AP_UINT16 reserve9; /* reserved */
AP_UINT32 contact_timer; /* contact timer (fast poll, */
/* in ms) */
AP_UINT16 contact_timer_retry; /* contact timer retry */
AP_UINT16 reserve1; /* reserved */
AP_UINT32 contact_timer2; /* contact timer (slow poll, */
/* in ms) */
AP_UINT16 contact_timer_retry2; /* contact timer 2 retry */
AP_UINT16 reserve2; /* reserved */
AP_UINT32 disc_timer; /* disconnect timer (in ms) */
AP_UINT16 disc_timer_retry; /* disconnect timer retry */
AP_UINT16 reserve3; /* reserved */
AP_UINT32 nve_poll_timer; /* negative poll timer(fast poll) */
AP_UINT16 nve_poll_timer_retry; /* negative poll timer retry */
AP_UINT16 reserve4; /* reserved */
AP_UINT32 nve_poll_timer2; /* negative poll timer(slow poll) */
AP_UINT16 nve_poll_timer_retry2; /* negative poll timer 2 retry */
AP_UINT16 reserve5; /* reserved */
AP_UINT32 no_resp_timer; /* No response timer (T1 timer)) */
/* (in ms) */
AP_UINT16 no_resp_timer_retry; /* No response timer retry */
AP_UINT16 reserve6; /* reserved */
AP_UINT32 rem_busy_timer; /* Remote busy timer (in ms) */
AP_UINT16 rem_busy_timer_retry; /* Remote busy timer retry */
unsigned char re_tx_threshold; /* reserved */
unsigned char repoll_threshold; /* reserved */
AP_UINT32 rr_timer; /* RR turnaround timer (in ms) */
unsigned char group_address; /* reserved */
unsigned char poll_frame; /* Poll frame to use when Primary */
/* and contact polling secondary */
/* XID, DISC, SNRM, SNRME, TEST */
AP_UINT16 poll_on_iframe; /* Can LS send poll bit on */
/* I-frame */
AP_UINT16 stub_spec_data_len; /* length of stub specific data */
STUB_SPEC_DATA stub_spec_data; /* stub specific data */
} SDL_LINK_SPEC_DATA;
typedef struct stub_spec_data
{
int mux_id; /* reserved */
unsigned char opt1; /* options flag 1 */
unsigned char opt2; /* options flag 2 */
unsigned char pad[2]; /* reserved */
AP_UINT32 linesp; /* line speed in bps */
AP_UINT16 rcv_pool_size; /* initial number of buffers for */
/* rcv pool */
AP_UINT16 poll_wait; /* seconds between polling HMOD */
/* for errors */
AP_UINT16 hmod_data_len; /* length of dial data string */
unsigned char hmod_data[64]; /* dial data string */
unsigned char x21_sequence[255]; /* reserved */
unsigned char x21_retry_count; /* reserved */
AP_UINT16 x21_retry_delay; /* reserved */
AP_UINT16 v25_tx_delay; /* reserved */
unsigned char cdstl; /* reserved */
unsigned char reserve1[3]; /* reserved */
} STUB_SPEC_DATA;
|
|
DLC-specific data for QLLC: |
typedef struct vql_ls_spec_data
{
V0_MUX_INFO mux_info; /* streams config info */
AP_UINT16 reserve1; /* reserved */
AP_UINT16 reserve2; /* reserved */
unsigned char vc_type; /* Virtual Circuit type */
unsigned char req_rev_charge; /* request reverse charge if */
/* non-zero */
unsigned char loc_packet; /* loc->rem packet */
/* size 2**locpacket */
unsigned char rem_packet; /* rem->loc packet */
/* size 2**rempacket */
unsigned char loc_wsize; /* loc->rem window size */
unsigned char rem_wsize; /* rem->loc window size */
AP_UINT16 fac_len; /* X.25 facilities length */
unsigned char fac[32]; /* X.25 facilities */
AP_UINT16 retry_limit; /* times to retry send QXID,QSM, */
/* QDISC */
AP_UINT16 retry_timeout; /* timeout for each of above tries*/
AP_UINT16 idle_timeout; /* timeout for no Q msgs during */
/* init */
AP_UINT16 pvc_id; /* PVC logical channel identifier */
AP_UINT16 sn_id_len; /* Length of the subnet identifier*/
unsigned char sn_id[4]; /* Subnet identifier */
AP_UINT16 cud_len; /* length of any call user data */
/* to send */
unsigned char cud[16]; /* actual call user data */
AP_UINT32 xtras; /* reserved */
AP_UINT32 xtra_len; /* reserved */
unsigned char rx_thruput_class; /* reserved */
unsigned char tx_thruput_class; /* reserved */
unsigned char cugo; /* reserved */
unsigned char cug; /* reserved */
AP_UINT16 cug_index; /* reserved */
AP_UINT16 nuid_length; /* reserved */
unsigned char nuid_data[109]; /* reserved */
unsigned char reserve3[2]; /* reserved */
unsigned char rpoa_count; /* reserved */
AP_UINT16 rpoa_ids[30]; /* reserved */
} VQL_LS_SPEC_DATA;
|
|
DLC-specific data for Token Ring, Ethernet, FDDI: typedef struct vdl_ls_cfg
{
V0_MUX_INFO mux_info; /* Streams config info */
AP_UINT16 reserve1; /* reserved */
AP_UINT16 reserve2; /* reserved */
AP_UINT16 test_timeout; /* TEST timeout value in seconds */
AP_UINT16 test_retry_limit; /* TEST retransmission limit */
AP_UINT16 xid_timeout; /* XID timeout value in seconds */
AP_UINT16 xid_retry_limit; /* XID retransmission limit */
AP_UINT16 t1_timeout; /* T1 timeout value in seconds */
AP_UINT16 t1_retry_limit; /* I-frame retransmission limit */
} VDL_LS_CFG;
|
Data for all DLC types: typedef struct v0_mux_info
{
AP_UINT16 dlc_type; /* DLC implementation type */
unsigned char need_vrfy_fixup; /* LS needs verification with */
/* corresponding DLC */
unsigned char num_mux_ids; /* reserved */
AP_UINT32 card_type; /* reserved */
AP_UINT32 adapter_number; /* reserved */
AP_UINT32 oem_data_length; /* reserved */
int mux_ids[5]; /* reserved */
} V0_MUX_INFO;
|
For Token Ring, Ethernet, or FDDI, the address parameter in the link_address structure is replaced by the following: typedef struct tr_address
{
unsigned char mac_address[6]; /* MAC address */
unsigned char lsap_address; /* local SAP address */
} TR_ADDRESS;
|
Supplied
Parameters | |
The application supplies the following parameters: - opcode
AP_DEFINE_LS - ls_name
Name of link station. This is an 8-byte ASCII string, padded
on the right with spaces if the name is shorter than 8 bytes. - def_data.description
A null-terminated text string (0-31 characters followed by
a null character) describing the LS. This string is for information
only; it is stored in the node's configuration file and returned
on the QUERY_LS, QUERY_PU, and QUERY_DOWNSTREAM_PU verbs, but SNAplus2 does
not make any other use of it. - def_data.initially_active
Specifies whether this LS is automatically started when
the node is started. Possible values are: - AP_YES
The LS is automatically started when the node is
started. - AP_NO
The LS is not automatically started; it must be
started manually.
- def_data.react_timer
Reactivation timer for reactivating a failed LS.
If the react_timer_retry parameter below is nonzero, to specify that SNAplus2
should retry activating the LS if it fails, this parameter specifies
the time in seconds between retries. When the LS fails, or when
an attempt to reactivate it fails, SNAplus2 waits for the specified time
before retrying the activation. If react_timer_retry is zero, this parameter is ignored. - def_data.react_timer_retry
Retry count for reactivating a failed LS. This parameter
is used to specify whether SNAplus2 should attempt to reactivate
the LS if it fails while in use (or if an attempt to start the LS
fails). Specify zero to indicate that SNAplus2 should not attempt
to reactivate the LS, or specify the number of retries to be made.
A value of 65,535 indicates that SNAplus2 should
retry indefinitely until the LS is activated. SNAplus2 waits for the time specified by the react_timer parameter above between successive retries. If the
retry count is reached without successfully reactivating the LS,
or if a STOP_LS is issued while SNAplus2 is retrying the activation,
no further retries are made; the LS remains inactive unless START_LS
is issued for it. If the auto_act_supp parameter is set to AP_YES,
the reactivation timer fields are ignored; if the link fails, SNAplus2
does not attempt to reactivate it until the user application that
was using the session attempts to restart the session. - def_data.port_name
Name of port associated with this link station.
This is an 8-byte ASCII string, padded on the right with spaces
if the name is shorter than 8 bytes, which must match the name of
a defined port. - def_data.adj_cp_name
Fully qualified name of the adjacent CP for this
LS. If the adj_cp_type parameter below is set to AP_NETWORK_NODE or AP_END_NODE,
and preassigned TG numbers are being used, set this parameter to
the CP name defined at the adjacent node; if the adjacent node sends
a CP name during XID exchange, it will be checked against this value. If adj_cp_type is set to AP_BACK_LEVEL_LEN_NODE, SNAplus2
uses this value only as an identifier; set it to any string (of
the format described below) that does not match other CP names defined
at this node. If adj_cp_type is set to any other value, or if preassigned TG numbers
are not being used, there is no need to specify this parameter;
SNAplus2 will check the CP name only if one is specified. The name is a 17-byte EBCDIC string, padded on the right with
EBCDIC spaces. It consists of a network ID of 1-8 A-string characters,
an EBCDIC dot (period) character, and a network name of 1-8 A-string characters. - def_data.adj_cp_type
Adjacent node type. If the adjacent node is an APPN node, and preassigned TG numbers
are not being used, this is normally set to AP_APPN_NODE,
indicating that the node type is unknown; SNAplus2 will determine
the type during XID exchange. If preassigned TG numbers are being used, you must specify
the node type explicitly. You can also specify it as an additional
security check if preassigned TG numbers are not being used. In
this case, SNAplus2 will reject a connection attempt from the adjacent
node if its node type does not match the one specified here. Use
one of the following values: - AP_APPN_NODE
The node type is unknown. SNAplus2 will determine
the type during XID exchange. - AP_END_NODE
End node, or up-level LEN node (one that includes
the Network Name CV in its XID3). - AP_NETWORK_NODE
Network node. If the adjacent node is not an APPN node, use one of the following
values: - AP_BACK_LEVEL_LEN_NODE
Back-level LEN node (one that does not include the
Network Name CV in its XID3). - AP_HOST_XID3
Host node; SNAplus2 should respond to a polling
XID from the node with a format 3 XID. - AP_HOST_XID0
Host node; SNAplus2 should respond to a polling
XID from the node with a format 0 XID. - AP_DSPU_XID
Downstream PU; SNAplus2 should include XID exchange
in link activation. The dspu_name and dspu_services fields must also be set. - AP_DSPU_NOXID
Downstream PU; SNAplus2 should not include XID exchange
in link activation. The dspu_name and dspu_services fields must also be set.
If you want to run independent LU 6.2 traffic over this LS,
you must set the adj_cp_type parameter to AP_APPN_NODE, AP_END_NODE, AP_NETWORK_NODE,
or AP_BACK_LEVEL_LEN_NODE. - def_data.dest_address.length
Length of the destination address field, as specified
in the following parameter or parameters.
For SDLC: - def_data.dest_address.address
Address of the secondary station on this LS. If the port that owns this LS is used
only for incoming calls (out_link_act_lim on DEFINE_PORT is zero), this parameter is reserved. If the port that owns this LS is switched primary and
is used for outgoing calls (port_type is AP_SWITCHED, ls_role is AP_LS_PRI, and out_link_act_lim on DEFINE_PORT is nonzero), either set this parameter
to 0xFF to accept whatever address is configured
at the secondary station, or set it to a 1-byte value in the range 0x01-0xFE which
must match the value configured at the secondary station. Otherwise, set it to a 1-byte value in the range 0x01-0xFE to
identify the link station. If the port is primary multi-drop (ls_role on DEFINE_PORT is AP_LS_PRI and tot_link_act_lim is greater than 1), this address
must be different for each LS on the port.
For QLLC: - def_data.dest_address.address
Address of the destination node for this LS. This parameter
is used only for SVC outgoing calls (defined by the vc_type parameter in the link-specific data, and by the link
activation limit parameters on DEFINE_PORT); it is ignored for incoming
calls or for PVC. The address is a string of 1-14 characters. The address is
in X.25 (1980) format; later address formats are not supported.
For Token Ring, Ethernet, FDDI: - def_data.dest_address.mac_address
MAC address of adjacent node. If the local and adjacent nodes are on LANs of different types
(one Token Ring or FDDI, the other Ethernet) connected by a bridge,
you will probably need to reverse the bit order of the bytes in
the MAC address. For more information, see “Bit
Ordering in MAC Addresses”. If the two nodes are on the same LAN, or on
LANs of the same type connected by a bridge, no change is required. - def_data.dest_address.lsap_address
Local SAP address of adjacent node.
For all link types: - def_data.auto_act_supp
Specifies whether the link can be activated automatically
when required by a session. Possible values are: - AP_YES
The link can be activated automatically. - AP_NO
The link cannot be activated automatically.
If this parameter is set to AP_YES: The reactivation timer fields are
ignored. If the LS fails, SNAplus2 does not attempt to reactivate
it until a dependent LU application that was using the session attempts
to restart the session; an LS used by independent LUs will not be
reactivated by SNAplus2, and must be restarted manually. If the link is to an APPN node, the LS must have
a preassigned TG number defined (see the following parameter), and cp_cp_sess_support must be set to AP_NO. If either the local node or the adjacent node is
an end node, the LS must also be defined as auto-activatable at
the adjacent node.
- def_data.tg_number
Preassigned TG number. This parameter is used only
if the adjacent node is an APPN node (adj_cp_type is either AP_NETWORK_NODE or AP_END_NODE);
it is ignored otherwise. This TG number is used to represent the link when the link
is activated. The node will not accept any other number from the
adjacent node during activation of this link; if the adjacent node
is using preassigned TG numbers, the same TG number must be defined
by the adjacent node on the adjacent link station. If the local node is a LEN node, or if the adjacent node is
a LEN node and the link is to be auto-activatable, set the TG number
to 1. Otherwise, specify a number in the range 1-20,
or zero to indicate that the TG number is not preassigned and is
negotiated when the link is activated. If a preassigned TG number is defined, the adj_cp_name parameter must also be defined, and the adj_cp_type parameter must be set to either AP_END_NODE or AP_NETWORK_NODE. - def_data.limited_resource
Specifies whether this link station is to be deactivated when
there are no sessions using the link. Link stations on a nonswitched
port cannot be configured as limited resource. Possible values are: - AP_NO
The link is not a limited resource and will not
be deactivated automatically. - AP_NO_SESSIONS
The link is a limited resource and will be deactivated
automatically when no active sessions are using it. - AP_INACTIVITY
The link is a limited resource and will be deactivated
automatically when no active sessions are using it, or when no data
has flowed on the link for the time period specified by the link_deact_timer field.
A limited resource link station may be configured for CP-CP
session support, by setting this field to AP_NO_SESSIONS and cp_cp_sess_support to AP_YES. In this case, if
CP-CP sessions are brought up over the link, SNAplus2 will not treat
the link as a limited resource (and so will not deactivate it). - def_data.solicit_sscp_sessions
Specifies whether to request the adjacent node to initiate
sessions between the SSCP and the local CP and dependent LUs. This
parameter is used only if the adjacent node is an APPN node (adj_cp_type is either AP_NETWORK_NODE or AP_END_NODE);
it is ignored otherwise. If the adjacent node is a host (adj_cp_type is either AP_HOST_XID3 or AP_HOST_XID0),
SNAplus2 always requests the host to initiate SSCP sessions. Possible values are: - AP_YES
Request the adjacent node to initiate SSCP sessions. - AP_NO
Do not request the adjacent node to initiate SSCP
sessions. If the adjacent node is an APPN node and dspu_services is set to a value other than AP_NONE,
this parameter must be set to AP_NO.
- def_data.pu_name
Name of the local PU that uses this link. This parameter
is used only if adj_cp_type is set to AP_HOST_XID3 or AP_HOST_XID0,
or if solicit_sscp_sessions is set to AP_YES; it is ignored otherwise.
This is an 8-byte alphanumeric type-A EBCDIC string (starting with
a letter), padded on the right with EBCDIC spaces. - def_data.disable_remote_act
Specifies whether to prevent activation of the LS
by the remote node. Possible values are: - AP_YES
The LS can only be activated by the local node;
if the remote node attempts to activate it, SNAplus2 will reject
the attempt. - AP_NO
The LS can be activated by the remote node.
- def_data.dspu_services
Specifies the services which the local node will
provide to the downstream PU across this link. This parameter is
used only if the adjacent node is a downstream PU or an APPN node
with solicit_sscp_sessions set to AP_NO; it is reserved
otherwise. Possible values are: - AP_PU_CONCENTRATION
Local node will provide PU concentration for the
downstream PU. The local node must be defined to support PU concentration. - AP_DLUR
Local node will provide DLUR services for the downstream
PU. The local node must be defined to support DLUR. (Not supported
on end node.) - AP_NONE
Local node will provide no services for this downstream
PU.
- def_data.dspu_name
Name of the downstream PU. The name is an 8-byte type-A
EBCDIC string (starting with a letter), padded to the right with
EBCDIC spaces. This parameter is required when both of the following conditions
are true; otherwise, it is reserved: The solicit_sscp_sessions parameter is set to AP_NO The dspu_services parameter is set to AP_PU_CONCENTRATION
- def_data.dlus_name
Name of the DLUS node from which DLUR solicits SSCP
services when the link to the downstream node is activated. This
field is reserved if dspu_services is not set to AP_DLUR. The name is a 17-byte EBCDIC string, right-padded with EBCDIC
spaces. It consists of a network ID of up to 8 A-string characters,
an EBCDIC dot (period) character, and a network name of up to 8
A-string characters. To specify the global default DLUS, defined using the DEFINE_DLUR_DEFAULTS
verb, set this parameter to 17 binary zeros. If this parameter is
set to zeros and there is no global default DLUS, then DLUR will
not initiate SSCP contact when the link is activated. - def_data.bkup_dlus_name
Name of the backup DLUS node from which DLUR solicits
SSCP services if the node specified by dlus_name is not active. This field is reserved if dspu_services is not set to AP_DLUR. The name is a 17-byte EBCDIC string, right-padded with EBCDIC
spaces. It consists of a network ID of up to 8 A-string characters,
an EBCDIC dot (period) character, and a network name of up to 8
A-string characters. To specify the global backup default DLUS, defined using the
DEFINE_DLUR_DEFAULTS verb, set this parameter to 17 binary zeros. - def_data.hpr_supported
This parameter is reserved. - def_data.hpr_link_lvl_error
This parameter is reserved. - def_data.link_deact_timer
Limited resource link deactivation timer, in seconds.
A limited resource link is automatically deactivated if no data
flows over the link for the time specified by this parameter. This
parameter is not used if limited_resource is set to any value other than INACTIVITY. The minimum value is 5; values in the range 1-4 will
be interpreted as 5. The value 0 (zero) indicates that no timeout
is used (the link is not deactivated, as if limited_resource were set to AP_NO. - def_data.default_nn_server
End node: Specifies whether this is a link supporting CP-CP
sessions to a network node that can act as the local node's network
node server. When the local node has no CP-CP sessions to a network
node server and needs to establish them, it checks this parameter
on its defined LSs to find a suitable LS to activate. This allows
you to specify which adjacent NNs are suitable to act as the NN
server (for example, to avoid using NNs that are accessed by expensive
or slow links). Possible values are: - AP_YES
This link supports CP-CP sessions to a network node
that can act as the local node's NN server; the local node can automatically
activate this link if it needs to contact an NN server. The cp_cp_sess_support parameter must be set to AP_YES. - AP_NO
This link should not be automatically activated
in an attempt to contact a network node server.
If the local node is not an end node, this parameter is ignored. - def_data.ls_attributes
This array contains further information about the adjacent
node, as described in the following parameters: - def_data.ls_attributes[0]
Host type. Set this to AP_SNA unless
you are communicating with a host of one of the other types listed
below. Possible values are: - AP_SNA
Standard SNA host. - AP_FNA
Fujitsu Network Architecture (VTAM-F) host. - AP_HNA
Hitachi Network Architecture host.
- def_data.ls_attributes[1]
Network Name CV suppression for a link to a back-level
LEN node. If adj_cp_type is set to AP_BACK_LEVEL_LEN_NODE or AP_HOST_XID3,
specify whether to suppress inclusion of the Network Name CV in
the format 3 XID sent to the LEN node, using one of the following
values: - AP_NO
Include the Network Name CV in the XID. - AP_SUPPRESS_CP_NAME
Do not include the Network Name CV.
If adj_cp_type is set to any other value, this parameter is ignored. - def_data.adj_node_id
Node ID of adjacent node. This is a 4-byte hexadecimal string,
consisting of a block number (three hexadecimal digits) and a node
number (five hexadecimal digits). Set it to zeros to disable node
ID checking. If this link station is defined on a switched port,
the node_id must be unique, and there may only be one null node_id on each switched port. - def_data.local_node_id
Node ID sent in XIDs on this LS. This is a 4-byte hexadecimal
string, consisting of a block number (3 hexadecimal digits) and
a node number (5 hexadecimal digits). Set it to zeros to use the
node ID specified in the DEFINE_NODE verb. - def_data.cp_cp_sess_support
Specifies whether CP-CP sessions are supported.
This parameter is valid only if the adjacent node is an end node
or network node (adj_cp_type is AP_NETWORK_NODE, AP_END_NODE,
or AP_APPN_NODE); it is ignored otherwise. Possible values are: - AP_YES
CP-CP sessions are supported. The solicit_sscp_sessions parameter must be set to AP_NO. - AP_NO
CP-CP sessions are not supported.
- def_data.use_default_tg_chars
Specifies whether the default TG characteristics supplied
on the DEFINE_PORT verb should be used. The TG characteristics apply
only if the link is to an APPN node; this parameter, and the parameters
in the tg_chars structure, are ignored otherwise. Possible values are: - AP_YES
Use the default TG characteristics; ignore the tg_chars structure on this verb. - AP_NO
Use the tg_chars structure on this verb.
- def_data.tg_chars.effect_cap
Actual bits per second rate (line speed). The value
is encoded as a 1-byte floating point number, represented by the
formula 0.1 mmm * 2 eeeee where the bit representation
of the byte is b'eeeeemmm'. Each unit of effective capacity is equal
to 300 bits per second. - def_data.tg_chars.connect_cost
Cost per connect time. Valid values are integer
values in the range 0-255,
where 0 is the lowest cost per connect time and 255 is
the highest. - def_data.tg_chars.byte_cost
Cost per byte. Valid values are integer values in
the range 0-255, where 0 is
the lowest cost per byte and 255 is the highest. - def_data.tg_chars.security
Security level of the network. Possible values are: - AP_SEC_NONSECURE
No security. - AP_SEC_PUBLIC_SWITCHED_NETWORK
Data is transmitted over a public switched network. - AP_SEC_UNDERGROUND_CABLE
Data is transmitted over secure underground cable. - AP_SEC_SECURE_CONDUIT
Data is transmitted over a line in a secure conduit
that is not guarded. - AP_SEC_GUARDED_CONDUIT
Data is transmitted over a line in a conduit that
is protected against physical tapping. - AP_SEC_ENCRYPTED
Data is encrypted before transmission over the line. - AP_SEC_GUARDED_RADIATION
Data is transmitted over a line that is protected
against physical and radiation tapping.
- def_data.tg_chars.prop_delay
Propagation delay: the time that a signal takes
to travel the length of the link. Specify one of the following values,
according to the type of link: - AP_PROP_DELAY_MINIMUM
Minimum propagation delay. - AP_PROP_DELAY_LAN
Delay is less than 480 microseconds (typical for
a LAN). - AP_PROP_DELAY_TELEPHONE
Delay is in the range 480-49,512 microseconds (typical
for a telephone network). - AP_PROP_DELAY_PKT_SWITCHED_NET
Delay is in the range 49,512-245,760 microseconds
(typical for a packet-switched network). - AP_PROP_DELAY_SATELLITE
Delay is greater than 245,760 microseconds (typical
for a satellite link). - AP_PROP_DELAY_MAXIMUM
Maximum propagation delay.
- def_data.tg_chars.user_def_parm_1 through def_data.tg_chars.user_def_parm_3
User-defined parameters, which you can use to include other
TG characteristics not covered by the above parameters. Each of
these parameters must be set to a value in the range 1-255. - def_data.target_pacing_count
Numeric value between 1 and 32,767 inclusive indicating
the desired pacing window size. (The current version of SNAplus2
does not make use of this value.) - def_data.max_send_btu_size
Maximum BTU size that can be sent from this link station.
This value is used to negotiate the maximum BTU size that a pair
of link stations can use to communicate with each other. The value
includes the length of the TH and RH (total 9 bytes) as well as
the RU. Specify a value in the range 265-65,535 (265-4105 for
SDLC). - def_data.ls_role
Link station role. This is normally set to AP_USE_PORT_DEFAULTS,
specifying that the LS role is to be taken from the definition of
the port that owns this LS. If you need to override the port's LS role for an individual
LS, specify one of the following values: - AP_LS_PRI
Primary - AP_LS_SEC
Secondary - AP_LS_NEG
Negotiable
- def_data.max_ifrm_rcvd
The maximum number of I-frames that can be received by
this link station before an acknowledgment is sent. Specify a value
in the range 0-127. If 0 is
specified, the value from DEFINE_QLLC_PORT DEFINE_SDLC_PORTis used. - def_data.dlus_retry_timeout
Reactivation timer for contacting a DLUS. If SNAplus2 fails
to contact the DLUS, this parameter specifies the time in seconds
between retries. Specify a value in the range 0x0001-0xFFFF. - def_data.dlus_retry_limit
The interval in seconds between the second and subsequent
attempts to contact the DLUS specified by the dlus_name and bkup_dlus_name parameters. Specify a value in the range 0x0001-0xFFFE,
or specify 0xFFFF to indicate that SNAplus2 should
retry indefinitely until it contacts the DLUS. The interval between
the first and second attempts is always 1 second. If zero is specified,
then the defaults specified using the DEFINE_DLUR_DEFAULTS verb
are used. This parameter is ignored if the dspu_services parameter is not set to AP_DLUR. - def_data.link_spec_data_len
Length of the link-specific data. The data should
be concatenated to the basic structure.
Link-specific data for SDLC: - mux_info.dlc_type
Type of the DLC. Set this to AP_IMPL_SDLC_SL - contact_timer
Timeout required before a SNRM or XID is retransmitted
in the event of nonacknowledgment (used for primary SDLC only).
This value must be greater than the no response (T1) timeout value no_resp_timer described below. The timer is specified in milliseconds. This timer is also used for special pre-activation polling. - contact_timer_retry
Number of times transmission and retransmission
of a contact frame (such as SNRM) is allowed using the normal poll
timer before SNAplus2 changes to the slow poll timer. A value of 0xFFFF indicates an unlimited
retry count. A value of 0x0001 indicates that
the switch to the slow poll should be made after the first timer
expiry. - contact_timer2
Slow poll contact timer in milliseconds. When the contact
timer retry count expires, SNAplus2 continues to poll using this
timer. This prevents leased (multi-drop) links from being flooded
by poll frames for absent stations. - contact_timer_retry2
The slow poll contact timer retry limit value corresponds
to the number of times transmission and retransmission of a contact
frame (such as SNRM) is allowed on the slow cycle before an outage
message is sent to the DLC user. A value of 0xFFFF indicates an unlimited
retry count. A value of 0x0001 indicates that
an outage should be generated after the first slow poll timer expiry. - disc_timer
Timeout required before a DISC is retransmitted
in the event of nonacknowledgment (used for primary SDLC only).
The timer is specified in milliseconds. - disc_timer_retry
The Disconnect timer retry limit value corresponds
to the number of times transmission and retransmission of a DISC
is allowed. A value of 0xFFFF indicates an unlimited
retry count. A value of 0x0001 indicates that
an outage should be generated after the first timer expiry. - nve_poll_timer
Timeout required before an adjacent secondary station (which
has previously been removed from the polling list because it has
no data to send) is reinserted into the polling list. The timer
is specified in milliseconds. - nve_poll_timer_retry
Number of times a station is removed from the polling list
on the normal poll timer before SNAplus2 switches to using the slow
poll timer. A value of 0xFFFF indicates an unlimited
retry count. A value of 0x0001 indicates that
the switch to the slow poll should be made after the first timer
expiry. - nve_poll_timer2
The slow negative poll timer in milliseconds. When
the negative poll timer retry count expires, SNAplus2 continues
to poll using this timer. This prevents leased (multi-drop) links
from being flooded by poll frames for idle stations. - nve_poll_timer_retry2
Number of times a station is removed from the polling list
on the slow poll cycle before an outage message is sent to the HLS.
Specify a value in the range 1-65,535. This
value is normally set to 0xFFFF, indicating infinite retry. - no_resp_timer
The maximum time a primary station waits (after having
sent a frame with a poll bit) for a response frame before trying
to poll another station. This timer is restarted when a frame without
the F-bit is received and stopped only when a frame with an F-bit
is received. The timeout should be set to a value not less than
twice the transmission time for the longest I-frame plus adjacent
station frame processing time. The timer is specified in milliseconds. - no_resp_timer_retry
Number of times an adjacent secondary station is
seen to fail to respond before the primary sends an outage message
to the DLC user. A value of 0xFFFF indicates an unlimited
retry count. A value of 0x0001 indicates that
an outage should be generated after the first timer expiry. - rem_busy_timer
Time allowed for an adjacent secondary station to
be in an RNR condition. This is used in conjunction with the retry
limit value to provide the overall time before an outage message
is sent. The timer is specified in milliseconds. - rem_busy_timer_retry
Used in conjunction with the timeout value to provide the
overall timeout before an outage message is sent. A value of 0xFFFF is used to indicate an
unlimited retry count. A value of 0x0001 indicates
that an outage should be generated after the first timer expiry. - rr_timer
The time in milliseconds to wait before turning
the poll bit around when the SDLC component has no work to do. This field may be set to zero, or to a nonzero value if the immediate
turn-around causes hardware problems on the link. Higher values
can also be used to optimize link usage, because often the higher-level
software will generate data in response to the data contained in
an I-frame carrying the poll bit; the pause allows the data to be
received and processed. - poll_frame
The frame to use for pre-activation polling. This
is normally XID, indicating that polling is in the control of the
DLC user. However, when SNAplus2 is primary talking to an old secondary
implementation, it may be necessary to poll using some other frame.
Possible values are: XID, DISC, SNRM, SNRME, TEST. - poll_on_iframe
Specifies whether this link station is permitted
to send the poll bit on an I-frame. This allows SNAplus2 to work
with certain SDLC implementations which do not handle receipt of
I-frames carrying the poll bit. Possible values are: - AP_YES
This link station is allowed to send the poll bit
on an I-frame. - AP_NO
This link station is not allowed to send the poll
bit on an I-frame.
- stub_spec_data_len
Length of the Stub specific data that follows. Set
this to size of (STUB_SPEC_DATA). - stub_spec_data
Stub specific data. These fields are used only for switched
outgoing links. The values specified in this structure override
those defined in the Stub specific data for the port that owns this
LS; where fields in this structure are shown as reserved, the values
from the port are used instead. For switched incoming links or leased
links, the parameters defined in the Stub specific data for the
port (not for the LS) are used. The structure contains the following fields: - stub_spec_data.opt1
HMOD port options flag 1. Set the appropriate bits
of this field as follows (bit 7 is the most significant bit): - bit 6
Use NRZI (NRZ if not set) - bit 4
Line is full-duplex (half-duplex if not set)
The remaining bits are reserved. - stub_spec_data.opt2
Reserved. - stub_spec_data.linesp
The line speed for the line used on this port. For example, 2400 (0x00000960)
for a 2400 baud line. Valid values are in the range 600-38,400 baud.
The exact meaning of this parameter depends on the value set on the physical_link parameter. If physical_link is set to SDLC_PL_X21, then
the stub_spec_data.linesp parameter is ignored. If physical_link is set to SDLC_PL_V25 or SDLC_PL_SMART_MODEM,
then the value of the stub_spec_data.linesp parameter is the speed at which the dial string is
sent to the modem. If physical_link is set to any other value, then the value of the stub_spec_data.linesp parameter is the speed of data transfer, only valid
if external clocking is specified.
- stub_spec_data.rcv_pool_size
Reserved. - stub_spec_data.poll_wait
Reserved. - stub_spec_data.hmod_data_len
Length of the dial data string that follows (in
the hmod_data parameter). If no dial data is specified, set this
parameter to zero. - stub_spec_data.hmod_data
Dial data for outgoing calls. This parameter applies only
to switched links; it is reserved if the port associated with this
LS is defined to be nonswitched. This is an ASCII string, specifying the dial string to be passed
to the modem to initiate the call. Support for dial data depends
on the SDLC adapter and modem that you are using; if they do not
support dial data, set this parameter to a null string. Link-specific data for QLLC:
- mux_info.dlc_type
Type of the DLC. Set this to AP_IMPL_NLI_QLLC. - vc_type
The Virtual Circuit type of the LS. Possible values
are: - VQL_SVC
Switched Virtual Circuit - VQL_PVC
Permanent Virtual Circuit
If you define both SVC and PVC LSs between the same local
node and remote node, unpredictable results may occur if the SVC
LS is started first (since it may not be possible to match the incoming
call to the correct LS). To avoid these problems, ensure that PVC
LSs are activated before any SVC LSs between the same pair of nodes. - req_rev_charge
Specifies whether X.25 should request reverse charging when
attempting to contact the remote system using this LS. Possible
values are: - AP_YES
Request reverse charging. - AP_NO
Do not request reverse charging. If the X.25 network
does not support facilities negotiation, this parameter must be
set to AP_NO.
If the X.25 network does not support facilities negotiation,
this parameter must be set to AP_NO (also see
the fac parameter below). - loc_packet
Packet size used for sending data from the local
station to the remote station. The actual size used is 2 to the power
of loc_packet; for example, setting loc_packet to 7 indicates a packet size of
2 to the power of 7, which is 128. To indicate using the default
packet size for the network, set this parameter to zero. Check with
the administrator of your X.25 network to determine the correct
value to use. - rem_packet
Packet size used for receiving data from the remote station.
The actual size used is 2 to the power of rem_packet (as for loc_packet above). To indicate using the default packet size for
the network, set this parameter to zero. Check with the administrator
of your X.25 network to determine the correct value to use. - loc_wsize
Window size used for sending data from the local station
to the remote station. Specify a value in the range 1-7,
or zero to indicate using the default window size for the network.
Check with the administrator of your X.25 network to determine the
correct value to use. - rem_wsize
Window size used for receiving data from the remote station.
Specify a value in the range 1-7,
or zero to indicate using the default window size for the network. Check
with the administrator of your X.25 network to determine the correct
value to use. - fac_len
Length of the additional X.25 facilities data that follows
(in the fac parameter). If no additional data is required, specify
zero. If the X.25 network does not support facilities negotiation,
specify zero and see the fac parameter below for more information. - fac
If the X.25 provider software is configured to allow
flow control negotiation, SNAplus2 includes information about reverse
charging options, packet sizes, and window sizes in the facilities
data sent to the remote system. If your X.25 network or the remote
system requires any other facilities data in addition to the above
parameters, specify it using this parameter. Check with the administrator
of your X.25 network, or the administrator of the remote system,
to determine what to specify in this parameter. If the X.25 network does not support facilities negotiation,
or if you do not want to use it, ensure that the X.25 provider software
is configured not to allow flow control negotiation. In this case,
the parameters req_rev_charge-rem_wsize above must all be set to use the network's default
values, and fac_len must be set to zero. - retry_limit
Number of times to retry sending a QXID, QSM, or QDISC
message if no response is received within the time specified by retry_timeout below. Range is 1-255. If vc_type above is set to VQL_PVC, this parameter
is ignored for QXID messages; XID sending is retried indefinitely
(so that an initially active LS can wait indefinitely for the remote
station to become active). - retry_timeout
Timeout in seconds for QXID, QSM, or QDISC messages.
A message will be retried (up to the number of times specified by retry_limit above) if no response is received within this time.
Range is 1-255. - idle_timeout
Timeout in seconds used to detect a completely idle line.
This value is used during connect processing for SVCs when the local
station is secondary and waiting for XIDs. If no message is received
in this time, SNAplus2 assumes that the remote station has failed. Range is 1-255. This
field is ignored if vc_type above is set to VQL_PVC. - pvc_id
PVC identifier. Set this to a decimal number to
identify which PVC (from the range of PVCs defined for your X.25
provider software) is to be used for this LS. This field is reserved
if vc_type above is set to VQL_SVC. - sn_id_len
Length of the subnet identifier that follows (in
the sn_id parameter). Set this parameter to 1 for
a single-port card, or 3 for a multi-port card,
to match the length of the sn_id parameter as described below. - sn_id
Subnet identifier: this parameter identifies the physical
connection to the X.25 network. Set it to a character string that matches the final character(s)
of the X.25 driver name, as follows: If you have more than one X.25 adapter
card installed in the HP-UX computer, set the first byte of this
parameter to the ASCII character 0 (zero) to use
the first card, the ASCII character 1 (one) to use
the second, and so on. If you have only one X.25 adapter card, set the
first byte of this parameter to the ASCII character 0 (zero)
. If the card is a multi-port card, set the second
byte to the ASCII character p, and the third
byte to the ASCII character 1 (one) to indicate
the first port on the card, the ASCII character 2 to
indicate the second, and so on. For example, 0p2 indicates
the second port on the first (multi-port) card.
The parameter must be set to the ASCII character value 0 or 1,
not to the numeric value zero or one. - cud_len
Length of the Call User Data that follows (in the cud parameter). - cud
Call User Data: this parameter identifies the protocol to
be used over the underlying X.25 virtual circuit. For most implementations,
this should be set to a single hex byte 0xC3,
indicating QLLC. Some remote systems may require additional bytes;
check with the System Administrator of the remote system.
DLC-specific data for Token Ring, Ethernet, FDDI: - mux_info.dlc_type
Type of the DLC. Possible values are: - AP_IMPL_TR_DLPI
Token Ring - AP_IMPL_ETHER_DLPI
Ethernet - AP_IMPL_FDDI_DLPI
FDDI
- test_timeout
Timeout required before a TEST frame is retransmitted
when trying to contact a remote station. The timer is specified
in milliseconds. Higher values may be needed if the remote station
is on a separate Token Ring connected by a bridge. - test_retry_limit
The TEST retry limit value corresponds to the number of
times transmission and retransmission of a TEST frame is allowed.
This count includes the initial transmission; that is, a value of 1 indicates “transmit once
but do not retry”. Higher values may be needed if the remote
station is on a separate Token Ring connected by a bridge. - xid_timeout
Timeout required before an XID is retransmitted
when trying to contact a remote station. The timer is specified
in milliseconds. Higher values may be needed if the remote station
is on a separate Token Ring connected by a bridge. - xid_retry_limit
The XID retry limit value corresponds to the number
of times transmission and retransmission of an XID is allowed. This
count does not include the initial transmission; that is, a value
of 1 indicates “transmit once and then
retry once”. Higher values may be needed if the remote station
is on a separate Token Ring connected by a bridge. - t1_timeout
Timeout required before an I-frame is retransmitted
if no response is received. The timer is specified in milliseconds.
Higher values may be needed if the remote station is on a separate
Token Ring connected by a bridge. Some systems may provide alternative methods of configuring
the LLC2 stack, in which case this parameter may be ignored; check
with your SNAplus2 supplier. - t1_retry_limit
The T1 retry limit value corresponds to the number
of times transmission and retransmission of an I-frame is allowed.
The minimum is 1. Higher values may be needed
if the remote station is on a separate Token Ring connected by a
bridge. Some systems may provide alternative methods of configuring
the LLC2 stack, in which case this parameter may be ignored; check
with your SNAplus2 supplier.
Returned
Parameters: Successful Execution | |
If the verb executes successfully, SNAplus2 returns the following parameters: Returned
Parameters: Parameter Check | |
If the verb does not execute because of a parameter error,
SNAplus2 returns the following parameters: - primary_rc
AP_PARAMETER_CHECK - secondary_rc
Possible values are: - AP_CANT_MODIFY_PORT_NAME
The ls_name parameter matched the name of an existing LS, but the port_name parameter did not match the existing definition. You
cannot modify the port name when changing the definition of an existing
LS. - AP_DEF_LINK_INVALID_SECURITY
The tg_chars.security parameter was not set to a valid value. - AP_INVALID_AUTO_ACT_SUPP
The auto_act_supp parameter was not set to a valid value, or was set
to AP_YES when cp_cp_sess_support was also set to AP_YES. - AP_INVALID_CP_NAME
The adj_cp_name parameter contained a character that was not valid,
was not in the correct format, or was not specified when required. - AP_INVALID_LIMITED_RESOURCE
The limited_resource parameter was not set to a valid value. - AP_INVALID_LINK_NAME
The ls_name parameter contained a character that was not valid. - AP_INVALID_LS_ROLE
The ls_role parameter was not set to a valid value. - AP_INVALID_NODE_TYPE
The adj_cp_type parameter was not set to a valid value. - AP_INVALID_PORT_NAME
The port_name parameter did not match the name of any defined port. - AP_INVALID_PU_NAME
The pu_name parameter did not match the name of any defined PU,
or was set when not expected. - AP_INVALID_DSPU_NAME
The dspu_name parameter did not match the name of any defined PU,
or was set when not expected. - AP_INVALID_DSPU_SERVICES
The dspu_services parameter was not set to a valid value, or was set when
not expected. - AP_INVALID_DSPU_NAME
A reserved parameter was set to a nonzero value. - AP_INVALID_DSPU_SERVICES
A reserved parameter was set to a nonzero value. - AP_INVALID_SOLICIT_SSCP_SESS
The solicit_sscp_sess parameter was not set to a valid value. - AP_INVALID_TARGET_PACING_CNT
The target_pacing_count parameter was not set to a valid value. - AP_INVALID_DLUS_NAME
The dlus_name parameter contained a character that was not valid
or was not in the correct format. - AP_INVALID_BKUP_DLUS_NAME
The bkup_dlus_name parameter contained a character that was not valid
or was not in the correct format. - AP_HPR_NOT_SUPPORTED
The hpr_supported parameter was set to AP_YES,
but the node does not support HPR. - AP_INVALID_TG_NUMBER
The TG number supplied was not in the valid range. - AP_MISSING_CP_NAME
A TG number was defined, but no CP name was supplied. - AP_MISSING_CP_TYPE
A TG number was defined, but no CP type was supplied. - AP_MISSING_TG_NUMBER
The link was defined to be auto-activated, but no
TG number was supplied. - AP_PARALLEL_TGS_NOT_SUPPORTED
This node cannot support more than one LS defined
between it and the same adjacent node. - AP_INVALID_DLUS_RETRY_LIMIT
The value specified for dlus_retry_limit was not valid. - AP_INVALID_DLUS_RETRY_TIMEOUT
The value specified for dlus_retry_timeout was not valid. - AP_INVALID_LS_ROLE
The value specified for the ls_role parameter is not valid. - AP_INVALID_BTU_SIZE
The value specified for the max_send_btu_size parameter was not valid. - AP_INVALID_MAX_IFRM_RCVD
The value specified for the max_ifrm_rcvd parameter was not valid.
Appendix A “Common
Return Codes” lists further
secondary return codes associated with AP_PARAMETER_CHECK,
which are common to all NOF verbs. Returned
Parameters: State Check | |
If the verb does not execute because of a state error, SNAplus2
returns the following parameters. - primary_rc
AP_STATE_CHECK - secondary_rc
Possible values are: - AP_DUPLICATE_CP_NAME
A link to the CP name specified in the adj_cp_name parameter has already been defined. - AP_DUPLICATE_DEST_ADDR
A link to the destination address specified in the address parameter has already been defined. - AP_DUPLICATE_ADJ_NODE_ID
The adj_node_id (node ID of adjacent node) has already been defined
in another link station. - AP_INVALID_LINK_NAME
The link station value specified in the ls_name parameter was not valid. - AP_INVALID_NUM_LS_SPECIFIED
The number of link stations specified was not valid. - AP_LOCAL_CP_NAME
The name specified for the adj_cp_name parameter is identical to the local CP name. - AP_LS_ACTIVE
The link station specified in the ls_name parameter is currently active. - AP_PU_ALREADY_DEFINED
The PU specified in the pu_name parameter has already been defined. - AP_DSPU_ALREADY_DEFINED
The downstream PU specified in the dspu_name parameter has already been defined. - AP_DSPU_SERVICES_NOT_SUPPORTED
AP_PU_CONCENTRATION or AP_DLUR has
been specified on the dspu_services parameter, but the node does not support it. - AP_DUPLICATE_TG_NUMBER
The TG number specified in the tg_number parameter has already been defined. - AP_TG_NUMBER_IN_USE
The TG number specified for the tg_number parameter is already being used by another LS.
Appendix A “Common
Return Codes” lists further
secondary return codes associated with AP_STATE_CHECK,
which are common to all NOF verbs. Returned
Parameters: Other Conditions | |
Appendix A “Common
Return Codes” lists further
combinations of primary and secondary return codes that are common
to all NOF verbs. Bit
Ordering in MAC Addresses | |
Ethernet LANs use a different representation of MAC addresses
from that used by Token Ring and FDDI; the order of the bits in
each byte of the address on Ethernet is the reverse of the order
on Token Ring. Normally, the local and remote nodes are on the same
LAN, or on LANs of the same type connected by a bridge; in this
case, they will both use the same representation of the MAC address,
and no conversion is required. If the two nodes are on LANs of different types (one Ethernet,
the other Token Ring or FDDI) connected by a bridge, you will normally
need to reverse the bit order of each byte of the address when specifying
a remote MAC address. To do this, take the following steps: List the MAC address as six bytes, each byte
represented by two hexadecimal digits. List the MAC address as six bytes, each byte represented
by two hexadecimal digits. Convert each digit as shown below: Table 3-1 Title not available (Bit
Ordering in MAC Addresses) | 0 → 0 | 8 → 1 | | 1 → 8 | 9 → 9 | | 2 → 4 | A → 5 | | 3 → C | B → D | | 4 → 2 | C → 3 | | 5 → A | D → B | | 6 → 6 | E → 7 | | 7 → E | F → F |
Table 3-2 Example of Bit Ordering in a MAC Address | Original address | 1A | 2B | 3C | 4D | 5E | 6F | | Swap digits | A1 | B2 | C3 | D4 | E5 | F6 | | Convert
digits (the bit-reversed form of the original address) | 58 | D4 | 3C | B2 | 7A | F6 |
|
Printable version
