TCP/IP SUPPLEMENT SCALE NETWORKING

(1)

701 S. RIDGE AVENUE TROY, OHIO 45374-0001

(2)

(3)

Understanding TCP/IP Communications Protocol...3

Understanding the IP Address... 3

Setting Up Scale IP Addressing...4

Entering IP Address Information for Server and Client Scales...4

Setting Up Client Scale’s Department IP Address on the Server Scale ...5

Setting Up ScaleMaster Located on a Different Network... 7

Backing Up Scales to Retain TCP/IP Information ... 7

Sample Ethernet Wiring Illustration...8

Multi Scales Connected in Stand Alone Department (Configured with IntraNet single point configuration) ...9

Multi Scales Connected to a Hub with ScaleMaster ...10

Multi Scales Connected to a Hub with ScaleMaster (Departments Configured with IntraNet Single Point Configuration)... 11

Scale IP Address Assignment Form... 13

Testing Scales TCP/IP Connection... 14

Troubleshooting IP Addressing... 16

Appendix ... 19

(4)

(5)

Understanding TCP/IP

Communication

Protocol

Transmission Communications Protocol/Internet Protocol (TCP/IP) is a communication protocol which maybe used to make your scale system communicate faster and more reliably. It serves as a traffic manager for sending and receiving packets of information between scales and devices. Scales can be automatically updated with information which is sent directly from a server scale or ScaleMaster.

Understanding the IP

Address

The IP Address is a naming convention used to identify a scale or device located on a network. Each IP Address must be unique to each scale (other scales or devices on a network cannot have the same IP Address).

☛

Note

If the scale is on an existing network, contact the Network Administrator for the correct IP Address information.

Base_Number . Store_Number . Department_Number . Scale_Number

127 208 003 001

IP Address 127 . 208 . 003 . 001

The following shows the components of an IP addressing scheme for scales connected to a Hobart only network.

IP Address Range Description

Base_Number (1 - 255) This is a number between 0 and 255.

Store_Number (1 - 255) This is a number assigned by the customer that represents each store in a chain.

Department_Number (1 - 255) This number identifies a department in a store. Server

Scale_Number (1 - 255)

This represents the scale ID number.

Intranet Client Scale_Number (2 - 99)

This represents the client scale ID number.

(6)

2

Setting Up Scale IP Addresses

Entering IP Address

Information for Server and

Client Scales

The following steps explain how to access and set up the IP Addresses for scales.

QUICK STEPS

From the Supervisor Menu:

1. PRESS [F5] 2. PRESS [F6] 3. PRESS [F2] 4. PRESS [F2]

5. TYPE the IP Address 6. PRESS [ESC]

7. PRESS [ESC] 8. Reset the scale

To set up Server and Client Scale IP Addresses:

1. From the Supervisor Menu, PRESS [F5] to select Scale Setup Menu.

2. PRESS [F6] to select Communications Menu. 3. PRESS [F2] to select TCP/IP Network.

4. From the TCP/IP Network Screen, PRESS [F2] until IntraNet or ScaleMaster is the selected network type.

☛

Note

There are several options available (None, MiniNetII, ScaleMaster, and IntraNet). Each time [F2] is pressed it cycles through these options. Select either ScaleMaster or IntraNet based on configuration needs.

(7)

5. TYPE the appropriate IP Address information for each scale. (Refer to the Scale IP Address Table.)

☛

Note

If setting up server scales, continue to Setting Up Client Scales Department IP Address on the Server Scale.

6. After entering the client scales IP Address, PRESS [ESC] to return to the TCP/IP Network Screen.

7. PRESS [ESC] until the Start a Run Screen displays. 8. PRESS the RESET button (located on the left side of the

scale) for 3 seconds and release. This will reset the scale with the updated communication settings. The scale will automatically power back on.

Setting up the Client Scale’s

Department IP Address on the

Server Scale

(IntraNet Configuration)

The Department IP Address List Menu is where you set up and identify the servers client scales. The list is used by the server to identify the client scale’s in a department.

Server Scale setup only

The following steps explain how to access and set up the department IP Addresses on Server Scales.

1. From the TCP/IP Network Screen, PRESS [F8] to select Department IP Address List.

(8)

4

QUICK STEPS

From the Supervisor Menu:

