1. 11 NETWORK CONNECTION HARDWARE Chapter 3

2. Chapter 3: NETWORK CONNECTION HARDWARE2 NETWORK INTERFACE ADAPTER  Provides the link between a computer and the network  Requires a device driver to perform both data-link and physical layer functions  Plugs into a bus slot or universal serial bus (USB) port on a computer  Also referred to as a network interface card (NIC)  Provides the link between a computer and the network  Requires a device driver to perform both data-link and physical layer functions  Plugs into a bus slot or universal serial bus (USB) port on a computer  Also referred to as a network interface card (NIC)

3. Chapter 3: NETWORK CONNECTION HARDWARE3 A NETWORK INTERFACE ADAPTER

4. Chapter 3: NETWORK CONNECTION HARDWARE4 TRANSMISSION FUNCTIONS  Network interface adapters perform the following functions during data transmission:  Data transfer, buffering, and encapsulation  Media Access Control (MAC)  Parallel/ serial conversion  Signal encoding and amplification  Network interface adapters perform the following functions during data transmission:  Data transfer, buffering, and encapsulation  Media Access Control (MAC)  Parallel/ serial conversion  Signal encoding and amplification

5. Chapter 3: NETWORK CONNECTION HARDWARE5 NETWORK INTERFACE ADAPTER FEATURES  Multiple duplex modes and autonegotiation of modes  Processor offloading features  Bus mastering  Checksum processing  Transmission Control Protocol (TCP) segmentation  IP Security (IPSec) processing  Network management  Wake on LAN  Multiple duplex modes and autonegotiation of modes  Processor offloading features  Bus mastering  Checksum processing  Transmission Control Protocol (TCP) segmentation  IP Security (IPSec) processing  Network management  Wake on LAN

6. Chapter 3: NETWORK CONNECTION HARDWARE6 HALF-DUPLEX AND FULL-DUPLEX MODES

7. Chapter 3: NETWORK CONNECTION HARDWARE7 SELECTION CRITERIA  When selecting network interface adapters, you must consider the following:  The data-link layer protocol being implemented and the specific standard  The transmission speed requirements for the local area network (LAN)  The specific cabling and connector types that will be used  Each computer’s bus architecture and resource availability  Network interface driver availability  The operating system type  When selecting network interface adapters, you must consider the following:  The data-link layer protocol being implemented and the specific standard  The transmission speed requirements for the local area network (LAN)  The specific cabling and connector types that will be used  Each computer’s bus architecture and resource availability  Network interface driver availability  The operating system type

8. Chapter 3: NETWORK CONNECTION HARDWARE8 INSTALLING A NETWORK INTERFACE ADAPTER IN A COMPUTER To install a network interface adapter: 1. Physically insert the network interface adapter card into the slot. 2. Configure the card to use the appropriate hardware resources. 3. Install the card’s device driver. To install a network interface adapter: 1. Physically insert the network interface adapter card into the slot. 2. Configure the card to use the appropriate hardware resources. 3. Install the card’s device driver. NIC Installation

9. Chapter 3: NETWORK CONNECTION HARDWARE9 A NETWORK INTERFACE ADAPTER IN A COMPUTER

10. Chapter 3: NETWORK CONNECTION HARDWARE10 CONFIGURING A NETWORK INTERFACE ADAPTER  Network interface adapters that do not support plug and play (PnP) must be manually configured for some or all of the following hardware resources:  Interrupt request (IRQ)  I/O  Memory address  Direct memory access (DMA) channel  Network interface adapters that do not support plug and play (PnP) must be manually configured for some or all of the following hardware resources:  Interrupt request (IRQ)  I/O  Memory address  Direct memory access (DMA) channel

11. Chapter 3: NETWORK CONNECTION HARDWARE11 NETWORK INTERFACE ADAPTER DEVICE DRIVERS  Network interfaces require a device driver to provide the link between the computer and the interface.  Operating systems ship with device drivers for common interfaces.  Operating systems that support PnP detect and configure the interface automatically.  You can get drivers from the manufacturer’s Web site.  The driver configuration must match the interface’s resource settings.  Network interfaces require a device driver to provide the link between the computer and the interface.  Operating systems ship with device drivers for common interfaces.  Operating systems that support PnP detect and configure the interface automatically.  You can get drivers from the manufacturer’s Web site.  The driver configuration must match the interface’s resource settings.

