NIC Teaming was a highlight we gotten through autonomous equipment merchants such as Broadcom. A isolated piece of program was introduced and you went through a GUI to group your interfacing. Some of the time it was simple to do, now and then it wasn't. Windows Server 2012 presently has NIC Joining built-in. NIC Teaming is the act of holding arrange connectors to make one coherent arrange connector. It gives valuable highlights such as stack adjusting over person joins and failover.

We can do this in two configurations:

- Connecting all network adapters to the same switch.

- Connecting network adapters to different switches.

Within switch-dependent mode, We have two choices for teaming:

- Generic -- 802.3ad

- Dynamic -- 802.1ax -- LACP

Network Availability

One of the reasons you'd utilize NIC Teaming is to supply organize accessibility to your server. This diminishes blackouts and anticipates disappointments such as NIC disappointments, switch disappointments or something as basic as somebody incidentally detaching the organize cable. In case one of the arrange interfacing goes down, all activity will failover to any remaining interfacing on the group. You'll have less amassed transfer speed but your server is still accessible.

Network Performance

Another reason for NIC Teaming is to supply more execution. With many workloads being virtualized you've got more thickness. Total the transmission capacity of all accessible arrange interfacing with NIC Teaming .

Algorithm

Activity is dispersed on outbound activity among accessible joins. There are two alternatives accessible.

Hyper-V switch port

The MAC address of the virtual machine provides the basis for dividing traffic.

Hashing

A hash is made based on the components of each bundle. It is at that point relegated to an accessible arrange connector. Bundles from the same TCP stream are set on the same organize adapter.

Inputs for the hashing function are:

- MAC addresses

- IP addresses

- TCP Ports

Configuration

- In Server Manager click on Local Server and then Disabled next to NIC Teaming

- In the NIC Teaming window,in the bottom left tile under Teams, click on TASKS and then click on New Team

- A new Window appears. In the Team name text box type in a name for this team and then select the adapters to be part of the team. Click on Additional properties and you can make modifications such as the Teaming mode, load balancing mode, Standby adapter, and Primary team interface.

- Team will now be created. I got a few warnings and errors before the team is finally up and running.

- In the Adapters and Interfaces Tile you have the ability to change the team and/or move interfaces into a new or existing team by clicking on TASKS.

- Clicking on Properties for the Team brings up the properties window.

- NIC Teaming is now enabled in Server Manager
https://mobileinfoworld.com/configure-nic-teaming-on-windows-server-2012-r2/

Did you know you could get a very good Cisco switch less than $1000? You can with the Cisco 500 series switches. A rack mountable and stackable managed switch. A Catalyst 2960 can costs around $2400!

Comparable to a Cisco Catalyst 2960 - the next step up from the 500 series - the biggest differences are

- CLI - TextView

- Not quite IOS but the commands are very much the same.

- Marvell silicon

- Not the Cisco manufactured silicon.

For a little and medium trade, the Cisco 500 Series switches are extraordinary. It's a stackable up to 8 switches and is competent of doing 10 Gigabit. Those are highlights required for a developing SMB. But in this post I will be centering on getting it up and running.

To urge the Cisco SMB 500 switch online, you'll either start designing the gadget through a serial support cable or permit the switch to secure a DHCP address. I'll begin the setup at the command line. To begin with thing to take note is, the switch doesn't utilize IOS. It employments a really comparative command line called TextView. The commands are nearly indistinguishable, perhaps indeed the same. The default username and watchword of the Cisco 500 switch is cisco / cisco.

Any other setting is separated off on the cleared out route. As you'll be able see, this SMB switch packs a lot of highlights. The same highlights you'd see on the Catalyst line of switches. After you do make a change, it isn't spared naturally. At the best right of the screen you'll see a flickering ruddy X another to the Spare content. Be beyond any doubt to continuously spare your configuration. The Framework Outline gives us a tall level diagram of the switch. A few of the important items are the stack mode and framework operational mode. By default, the Cisco 500 begins in Layer 2 (L2) mode. You have got your uptime, administrations enabled/disabled, firmware form, and PoE consumption.