1. PRESS [F8 2. PRESS [F3]

3. TYPE the IP Address 4. PRESS [ESC]

5. PRESS [ESC] 6. Reset the scale

2. PRESS [F3] to select New IP Address. A line number displays with space to enter the client scale IP Address.

3. TYPE the IP Address for the client scales on the line which displays. Up to 29 scales can be added to a department.

☛

Note

The Department IP Address List identifies the server’s client scales by department. Additional departments require a separate server setup for each department.

4. Once all client scale’s IP Addresses are entered, PRESS [ESC] to return to the TCP/IP Network Screen.

5. PRESS [ESC] until the Start a Run Screen displays. 6. PRESS the RESET button (located on the left side of the

scale) for 3 seconds and release. This resets the scale with the updated communication settings. The scale will automatically power back on.

(9)

Setting up ScaleMaster

Located on a Different

Network

If your scales are not physically located on the same

network as the PC which is running ScaleMaster, you must set up the Gateway IP Addresses for that network.

☛

Note

Contact your Network Administrator for specific Gateway details for Network IP Routing.

1. From the TCP/IP Network Screen, PRESS [F7] to select Network IP Routing Table Screen.

2. Enter the Gateway IP Address and the Network IP Address as specified by the Network administrator.

Gateway IP Address XXX . XXX . XXX . XXX Network IP Address XXX . XXX . XXX . XXX

Backing Up Scales to Retain

TCP/IP Information

After setting up the TCP/IP scale information, it is

recommended to back up the scale system settings. Refer to your scale manual for detailed procedures.

☛

Note (Caution)

Loading an older database into the scale, with configuration turned "on" (type of data transfer), may wipe out the new IP Address information. This may result in loading incorrect IP Address information into the scale.

(10)

6

Sample Ethernet Wiring

Illustration

Use the following suggested IP Addresses for one of the types listed below:

• Multi Scales connected in Stand Alone Department (configured with IntraNet single point configuration).

• Multi Scales connected to a Hub with ScaleMaster

• Multi Scales connected to a Hub with ScaleMaster (Departments configured with IntraNet single point configuration)

Look At This

(11)

Multi Scales Connected in

Stand Alone Department

(configured with IntraNet single

point configuration)

The following configuration shows 2 stand alone scales connected to a hub using the Intranet option.

From the TCP/IP Network Screen, ENTER the following:

Server Scale

TCP/IP Network Scale Menu

Type: Intranet (same for client) Scale IP Address

127 . 208 . 003 . 001

Server IP Address (same for client) 127 . 208 . 003 . 001

Subnet Mask (same for client)

255 . 255 . 255 . 000

Well known port number 6000 (same for client)

Server Scale From the Department IP Address List Screen, set up the Client Scale’s Department IP Address on the server. A maximum of 29 scales for a single department can be added to a Server. Department IP Address List

1) 127 . 208 . 003 . 002 (Client scale 002 IP Address)

Client Scale 002 Setup From the TCP/IP Network Screen, ENTER the Client Scale’s IP Address. All other fields must be the same as the Server information.

Scale IP Address 127 . 208 . 003 . 002

☛

Note

The Department IP Address settings, on Client Scales, always remain blank. After entering all IP Address information, PRESS the RESET button (located on the left side of the scale) for 3 seconds and release. This resets the scale with the updated communication settings and enables the changes to take affect. The scale will automatically power back on.

(12)

8

Multi Scales Connected to a

Hub with ScaleMaster

The following illustrates scales connected to the network via a Hub with ScaleMaster configuration.

☛

Note

If your scales are not physically located on the same

network as the PC which is running ScaleMaster, you must set up the Gateway IP Addresses for that network. Contact your Network Administrator for specific Gateway details for Network IP Routing.

Each scale must us a unique IP address.

TCP/IP Network Scale Menu Type: ScaleMaster

Scale IP Address 127 . 208 . 003 . 001 Server IP Address

000 . 000 . 000 . 000 Subnet Mask

255 . 255 . 255 . 000

Well known port number 6000

☛

Note

(13)

Multi Scales connected to a

Hub with ScaleMaster

(Departments configured with

IntraNet single point configuration)

The following illustrates scales connected to the network via a hub and configured for IntraNet.

Server Scale

TCP/IP Network Scale Menu

Type: Intranet (same for client) Scale IP Address

127 . 208 . 003 . 001

Server IP Address (same for client) 127 . 208 . 003 . 001

Subnet Mask (same for client)

255 . 255 . 255 . 000

Well known port number 6000 (same for client)

Server Scale From the Department IP Address List Screen, set up the Client scales Department IP Address information on the server. A maximum of 29 Department Scales can be added to a Server.

Department IP Address List

1) 127 . 208 . 003 . 002 (Client Scale 002) 2) 127 . 208 . 003 . 003 (Client Scale 003)

Through