12. Chapter 3: NETWORK CONNECTION HARDWARE12 CONFIGURATION TOOLS  The configuration tool you use to install and configure network interface adapters and drivers depends on the operating system.  For all Microsoft Windows operating systems, use the Device Manager utility (accessed from the System Properties dialog box in Control Panel or from the Computer Management console).  For Novell NetWare  Use Install.nlm for versions earlier than NetWare 5.  Use Nwconfig.nlm for NetWare 5.  Use Hdetect.nlm and Inetcfg.nlm for NetWare 6.5.  For UNIX or Linux, use the line command Ifconfig.  The configuration tool you use to install and configure network interface adapters and drivers depends on the operating system.  For all Microsoft Windows operating systems, use the Device Manager utility (accessed from the System Properties dialog box in Control Panel or from the Computer Management console).  For Novell NetWare  Use Install.nlm for versions earlier than NetWare 5.  Use Nwconfig.nlm for NetWare 5.  Use Hdetect.nlm and Inetcfg.nlm for NetWare 6.5.  For UNIX or Linux, use the line command Ifconfig.

13. Chapter 3: NETWORK CONNECTION HARDWARE13 ISOLATING A PROBLEM  Isolating a problem to a specific device involves excluding other related hardware and software.  Check existing cables and connectors to make sure they are secure.  Test different cables and connectors that are known to work.  Verify the following:  The appropriate driver is installed.  Network communication components are installed and configured properly.  Isolating a problem to a specific device involves excluding other related hardware and software.  Check existing cables and connectors to make sure they are secure.  Test different cables and connectors that are known to work.  Verify the following:  The appropriate driver is installed.  Network communication components are installed and configured properly.

14. Chapter 3: NETWORK CONNECTION HARDWARE14 ISOLATING A PROBLEM (CONT.)  Verify the following (Cont.):  The network interface is functioning. (Run the diagnostic software.)  The driver configuration matches the interface’s resource settings and there are no conflicts with other devices.  Verify the following (Cont.):  The network interface is functioning. (Run the diagnostic software.)  The driver configuration matches the interface’s resource settings and there are no conflicts with other devices.

15. Chapter 3: NETWORK CONNECTION HARDWARE15 TROUBLESHOOTING A NETWORK INTERFACE ADAPTER  To troubleshoot the suspect network interface adapter, open the computer case and do the following:  Verify that the interface is seated properly in the bus slot.  Remove the card, clean the slot, and then reseat the card in the same slot or try another slot.  Test a different interface (known to be functional) in the same slot and in a different slot  To troubleshoot the suspect network interface adapter, open the computer case and do the following:  Verify that the interface is seated properly in the bus slot.  Remove the card, clean the slot, and then reseat the card in the same slot or try another slot.  Test a different interface (known to be functional) in the same slot and in a different slot

16. Chapter 3: NETWORK CONNECTION HARDWARE16 PHYSICAL, DATA-LINK, AND NETWORK LAYER HARDWARE

17. Chapter 3: NETWORK CONNECTION HARDWARE17 HUBS, REPEATERS, AND CONCENTRATORS  Hubs, repeaters, and concentrators are all physical layer devices that  Amplify and repeat signals  Extend the distance of a network  Hubs, repeaters, and concentrators are all physical layer devices that  Amplify and repeat signals  Extend the distance of a network

18. Chapter 3: NETWORK CONNECTION HARDWARE18 THICK ETHERNET REPEATERS  Thick Ethernet repeaters extend the distance of a bus network.  The maximum segment length is 500 meters.  The maximum network distance is 2500 meters.  You must observe the 5-4-3 rule.  Thick Ethernet repeaters extend the distance of a bus network.  The maximum segment length is 500 meters.  The maximum network distance is 2500 meters.  You must observe the 5-4-3 rule.

19. Chapter 3: NETWORK CONNECTION HARDWARE19 THIN ETHERNET REPEATERS  Thin Ethernet repeaters extend the distance of a bus network.  The maximum segment length is 185 meters.  The maximum network distance is 925 meters.  You must observe the 5-4-3 rule.  Thin Ethernet repeaters extend the distance of a bus network.  The maximum segment length is 185 meters.  The maximum network distance is 925 meters.  You must observe the 5-4-3 rule.

