| Document revision date: 30 March 2001 | |
![]() |
|
|
|
| Previous | Contents | Index |
Gigabit Ethernet (802.3z) is an extension of the IEEE 802.3 standard. It runs over fiber-optic cabling and twisted-pair wiring. It increases the data transmission rate to 1000Mbps. The frame formats are identical to Ethernet and Fast Ethernet which allows good interoperability across these technologies. Gigabit Ethernet is suitable as a high-speed backbone interconnect but may be used to connect high-performance workstations or systems that need the increased bandwidth.
Table 1-4 shows the types of cabling used for Gigabit Ethernet.
| Cable | Description |
|---|---|
| 1000Base-SX | Works with fiber optic cabling. Used mainly for shorter backbone applications. With multimode, it supports distances of up to 550 meters. |
| 1000Base-LX | Works with fiber optic cabling. Used mainly for longer single-mode building of fiber backbones and single-mode campus backbones. With single mode, it supports distances of up to 5 kilometers. |
| 1000Base-CX | Works with shielded copper cabling. Used mainly for interconnection of equipment clusters where the physical interface is short. It supports, for example, a switching closet or computer room with interconnections to 25-meter distances. |
| 1000BaseT | Works with unshielded copper cabling. Used mainly for horizontal copper cabling applications. It supports a signal transmission over four pairs of category 5 unshielded twisted pair (UTP), covering distances up to 100 meters, or networks with a diameter of 200 meters. |
OpenVMS supports the DEGPA Gigabit Ethernet LAN controller on Alpha
PCI-based systems.
1.6 LAN ATM Network Support (Alpha Only)
LAN ATM implements LAN emulation and Classical IP over an ATM network.
The following sections present LAN emulation features, components, and
topology.
1.6.1 LAN Emulation over an ATM Network (Alpha Only)
OpenVMS supports LAN emulation for Ethernet over asynchronous transfer mode (ATM) networks. ATM is a switched, connection-oriented mode of transfer, unlike Ethernet which is a shared, connectionless protocol medium.
The ATM protocol communicates by first establishing endpoints between two computers with a virtual circuit (VC) through one or more ATM switches. ATM then provides a physical path for data flow between the endpoints by either a permanent virtual circuit (PVC), or a switched virtual circuit (SVC).
Permanent Virtual Circuits (PVCs)
Permanent Virtual Circuits are set up and torn down by prior arrangement. They are established manually by a user before the sending of any data between endpoints on a network. Some PVCs are defined directly on the switch; others are predefined for use in managing switched virtual circuits (SVCs).
Switched Virtual Circuits (SVC)
Switched virtual circuits require no operator interaction to create and
manage connections between endpoints. Software sets up and tears down
connections dynamically as they are needed through the request of an
endpoint.
1.6.1.1 LAN Emulation Components (Alpha Only)
LAN emulation over an ATM network allows existing applications to run essentially unchanged while also allowing the applications to run on computers directly connected to the ATM network. The LAN emulation hides the underlying ATM network at the media access control (MAC) layer, which provides device driver interfaces.
Table 1-5 shows the four components that make up a LAN emulation over ATM network. Of the four components, OpenVMS supports only the LAN emulation client (LEC).
| Component | Function |
|---|---|
| LAN emulation client (LEC) | Provides a software driver that runs on a network client and enables LAN clients to connect to an ATM network. |
| LAN emulation server (LES) | Maintains a mapping between LAN and ATM addresses by resolving LAN media access control (MAC) addresses with ATM addresses. |
| Broadcast and Unknown Server (BUS) | Maintains connections with every LAN emulation client (LEC) in the network. For broadcast messages, the BUS sends messages to every attached LEC. The LECs then forward the message to their respectively attached LANs. For multicast messages, the BUS sends messages to only those LECs that have devices in the multicast group. For a LEC that wants to send a regular message whose destination MAC address is unknown, the BUS can be used to determine this address. |
| LAN emulation Configuration Server (LECS) | Provides a service for LAN emulation clients by helping to determine which emulated LAN each of the LEC's registered users should join, since each client can specify which emulated LAN to join. |
The LEC exists on all ATM-attached computers that participate in the
LAN emulation configuration. LEC provides the ATM MAC-layer
connectionless function that is transparent to the LAN-type
applications. The LEC, LES, and BUS can exist on one ATM-attached
computer or on separate computers. The server functions usually reside
inside an ATM switch, but can be implemented on client systems.
1.6.1.2 LAN Emulation Topology (Alpha Only)
Figure 1-1 shows the topology of a typical emulated LAN over ATM.
Figure 1-1 Emulated LAN Topology
Classical IP (CLIP) implements a new data-link level device that has the same semantics as an Ethernet interface (802.3). This interface is used by a TCP/IP protocol to transmit 802.3 (IEEE Ethernet) frames over an ATM network. The model that OpenVMS Alpha follows for exchanging IP datagrams over ATM is based on RFC 1577 (Classical IP over ATM).
For information on using LANCP commands to manage Classical IP, refer
to the OpenVMS System Management Utilities Reference Manual: A--L.
1.7 Supporting and Configuring LAN Emulation over ATM (Alpha Only)
OpenVMS provides LAN Emulation Client (LEC) support over three ATM LAN devices: ATMworks 350, ATMworks 351, and ATMworks 750. The LAN Emulation Client software supports IEEE/802.3 Emulated LANs, and UNI 3.0 or UNI 3.1. It also supports the maximum frame sizes of 1516, 4544, and 9234 bytes.
The ATMworks 350 is a 155 megabits per second (Mb/s) ATM device for PCI-bus systems. SYS$HWDRIVER.EXE provides support for this adapter.
The ATMworks 351 is a 155 megabits per second (Mb/s), full-duplex ATM device that enables systems with peripheral component interconnect (PCI) slots to communicate over an ATM network. The ATMworks 351 driver is supported by the SYS$ATMWORKS351 port driver which has a device name HWcu, where c is the controller and u is the unit number, as for example, HWA0.
The ATMworks 750 is a 155 Mb/s ATM device for Turbochannel systems with the exception of the DEC 3000-300. SYS$HCDRIVER.EXE provides support for this adapter.
SYS$ELDRIVER.EXE provides the Emulated LAN support, and it provides the means for communicating over the LAN ATM. The device type for the Emulated LAN device is DT$_EL_ELAN.
The device name for the Emulated LAN is:
ELcu
where c is the controller and u is the unit number (for example, ELA0).
|
The ATM drivers have the capability of operating with either
synchronous optical network (SONET) or synchronous digital hierarchy
(SDH) framing. Setting the system parameter, LAN_FLAGS, to 1 enables
SDH framing. Setting bit 0 of the system parameter, LAN_FLAGS, to 0
enables SONET framing (default). For this to take affect, the system
parameter must be specified correctly before the ATM adapter driver is
loaded.
1.7.2 Booting (Alpha Only)
OpenVMS Alpha does not support ATM adapters as boot devices.
1.7.3 Configuring an Emulated LAN (ELAN) (Alpha Only)
The LANCP utility sets up an Emulated LAN (ELAN). If the ELAN is defined in the permanent database, these settings take affect at boot time. To define the commands in the permanent database for specific adapters, you invoke the DEFINE DEVICE commands. Once these commands define the adapters in the permanent database, the ELAN can be started during system startup.
You can also invoke the LANCP SET commands to start up an ELAN after the system is booted.
The following example shows the DEFINE DEVICE commands that define the adapter in the permanent database.
$ mcr lancp
LANCP> define device ela0/elan=create
LANCP> define device ela0/elan=(parent=hwa0,type=csmacd,size=1516)
LANCP> define device ela0/elan=(descr="An ATM ELAN")
LANCP> define device ela0/elan=enable=startup
LANCP> list dev ela0/param
Device Characteristics, Permanent Database, for ELA0:
Value Characteristic
----- --------------
HWA0 Parent ATM device
"An ATM ELAN" Emulated LAN description
1516 Emulated LAN packet size
CSMA/CD Emulated LAN type
Yes Emulated LAN enabled for startup
LANCP> exit
$
|
The following example shows the SET DEVICE commands required for setting up an ELAN with the desired parameters. Note that some of the commands generate a console message.
$ mcr lancp
LANCP> set dev ela0/elan=create
%%%%%%%%%%% OPCOM 26-MAR-1996 16:57:12.89 %%%%%%%%%%%
Message from user SYSTEM on ALPHA1
LANACP LAN Services
Found LAN device ELA0, hardware address 00-00-00-00-00-00
LANCP> set dev ela0/elan=(parent=hwa0,type=csmacd,size=1516)
LANCP> set dev ela0/elan=(descr="An ATM ELAN")
LANCP> set dev ela0/elan=enable=startup
%ELDRIVER, LAN Emulation event at 26-MAR-1996 16:57:28.78
%ELDRIVER, LAN Emulation startup: Emulated LAN 1 on device ELA0
LANCP> sho dev ela/char
Device Characteristics ELA0:
Value Characteristic
----- --------------
Normal Controller mode
External Internal loopback mode
CSMA/CD Communication medium
16 Minimum receive buffers
32 Maximum receive buffers
No Full duplex enable
No Full duplex operational
Unspecified Line media
10 Line speed (megabits/second)
CSMA/CD Communication medium
"HWA0" Parent ATM Device
"An ATM ELAN" Emulated LAN Description
3999990000000008002B LAN Emulation Server ATM Address
A57E80AA000302FF1300
Enabled Emulated LAN State
LANCP> exit
$
|
For information about using LANCP and system manager commands with
qualifiers for LAN emulation over ATM networks, refer to the
OpenVMS System Management Utilities Reference Manual: A--L, and OpenVMS System Manager's Manual.
1.7.4 Configuring ATM hardware
The following is a specific example of setting up the GIGAswitch/ATM for LAN Emulation (ELAN). The OpenVMS LAN Emulation Client (LEC) software adheres to the ATM forum LAN Emulation V1.0 specification. Hence, it works with any ATM switch that supports the ELAN server software of the LAN emulation server (LES), broadcast and unknown server (BUS), and LAN emulation configuration server (LECS).
For more information about using the GIGAswitch/ATM, see
GIGAswitch/ATM System Management Manual.
1.7.4.1 Configuring a GIGAswitch/ATM for ELAN
The GIGAswitch must have its ELAN services enabled before the OpenVMS
host can join an ELAN. A LECS, BUS, and a LES must all be started on
the GIGAswitch/ATM. By using the GIGAswitch/ATM console, you can log in
and verify if the services are enabled, which they are in the following
example:
GIGAswitch/ATM login: user
Password:
GIGAswitch/ATM-> bus
Broadcast and Unknown Server Summary
BUS Number Status Description
1 enabled
GIGAswitch/ATM-> les
LAN Emulation Server Summary
LES Number Status Description
1 enabled
GIGAswitch/ATM-> elan
LECS Emulated LAN Summary
Number Status Name Default Type Size
1 enabled * 802.3 1516
GIGAswitch/ATM->
|
If the services were not enabled, start by enabling the BUS. The following two commands create BUS 1, set the frame size, the ELAN name, and enable it.
GIGAswitch/ATM-> bus 1 GIGAswitch/ATM-> bus 1 +f 1516 GIGAswitch/ATM-> bus 1 +n "elan 1" GIGAswitch/ATM-> bus 1 -e |
This next set of commands create LES 1, sets the frame size, the ELAN name, assigns BUS 1 to LES 1, and enables it.
GIGAswitch/ATM-> les 1 GIGAswitch/ATM-> les 1 +f 1516 GIGAswitch/ATM-> les 1 +n "elan 1" GIGAswitch/ATM-> les 1 +bus bus1 GIGAswitch/ATM-> les 1 -e |
Finally, the LECS is given knowledge of LES 1, the ELAN frame size, the ELAN name, and ELAN 1 is enabled.
GIGAswitch/ATM-> elan 1 GIGAswitch/ATM-> elan 1 +f 1516 GIGAswitch/ATM-> elan 1 +n "elan 1" GIGAswitch/ATM-> elan 1 +les les1 GIGAswitch/ATM-> elan 1 +u 10 ! max unknown frame count GIGAswitch/ATM-> elan 1 +tu 60 ! max unknown frame time GIGAswitch/ATM-> elan 1 +tf 4 ! flush time-out GIGAswitch/ATM-> elan 1 -e |
These commands must be executed each time the GIGAswitch/ATM is rebooted unless you store the configuration in NVRAM with the following commands:
GIGAswitch/ATM-> bus 1 +nv GIGAswitch/ATM-> les 1 +nv GIGAswitch/ATM-> elan 1 +nv |
The following sections show how to make an application program
recognize a specific LAN device for LATs, PATHWORKS, UCX, LAST, and
DECnet.
1.7.5.1 Configuring a LAT over an Emulated LAN
By default LAT starts on the first adapter it configures. To restrict
LAT to a specific device, assign the system logical LAT$DEVICE before
executing @SYS$STARTUP:LAT$STARTUP.
1.7.5.2 Configuring PATHWORKS over an Emulated LAN
To use PATHWORKS with the Emulated LAN on OpenVMS Alpha, a logical must be defined before invoking PATHWORKS. This logical must be defined once per system boot before any invocation of PATHWORKS. The following DCL command can be used to define the required logical:
$ DEFINE/SYSTEM NETBIOS$DEVICE ELc0
where c is the controller letter (for example, ELA0).
|
The Emulated LAN is a network device that may not be recognized by the current version of Digital TCP/IP. For Digital TCP/IP to communicate over the Emulated LAN, the device EL must be defined by the following Digital TCP/IP command:
UCX> DEFINE COMMUNICATION_CONTROLLER ELc0
/TYPE=(ETHERNET)/INTERNET_INTERFACE=L
where c is the controller letter (for example, ELA0).
|
In the above example, the command creates an LL0 device which an IP address can be assigned.
For more information, refer to the TCP/IP Networking on OpenVMS Systems manual.
1.7.5.4 Configuring LAST over an Emulated LAN
By default, LAST starts on all adapters, and there is currently no
method specifying a specific device to be used.
1.7.5.5 Configuring DECnet over an Emulated LAN
DECnet configures over an emulated LAN like any other LAN device. Refer
to the DECnet Phase IV and DECnet-Plus documentation.
1.8 Ports and LAN Configuration
A port in a LAN configuration consists of a protocol type, a service access point (SAP) or protocol identifier, and a controller. There are as many ports on a LAN controller as there are protocol types, SAPs, and protocol identifiers. Each port is independent of other ports running on the same LAN controller.
Application programs use either the LAN driver's QIO interface or VCI interface to perform I/O operations to and from other nodes on the LAN. This chapter describes the QIO interface. Figure 1-2 shows the relationship of most Ethernet controllers to the processor and to the user application program.
Figure 1-2 Typical Ethernet Configuration
The following sequence initializes and starts a port on a LAN device driver:
The sample programs described in Section 1.18.2 illustrate how to perform
these procedures for Ethernet and IEEE 802 ports.
1.9 Ethernet Addresses
The LAN is a medium for creating a network; it is not a network by
itself. The LAN controller and the local system constitute a node.
Nodes on the LAN are identified by unique Ethernet addresses. A message
can be sent to one, several, or all nodes on the LAN simultaneously,
depending on the Ethernet address used. You do not have to specify the
Ethernet address of your own node to communicate with other nodes on
the same Ethernet. However, you do need to know the Ethernet address of
the node with which you want to communicate.
1.9.1 Format of Ethernet Addresses
An Ethernet address is 48 bits in length. Ethernet addresses are represented by the Ethernet standard as six pairs of hexadecimal digits (six bytes), separated by hyphens (for example, AA-01-23-45-67-FF). The bytes are displayed from left to right in the order in which they are transmitted; bits within each byte are transmitted from right to left. In this example, byte AA is transmitted first; byte FF is transmitted last. (See the description of NMA$C_PCLI_PHA in Table 1-16, Section 1.16.3.1, for the internal representation of addresses.)
Upon application, IEEE assigns a block of addresses to a producer of
LAN nodes. Thus, every manufacturer has a unique set of addresses to
use. Normally, one address out of the assigned block of physical
addresses is permanently associated with each controller (usually in
read-only memory). This address is known as the hardware address of the
controller. Each individual controller has a unique hardware address.
1.9.2 Ethernet Address Classifications
An Ethernet address can be a physical address of a single node or a multicast address, depending on the value of the low-order bit of the first byte of the address (this bit is transmitted first). Following are the two types of node addresses:
Contrary to the Ethernet specification and the IEEE 802.3 Standard, the
broadcast address (FF-FF-FF-FF-FF-FF) must be enabled as a multicast
address in order to receive messages addressed to it.
1.9.3 Selecting an Ethernet Physical Address
The OpenVMS interface to the LAN controllers allows you to set a physical address of the controller. The selection of the physical address of a LAN controller is different for CSMA/CD (Ethernet and 802.3) and FDDI.
For CSMA/CD, all users of the controller must agree on this address. The first user of the controller chooses the physical address; any additional users of the controller must specify either the same physical address, no physical address, or change the address (if allowed). When all channels to the controller are shut down, the next user to start a channel chooses the physical address. The controller's physical address is always chosen on the first successful startup when there are no active ports. If the address is not chosen at this time, the controller's hardware address is used as the physical address.
For CSMA/CD, the Can Change Address parameter allows the physical address to be changed even though there are active users. If all current users of the controller have set the NMA$C_PCLI_CCA parameter to NMA$C_STATE_ON, then the physical address can be changed.
For FDDI, each port using a controller may specify its own unique physical address. Any combination of sharing of physical addresses is also allowed across the ports of an FDDI controller. For example, ports A, B, and C may use one unique physical address and ports D and E may use another unique address.
| Previous | Next | Contents | Index |
|
| privacy and legal statement | ||
| 6136LAN_001.HTML | ||