(14)

10

Client Scales 002 thru 029 From the TCP/IP Network Screen, Enter each Scales IP Address. All other fields must be the same as the Server information.

Scale IP Address

127 . 208 . 003 . 002 (Client Scale 002) 127 . 208 . 003 . 003 (Client Scale 003)

Through

-127 . 208 . 003 . 029 (Client Scale 029)

☛

Note

(15)

Scale IP Address Assignment Form

Scale Network Addressing Example Base_Number Store_Number Dept._Number Scale_Number

I. Server Scale IP Address:

Server scale located in the Department A) Bakery: XXX.XXX.001.001

B) Cheese: XXX.XXX.002.001

C) Deli: XXX.XXX.003.001

D) Meat: XXX.XXX.004.001

E) Service Meat: XXX.XXX.005.001

F) Sea Food: XXX.XXX.006.001

G) Produce: XXX.XXX.007.001

H) Specialty: XXX.XXX.008.001

ScaleMaster: XXX.XXX.XXX.XXX

(refer to your ScaleMaster documentation)

II. Scale Subnet Mask (same for all scales):

Scale Subnet Mask: 255.255.255.000

III. Well Known Port Number (same for all scales):

Well known port number:6000 IV. Client Scale IP Addresses: (Intranet Configuration)

Note: Each Department will require a separate Server with the Department Client Scale IP information added. A) Bakery: XXX.XXX.001.001

Client Scales XXX.XXX.001.002 - 029

B) Cheese: XXX.XXX.002.001

C) Deli: XXX.XXX.003.001

D) Meat: XXX.XXX.004.001

E) Service Meat: XXX.XXX.005.001

F) Sea Food: XXX.XXX.006.001

G) Produce: XXX.XXX.007.001

H) Specialty: XXX.XXX.008.001

Server Scale: . . . (A maximum of 29 Client Scales can be added to a Department )

1) Scale: . . . 2) Scale: . . . 3) Scale: . . . 4) Scale: . . . 5) Scale: . . . 6) Scale: . . . 7) Scale: . . . 8) Scale: . . . 9) Scale: . . . 10) Scale: . . . 11) Scale: . . . 12) Scale: . . . 13) Scale: . . . 14) Scale: . . . 15) Scale: . . . 16) Scale: . . . 17) Scale: . . . 18) Scale: . . . 19) Scale: . . . 20) Scale: . . . 21) Scale: . . . 22) Scale: . . . 23) Scale: . . . 24) Scale: . . . 25) Scale: . . . 26) Scale: . . . 27) Scale: . . . 28) Scale: . . . 29) Scale: . . .

(16)

12

Testing the Scales TCP/IP

Connection

The following steps will confirm that the scales are connected and communicating with each other over the network.

1. Check the Ethernet Diagnostic L.E.D.s to see if they are functioning correctly.

This L.E.D. Does This

Ethernet Diagnostic L.E.D.s LNK (Link) Indicates a link has been established with the Ethernet network. This will be on when the scale is connected to an Ethernet network.

POL (Polarity) Verifies the polarity of the receive pair from the network. This should be off if the network wiring polarity is correct. (Note: Even if the light is on, the scale may still communicate and respond to a ping test.)

COL (Collision) Indicates a collision condition on the Ethernet network. This condition is caused by 2 devices trying to communicate at the same time. This should be off most of the time. (Note: This light may occasionally blink if connected to an active Network.)

RCV (Receive) Indicates network activity. Any network activity should cause it to flash. Intense network activity may cause it to appear to remain on.

XMT (Transmit) Indicates that the scale is communicating to the Ethernet network. During

communication this will flash or may appear to remain on.

(17)

2. Update a product on the Server Scale (updates are automatic with the Intranet network selection). 3. Check the Server Scale for the Transmission Occured

message.

4. Verify that the product update is reflected on the Client Scales associated with the Server.

☛

Note

If an error occurred and the Ethernet Diagnostic L.E.D. are functioning correctly, check the error log, refer to

Troubleshooting IP Addresses or reset each scale by pressing and releasing the Reset button then repeat steps 2 through 4.

(18)

14

Troubleshooting IP

Addresses

The following section contains information to help you_{troubleshoot problems within your configuration. The}

references give you items to troubleshoot, tools to use while troubleshooting and messages to look for when you are troubleshooting.

Error Message Possible Cause Suggested Action

TCP/IP: Connect error, check IP Address configuration.

Invalid IP Address configured for the scale.

Compare the IP Address in the scale to the IP Address, which you configured in ScaleMaster. These addresses should match.