There's moreover a pleasant graphical interface of your switch (or switches) with their dynamic ports. One of the leading highlights is the capabilities to stack up to 8 switches. The realistic will show the stack in arrange as Units and will tell you which switch is the Master. You may have taken note the GUI is utilizing standard harbour 80 to oversee the switch. Let's empower secure management by empowering HTTPS and SSH. Within the cleared out Route, extend Security and tap on TCP/UDP Administrations. Empower HTTPS.

In case you would like to adjust the Administration interface you'll do so by extending Organization, extend Administration Interface, and tap on IPv4 Interface.

Alter the Administration VLAN, IP address sort, and portal. The press on Apply.

 

System Mode and Stack Management is an vital region to require note of. Depending on how you configured the stacking cables you may see what kind of stack topology is being utilized. The stack master will too be distinguished - which is additionally identified as a green LED on the physical switch. If you're having inconvenience designing directing at that point take note of the Framework Mode the switch is as of now running in. You'll need L3 mode on the off chance that you wish routing.

That's an presentation to the Cisco Little Commerce 500 Switch. It packs a part of highlights. I scarcely indeed knew almost the Cisco 500 arrangement switch. At whatever point I required a little switch I continuously obtained the Catalyst 2960. The 500 Little Commerce switch is estimated right for SMBs when a Catalyst 2960 is fair out of the budget run. It offers a part of the same highlights as a Catalyst 2960:

- Stacking

- Power over Ethernet (PoE)

- Quality of Service (QoS)

- Spanning Tree

- IPv6

- ACLs

- Has Layer 3 capabilities

- And more...

In related posts I will see into other nitty gritty setup settings. Be on the post for my visitor post on Cisco's blog.
https://mobileinfoworld.com/getting-started-with-ciscos-500-series-smb-switches/

Implementing Cisco IP Switched Networks, 300-115. SDM template of parent  Configure and verify switch administration.

SDM stands for Switching Database Manager. The SDM manages layer 2 and layer 3 switching information. It is maintained on the Ternary Content Addressable Memory, or TCAM. The TCAM itself is used for forwarding lookups. These lookups are done in hardware by the ACL engine. It's supposed to be fast compared to doing it in software. The ACL engine determines how the switch will handle each packet by either permitting or denying. Although the TCAM can provide a performance increase, there are limited amount of entries which can lead to resource contention and exhaustion.

Architecture

Most switches have one TCAM and it is shared between Layer 2 and Layer 3 for forwarding entries, RACLs, VACLs, and QoS ACLs.

The table structure is broken out into the following tables:

- Layer 2 Learning - Port learning policies

- Layer 2 Forwarding - Learned unicast and multicast addresses

- Layer 3 Routing - Used for unicast and multicast route lookups

- ACL and QoS - Identifying traffic according to security and QoS ACLs

SDM Templates

There are three predefined templates:

- Routing Template - Maximizes resources for unicast routing and is used when a switch is used as a router or route aggregator.

- VLAN Template - Unicast routing is disabled and allows for the maximum number of supported MAC addresses. Implemented when a switch is purely a layer 2 device.

- Default Template - The best of both worlds, a mixture between the routing and VLAN template.

Each template has two versions, the Desktop Template and the Aggregator Template. The Aggregator Template is limited to specific switches. When modifying the SDM template on a switch it is required to reload the switch in order to use the new SDM template.

Configuration

Configuring and verifying the SDM template of a switch is simple.

show sdm prefer or show sdm prefer

SW1#show sdm prefer

The current template is "desktop default" template.

Change the SDM Template

config t

sdm prefer

reload

Resources Exhaust

During layer 2 forwarding and learning, new learned addresses are flooded to all ports within the ingress VLAN.

During layer 3 routing, layer 3 unicast and multicast routes are learned only in software and not in TCAM which results in slower routing processes.

 
https://mobileinfoworld.com/switch-sdm-template/