Reading Time: < 1 minute

This is an article that I wrote as a contribuitor for the Aruba blog. Read the full article.

A network switch works at Layer 2 (in the ISO/OSI model) and potentially does not need any configuration because it can learn about the network topology and how to forward properly the Ethernet frames using its internal MAC address or port table.

This is different in other types of devices. For example, Fibre Channel (FC) switches used in some storage area networks (SANs) need a proper and manual configuration (zoning) to define who can talk with who.

In the SMB segment or the entry-level models, there are managed or unmanaged network switches.

Read the rest of the post at: https://blogs.arubanetworks.com/solutions/switch-management-considerations/

Share

Related Posts

  • Stacking network switches: why and why not

    This is an article that I wrote as a contribuitor for the Aruba blog. Read the full article Stacking Network Switches: Why and Why Not. In networking, the term “stack” (or stackable) refers to a group of physical switches that have been cabled and grouped…

  • ESXi 6.x virtual switch ports configuration

    One propertiers of VMware (standard) virtual switches was the number of ports per switch. A parameter (120 was the default in ESXi 5.x) that define how many virtual NIC and/or vmkernel interfaces you can connect to the virtual switch portgroups. This parameter was static and…

  • Which switch to choose for the edge network?

    This is an article that I wrote as a contribuitor for the Aruba blog. Read the full article. What is the edge when it comes to networking terminology? Unfortunately, there isn’t a simple and clear answer. One possible definition of edge switch is a switch located…