TCP/IP: Could not talk to scale. Check with Network Administrator. Something terminated the connection between the scale and ScaleMaster.

Check with your Network Administrator.

TCP/IP: Could not disconnect. System time-out occurred.

After a successful connection, the disconnect from the scale failed.

Check with your Network Administrator. This is a network-related problem. TCP/IP device not installed (PathWay Runtime stack). Invalid components installed.

Check PathWay Runtime installation against Hobart

recommended installation. (This is a ScaleMaster component. Contact your Network Administrator for details.)

TCP/IP socket table full, no sockets available (no buffer space).

TCP/IP stack out of resource.

Increase packet buffer sizes in PathWay Runtime installation. This can be done through the Advanced Configuration Setup available in PathWay Runtime. (This is a ScaleMaster

component. Contact your Network Administrator for details.) TCP/IP socket is

already connected.

ScaleMaster is trying to connect to a scale that is already connected.

Wait 30 seconds for the scale to time out and retry the operation.

TCP/IP could not establish socket, check IP and network.

Invalid IP Address configured or the PC is not connected to the ethernet network.

Verify the IP Address in the scale against the IP Address, which you configured in ScaleMaster. The numbers should match.

--OR--Check your network connection.

--OR--Verify that Well Know Port setting in the uiconf.txt file matches the scale (ScaleMaster uses 6000).

TCP/IP connection refused, check cables/ports/IP Address.

The scale has exhausted all of its sockets.

(19)

Error Message Possible Cause Suggested Action

TCP/IP: The scale aborted the communications task.

The scale

encountered a critical error during

communication and aborted the task.

View the Activities that were Attempted Screen concerning the communication error. (This is a ScaleMaster component. Contact your Network Administrator for details.)

The scale is out of memory.

The scale does not have enough memory available to process any new data.

Free memory available in the scale (i.e., delete totals, add memory, delete unused PLUs, etc.).

Ethernet Card

Symptom Possible Cause Suggested Action

Link light on ethernet card not on. (If the card is equipped with lights.)

A cable is

disconnected and/or damaged.

Verify cable connections and integrity. The link light only functions for the RJ-45 connector. If the card has a BNC connector and the connector is in use, the link light may not light. You receive system error messages during boot. There are configuration problems.

Verify the correct drivers are being used. Consult the ethernet cards documentation and perform the card diagnostics provided by the manufacturer.

The system cannot communicate.

The connections to both the BNC and RJ-45 connectors.

Some manufacturers of ethernet adapters provide connector for both BNC and RJ-45 connections. If the card has both connectors in use, generally the RJ-45 connection takes precedence. Consult the manufacturers documentation for specific information.

Hub to Scale

Both the scale and hub link lights are off or flashing.

• A cable is disconnected and/or damaged.

• Verify cable connections and cable integrity.

• It is the incorrect cable and/or an incorrectly wired cable.

• Verify the correct cable is being used for the port in use at the hub (Straight Through or Crossover, depending on

configuration). Verify the plug wiring at both ends.

•No power to hub and/or scale.

• Verify that the hub and/or scale is connected to the appropriate power source.

Both the scale and hub link lights are off or flashing.

The hub switch setting is incorrect.

Verify that the hub crossover switch is set correctly. (Not all hubs have switches.)

(20)

16

Hub to Scale (continued)

The scale link light is off.

• A cable is disconnected and/or damaged.

• Verify cable connections and cable integrity.

• It is the incorrect cable.

• Verify that a crossover cable is used if connecting to two ports marked with a "X" (internal crossover).

• Verify that a straight through cable is used if connecting to a port on one hub marked with an "X" (internal crossover).

• The RJ-45 plug pins 3 & 6 are wired incorrectly.

• Verify the wiring at both ends.

• No power to scale. • Verify that scale is connected to the appropriate power source.

• Defective port on hub.

• Connect scale to a different port and recheck link light.

• The scale board is defective.

• Replace board. Prior to replacing the board, connect the scale in place of a scale that is working and recheck link light. Hub link light is

off or flashing.

A cable is

disconnected and/or damaged.

Verify cable connections and cable integrity.

Hub link light is off or flashing. (continued)

• There is no power to the hub.

• Verify that the hub is connected to the appropriate power source.

• It is the incorrect cable.

• Verify that a crossover cable is used if connecting to two ports marked with an "X" (internal crossover).

• The RJ-45 plug pins 1 & 2 are wired incorrectly.

• Verify the wiring at both ends.

• The hub switch setting.

• Verify that the hub crossover switch is set correctly. (Not all hubs have switches.) Refer to Understanding ScaleMaster