20. Chapter 3: NETWORK CONNECTION HARDWARE20 AN ETHERNET REPEATER

21. Chapter 3: NETWORK CONNECTION HARDWARE21 10BASE-T AND 100BASE-X HUBS  10Base-T and 100Base-TX/100Base-T4 standards define Ethernet networks that function at 10 Mbps and 100 Mbps, using baseband signaling over twisted-pair wire.  10Base-T  Maximum distance limitation for each connection: 100 meters, including workstation-to-hub and hub-to-hub connections  Can have up to four hubs connected to form a hierarchical star  Includes an internal crossover circuit  Uses an uplink port to form a hierarchical star  10Base-T and 100Base-TX/100Base-T4 standards define Ethernet networks that function at 10 Mbps and 100 Mbps, using baseband signaling over twisted-pair wire.  10Base-T  Maximum distance limitation for each connection: 100 meters, including workstation-to-hub and hub-to-hub connections  Can have up to four hubs connected to form a hierarchical star  Includes an internal crossover circuit  Uses an uplink port to form a hierarchical star

22. Chapter 3: NETWORK CONNECTION HARDWARE22 10BASE-T AND 100BASE-X HUBS (CONT.)  100Base-TX and 100Base-T4  There are two types of hubs: Class I and Class II.  The maximum distance for each node connection is 100 meters.  Class II hub-to-hub connections can be no more than 5 meters long.  100Base-TX and 100Base-T4  There are two types of hubs: Class I and Class II.  The maximum distance for each node connection is 100 meters.  Class II hub-to-hub connections can be no more than 5 meters long.

23. Chapter 3: NETWORK CONNECTION HARDWARE23 HUB CONNECTIONS Play Video

24. Chapter 3: NETWORK CONNECTION HARDWARE24 10BASE-T HUB

25. Chapter 3: NETWORK CONNECTION HARDWARE25 BRIDGES AND SWITCHES  Are data-link layer devices that use destination addresses to forward frames  Are protocol independent  Do not filter broadcast packets  Do not define separate networks  Two forwarding modes in switches: cut-through and store-and-forward  One forwarding mode in bridges: store-and-forward  Are data-link layer devices that use destination addresses to forward frames  Are protocol independent  Do not filter broadcast packets  Do not define separate networks  Two forwarding modes in switches: cut-through and store-and-forward  One forwarding mode in bridges: store-and-forward

26. Chapter 3: NETWORK CONNECTION HARDWARE26 CUT-THROUGH SWITCHING  The cut-through method is the fastest way to forward frames.  Looks at only the first 6 bytes (destination MAC address) before forwarding  Does not perform cyclical redundancy check (CRC) on the frame contents  Does not define separate collision domains  The cut-through method is the fastest way to forward frames.  Looks at only the first 6 bytes (destination MAC address) before forwarding  Does not perform cyclical redundancy check (CRC) on the frame contents  Does not define separate collision domains Hubs & Switches

27. Chapter 3: NETWORK CONNECTION HARDWARE27 STORE-AND-FORWARD SWITCHING  Store-and-forward switching is slower but more reliable than the cut-through method of forwarding frames.  Store-and-forward switching pulls in the entire frame and performs a CRC check on the frame contents.  Each port defines a separate collision domain.  Store-and-forward switching is slower but more reliable than the cut-through method of forwarding frames.  Store-and-forward switching pulls in the entire frame and performs a CRC check on the frame contents.  Each port defines a separate collision domain.

28. Chapter 3: NETWORK CONNECTION HARDWARE28 TRANSPARENT BRIDGING AND SWITCHING Perform three basic functions:  Flood  Frames with unidentified destination addresses are transmitted out all ports except the one they were received through.  Learn  Switches use the source addresses within frames to learn which devices use specific ports, and then they use this information to build their internal address tables.  Forward  Frames are selectively forwarded to a port using known destination addresses stored in the MAC address table. Perform three basic functions:  Flood  Frames with unidentified destination addresses are transmitted out all ports except the one they were received through.  Learn  Switches use the source addresses within frames to learn which devices use specific ports, and then they use this information to build their internal address tables.  Forward  Frames are selectively forwarded to a port using known destination addresses stored in the MAC address table.

