Ethernet Switch
Ethernet Switch
Ethernet Switch
Hubs are similar to Ethernet switches in that connected devices on the LAN will be
wired to them, using multiple ports. The big difference is that hubs share bandwidth
equally among ports, while Ethernet switches can devote more bandwidth to certain
ports without degrading network performance. When many devices are active on a
network, Ethernet switching provides more robust performance.
Most corporate networks use combinations of switches, routers, and hubs, and wired
and wireless technology.
The first Ethernet cross-connecting devices were "hubs" that share the total bandwidth.
However, the switch treats each send-receive pair at full speed, and most all hubs have
been replaced with switches
Hubs and Switches
Frames are sequences of information, travel over Ethernet networks to move data
between computers. An Ethernet frame includes a destination address, which is where
the data is traveling to, and a source address, which is the location of the device
sending the frame. In a standard seven-layer Open Systems Interconnection (OSI)
model for computer networking, frames are part of Layer 2, also known as the data-link
layer. These are sometimes known as “link layer devices” or “Layer 2 switches.”
Terms and Functions of Ethernet Switches Work:
Transparent Bridging is the most popular and common form of bridging, crucial to
Ethernet switch functionality. Using transparent bridging, a switch automatically begins
working without requiring any configuration on a switch or changes to the computers in
the network (i.e. the operation of the switch is transparent).
Address Learning -- Ethernet switches control how frames are transmitted between
switch ports, making decisions on how traffic is forwarded based on 48-bit media
access control (MAC) addresses that are used in LAN standards. An Ethernet switch
can learn which devices are on which segments of the network using the source
addresses of the frames it receives.
Every port on a switch has a unique MAC address, and as frames are received on
ports, the software in the switch looks at the source address and adds it to a table of
addresses it constantly updates and maintains. (This is how a switch “discovers” what
devices are reachable on which ports.) This table is also known as a forwarding
database, which is used by the switch to make decisions on how to filter traffic to reach
certain destinations. That the Ethernet switch can “learn” in this manner makes it
possible for network administrators to add new connected endpoints to the network
without having to manually configure the switch or the endpoints.
Traffic Filtering -- Once a switch has built a database of addresses, it can smoothly
select how it filters and forwards traffic. As it learns addresses, a switch checks frames
and makes decisions based on the destination address in the frame. Switches can also
isolate traffic to only those segments needed to receive frames from senders, ensuring
that traffic does not unnecessarily flow to other ports.
Frame Flooding -- Entries in a switch’s forwarding database may drop from the list if
the switch doesn’t see any frames from a certain source over a period of time. (This
keeps the forwarding database from becoming overloaded with “stale” source
information.) If an entry is dropped— meaning it once again is unknown to the switch—
but traffic resumes from that entry at a later time, the switch will forward the frame to all
switch ports (also known as frame flooding) to search for its correct destination. When it
connects to that destination, the switch once again learns the correct port, and frame
flooding stops.
Multicast Traffic -- LANs are not only able to transmit frames to single addresses, but
also capable of sending frames to multicast addresses, which are received by groups of
endpoint destinations. Broadcast addresses are a specific form of multicast address;
they group all of the endpoint destinations in the LAN. Multicasts and broadcasts are
commonly used for functions such as dynamic address assignment, or sending data in
multimedia applications to multiple users on a network at once, such as in online
gaming. (Streaming applications such as video, which send high rates of multicast data
and generate a lot of traffic, can hog network bandwidth.
Managed Ethernet switching refers to switches that can be managed and programmed
to deliver certain outcomes and perform certain tasks, from adjusting speeds and
combining users into subgroups, to monitoring network traffic.
While a network switch can connect multiple devices and networks to expand the LAN,
a router will allow you to share a single IP address among multiple network devices. In
simpler terms, the Ethernet switch creates networks and the router allows for
connections between networks.
Does an Ethernet switch need a router?
Note: switches have absolutely no routing functionality and cannot take the place of
a router. Your router likely has a four-port switch built into it but that does not mean your
new eight-port dedicated switch can replace your router—you still need the router to
mediate between your modem and switch.
Before we discuss how a network switch works, first consider the role an
ethernet switch plays in connectivity. An ethernet switch connects devices on
a network to ensure the data arrives at its destination. The network switch
may include ports for 5, 8, 12, 16, 24 or 28 devices, whereas corporate
ethernet switches may commonly offer between 32 and 128 connections.
Packet switching allows the network to receive, forward and process that
data before delivering it to the intended device. Networked devices
communicate effortlessly when their respective cables connect into the
switch.
Ethernet hubs work much in the same way but can only complete a simple
data transfer between connected devices. In contrast, switches offer added
layers of security and control over how data is transferred. A home network
may only require a hub, whereas a business or enterprise network may need
one or more switches for proper network functioning.
A network switch carries numerous benefits over the less sophisticated
ethernet hub, which cannot distinguish between recipients and nonrelated
computers and devices. For this reason, ethernet switches tend to be more
efficient and reliable than hubs.
For a deeper look at the differences and advantages of these devices, read
our guide on Ethernet Switches vs. Routers vs. Hubs.
The first Ethernet bridges were two-port devices that could link two of the
original Ethernet system’s coaxial cable segments together. At that time,
Ethernet only supported connections to coaxial cables. Later, when twisted-
pair Ethernet was developed and switches with many ports became widely
available, they were often used as the central connection point, or hub, of
Ethernet cabling systems, resulting in the name “switching hub.” Today, in
the marketplace, these devices are simply called switches.
Things have changed quite a lot since Ethernet bridges were first developed
in the early 1980s. Over the years, computers have become ubiquitous, and
many people use multiple devices at their jobs, including their laptops,
smartphones, and tablets. Every VoIP telephone and every printer is a
computer, and even building management systems and access controls (door
locks) are networked. Modern buildings have multiple wireless access points
(APs) to provide 802.11 Wi-Fi services for things like smartphones and
tablets, and each of the APs is also connected to a cabled Ethernet system. As
a result, modern Ethernet networks may consist of hundreds of switch
connections in a building, and thousands of switch connections across a
campus network.
What Is a Switch?
You should know that there is another network device used to link networks,
called a router. There are major differences in the ways that bridges and
routers work, and they both have advantages and disadvantages, as described
in Routers or Bridges?. Very briefly, bridges move frames between Ethernet
segments based on Ethernet addresses with little or no configuration of the
bridge required. Routers move packets between networks based on high-level
protocol addresses, and each network being linked must be configured into
the router. However, both bridges and routers are used to build larger
networks, and both devices are called switches in the marketplace.
TIP
While the 802.1D standard provides the specifications for bridging local area
network frames between ports of a switch, and for a few other aspects of
basic bridge operation, the standard is also careful to avoid specifying issues
like bridge or switch performance or how switches should be built. Instead,
vendors compete with one another to provide switches at multiple price
points and with multiple levels of performance and capabilities.
The result has been a large and competitive market in Ethernet switches,
increasing the number of choices you have as a customer. The wide range of
switch models and capabilities can be confusing. In Chapter 4, we discuss
special purpose switches and their uses.
Operation of Ethernet Switches
GATEWAY :
IEDs are a key component of substation integration and automation technology. Substation
integration involves integrating protection, control, and data acquisition functions into a
minimal number of platforms to reduce capital and operating costs, reduce panel and
control room space, and eliminate redundant equipment and databases.
IEDs facilitate the exchange of both operational and non-operational data. Operational data,
also called supervisory control and data acquisition (SCADA) data, are instantaneous
values of power system analog and status points such as volts, amps, MW, MVAR, circuit
breaker status, switch position. This data is time critical and is used to monitor and control
the power system (e.g., opening circuit breakers, changing tap settings, equipment failure
indication, etc.). Non-operational data consists of files and waveforms such as event
summaries, oscillographic event reports, or sequential events records, in addition to
SCADA-like points (e.g., status and analog points) that have a logical state or a numerical
value. This data is not needed by the SCADA dispatchers to monitor and control the power
system.
Protocol Considerations - There are two capabilities a utility considers for an IED. The
primary capability of an IED is its standalone capabilities, such as protecting the power
system for a relay IED. The secondary capability of an IED is its integration capabilities,
such as its physical interface (e.g., RS-232, RS-485, Ethernet) and its communication
protocol (e.g., DNP3, Modbus, IEC 61850 MMS). Today utilities typically specify the IEDs
they want to use in the substation rather than giving a supplier a turnkey contract to provide
the supplier’s IEDs only in the substation. However, utilities typically choose the IEDs based
on the IED’s standalone capabilities only, without considering the IED’s integration
capabilities.
The need for a standard IED protocol dates back to the late 1980s. IED suppliers
acknowledge that their expertise is in the IED itself – not in two-way communications
capability, the communications protocol, or added IED functionality from a remote user.
Though the industry made some effort to add communications capability to the IEDs, each
IED supplier was concerned that any increased functionality would compromise
performance and drive the IED cost so high that no utility would buy it. Therefore, the
industry vowed to keep costs competitive and performance high as standardization was
incorporated into the IED.
IED and RTU serve two different purposes and you can not swap one for another. IEDs
do not communicate to the SCADA master station directly. They communicate to the
main RTU using serial communication protocol and then RTU send the collate data to
the SCADA master station via FEPs.