Ethernet Networks.

• A defective port on the hub and/or a defective hub.

• Connect scale to a different port and recheck link light.

• The scale board is defective.

• Replace board. Prior to replacing the board, connect the scale in place of a working scale and recheck link light.

(21)

Hub to Hub

The link lights on both hubs are off or flashing.

• It is an incorrect cable.

• Verify that a crossover cable is used if connecting to two ports marked with an "X" (internal crossover).

• There is no power to hub(s).

• Verify that the hub(s) are connected to the appropriate power source.

The polarity light (POL) on scale is on.

The polarity is incorrect.

Verify cable wiring. The Polarity light indicates that the polarity is reversed in a RJ-45 plug between pins 3 & 6 in the cable from the scale to the hub.

The collision light (COL) on the scale is on.

Multiple devices are trying to

communicate at the same time.

Contact the system administrator.

The partition light on the scale is on.

There are wiring/device problem(s).

Remove power from the hub. Wait 30 seconds and reconnect. If the partition light comes back on, troubleshoot the wiring attached to the indicated hub port. Look for bad wiring, EMF sources close to the wiring, and/or a device problem.

All TCP/IP scales are off-line.

There are computer problem(s).

• Verify that all drivers are loading while the computer is booting and that no error messages are displayed.

• Attempt to ping the computer using an IP of 127.0.0.1. If the ping test fails, troubleshoot the ethernet adapter board and/or the drivers.

• Attempt to ping the computer where ScaleMaster is installed from any other computer on the network.

• Initiate a ping test to any valid address. While the ping test is in progress, observe the activity light on the ethernet adapter board, (it should be flashing). Also observe the RCV L.E.D.s on the scales. The L.E.D.s should be flashing. If the L.E.D. flashes on the ethernet adapter, but not on the scales,

troubleshoot the configuration and/or network wiring. If the L.E.D. on the ethernet adapter does not flash, troubleshoot the computer/adapter installation.

(22)

18

Hub to Hub (continued)

All TCP/IP scales are off-line. (continued)

• There are configuration problem(s).

• Verify that the Well-Known Port setting in Uiconf.txt matches the Well-Known Port setting in the scales (ScaleMaster uses 6000).

• Verify that the scale IP Addresses match the IP Addresses configured in ScaleMaster.

• Verify that the IP configured in PathWay Runtime is correct and that the correct subnet mask was specified.

•There are wiring problem(s).

• Verify that all cables are connected.

• Verify that all link lights are on at the hubs and at the scales.

• Disconnect all scales from the network and attempt to communicate with each scale after reconnecting.

• Verify that the scale network has not been partitioned by the ethernet hub.

Some scales are on-line and one or more scales are off line.

•The scale configuration is incorrect.

• Verify the scale network configuration.

• Verify that each scale has a unique IP Address.

• Verify the status of the scales ethernet L.E.D.s for link, polarity, and collision.

• Verify the scale has the correct Well-Known Port (ScaleMaster uses 6000).

•There are wiring problem(s).

• Verify that all cables are connected on the affected segments.

• Verify that all link lights are on at the hubs and at the scales.

• Verify that the scale network has not been partitioned by the ethernet hub.

•There are hub problem(s).

• If all the scales that are off-line are connected to one hub, troubleshoot the hub.

(23)

Appendix

Understanding Ethernet

Networks

To effectively set up Scales with TCP/IP, you should have a_{basic understanding of ethernet networking. A Network} Consultant or Network Administrator should be contacted prior to implementing an Ethernet LAN system.

Hubs

Hubs for 10BaseT are available with different numbers and_{types of ports. The IEEE 802.3 standard recommends that the} signal crossover function for 10BaseT connection is done inside the hub port. This standard also notes that all ports featuring an internal crossover be designated with an "X". Some hubs provide a port where the crossover function is controlled by a switch. This port is generally used for cascading hubs using straight through cables. Hubs where all ports feature an internal crossover generally require a crossover cable to cascade the hubs. stackable hubs, which provide a special connection for stacking 2 or more hubs, are also available. Stacked hubs count as one hub when

calculating the number of hubs and segments between two stations.

☛

Note

10BaseT hubs are also available with connections for attaching to a 10Base2 (coax cable) network.

Wiring

An Ethernet network may consist of several different cable_{types. ScaleMaster may be used successfully with any type} of Ethernet network if provisions are made to provide a 10BaseT connection for each scale. Refer to your ScaleMaster TCP/IP supplement for more information (F-33863).

