NAME

idn - Inter-Domain Network device driver

DESCRIPTION

idn is a multi-thread, loadable, clonable, STREAMS-based pseudo driver that supports the connectionless Data Link Provider Interface, dlpi(7P), over the Enterprise 10000 Gigplane-XB Interconnect. This connection is permitted only between domains within the same Enterprise 10000 server.

The driver provides one to 32 logical network interfaces. One or more of these interfaces may be connected to one or more dynamic system domains that have been previously linked to the local domain via the domain_link(1M) command. (See domain_link(1M) in the Ultra Enterprise 10000 SSP 3.1 Reference.) The driver works in conjunction with the SSP to perform domain linking and unlinking, along with automated linking upon host bootup.

The cloning character-special device /dev/idn is used to access all IDN services provided by the system.

idn ( 7 ) idn and DLPI

The idn driver is a "style 2" Data Link Service provider. All M_PROTO and M_PCPROTO type messages are interpreted as DLPI primitives. An explicit DL_ATTACH_REQ message by the user is required for idn to associate the opened stream with a particular device (ppa). The ppa ID is interpreted as an unsigned long and indicates the corresponding device instance (unit) number. The error DL_ERROR_ACK is returned by the driver if the ppa field value does not correspond to a valid device instance number for the system. The device is initialized on first attach and de-initialized (stopped) on last detach.

The values returned by the driver in the DL_INFO_ACK primitive in response to the DL_INFO_REQ from the user are as follows:

The maximum SDU is configurable via ndd(1M) and has the range of 512 bytes to 512K bytes. The default value is 16384 bytes.

The minimum SDU is 0.

The dlsap address length is 8.

The MAC type is DL_ETHER.

The sap length value is -2, meaning the physical address component is followed immediately by a 2-byte sap componenet within the DLSAP address.

The service mode is DL_CLDLS.

No optional quality of service (QOS) support is included at present so the QOS fields are 0.

The provider style is DL_STYLE2.

The version is DL_VERSION_2.

The broadcast address value is Ethernet/IEEE broadcast address (0xFFFFFF). Note that IDN supports broadcast by issuing messages to each target individually. IDN is inherently a point-to-point network between domains. Once in the DL_ATTACHED state, the user must send a DL_BIND_REQ to associate a particular SAP (Service Access Pointer) with the stream. The idn driver interprets the sap field within the

DL_BIND_REQ as an Ethernet "type" therefore valid values for the sap field are in the [0 -0xFFFF] range. Only one Ethernet type can be bound to the stream at any time.

If the user selects a sap with a value of 0 ,the receiver will be in 802.3 mode. All frames received from the media having a "type" field in the range [0 -1500 ]are assumed to be 802.3 frames and are routed up all open Streams which are bound to sap value 0 . If more than one Stream is in "802.3 mode" then the frame will be duplicated and routed up multiple Streams as DL_UNITDATA_IND messages.

In transmission, the driver checks the sap field of the DL_BIND_REQ if the sap value is 0 , and if the destination type field is in the range [0 -1500 ]. If either is true, the driver computes the length of the message, not including initial M_PROTO mblk (message block), of all subsequent DL_UNITDATA_REQ messages and transmits 802.3 frames that have this value in the MAC frame header length field.

The driver also supports raw M_DATA mode. When the user sends a DLIOCRAW ioctl, the particular Stream is put in raw mode. A complete frame along with a proper ether header is expected as part of the data.

The idn driver DLSAP address format consists of the 6 byte physical (Ethernet) address component followed immediately by the 2 byte sap (type) component producing an 8-byte DLSAP address. Applications should not hardcode to this particular implementation-specific DLSAP address format but use information returned in the DL_INFO_ACK primitive to compose and decompose DLSAP addresses. The sap length, full DLSAP length, and sap/physical ordering are included within the DL_INFO_ACK. The physical address length can be computed by subtracting the sap length from the full DLSAP address length or by issuing the DL_PHYS_ADDR_REQ to obtain the current physical address associated with the stream.

Once in the DL_BOUND state, the user may transmit frames on the IDN by sending DL_UNITDATA_REQ messages to the idn driver. The idn driver will route received IDN frames up all those open and bound streams having a sap which matches the Ethernet type as DL_UNITDATA_IND messages. Received IDN frames are duplicated and routed up multiple open streams if necessary. The DLSAP address contained within the DL_UNITDATA_REQ and DL_UNITDATA_IND messages consists of both the sap (type) and physical (Ethernet) components.

idn Primitives

In addition to the mandatory connectionless DLPI message set the driver additionally supports the following primitives.

The DL_ENABMULTI_REQ and DL_DISABMULTI_REQ primitives enable/disable reception of individual multicast group addresses. A set of multicast addresses may be iteratively created and modified on a per-stream basis using these primitives. These primitives are accepted by the driver in any state following DL_ATTACHED .

The DL_PROMISCON_REQ and DL_PROMISCOFF_REQ primitives with the DL_PROMISC_PHYS flag set in the dl_level field enables/disables reception of all ("promiscuous mode") frames on the media including frames generated by the local domain. When used with the DL_PROMISC_SAP flag set this enables/disables reception

of all sap (Ethernet type) values. When used with the DL_PROMISC_MULTI flag set this enables/disables reception of all multicast group addresses. The effect of each is always on a per-stream basis and independent of the other sap and physical level configurations on this stream or other streams.

The DL_PHYS_ADDR_REQ primitive return the 6 octet Ethernet address currently associated (attached) to the stream in the DL_PHYS_ADDR_ACK primitive. This primitive is valid only in states following a successful DL_ATTACH_REQ .

The DL_SET_PHYS_ADDR_REQ primitive is not allowed by the idn driver as the driver maintains point-to-point domain address information in the address in order to direct packets to the correct destination.

NOTES

The driver supports a set of tuneable parameters. The list can be retrieved via ndd(1M).

FILES

/dev/idn idn special character device.

idn ( 7 ) SEE ALSO

Inter-Domain Network User's Guide

domain_link(1M), domain_unlink(1M) in the Ultra Enterprise 10000 SSP Reference

Manual

ndd(1M) in man Pages(1M): System Administration Commands of the SunOS Reference Manual.

dlpi(7P), qe(7P) in man Pages(7): Device and Network Interfaces of the SunOS Reference Manual.