29. Chapter 3: NETWORK CONNECTION HARDWARE29 FLOODING AND LEARNING

30. Chapter 3: NETWORK CONNECTION HARDWARE30 FORWARDING

31. Chapter 3: NETWORK CONNECTION HARDWARE31 OTHER BRIDGING TECHNOLOGIES  Source route bridging  Source route bridging is used in Token Ring networks.  The source host determines the path through the network, not the bridge.  Bridges add path information when frames are forwarded and use this information to continue to forward frames between source and destination hosts.  Translation bridging  Translation bridging is used to connect dissimilar data-link architectures.  Remote bridge  A remote bridge connects two segments across a wide area network (WAN) link.  Source route bridging  Source route bridging is used in Token Ring networks.  The source host determines the path through the network, not the bridge.  Bridges add path information when frames are forwarded and use this information to continue to forward frames between source and destination hosts.  Translation bridging  Translation bridging is used to connect dissimilar data-link architectures.  Remote bridge  A remote bridge connects two segments across a wide area network (WAN) link.

32. Chapter 3: NETWORK CONNECTION HARDWARE32 OTHER DATA-LINK LAYER TECHNOLOGIES  Spanning tree protocol  Used to avoid bridging loops  Ensures a single active path to all segments within a LAN  Virtual LANs (VLANs)  Are logical LANs defined on switches  Layer 3 switches  Have built-in routing capabilities  Spanning tree protocol  Used to avoid bridging loops  Ensures a single active path to all segments within a LAN  Virtual LANs (VLANs)  Are logical LANs defined on switches  Layer 3 switches  Have built-in routing capabilities

33. Chapter 3: NETWORK CONNECTION HARDWARE33 SPANNING TREE

34. Chapter 3: NETWORK CONNECTION HARDWARE34 VLANS

35. Chapter 3: NETWORK CONNECTION HARDWARE35 ROUTERS Routers are network layer devices that connect LANs.  Connect similar or different data-link layer LANs  Must understand and support the network layer protocol and addressing  Perform fragmentation  Strip the data-link header and footer off received frames  Add a new data-link header and footer before transmitting frames  Use routing protocols to build routing tables and forward frames  Define separate broadcast domains Routers are network layer devices that connect LANs.  Connect similar or different data-link layer LANs  Must understand and support the network layer protocol and addressing  Perform fragmentation  Strip the data-link header and footer off received frames  Add a new data-link header and footer before transmitting frames  Use routing protocols to build routing tables and forward frames  Define separate broadcast domains Bridges & Routers

36. Chapter 3: NETWORK CONNECTION HARDWARE36 A SIMPLE ROUTED NETWORK

37. Chapter 3: NETWORK CONNECTION HARDWARE37 A ROUTED INTERNETWORK

38. Chapter 3: NETWORK CONNECTION HARDWARE38 GATEWAYS  Can include the functions of all seven layers of the OSI model  Connect dissimilar systems and protocols  Perform translation and conversion services  Can include the functions of all seven layers of the OSI model  Connect dissimilar systems and protocols  Perform translation and conversion services

39. Chapter 3: NETWORK CONNECTION HARDWARE39 SUMMARY  Network interface adapters provide the physical link between computers and the network.  Hubs are physical layer devices that amplify and repeat signals out all ports except the one they were received through.  Bridges and switches are data-link layer devices that use destination addresses to forward frames.  Spanning tree is used by bridges and switches to avoid loops.  VLANs are logical LANs used to group computers within a switched network.  Routers are network layer devices that forward datagrams between LANs.  Gateways translate and convert protocols between dissimilar systems.  Network interface adapters provide the physical link between computers and the network.  Hubs are physical layer devices that amplify and repeat signals out all ports except the one they were received through.  Bridges and switches are data-link layer devices that use destination addresses to forward frames.  Spanning tree is used by bridges and switches to avoid loops.  VLANs are logical LANs used to group computers within a switched network.  Routers are network layer devices that forward datagrams between LANs.  Gateways translate and convert protocols between dissimilar systems.