Wiring Specifications 10BaseT (or UTP-Unshielded Twisted Pair) length segments_{have a maximum of 328Ì (100m). This is the maximum} amount allowed between hubs or remote devices (i.e. scales or computers). The network is also restricted to a maximum of 4 hubs between any two devices.

(24)

20

Wiring Categories Hobart Ethernet scales supporting TCP/IP require a network_{connection using 10BaseT wiring. Hobart recommends that} all wiring conform to Category 3 or 5 standards, published by EIA.

☛

Note

Category 3 wiring may be used but is not recommended.

Look At This

All wiring and cabling must be installed to meet National and Local Electrical Codes.

All Ethernet wiring must conform to IEEE 802.3 specifications.

All cabling should be installed to meet the cabling pathway requirements of EIA/TIA Standard 569, table 4.8-5.

Crossover Function

Two Ethernet 10BaseT devices can only communicate if the_{transmitter on one device is connected to the receiver on the} other device. When connecting two identical 10BaseT ports (ports that either both support the crossover function or both do not support the crossover function), the crossover

function must be implemented in the wiring.

Patch Cord Wiring A patch cord is the connecting cable between two pieces of_{hardware on an ethernet network. The recommended} standard for wiring patch cords is the EIA/TIA 568B standard, using RJ-45 8 conductor connectors. The patch cords used may be wired to any standard as long as all cords are wired using the same standard. The EIA/TIA 568B standard is recommended for conformity with industry standards.

(25)

Straight Thru Patch Cord A straight thru patch cord has both ends wired the same and_{is generally used to connect computers to the hub and to} connect devices to hubs. Depending on the hub a straight thru patch cord or crossover patch cord may be required to cascade hubs. Refer to the documentation provided by the manufacturer of you hub.

10 Base - T Straight Thru Patch Cord

Pin Color Signal

1 White/orange TX data +

2 Orange/white TX data

-3 White/green RX data +

4 Blue

--5 White/blue

--6 Green/white RX data

-7 White/brown

(26)

--22

Crossover Patch Cord _{A crossover patch cord is generally used to cascade hubs. A} crossover patch cord has one end wired as a straight thru connection and the other end wired as a crossover

connection. Depending on the hub, a straight thru patch cord, or a crossover patch cord may be required to cascade hubs. Refer to the documentation provided by the

manufacturer of your hub.

10 Base - T Crossover Patch Cord

Pin Color Signal

1 White/green RX data +

2 Green/white RX data

-3 White/orange TX data +

4 Blue

--5 White/blue

--6 Orange/white TX data

-7 White/brown

(27)

--Wiring Identification _{As part of the Hobart recommended cable identification} scheme, all ethernet hubs should be marked with a unique hub number. All ethernet patch cords should be marked at both ends with the originating hub and port number and the destination hub and port number. Refer to the following example.

(28)

24

Glossary

Abstract Notation Syntax One (ASN.1)

A language used in OSI and TCP/IP networks to define data types for use in network management.

Address An identifiable location. A location within memory. A location of a node within a network. A way of identifying a network, sub network, or node.

Address Mask A way of omitting certain parts of an IP Address in order to reach the target destination without broadcasting an

address to unnecessary LAN segments or sub networks. It is also referred to as a subnet mask. The address mask uses the 32-bit IP Addressing scheme. A variation of 255.255.255.255 is used.

Address Resolution The mapping of an IP Address to a hardware address. In the TCP/IP suite of protocols, Address Resolution Protocol (ARP) performs this function.

API Application Program Interface. Defined routines that are callable services by a program.

Application Layer The topmost layer in the OSI reference model that aids in the identification of communicating partners.

Backbone Used to refer to a set of nodes and links connected together compromising a network. It is also used to refer to the physical media that connects components to a network. Baseband A type of channel where data transmission is carried across

only one communication channel. Baseband supports one signal transmission at a time. Ethernet is an example of baseband technology.

BER Bit Error Rate

Bit rate The rate, usually expressed in seconds, that bits are transmitted.

Bridge A network device capable of connecting networks using similar protocols.

Broadband A range of frequencies divided into narrow bands, each of which can be used for different transmission purposes. Also known as wideband.

Broadcast Simultaneous transmission of the same data to all nodes connected to a network.

(29)

Carrier Sense A signal generated at the physical network layer to inform the data link layer that one or more nodes are transmitting on the underlying medium.

Carrier Sense Multiple Access with Collision Detection (CSMA/CD)

This is the media access control protocol. Nodes using this protocol listen to the medium to which they are attached. As long as there is no signal on the medium being monitored, a node listening can send data across the medium.

Client A program that can be invoked by a user; a user being a human or a program.

Client/Server Architecture A general phrase used to refer to a distributed application environment where a program exists that can initiate a session and a program exists to answer the requests of a client.

Client/Server Terms used to refer to a peer to peer method of operation of applications within hosts.

Collision An event that occurs when two or more nodes broadcast on the same network medium at the same time.

Collision Detection The ability of a device to detect if a collision has occurred. Crosstalk Signals that interfere with another signal being transmitted. Daemon A common UNIX program that operates unattended,

performing standard services. This type of program can be triggered by time intervals for execution.

Datagram A basic unit of data that traverses a TCP/IP internet. Data Link The part of a node that is controlled by a data link protocol.

It is the logical connection between two nodes. Data Link Protocol A prescribed way of handling the establishment,

maintenance, and termination of a logical link between two nodes.

Destination Address In an Ethernet network, this refers to the target node address.

Distributed Processing I/O processing, control functions, and actual processing is dispersed among two or more nodes.

Domain Name System A service used with TCP/IP to replace the previous method of keeping track with host names, aliases, and internet addresses. The domain name service is a distributed

database used to convert node names to internet addresses. Dotted Decimal Notation A representation of addressing typically used in expressing internet protocol addresses. For example, 137.1.1.100 is an

(30)

26

Double Byte Character Set A character set where alphanumeric characters are

represented by two bytes. Examples of languages where this is used include: Japanese, Chinese, and Korean.

Encapsulation A technique used by layered network protocols where, as data travels down the network layers, headers and trailers are added to represent that layer. For example, when data is passed from an application above the TCP layer, TCP adds a header and a trailer encapsulating the data; likewise, this datagram is passed to the IP layer where IP wraps an IP header and trailer around the TCP portion, and so on for each layer. When this arrives at the target host, the reverse occurs, as the data travels up the layers, respective headers and trailers are removed.

Ethernet A data link level protocol. It comprises layers one and two when compared to the OSI reference model. Ethernet is a broadcast technology and can be implemented with

different media types, such as thick or thin coaxial cable or twisted pair cable. Ethernet uses CSMA/CD mechanism to access the medium.

Ethernet Address A 48 bit address, commonly referred to as a hard address. This address identifies an Ethernet network interface card (NIC), thus identifying a host hardware address.

Frame Refers to the data and all headers and trailers.

Frame Check Sequence (FCS) A mathematical function used with bits in a frame. The FCS is appended to the frame and used by the receiving end to recalculate the value to determine if an error has occurred. Frame Relay A switching mechanism for routing frames as quickly as

possible.

File Transfer Protocol (FTP) A TCP/IP based application used for transferring files from one system to another. Part of FTP provides password protection.

Gateway A networking device that translates all protocols of one type network into all protocols of another type network. (i.e. Ethernet to Token Ring).

Hardware Address A low-level address associated with each node on the network. This address is generally the address related to the interface card in the node. This may also be referred to as the Ethernet Address.

Internet Control Message Protocol (ICMP)

A protocol that works in conjunction with the Internet Protocol (IP) that handles error messages.

Interface A shared point between two entities, either software or hardware.

(31)

Internet Address A 32-bit address used to identify hosts and networks. Internet Protocol (IP) The part of the TCP/IP protocol that handles routing of

data.

IP Datagram The basic unit of information passed through a TCP/IP network. This datagram contains source and destination addresses.

ISO International Standards Organization

ISO Reference Model The networking model created by ISO defining seven layers of a network, isolating functions within each layer. It is used as a baseline for comparison with other network types. Jitter A situation that can occur with a 10BaseT network where

signals are out of phase with each other.

Local Area Network (LAN) A collection of computer related equipment connected in such a way that communication can occur between all nodes connected to the medium.

Learning Bridge Serves as a bridge but has the capability to learn what nodes are connected and route data accordingly.

Leased Line A dedicated communication line between two points. Link Used to refer to a connection between two end points. Logical Link Control The upper part of the data link sublayer protocol

responsible for governing the exchange of data between two endpoints.

Media Access Control (MAC) The lower half of the data link sublayer. It is responsible for framing data and controlling the physical link between two stations.

Maximum Transmission Unit (MTU)

The largest datagram that can transverse a given network such as Ethernet or Token Ring.

Medium Access Unit (MAU) A device for central connection of nodes operating in a network.

Management Information Base (MIB)

A database containing configuration and statistical information about nodes on a network.

Name Resolution The process of mapping aliases to an address. The domain name system provides a mechanism to perform this function.

Network Administrator The person designated to maintain the network. This person should have working knowledge of network wiring,

(32)

28 Network Basic Input Output

Operating System (NETBIOS)

An IBM and compatible network programming interface.

Network A collection of computers and related devices connected so that communication can occur.

Network Address In TCP/IP networks, this refers to the IP Address of a node. Network File System (NFS) Sun MicroSystems protocols that permit clients to mount

remote directories onto their own local file system, thus appearing to be local.

Network Interface Card (NIC) A generic reference to a networking interface card.

Node Refers to different types of networking devices.

Open Systems Interconnection (OSI)

A set of ISO standards relating to data communications.

Packet In TCP/IP networks, this refers to the data passing between the internet layer and the data link layer. A packet includes the IP header, TCP header, and data.

Pathname The complete string of information that must be entered into a system in order to access or identify a file.

Packet InterNet Groper (PING) A program used with TCP/IP networks. The PING program provides a way of testing access to a destination by sending an ICMP echo request, then waiting for a response from the target host.

Point to Point Protocol (PPP) A protocol that has the ability to provide host to network and router to router connections over synchronous and asynchronous lines.

Port In TCP/IP, a number used to identify applications. In general, a port is referred to as an entry or exit point. Ports are associated with TCP or UDP transport protocols. Protocol A set of rules governing the method of operation.

Protocol Conversion Changing one type of protocol to another type of protocol. Repeater A network device that repeats signals so the length of a

network can be extended.

Routing The process of determining which path is to be used for data transmission.

Routing Table A list of valid paths through which data can be transmitted. RS-232-C A physical layer specification for connecting devices.

(33)

Segment A protocol data unit that consists of TCP header information and optional data.

Parts of a network; typically Ethernet LANs are divided into parts, generally referred to as segments.

Server An application that answers requests from clients. Simple Mail Transfer Protocol

(SMTP)

In TCP/IP, an application including a client and a server providing E-Mail services for all hosts with TCP/IP software installed and enabled.

Serial Line Internet Protocol (SLIP)

A protocol used to utilize Internet protocol over serial lines, such as a switched telephone line.

Socket In TCP/IP, a socket is an addressable point that consists of the IP Address and the TCP or UDP port number. It provides access to TCP/IP protocols.

Socket Address The complete designation of a TCP/IP node. It consists of a 32-bit IP Address and a 16 bit port number.

Subnet The part of a TCP/IP network identified by a portion of the internet address.

Subnet Address The part of the IP Address that identifies the subnetwork. Subnet Mask A way of isolating broadcasts to the desired network(s). System Administrator The person responsible for maintaining the ScaleMaster

system. See Network Administrator.

Telnet A TCP/IP application using TCP as a transport mechanism. It consists of a client and a server. All TCP/IP protocol suites have this application because it is part of the definition of TCP/IP.

TCP Transmission Control Protocol. A transport layer protocol that is part of the TCP/IP protocol suite. TCP provides a reliable stream mechanism performing re-transmission when a positive acknowledgment is not returned to the source from the destination node.

TCP/IP Transmission Control Protocol / Internet Protocol. TCP/IP is an upper layer networking protocol. It is client/server based at the application layer.

10Base2 A reference to the cabling used in an Ethernet network. It literally means 10Megabits per second, using baseband signaling, with a continuous cable segment length of 100 meters and a maximum of 2 segments.

(34)

30

10Base5 A reference to the cabling used in an Ethernet network. It literally means 10Megabits per second, using baseband signaling, with 5 continuous segments, not exceeding 100 meters per segment.

10BaseT A reference to the cabling used in an Ethernet network. Meaning 10Megabits per second, using baseband signaling, and twisted pair cabling.

Throughput The amount of data that can be successfully moved across a medium or processed within a certain time period.

Token Ring A lower layer networking protocol using a token passing method controlling data traffic. It is connection oriented at a data link level.

Topology The configuration of network devices. Examples include: BUS, Star, Ring, Dual Ring, etc.

Traffic A generic term used to describe the amount of data on a network backbone at a given period in time.

Transceiver A network device required in baseband networks. It takes a digital signal and puts it on the analog baseband medium. Transceivers are devices that also sense collisions.

User Data Protocol (UDP) A transport layer protocol in the TCP/IP protocol suite. Unlike TCP it does not provide re-transmission.

Virtual Appearing to exist, but in reality the appearance is achieved by functions or processes.

Well Known Port In TCP/IP, an address for an expressed purpose generally agreed upon by TCP/IP users.

(35)

(36)